Item Validity - Revision history

Vmurrell: /* Codelist Wizard – Stating the Codelist Type */

2024-04-01T15:14:00Z

‎Codelist Wizard – Stating the Codelist Type

2021-05-05T09:33:36Z

‎Codelist

2021-05-05T09:32:41Z

‎Codelist Map Wizard

2021-05-05T09:31:31Z

‎Hierarchical Codelist Wizard

2021-05-05T09:30:47Z

‎Codelist Wizard – Assigning a Validity Period to an Item

2021-05-05T09:29:11Z

‎Codelist Wizard – Assigning a Validity Period to an Item

2021-05-05T09:28:16Z

‎Codelist Wizard – Stating the Codelist Type

2021-05-05T09:27:31Z

‎Reassigning a Code

2021-05-05T09:26:45Z

‎Overview

2021-05-05T09:25:41Z

‎Overview

@@ Line 38: / Line 38: @@
 ==Assigning Item Validity==
-===Codelist Wizard – Stating the Codelist Type===
+===Codelist Wizard – Specifying the Codelist Type===
 The Codelist Wizard in Fusion Registry allows the user to create and edit Codelists.  In Step 1 of the wizard aside from the standard elements that make up a structure, the Codelist wizard adds a further choice control which allows a Codelist to be defined in one of three forms:

@@ Line 107: / Line 107: @@
-[[File:IV13.PNG|800px]]<br>
+[[File:IV13.PNG|Codelist|800px]]<br>
 When the user clicks “View Codelist”, if the Codelist does not have codes with validity at the item level, then the modal dialog shows a table of codes with the columns: Position, Id, Name and Description.  If the Codelist has codes with validity at the item level then the Description column is not shown in the table and the Validity Period is shown instead.
-[[File:IV14.PNG|800px]]<br>
+[[File:IV14.PNG|View Codelist|800px]]<br>
 Note that there may be duplicate rows for the same ID and that for these rows, the position is the same.  Any rows which are considered invalid for today will be rendered in grey text.

@@ Line 90: / Line 90: @@
-[[File:IV11.PNG|800px]]<br>
+[[File:IV11.PNG|Adding a Validity Period to a Codelist Map|800px]]<br>
-If a mapping has a validity period, it is shown with a calendar icon to state that this mapping is date dependant.  To assign, remove or edit a Validity Period for a mapping, activate the button labelled “Modify Validity Period” and the following modal is displayed:
+If a mapping has a validity period, it is shown with a calendar icon to state that this mapping is date dependent.  To assign, remove or edit a Validity Period for a mapping, activate the button labelled “Modify Validity Period” and the following modal is displayed:
-[[File:IV12.PNG|500px]]<br>
+[[File:IV12.PNG|Modify Validity Period|500px]]<br>
 The input for each is an SDMX datetime. Clearing the values and clicking “Set Validity Period” will remove the mapping.

← Older revision		Revision as of 09:31, 5 May 2021
Line 79:		Line 79:


−	[[File:IV10.PNG\|800px]]<br>	+	[[File:IV10.PNG\|Add Validity Period\|800px]]<br>

	It is permissible to add multiple Validity Periods to a particular item if desired.		It is permissible to add multiple Validity Periods to a particular item if desired.

@@ Line 54: / Line 54: @@
-[[File:IV7.PNG|800px]]<br>
+[[File:IV7.PNG|Assigning a Validity Period to an Item|800px]]<br>
 The third step of the wizard allows the user to manually add, edit, and delete Codes in the Codelist.  For editing and deleting codes, if the Codelist is of type “Item Validity” then the edit window will have entries for “Valid From” and “Valid To”.  If it is a “standard” Codelist these fields will not be present.
-[[File:IV8.PNG|Assigning a Validity Period to an Item|400px]]<br>
+[[File:IV8.PNG|Manual Edit|400px]]<br>
 Simply editing the “Valid From” and “Valid To” fields is enough to specify Item Validity to the currently edited item.  The input takes SDMX Datetimes, so such values as 2001-Q1 and 2002-W50 are also permitted.
@@ Line 68: / Line 68: @@
-[[File:IV9.PNG|Manual Edit|800px]]<br>
+[[File:IV9.PNG|Add Validity Period|800px]]<br>
 ===Concept Scheme Wizard===

← Older revision		Revision as of 09:28, 5 May 2021
Line 49:		Line 49:


−	[[File:IV6.PNG\|800px]]<br>	+	[[File:IV6.PNG\|800px\|Codelist type]]<br>

	===Codelist Wizard – Assigning a Validity Period to an Item===		===Codelist Wizard – Assigning a Validity Period to an Item===

@@ Line 25: / Line 25: @@
-[[File:IV4.PNG|500px]]<br>
+[[File:IV4.PNG|Diagram 4|500px]]<br>
 With the dissolution of the Gilbert and Ellice Islands, the code “GE” is re-assigned to Georgia and Georgia’s existing code (“XX”) is discontinued.
@@ Line 31: / Line 31: @@
 With the use of Item Validity, a single Codelist can discontinue the use of the code “GE” to mean the Gilbert and Ellice Islands and re-assign it to Georgia. The use of Valid From and Valid To dates means that codes can be terminated and re-assigned as desired.
-[[File:IV5.PNG|500px]]<br>
+[[File:IV5.PNG|Diagram 5|500px]]<br>

@@ Line 7: / Line 7: @@
-[[File:IV1.PNG|Example|500px]]<br>
+[[File:IV1.PNG|Diagram 1|500px]]<br>
 The Currency Codelist (version 1.0) contains the codes for all currencies. With the introduction of the Euro and the discontinuation of existing currencies (DEM and FRF), a new Codelist must be created (version 2.0) which contains only the codes that are to be used. Each version of the Codelist should have a date that states when it should be used. For Codelist version 1.0, this is up to Jan 1, 1999 and for Codelist version 2.0 this is from Jan 1, 1999. Any codes that don’t change are reflected in both Codelists.
@@ Line 14: / Line 14: @@
-[[File:IV2.PNG|500px]]<br>
+[[File:IV2.PNG|Diagram 2|500px]]<br>
 For the new Euro code, this can be added to the Codelist with a date specifying when this code is Valid From. So now the Codelist will have different codes for different periods of time.
-[[File:IV3.PNG|500px]]<br>
+[[File:IV3.PNG|Diagram 3|500px]]<br>
 ==Reassigning a Code==