...
This is not intended to be a complete introduction to reference data. It is aimed at providing a list of reference data decisions that should be made prior to migration and documenting the order in which records should be migrated from legacy systems. Also, because this list is based on Texas A&M University's (TAMU) migration, it is not exhaustive, because as TAMU did not migrate all possible record types from its previous system.
...
Data record | Application | Prerequisite reference data or other data records (settings/... entries are relative to FOLIO baseurl) | Schema or other documentation | Notes |
|---|---|---|---|---|
| instances | inventory |
|
| Institutions may wish to identify records with statistical codes for a variety of reasons. Example: grouping records supplied by a given ebook vendor. |
| holdings | inventory |
| Institutions may wish to identify records with statistical codes for a variety of reasons. Example: grouping records supplied by a given ebook vendor. | |
| items | inventory |
| Schema: https://s3.amazonaws.com/foliodocs/api/mod-inventory-storage/p/item-storage.html#item_storage_items_post | Institutions may wish to identify records with statistical codes for a variety of reasons. Example: recording multiple item statuses from a previous system |
| users | users |
| Schema: https://github.com/folio-org/mod-user-import/blob/master/ramls/schemas/userdataimport.json | |
| proxies | users |
| Schema: https://s3.amazonaws.com/foliodocs/api/mod-users/p/proxiesFor.html#proxiesfor_post | |
| loans |
| For migration purposes, calendar begin and end dates must include the earliest loan to be migrated and the latest possible due date based on loan policy. Also for migration, institutions may choose to use storage endpoints or business logic endpoints to migrate loans. See Considerations for migrating loans for a comparison and contrast of these approaches and links to the relevant schema definitions. | ||
| requests (recall/hold/page) | requests |
| https://s3.amazonaws.com/foliodocs/api/mod-circulation/p/circulation.html#circulation_requests_post | Institutions have differed in their approach to migrating requests, some choosing to use business logic modules and others choosing storage modules. Both schema urls are listed for that reason. |
| fees and fines |
| https://s3.amazonaws.com/foliodocs/api/mod-feesfines/p/accounts.html#accounts_post https://s3.amazonaws.com/foliodocs/api/mod-feesfines/p/feefineactions.html#feefineactions_post |
| |
| contacts (organizations) | organizations | Schema: https://s3.amazonaws.com/foliodocs/api/mod-organizations-storage/p/contact.html#organizations_storage_contacts_post |
| |
| organizations | organizations |
| Schema: https://s3.amazonaws.com/foliodocs/api/mod-organizations-storage/p/category.html#organizations_storage_categories_post |
|
| purchase orders | orders |
| Schema: https://s3.amazonaws.com/foliodocs/api/mod-orders/p/order.html#orders_composite_orders_post | |
| pieces | receiving |
| https://s3.amazonaws.com/foliodocs/api/mod-orders/p/pieces.html#orders_pieces_post | "Pieces" records may be created to contain loose issues that have been checked in but not yet bound and therefore lack an item record in inventory. The piece record requires a uuid link to the titleId that appears in the po line, but that uuid doesn't exist until the purchase order and its lines are POSTed to the /orders/composite-orders endpoint, so it's necessary to post the order po lines and get the title ids before creating the piece records. As an alternative to creating piece records, some institutions have chosen to update the "receivingHistory" data element in the inventory holdings record to contain information about loose issues. |
...