Concepts Schemes and Concepts - Revision history

Vmurrell at 10:57, 22 August 2022

2022-08-22T10:57:13Z

2021-05-05T08:24:06Z

‎Step 3 - Manual Editing

2021-05-05T08:21:53Z

‎Step 2 - Import Concepts

2021-03-09T12:34:15Z

‎Step 3 - Manual Editing

2021-03-09T12:33:28Z

‎Step 2 - Import Concepts

2021-03-09T12:33:06Z

‎Step 1 - High Level Details

2021-03-09T12:31:49Z

‎Step 1 - High Level Details

2021-03-09T12:31:22Z

‎Overview

2021-03-09T12:31:00Z

2021-02-01T16:38:15Z

← Older revision		Revision as of 10:57, 22 August 2022
Line 1:		Line 1:
	[[Category:Structural Metadata]]		[[Category:Structural Metadata]]
		+	[[Category:Structural Metadata V11]]
	=Overview=		=Overview=

@@ Line 34: / Line 34: @@
-[[File:CON4.PNG|800px]]<br>
+[[File:CON4.PNG|Concepts - Step 3|800px]]<br>
 Each Concept can be assigned a default representation.  This representation is inherited by Components of a Data Structure Definition (DSD) as a default.  Default representation can be overridden by each Component of the DSD if required.  To apply a Representation to a Concept, select the Concept in the table, and click the Change Representation button.
-[[File:CON7.PNG|800px]]<br>
+[[File:CON7.PNG|Concepts - Change Representation|800px]]<br>
 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.
@@ Line 46: / Line 46: @@
-[[File:CON5.PNG|300px]]<br>
+[[File:CON5.PNG|Data Type and Restriction|300px]]<br>
 ==Step 4 - Build Hierarchy==
 The final step of the Wizard allows the user to organise the Concepts into a Hierarchy using drag and drop.

← Older revision		Revision as of 08:21, 5 May 2021
Line 19:		Line 19:


−	[[File:CON3.PNG\|800px]]<br>	+	[[File:CON3.PNG\|Import Concepts\|800px]]<br>

	When importing Concepts it is important to note that the following:		When importing Concepts it is important to note that the following:

@@ Line 41: / Line 41: @@
 [[File:CON7.PNG|800px]]<br>
-To link a concept to a codelist, select the concept and click the Change Representation button. All codelists will be displayed (as long as 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.
+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.
 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.

@@ Line 24: / Line 24: @@
 # 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.
 # 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.

@@ Line 12: / Line 12: @@
 From the Items menu, select the Concepts Scheme Page and use the maintenance button to create a Concept Scheme. [[File :cogs.PNG|40px]]<br>
-The steps in a Concept Scheme Wizard includes step 1 which provides the generic, high level details about the Concepty Scheme.uthoring and maintaining structures. See this article [https://fmrwiki.sdmxcloud.org/All_Structures for more information on authoring and maintaining structures.]
+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.]
 ==Step 2 - Import Concepts==

@@ Line 4: / Line 4: @@
 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.
-See this article [https://fmrwiki.sdmxcloud.org/All_Structures_-_FMR for more information on authoring and maintaining structures.]
+See this article [https://fmrwiki.sdmxcloud.org/All_Structures for more information on authoring and maintaining structures.]
 =Wizard=

← Older revision		Revision as of 12:31, 9 March 2021
Line 1:		Line 1:
	[[Category:Structural Metadata]]		[[Category:Structural Metadata]]
−
	=Overview=		=Overview=

← Older revision		Revision as of 16:38, 1 February 2021
Line 1:		Line 1:
−	[[Category:~~Editing and Maintaining Structures using the UI~~]]	+	[[Category:Structural Metadata]]

	=Overview=		=Overview=