Alma Glossary of Terms
- brandon dudley (Unlicensed)
Owned by brandon dudley (Unlicensed)
| Term | Definition | In III | In Voyager |
| Access rights | The area in Fulfillment configuration where permissions are granted to patrons that allow them to access digital and electronic resources. | Patron Blocks/PTYPE configuration | |
| Access rights checker | A plug‐in component that determines access rights and restrictions for a user regarding a particular resource. | Patron API | |
| Activation | The process of enabling access to e‐resources for patrons. Includes confirming that the library has access to the resource and setting up technical information so the public has access. | Activation (in SFX) | |
| Administrative/ consortial structure | The hierarchical structure of management within Alma. The levels are Consortium, Institution, and Library. | Central/Local (in INN-Reach); Branch/workstation; Locations Served table | |
| Aggregator package | A type of electronic collection that includes all titles (as opposed to a selective package, which includes only some of the collection’s titles). | Resource | |
| Alerts | Messages or warnings found throughout Alma that direct users to actions that need attention, for example: “Items already exist in the repository.” | Messages & Alerts | |
| Alma Link Resolver | Almaʹs fulfillment engine that responds to external requests with a menu of physical, electronic, and digital services. For physical resources, requests are offered; for electronic resources, context‐sensitive links are provided; for digital resources, direct links to the digital object are provided. The Alma Link Resolver responds to OpenURL requests as well as requests from systems such as Primo. | WebBridge product/SFX/Counter 360 | |
| Alma Menu | Lists all of the actions and areas that a user can work in depending on what role(s) they have been assigned. | Workflow | |
| Analytics | The tool used to manage data reports and the dashboard. | Statistics, Web Management Reports | |
| Analysis | The querying option within Analytics that allows a user to create a report. | Query | |
| Assignments | The tasks or records worked on by operators. Assignments can be the responsibility of the user who is logged in, of others, or they can be unassigned. Assignments may be changed if the appropriate permissions allow this. | Tasks | |
| Attachment | A file that is associated with an entity at the system level, is stored in the system, and can be accessed from the entity details. | n/a | |
| Audit Event | A logged action taken in the system. The event includes the user that took the action and the time the action was taken. | Transaction | |
| Auditing | Reviewing the actions taken on a record or entity. | n/a | |
| Available balance | The money that is available for use in an allocated fund. [Available balance] = [allocated amount] ‐ [encumbrances] ‐ [expenditures] | ||
| Boilerplate statement | The copyright statement presented to users depositing items. | n/a | |
| Brief Record | A bibliographic record that is identified as brief by an equation that considers the values of various fields of the record. For details, see Identifying brief records in the Alma Resource Management Guide. | Brief Record | |
| Campus | A collection of buildings that belongs to a given institution. Users may be affiliated with a specific campus where they can request library services. Libraries may be affiliated with a specific campus, which is where their physical inventory is expected to circulate. | Site | |
| Cash balance | The money that is currently in the fund/ledger. [Cash balance] = [allocated amount] ‐ [expenditures]. | ||
| Catalog | The catalog contains all descriptive metadata managed by a library, institution, consortium, or community. This may include private descriptive metadata for a library, institution, or consortium or may reference descriptive metadata contained in the Community Catalog. | WebPAC | |
| CKB | Central Knowledge Base within the Community Zone. | SFX KB | |
| CKB package | A collection of electronic portfolios (titles) made available from one provider. | Resource | |
| Cloud computing | The delivery of software and storage of data at a location (a server) remote from the physical location of the library, accessed by the internet. | Cloud Computing/Hoisted Services | |
| Collaborative Network (CN) | The overarching concept for all types of collaboration (for example, cataloging, acquisitions, fulfillment) between libraries and institutions. In Alma, it is used particularly when referring to a consortium model of collaboration. | Network | |
| Collection | An entity that groups any number and type of resources together as a database or package, allowing for enhanced organization of mixed‐type materials based on topic‐based hierarchical structures. | Resource | |
| Community Catalog (CC) | A catalog of bibliographic records in the Community Zone for the use of the Alma Community. Can be accessed by any institution that is part of Alma for cataloging purposes. For information on its scope, standards, policies, and merge logic, see Alma Community Catalog: Cataloging Standards, Policies, Rights, and Responsibilities. | Skyriver product/Inn-Reach product | |
| Community Zone (CZ) | The Alma Community Zone. Incorporates the Knowledge Base, a Community Bibliographic Catalog, and Global Authority Files. Can be accessed by any institution that is part of Alma for Acquisitions and Collection Development purposes. | n/a | |
| Context object | A metadata container that holds attributes pertaining to the OpenURL. | ||
| Context service | A container of potential services collected according to specific attributes. | ||
| Controlled Vocabulary (CV) | An organized set of pre‐defined, authorized terms. One example is the Library of Congress subject headings. | Controlled Vocabulary | |
| Copyright clearance | The process of getting permission to use copyrighted works. A digitization process may require performing copyright clearance. | Copyright Clearance | |
| Dashboard | The opening page of Alma after a user signs in. Its contents vary according to a user’s role. The dashboard may include reports, widgets, and a task list. | Dashboard (in Sierra) | |
| Database | Formerly, a collection whose resources cannot be individually managed through an interface. Currently, the term and its functions are being combined with those of “package” to allow for more flexibility in both functionalities. Eventually, “database” and “package” will be deprecated and “electronic collection” will cover both entities. | Resource | |
| Delivery | The process of taking a request for a digital item and enabling the user who requested it to view or access a copy. | n/a | |
| Delivery rules | Rules that determine how digital content is delivered to users and external systems. The rules are configurable by the customer. | n/a | |
| Department | An area in the library where dedicated physical inventory actions take place, such as receiving acquired physical material and digitizing physical material. | Department | |
| Deposit flow | The process of making digital material part of the institution’s permanent inventory. | n/a | |
| Descriptive Metadata (DMD) | Descriptive Metadata. Typically, DMD appears in records in the Metadata management system (MMS). | Descriptive Metadata | |
| Digital resource | A file or group of files with metadata that exists on a local network, a server, or cloud. It may include, among other possible formats, streaming media, e‐books, or .jpg images. Digital resource files can be stored and managed externally, but the metadata is always managed by Alma. The resource generally requires a viewer on the user’s machine. | Resource | |
| Digitization approval | The process of approving a digitization request. The process may include receiving copyright clearance from the proper agencies | n/a | |
| DLF Electronic Resource Management Initiative (DLF ERMI) | An industry‐wide, standardized solution developed by the Digital Library Federation. DLF ERMI handles the specifications and tools needed for managing the license agreements, related administrative information, and internal processes associated with collections of licensed electronic resources. | n/a | |
| Domain-normalized XML (DNX) | A normalized version of inventory‐related metadata that is not bibliographic (for example, material type for the Title/ Resource level or the policy, location, or barcode for the item level). | MetaData Builder record (not directly analogous) | |
| DNX representation | The complete record of the inventory in the DNX XML including the attributes contained in ORACLE tables. | n/a | |
| Document delivery | The supply of journal articles, chapters, and other digital items to individuals who make requests. | Document Delivery | |
| Drools | A business rules management system based on the JBOSS Rules engine. Drools are used for automated, rule‐based updates to metadata. | Rapid/Global update (not directly analogous) | |
| Electronic collection | A collection of electronic resources that can contain packages (which include portfolios) or databases (which include URLs). | Resource | |
| Electronic Data Exchange (EDX) | A file delivery method for the transfer of data by standard File Transfer Protocol (FTP) whereby OCLC provides an Electronic Data Exchange account into which OCLC posts bibliographic records and reports. | FTS | |
| Electronic resource | A digital object that is stored and managed externally from the local library or Institution Zone. | Resource | |
| Embedded order data (EOD) record | Vendor‐supplied fields that describe the library’s order for a resource. (Referred to as ʺembedded order confirmation recordʺ by some vendors.) Alma imports the EOD record, enters the description into the MMS, and turns the embedded order information into a PO line. | EDI record | |
| EOD import profile | A software component that takes fields from a source record and maps them to a normalized PO line structure. Each profile may have an EOD import syntax check associated with it. | EDIFACT, Electronic Invoice Processing | |
| Enhancement | A tool within the metadata editor that allows normalization rules to be applied and thus improves the quality of the record. | n/a | |
| Event | An action that involves at least one entity or agent in the system. Used for audit trail purposes. | n/a | |
| External system | An institution’s existing data management system that Alma may use as a source or target for information. Examples are a student information system or an ERP (enterprise resource planning system such as PeopleSoft). | III has no standard term for this. | |
| External user management | A model whereby an external system is treated as the authoritative source for user information. External user data is considered owned by the external system and is read‐only in Alma. | External Patron Verification | |
| Facets | Facets are used in search results lists to allow sorting and reduction of the results. For example, order lines may be filtered by fund, location, or digital format. | Facet/Limit By | |
| Form editor | A page that is accessible from the metadata editor and allows one to edit or add fixed fields. | Editor | |
| Fulfillment plan | A series of automated steps that facilitate making a requested resource available at the time and location that has been requested. See also Smart request. | III has no standard term for this | |
| Fulfillment unit (FU) | A number of shelving locations with similar fulfillment policies and blocks. | n/a | |
| Full text service | A service that provides the user with access to the full text of the e‐resource. | Full Text Service (SFX) | |
| Headings file | A file containing the collection of all the headings in all the bibliographic or authority records, with references to the records where they are used. Headings from bibliographic and authority records are managed separately, in different headings files. | Headings report | |
| ILL incoming (lending) request | See Resource sharing incoming (lending) request. | n/a | |
| ILL outgoing (borrowing) request | See Resource sharing outgoing (borrowing) request. | n/a | |
| Interface | In Alma, interfaces refer to vendor interfaces—that is, sites maintained by the vendor—only. | III has no standard term for this | |
| Institution Zone (IZ) | The area of the Metadata Management System comprising local institutional data such as locally managed bibliographic records, locally activated electronic portfolios, local physical holdings. Paired with the Community Zone, which contains globally shared data. | III does not make such a distinction. | |
| Institutions | A group of libraries managed together. For example, a university may be an Institution consisting of a main library, a science library, a business library, and several specialized libraries. | Branches | |
| Integration profile | A mechanism for integrating the import and export processes between Alma and an external system. | Load Table / Export Table | |
| Intellectual entity (IE) | A resource that is being managed and described in the Alma system. An IE may have one or more holdings or digital representations. | Vendor | |
| Internal user management | A model whereby the user information is managed wholly within Alma. | Patron database | |
| Inventory | The resources that are owned or licensed by or associated with a particular library, institution, or consortium. All descriptive bibliographic metadata resides in the Metadata management system (MMS) with appropriate links from the inventory to the corresponding descriptive information. | Items/Copies | |
| Invoiced but not paid balance | Invoices that have a “ready” status but have not been paid yet (based on the invoice status). | Amount Due | |
| Item | The inventory level of a resource for fulfillment and usage. Items may include bar codes and other identification details. | Item record | |
| Itemized set | A group of objects whose set members are determined at the time the set is saved. There is no stored relation between the set members and the query from which they were derived. The data in this set is static. See also Logical set. | Review File | |
| Job | A scheduled or on‐request process. | Cron Job/Automatic Process/task (in Task Builder) | |
| Library | The lowest level in the hierarchical structure of management within Alma, which is: Consortium, Institution, and Library. An institution can consist of a number of libraries—physical locations that are normally housed at a single building or in a couple of buildings in close proximity of one another, such as a Main Library, a Science Library, a Law Library, and so forth. A library has locations and circulation desks that are wellknown to the library patrons. | Branch | |
| Loan | An issue of a resource to a user (patron). Formerly referred to by some institutions as issue. | (Item) Check out | |
| License management | The management of a contract between the library and a vendor for the lease of one or more copyrighted bibliographic databases or online resources. This includes creating, updating, and deleting licenses. | License management | |
| Limited trial | An e‐resources trial type.This trial is limited to a group of defined trial participants. They are the only ones that have access to the resource during the trial. | Trial (not used by III) | |
| Local catalog | Materials managed locally within Resource Management | Catalog | |
| Location | A physical place where items are stored (for example, a shelving location). | Location | |
| Logical set | A group of records whose members are determined by a query. The set updates every time it is run based on the most current results of the query. See also Itemized set. | Saved Search | |
| Management tags | Can be set from within the metadata editor to suppress records from the discovery layer, to export to WorldCat, or to indicate that the record is brief. | Fixed-Length Fields (various) | |
| MARC record | A record conforming to machine readable cataloging (MARC). | MARC record | |
| Match method | The approach Alma uses to identify duplicate records. When a record is loaded into the Alma database, the system attempts to find a similar record based on the match method. | Match/Overlay (Load Profile) | |
| Material type | The type of material, such as a book or electronic journal package, from which an item takes its form. Note that the material type does not control the PO line workflow and can be modified when creating/editing a PO line. An item material type manifests itself in Primo’s Get It/Details tabs.Material types are system‐defined and cannot be configured through the Alma interface. | Material Type | |
| MD | Metadata | Metadata | |
| Metadata editor | The tool for editing and creating bibliographic and holdings records in Alma | Millennium/Sierra Editor | |
| Metadata form | A form used to fill in metadata information regarding a deposited object. May be used for a PO line description. | (Item/Bibliographic) Record template | |
| Metadata import profile | A metadata profile used for importing records. An import profile may store embedded or inventory data. | Load Profile/Load Table | |
| Metadata management system (MMS) | The interfaces, functions, and data that define institutional systems and allow them to manipulate their descriptive metadata. The MMS includes a Community Zone and a Library Zone. | ILS | |
| Metadata profile | A set of configuration parameters that define the applicable fields, subfields, indicators, fixed positions and their values (if needed) for a metadata schema. | MARC format validity table | |
| Metadata registry | The repository for information about all metadata schemas supported by Alma. It can include Marc 21 Bibliographic, Marc 21 Holdings, Marc 21 Authority, and Dublin Core. The registry is the basis for a variety of data services such as validation, normalization, and mapping. | n/a | |
| MMS Management Tags | Tags attached to each MMS record that define attributes to be used for further management of the record, such as exporting, publishing, and enhancing. | n/a | |
| Network Zone (NZ) | The area where shared data (such as catalog, licenses, and e‐resources) is managed and is required for certain Collaborative Network functionality.Can be accessed by any institution that is part of a cataloging or acquisitions network. Specific cases include shared catalog and joint acquisitions management. | INN-Reach Central Server/Skyriver system | |
| Non-bibliographic item | An item that is not classified as a bibliographic item but that needs to be managed by the system. Usually, this is a physical item (such as a computer) that is bought for the library. | III treats these as items | |
| Non-repository citations | Titles that are used for a course’s reading list, with no link to the institution’s inventory. These are typically faculty resources that are not part of the institution’s inventory. See To add a non‐repository citation: on page 239. | III requires course materials to have an Item/Bib record in the system | |
| Normalization rules | A set of rules that can be built and applied to bibliographic records in order to enhance the record. These rules may add fields, remove fields, or make changes to fields. The rules can be applied to an individual record, via bulk import and as part of the global update process | Load Table/Rapid or Global Update (not directly analogous) | |
| OCLC holding library code | Identifies a collection or campus under an OCLC symbol. | Holding Symbol | |
| OCLC symbol | A unique identifier assigned by OCLC to member and participating institutions. | Holding Symbol | |
| OpenURL | A type of Uniform Resource Locator (URL) that contains the address of an OpenURL Web site combined with the itemʹs identification. The OpenURL Web site serves as a resolver and finds the physical address of the item and returns it to the user’s browser. | OpenURL | |
| Organization unit | A library which can be configured for fulfillment and which controls the fulfillment unit collections under its control. | Site/Branch | |
| Out-of-the-box (OTB/OOTB) | The features, settings, and configurations that come with the installation of a product and are available as soon as the product has been installed. | Standard Configuration | |
| Package | Formerly, a collection of portfolios from a specific data provider. (Analogous to SFX KB target.) Currently, the term and its functions are being combined with those of “database” to allow for more flexibility in both functionalities. Eventually, “package” and “database” will be deprecated and “electronic collection” will cover both entities. | Resource | |
| Packaging | An automated method by which PO lines are passed through normalization and validations and are brought together into a purchase order, ready for approval. | Printing Purchase Order | |
| Patron digitization request | A request by a patron for the digitization of a resource. | n/a | |
| Patron Directory Service (PDS) | A back‐end Web component that facilitates user authentication and signing in to the system. PDS is part of the standard calling application package, but it is a distinct and separate component. It does not have a user database of its own. Rather, it is configured to work with the institution’s authentication server(s) and user database(s), such as an LDAP directory service. | PatronAPI/LDAP/SSO | |
| Patron services area | A portion of Alma used by library staff to perform fulfillment functionality (loans/transactions, requests) on behalf of a patron. | Circulation module | |
| Persistent search box | A drop‐down search box consisting of various search options. The persistent search box is always available from the top middle of any Alma page. | Search | |
| Plug-in | A software module that adds a specific feature or service to a larger system. | n/a | |
| Plug-in manager | An infrastructure component for installing and managing plug‐ins. | n/a | |
| Policies | Stipulations of a Terms of Use contract. | Resource License Use fields | |
| Policy type | Specifies the policy influence area (for example, due dates or fines). | Loan Rule Determiner table | |
| Portfolio (Inventory) | The specific coverage, services, and link information relevant for a particular title within a package. May include administrative/access information. May be local or global. Analogous to SFX KB Object Portfolio. | Object Portfolio (SFX) | |
| Privileges | The discrete permissions that make up a user role. For example, editing rights to metadata records. | Permissions | |
| Public trial | An e‐resource trial type. In the public trial, the resources are part of the library collection and are available to all end users.Trial feedback may be received from a predefined trial participant group and from general users. | Trial (not used by III) | |
| Publishing | A process that extracts and formats metadata for external uses, such as for discovery in Primo. | Export Data | |
| Purchase order line type | Also goes by PO line type and purchase type. Defines the type of inventory and continuity (one‐time or continuous) of the PO line. For more information, see the following table in the Alma Acquisitions Guide: Repository Search, Recommended Purchase Types, Workflow & Inventory on page 17. | Details in Purchase Order template | |
| Reading lists | List of resources (physical, digital, and/or electronic) and the applied workflows associated with them that are reserved for use for a specific course. | Course reserves list | |
| Receiving | The process of accepting physical items shipped to the library by vendors. | Receiving | |
| Remote storage | An off‐site storage facility. A location that is used to store physical library materials at a distance from the library. Remote storage facilities can be shared by a number of institutions and managed by a system other than the institutionʹs library system. | Remote Storage | |
| Reporting code | An attribute of a PO line or invoice line that codes a type of material within the ledger and fund system. For example: monograph, ejournal. This allows reporting on funds by attributes other than the funds hierarchy. | ||
| Requester | The user for whom a request is made. The request form can be filled out by the requesting user or by a staff user on behalf of the requester. | Requestor | |
| Resource request | A request to make a library resource available at a specific location for a specific purpose. The resource request may be triggered by a patron‐initiated request or by an internal library work order request, such as: o Moving items to reserves o Sending items out to the bindery o Sending items to digitization Resource requests vary in: o The requester type (patron, library, department) o The resource format (physical/digital) o The delivery method (move physical item to a location, send link to a digital resource, and so forth) | III does not have a term for this | |
| Resource sharing incoming (lending) request | A request placed by another institution’s patron and fulfilled by a resource of the local institution. | Lending request | |
| Resource sharing outgoing (borrowing) request | A request placed by local patron and fulfilled by another institution’s resource. | Borrowing request | |
| Resource sharing partner | An institution or a distinct external ILL system that participates in a resource sharing process, either as borrower or as lender. | Participating Site | |
| Role parameter | A role modifier or limiter. For example, a Circulation Desk Operator who is permitted to operate only at a specific Circulation Desk. | User/Permissions | |
| Rota list | A list of potential lending partners that are searched to fulfill the sharing request. The creation of this list is based on the configuration of rota templates. | n/a | |
| Selective full text service | A service that provides the user with access to selective portions of the e‐resource, rather than the full text of the eresource. | GetHoldings Service (SFX) | |
| Selective package | A type of electronic collection that includes only some of the collection’s titles (as opposed to an aggregator package, which includes all of the e‐collection’s titles). | Resource | |
| Service unit | A unit that provides services to other organizational units. It may have staff users, a physical (billing) address, departments, a circulation desk, funds, and other objects associated with it. | III does not have a term for this | |
| Services registry | A list of actions that may be performed on metadata records. Each action is a service, and services may be grouped together for bulk data updates. | Choose Command (Global Update) | |
| Set | A physical group of objects created in one of two ways, through an Itemized set or a Logical set. | Review file | |
| Set management | Activities performed by authorized staff users that involve creating and administering logical and itemized sets. | Create Lists function | |
| Set member | A bibliographic record or inventory item that belongs to an itemized set or the output of a logical set’s query. | Record | |
| SIP2 | A protocol from 3M that provides a standard interface between a library’s automated circulation system and library automation devices. | SIP2 | |
| Smart request | Patron requests for library materials that are satisfied by providing the most appropriate resources to a patron across resource types, locations, formats, and preferences. See also Fulfillment plan. | n/a | |
| Staff user | An individual who has permissions to work within Alma. | User | |
| Summary funds | Funds that are used for aggregate reporting on the subordinate (child) funds.They are not used for ordering or invoicing. | ||
| Synchronization | A process that ensures that data in Alma is updated, at relevant times, with the latest values from the owner of the data. | III does not have a term for this | |
| Task | An operation performed within Alma that moves the item along in its lifecyle, for example: approve a PO line. | III does not have a term for this | |
| Task chain | An ordered list of tasks. | III does not have a term for this | |
| Task list | A list of action items requiring a staff user to take some action on a resource in order to move it forward in its lifecycle. For example, a PO line may need to be manually approved before it can be automatically sent. | III does not have a term for this | |
| Terms of Use (TOU) | A list of predefined fulfillment policies that defines the institution/library commitment to the patron and under which the service will be provided or disconnected. (TOU can be referred to as the “contract” between the library and the patrons). | Loan Rule | |
| TOU type | Terms of Use that can be assigned to a specific type of a fulfillment activity (such as Loans). | Loan Rule | |
| Transaction | A financial activity that may impact the fund’s balance. | ||
| Transaction Entry | A component of a transaction header that affects the balance of a single fund. | ||
| Transaction Entry Type | The reason for a transaction entry that is changing a fund balance. A transaction entry type could be an allocation, an encumbrance, or an expenditure. | ||
| Transaction Header | An action with all its entries that makes up a complete business action, affecting the balances of one or more funds. | ||
| Transit Slip | A printed slip attached to a physical item that is placed in transit. The slip identifies the requested material and its destination. | Transit Slip | |
| Transit time | The time it takes for a physical item to make it from one location to another. | III does not have a term for this | |
| URD(2) | Universal Resource Discovery (and Delivery). The Ex Libris framework for end‐user services that focuses on search, delivery, and other library services. Offerings such as Primo are part of the URD2 framework. | n/a | |
| URL | Uniform Resource Locator. A path to a file stored on the Internet or on an internal network. | URL | |
| URM | Unified resource management. The Ex Libris resource management framework that allows libraries to optimize technical support, purchasing power, collections, and staff knowledge and resources. Alma is based on a URM framework. | n/a | |
| User | An individual who interacts in some way with the system. A user may be a staff member such as a Cataloger or Circulation Desk Operator or a patron interacting with resources through a discovery interface. | User/Patron | |
| User blocks | Flags on a user’s account that can prevent various fulfillment activities such as requests or loans. | Patron Block | |
| User management/ maintenance | An area of Alma designed for managing users and contacts. | Millennium/Sierra Administration | |
| User record | The collected information stored in Alma about a user. This user may be a student, an Alma operator, faculty, staff member, or organization. The record consists of a core set of information plus repeatable segments for such items as multiple addresses. | Patron record | |
| User registration | The process of defining a person as an authorized user of the system. Registration may be performed at the Circulation Desk, online using the user management system, or through user import options. | Patron record creation/User addition | |
| User role | A grouped set of rights assigned to an Alma user that grants privileges and tasks. Roles are based on expected workflows and job responsibilities in Alma. The rights bundled within individual roles (e.g., ʺLicensing Managerʺ) are not editable by individual institutions. However, a single user record may mix and match different roles to create the appropriate set of staff rights. | Permissions/Functions/User groups | |
| User role profiles | A predefined group of roles (including scopes) that may be attached to users in one action. | Workflow | |
| User segment | A repeatable section of the user record with grouped information. Examples are addresses, phone numbers, email addresses, notes, and blocks. | III does not have a term for this | |
| User-submitted job | A combination of a task chain and a set of resources that the task chain will run on, initiated by the user. | n/a | |
| Vendor account | A subset of the vendor; may contain business rules for specific types of data. For example, a rush account may contain contacts and instructions on how to handle this material. | Vendor record | |
| Versioning | Sequentially numbering committed updates to a record for the purposes of retrieval and rollback. This applies to MARC records in the metadata editor. | n/a | |
| Vocabulary | A specified list of terms developed by creators of catalogs and databases to ensure precise and comprehensive searching. The terms chosen may vary from database to database. In Alma, each vocabulary has its own code and name. | Vocabulary | |
| Widget | A small visual link found on the dashboard, which can be controlled by the operator. Examples include reports for graphs suitable for your area of interest, or access to a calendar, local weather, or a link to notifications. | Widget (Sierra) | |
| Work order | An internal library request to route physical materials for internal processing. A work order sends an item to a work order department (marking it as not available on the shelf), where it can be managed according to internal statuses. Both departments and statuses are configurable and can be used to manage tasks according to a library’s local needs. | n/a | |
| Z39.50 | A client–server protocol for searching and retrieving information from remote computer databases. | Z39.50 |