...
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 | |
Project title | |
|---|---|
Issue | |
Status | |
Assigned to | |
Priority | |
Instructions | |