search

sul-dlss / folio-support

For FOLIO users to report issues or send feedback
0 stars 0 forks source link

Linked 880 fields #29

Closed ahafele closed 1 year ago

ahafele commented 2 years ago
  1. Many 880 fields with information in non-Latin script are not mapped, and therefore not visible in the Instance record. These include 250, 264, 490, 5xx's including 505 (multiple EAL staff have commented about the 505 in original script not displaying), 6xx, 7xx. Only the 880s that are paired with the main entry (1xx) and the 245 display. Can more 880s be mapped for display in the Instance record?

Below is the list of how linked 880 fields are handled. https://docs.google.com/spreadsheets/d/11lGBiPoetHuC3u-onVVLN4Mj5KtVHqJaQe4RqCxgGzo/edit#gid=915548926

It is my understanding that any linked field that is in default mapping will be included. See https://drive.google.com/file/d/1nxZ450PIQJgSnqrL9B5s6-eSrzaeGBE2/view?usp=sharing. Work done here - https://issues.folio.org/browse/MODDICORE-114

Example - Working for 500 a10498189, but not 505 a12196508

  1. Can an 880 be "preferred" over a regular MARC tag with transliterated data? needs investigation to see if this could be written into the mapping rules

There was a former Alternate Graphical Representations where some of these things were discussed around 2019-2020.

Note: all existing original script fields displaying in the instance is wanted by Hoover

ahafele commented 2 years ago

This seems to be a bug and not a result of the mapping. Documented here https://github.com/sul-dlss/FOLIO-Project-Stanford/issues/242

ahafele commented 1 year ago

This was fixed in the upstream Ebsco Migration Tools. The migration tools will now have parity with Data Import. All 880s with a mapped equivalent will show in instance.