EGA.policy.xsd

[ega-agent]

Update to the Policy schema to include the mandatory use of at least one (1) Data Use Ontology (DUO) codes. This update is intended to ensure and allow submitters to use the most appropriate DUO code for their research.

[raskoleinonen]

This is a backward incompatible change. If any existing XMLs would not validate against the new XML schema then please provide instructions how these existing XMLs should be changed to make them valid against the updated XML Schema.

[ega-agent]

@raskoleinonen thanks for the comment. Our plan going forward is that for Policies currently registered and that do not contain DUOs we will contact the DACs to request that they provide us with the codes that best reflect the Data Use the Policy and the original consent forms cover. We are also working on a mechanism to apply a default DUO in the event that DACs fail to provide a code. Going forward we would like to ensure that all policies are DUO tagged by the submitter as part of the submission process. The timeline for this is still being discussed.

I will be happy to look into any further comments or suggestions that you may have.

[raskoleinonen]

The schema currently supports 0 or more DATA_USE elements:

<xs:element name="DATA_USES" minOccurs="0" maxOccurs="1">
xs:complexType
<xs:sequence minOccurs="1" maxOccurs="unbounded">
<xs:element name="DATA_USE" type="DataUseType"/>
</xs:sequence>
</xs:complexType>
</xs:element>

Based on you requirements I suggest:

1. You would announce a date X after which submitters must provide at least one DATA_USE.
2. We do not make any schema changes BUT deploy a business level check on date X that at least one DATA_USE must be provided. This check would be done in the Webin submission service.
3. If no DATA_USE has been provided then the business level check could inject a default one.
4. Once all existing policies have been changed to have at least one DATA_USE we would change the schema to:

<xs:element name="DATA_USES" minOccurs="1" maxOccurs="1">
xs:complexType
<xs:sequence minOccurs="1" maxOccurs="unbounded">
<xs:element name="DATA_USE" type="DataUseType"/>
</xs:sequence>
</xs:complexType>
</xs:element>

that would make it an XML schema level requirement to provide at least one DATA_USE.

Note that if any interactive Webin changes are required then I would suggest that you would work with us to move EGA policy/dac/dataset interface functionality to Webin Portal that is a more modern Angular app.