re3data domains (contentType)

[bansp]

For our information, this is the r3data schema v. 4.0: http://schema.re3data.org/4-0/re3dataV4-0.xsd

Their domains do not fit our purposes pretty well, but we should have a clear policy on that: do we map? Do we take the non-linguistic types over and map the linguistic ones? If so, then do we keep the metacategories or create new divisions? Etc.

<xs:simpleType name="contentTypeNames">
<xs:restriction base="xs:string">
<xs:enumeration value="dataset"/>
<xs:enumeration value="aggregated data"/>
<xs:enumeration value="clinical trial data"/>
<xs:enumeration value="compiled data"/>
<xs:enumeration value="encoded data"/>
<xs:enumeration value="experimental data"/>
<xs:enumeration value="genomic data"/>
<xs:enumeration value="geospatial data"/>
<xs:enumeration value="laboratory notebook"/>
<xs:enumeration value="measurement and test data"/>
<xs:enumeration value="observational data"/>
<xs:enumeration value="recorded data"/>
<xs:enumeration value="simulation data"/>
<xs:enumeration value="survey data"/>
<xs:enumeration value="image"/>
<xs:enumeration value="moving image"/>
<xs:enumeration value="still image"/>
<xs:enumeration value="software"/>
<xs:enumeration value="research software"/>
<xs:enumeration value="source code"/>
<xs:enumeration value="text"/>
<xs:enumeration value="other"/>
</xs:restriction>
</xs:simpleType>

[bansp]

Two examples in action:

• https://www.re3data.org/repository/r3d100010382
• https://www.re3data.org/repository/r3d100010152