Bug #1924

Archivematica language metadata not exporting properly to AtoM

Added by David Juhasz over 8 years ago. Updated over 6 years ago.

Status:NewStart date:
Priority:MediumDue date:
Assignee:-% Done:


Target version:post 1.1
Google Code Legacy ID:archivematica-1269 Pull Request:
Sponsored:No Requires documentation:


To recreate this 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:

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:

User should be able to enter a language in Archivematica in an ISO 3166-compliant format, 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 on this 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

justin_1924_1-ee3cd8bb-675b-4b24-9f37-9609a1529fae.tar.gz (1.35 MB) Justin Simpson, 03/18/2014 07:26 PM


#1 Updated by David Juhasz over 8 years ago

[g] New owner: Mike Cantelon

#2 Updated by Redmine Admin over 8 years ago

  • Category set to Metadata

#3 Updated by Courtney Mumma about 8 years ago

  • Target version set to Release 1.0.0

#4 Updated by David Juhasz about 8 years ago

  • Sponsored set to No

See related AtoM issue #4451, and fixes for that issue in https://github.com/artefactual/atom/commit/8de68ca36aef3418b4a2f02968143b9218e0e57c

I think it would be better to use the same DC import code for AtoM DC import (lib/QubitXmlImport.class.php) and SWORD transfer (plugins/qtSwordPlugin/lib/qtPackageExtractorMETSArchivematicaDIP.class.php) rather then maintaing two separate DC profiles.

#5 Updated by David Juhasz about 8 years ago

  • Description updated (diff)

Fix formatting of description text

#6 Updated by Courtney Mumma about 8 years ago

  • Assignee changed from Mike Cantelon to Jesús García Crespo

#7 Updated by Courtney Mumma over 7 years ago

  • Target version changed from Release 1.0.0 to Release 1.1.0

#8 Updated by Justin Simpson over 7 years ago

I have a couple questions about this ticket. ISO-3166 appears to be a set of country codes, not language codes. I think language codes are listed in ISO-639.

I tested dip upload to Atom 2.0.1 from Archivematica 1.1 rc1. The digital objects get uploaded, but none of the dc metadata appears in Atom. The dip includes a METS file that lists the dc that was entered in Archivematica, here is a snippet of my sample:

<?xml version='1.0' encoding='ASCII'?>
<mets xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.loc.gov/METS/" xsi:schemaLocation="http://www.loc.gov/METS/ http://www.loc.gov/standards/mets/version18/mets.xsd">
  <metsHdr CREATEDATE="2014-03-19T01:24:20"/>
  <dmdSec ID="dmdSec_1">
    <mdWrap MDTYPE="DC">
        <dublincore xmlns="http://purl.org/dc/terms/" xsi:schemaLocation="http://purl.org/dc/terms/ http://dublincore.org/schemas/xmls/qdc/2008/02/11/dcterms.xsd">
          <title>Testing bug 1924</title>
          <type>Archival Information Package</type>

Archivematica is not restricting the possible values that can be entered for language in the dc metadata form, that is one issue.

How much of the dc metadata is supposed to show up in Atom 2.0.1? Where is it displayed?

#9 Updated by Justin Simpson over 7 years ago

I attached a dip that has this mets file in it, that I tested with.

#10 Updated by Justin Simpson about 7 years ago

  • Target version changed from Release 1.1.0 to post 1.1

the language metadata issue here is not getting fixed in 1.1.

#11 Updated by Jesús García Crespo over 6 years ago

  • Assignee deleted (Jesús García Crespo)

Also available in: Atom PDF