Time Period Format Validation - Revision history

Vmurrell at 15:40, 17 April 2024

2024-04-17T15:40:23Z

2024-03-23T12:19:25Z

2023-07-06T08:59:11Z

‎Using 'H' for half-year (semiannual)

2023-07-06T08:54:51Z

2022-07-29T09:33:04Z

2022-07-29T09:20:13Z

2022-07-29T09:14:28Z

2022-07-29T09:13:59Z

2022-07-29T09:13:21Z

2022-07-29T09:07:50Z

‎Using 'H' for half-year (semiannual)

← Older revision		Revision as of 15:40, 17 April 2024
Line 1:		Line 1:
−	[[Category:~~Draft_-_Installation_and_Configuration~~]]	+	[[Category:Installation_and_Configuration]]

	[[Category:FMR_Configuration_Reference]]		[[Category:FMR_Configuration_Reference]]

← Older revision		Revision as of 12:19, 23 March 2024
Line 1:		Line 1:
		+	[[Category:Draft_-_Installation_and_Configuration]]
		+
	[[Category:FMR_Configuration_Reference]]		[[Category:FMR_Configuration_Reference]]
	The Registry will validate observation time periods for consistency with the series frequency value in the FREQ dimension.		The Registry will validate observation time periods for consistency with the series frequency value in the FREQ dimension.

← Older revision		Revision as of 08:59, 6 July 2023
Line 54:		Line 54:

	Active system properties can also be queried using the REST API [[System_Properties\|here]].		Active system properties can also be queried using the REST API [[System_Properties\|here]].
		+
		+	== Is Alternate Half-Format set ==
		+
		+	On startup the Fusion Registry system log will report the following message:
		+
		+	2021-12-31 23:59:59.123 INFO main io.sdmx.core.fmr.application.FusionRegistryApplicationInitialiser - Using 'Alternate Half-Year' Setting
		+
		+	Active system properties can also be queried using the REST API which is detailed [[System_Properties\|here]].

← Older revision		Revision as of 08:54, 6 July 2023
Line 1:		Line 1:
		+	[[Category:FMR_Configuration_Reference]]
	The Registry will validate observation time periods for consistency with the series frequency value in the FREQ dimension.		The Registry will validate observation time periods for consistency with the series frequency value in the FREQ dimension.

@@ Line 34: / Line 34: @@
 * Frequency value H means half-year (semiannual or semester)
 * The hourly frequency is not supported
-* 'YYYY-S1' and 'YYYY-H1' are valid TIME_PERIOD formats for half-yearly observations
+* 'YYYY-S1' and 'YYYY-H1' are valid TIME_PERIOD formats for half-yearly observations, however time periods are standardised to ‘YYYY-S1’ on conversion (e.g. such as when converting data in Excel to SDMX 2.1 structure specific)
 Alternate half year mode is controlled at system level on Registry start-up by setting the Java System variable “'''TF_ALTERNATE_HALF_YEAR'''” to “'''true'''”.

@@ Line 3: / Line 3: @@
 This check is not performed if the DSD has no FREQ dimension.
-Default frequencies and valid time period formats are set out in the following table:
+Default frequencies and their corresponding valid time period formats are set out in the following table:
 {| class="wikitable"
 |-

@@ Line 1: / Line 1: @@
-The Registry will validate observation dates against an expected format. This Data Validator is called “Time Period Format” and enforces that format of the reported time periods match the expected value defined in the DSD. '''Note:''' This Data Validator is only applied if the Data Structure has a dimension called “FREQ”. This time formats are defined as follows:
+The Registry will validate observation time periods for consistency with the series frequency value in the FREQ dimension.
 {| class="wikitable"
 |-

@@ Line 34: / Line 34: @@
 Alternate half year mode is controlled at system level on Registry start-up by setting the Java System variable “'''TF_ALTERNATE_HALF_YEAR'''” to “'''true'''”.
-The simplest way to perform this is by modifying the setenv.bat or setenv.sh file. To illustrate this:
+If using Apache Tomcat, JAVA_OPTS can be set in the setenv.bat or setenv.sh file:
    SET JAVA_OPTS=-DTF_ALTERNATE_HALF_YEAR=true
@@ Line 41: / Line 41: @@
    export JAVA_OPTS=-DTF_ALTERNATE_HALF_YEAR=true
    (For Unix systems)
 The Fusion Registry system log will report the following message: