Time Format Alternate Half Year - Revision history

Vmurrell at 16:49, 30 October 2025

2025-10-30T16:49:34Z

Vmurrell at 07:35, 11 September 2023

2023-09-11T07:35:17Z

Plazarou at 08:46, 13 July 2023

2023-07-13T08:46:13Z

Plazarou at 08:04, 12 July 2023

2023-07-12T08:04:11Z

Plazarou: /* Is Alternate Half-Format set */

2023-07-11T11:27:04Z

‎Is Alternate Half-Format set

Plazarou: /* Setting System Property */

2023-06-30T14:23:58Z

‎Setting System Property

Plazarou: /* Is Alternate Half-Format set */

2023-06-30T14:23:17Z

‎Is Alternate Half-Format set

Plazarou at 14:23, 30 June 2023

2023-06-30T14:23:01Z

Plazarou: Created page with "At ESCB level SDMX data exchanges, there is an agreement to use 'H' as the frequency value for semiannual observations. This is specified via 'YYYY-H1' or 'YYYY-H2'. The Regi..."

2023-06-30T14:21:26Z

Created page with "At ESCB level SDMX data exchanges, there is an agreement to use 'H' as the frequency value for semiannual observations. This is specified via 'YYYY-H1' or 'YYYY-H2'. The Regi..."

New page

At ESCB level SDMX data exchanges, there is an agreement to use 'H' as the frequency value for semiannual observations. This is specified via 'YYYY-H1' or 'YYYY-H2'.

The Registry supports this by setting a system property so the Registry is in 'alternate half year' mode. Under this mode:
* 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, however conversion will output in ‘YYYY-H1’ format

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".

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
(For Windows systems)

export JAVA_OPTS=-DTF_ALTERNATE_HALF_YEAR=true
(For Unix systems)

Different procedures may be required for other web application servers like JBoss.

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 here.

← Older revision		Revision as of 16:49, 30 October 2025
Line 1:		Line 1:
−	[[Category:Fusion Registry ~~Install~~]]	+	[[Category:Fusion Registry Configuration]]
−	~~[[Category:How_To]]~~
−
	At ESCB level SDMX data exchanges, there is an agreement to use 'H' as the frequency value for semi-annual observations. This is specified via 'YYYY-H1' or 'YYYY-H2'.		At ESCB level SDMX data exchanges, there is an agreement to use 'H' as the frequency value for semi-annual observations. This is specified via 'YYYY-H1' or 'YYYY-H2'.

← Older revision		Revision as of 07:35, 11 September 2023
Line 1:		Line 1:
		+	[[Category:Fusion Registry Install]]
		+	[[Category:How_To]]
		+
	At ESCB level SDMX data exchanges, there is an agreement to use 'H' as the frequency value for semi-annual observations. This is specified via 'YYYY-H1' or 'YYYY-H2'.		At ESCB level SDMX data exchanges, there is an agreement to use 'H' as the frequency value for semi-annual observations. This is specified via 'YYYY-H1' or 'YYYY-H2'.

@@ Line 4: / Line 4: @@
 * Frequency value 'H' means half-year (semiannual or semester) as does frequency value 'S'. They are interchangeable as input.
 * 'YYYY-S1' and 'YYYY-H1' are valid TIME_PERIOD formats for half-yearly observations.
-* Output will always be in the 'S' format (e.g. an input of 'YYYY-H1' will be converted to 'YYYY-S1'). This ensures that the output is correct to the SDMX specification.
+* Output in SDMX-ML 2.1 will always be in the 'S' format (e.g. an input of 'YYYY-H1' will be converted to 'YYYY-S1'). This ensures that the output is correct to the SDMX specification.
 * The hourly frequency is not supported.

@@ Line 1: / Line 1: @@
-At ESCB level SDMX data exchanges, there is an agreement to use 'H' as the frequency value for semiannual observations. This is specified via 'YYYY-H1' or 'YYYY-H2'.
+At ESCB level SDMX data exchanges, there is an agreement to use 'H' as the frequency value for semi-annual observations. This is specified via 'YYYY-H1' or 'YYYY-H2'.
-The Registry supports this by setting a system property so the Registry is in 'alternate half year' mode.  Under this mode:
+The Registry supports this with a system property. When this is enabled the Registry is in 'alternate half year' mode.  Under this mode:
-* Frequency value 'H' means half-year (semiannual or semester)
+* Frequency value 'H' means half-year (semiannual or semester) as does frequency value 'S'. They are interchangeable as input.
-* 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 conversion will output in ‘YYYY-H1’ format
+* Output will always be in the 'S' format (e.g. an input of 'YYYY-H1' will be converted to 'YYYY-S1'). This ensures that the output is correct to the SDMX specification.
-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".
+'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".
 == Setting System Property ==

@@ Line 20: / Line 20: @@
 Different procedures may be required for other web application servers like JBoss.
-== Is Alternate Half-Format set ==
+== Is Alternate Half-Year Format set? ==
 On startup the Fusion Registry system log will report the following message:

@@ Line 10: / Line 10: @@
 == Setting System Property ==
-If using Apache Tomcat, it is recommended to set the value via JAVA_OPTS and using the setenv.bat or setenv.sh file:
+If using Apache Tomcat, it is recommended to set the value via JAVA_OPTS and using the ''setenv.bat'' or ''setenv.sh'' file:
   SET JAVA_OPTS=-DTF_ALTERNATE_HALF_YEAR=true

← Older revision		Revision as of 14:23, 30 June 2023
Line 26:		Line 26:
	2021-12-31 23:59:59.123 INFO main io.sdmx.core.fmr.application.FusionRegistryApplicationInitialiser - Using 'Alternate Half-Year' Setting		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 [here~~\|System_Properties~~].	+	Active system properties can also be queried using the REST API which is detailed [[System_Properties\|here]].