Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 2.12
edited by Helena
on 2025/05/21 15:04
Change comment: There is no comment for this version
To version 2.16
edited by Helena
on 2025/05/21 15:11
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1105,10 +1105,10 @@
1105 1105  
1106 1106  An organisation which publishes statistical data or reference metadata and wishes to make it available to an SDMX enabled community is called a Data Provider. In terms of the SDMX Information Model, the Data Provider is maintained in a Data Provider Scheme.
1107 1107  
1108 +[[image:1747829109466-595.png]]
1108 1108  
1109 1109  **Figure 11: SDMX-IM of the Data Provider**
1110 1110  
1111 -
1112 1112  Note that the Data Provider does not inherit the hierarchy association. The diagram below shows a logical schematic of the data model classes required to maintain provision agreements
1113 1113  
1114 1114  [[image:1747824123019-181.jpeg]]
... ... @@ -1117,8 +1117,10 @@
1117 1117  
1118 1118  The diagram below is a logical representation of the data required in order to maintain Provision Agreements.
1119 1119  
1120 +[[image:1747829139951-378.png]]
1120 1120  
1121 -==== Figure 13: Logical class diagram of the information contained in the Provision Agreement ====
1122 +(% class="wikigeneratedid" id="HFigure13:LogicalclassdiagramoftheinformationcontainedintheProvisionAgreement" %)
1123 +**Figure 13: Logical class diagram of the information contained in the Provision Agreement**
1122 1122  
1123 1123  A Provision Agreement is structural metadata. Each Provision Agreement must reference a Data Provider and a Dataflow or Metadataflow Definition. The Data Provider and the Dataflow/Metadataflow Definition must exist already in order to set up a Provision Agreement.
1124 1124  
... ... @@ -1146,13 +1146,12 @@
1146 1146  
1147 1147  === 7.3.3 Data and Metadata Constraints: Model ===
1148 1148  
1151 +[[image:1747829204737-370.png]]
1149 1149  
1153 +**Figure 15: Logical class diagram showing inheritance between and reference to constrainable artifacts**
1150 1150  
1151 -==== Figure 15: Logical class diagram showing inheritance between and reference to constrainable artifacts ====
1155 +The class diagram above shows that DataProvider, DataflowDefinition, MetadataflowDefinition, ProvisionAgreement, DataStructureDefinition, MetadataStructureDefinition, SimpleDatasource and QueryDatasource are all concrete sub-classes of ConstrainableArtefact and can therefore have Constraints specified. Note that the actual Constraint as submitted is associated to the reference classes which inherit from ConstrainableRef: these are used to refer to the classes to which the Constraint applies.
1152 1152  
1153 -The class diagram above shows that DataProvider, DataflowDefinition, MetadataflowDefinition, ProvisionAgreement, DataStructureDefinition, MetadataStructureDefinition, SimpleDatasource and QueryDatasource are all concrete sub-classes of ConstrainableArtefact and can therefore have Constraints specified. Note that the actual Constraint as submitted is associated to the reference classes which inherit from ConstrainableRef: these are used to refer to the classes to which the Constraint applies.
1154 -
1155 -
1156 1156  The content of the Constraint can be found in the SDMX Information Model document.
1157 1157  
1158 1158  == 7.4 Data and Metadata Registration ==
... ... @@ -1187,11 +1187,14 @@
1187 1187  
1188 1188  The Registration has an action attribute which takes one of the following values:
1189 1189  
1190 -|**Action Attribute Value**|**Behaviour**
1191 -|Append|Add this Registration to the registry
1192 -|Replace|Replace the existing Registration with identified by the id in the Registration of the Submit Registration Request
1193 -|Delete|Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
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
1194 1194  
1197 +[[image:1747829290890-122.png]]
1198 +
1195 1195  **Figure 17: Logical Class Diagram of Registration of Data and Metadata**
1196 1196  
1197 1197  The Query Datasource is an abstract class that represents a data source which can understand an SDMX-ML query (SOAPDatasource) or RESTful query
... ... @@ -1206,25 +1206,19 @@
1206 1206  
1207 1207  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.
1208 1208  
1209 -|**Indexing Required**|**Registration Process Activity**
1210 -|indexTimeSeries|Extract all the series keys and create a KeySet(s) Constraint.
1211 -|indexDataSet|(((
1212 -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
1213 -
1214 -Regions containing Member Selections of Dimension Components of the Constraints model in the SDMX-IM, and the associated Selection Value.
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.
1215 1215  )))
1216 -|indexReportingPeriod|(((
1218 +|(% style="width:185px" %)indexReportingPeriod|(% style="width:1686px" %)(((
1217 1217  This applies only to a registered dataset.
1218 -
1219 1219  Extract the Reporting Begin and Reporting End from the Header of the Message containing the data set, and create a Reference Period constraint.
1220 1220  )))
1221 -|indexAttributes|(((
1222 +|(% style="width:185px" %)indexAttributes|(% style="width:1686px" %)(((
1222 1222  **Data Set**
1223 -
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
1225 -
1226 1226  **Metadata Set**
1227 -
1228 1228  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.
1229 1229  )))
1230 1230  
... ... @@ -1234,14 +1234,13 @@
1234 1234  
1235 1235  === 7.4.3 Registration Response ===
1236 1236  
1237 -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
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 1238  
1239 -“Success”, “Warning” or “Failure”.
1240 -
1241 1241  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.
1242 1242  
1243 1243  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:
1244 1244  
1241 +[[image:1747829477882-750.png]]
1245 1245  
1246 1246  **Figure 18: Logical class diagram showing the registration response**
1247 1247  
1747829109466-595.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +30.4 KB
Content
1747829139951-378.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +21.1 KB
Content
1747829204737-370.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +55.8 KB
Content
1747829290890-122.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +41.4 KB
Content
1747829477882-750.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +24.6 KB
Content