UpdatedAfter for non-observation level attributes
The purpose of this ticket is to extend and improve the functionality of the linked tickets related to the updatedAfter
feature for data and referential metadata.
- The implementation done in that ticket allows to store timestamp information for Append and Replace actions for observation level attributes and for ref. metadata attributes at partial key level.
- The work required in this ticket is to cover the functional requirement for attributes attached to Groups and Series, for dataset-level attributes and for dataflow level referential metadata:
- Data: If Group and Series attributes have been updated (before the updatedAfter datetime) but related observations haven't, then the web service should return either the Group and Series attributes that have changed or the dataflow attributes if only they have changed.
- Ref. metadata: If dataflow level ref. metadata attributes have been updated (before the updatedAfter datetime), then the web service should return those ref. metadata attributes
Tasks:
-
Extend the database model to store timestamp information (for usage by the updatedAfter query) for: -
Group and Series attributes -
Dataflow level attributes -
Dataflow level referential metadata attributes
-
-
Change the data and referential metadata views used by the NSIWS when the updatedAfter parameter is specified. -
Create a solution that do not require to present the information for the lower level components, when they have not been updated. For example, if the only change done after a specific time is the change in value of a dataflow level attribute, the view should not return all the values for the observation level attributes.
-
-
Provide the database migration scripts. -
Update the database model design and documentation.
Edited by Pedro Carranza