Bug #1924

Updated by David Juhasz about 8 years ago

*To To recreate this issue:* issue:

1) At the ingest stage in Archivematica, add metadata to a DIP before uploading it to AtoM (using the Dublin Core template provided in Archivematica)

2) In the language field, insert an ISO 3166-compliant language (i.e., ISO recognized 3 letter code for language)

3) upload the DIP to AtoM, adding an intermediate description level (so that the metadata you have created in the Archivematica DC template will be exported to AtoM)

4) In AtoM, navigate to your new intermediate description

*Resulting error:*

Resulting error:

Language is imported into AtoM in the correct field, but does not correspond to the auto-populated ISO-compliant language list, and does not replace the 3 letter language code with a language name formatted for readability. Further, if the user attempts to edit this language (using the "Edit" button in AtoM and navigating to the language field), the imported language does not show up on the edit template (field appears blank), and any new language entered in the template will overwrite the imported language selection.

*Expected Result:*

Expected Result:

User should be able to enter a language in Archivematica in an ISO 3166-compliant format, formate, and have it be recognized by AtoM, stored, and replaced with the appropriate language label formatted for readability (ex: entering "fre" in Archivematica should result in "French" being displayed in AtoM).

User should be able to enter edit mode on the archival description, and see the imported language listed. User should be able to add other languages without overwriting the imported language data, and/or delete the imported data without having to overwrite it with new data.

*Notes Notes on this issue* issue

This issue will be difficult to resolve without potentially changing the data entry field in Archivematica, and/or introducing new script into AtoM.

* One option would be to include a drop-down menu with languages in Archivematica that is linked to the IS0-compliant language format - similar to AtoM. This requires a redesign of the existing metadata template and packaging the languages with Archivematica.

* Otherwise, Archivematica may need to encode the field differently, and/or script may need to be added to AtoM to properly recognize the ISO compliant data entered and populate the field with a readable language label upon import.

[g] Legacy categories: Data management