|Availability||On the item record - may describe information about where an item is (available; recently returned) or if it can be circulated. As of Q12020 labeled as "Item Status"|
Container records hold multiple Instance, Holdings, and/or Item records and serve as virtual containers.
The container represent an additional level of hierarchy and associate data that may not have bibliographic associations. The container is not yet implemented as of 3/27/2020.
|Effective call number||The string that displays in apps other than Inventory as "call number." This is stored at the Item level and takes data from either the holdings or the item record call number field. The effective call number includes the prefix, call number, suffix, and copy number.|
|Effective location||This is currently an item-level property. FOLIO has permanent and temporary location fields on the Holdings and Items records. There is built-in logic for FOLIO to compute the item's "effective location" based off of what values are set. See Effective Location Logic in the Resource Access wiki for more details.|
|Holdings||The Holdings record contains data about the materials held, such as location and call number. A Holdings record must be associated with an Instance record.|
The Instance record is what is known the bibliographic record (or bib record, for short).
The use of the terminology is inspired by the BibFrame universe (Instance, holdings, and items).
|Inventory||Inventory is the FOLIO app that stores bibliographic, holdings, and item data in the form of Instance, Holdings, Item, and Container (not yet implemented) records. Instance records may be created within FOLIO or generated from records in source record storage (SRS).|
|Item||The Item record contains data specific to a single volume or piece, such as barcode and circulation status. An Item record must be associated with a Holdings record.|
Item Status is a field that reflects information about an item's availability, staff processing, and needs for future use.
See Item State in FOLIO for a discussion of the three-part item state structure - which is currently in development.
|Loan type||Loan type is a field on the item record that can be used as an element in FOLIO circulation rules|
Items must have a permanent loan type. They can also have a temporary loan type. If an item has a temporary loan type set, that is the loan type that would be matched on in circulation rules.
|MARCcat||MARCcat is a FOLIO app for editing MARC bibliographic and authority data.|
|Move||A record is moved when it|
|Needed For||On the item record; Allows libraries to assign a path for an item to follow when it is needed for specific things. These may be for staff needs, or for patron needs. Needed For might include Requests; Course Reserves; Binding; etc. As of Q12020 not yet implemented. See Item State in FOLIO for more information.|
|Process||On the item record; Describes a staff process that an item is in. Processes might include Digitization; Repair; Cataloging; etc. As of Q12020 not yet implemented. See Item State in FOLIO for more information.|
|SRS||Source Record Storage. If an instance has an underlying MARC record, then this record is stored in SRS. The underlying MARC record is also named the source of truth.|
|View source||View source means view the underlying bibliographic record, from which the instance record origins. View source can point to a MARC record in SRS internally in FOLIO, or direct outside of FOLIO if the library use a union catalogue as source of truth (e.g. LIBRIS and K10Plus).|