The migration process#
In order to perform migrations according to this process, you need the following:
Python 3.10 or later
An Installation of FOLIO Migration Tools. See the Installing page for information.
A repo created from the template repository migration_repo_template
A FOLIO tenant running Ramsons or later
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:
Result files#
The following table outlines the result records and their use and role
File |
Content |
Use for |
|---|---|---|
folio_holdings_<transformer_task_name>.json |
FOLIO Holdings records in json format. One per row in the file |
To be loaded into FOLIO using the batch APIs |
folio_instances_<transformer_task_name>.json |
FOLIO Instance records in json format. One per row in the file |
To be loaded into FOLIO using the batch APIs |
folio_items_<transformer_task_name>.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 |
instances_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 |
data_issues_log_<transformer_task_name>.tsv |
A TSV file with errors and data issues together with the row number or id for the source record |
To be used in fixing of data issues |
report_<transformer_task_name>.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 |
folio_marc_instances_<transformer_task_name>.mrc |
A MARC dump of the bib records, with the proper 999$i fields added |
For loading MARC records for instances . |
HRID handling#
Current implementation#
Previous versions of the migration tools pre-populated HRIDs for instances when transforming to acommodate requirements for creating SRS JSON records. The current process for transforming MARC bibs does not require setting the HRID of the instance record. The value will be set by FOLIO when the instances are posted and in the SRS records created by Data Import when loading the corresponding MARC data.
Note
If you set hridHandling to "preserve001", the 001 of the source MARC record will be used as the instance HRID value.
Legacy implementation (deprecated):#
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.