Issue

MARC relator codes in the $4 were used before the advent of of RDA relationship designators. These $4 codes will be mapped to equivalent RDA RDs in the ultimate migration of catalog data to FOLIO. However, we have some incorrect values in some $4s in our records which need to be resolved, so that these mappings are successful.

Status

Unassigned

Assigned to

Priority

Instructions

• Open this spreadsheet: $4 incorrect values clean up -- 2nd load - Google Sheets

  • Skip orange highlighted entries – these changes can be made via Global Update, and also Dao is checking to see if trailing periods are being added by export or FOLIO processes, rather than being present in our existing data

• Perform Create List or Browse Query searches for the incorrect values in question

• Correct each erroneous code, using the MARC Relator Code list as a reference: Relator Code and Term List -- Term Sequence: MARC 21 Source Codes (Network Development and MARC Standards Office, Library of Congress) (loc.gov)

  • Check for trailing spaces

• If uncertain, remove $4 altogether and either assign RDA relationship designator instead, or omit entirely

Issue

Convert the 260 $e, f and g to the relevant 264 for rare books

Status

Assigned; not begun

Assigned to

CopyCat

Priority

Instructions

• TBD by Joshua Barton

Issue

Valid values are a, c, d, n, p; we have a lot of invalid values.

Will need to run a Create List to grab invalid values. Probably export to spreadsheet will be most effective for isolating invalid values.

Status

In Progress

Assigned to

CatMan

Priority

Instructions

Issue

Possible project needed to identify control numbers (OCLC and vendor) in the 001 that aren’t present in corresponding 035 fields, and therefore are not mapped to identifier types in FOLIO.

Status

Tentative project pending This might already be in the works – Dao and Lucas can clarify/confirm.

Assigned to

Priority

Instructions

Issue

~3500 records with invalid language codes need correcting.

• ??? and unk can probably be globally updated to und

• Others will need manual review and changes, with an eye to ISO codes that may be present

  • Lucas’s notes: Some codes flagged as invalid are valid iso639-3 codes and rightly tagged in the source MARC record's 041; some others have the same three characters as valid iso639-3 code but not coded as iso639-3 in 041$2 which I think may be invalid (have to take a look of the MARC 546 to decide)

• See list here

Status

Assigned

Assigned to

MetMan

Priority

Instructions

Issue

3 Records failed to transform through the mapping migration process. In each case, EBSCO failed to find a title.

MSULM CMTF Test DB Analysis - Google Sheets

Status

In process (need additional support from EBSCO?)

Assigned to

Lucas Mak?

Priority

Instructions

Issue

The valid leader byte 7 = a, b, c, d, i, m or s, MSU has several more than the approved type. Clean-up the old unvalid codes.

Status

Complete

Assigned to

CatMan

Priority

Instructions

• TBD by Joshua Barton

  • Use MARC Leader documentation (Bibliographic Level)

• https://github.com/FOLIO-FSE/migration_michigan_state/blob/main/migration_reports/goldenrod/instance_transformation_report.md#bibliographic-records-transformation-results

• 2 1

  8 1

  I 3

  L 1

  N 1

  e 1

  g 1

  q 1

  t 1

  u 1

  y 1

Issue

There are 873 records that do not have a 336$b. These were automatically assigned ‘text’ by default.

• Please note: in the absence of a 336$b, we would look at the relevant positions in the 008. However, there were several instances of unexpected 008 values, as seen in the ‘Mapped instance types’ section (https://github.com/FOLIO-FSE/migration_michigan_state/blob/main/migration_reports/goldenrod/instance_transformation_report.md#mapped-instance-types)

Status

Complete

Assigned to

CopyCat

Priority

Instructions

• Run a Create List identifying these records in Sierra

• Add appropriate 336$b data.

• Other instructions TBD by Autumn.

Issue

Leading or trailing spaces in Sierra MARC record causing valid 338$b values to appear as errors in FOLIO migration.

Review file 379 has 391 records needing removal of these spaces, and there are some other formatting issues in the 338 field that can be resolved as well.

See 338 Carrier Type (oclc.org) for correct formatting and values.

Status

Complete

Assigned to

CatMan

Priority

Instructions

Issue

Various versions of the term “rdacarrier” and other 338 $2 vocab terms are incorrect in our data.

Status

Complete

Assigned to

MetMan (338 $2)

Priority

Instructions

Issue

15 records with no title.

MSULM CMTF Test DB Analysis - Google Sheets

Status

Complete

Assigned to

CatMan

Priority

Instructions