Skip to Content
Last modified by Artur on 2025/09/30 13:28
From version 21.13
edited by Helena
on 2025/06/08 16:42
Change comment: There is no comment for this version
To version 21.11
edited by Helena
on 2025/06/08 16:41
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -933,7 +933,7 @@
933 933  
934 934  **Figure 16: Schematic of the Objects Concerned with Registration**
935 935  
936 -==== 7.4.2.2 Registration Request Model ====
936 +**7.4.2.2 Registration Request Model**
937 937  
938 938  The following UML diagram shows the composition of the registration request. Each request is made up of one or more Registrations, one per dataset to be registered. The Registration can optionally have information, which has been extracted from the Registration:
939 939  
... ... @@ -945,11 +945,13 @@
945 945  
946 946  The Registration has an action attribute which takes one of the following values:
947 947  
948 +:
949 +
948 948  (((
949 -|(% style="width:224px" %)**Action Attribute Value**|(% style="width:1457px" %)**Behaviour**
950 -|(% style="width:224px" %)Append|(% style="width:1457px" %)Add this Registration to the registry
951 -|(% style="width:224px" %)Replace|(% style="width:1457px" %)Replace the existing Registration with identified by the id in the Registration of the SubmitRegistrationRequest
952 -|(% style="width:224px" %)Delete|(% style="width:1457px" %)Delete the existing Registration identified by the id in the Registration of the SubmitRegistrationRequest
951 +|**Action Attribute Value**|**Behaviour**
952 +|Append|Add this Registration to the registry
953 +|Replace|Replace the existing Registration with identified by the id in the Registration of the SubmitRegistrationRequest
954 +|Delete|Delete the existing Registration identified by the id in the Registration of the SubmitRegistrationRequest
953 953  )))
954 954  
955 955  [[image:SDMX 3.1 Section 5_en_90b3c64a.jpg||height="434" width="579"]]
... ... @@ -968,24 +968,30 @@
968 968  
969 969  https:~/~/github.com/sdmx-twg/sdmx-rest/blob/master/doc/availability.md
970 970  
973 +:
974 +
971 971  (((
972 -(% style="width:918.835px" %)
973 -|**Indexing Required**|(% style="width:745px" %)**Registration Process Activity**
974 -|indexTimeSeries|(% style="width:745px" %)Extract all the series keys and create a KeySet(s) Constraint.
975 -|indexDataSet|(% style="width:745px" %)Extract all the codes and other content of the Key value of the Series Key in a Data Set and create one or more Cube Regions containing Member Selections of Dimension Components of the Constraints model in the SDMX-IM, and the associated Selection Value.
976 -|indexReportingPeriod|(% style="width:745px" %)(((
976 +|**Indexing Required**|**Registration Process Activity**
977 +|indexTimeSeries|Extract all the series keys and create a KeySet(s) Constraint.
978 +|indexDataSet|Extract all the codes and other content of the Key value of the Series Key in a Data Set and create one or more Cube Regions containing Member Selections of Dimension Components of the Constraints model in the SDMX-IM, and the associated Selection Value.
979 +|indexReportingPeriod|(((
977 977  This applies only to a registered __dataset__.
981 +
978 978  Extract the Reporting Begin and Reporting End from the Header of the Message containing the data set, and create a Reference Period constraint.
979 979  )))
980 -|indexAttributes|(% style="width:745px" %)(((
984 +|indexAttributes|(((
981 981  **Data Set**
986 +
982 982  Extract the content of the Attribute Values in a Data Set and create one or more Cube Regions containing Member Selections of Data Attribute Components of the Constraints model in the SDMXIM, and the associated Selection Value
983 983  
984 984  **Metadata Set**
985 -Indicate the presence of a Reported Attribute by creating one or more Cube Regions containing Member Selections of Metadata Attribute Components of the Constraints model in the
990 +
991 +Indicate the presence of a Reported Attribute by creating one or more Cube Regions containing Member Selections of Metadata Attribute
992 +
993 +Components of the Constraints model in the
986 986  )))
987 -|**Indexing Required**|(% style="width:745px" %)**Registration Process Activity**
988 -| |(% style="width:745px" %)SDMX-IM. Note that the content is not stored in the Selection Value.
995 +|**Indexing Required**|**Registration Process Activity**
996 +| |SDMX-IM. Note that the content is not stored in the Selection Value.
989 989  )))
990 990  
991 991  Constraints that specify the contents of a //QueryDatasource// are submitted to the Registry via the structure submission service (i.e., the RESTful API).
... ... @@ -992,7 +992,7 @@
992 992  
993 993  The Registration must reference the ProvisionAgreement to which it relates.
994 994  
995 -=== 7.4.3 Registration Response ===
1003 +===== {{id name="_Toc90825"/}}7.4.3 Registration Response =====
996 996  
997 997  After a registration request has been submitted to the registry, a response is returned to the submitter indicating success or failure. Given that a registration request can hold many Registrations, then there must be a registration status for each Registration. The SubmitRegistration class has a status field, which is either set to “Success”, “Warning” or “Failure”.
998 998