Appendix 2. Declare the language of the resource at the item level: Implementation examples following metadata standards/guidelines
| Datacite Schema 4.4 | 9 LanguageUsage: optional Occurrence: 0-1 (Not repeatable)Recommended encoding IETF BCP 47 or ISO 639-1 language codes |
| Dublin Core (DC) | Term Name: languageUsage: optionalOccurrence: repeatableRecommended practice is to use either a non-literal value representing a language from a controlled vocabulary such as ISO 639-2 or ISO 639-3, or a literal value consisting of an IETF Best Current Practice 47 [IETF-BCP47] language tag. |
| Electronic thesis and dissertation metadata standard (ETDMS) | dc.languageUsage : Optional,Occurrence: 0-N (Repeatable) Language names themselves should be recorded using ISO 639-2 (or RFC 1766). If the language is not specified, it is assumed to be english (en). |
| Metadata Object Description Schema (MODS) | Top Level Element <language>Usage : OptionalOccurrence: 0-N (Repeatable)This resource contains both English and French text:<language><languageTerm type=”code” authority=”iso639-2b”>eng<languageTerm></language><language><languageTerm type=”code” authority=”iso639-2b”>fre<languageTerm></language> This resource contains text in Egyptian Arabic, which is coded as an individual language in ISO 639-3:<language><languageTerm type=”code” authority=”rfc4646″ >zh-Hans</languageTerm></language><language><languageTerm type=”code” authority=”iso639-3″ >arz</languageTerm></language> |
| OpenAIRE Guidelines for Literature, institutional, and thematic Repositories | dc:languageUsage: Mandatory if Applicable (MA)Occurrence: 0-N (Repeatable)Recommendation: take values from one of the following lists:IETF BCP 47, the IANA Language Subtag RegistryISO 639-x, where x can be 1,2 or 3. Best Practice: we use ISO 639-3 and by doing so we follow: http://www.sil.org/iso639-3/If necessary, repeat this element to indicate multiple languages.If ISO 639-2 and 639-1 are sufficient for the contents of a repository they can be used alternatively. Since there is a unique mapping this can be done during an aggregation process. |
| Japan Consortium for Open Access Repository (JPCOAR) | dc:languageUsage: R (Recommended)Occurrence: 0-N (Repeatable: expect mandatory term)Usage InstructionsEnter the main languages that are used in the main text of the resource. Use the ISO 639-3 language codes.It is optional to use the ISO 639-3 macrolanguage.NotesDo not enter language names.Do not enter country names.Enter in order of language priority.Recommended ExamplesThe main text of the resource is in English.<dc:language>eng</dc:language>The main text of the resource is in English and Japanese.<dc:language>eng</dc:language><dc:language>jpn</dc:language> Unrecommended ExamplesISO 639-1 is not recommended.<dc:language>ja</dc:language> Do not enter multiple languages in one element.<dc:language>engjpn</dc:language>Do not use capital letters and double-byte characters.<dc:language>JPN</dc:language><dc:language>ｅｎｇ</dc:language>Do not enter language names.<dc:language>日本語</dc:language>Do not enter country names.<dc:language>US</dc:language>Do not enter language codes other than ISO 639.<dc:language>en_US</dc:language> |
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