Individual Data Elements - Details

1. <instance>

<instanceIdentifier> (NR): This is a system-generated unique identifier for the instance document in the OLE DocStore.
<resourceIdentifier> (R) : This is the unique bibliographic identifier from the source bibliographic record.
<formerResourceIdentifer> (R) : These are the bibliographic record identifiers that are used when linking instance documents with the appropriate bibliographic records in OLE after legacy data migration. If the source is a MARC record, then it maps to the 035 field.

2. <oleHoldings>

Location information presented here is automatically inherited by the linked items.
Location information at the item level with the flag "primary=true" will imply that location for the item may have temporarily changed. In cases where the item has been moved permanently, the flag can be left untouched.

<extentOfOwership> (R)
1. <textualHoldings> : This is a free text field for entering textual holdings and may include both the captions and enumerations and chronology for the holdings. Examples: v. 1-23; v.3 pt 1-2
2. <type>: This indicates whether the summary statement is of type Basic, Supplementary or Indexes. This will determine if the holdings is going to be recorded in 866, 867, or 868 MARC fields.
3. <holdingNote> (R): Notes for textual holdings that can be public or non-public and maps to $x or $z.
<receiptStatus> (NR) : This indicates the status of receiving and has a set of controlled values as specified in MFHD. This data element will map to MFHD 008 position 06.
<uri> : (R) This data element represent the uniform resource identifier and maps to MFHD 856$u. This can also be found in the Bib MARC record and represents the general access link for a title. A URI can also be recorded at the item level in accessInformation to specify the link to an individual item or volume.
<holdingsNote> (R) : Note that can be for public or non-public. This maps to 852 $x if non-public and $z if public.
<location>
1. <locationLevel> : This represents the various levels for a location. Even though institutions can use as many levels as they desire, MFHD supports only three levels. The lower most level is going to be used for indicating the shelving location. OLE will also support 3 levels out of the box to accommodate MFHD conversion.
<shelvingScheme> : This indicates the shelving scheme used and has a set of controlled value as specified in the MFHD 852 ind1.
<callNumberType> : This can be used in addition to the shelving scheme for institutions who use local values or values outside the MARC specs. From a mapping perspective OLE will designate it 852 $2.
<callNumber> : Indicates the call number to be used for a work. Call number exists both within oleHoldings and item. By default the call number within all items of an instance will be inherited from the call number in oleHoldings. However, the call number within an individual item will be editable and therefore can be changed from the default so that it no longer matches the oleHoldings call number. A callNumber may consist of up to three parts: callNumberPrefix, classificationPart, and itemPart.
1. <callNumberPrefix> : This value precedes the call number and maps to MFHD 852$k. Example: Folklore
2. <classificationPart> : Classification part of the call number, or class number, used for the shelving scheme of a work. A Cutter, date, or term that is added to the classification to distinguish one work from any other work assigned the same classification is recorded in the itemPart. Maps to MFHD 852$h.
3. <itemPart> : Cutter, date, or term that is added to the classification contained in classificationPart to distinguish one work from any other work assigned the same classification. Maps to 852$i.
4. <shelvingOrder>: This is the normalized form of the call number and determines how the call number is actually sorted in an index. Maps to 852 ind2.
5. <shelvingScheme>: This maps to 852 ind1 of a MARC holding record.
6. <prefix>: Term that precedes a callNumber. Maps to 852 $k of MARC holdings.

Instance Editor has one text area where users can key in the call numbers. Even though there are separate data elements for item parts and class parts, they can be left blank for data migration purposes.

3. <sourceHoldings>

This section contains the raw holdings record in the native format wrapped in CDATA which allows for the flexibility of using any format for holdings (MFHD, MODSHD, DCHD etc.). OLE will provide for an editor to edit the MFHD record out of the box. Any custom holdings format will need to be handled by the implementing institutions.

4. <item>

Classification part and Item parts will be presented as one single text box in the UI. Institutions using marc holdings get to retain that information in the individual sub-fields. Institutions that dont use Marc holdings can use it as one string that will be stored in the item part and if at a given point for a given record the holdings format changes from oleHoldings to marc holdings, the item part will be retained in the 852$h.

<itemIdentifier> : This is a system generated unique identifier for the item record.
<purchaseOrderLineItemIndentifier> : This is the Purchase Order line item identifier for the item that links to the OLE transactional document.
<vendorLineItemIdentifier> : This is the vendor number for the vendor from which the item was purchased from the OLE transactional document.
<accessInformation> : This is the volume specific URL. The general access information for a title could be recorded at the holdings level in data element "uri", but for specific volumes or items, here is where one would record it.
<barcodeARSL> : Special identifier for institutions that have automated storage and retrieval systems.
<formerIdentifiers> : Does not map to MFHD. Identifies previously used barcodes or other identifiers for the holdings/item being described. Also allows for indicating types of identifiers, such as legacy systems.
<statisticalSearchingCodes> : Codes that can be used for searching within a discovery layer/OPAC, and/or for assigning items to specific categories for statistical reporting. Each OLE site will be free to make up its own list of statisticalSearchingCodes.
<itemType> : Locally defined value that is used for circulation purposes and is a controlled value.
<copyNumber> : Maps to MFHD 876$t. Library assigned to distinguish each copy of the same volume of the same title. Often printed, with the associated copyNumberLabel at the end of a spine label.
<copyNumberLabel> : Does not map to MFHD. Identifies the type of copyNumber (e.g. "c" for "copy").
<volumeNumber> : Does not map to MFHD. Library assigned to distinguish each volume of a multipart title. CONSIDER DELETING THIS ELEMENT -- REDUNDANT WITH "ENUMERATION" -GARY CHARBONNEAU
<volumeNumberLabel> : Does not map to MFHD. Identifies the nature of the volume number (e.g. "v." or "no."). CONSIDER DELETING THIS ELEMENT -- REDUNDANT WITH "ENUMERATION" - GARY CHARBONNEAU
<itemNote> : Item specific note that can be public or non-public.
<enumeration> : Does not map to MFHD. Designation to identify a specific part of a multipart title when there are multiple levels.
<chronology> : Does not map to MFHD. Designation used to identify the issue date of a specific part of a multipart title. Single dates may typically be printed at the end of the callNumberLabel attached to the part.
<highDensityStorage> : Specific storage information.
<barcodeNumber> : Identifier physically attached to an item as a unique identifier.
<temporaryItemType> : This indicates a temporary item type for an item, most likely to be used when the item is moved to a temporary location.
<fund> : This is the account number from the Purchase Order line item that appears in the accounting lines and represents the fund used to purchase the item.
<donorPublicDisplay> : This is automatically inherited from the Purchase Order line item for the appropriate fund used. Place holder for now, but needs more discussion.
<donorNote> : Donor information for items if not purchased using specific funds. Example: gifts
<callNumber> : Indicates the call number to be used for an individual item. A call number may consist of up to three parts:
1. <callNumberPrefix> : Term that precedes a call number.
2. <classificationPart> : Classification part of the call number used as the shelving scheme for a work. A Cutter, date, or term that is added to the classification to distinguish one work from any other work assigned the same classification is recorded in itemPart.
3. <itemPart> : Cutter, date, or term that is added to the classification contained in classificationPart to distinguish one work from any other work assigned the same classification.
4. <callNumberType> : This can be used in addition to the shelving scheme for institutions who use local values or values outside the MARC specs. LC or Duewy decimal etc... This is in addition to the shelving scheme values. Institutions may have values outside MARC specs. Could be locally defined values.
<price> : Price of the item, from the Purchase Order line item.
<numberOfPieces> : The count of individual pieces in the barcoded item. Defaults to 1.
<itemStatus> : Indicates the current status of the item.
<itemEffectiveStatusDate> : Date when the status was assigned. Tied to the itemStatus.
<checkinNote> : Free text note. If populated, operator is prompted with the note for acknowledgement when the item is checked in.
<staffOnlyFlag> :Indicates that the item data is not to be displayed in the public display interface.
<fastAddFlag> : Indicates that the item was created at a circulation desk. May generate a check-in note (e.g. "Route to Cataloging").