Metadata field changes

[UcDust]

Item 1 mentions changes to metadata fields.

Once we have a list of the fields being changed/added, we can add them to the transform code so it can be indexed and available to the ui.

We'll also need to determine how to represent the new data in the ui once finalized.

[EricNebeker]

Physical description (schema:material)
Location
Language

[EricNebeker]

For schema:material, use format in the UI.

[UcDust]

For the inLanguage field translation, it looks like https://en.wikipedia.org/wiki/IETF_language_tag#Syntax_of_language_tags could be helpful. This registry has a standard subtag registry we may be able to use, although the tags in https://stage.dams.library.ucdavis.edu/fcrepo/rest/collection/boh/hours/book_of_hours don't seem to match the official tags in this registry. @EricNebeker do you know where those language codes came from?

[UcDust]

@EricNebeker

This is what it should look like now:

The language metadata is described here. They would look like:

"schema:material": "ff. i + 97 + i - Plain red morocco, twentieth century. Parchment - 206 x 155 mm - 21-22 long lines ruled in pale red ink",
"schema:location": "Poitiers, France",
"schema:inLanguage": {"@id": "https://www.iana.org/assignments/language-subtag-registry#cy"},

Or, for collections with multiple languages, inLanguage can be an array type:

"schema:inLanguage": [
    {"@id": "https://www.iana.org/assignments/language-subtag-registry#fr"},
    {"@id": "https://www.iana.org/assignments/language-subtag-registry#la"}
  ]