[Snapshot] - Enhancement in order to provide a first concept of revision and source reference
[Snapshot] - Enhancement in order to provide a first concept of revision and source reference
Requirements
New configuration items must be introduced. Must work with LSC / web services queries. See below actual and expected in order to have a more broad idea of the requirements.
Descriptive title for this enhancement
[Snapshot] - Enhancement in order to provide a first concept of revision and source reference
Actual behavior
Snapshot is a manual operation and has not concept of retention nor origin of data sources.
Expected behavior
It must be able to have a concept of retention date as well as minimum number of "revisions" to be kept. A new attribute containing the origin of the source must be present. The backend configuration should reflect the changes for snapshot, allowing the above configuration as well as adding the possibility to automate the creation of snapshot upon account save.
Step by step description of new behavior
A possible new tab within configuration must be created (snapshot), adding :
- Retention date.
- Minimum retention.
- Automatic snapshot.
A possible new tab within configuration must be created (aggregation?), adding :
- The possibility to add the origin/source of the received data.
When creating a snapshot, there would be an invisible option (only in the GUI) allowing LSC or web service queries to specify the origin of the data.
Benefits
One of the many possible benefits would be to allow aggregation and disaggregation. Knowing the source of the data allows creating a trust level. (To be developed).
Possible Drawbacks
None.
Applicable Issues
None