MARC bib - FOLIO instance mapping | Adjust contributor and relator term mapping WRT punctuation

Description

Summary:

  1. Adjust the 1xx/7xx name mappings so that any ending periods and commas are ignored, so that the contributor browse index will not split names into separate entries solely because of ending punctuation

  2. Refine the relator term (contributor type) mappings that were worked on in MODSOURMAN-837 to ignore ending period, comma, semi-colon when comparing $e or $j term to the spelled-out version of $4, so that more relator terms will be in the controlled field than in the free-text field.

Punctuation marks
period = .
comma = ,
semi-colon = ;

Background:
See attached MARC record and Excel file with changes

Scenario 1

  • For the MARC 100, 110, 111, 700, 710, 711, and 720, FOLIO currently maps the following subfields to the name field:

    • 100$abcdfgjklnpqtu

    • 110$abcdfgklnptu

    • 111$abcdfgklnptu

    • 700$abcdfgjklnopqtu

    • 710$abcdfgklnoptu

    • 711$abcdfgklnptu

    • 720$a

  • And currently if the ending punctuation of the last mapped subfield is a period, we strip it, but if the ending punctuation of the last mapped subfield is a comma, we do not strip it. That leads to results in red in column B of the attached spreadsheet, with commas at the end of some names. When that happens, the browse index will be split, as can be seen in the attached Contributor ending punctuation screenshot

  • CHANGE:

    • If ending punctuation of the last mapped subfield of the field is a period or comma, then remove it, EXCEPT

      • If the last mapped text ends with a single letter and then a period (e.g. Brown, Sterling K.), then do not remove the ending period

      • If the last mapped text ends with a period, followed by a comma, (e.g. Brown, Sterling K,.), then remove the comma, but leave the period

      • If the last mapped text ends with a hyphen (e.g. Kaluuya, Daniel, 1989-), then do not remove the hyphen

Scenario 2

  • For the MARC fields 100, 110, 700, and 710

  • Refine the instance contributor type assignment, so that any ending punctuation (period, comma, semi-colon) is ignored when comparing the text of the $e to the spelled-out version of the relator codes. See attached spreadsheet columns E, F, G, H for examples of current assignments versus updated assignments for the contributors in the attached MARC file, once these changes are in place.

  • Question: what to do when the spelled-out term for the contributor type ends in a period, e.g. Author of introduction, etc. Maybe ignore ending punctuation for both the $j and the spelled out version of the contributor type when comparing?

Scenario 3

  • For the MARC fields 111 and 711

  • Refine the instance contributor type assignment, so that any ending punctuation (period, comma, semi-colon) is ignored when comparing the text of the $j to the spelled-out version of the relator codes. See attached spreadsheet columns E, F, G, H for examples of current assignments versus updated assignments for the contributors in the attached MARC file, once these changes are in place.

  • Question: what to do when the spelled-out term for the contributor type ends in a period, e.g. Author of introduction, etc. Maybe ignore ending punctuation for both the $j and the spelled out version of the contributor type when comparing?

Scenario 4

  • Create an Orchid-to-Poppy migration script, since this is a mandatory mapping change

  • If a migration script is needed, please move this scenario to a separate Jira, and cover MODDICORE-323 also

Document in the following areas:

Notes:

  • Import the following authority records to check ending punctuation:

    • no2014066732 Shawver, Michael P.

    • n 83169267 Lee, Stan, 1922-2018

Manual testing

  • Import the attached MARC record

  • Compare the contributor name, type, and free-text fields to columns C, G, and H in the attached spreadsheet

Environment

None

Potential Workaround

None

Attachments

5
100% Done
Loading...

Checklist

hide

TestRail: Results

Activity

Show:

Ann-Marie Breaux June 23, 2023 at 1:29 PM

Thanks for making the little fix, . All looks great!

A-M

Maksym Ishchenko June 22, 2023 at 12:52 PM

Hi  

Ticket verified on snapshot env. 700 field with Wright Letitia is now mapped as expected. Moving ticket to In review column

Screenshot:

cc:  

Volodymyr Rohach June 19, 2023 at 9:12 AM

Hi ! I moved it back to In progress. Investigating this case.

Ann-Marie Breaux June 19, 2023 at 5:53 AM

Hi and There's one configuration that does not match the spreadsheet:

  • 700 1 ‡a Wright, Letitia, ‡d 1993- ‡e author of introduction, etc.; ‡e actor.

Has a period, then a semi-colon after the first $e. If you remove the semi-colon, but not the period, you are left with a valid relator term: Author of introduction, etc. so that should be the one displayed for Letitia Wright instead of Actor. Would it be better to close this issue and make a small bug?

cc:

Maksym Ishchenko June 16, 2023 at 10:18 AM

Hi  

Ticket verified on snapshot env. All contributors values are mapped as expected. Moving ticket to In review column

Screencast:

cc:  

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Folijet

Fix versions

Release

Poppy (R2 2023)

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created April 26, 2023 at 8:52 AM
Updated May 27, 2024 at 7:35 AM
Resolved June 23, 2023 at 1:29 PM
TestRail: Cases
TestRail: Runs