Info |
---|
See also: OLE Instance Document as recommended replacement August 2012, pending PM and FC approval. Instance v 9.0 (OLE 0.8) https://jira.kuali.org/browse/OLE-2980 (v 9.x under review) Instance v 8.1 (OLE 0.6) https://jira.kuali.org/browse/OLE-2293 (Available in OLE-DEMO) Instance Editor: https://jira.kuali.org/browse/OLE-2555 and related linked tasks |
Section |
---|
Column |
---|
| OLE Instance documents are used to identify and describe library resources locally owned/licensed by libraries and as such contain unique information that can not be captured in Bibliographic documents that may be used/shared by multiple libraries. OLE Terms and Definitions - Instance. This document type includes information traditionally known as holdings and item information. It is a single document type with 2 categories of information (holdings and item).
- 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.
- Item. Describes the smallest unit of a resource that is managed and/or circulated individually. It provides specific information regarding the physical location when pertinent.
The OLE Instance schema is loosely based on the MARC Format for Holdings Data (MFHD) and represents core elements that must be included when describing holdings and items. The schema does not support every MFHD field/subfield but does include additional pieces of information not supported by MFHD. Additionally, the OLE Instance schema has taken some elements traditionally captured with holdings data and moved those to item descriptions. These include elements for describing the location of items (MFHD 852 field and subfields) as well as information relating to how users may access electronic resources (MFHD 856 field and subfields). Because the current schema only represents "core" elements, it does allow for the addition of "local" pieces of data via the <extension> element. The OLE Instance schema does not dictate how libraries combine items to comprise holdings data. As with MFHD, libraries may choose to describe multiple copies of a single resource in one OLE Instance or provide separate OLE Instance documents for each copy. The OLE Instance <separateOrCompositeReport> element will allow libraries to indicate for each OLE Instance document whether or not it is for only one copy or for a consolidation of information about more than one copy of the bibliographic item. |
Column |
---|
|
Panel |
---|
borderColor | #97A0A9 |
---|
bgColor | #F8FCFF |
---|
titleBGColor | #F2F8FF |
---|
borderStyle | dashed |
---|
| Page Tree |
---|
root | OLE:@self |
---|
expandCollapseAll | true |
---|
startDepth | 3 |
---|
searchBox | False |
---|
|
|
|
|
DATA
META DATA
Currently, the meta data keeps as the properties in instance/item nodes, following is the list:
...
Instance meta metadata meeting notes is the best place to learn the more detailed information or background knowledges.
OLE 0.6 release: Instance schema V8.1
...
Meeting notes on applying instance schema v9 to DocStore
John Pillans is working on re-evaluating the loading data, need to check with Gary so that we are all on the same stage.
FEATURES
LINKING
Currently the linkage information is kept as the instance properties in the instance node.
The versioning for instance/holding/items was turned off now.
(Carried forward from OLE release 0.6- to be modified as changes made)
...