Comments COAR-Repositories

Sometimes names of Indigenous Australians will include their traditional country and that needs to be captured

The issue of controlled vocabularies not being comprehensive, is especially the case in relation to First Nations people in Australia

Presumably this is an area where AI could actually usefully be employed, though it is not my area of expertise

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.

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.

(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

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.

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.

 
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
 

ORCID or ISNE help to identify authors or creators nowadays, but the use of authorities catalogues should be included.