Available since: 2017.01
Introduction: why was this built and what does it do?
Any Delft-FEWS configuration is based on the linkages between unique IDs (identifiers for locations, parameters, qualifiers, module-instances etc.). In the early stages of the development of a configuration these IDs were chosen and from that moment on, these IDs are known in the database and cannot be 'renamed' anymore.
While working with the configuration over time, it may happen that a chosen ID (in the past) turns out not be very handy or consistent or may contain typos. For the readability and consistency of a configuration, functionality has become available to 'repair' inconsistencies in these IDs.
The overall idea is that an (optional) configuration file can be added which contains a mapping between the required 'new' ID (= 'configuration-id') and the 'old' ID (='database-id'). Synonym for the 'database-id' is 'persistent-id'. When a new 'configuration-id' is chosen, this ID should be used in the complete configuration.
This functionality will not 'rename' any ID in the database. It will leave the database intact. Since this functionality is a part of the configuration, it can also easily rolled back (if needed).
Use Cases: where to use this functionality for?
Configuration examples
...
Sometimes you want to change some location/parameter/qualifier and module instance ids in you configuration. This happens when you want to keep external and internal ids in sync and the external id changes or when you want to change the ids to make it more consistent. Since 2017.01 this is possible without converting the local, central or open database and archives. To make it still possible for FEWS to resolve the location/parameter/qualifier and module instances in the database or archive you have to create CSV files with two columns that maps the config id to the original persistent database/archive id. When data is written to the database / archive the initial old persistent ids are still used instead of the updated config ids. You only have to list the config en persistent id when they are different from each-other. You can split the CSV files if you want.
...