| instances | inventory | - reference data: instance-types (required if loading through Data Import), formats (optional)Reference data
- MARC bib-to-Instance map (
required if storing MARC records in SRS)
| instance-storage/instances | - 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 Reference data:
- full location hierarchy (institutions/campuses/libraries/locations)
and - (required)
- service points (required)
, call-number-types (required), holdings-types (required), holdings-type-notes (optional).- FOLIO baseurl/settings/inventory Holdings section (optional)
- FOLIO baseurl/settings/inventory/ Instance, holdings, items section statistical code types, statistical codes (optional)
- Data records
| holdings-storage/holdings |
| | 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 Reference data:
- full location hierarchy (institutions/campuses/libraries/locations)
and - (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
-- (optional)- - other data Data records: instances, holdings (both required)
| item-storage/items | 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 |
| contacts (organizations) | organizations | - reference Reference data: categories (optional)
| organizations-storage/contacts | 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)
| organizations-storage/categories | 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)
| user-import | https://github.com/folio-org/mod-user-import/blob/master/ramls/schemas/userdataimport.json | - as of 202001, latest commit to this repository was made in 201801. The schema is out of date with the user schema, so the local tenant may wish to use the user schema and endpoints instead.
|
| proxies | users | - other data records: users (required)
| proxiesfor | https://s3.amazonaws.com/foliodocs/api/mod-users/p/proxiesFor.html#proxiesfor_post |
|
| purchase orders | orders | - reference data: full location hierarchy (institutions/campuses/libraries/locations) and service points (required), addresses
- other data records: instances (optional), organizations (vendors) (required)
- finance structure (Ledgers, FY, Funds, Budgets required, Fund groups optional)
- acquisitions units required if orders/financials must be separated/permissioned differently for different users within the same tenant
| orders/composite-orders | https://s3.amazonaws.com/foliodocs/api/mod-orders/p/order.html#orders_composite_orders_post |
|