Edi Lenient Mode - Revision history

Vmurrell at 14:06, 5 September 2022

2022-09-05T14:06:21Z

Vmurrell at 14:29, 8 March 2021

2021-03-08T14:29:53Z

Plazarou at 14:03, 30 July 2020

2020-07-30T14:03:04Z

Plazarou at 09:29, 22 April 2020

2020-04-22T09:29:14Z

Plazarou at 09:53, 17 April 2020

2020-04-17T09:53:37Z

Plazarou: Created page with "Fusion Registry may be run in "EDI Lenient" mode. When running in this mode certain aspects of EDI which are enforced by the EDI standard are ignored. == Structures == EDI d..."

2020-04-17T09:52:35Z

Created page with "Fusion Registry may be run in "EDI Lenient" mode. When running in this mode certain aspects of EDI which are enforced by the EDI standard are ignored. == Structures == EDI d..."

New page

Fusion Registry may be run in "EDI Lenient" mode. When running in this mode certain aspects of EDI which are enforced by the EDI standard are ignored.

== Structures ==
EDI does not permit a structure to reference another structure belonging to a different Agency. When running in EDI Leniency mode, this restriction is disabled and the structures will all be stated as belonging to the same agency. For example, a Data Structure Definition in Agency 1 if it refers to a Codelist in Agency 2 cannot strictly be converted into EDI since EDI cannot express that the DSD and Codelist are in different agencies. In EDI Leniency mode, the outputted EDI file would state that both are owned by Agency1.
The EDI standard does not support uncoded dimensions in a Data Structure. All dimensions must be explicitly coded. When running in EDI Leniency mode, Data Structures with uncoded dimensions may be read or written without an exception being thrown.

== Data ==
EDI enforces the following limits on a data file:
* The Observation Value is limited to a maximum of 15 characters
* The Observation Attribute “OBS_STATUS” is limited to a maximum of 35 characters
* The Observation Attribute “OBS_CONF” is limited to a maximum of 35 characters
* The Observation Attribute “OBS_PRE_BREAK” is limited to a maximum of 15 characters
When running in EDI Leniency mode, none of the above restrictions apply when reading or writing a data file.

== Enabling EDI Leniency Mode ==
To run the Registry in EDI Lenience Mode, the Registry must be started and a Java System variable called "edi.lenient.enabled" must be specified and set to "true". This is supplied via the -D parameter thus: <code> -Dedi.lenient.enabled=true </code>

When using Apache Tomcat, the simplest way to perform this is by modifying the setenv.bat or setenv.sh file. To illustrate this:

<code>
SET JAVA_OPTS=-Djson.legacy.enabled=true
</code>
''(For Windows systems)''

<code>
export JAVA_OPTS=-Djson.legacy.enabled=true
</code>
''(For Unix systems)''

← Older revision		Revision as of 14:06, 5 September 2022
Line 1:		Line 1:
	[[Category:How_To]]		[[Category:How_To]]
		+	[[Category:How_To V11]]
	Fusion Metadata Registry may be run in "EDI Lenient" mode. When running in this mode certain aspects of EDI which are enforced by the EDI standard are ignored.		Fusion Metadata Registry may be run in "EDI Lenient" mode. When running in this mode certain aspects of EDI which are enforced by the EDI standard are ignored.

@@ Line 1: / Line 1: @@
 [[Category:How_To]]
-Fusion Registry may be run in "EDI Lenient" mode.  When running in this mode certain aspects of EDI which are enforced by the EDI standard are ignored.
+Fusion Metadata Registry may be run in "EDI Lenient" mode.  When running in this mode certain aspects of EDI which are enforced by the EDI standard are ignored.
 == Structures ==

← Older revision		Revision as of 09:53, 17 April 2020
Line 1:		Line 1:
		+	[[Category:How_To]]
	Fusion Registry may be run in "EDI Lenient" mode. When running in this mode certain aspects of EDI which are enforced by the EDI standard are ignored.		Fusion Registry may be run in "EDI Lenient" mode. When running in this mode certain aspects of EDI which are enforced by the EDI standard are ignored.

@@ Line 4: / Line 4: @@
 == Structures ==
 EDI does not permit a structure to reference another structure belonging to a different Agency. When running in EDI Leniency mode, this restriction is disabled and the structures will all be stated as belonging to the same agency.  For example, a Data Structure Definition in Agency 1 if it refers to a Codelist in Agency 2 cannot strictly be converted into EDI since EDI cannot express that the DSD and Codelist are in different agencies.  In EDI Leniency mode, the outputted EDI file would state that both are owned by Agency1.
 The EDI standard does not support uncoded dimensions in a Data Structure.  All dimensions must be explicitly coded.  When running in EDI Leniency mode, Data Structures with uncoded dimensions may be read or written without an exception being thrown.

@@ Line 20: / Line 20: @@
 <code>
-SET JAVA_OPTS=-Djson.legacy.enabled=true
+SET JAVA_OPTS=-Dedi.lenient.enabled=true
 </code>
 ''(For Windows systems)''
 <code>
-export JAVA_OPTS=-Djson.legacy.enabled=true
+export JAVA_OPTS=-Dedi.lenient.enabled=true
 </code>
 ''(For Unix systems)''