Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 9.4
edited by Helena
on 2025/05/23 13:07
Change comment: There is no comment for this version
To version 12.1
edited by Artur
on 2025/05/27 15:51
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.helena
1 +xwiki:XWiki.arturkryazhev
Content
... ... @@ -1154,11 +1154,11 @@
1154 1154  
1155 1155  The Registration has an action attribute which takes one of the following values:
1156 1156  
1157 -(% style="width:970.294px" %)
1158 -|(% style="width:212px" %)**Action Attribute Value**|(% style="width:756px" %)**Behaviour**
1159 -|(% style="width:212px" %)Append|(% style="width:756px" %)Add this Registration to the registry
1160 -|(% style="width:212px" %)Replace|(% style="width:756px" %)Replace the existing Registration with identified by the id in the Registration of the Submit Registration Request
1161 -|(% style="width:212px" %)Delete|(% style="width:756px" %)Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
1157 +(% style="width:798.294px" %)
1158 +|(% style="width:212px" %)**Action Attribute Value**|(% style="width:582px" %)**Behaviour**
1159 +|(% style="width:212px" %)Append|(% style="width:582px" %)Add this Registration to the registry
1160 +|(% style="width:212px" %)Replace|(% style="width:582px" %)Replace the existing Registration with identified by the id in the Registration of the Submit Registration Request
1161 +|(% style="width:212px" %)Delete|(% style="width:582px" %)Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
1162 1162  
1163 1163  [[image:1747829290890-122.png]]
1164 1164  
... ... @@ -1176,16 +1176,17 @@
1176 1176  
1177 1177  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.
1178 1178  
1179 -|(% style="width:185px" %)**Indexing Required**|(% style="width:1686px" %)**Registration Process Activity**
1180 -|(% style="width:185px" %)indexTimeSeries|(% style="width:1686px" %)Extract all the series keys and create a KeySet(s) Constraint.
1181 -|(% style="width:185px" %)indexDataSet|(% style="width:1686px" %)(((
1179 +(% style="width:860.294px" %)
1180 +|(% style="width:185px" %)**Indexing Required**|(% style="width:672px" %)**Registration Process Activity**
1181 +|(% style="width:185px" %)indexTimeSeries|(% style="width:672px" %)Extract all the series keys and create a KeySet(s) Constraint.
1182 +|(% style="width:185px" %)indexDataSet|(% style="width:672px" %)(((
1182 1182  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.
1183 1183  )))
1184 -|(% style="width:185px" %)indexReportingPeriod|(% style="width:1686px" %)(((
1185 +|(% style="width:185px" %)indexReportingPeriod|(% style="width:672px" %)(((
1185 1185  This applies only to a registered dataset.
1186 1186  Extract the Reporting Begin and Reporting End from the Header of the Message containing the data set, and create a Reference Period constraint.
1187 1187  )))
1188 -|(% style="width:185px" %)indexAttributes|(% style="width:1686px" %)(((
1189 +|(% style="width:185px" %)indexAttributes|(% style="width:672px" %)(((
1189 1189  **Data Set**
1190 1190  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
1191 1191  **Metadata Set**
... ... @@ -1231,11 +1231,12 @@
1231 1231  1. A validity period which defines both when the subscription becomes active and expires. The subscriber may be sent a notification on expiration of the subscription.
1232 1232  1. A selector which specifies which type of events are of interest. The set of event types is:
1233 1233  
1234 -|(% style="width:319px" %)**Event Type**|(% style="width:1553px" %)**Comment**
1235 -|(% style="width:319px" %)STRUCTURAL_REPOSITORY_EVENTS|(% style="width:1553px" %)Life-cycle changes to Maintainable Artefacts in the structural metadata repository.
1236 -|(% style="width:319px" %)DATA_REGISTRATION_EVENTS|(% style="width:1553px" %)Whenever a published dataset is registered. This can be either a SDMXML data file or an SDMX conformant database.
1237 -|(% style="width:319px" %)METADATA_REGISTRATION_EVENTS|(% style="width:1553px" %)Whenever a published metadataset is registered. This can be either a SDMXML reference metadata file or an SDMX conformant database.
1238 -|(% style="width:319px" %)ALL_EVENTS|(% style="width:1553px" %)All events of the specified EventType
1235 +(% style="width:1031.29px" %)
1236 +|(% style="width:319px" %)**Event Type**|(% style="width:678px" %)**Comment**
1237 +|(% style="width:319px" %)STRUCTURAL_REPOSITORY_EVENTS|(% style="width:678px" %)Life-cycle changes to Maintainable Artefacts in the structural metadata repository.
1238 +|(% style="width:319px" %)DATA_REGISTRATION_EVENTS|(% style="width:678px" %)Whenever a published dataset is registered. This can be either a SDMXML data file or an SDMX conformant database.
1239 +|(% style="width:319px" %)METADATA_REGISTRATION_EVENTS|(% style="width:678px" %)Whenever a published metadataset is registered. This can be either a SDMXML reference metadata file or an SDMX conformant database.
1240 +|(% style="width:319px" %)ALL_EVENTS|(% style="width:678px" %)All events of the specified EventType
1239 1239  
1240 1240  === 7.5.3 Wildcard Facility ===
1241 1241  
... ... @@ -1289,14 +1289,13 @@
1289 1289  
1290 1290  Whenever a dataset or metadata-set is registered a registration event is created. A subscription may be observing all data or metadata registrations, or it may focus on specific registrations as shown in the table below:
1291 1291  
1292 -|(% style="width:405px" %)**Selector**|(% style="width:1467px" %)**Comment**
1293 -|(% style="width:405px" %)DataProvider|(% style="width:1467px" %)Any datasets or metadata sets registered by the specified data provider will activate the notification.
1294 -|(% style="width:405px" %)ProvisionAgreement|(% style="width:1467px" %)Any datasets or metadata sets registered for the provision agreement will activate the notification.
1295 -|(% style="width:405px" %)Dataflow (&Metadataflow)|(% style="width:1467px" %)Any datasets or metadata sets registered for the specified dataflow (or metadataflow) will activate the notification.
1296 -|(% style="width:405px" %)DataStructureDefinition & MetadataStructureDefinition|(% style="width:1467px" %)Any datasets or metadata sets registered for those dataflows (or metadataflows) that are based on the specified Data Structure Definition will
1297 -|(% style="width:405px" %)**Selector**|(% style="width:1467px" %)**Comment**
1298 -|(% style="width:405px" %) |(% style="width:1467px" %)activate the notification.
1299 -|(% style="width:405px" %)Category|(% style="width:1467px" %)Any datasets or metadata sets registered for those dataflows, metadataflows, provision agreements that are categorised by the category.
1294 +(% style="width:974.294px" %)
1295 +|(% style="width:295px" %)**Selector**|(% style="width:677px" %)**Comment**
1296 +|(% style="width:295px" %)DataProvider|(% style="width:677px" %)Any datasets or metadata sets registered by the specified data provider will activate the notification.
1297 +|(% style="width:295px" %)ProvisionAgreement|(% style="width:677px" %)Any datasets or metadata sets registered for the provision agreement will activate the notification.
1298 +|(% style="width:295px" %)Dataflow (&Metadataflow)|(% style="width:677px" %)Any datasets or metadata sets registered for the specified dataflow (or metadataflow) will activate the notification.
1299 +|(% style="width:295px" %)DataStructureDefinition & MetadataStructureDefinition|(% style="width:677px" %)Any datasets or metadata sets registered for those dataflows (or metadataflows) that are based on the specified Data Structure Definition will activate the notification.
1300 +|(% style="width:295px" %)Category|(% style="width:677px" %)Any datasets or metadata sets registered for those dataflows, metadataflows, provision agreements that are categorised by the category.
1300 1300  
1301 1301  The event will also capture the semantic of the registration: deletion or replacement of an existing registration or a new registration.
1302 1302