| instances | inventory | - Reference data
- MARC bib-to-Instance map (optional; if desired to change default marc-to-instance mapping for all MARC records)
- FOLIO baseurl/settings/inventory instances section (optional)
- FOLIO baseurl/settings/inventory/ Instance, 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:
- full location hierarchy (institutions/campuses/libraries/locations) (required)
- service points (required)
- FOLIO baseurl/settings/inventory Holdings section (optional)
- FOLIO baseurl/settings/inventory/ Instance, 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
- full location hierarchy (institutions/campuses/libraries/locations) (required)
- service points (required),
- loan-types (required),
- material-types (required),
- FOLIO baseurl/settings/inventory Items section
- FOLIO baseurl/settings/inventory/ Instance, holdings, items section statistical code types, statistical codes (optional)
- Data records: instances, holdings (both 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:
- groups (required)
- 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 |
|
| contacts (organizations) | organizations | - Reference data: categories (optional)
| 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:
- categories (optional),
- 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
| .users | users | - Reference data:
- groups (required)
- addresstypes (required)
| Schema: https://s3.amazonaws.com/foliodocs/api/mod-users/p/proxiesFor.html#proxiesfor_postSchema: https://github.com/folio-org/mod-user-import/blob/master/ramls/schemas/userdataimportjson | proxies | users | - Data records: users (required)
| |
| purchase orders | orders | - Reference data:
- full location hierarchy (institutions/campuses/libraries/locations)
- service points (required), addresses
- Data records:
- instances (optional)
- organizations (vendors) (required)
- finance structure (Ledgers, FY, Funds, Budgets required, Fund groups and expense classes optional)
- acquisitions 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 |
|