Metadata discussed this ticket during our meeting on 1/7/25: Regarding the EAD 2.0 export for language/script of description : Within the <profiledesc> portion of the <eadheader> an optional subelement <langsage> can be used to provide information about the languages, sublanguages, and dialects represented in the finding aid. The language(s) in which the finding aid is written can be further specified using the <language> subelement within <langusage>. For bilingual or multilingual finding aids, either identify each language in a separate <language> element, or mention only the predominant language. The LANGCODE attribute can be used to provide the three-letter ISO 639-2b code for the language. The SCRIPTCODE attribute may be used to specify the ISO 15924 code for the script in which the language is written.

Metadata will address this as part of their review of export functionality next term.

DevPri discussed this ticket at the November 2022 meeting and recommend:

1. No changes should be made to fields searchable in the PUI

2. Fields should display consistently

3. Do not add an option to publish certain fields (a new ticket should be created if this is a future issue for users)

4. Metadata standards should review the EAD export display issues before passing the ticket

The table in my October 21 comment has been updated to reflect the November 2022 DevPri discussion

Some notes:

• Backend PDFs are generated from EAD, hence you cannot have "No" in the latter column and "Yes" in the former.

• If display of certain fields are optional in the PUI because they might contain confidential information, then they should also be optional in EAD (because otherwise they'll be made public via OAI-PMH) and backend PDFs (because some ArchivesSpace members, such as Yale, serve backend PDFs via their public web sites.)

• Are end users likely to want to search for the finding aid's author, or the language/script it is written in? It means someone searching for English poetry will get back results including poetry in all other languages, as long as they are described in English. Or someone searching for Paris will get back results including any collections catalogued by someone with Paris in their name. It might be better to give such fields their own dedicated indexes, for searching/filtering in the staff interface.

Usability reviewed this ticket at the October 2022 meeting and created a new chart documenting optimal display outcomes. We recommend at least two fields (Sponsor; Finding Aid Note) are optional to publish. All other fields should display consistently. We also recommend the Finding Aid Date, Finding Aid Author, and Script of Description display on the PDF title page.