| instances | inventory | - Reference data
- MARC bib-to-Instance map (optional; if desired to change default marc-to-instance mapping for all MARC records)
- settings/inventory instances section (optional)
- settings/inventory/ Instanceinstances, holdings, items section statistical code types, statistical codes (optional)
| https://github.com/folio-org/mod-source-record-manager/blob/master/mod-source-record-manager-server/src/main/resources/rules/rules.json | 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 | - Reference data:
- settings/tenant-settings/location-institutions (required)
- settings/tenant-settings/location-campuses (required)
- settings/tenant-settings/location-libraries (required)
- settings/tenant-settings/servicePoints (required)
- settings/inventory Holdings section (optional)
- settings/inventory/ Instanceinstances, holdings, items section statistical code types, statistical codes (optional)
- Data records
| | 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 | - Reference data
- settings/tenant-settings/location-institutions (required)
settings/tenant-settings/location-campuses (required)- settings/tenant-settings/location-libraries (required)
- settings/tenant-settings/servicePoints (required)
- settings/inventory/loantypes (required),
- settings/inventory/materialtypes (required),
- settings/inventory Items section (optional)
- settings/inventory/ Instanceinstances, holdings, items section statistical code types, statistical codes (optional)
- Data records:
- instances (required)
- holdings and their prerequisites (required)
| 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 | - Reference data:
- settings/users/groups (required)
- settings/users/addresstypes (required)
| Schema: https://github.com/folio-org/mod-user-import/blob/master/ramls/schemas/userdataimport.json |
|
| proxies | users | - Data records: users (required)
| Schema: https://s3.amazonaws.com/foliodocs/api/mod-users/p/proxiesFor.html#proxiesfor_post |
|
| loans |
| - Reference data:
- settings/tenant-settings/servicePoints
- settings/calendar
- settings/circulation/loan policies
- settings/circulation/request policies
- settings/circulation/notices policies
- settings/circulation/overdue fine policies
- settings/circulation/lost item fee policies
- settings/circulation/patron-notices
- settings/circulation/rules
- Data records:
- users and their prerequisites (required)
- instanceinstances, holdings, items and their prerequisites (required)
|
| 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 | - Data records:
- instances, holdings, items and their prerequisites (required)
- users and their prerequisites (required)
- instance, holdings, items loans and their prerequisites (required)
| https://s3.amazonaws.com/foliodocs/api/mod-circulation/p/circulation.html#circulation_requests_post https://s3.amazonaws.com/foliodocs/api/mod-circulation-storage/p/request-storage.html#request_storage_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 |
| - Reference records:
- settings/users/owners
- settings/users/feefinestable
- Data records:
- users and their prerequisites (required)
- instanceinstances, holdings, items and their prerequisites (required)
|
| The settings/users/owners and
settings/users/feefinestable must be setup set up if the institution chooses to migrate existing fees/fines as "not automatic". |
| contacts (organizations) | organizations |
| Schema: https://s3.amazonaws.com/foliodocs/api/mod-organizations-storage/p/contact.html#organizations_storage_contacts_post | - urls in the contact record must begin with 'http://' or 'https://', otherwise the record will be rejected as invalid.
|
| organizations | organizations | - Reference data:
- settings/organizations/category (optional),
- Data records: contacts (optional)
| Schema: https://s3.amazonaws.com/foliodocs/api/mod-organizations-storage/p/category.html#organizations_storage_categories_post | - urls in the organizations record must begin with 'http://' or 'https://', otherwise the record will be rejected as invalid.
|
| purchase orders | orders | - Reference data:
- settings/tenant-settings/location-institutions (required)
- settings/tenant-settings/location-campuses (required)
- settings/tenant-settings/location-libraries (required)
- settings/tenant-settings/servicePoints (required)
- Data records:
- instances (optional)
- organizations (vendors) (required)
- finance structure (Ledgers, FY, Funds, Budgets required, Fund groups and expense classes optional)
- settings/acquisition-units required if orders/financials must be separated/permissioned differently for different users within the same tenant
| Schema: https://s3.amazonaws.com/foliodocs/api/mod-orders/p/order.html#orders_composite_orders_post |
|