Concept Schemes and Concepts - Revision history

Vmurrell: Vmurrell moved page Concept Schemes - Structural Metadata Management to Concept Schemes and Concepts

2023-09-13T16:30:06Z

Vmurrell moved page Concept Schemes - Structural Metadata Management to Concept Schemes and Concepts

Vmurrell at 16:26, 13 September 2023

2023-09-13T16:26:14Z

Vmurrell at 14:51, 12 September 2023

2023-09-12T14:51:59Z

Vmurrell at 10:29, 8 August 2023

2023-08-08T10:29:45Z

Mbaird at 11:11, 15 November 2019

2019-11-15T11:11:45Z

Mbaird at 11:10, 15 November 2019

2019-11-15T11:10:16Z

Mbaird at 10:55, 15 November 2019

2019-11-15T10:55:09Z

Mbaird: Created page with "== Overview == Concept Schemes are a container for '''Concepts'''. Concepts are used by '''Dimensions''', '''Attributes''', '''Measures''', and '''Metadata Attributes''' to p..."

2019-11-15T10:46:42Z

Created page with "== Overview == Concept Schemes are a container for '''Concepts'''. Concepts are used by '''Dimensions''', '''Attributes''', '''Measures''', and '''Metadata Attributes''' to p..."

New page

== Overview ==
Concept Schemes are a container for '''Concepts'''. Concepts are used by '''Dimensions''', '''Attributes''', '''Measures''', and '''Metadata Attributes''' to provide them with a semantic meaning. Concepts can also be used to define a default representation, for example it is possible to link the Concept of Frequency to a Codelist containing all the Frequency Codes, any structure using the Concept will inherit the default representation.

@@ Line 1: / Line 1: @@
 __NOTOC__
 [[Category:Structural Metadata]]
-== Overview ==
+=Overview=
-::[[File:CS_Pic_1.jpg|frameless|300px]]
+Concept Schemes are a container for Concepts.  Concepts are used by Dimensions, Attributes, Measures, and Metadata Attributes to provide them with a semantic meaning. Concepts can also be used to define a default representation, for example it is possible to link the Concept of Frequency to a Codelist containing all the Frequency Codes, any structure using the Concept will inherit the default representation.
-::[[File:Concept Schemes Fig 1.jpg|frameless|750px]]
+=Wizard=
-::<small>''Figure 1 showing Concepts in a Concept Scheme'</small>
+==Step 1 - High Level Details==
-The above shows the Concepts in a Concept Scheme, the image below shows how Concepts are used to give various Components of a Data Structure a name.  Concepts can be used by any number of structures, and a structure (such as a DSD) can reference Concepts from any number of Concept Schemes.
+The steps in a Concept Scheme Wizard includes step 1 which provides the generic, high level details about the Concepty Scheme. See this article [https://fmrwiki.sdmxcloud.org/All_Structures for more information on authoring and maintaining structures.]
-::[[File:Concept Schemes Fig 2.jpg|frameless|300px]]
+==Step 2 - Import Concepts==
-::<small>''Figure 2 showing the Concepts used by a Data Structure Definition providing the names and descriptions for each Dimension and Attribute of the Data Structure''</small>
+The second step allows the user to import Concepts from CSV.  CSV text can be copied and pasted into the text field provided.  On clicking '''Next''' Concepts will be created based on this CSV and added to the Concept Scheme.
-== Concept Scheme Wizard ==
+[[File:CON3.PNG|Import Concepts|800px]]<br>
 When importing Concepts it is important to note that the following:
-#Concepts will be added to the Concept Scheme, and therefore this step can be used to add additional Concepts to an existing scheme.
+# Concepts will be added to the Concept Scheme, and therefore this step can be used to add additional Concepts to an existing scheme.
-#The import language for the name and description fields is defined in the drop down list above the text area.
+# The import language for the name and description fields is defined in the drop-down list above the text area.
-#If a Concept already exists it will be modified based on the information supplied in the CSV. Modifications include addition of a name or description in a new language into an existing Concept.
+# If a Concept already exists it will be modified based on the information supplied in the CSV. Modifications include addition of a name or description in a new language into an existing Concept.
-#Sub Concepts can be created by using parent Concept Id field.  This is shown in the image above where SUB_CONCEPT is a sub-concept of REF_AREA.
+# Sub Concepts can be created by using parent Concept Id field.  This is shown in the image above where SUB_CONCEPT is a sub-concept of REF_AREA.
-#The same number of delimiters are required for each line, even if there is no information for the field, shown above where Frequency includes an additional comma followed by no text (there is no Parent Concept Id).
+# The same number of delimiters are required for each line, even if there is no information for the field, shown above where Frequency includes an additional comma followed by no text (there is no Parent Concept Id).
-#If a field contains the delimiter (for example if a name includes a comma) then the text can be put in double quotes.
+# If a field contains the delimiter (for example if a name includes a comma) then the text can be put in double quotes.
 The third step is to manually add, edit, and delete Concepts.
-::[[File:Concept Schemes Fig 4.jpg|frameless|500px]]
+[[File:CON4.PNG|Concepts - Step 3|800px]]<br>
-Representation can be non-enumerated or enumerated.  Non-enumerated formats refer to data formats which are restricted by data type as oppose to enumerated representation which provide a list of allowed values.  Non-enumerated format includes types such as String, Integer, and Decimal, amongst others.  Each non-enumerated format can optionally provide additional details relevant to the selected format, such as min/max length for String. Enumerated formats allow a Concept to be linked to a Codelist.  The Codelist is used to define the enumerated list of all the allowable values for the Concept.
+[[File:CON7.PNG|Concepts - Change Representation|800px]]<br>
-::[[File:Concept Schemes Fig 5.jpg|frameless|400px]]
+To link a concept to a codelist, select the concept and click the Change Representation button. All codelists will be displayed (if you have clicked the Enumerated button). Simply highlight the required codelist and then Save. Enumerated formats allow a Concept to be linked to a Codelist.  The Codelist is used to define the enumerated list of all the allowable values for the Concept.
-::<small>''Figure 5 showing an example non-enumerated representation form''</small>
+Representation formats can also be non-enumerated or enumerated.  Non-enumerated formats refer to data formats which are restricted by data type as oppose to enumerated representation which provide a list of allowed values.  Non-enumerated format includes types such as String, Integer, and Decimal, amongst others.  Each non-enumerated format can optionally provide additional details relevant to the selected format, such as min/max length for String.
-::''<small>Figure 6 showing the list of Codelists that could be assigned to a Concept</small>''
+[[File:CON5.PNG|Data Type and Restriction|300px]]<br>
 The final step of the Wizard allows the user to organise the Concepts into a Hierarchy using drag and drop.

@@ Line 1: / Line 1: @@
 __NOTOC__
 [[Category:Structural Metadata]]
 == Overview ==
 Concept Schemes are a container for '''Concepts'''.  Concepts are used by '''Dimensions''', '''Attributes''', '''Measures''', and '''Metadata Attributes''' to provide them with a semantic meaning. Concepts can also be used to define a default representation, for example it is possible to link the Concept of Frequency to a Codelist containing all the Frequency Codes, any structure using the Concept will inherit the default representation.

@@ Line 1: / Line 1: @@
 __NOTOC__
 [[Category:Structural Metadata]]
 == Overview ==
 Concept Schemes are a container for '''Concepts'''.  Concepts are used by '''Dimensions''', '''Attributes''', '''Measures''', and '''Metadata Attributes''' to provide them with a semantic meaning. Concepts can also be used to define a default representation, for example it is possible to link the Concept of Frequency to a Codelist containing all the Frequency Codes, any structure using the Concept will inherit the default representation.

@@ Line 1: / Line 1: @@
 __NOTOC__
 [[Category:Structural Metadata]]
 == Overview ==
 Concept Schemes are a container for '''Concepts'''.  Concepts are used by '''Dimensions''', '''Attributes''', '''Measures''', and '''Metadata Attributes''' to provide them with a semantic meaning. Concepts can also be used to define a default representation, for example it is possible to link the Concept of Frequency to a Codelist containing all the Frequency Codes, any structure using the Concept will inherit the default representation.

@@ Line 1: / Line 1: @@
 == Overview ==
 Concept Schemes are a container for '''Concepts'''.  Concepts are used by '''Dimensions''', '''Attributes''', '''Measures''', and '''Metadata Attributes''' to provide them with a semantic meaning. Concepts can also be used to define a default representation, for example it is possible to link the Concept of Frequency to a Codelist containing all the Frequency Codes, any structure using the Concept will inherit the default representation.
@@ Line 15: / Line 18: @@
 ::<small>''Figure 2 showing the Concepts used by a Data Structure Definition providing the names and descriptions for each Dimension and Attribute of the Data Structure''</small>

← Older revision	Revision as of 16:30, 13 September 2023
(No difference)

← Older revision		Revision as of 10:55, 15 November 2019
Line 1:		Line 1:
	== Overview ==		== Overview ==
	Concept Schemes are a container for '''Concepts'''. Concepts are used by '''Dimensions''', '''Attributes''', '''Measures''', and '''Metadata Attributes''' to provide them with a semantic meaning. Concepts can also be used to define a default representation, for example it is possible to link the Concept of Frequency to a Codelist containing all the Frequency Codes, any structure using the Concept will inherit the default representation.		Concept Schemes are a container for '''Concepts'''. Concepts are used by '''Dimensions''', '''Attributes''', '''Measures''', and '''Metadata Attributes''' to provide them with a semantic meaning. Concepts can also be used to define a default representation, for example it is possible to link the Concept of Frequency to a Codelist containing all the Frequency Codes, any structure using the Concept will inherit the default representation.
		+
		+	::[[File:CS_Pic_1.jpg\|frameless\|300px]]
		+
		+
		+	::[[File:Concept Schemes Fig 1.jpg\|frameless\|750px]]
		+
		+	::<small>''Figure 1 showing Concepts in a Concept Scheme'</small>
		+
		+
		+	The above shows the Concepts in a Concept Scheme, the image below shows how Concepts are used to give various Components of a Data Structure a name. Concepts can be used by any number of structures, and a structure (such as a DSD) can reference Concepts from any number of Concept Schemes.
		+
		+	::[[File:Concept Schemes Fig 2.jpg\|frameless\|300px]]
		+
		+	::<small>''Figure 2 showing the Concepts used by a Data Structure Definition providing the names and descriptions for each Dimension and Attribute of the Data Structure''</small>