Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Language and Script of Description do not export in EAD

Description

This was mentioned in https://archivesspace.atlassian.net/browse/ANW-1055

Neither Language of Description nor Script of Description export in either EAD 2002 or EAD3. This was tested against Master as of 2021-11-23 and thus past 3.1.1.

Steps to reproduce:

  1. Create or use any Resource record with the required Language of Description, the required Script of Description, and the optional Language of Description Note

  2. Export to EAD2002

  3. Export to EAD3

  4. Note whether any fields export

I will tag the Metadata committee for an opinion on how exactly these fields should export, because it may be informed by the presence of the optional Language of Description Note.

Quick link to EAD 2002 tag library: https://www.loc.gov/ead/tglib/elements/language.html

And semi-quick link to EAD3 tag library, where you can search for <languagedeclaration>: https://www.loc.gov/ead/EAD3taglib/index.html

Environment

None

Attachments

1
  • 05 Jan 2022, 09:34 PM

Confluence content

mentioned on

Activity

Show:

Angela WhiteMarch 8, 2022 at 3:36 PM

Dev-Pri looked at this ticket during our March meeting and have decided to close it. We were not able to reproduce the error--our test exports included language and script.

Valerie AddonizioJanuary 5, 2022 at 9:34 PM

I am now commenting not as the ticket submitter but on behalf of the TAC-Metadata subteam.

For this comment, I created a resource record and indicated that the finding aid was written in the French language, Latin script, and further included a Finding Aid Language note. See screenshot.

I then got the record out through the API and isolated the relevant fields in the JSON:

    "finding_aid_language_note": "Finding aid is in French.",     "finding_aid_language": "fre",     "finding_aid_script": "Latn",

Using the field names in the JSON above, this is the proposed mapping for EAD export. Each of these requires a lookup to match the lang code (Language ISO 639-2) and script code (Language Script ISO 15924) to their display strings to populate the relevant tags. Since the finding_aid_language_note is optional, it is suggested that it only be populated when it is present, to prevent the export of empty tags.

EAD2002:

# Scenario with a value present in finding_aid_language_note. # The example below creates mixed content, but it follows the LoC EAD2002 example. <langusage> {finding_aid_language_note} <language langcode="{finding_aid_language}">French</language> <language scriptcode="{finding_aid_script}">Latin</language> </langusage> # Scenario without a value present in finding_aid_language_note: <langusage> <language langcode="{finding_aid_language}">French</language> <language scriptcode="{finding_aid_script}">Latin</language> </langusage>

 

EAD3:

# Scenario with a value present in finding_aid_language_note: <languagedeclaration> <language langcode="{finding_aid_language}">French</language> <script scriptcode="{finding_aid_script}">Latin</script> <descriptivenote><p>{finding_aid_language_note}</p></descriptivenote> </languagedeclaration> # Scenario without a value present in finding_aid_language_note: <languagedeclaration> <language langcode="{finding_aid_language}">French</language> <script scriptcode="{finding_aid_script}">Latin</script> </languagedeclaration>
Won't Do

Details

Assignee

Reporter

Labels

Priority

Harvest Time Tracking

Open Harvest Time Tracking

Created November 23, 2021 at 9:33 PM
Updated March 8, 2022 at 3:36 PM
Resolved March 8, 2022 at 3:35 PM
Harvest Time Tracking

Flag notifications