Importing/overlaying bib records in FOLIO
Import & overlay options
Data Import (preferred) | Single-record import in Inventory | Push from Connexion (not recommended) | |
---|---|---|---|
Carries over local Connexion edits? | Only imports the OCLC master record. | ||
Allows overlay? | |||
Auto-generates holdings/items? | Can be fully customized for different types of cataloging. | Yes, but generic; must be edited after. Use macros, copy/paste text strings, etc., instead of typing in values to reduce errors. | |
Multiple records at once? | |||
Process | Prepare the MARC file
The first time you export in your Connexion session, you'll be asked to choose a file location; subsequent exports continue to use this same location instead of asking you. Additionally, if you do not change the file extension after each export, Connexion will add records to that same .dat file instead of creating a new one. For best results, just delete your .mrc file after each import! Import into FOLIO
| In Connexion
In Inventory
| In Connexion
In Inventory
|
Notes | This method can be used both to import new or overlay on existing instance records, regardless of whether they are source MARC or FOLIO. Set up on your desktop and in Connexion
| The list of target job profiles you can select from accommodate the following scenarios:
| Set up in Connexion
|
949 field mapping
Using a 949 field in an imported MARC to populate values in FOLIO is only an option when using Data Import.
This configuration is a change from the initial practice of using 947, 948, and 949 fields for instance / holdings / item data respectively. As of the Poppy release installed in March 2024, Data Import cannot accommodate multiple 9XX fields related to one singe instance. (The Poppy release included new functionality to create multiple holdings/items – but data for each one must have its own 9XX field.)
949 subfield | FOLIO record / field | Must be included in your 949? | Default value supplied by job profile | Other commonly used values (See all available values in the holdings or item record edit screen for the field) |
---|---|---|---|---|
$a | Instance HRID | If overlaying | ||
$b | Instance OCLC number | Not an option as of March 2024; reserving this for expected updates to functionality. | ||
$c | Order POL number | For Acquisitions workflows only | ||
$d | Order vendor reference number | For Acquisitions workflows only | ||
$e | Holdings type | Optional | Default |
|
$f | Holdings permanent location | See Location chart for codes | ||
$g | Holdings temporary location | Optional | ||
$h | Holdings copy number | Optional | 1 | |
$j | Holdings call number type | Optional | Library of Congress classification | |
$k | Holdings e-access relationship type (for 856, if present) | Optional | Resource | |
$m | Item material type | Optional | Printed Material |
|
$n | Item copy number | Optional | 1 | |
$p | Item volume info | Optional | ||
$q | Item permanent loan type | Optional | Can Circulate |
|
$r | Item temporary loan type | Optional |
| |
$s | Item permanent location | Optional | Inherits from the holdings permanent location unless otherwise specified. | |
$t | Item temporary location | Optional | ||
$u | Item status | Optional | In process |
|
$v | Item call number type | Optional | Library of Congress classification |
|
$w | Item workstat | See the workstats formatting page for details |
ǂa HRID ǂb OCLC# ǂc POL# ǂd VRN ǂe Holdings type ǂf Holdings perm loc ǂg Holdings temp loc ǂh Holdings copy # ǂj Holdings call # type ǂk Holdings 856 rel type ǂm Item mat type ǂn Item copy # ǂp Item vol info ǂq Item perm loan type ǂr Item temp loan type ǂs Item perm loc ǂt Item temp loc ǂu Item status ǂv Item call # type ǂw Item workstat
This template is also available in our Connexion online save file for constant data, titled 949 template March 2024.