1.2 Automatically create mapping sets in the mapping store database (Replace NSI-Plugin)

Once the work to allow multiple mapping sets per dataflow is finished, the following tasks should be done for the data import process:

• Automatically create mapping sets for dataflows.
  • The creation should happen in the same way as we currently create actual content constraints (Using the Estat.Sri.Sdmx.MappingStore library).
  • There should be two mapping sets per dataflow, with validity from and to dates. See more.
  • Adjust the validity dates when there is a creation of a new PIT version, PIT restoration or PIT release. See more:
    • API documentation PIT methods
    • PIT feature documentation
• Automatically store the sql queries for the data retreival.
  • For each related dataflow, create two new entries in the [dbo].[DATASET] table in the mapping store database.
  • The value stored in the QUERY column, should be a query to the set of A and B views [data].[VI_CurrentDataDataFlow_{internal df id}_{table version(A|B)}], implemented in this ticket
• Treat the real PIT release
  • When the release date of a PIT version has passed, during the next data load, update the mapping set information
    • Adjust the release dates if there is not a PIT version anymore.
• Migrate existing users
  • Create corresponding mapping sets for existing dataflows in all data spaces.