Term or Acronym | Description |
Accounting code | A reference number used to identify a vendor in an external payment system. |
Acquisition unit | An additional layer you can add to acquisitions records that restricts a user’s ability to interact with those records unless they have been assigned to that unit. For example, you may create acquisition units to represent the different libraries within your library system. Units are defined and determined by your library in the Settings app. |
Allocated fund | A fund that has been assigned a monetary value for the fiscal year and therefore has money to spend. |
Availability | The status of an item in terms of circulation (for example, available; recently returned). In FOLIO, "Item Status" displays availability. |
Batch group | Invoices grouped together for export to an external accounts payable system. Invoices from the same library are generally processed together, as determined by the batch group assignment on each invoice. |
Bound-with | Multiple, separate bibliographic titles that are bound together in a single volume, most frequently by a former owner but also sometimes by a publisher and for other reasons. |
Budget | A finance record that describes the amount of money available for a fiscal year within a fund that includes a definition of the allowed expenditure percentage and allowed encumbrance percentage. Transfers and allocations transactions are performed against a budget. Expense classes can be assigned to a budget. |
Bug | An error, fault or flaw in a software system. |
Campus | The second level of the four level location structure (Institution -> Campus -> Library -> Location). The structure is hierarchical - a campus must be linked to one institution, and a library must be linked to one campus. |
Child record | Associated with linking bound-withs, which allows for "links" between separate bibliographic records and/or a bibliographic record and items belonging to another bibliographic record. Child recordsare those associated bibliographic records. |
CQL | Contextual Query Language. A formal language for representing queries to Information Retrieval systems such as web indexes, bibliographic catalogues and museum collection information. |
CRUD | Create, Read, Update, Delete. The basic actions that can be taken on a record in a software system. |
Department | Organizations at a library’s institution of which patrons and staff may be a part, for example, Campus Facilities or Chemical Engineering. |
Discovery display name | The name of a service point to be displayed to patrons in a discovery layer, if needed. |
Effective call number (item), eye readable | A way of presenting the call number that may be easier for a human being to read. |
Effective call number (item), normalized | A standardized way of presenting the call number that may be harder for a human being to read, but easier for a machine to process. |
Expense class | A fiscal entity used to track transactions against a specific purpose or function within a Fund. |
Item effective location | 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 on what values are set. |
eHoldings | Contains information such as the resource’s URL, call number, etc to enable staff to locate and manage library electronic holdings. |
Encumbrance | An amount of money that the library commits to pay to a vendor from a fund budget for ordered materials that will be invoiced in the future. |
ERM | Electronic Resource Management. ERM is used within the FOLIO community to describe functions that manage the acquisition, licensing, access, maintenance, usage, retention, and de-selection of electronic resources. |
eUsage | App that tracks statistics for access and use of electronic resources. |
Expiration date (patron blocks) | The date at which the patron block is removed from the patron record, and the blocked privileges are restored to their user account. |
Expiration date (user record) | The amount of time set before the user record lapses and the user no longer has active permissions or has ability to borrow items |
Fee/fine | Charges attached to patron records for reasons such as damaged materials, late item returns, or rental fees. |
Fiscal year | The twelve-month period a library uses to manage its finances. |
FOLIO | Future of Libraries is Open. An open-source collaboration of libraries, developers and vendors building an open source library services platform. It supports traditional resource management functionality and can be extended into other institutional areas. |
Fund | A fiscal entity used to track transactions against a general purpose or function' within a ledger. Funds are associated with only one ledger. Fund information persists from year to year as new budgets are created for the fund each year. |
FYRO | Fiscal year roll-over. After ordering and invoice processing is completed for the fiscal year, a library performs fiscal year roll-over processes to open new fiscal year budgets, close budgets from the prior fiscal year, and create encumbrance transactions in the new fiscal year. |
Group | A collection of one or more funds grouped together. A group can bring multiple funds together regardless of fiscal year and ledger which enables the total amount of money available or allocated across multiple funds to be analyzed. |
Hidden permission | A permission that you do not see in the list of permissions to assign to users. Hidden permissions are generally very granular permissions that are bundled together in larger permissions sets that are then made viewable to assign to users. |
Holdings | A data record that contains information such as location, call number, and volumes owned, to enable staff to locate and manage library holdings. Holdings records may describe library holdings that are physical, electronic, or other formats. |
Identifier | A unique label of a record, such as an ISBN, ASIN, or OCLC number. |
ILS | Integrated Library System. A centralized system where you do most or all of major library transactions such as cataloging, circulation, electronic resource management, etc. |
In-app report | A specific report or reporting function that has been developed as an added feature in a FOLIO app, rather than via an external reporting tool that an institution may be using. |
Instance | A bibliographic record. Contains bibliographic and administrative information about a particular title or item; are mostly derived from full bibliographic records (in MARC or other formats) and are intended to provide information for library staff to identify and select records in order to perform work on associated holdings and items. |
Institution | In FOLIO, an Institution is the top level of the four-level location structure (Institution -> Campus -> Library -> Location). |
Invoice | A list of the payments due for materials ordered by a library from a vendor. |
Invoice line | The individual line items being paid for within each invoice. Each line consists of a description of the materials being paid for, the costs incurred, and a vendor reference number. Invoices are primarily a sum of the information from these lines. |
ISBN | International Standard Book Number: global unique identifier for a book. |
ISBN, normalized | International Standard Book Number, in a standard form without spaces or hyphens. |
ISSN | International Standard Serial Number. A global unique identifier for a serial. |
Item | A data record representing a single item. Contains information needed to identify and track a single item or piece, such as barcode, availability, and material type. |
Item HRID | Human readable ID. A FOLIO generated or migrated ID for the Item record. |
Item status | A field that currently reflects item availability, and in future development will also reflect information about an item's staff processing, and needs for future use. |
KB | Knowledge base. A self-serve web-based library of information about a product, topic, etc. |
LDP | Library Data Platform. A project that develops an open-source analytics platform (https://github.com/library-data-platform ) which can be utilized by FOLIO reporting (https://github.com/folio-org/folio-analytics ) for statistical and operational analytics. The term, "LDP," is sometimes also used as a shorthand for a specific component of the platform, such as the LDP database or the LDP query builder app which runs in FOLIO. |
Ledger | A collection of funds that need to be kept fiscally separate from another ledger’s collection of funds. All funds within a ledger share future fiscal year rollover behavior. Each fund record is assigned to only one ledger. |
Library | The third level of the four-level location structure (Institution -> Campus -> Library -> Location). The structure is hierarchical - a library must be linked to one campus, and a location must be linked to a library. A library may have more than one location. |
Loan type | An optional element in FOLIO circulation rules. Items must have a permanent loan type and 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. |
Location | The fourth level of the four-level location structure (Institution -> Campus -> Library -> Location). Locations are used in functionality including item routing, fees and fines, and remote storage configuration. Items may also have an “effective location” value that is used in circulation. |
LSP | Library Services Platform. The next generation of library automation systems that extend and improve upon the functions of the ILS (integrated library system). The term was coined by Marshall Breeding in 2011. |
Material type | A required field on the item record, used as an optional element in FOLIO circulation rules. The field is intended to describe the material nature of a specific item, with the intention to permit more specific information than resource type alone. |
Metadb | The open-source analytics platform used in LDP (Library Data Platform), introduced at CNI Fall 2020. |
MM | Metadata Management. MM is used within the FOLIO community to describe essential bibliographic management functions, such as creating, editing, suppressing, deleting, importing, exporting, replacing, overlaying, and reporting. |
Mode of issuance | The abstract form of the resource (eg., monograph, subunit). |
Net transfers | Money transferred between funds during a fiscal year. |
Order | A purchase order featuring a list of titles or packages (physical or electronic) being ordered by a library from a vendor. |
Organization | Any institution with whom your library interacts (this may or may not be an institution from whom you purchase materials). |
Package (in Orders) | A purchase order that represents the acquisition of multiple titles. |
Parent record | The main link in a bound-with situation: It will have an item record (and thus barcode) that all other bibliographic records associated with a given bound-with volume can link to. Child records are those associated bibliographic records. Child records will have LKR fields in the bibliographic record that include the ADM number of the parent record and "Enum. Level.1" information found in the parent record's item record. Doing this allows all item record information in the parent record to display in the child record, so the same barcode, sublibrary, collection, description, call number, etc. will show up for all titles in a bound-with. |
Patron blocks | Optional limits that libraries can impose on patron circulation privileges, removing privileges when the limits are exceeded. For example, a library can say that if a patron has five lost items, they can no longer borrow books until that number is reduced to four lost items or fewer. |
Patron groups | Types or classes of library users. |
Permission | Value granted to a FOLIO user that allows them access to view, create, update or delete records in FOLIO, or to carry out specific FOLIO tasks. |
Permission set | A group of permissions that allows a user to perform a specific set of tasks. |
Persona | A detailed biography of a fictitious user of a software product. A software design team creates a persona for each category it deems important to serve. |
Piece | A subsection of a receiving title that is expected to be received. For example, if the ordered title is a journal subscription, then a piece of that title could be volume one of the journal. |
POL | Purchase Order Line. A purchase order line contains one of the titles or packages being ordered by the library. Orders can contain multiple order lines. |
Proxy | A person who is authorized (by a sponsor) to act on their behalf to checkout, renew, recall, etc. |
Query search | Criteria or elements included in a data request from a system or dB. |
QuickMARC | An editor for MARC records that opens from the Inventory app to edit specific MARC records. |
RA | Resource Access. RA is used within the FOLIO community to describe functions that allow libraries to circulate and provide access to materials and support patron service needs. |
Receiving | The management of information about ordered materials that have arrived at a library by delivery from a vendor. Also known as serials check-in and arriving. |
Resource type | Defined by RDA vocabulary list, rdacontent. |
RM | Resource Management. RM is used within the FOLIO community to describe a category of acquisitions functions which include Finance/Budgets, Organizations/Vendors, Orders, Invoices, and Electronic Resource Management. |
Service point | A service point in FOLIO is a setting that libraries configure to support circulation functions. Every FOLIO item must have a location, and every location must have an attached service point. You must set up at least one service point to be able to check items in and out; allow patrons to request items; charge and collect fines; and put items in transit between locations at your library. |
Shelving lag time | Locally determined time-frame between the return of material and the time it should be reshelved. This functionality is not yet in place for the Honeysuckle version of FOLIO. |
SIG | Special Interest Group. A SIG consists of a group of subject-matter experts that are interested in contributing to a specific functional area of the FOLIO platform. |
Sponsor | A person who authorizes another person to do something on his or her behalf, i.e., checkout, renew, recall, etc. |
SRS | Source Record Storage. A storage layer in FOLIO. 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. |
Tag | A label applied to a FOLIO record that allows for cross-app faceting, filtering, record batching and reporting. |
Tenant | A client in FOLIO whose data are stored separately and are accessible and visible separately from other clients. FOLIO installations may be “single-tenant” or “multi-tenant” depending on how their hosting environment is configured. A client is typically a library or a branch library. Each tenant uses its own set of deployed modules. |
Token | A value in a notice used to dynamically fill content in a notice when it is sent. For example, if a notice template includes the token {{item.title}}, when the notice is generated, {{item.title}} will be replaced by the title of the item to which the notice is referring. |
User | Any person who interacts with or performs tasks in FOLIO. |
UM | User Management. UM is used within the FOLIO community to describe practices at libraries for managing patron and staff records, including permissions to the FOLIO system itself. |
Vendor | Any institution from whom your library purchases materials or services. |
Visible permission | One that you can see in the list of permissions in the UI. They can be assigned to users directly or used to create groups of permissions called permission sets that can be assigned to users directly. |
Voucher | A record generated to transmit information to the Accounts Payable system which is needed to make payment on an invoice. |
Page Comparison
General
Content
Integrations