[SDMX-RI] SDMX-RI implementation for .Stat Suite
As a .Stat DLM user, I would like
- to be able to use Mapping Assistant to define mappings on data in non-dissemination space and to transfer the mapped data using an SDMX-NSI ws into another internal space (e.g. dissemination)
- to be able to use Mapping Assistant to define mappings on data in a dissemination space and to externally expose mapped data using an SDMX-NSI ws e.g. for reporting purposes
User scenario:
-
User uploads "unmapped" DSD and its data to the design, process etc space.
-
User opens the Mapping Assistant and performs there the following actions (all using the Mapping Assistant):
- Upload the target DSD/Dataflow (which is already defined in the dissemination space) to be used for the mapping
- Choose the DSD/Dataflow and get the corresponding data query of the source data in the design/process/.. space (it should be clear for the user with which space the user is working)
- Create the mapping from the source data to the target DSD/Dataflow
-
User can see/view the mapped dataflow with data using an external space in the DLM
-
User transfers data from the mapped dataflow in the external space to the dissemination space in the DLM
-
User (re)opens the Mapping Assistant and performs there the following actions (all using the Mapping Assistant):
- Upload the target DSD/Dataflow (which is already defined in the Global SDMX registry for reporting) to be used for the mapping
- Choose the DSD/Dataflow and get the corresponding data query of the source data in the dissemination space (it should be clear for the user with which space the user is working)
- Create the mapping from the source data to the target DSD/Dataflow
-
User uses external (mapping-enabled) NSI web service to extract data of the disseminated mapped dataflow
-
DE is configured to allow searching and visualising data of the disseminated mapped dataflow
Open questions: When working with mappings on multiple spaces:
- Is one Mapping Assistant sufficient?
- Is one mapped NSI web service for internal use and one for external use sufficient?
- If one mapped NSI web service for all internal use is sufficient, how can the user distinguish the spaces from which the data are originally coming from? Is is possible to use one NSI web service for both non-mapped and mapped data? (Note: ISTAT should be contacted on this question as they have done work in this sense) If this is possible then our current infrastructure with one NSI web service per space per environment (internal/external) serving both non-mapped and mapped data would be sufficient. Acceptance criteria Do the initial analysis of the requirements and propose the target architecture (e.g location of the Mapping Assistant, required number of Mapping Store databases, required number and configuration of internal and external NSI WS with the mapped data etc.) Try the first implementation in the PM environment Use the Mapping Assistant available in file://T:\SDD\Jens\mappingassistant-6.4.0@76e5ea12106.zip When it is successful in PM, the SDMX-RI implementation should become a part of the deployment process for any environment
Issue 1:
Difficult to create a dataset because table names are not informative enough to know where to find the required data
The issue comes from that when you set the ignore production flag to false, then a dataflow that doesnt have a mapping throws a 500 error and doesnt continue to the next dataretriever in the list of dataretrievers. So e.g. i put the default Estat dataretriever first in the list (in web.config) and query a dataflow that was created by the DLM, then the Estat data retriever will throw the 500 error and wont fallback on the next dataretriever in the list of dataretrievers, which would be the Dotstat dotstat dataretriever.