...
Question | Answer | |
|---|---|---|
| 1 | For script identification, do we just consider the Unicode value? Or do we allow the user to enter the script in the instance and NOT map it from the 880 $6? | I lean toward keeping the Instance data “locked” when source = MARC but would like this confirmed (-Laura) |
| 2 | List of elements/fields we want to consider | see table on slide 6 |
| 3 | Do we need to consider unlinked 880s? |
|
| 4 | Are we considering the concept of a “primary” field? | I think we need to, ideally would be configurable at tenant level (-Laura) |
| 5 | Did we decide on which script would be shown in the results list - (I know that each would be indexed and searchable as the same element)? | Outstanding question to bring back to MM--I think it’s best to show both/all, with the “primary” one displaying first and being the sort value (-Laura) |
| 6 | For configuring the “primary” field - does this mean setting whether an 880 value or the other tag (such as 245) should be the preferred form? - this may be complicated by the ability to add multiple 880 links. | |
| 7 | Do we need to capture the orientation? | |
| 8 | For source = MARC, should we only map scripts from the 880$6 when the code matches the Unicode code?
| |
| 9 | Would configuration of primary script occur for all fields, or per field? For example, is a different script the primary for Resource title vs Contributor? Or would one script be considered the primary script for all fields? | Designation of primary script would be applied across all fields. |
| 10 | Do we want “graphical” instead of “graphic” as listed in the standard? | “Graphic” is fine. Updating various documents to reflect this (6//5/2025) |
| 11 | When configuring the primary script, is this a question of transliterated vs the vernacular script? Or a specific script to prefer if available, else use the tag that is linked from the 880? |
...