Status: This is the
current Version of the Holdings Schema, approved December 2002. This definition
supercedes earlier versions and Changes from version 1.2 are marked in red. (Differences between 1.2
and 1.3 are not distinguished. 1.3 was an interim version.)
XML
Version of this schema | ESN
B2 (summary information) | ESN B3 (detailed information)
Holdings Model
Within the context of the Holdings schema, we will not attempt to distinguish between the types of bibliographic units (basic or secondary), nor will we insist on their type of holdings (single-part, multipart or serial), other than providing those characteristics at the time of report. We will simply consider that a bibliographic item may be composed of a certain number of 'parts', issued over a period of time; these parts are modelled as forming a hierarchical tree structure. Thus any part may comprise subsidiary parts and each of these may contain further subsidiary parts.
For example, a serial may consist of parts corresponding to the basic bibliographic unit, the indexes and the supplements. The part for the basic bibliographic unit may contain subsidiary parts corresponding to annual volumes of the serial. Each volume may contain subsidiary parts corresponding to individual monthly issues.
It should be noted that 'part' is a logical construct that may or may not have a 1:1 mapping to the physical 'pieces' contained in the organization's collections. For modelling puposes, one piece is assumed to correspond to some particular part in a hierarchy of parts. This one part a leaf in the tree-structure of parts: it may have both superior and subsidiary nodes in the hierarchy. If so, these other parts do not themselves correspond to pieces. It is important to note that the mapping of parts to pieces at any given site may change over time. For example, a serial received in monthly issues will initially have the part for each issue correspond to a piece as it is received. As issues are bound into annual volumes, the pieces for the issues will cease to exist and will be replaced with a piece corresponding to the annual volume. The parts for the issues, however, will remain in order to describe the logical composition of the serial (and also to provide an audit record for the receipt of the individual parts). When the part information for the volume is retrieved, it may contain the part information for all its subordinate parts, either by including the part information itself or by including a summary of the part information.
Bibliographic Level View of Holdings
Bibliographic level view of holdings describes a bibliographic item in a generic way, i.e., independently of any specific copy.
Bibliographic-item (Item Identification Area)
Part 1: Bibliographic-part level 1 (General Holdings Area)
Part 1.1: Bibliographic-part level 2 (Extent of Holdings Area)
Part 1.1.1: Bibliographic-part level 3
Part 1.1.2: Bibliographic-part level 3
(...)
Part 1.1.n: Bibliographic-part level 3
Part 1.2: Bibliographic-part level 2 (Extent of Holdings Area)
(...)
Part 1.n: Bibliographic-part level 2 (Extent of Holdings Area)
Part 2: Bibliographic-part level 1
(...)
Part n: Bibliographic-part level 1
This view simply describes a bibliographic item as a series of bibliographic parts, which correspond to the ISO definition of a bibliographic unit and/or physical unit. Each bibliographic part may be made of a number of subsidiary parts, each in turn possibly containing a number of further subordinate parts. It is essentially the 'publisher's view' of the bibliographic item, i.e. reflecting the publisher's initial issue or publication of the item. (For example, a serial item could have a part called "v.1:no.1/2", which comprises the two underlying bibliographic parts, i.e. v.1:no.1 and v.1:no.2). This model provides for what is usually referred to as 'summary holdings' and 'detailed holdings'.
Copy and Piece Level View of Holdings
Copy and piece level view of holdings provides the holdings data for each individual copy of a bibliographic item and the physical pieces comprising the copy. It has the following general structure:
Bibliographic-item (Item Identification Area)
Copy-1
Piece-1.1=Bibliographic-part-1 (General Holdings Area)
Bibliographic-part-1.1 (Extent of Holdings Area)
Bibliographic-part-1.2 (Extent of Holdings Area)
(...)
Bibliographic-part-1.3 (Extent of Holdings Area)
Piece-1.2=Bibliographic-part-2
(...)
Piece-1.n=Bibliographic-part-n
Copy-2
(...)
Copy-n
This view, although similar to the bib level view, describes the individual copies of a bib item. Therefore, each copy is also made of a number of physical pieces (with characteristics applying to the copy only), each corresponding to a single part in the part hierarchy. Each part may have parent parts as well as subsidiary parts.

Figure 1: Entity-relationship diagram of bibliographic and holdings data
Holdings Reporting Levels
The Holdings reporting levels proposed below are derived from a number of standards (ISO 10324, NISO Z39.71 and MARC21 for Holdings), but concentrate mainly on the information that is or might be needed from the Z39.50 end-user's perspective. For the purpose of Holdings, two categories of holdings reporting levels are proposed:
Table 1 presents the general content of bibliographic level holdings statements at four different levels, defined as follows:
Level B-1: Minimal bibliographic level holdings (i.e. 'Locations only')
Level B-2: Summary Bibliographic Level Holdings (i.e. summary information about top-level parts held per location, without details of arrangement into physical pieces). This level includes holdings as reported to a union catalogue system.
Summary bibliographic level holdings corresponds partly to ISO/NISO level-3 holdings statements. This level reports summary holdings at the bibliographic level, non copy specific, and makes no distinction on how the local institution physically arranges the different physical parts. Holdings are provided for all bibliographic units of an item, at the highest level of enumeration. SummaryBibLevelHoldings is a list of BibParts, described below. None of the BibParts contain subordinate BibParts
Level B-3: Detailed Bibliographic Level Holdings (i.e. detailed information about parts held per location, without details of arrangement into physical pieces).
Detailed bibliographic level holdings corresponds partly to NISO Z39.71 level-4 holdings statement. This level reports the holdings of bibliographic units at the lowest level, independently of individual copies held by a site. Therefore, a single instance of each bib part is provided (i.e. the specific issue held and not the number of copies of the issue). DetailedBibLevelHoldings is a list of BibParts, described below. Each BibPart will contain subordinate BibParts, if there are any.
Level B-4: Extended bibliographic level holdings (i.e. detailed information about parts held per location, including details of arrangement into physical pieces with circulation information for each piece).
(Please, refer to the corresponding schema definition section for detailed definition of each. The 'Holdings Statement' section provides overview of all levels).
In addition, Appendix A presents the general structure of bibliographic level holdings statements.
Table 1: Bibliographic Level Holdings Element specification
Notation: "M" must be provided if the data is available or appropriate. It is recognized that not all servers will be able to provide all the information marked M
|
|
B-1 |
B-2 |
B-3 |
B-4 |
Rpt |
MARC21 field/subfield |
|
Holdings Structure |
|
|
|
|
|
|
|
bibItemInfo - one of the following: |
O |
O |
O |
O |
NR |
|
|
actualBibItem |
O |
- |
- |
- |
|
changed |
|
targetItemId |
O |
M |
M |
M |
|
004 |
|
holdingsStatements |
|
|
|
|
|
one or more instances of the HoldingsStatement datatype below |
|
remoteHoldingsData |
O |
O |
O |
O |
R |
850,852+ |
|
HoldingsStatement |
|
|
|
|
|
|
|
holdingsSiteLocation |
M |
M |
M |
M |
NR |
One instance of the SiteLocation datatype below |
|
dateOfReport |
- |
O |
O |
O |
NR |
005 |
|
publicationType |
- |
M |
M |
M |
NR |
Leader/06 |
|
unionCatShelfMark |
- |
M |
M |
- |
NR |
852 $h-m |
|
localHoldings - bibView |
- |
M |
M |
M |
R |
853+ One or more instances of the BibPart datatype below |
|
numberOfTopBibParts |
- |
M |
M |
M |
NR |
|
|
numberOfCopies |
- |
M |
M |
- |
NR |
008/17-19 |
|
unionCatCompletenessDesignator |
- |
M |
M |
- |
NR |
008/16 |
|
unionCatAcqStatusDesignator |
- |
M |
M |
- |
NR |
008/06 |
|
unionCatRetentionDesignator |
- |
M |
M |
- |
NR |
008/12 |
|
unionCatReproductionNote |
- |
M |
M |
- |
NR |
843 |
|
unionCatLendingInfo |
- |
M |
M |
- |
NR |
008/20 One instance of the ServiceInfo datatype below |
|
unionCatReproductionInfo |
- |
M |
M |
- |
NR |
008/21 One instance of the ServiceInfo datatype below |
|
unionCatTermsUseRepro |
- |
M |
M |
- |
NR |
845 |
|
summaryReservationPolicy |
- |
M |
M |
- |
NR |
One instance of the ServiceInfo datatype below |
|
summaryReservationInfo |
- |
M |
M |
- |
NR |
One instance of the ReservationInfo datatype below |
|
remoteHoldings |
- |
O |
O |
O |
NR |
|
|
HoldingsNotes |
- |
O |
O |
O |
NR |
852 $z |
|
SiteLocation |
|
|
|
|
|
|
|
TargetLocationId |
- |
O |
O |
O |
NR |
all target ids have been made optional because not needed by the client, except for use as a query term in eSpec-Q |
|
InstitutionOrSiteId |
M |
M |
M |
M |
NR |
852$a |
|
LocationName |
O |
M |
M |
M |
NR |
852$a,$b,or $c |
|
isilCode |
O |
O |
O |
O |
NR |
ISO 15511 |
|
StreetAddress |
- |
O |
O |
O |
R |
852 $e |
|
CountryId |
- |
O |
O |
O |
NR |
852 $n (ISO 3166) |
|
regionId |
- |
O |
O |
O |
R |
repeatable to allow a server to identify multiple regions - e.g. a resource sharing consortium could be named here, or a geographic region, etc. |
|
networkAddress |
- |
O |
O |
O |
NR |
|
|
siteNotes |
- |
O |
O |
O |
NR |
|
|
subLocation |
- |
O |
O |
O |
NR |
One instance of a SiteLocation datatype it is the server's choice as to how detailed a location structure it provides |
|
moreInfo |
- |
O |
O |
O |
NR |
a URL to more information about the siteLocation, e.g. hours, services, etc. |
|
BibPart |
|
|
|
|
|
1st level only for B2; MARC21 defines up to 6 levels for B3 |
|
targetBibPartId |
- |
O |
O |
O |
NR |
|
|
parentBibPartId |
- |
- |
O |
O |
NR |
|
|
typeofUnitDesignator |
- |
M |
M |
M |
NR |
Leader/17 + presence of 865-878 |
|
unitName |
- |
M |
M |
M |
NR |
844 or 852 $3 |
|
physicalFormDesignator |
- |
O |
O |
|
NR |
007/00-01 This element is retained for backward compatibility. Is has been replaced by copyPhysicalFormDesignator and piecePhysicalFormDesignator |
|
bibPartLendingInfo |
- |
O |
O |
O |
NR |
ServiceInfo |
|
bibPartReproductionInfo |
- |
O |
O |
O |
NR |
ServiceInfo |
|
bibPartEnumeration |
- |
- |
M |
M |
NR |
853-866 one instance of the Enumeration datatype below |
|
bibPartChronology |
- |
- |
M |
M |
NR |
853-866 one instance of the Chronology datatype below |
|
alternativeEnumeration |
- |
- |
O |
O |
R |
853-866 one instance of the Enumeration datatype below |
|
alternativeChronology |
- |
O |
O |
O |
R |
853-866 one instance of the Chronology datatype below |
|
numberOfChildBibParts |
- |
M |
M |
M |
NR |
|
|
childEnumChronSummary - one of the following: |
- |
M |
- |
- |
NR |
excluded from B3, because child parts are included, which contain their own enum/chron
|
|
structured |
- |
O |
- |
- |
|
Structured and unstructured are normally mutually exclusive 853-866 |
|
unstructured |
- |
O |
- |
- |
|
866-868 $a The unstructured choice is retained here for backward compatibility. Unstrcutured has been added as an element to SummaryEnum and it is recommanded to use that element for unstructured child eumeration and chronology data |
|
childCompletenessDesig |
- |
M |
M |
M |
NR |
an indication as to whether all expected child parts (and their descendants) are present |
|
bibPartNotes |
- |
O |
O |
O |
NR |
866 $z, 852 $z |
|
childBibParts |
- |
- |
- |
M |
R |
repeats of 853-856 at increasing levels multiple instances of the BibPart datatype |
|
numberOfPieces |
- |
- |
O |
O |