Frequently Asked Questions - Conversion to CMDI

If you have old records in the

ISLE Meta Data Initiative

See: http://en.wikipedia.org/wiki/IMDI

format you can use the following profiles:

• for sessions: https://catalog.clarin.eu/ds/ComponentRegistry#/?itemId=clarin.eu%3Acr1…
• for sign language sessions: https://catalog.clarin.eu/ds/ComponentRegistry#/?itemId=clarin.eu%3Acr1…
• for corpus nodes: https://catalog.clarin.eu/ds/ComponentRegistry#/?itemId=clarin.eu%3Acr1…

From the profile you can generate the XSD:

• for sessions: https://catalog.clarin.eu/ds/ComponentRegistry/rest/registry/1.x/profil…
• for sign language sessions: https://catalog.clarin.eu/ds/ComponentRegistry/rest/registry/1.x/profil…
• for corpus nodes: https://catalog.clarin.eu/ds/ComponentRegistry/rest/registry/1.x/profil…

And then you can transform your IMDI files into

Component Metadata Infrastructure

See: http://www.clarin.eu/cmdi

files that comply with the profile with the following set of XSLTs:

https://github.com/TheLanguageArchive/MetadataTranslator/tree/master/Tr…
 

EDM metadata can be converted to

Component Metadata Infrastructure

See: http://www.clarin.eu/cmdi

by means of a dedicated CMDI profile and an XSLT stylesheet (+documentation).

There are 2 CMDI profiles and an XSLT stylesheet available that can achieve this. (access requires an SVN account)

Use the MODS profile and the XSLT stylesheet provided by the University Library of Utrecht

If you have records in the Meta-Share maximal format you can use the profiles and conversion stylesheets as described at the Meta site.

If you have records in the Meta-Share minimal format you can use this profile (and the generated XSD).

Then you can use an XSLT transformation to transform your Meta-Share records into the

Component Metadata Infrastructure

See: http://www.clarin.eu/cmdi

equivalent. For the maximal Meta-Share schema, guidelines and XSLT files are provided here. For the minimal MS-schema to

Open Language Archives Community

See: http://www.language-archives.org

, the XSLT is provided here.

Related to this Jozef Misutka from UFAL has been so kind to implement an OAI-PMH module for the Meta-Share repository.

See also: CMDI interoperability workshop

There is no general procedure to do this, as

Text Encoding Initiative

See: http://en.wikipedia.org/wiki/Text_Encoding_Initiative

has many variants and extensions. However, you could follow the following general workflow:

• Inspect your TEI headers and decide what the relevant parts are. Some information (e.g. layout tags etc.) might be lost during the conversion.
• Compare your needs with one of the existing TEI profiles (teiHeader type 1, teiHeader type 2, teiHeader type 3) in the
  Component Metadata Infrastructure
  See: http://www.clarin.eu/cmdi
  component registry. If it fulfills your needs, go to the next steps. If it does not, use the TEI profile as a basis to create your own CMDI profile.
• Create an XSLT that generates CMDI instances (according to the profile that you chose in the previous step) from the TEI files. (Have a look at olac2cmdi.xsl and imdi2clarin.xsl for some inspiration).

If you have old records in

Dublin Core

See: http://dublincore.org/

(or

Open Language Archives Community

See: http://www.language-archives.org

, a linguistic extension of DC) you can use the following profile:

http://catalog.clarin.eu/ds/ComponentRegistry?item=clarin.eu:cr1:p_1288172614026

From that profile you can generate the XSD:

http://catalog.clarin.eu/ds/ComponentRegistry/rest/registry/profiles/clarin.eu:cr1:p_1288172614026/xsd

And then you can transform your DC XML files into

Component Metadata Infrastructure

See: http://www.clarin.eu/cmdi

files that comply with the profile with the following XSLT:

http://www.clarin.eu/cmd/xslt/olac2cmdi.xsl

An example (DC) inputfile:
http://infra.clarin.eu/cmd/example/conversion/input/oai_ota_oucs_0001.xml

The corresponding (CMDI) outputfile:
http://infra.clarin.eu/cmd/example/conversion/output/oai_ota_oucs_0001.cmdi