The migration process

In order to perform migrations according to this process, you need the following:

FOLIO Inventory data migration process

The FSE FOLIO Migration tools requires you to run the transformation an data loading in sequence, and each step relies on previous migrations steps, like the existance of a file with legacy system IDs and their FOLIO equivalents. The below picture shows the proposed migration steps for legacy objects into FOLIO: image

Result files

The following table outlines the result records and their use and role

File

Content

Use for

folio_holdings.json

FOLIO Holdings records in json format. One per row in the file

To be loaded into FOLIO using the batch APIs

folio_instances.json

FOLIO Instance records in json format. One per row in the file

To be loaded into FOLIO using the batch APIs

folio_items.json

FOLIO Item records in json format. One per row in the file

To be loaded into FOLIO using the batch APIs

holdings_id_map.json

A json map from legacy Holdings Id to the ID of the created FOLIO Holdings record

To be used in subsequent transformation steps

holdings_transformation_report.md

A file containing various breakdowns of the transformation. Also contains errors to be fixed by the library

Create list of cleaning tasks, mapping refinement

instance_id_map.json

A json map from legacy Bib Id to the ID of the created FOLIO Instance record. Relies on the “ILS Flavour” parameter in the main_bibs.py scripts

To be used in subsequent transformation steps

instance_transformation_report.md

A file containing various breakdowns of the transformation. Also contains errors to be fixed by the library

Create list of cleaning tasks, mapping refinement

item_id_map.json

A json map from legacy Item Id to the ID of the created FOLIO Item record

To be used in subsequent transformation steps

item_transform_errors.tsv

A TSV file with errors and data issues together with the row number or id for the Item

To be used in fixing of data issues

items_transformation_report.md

A file containing various breakdowns of the transformation. Also contains errors to be fixed by the library

Create list of cleaning tasks, mapping refinement

marc_xml_dump.xml

A MARCXML dump of the bib records, with the proper 001:s and 999 fields added

For pre-loading a Discovery system.

srs.json

FOLIO SRS records in json format. One per row in the file

To be loaded into FOLIO using the batch APIs

HRID handling

Current implementation:

Download the HRID handling settings from the tenant. If there are HRID handling in the mapping rules:

  • The HRID is set on the Instance

  • The 001 in the MARC21 record (bound for SRS) is replaced with this HRID.

If the mapping-rules specify no HRID handling or the field designated for HRID contains no value:

  • The HRID is being constructed from the HRID settings

  • Pad the number in the HRID Settings so length is 11

  • A new 035 field is created and populated with the value from 001

  • The 001 in the MARC21 record (bound for SRS) is replaced with this HRID.

Relevant FOLIO community documentation