Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Scope: Bibliographic data (i.e. bib, holding, item) cleanup is an essential activity to ensure data integrity and operational efficiencies.  This page lists all of components for the  FY22 project. Links to project component action plans lead to the Box folder for the project.  This page will be updated to reflect new or updated information as the timeline advances.

Contact: Jacquie Samples Natalie Sommerville

Units: Metadata and Discovery Strategy Department and Resource Description Department

Date created:  07/29 Jul /2021 

Date of next review: 07/15 Jul /2022 

...

Priority Definitions

LevelPriorityPriority description
P1

Major Blocker/no work around
Must be completed before or during OCLC DataSync and Postwork period

Probable deadlines prior to May 27, 2022

Broken data that means FOLIO will not work correctly if it is not cleaned up.
Project need for transition to RapidILL
Patrons may not be able to find/access materials.
Example: bad Unicode as found in error logs from Nov. 2020 Honeysuckle load
P2

Huge Hurdle/work around painful
Can wait until after OCLC DataSync, but before FOLIO implementation


Probable deadlines prior to June 30, 2022 (adjusted since FOLIO timeline shifted)

Errors in data that will be difficult or impossible to remediate in FOLIO on migration or immediately after migration. 
Example: Item material type is BK instead of SER.
Example: Batch change IPS for withdrawing items, missing items, etc.
Example: Fragile data like the LKR , like multiple bibs for 1 title.
Example: Addressing invalid (legacy) location codes when the code exists in Aleph records but not in Aleph tables (PENAP, ECCO, etc.)

P3

Data Enhancement/work around not sustainable

Probable deadline time-frame to be determined

Data change not possible in FOLIO  on migration or immediately after migration, but we could limp along.  Fine for now, clean up would add value.
P4Nice to doProbably can't do in FOLIO, but won't really mess any process up.
P5none knownJust don't forget this type of problem exists

...