Known issue tracking

Summary: The table below records known issues in the migration to FOLIO along with any workarounds and statuses. Contact your supervisor with any questions or concerns.


 

 

Contact

Kay Granskog, Joshua Barton, Autumn Faulkner

Team

Tech Services

Updated

July 2023

Created

July 2022

 



Issue Name

Brief description

Workaround

Status

Issue Name

Brief description

Workaround

Status

Position 5 Error

“Position 5” code in the MARC Leader = “record status.” This was not used in Sierra, but FOLIO validates MARC upon saving, an invalid code will stop the record from saving. Invalid codes migrated from Sierra (too many to quickly clean up)

Change “record status” to a valid code. C - “corrected or revised” is recommended. In the example below, ‘c' is in ‘position 5’ in the leader.

 

Known issue because of bad data in Sierra. A clean-up project to deal with the 150k-200k affected records may be undertaken in future.

Mismatch between Leader and 008.

User cannot edit MARC SRS record. Usually receives error message “Record cannot be saved. Leader and 008 do not match.” Cannot be corrected in QuickMARC because valid 008 cannot be added.

  • Create a workform in OCLC with valid fixed field coding.

  • Copy information from FOLIO (110, 245, 246s, notes, etc.) to the workform and add 947 $c with instance number.

  • DO NOT update workform to send to OCLC.

  • Go to Tools > Options > Export and make sure that “Allow export of workforms” is checked.

  • Export the workform and overlay the FOLIO instance (CAT5 job profile).

  • Use QuickMARC to delete 035 (OCoLC)NEW.

Known issue affecting records which were created locally in Sierra for staff use (such as records ACQ uses to order e-packages) and which have invalid MARC data. Will be fixed as staff find them.

Going forward, records such as these for staff use only will be created as source=FOLIO to avoid validation problems.

Missing Instances

Orders in Folio that have no linked Instance. There is a hot-linked title in the FOLIO order record, but the link doesn’t actually go to an instance record.  When the instance is searched in Inventory, it doesn’t exist.

  • Double-check that there is no instance by searching the order number in Sierra, copying the Sierra bib number, and searching the bib number in FOLIO.  If you still don’t find an instance:

  • Bring in a new instance as you would for any other piece with no instance to overlay.

  • Catalog normally and send the piece on.

  • Keep track of the POL number and the corresponding new instance number, either on a list or by writing the instance number on the order streamer.

  • Give the list or streamers to JKB.  For now she will re-link the order record to the new instance.

  • As of January 2023, Ebsco has restored the missing instances, but the links between instance and SRS have been broken so the restored instances are not usable.

  • Restored instances have ‘view source’ and ‘edit MARC’ options greyed out on the Actions menu, and no import job will work for these records.

  • If you find these unusable instances in the future, follow instructions for Resolving import errors of disassociated Instances and SRS.