Skip to end of banner
Go to start of banner

FOLIO Migration Clean-up Projects

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Summary: This document lists and tracks database clean-up projects discovered as a part of the test mapping undertaken by EBSCO and the MSU/LM Cataloging & Metadata Taskforce.

Instance format 338 $b

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

Unassigned

Assigned to

Metadata Management? Catalog Management?

Priority

Instructions

Instance format 337 + 338 term variations

Issue

Various versions of the term “rdacarrier” and other 33X vocab terms are incorrect in our data.

Status

In progress? Joshua handed off to Lisa R.

Assigned to

MetMan

Priority

Instructions

Record status (Leader/05) invalid values

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

Unassigned

Assigned to

MetMan? CatMan? CopyCat?

Priority

Instructions

001s to 035s

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

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

Assigned to

Priority

Instructions

Invalid mode of issuance codes

Issue

A handful of invalid codes in Leader byte 7 (mode of issuance) need correcting.

Status

Unassigned?

Assigned to

Lisa R.? Others?

Priority

Instructions

The columns below represent the incorrect values (left) and the number of records which contain them. In Sierra, find and correct each one.

2 1

8 1

I 3

L 1

N 1

e 1

g 1

q 1

t 1

u 1

y 1

Invalid language codes

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

Unassigned

Assigned to

CopyCat?

Priority

Instructions

  • No labels