Since 2017.02. The result of the analysis, a list of expired datasets, will be written to this file
Since 2023.01. The maximum amount of data sets in a single output file. If there more data sets then the maximum then aditional outputfiles will be written with the format outputfile_n.csv (outputfile_1.csv)
Since 2017.02. The task "remove data from archive" will move the files from the archive to this folder.
The events of the archive are stored in a folder. Each area will have a sub-folder in this folder. The data management tool uses the event information to determine
which data sets are expired.
The folder which contains the config for the archive.
By the default the base path is equal to the base folder of the archive. However it is possible to define rule per sub folder. In this case the base path can overrule the base path of the archive.
The life time which will be applied when it is not possible to find more specific life time rule in the config.
The action which will be applied when it is not possible to find more specific life time rule in the config. This action is a custom action and will not be used by
the RemoveDataFromArchiveTask.
Multiple lifeTimeSimulatedDataSets can be defined for different source ids, only 1 lifeTimeSimulatedDataSets can be defined without source id.
Multiple lifeTimeObservedDataSets can be defined for different source ids, only 1 lifeTimeObservedDataSets can be defined without source id.
Multiple lifeTimeExternalForecastDataSets can be defined for different source ids, only 1 lifeTimeExternalForecastDataSets can be defined without source id.
The archive can store FEWS messages. At the moment the only messages supported are the forecaster notes. This element can be used to configure a single life time
rule for all messsages data sets.
This element can be used to configure a single life time rule for the configuration data sets.
This element can be used to configure a single life time rule for the rating curve data sets.
Since 2017.02. This element can be used to configure a single life time rule for the product data sets.
Since 2017.02. This element can be used to configure a single life time rule for the snapshots.
Since 2018.02. This element can be used to configure a single life time rule for a data set containing log messages
Data sets which are part of an event can have a different life time than the regular life time. It is possible to define a life time for each event type.
This action is for custom purposes only. It can be used when the output of the this task is used by a custom tool. It is not used by the remove data from archive
task.
This tool can not handle multiple different source ids in 1 data set. Only data sets with identical (or missing) source ids are supported.
This action is for custom purposes only. It can be used when the output of the this task is used by a custom tool. It is not used by the remove data from archive
task.