Difference between revisions of "Maintainable"

From Fusion Registry Wiki
Jump to navigation Jump to search
(→‎Maintainable Properties)
(→‎Maintainable Structures)
 
Line 39: Line 39:
 
| Agency Scheme || 1.0 || Yes  || List of [[Agency|Agencies]]  (every Maintainable type is owned by ONE Agency)
 
| Agency Scheme || 1.0 || Yes  || List of [[Agency|Agencies]]  (every Maintainable type is owned by ONE Agency)
 
|-
 
|-
−
| Data Provider Scheme || Example || Example || Example
+
| Data Provider Scheme || 2.0|| Yes || List of Data Providers (a Data Provider report data)
 
|-
 
|-
−
| Data Consumer Scheme || Example || Example || Example
+
| Data Consumer Scheme || 2.0 || Yes  || List of Data Consumers - used for authorisation to resources
 
|-
 
|-
−
| Data Structure Definition || Example || Example || Example
+
| Data Structure Definition || 2.0|| Yes  || Defines the structure of a Dataset
 
|-
 
|-
−
| Dataflow || Example || Example || Example
+
| Dataflow || 2.0|| Yes  || Defines a data ‘topic’ for collection or dissemination
 
|-
 
|-
−
| Category Scheme || Example || Example || Example
+
| Category Scheme || 2.0|| Yes  || List of Categories, can be hierarchical, typically used to categorise datasets
 
|-
 
|-
−
| Categorisation || Example || Example || Example
+
| Categorisation || 2.0|| Yes  || Links a Category to ANY other Identifiable Structure (e.g Category to a Dataflow)
 
|-
 
|-
−
| Codelist || Example || Example || Example
+
| Codelist || 1.0 || Yes  || List of Codes (e.g Country Codelist)
 
|-
 
|-
−
| Hierarchical Codelist || Example || Example || Example
+
| Concept Scheme || 1.0|| Yes  || List of Concepts (used by Data Structures, Metadata Structures)
 
|-
 
|-
−
| Concept Scheme || Example || Example || Example
+
| Hierarchical Codelist || 2.0 || Yes  || Enables construction of one or more Code Hierarchies (view on top of Codelists)
 
|-
 
|-
−
| Metadata Structure || Example || Example || Example
+
| Metadata Structure || 2.0 || Yes  || Defines the structure of a Metadata Report
 
|-
 
|-
−
| Metadataflow || Example || Example || Example
+
| Metadataflow || 2.0 || No || Defines a metadata ‘topic’ for collection or dissemination
 
|-
 
|-
−
| Structure Set || Example || Example || Example
+
| Structure Set || 2.0 || Yes || Container for mapping between structures (Codelist Map, Dataflow Map)
 
|-
 
|-
−
| Content Constraint || Example || Example || Example
+
| Content Constraint || 2.0 || Yes || Defines restrictions on Codelists or Series for Data Reporting
 
|-
 
|-
−
| Attachment Constraint || Example || Example || Example
+
| Attachment Constraint || 2.0 || No ||  
 
|-
 
|-
−
| Provision Agreement || Example || Example || Example
+
| Provision Agreement || 2.0 || Yes|| Links a Data Provider to a Dataflow for Data Reporting
 
|-
 
|-
−
| Process || Example || Example || Example
+
| Process || 2.0 || No ||  
 
|}
 
|}

Latest revision as of 06:07, 18 March 2020

Overview

An Maintainable Structure is an abstract term for any structure which is a top level container of information, i.e a Maintianable structure is maintained inside any other structure. An example is a Codelist which is a Maintainable structure, and a Code which is not Maintainable as it is maintained as an artefact inside its parent Codelist.

A Maintanable structure is both Identifiable and Nameable, it also must contain a reference to the Agency that is responsible for maintaining it.

Maintainable Properties

Property Mandatory Description
Id Yes Identifier - Inherited from Identifiable
URN Yes Unique Identifier - Inherited from Identifiable
Name Yes Human readable name, multilingual supported - Inherited from Nameable
Description No Human readable description , multilingual supported - Inherited from Nameable
Agency Id Yes The organisation responsible for the creation of, and ongoing maintenance of this structure
Version Yes The version of this structure
Valid From No If applicable, the date from which this structure was valid. See Time Formats
Valid To No If applicable, the date from which this structure was no longer valid. See Time Formats
Is Final No Indicates there will be no major changes to this structure

Maintainable Structures

The following lists all the maintainable structures which the Fusion Registry supports. Note, some of these structures are not part of the SDMX Specification. Structures which are part of the SDMX specification are indicated in the SDMX Version column which is used to indicate which version of SDMX the structure was introduced in. For non-SDMX structures the entry in this column is N/A.

Maintainable Type SDMX Version UI Support Description
Agency Scheme 1.0 Yes List of Agencies (every Maintainable type is owned by ONE Agency)
Data Provider Scheme 2.0 Yes List of Data Providers (a Data Provider report data)
Data Consumer Scheme 2.0 Yes List of Data Consumers - used for authorisation to resources
Data Structure Definition 2.0 Yes Defines the structure of a Dataset
Dataflow 2.0 Yes Defines a data ‘topic’ for collection or dissemination
Category Scheme 2.0 Yes List of Categories, can be hierarchical, typically used to categorise datasets
Categorisation 2.0 Yes Links a Category to ANY other Identifiable Structure (e.g Category to a Dataflow)
Codelist 1.0 Yes List of Codes (e.g Country Codelist)
Concept Scheme 1.0 Yes List of Concepts (used by Data Structures, Metadata Structures)
Hierarchical Codelist 2.0 Yes Enables construction of one or more Code Hierarchies (view on top of Codelists)
Metadata Structure 2.0 Yes Defines the structure of a Metadata Report
Metadataflow 2.0 No Defines a metadata ‘topic’ for collection or dissemination
Structure Set 2.0 Yes Container for mapping between structures (Codelist Map, Dataflow Map)
Content Constraint 2.0 Yes Defines restrictions on Codelists or Series for Data Reporting
Attachment Constraint 2.0 No
Provision Agreement 2.0 Yes Links a Data Provider to a Dataflow for Data Reporting
Process 2.0 No
Retrieved from "https://wiki.sdmxcloud.org/index.php?title=Maintainable&oldid=1335"