DocStore and Editor Terms and Definitions
Chapter 5. Appendix

Term

Definition

Bibliographic Record

An OLE document that describes a bibliographic entity as published.  OLE will initially support two kinds of bibliographic records: (1) Those in the USMARC bibliographic formats, and (2) Dublin Core records.

Synonym: Bibliographic Description

Bound-with

A physical object where two or more titles are joined together under one cover.  The object is represented in a system as a single item which links to more than one bibliographic record.

[Element] Classification

The set of data elements within the OLE Instance Schema that, taken together, make up the “call number” and state what classification/call number system (e.g., Library of Congress, Superintendent of Documents, and Dewey Decimal) the call number conforms to.  

Code

An individual Code within a Code List.  A Code within a table of Codes will have the attribute, Display Value.  See also Display Value.

Code List

A list of valid values for a particular data element within OLE.  For example, there will be a Code List for Locations; a user cannot assign a Location value within an Item unless it is part of the library’s Location Code List (which might be shown in an OLE editor in the form of a pull-down menu).  Ideally, the user could not assign the Code for a Location unless the user were authorized to assign that particular Code (in which case the OLE editor should show the user a pull-down menu of Locations that included only those Locations that the user is allowed to use).

Copy

A single specimen of an intellectual entity, e.g., a library can have one (or more) Copies of a multivolume set.  A single subscription to a journal may also be known as a Copy.  A multi-part book (or a serial subscription) is a Copy with as many Items as there are volumes.

Display Value

An attribute of a Code that specifies an alternate display value for the Code within a particular interface.  For example, the code “REGENSTEIN” might have Display Value “Regenstein Library.”  The display value could appear in places within the OLE user interface, but could also be used by an external Discovery Tool.

DocStore

OLE architecture for structured and unstructured metadata (e.g., bib, item, holding, authority, licenses) that works in conjunction with linked transactional data in OLE RDBMS/relational tables (e.g., purchasing, circulation, users, financial, borrowers).

Hide Record

To mark a record (bibliographic, holdings, item) so that is does not display in a public-facing service.

Holdings

Describes the extent of a resource available to the user.  In the case of continuing resources holdings data may record the pattern of issuance of a resource and/or a summary statement of volumes held.

Import Process

Batch process for importing bibliographic and/or authority records, as well as accompanying holdings and/or purchase order information

Item

The smallest unit of a resource that is managed and/or circulated individually.  It provides specific information about the physical location when pertinent.

Location

An element in a library’s system configuration that describes a conceptual entity or institution (e.g., “The University of X Library”) or a building (“John Doe Memorial Library”) or an area “Doe Library, Book stacks”; “Doe Library, Circulation Desk”) where items are shelved or work is performed.  All library items are assigned to a Shelving Location and this becomes an attribute for circulation policy.  Locations may also refer to library staff work areas at which certain functions (e.g., acquisitions (or ordering and receiving), cataloging, serials receiving, course reserve or circulation are the standard ones) are performed on or with items housed at Shelving Locations; work areas (e.g., circulation location) are identified as part of an operator’s login.

Location Code

A Code value from a Code List that describes, with a greater or lesser degree of specificity, the Location where an Item is located.

Match Point

A data element used to determine that a bibliographic record or authority record in a file of records being imported matches an existing record within OLE, such that the incoming record “overlays” and replaces the existing record completely or in part.  

OLE Holding

This section of the OLE Instance records "general" holdings information in a format specific to OLE.

OLE Instance

OLE XML document type that describes individual Holdings and Items

OLE Source Holding

This section of the OLE Instance represents "specific" holdings information entered according to some standard external to OLE. Examples are MARC holdings, MODS holdings or any other format specific holdings.

Ownership

The idea that permissions or policies based on a piece of data in a document (bib control numbers, item location, and ownership field data) could be used to infer ownership, in conjunction with policies. Work Units or Roles would be connected or allowed to complete certain actions based on additional qualifier for ownership.

Public-facing Service

Any service/system that allows public users to query a library’s database.  Examples include discovery layers (such as VuFind) and Z39.50.

Role or Group Qualifier/

Parameter

OLE Roles or Groups will be extended to include optional qualifiers or parameters on applied permissions. A Role or Group can continue with no qualifiers, or multiple.

Work Unit

A location, departmental, or organizational field, used to as an attribute or match point between documents and Roles/Permissions. The Work Unit will be compared between a Document and as a qualifier on a Role, in order for Permissions/Policy to designate what staff can perform which actions on a document. Work units can be designated with parent-child relationships, to allow easier creation of roles/permissions across work units (one parent work unit can include or cover multiple child work units).