Last modified by Helena on 2025/09/10 11:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 2 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1188,14 +1188,11 @@ 1188 1188 1189 1189 The Registration has an action attribute which takes one of the following values: 1190 1190 1191 -(% style="width:970.294px" %) 1192 -|(% style="width:212px" %)**Action Attribute Value**|(% style="width:756px" %)**Behaviour** 1193 -|(% style="width:212px" %)Append|(% style="width:756px" %)Add this Registration to the registry 1194 -|(% style="width:212px" %)Replace|(% style="width:756px" %)Replace the existing Registration with identified by the id in the Registration of the Submit Registration Request 1195 -|(% style="width:212px" %)Delete|(% style="width:756px" %)Delete the existing Registration identified by the id in the Registration of the Submit Registration Request 1191 +|**Action Attribute Value**|**Behaviour** 1192 +|Append|Add this Registration to the registry 1193 +|Replace|Replace the existing Registration with identified by the id in the Registration of the Submit Registration Request 1194 +|Delete|Delete the existing Registration identified by the id in the Registration of the Submit Registration Request 1196 1196 1197 -[[image:1747829290890-122.png]] 1198 - 1199 1199 **Figure 17: Logical Class Diagram of Registration of Data and Metadata** 1200 1200 1201 1201 The Query Datasource is an abstract class that represents a data source which can understand an SDMX-ML query (SOAPDatasource) or RESTful query ... ... @@ -1210,19 +1210,25 @@ 1210 1210 1211 1211 Information in the data or metadata set is extracted and placed in one or more Content Constraints (see the Constraints model in the SDMX Information Model – Section 2 of the SDMX Standards). The information to be extracted is indicated by the Boolean values set on the Provision Agreement as shown in the table below. 1212 1212 1213 -|(% style="width:185px" %)**Indexing Required**|(% style="width:1686px" %)**Registration Process Activity** 1214 -|(% style="width:185px" %)indexTimeSeries|(% style="width:1686px" %)Extract all the series keys and create a KeySet(s) Constraint. 1215 -|(% style="width:185px" %)indexDataSet|(% style="width:1686px" %)((( 1216 -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. 1210 +|**Indexing Required**|**Registration Process Activity** 1211 +|indexTimeSeries|Extract all the series keys and create a KeySet(s) Constraint. 1212 +|indexDataSet|((( 1213 +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 1214 + 1215 +Regions containing Member Selections of Dimension Components of the Constraints model in the SDMX-IM, and the associated Selection Value. 1217 1217 ))) 1218 -| (% style="width:185px" %)indexReportingPeriod|(% style="width:1686px" %)(((1217 +|indexReportingPeriod|((( 1219 1219 This applies only to a registered dataset. 1219 + 1220 1220 Extract the Reporting Begin and Reporting End from the Header of the Message containing the data set, and create a Reference Period constraint. 1221 1221 ))) 1222 -| (% style="width:185px" %)indexAttributes|(% style="width:1686px" %)(((1222 +|indexAttributes|((( 1223 1223 **Data Set** 1224 + 1224 1224 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 1226 + 1225 1225 **Metadata Set** 1228 + 1226 1226 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 SDMX-IM. Note that the content is not stored in the Selection Value. 1227 1227 ))) 1228 1228 ... ... @@ -1232,13 +1232,14 @@ 1232 1232 1233 1233 === 7.4.3 Registration Response === 1234 1234 1235 -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 Submit Registration class has a status field which is either set to “Success”, “Warning” or “Failure”.1238 +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 Submit Registration class has a status field which is either set to 1236 1236 1240 +“Success”, “Warning” or “Failure”. 1241 + 1237 1237 If the registration has succeeded, a Registration will be returned - this holds the Registry-allocated Id of the newly registered Datasource plus a Datasource holding the URL to access the dataset, metadataset, or query service. 1238 1238 1239 1239 The Registration Response returns set of registration status (one for each registration submitted) in terms of a Status Message (this is common to all Registry Responses) that indicates success or failure. In the event of registration failure, a set of Message Text are returned, giving the error messages that occurred during registration. It is entirely possible when registering a batch of datasets, that the response will contain some successful and some failed statuses. The logical model for the Registration Response is shown below: 1240 1240 1241 -[[image:1747829477882-750.png]] 1242 1242 1243 1243 **Figure 18: Logical class diagram showing the registration response** 1244 1244
- 1747829290890-122.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -xwiki:XWiki.helena - Size
-
... ... @@ -1,1 +1,0 @@ 1 -41.4 KB - Content
- 1747829477882-750.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -xwiki:XWiki.helena - Size
-
... ... @@ -1,1 +1,0 @@ 1 -24.6 KB - Content