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)

List of elements/fields we want to consider

 see table on slide 6

Do we need to consider unlinked 880s?

Are we considering the concept of a “primary” field?

 I think we need to, ideally would be configurable at tenant level (-Laura)

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)

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.

Do we need to capture the orientation?

For source = MARC, should we only map scripts from the 880$6 when the code matches the Unicode code?

• For example - Arabic:

  • MARC-8 coded character set escape sequences = (3

  • Unicode = arab

• Would we leave the script undefined for the MARC-8 coded character, but identify the script as “Arabic” if we find the Unicode version?

https://www.unicode.org/iso15924/iso15924-codes.html

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?

Do we want “graphical” instead of “graphic” as listed in the standard?

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?

The Instance should capture data on multiple graphic representations (data in multiple scripts)

FOLIO source Instances should have the ability to enter an element in a script, identify the corresponding field for which it is equivalent, and identify the script itself

For MARC source Instances, this data should be mapped from 880 fields

Multiple scripts should be able to be paired with other fields

For example, the system needs to be able to correlate multiple scripts to the resource title field.

 Fields we need to support:

• Contributor

• Resource title

• Index title

• Alternative title(s)

• Edition

• Preceding title

• Succeeding title

• Uniform title

• Series statement

• Publisher

• Place

• Physical description

• Instance notes

• Child instances

• Parent instances

• Other related titles

Need to support tenant-level configuration of which script is considered the primary script

*For ECS, would need to be configurable at the member tenant level

Contributor

100, 110, 111, 700, 710, 711

Resource title

245

Index title

245 adjusted according to 2nd indicator

Alternative title(s)

246, 247, 730, 740

Edition

250

Preceding title

780

Succeeding title

785

Uniform title

130, 240

Series statement

130, 240

Publisher

260/264$b

Place

260/264$b

Physical description

300

Instance notes

Parent instances

Other related titles (don’t currently capture)

787