As an archivist, I would like to record finding aid Language of Description using controlled values


The current Language of Description element in the Resource record is a free-text field, without the option of recording an ISO639-2b value. We would like to be able to use a controlled value list similar to the Language field. However, we would also like to record multiple entries, with the option for linked script and note information as given in the EAD3 <languagedeclaration> element.

We would also like to have existing field data parsed and migrated to the new element, if possible.


Cory Nimer
June 13, 2018, 4:50 PM

Finalized, reviewed version of specification for Language of Description data entry, display, import, and export available here:

Cory Nimer
May 17, 2018, 3:48 PM

A specification for revisions to Language of Description data entry, display, import, and export is available at:

Cory Nimer
May 2, 2018, 6:55 PM

Alternatively, we could just rely on text boxes, perhaps with conditional requirements that if either the language or script fields are used then the note field could be used, and that if language or script is used then the other must be completed. On the backend, though, it would be helpful to have a compatible solution to allow reuse for ANW-697.

Lydia Tang
May 2, 2018, 6:32 PM

Thanks for the clarification! Maybe the Text area could be called "Language text expression" (definitely could be improved) or somehow otherwise indicate that it would function similarly to a date expression and maybe have an explanatory tool tip that describes how it's optional.

Cory Nimer
May 2, 2018, 6:25 PM

The typeahead boxes should work in the same way as the current "Language" field in Resource records, and include all available terms in ISO639-2.



Lora Woodford


Cory Nimer

Affects versions