Details
-
Story
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
None
-
-
Folijet Sprint 167, Folijet Sprint 168
-
5
-
Folijet
-
Poppy (R2 2023)
Description
Summary:
- 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
- Refine the relator term (contributor type) mappings that were worked on in
MODSOURMAN-837to 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
- If ending punctuation of the last mapped subfield of the field is a period or comma, then remove it, EXCEPT
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-323also
Document in the following areas:
- Poppy release notes (see Orchid release notes as an example: https://wiki.folio.org/display/REL/Orchid+%28R1+2023%29+Release+Notes)
- List of Poppy mapping changes: https://wiki.folio.org/display/FOLIJET/Poppy+R2+2023+Release%3A+Updates+of+default+mapping+rules+Main
- Add a page under that list with details of the change, similar to this one for Orchid relator terms: https://wiki.folio.org/display/FOLIJET/Update+of+mapping+to+change+how+Relator+term+is+populated+on+instance+record+R1+2023+Orchid+release
- Migration script: https://wiki.folio.org/display/FOLIJET/Orchid+MARC-to-Instance+mapping+rules+update+instructions
- List of mapping changes in Tips and tricks area: https://wiki.folio.org/display/FOLIOtips/Default+MARC+Bib-to-Inventory+Instance+mapping+rules+updates
- Check with abreaux if any questions
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
TestRail: Results
Attachments
Issue Links
- defines
-
UXPROD-3840 NFR: Data Import and Inventory Technical, NFR, & Misc work (Poppy R2 2023)
-
- In progress
-
- relates to
-
FAT-6404 Review of C398003
-
- Closed
-
-
MODSOURMAN-837 MARC bib - FOLIO instance mapping | Update default mapping to change how Relator term is populated on instance record
-
- Closed
-
(1 mentioned in)