Skip to Content
Last modified by Elena on 2025/09/10 11:19
From version 2.29
edited by Helena
on 2025/07/02 15:33
Change comment: There is no comment for this version
To version 2.26
edited by Helena
on 2025/07/02 15:31
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -897,13 +897,13 @@
897 897  
898 898  ~1. Without the //updatedAfter//, //includeHistory//, //detail//, //attributes// or //measures// URL parameters:
899 899  
900 -The response message should contain the retrieved data in a //Replace// dataset (instead of the previous *information* dataset).
900 +The response message should contain the retrieved data in a *Replace* dataset (instead of the previous *information* dataset).
901 901  
902 -2. Without the //updatedAfter// and //includeHistory//, but with //detail//, //attributes// or //measures// URL parameters:
902 +2. Without the *updatedAfter* and *includeHistory*, but with *detail*, *attributes* or *measures* URL parameters:
903 903  
904 -The response message should contain the retrieved data in a //Merge// dataset (instead of the previous *Information* dataset).
904 +The response message should contain the retrieved data in a *Merge* dataset (instead of the previous *Information* dataset).
905 905  
906 -3. With the //updatedAfter// URL parameter:
906 +3. With the *updatedAfter* URL parameter:
907 907  
908 908  The response must include the information of all previously updated, inserted and deleted data or data-related reference metadata, even if bulk deletions have been used. One of the two approaches are possible:
909 909  
... ... @@ -912,7 +912,8 @@
912 912  * a //Delete// dataset for entirely deleted observations, for entirely deleted sets of (data-related reference metadata) attribute values attached to specific dimension combinations and for individually deleted mesure, attribute and reference metadata values and
913 913  a //Merge// dataset for all other updated or inserted observation, attribute and data-related reference metadata values.
914 914  
915 -The DB synchronization use case requires that the generated response must always allow achieving to replicate the exact same punctual data content as currently stored in the queried data source.
915 +
916 + The DB synchronization use case requires that the generated response must always allow achieving to replicate the exact same punctual data content as currently stored in the queried data source.
916 916  
917 917  1. With the *includeHistory* URL parameter:
918 918