Allow storing referential metadata linked to either a DF or DSD
As described in the epic, referential metadata can belong to a dataflow or a datastructure. At the moment, reference metadata values at lower levels are not saved specifically per dataflow, but are generic for the whole DSD. Vice-versa, reference metadata values at top level are always saved specifically per dataflow, but cannot be provided generically for the whole DSD. The task is to extend the transfer service, to allow storing the referential metadata at any level in a way that it can be linked to either a dataflow or a datastructure.
Tasks:
-
Change data database model to support storage at both dataflow and datastructure levels. -
As agreed with practice team, all existing referential metadata, by default, will be linked to the DSD.
-
-
Add/Change database views in the way that referential metadata linked to both the DSD and Dataflow can be consumed by the NSIWS. - To be defined if a single view will combine the referential metadata from both DSD and Dataflow.
-
Migrate existing users to adopt the changes required in their databases. -
Update documentation.
As discussed in the standup meeting, in the case when the only import(s) of referential metadata are done using the DSD reference, there will not be any initialization of mappingsets. This implies that, in this case, the referential metadata cannot be downloaded using the NSIWS; It will throw an error, saying that there are not mappingsets found for that dataflow.