Appendix 3. Declare the language of the metadata (xml:lang attribute): Implementation examples following metadata standards/guidelines
Datacite Schema 4.4 | xml:lang=”EN”, for example <xs:element name=”title” maxOccurs=”unbounded”><xs:annotation><xs:documentation>A name or title by which a resource is known.</xs:documentation></xs:annotation><xs:complexType><xs:simpleContent><xs:extension base=”xs:string”><xs:attribute name=”titleType” type=”titleType” use=”optional”/><xs:attribute ref=”xml:lang”/>Similarly, for xs:element name=”creatorName“>, <xs:element name=”publisher“>, <xs:element name=”subjects” minOccurs=”0″>, <xs:element name=”contributorName“>, <xs:element name=”rightsList” minOccurs=”0″>, <xs:element name=”descriptions” minOccurs=”0″>, <xs:element name=”language” type=”xs:language” minOccurs=”0″>, <xs:annotation><xs:documentation>Primary language of the resource. Allowed values are taken from IETF BCP 47, ISO 639-1 language codes.</xs:documentation> |
Dublin Core (DC) | Where the language of the value is indicated, it should be encoded using the ‘xml:lang’ attribute. For example:<dc:subject xml:lang=”en”>seafood</dc:subject><dc:subject xml:lang=”fr”>fruits de mer</dc:subject> |
Electronic thesis and dissertation metadata standard (ETDMS) | Language is a global qualifier that can be used in any element: https://ndltd.org/wp-content/uploads/2021/04/etd-ms-v1.1.html#qualifiers |
Metadata Object Description Schema (MODS) | There are Language-Related Attributes https://www.loc.gov/standards/mods/userguide/attributes.html#listISO 639-2/b |
OpenAIRE institutional and thematic repository Guidelines | The use of the xml:lang attribute to indicate the language of the metadata. Example: <dc:description> Foreword [by] Hazel Anderson; Introduction; The scientific heresy: transformation of a society; Consciousness as causal reality [etc]</dc:description> <dc:description xml:lang=”en-US”> A number of problems in quantum state and system identification are addressed.</dc:description>OpenAIRE supports the xml language tag and the aggregator conducts metadata checks for language – e.g. in subjects, titles and abstracts/descriptions; no names though – ORCID is recommended for names – OpenAIRE I+T: Title https://openaire-guidelines-for-literature-repository-managers.readthedocs.io/en/latest/field_title.html#dci-title , Description https://openaire-guidelines-for-literature-repository-managers.readthedocs.io/en/latest/field_description.html#attribute-lang-oOpenAIRE also allows multiple languages https://openaire-guidelines-for-literature-repository-managers.readthedocs.io/en/v4.0.0/field_language.html – content resource has this language. |
JPCOAR 1.0.2https://schema.irdb.nii.ac.jp/ja/schema | xml:lang attribute can be used for each element In principle, use the two-digit language code of ISO 639-1 (e.g. Japanese: “ja”; English: “en”).For Japanese ‘yomi’, use “ja-Kana“. Where ‘yomi’ is entered, you must enter its original information (i.e. in kanji) with the description that ‘xml:lang is “ja”’.For Chinese, it is desirable to separately enter simplified Chinese as “zh-ch” and traditional Chinese as “zh-tw”. |
JPCOAR Metadata Schema 2.0 Drafthttps://schema.irdb.nii.ac.jp/ja/schema/2.0-draft/14 https://schema.irdb.nii.ac.jp/ja/schema/2.0-draft/1 | Change from 1.0.2 : additionally support “ja-Latn”.The Excerpts from updated part:For Japanese ‘yomi’with Katakana characters, use “ja-Kana” and For Japanese ‘yomi’ with Roman letters (alphabet), use “ja-Latn”. Where ‘yomi’ is entered, you must enter its original information (i.e. in kanji) with the description that ‘xml:lang is “ja”’. |
Akdeniz, Esra, & Moilanen, Katja. (2023). CMM CESSDA Metadata Model (3.0). Zenodo. https://doi.org/10.5281/zenodo.7528240 | 1.1.3.1 Language of Study TitleThe language of the content of the element.MISO 639-1Occurrence 1ddi:DDIInstance/s:StudyUnit/r:Citation/r:Title/r:String/@xml:lang Similarly for Language of Subtitle; Language of Alternative Title; Language of Versioning Reason; Language of Abstract; Language of Study Topic (descriptive); Language of Keyword (descriptive); Language of discipline (freetext); Language of Type of Data Source (descriptive); Language of Mode of Data Collection (descriptive); Language of Data Access Conditions; Language of Metadata Access Conditions (Study); Language of Full Name of Organization; Language of Organization Name Abbreviation/Acronym; Language of Description of the organization; Language of Dataset Version Description; Dataset Language; Language of Dataset File Description; Language of File Name; Language of Document Title; Language of Publication Title; Language of Name of the Journal/Serial – 75 metadata fields overall to indicate the language; There are also metadata fields to indicating translations, e.g. 1.1.3.2Translation Status of Study TitleIs the content of the element translated?Rtrue, falseOccurrence 0-1ddi:DDIInstance/s:StudyUnit/r:Citation/r:Title/r:String/@isTranslated; and 28 metadata fields mentioning translation |
Recent Comments in this Document
June 30, 2023 at 5:22 am
Sometimes names of Indigenous Australians will include their traditional country and that needs to be captured
See in context
June 30, 2023 at 5:20 am
The issue of controlled vocabularies not being comprehensive, is especially the case in relation to First Nations people in Australia
See in context
June 30, 2023 at 5:18 am
Presumably this is an area where AI could actually usefully be employed, though it is not my area of expertise
See in context
June 30, 2023 at 5:13 am
We are particularly keen to note the importance of inclusion of Indigenous languages in these discussions. Alongside the use of text in a specific language is also the need to identify the Indigenous country that the work is associated with. There is work ongoing for this in Australia.
See in context
June 30, 2023 at 5:02 am
We are concerned that this will never happen at any useful scale – below the very high level. For example, it is already hard enough to get people to change US English to Australian English in a familiar word processing tool such as Word.
See in context
June 30, 2023 at 1:26 am
(This is actually a comment on Appendix 3.)There is a correction regarding the URL as follows.JPCOAR Metadata Schema 2.0 Drafthttps://schema.irdb.nii.ac.jp/ja/schema/2.0-draft/14https://schema.irdb.nii.ac.jp/ja/schema/2.0-draft/1 –>JPCOAR Metadata Schema 2.0https://schema.irdb.nii.ac.jp/en/schema/2.0/14https://schema.irdb.nii.ac.jp/en/schema/2.0/1
See in context
June 30, 2023 at 1:16 am
I corrected the descriptions about WEKO3.before: WEKO3 is a cloud-based repository system supported by JPCOAR (Japan Consortium for Open Access Repositories). It is developed based on INVENIO by CERN.↓after: WEKO3 is a repository software developed by NII (National Institute of Informatics, Japan) based on INVENIO by CERN. This software operates JAIRO Cloud, a cloud-based repository system, which is supported by JPCOAR (Japan Consortium for Open Access Repositories) and NII.before: Specifically, ISO-639-3 is acceptable as the language of the text and for a language attribute of other metadata elements, ISO-639-1 is acceptable.↓after: Specifically, ISO-639-3 is acceptable as the language of the text, and for a language attribute of other metadata elements, ISO-639-1 is acceptable.before: With each field, you can add a language tag in the form of a two-character ISO using the dropdown menu.↓after: With WEKO3, you can add the language tag in the form of a two-character ISO using the dropdown menu, checkbox, and radio button.
See in context
June 30, 2023 at 1:08 am
It would be recommended that the introduction and recommendations be translated in multiple languages and shared from the COAR website to promote and encourage the multilingualism.
See in context
June 28, 2023 at 6:04 pm
Besides the recognition of the translator we encourage to recognize all the professionals involved in the editorial process(I added) mentioned in the resource, it takes a lot of time but it is worthy. This is an example:
.contributor.assistanttotheeditorinchief
Cruz Salas, Minerva
dc.contributor.businessmanager
Zempoalteca Quintana, Mario
dc.contributor.copyeditorandtranslator
Dashner Monk, Heather
dc.contributor.designer
Pérez Ramírez, Patricia
dc.contributor.editorinchief
Jiménez, Teresa Andreu
dc.contributor.layout
Álvarez Sotelo, María Elena
dc.contributor.salesandcirculationmanager
Creamer Tejeda, Cynthia
dc.contributor.translator
Fernández Hall, María Cristina
In fact, RECOLECTA evaluation for repositories considers this point: “4.5.- Existe un campo específico para indicar la descripción de la colaboración. En este campo se registra la entidad o persona responsable de coordinar, corregir, comentar o, en general, contribuir de alguna otra manera al desarrollo del recurso” (4.5.- There is a specific field to indicate the description of the collaboration. This field records the entity or person responsible for coordinating, correcting, commenting or, in general, contributing in some other way to the development of the resource.
https://calidadrevistas.fecyt.es/sites/default/files/informes/2021guiaevaluacionrecolecta_vf.pdf
See in context
June 28, 2023 at 5:29 pm
ORCID or ISNE help to identify authors or creators nowadays, but the use of authorities catalogues should be included.
See in context