| Wiki Markup |
|---|
{section}
{column:width=50%}
h4.
{info:title=JIRA#}[| Section |
|---|
]
{info}
{info:title=SVN Link}[]
{info}
{info:title=Contributors} Case
{info}
{column}
{column:width=50%}
\\
{panel:borderStyle=dashed|borderColor=#97A0A9|titleBGColor=#F2F8FF|bgColor=#F8FCFF}
h3. Instance 9.1 documentation
{pagetree:root=@self|searchBox=False|startDepth=5|expandCollapseAll=true}
{panel}
{column}
{section}
h4. 1. Description
The OLE Instance document is a container for recording holdings and item information for a bibliographic record. Even though there is a standard for [MARC Holdings|http://www.loc.gov/marc/holdings/] (which has often been loosely followed), there isn't one for items and depending on the vendor systems, these are stored in different ways. OLE Instance defines a standard for storing holdings/item information in three main sections as described below.
h4. 2. Main Sections of the OLE Instance Document
{info}
For a given bibliographic record, only one of either oleHoldings or sourceHoldings can be used as the main holdings record. OLE will not support usage of both for a given record as that leads to overhead of managing data consistencies between the two sections. If an OLE Instance is initially created using oleHoldings, a staff user will be able to click a button in order to convert the oleHoldings to sourceHoldings via a mapping from one to the other.
{info}
# {color:#339966}oleHoldings{color}: This section records "general" holdings information in a format specific to OLE.
# {color:#339966}sourceHoldings{color}: This section represents "specific" holdings information entered according to some standard external to OLE. Examples are MARC holdings, MODS holdings or any other format specific holdings.
# {color:#339966}items{color}: This section records information about 1 or more items.
{info}Information such as location, callNumbers etc are captured at the holdings level and linked items inherit those. Further the data is only recorded once and not copied at individual item levels unless applicable for a particular item.
{info}
h4. 3. Business requirements/Workflows
More of business rules etc.. or links to google docs. Coming soon\!
h4. 4. {link-window:http://dev.docstore.ole.kuali.org/schema/ole-instance-schema.xsd|scrollbars=true|menubar=true|location=true|statusbar=true|resizable=true|width=800|height=600|icon=false}Schema{link-window}
Detailed information about the OLE Instance schema and the various parts.
h4. 5. [Sample XMLs] \- (Books, Serials, Mutli-Part etc..)
h4. 6. Validation of Instance XML with the Schema
Visit [W3C XML Schema (XSD) Validation online|http://www.utilities-online.info/xsdvalidation/] and paste the XML and the schema (from section 4 and 5 above) into text areas and click the 'Validate XML against XSD' button.
h4. 7. [Individual Data Elements - Details|OLE:Individual Data Elements - Details]
h4. 8. [Revised Editor|OLE:Revised Editor - Wireframes]
h4. 9. Storage
The OLE Instance document will be stored in ole-docstore in three separate documents namely, instance, holdings and items. Each of the documents gets a unique identifier generated by ole-docstore ([Apache Jackrabbit|http://jackrabbit.apache.org/]| Column |
|---|
|
| Panel |
|---|
| borderColor | #97A0A9 |
|---|
| bgColor | #F8FCFF |
|---|
| titleBGColor | #F2F8FF |
|---|
| borderStyle | dashed |
|---|
| Instance 9.1 documentation| Page Tree |
|---|
| root | @self |
|---|
| expandCollapseAll | true |
|---|
| startDepth | 5 |
|---|
| searchBox | False |
|---|
|
|
|
|
1. Description
The OLE Instance document is a container for recording holdings and item information for a bibliographic record. Even though there is a standard for MARC Holdings (which has often been loosely followed), there isn't one for items and depending on the vendor systems, these are stored in different ways. OLE Instance defines a standard for storing holdings/item information in three main sections as described below.
2. Main Sections of the OLE Instance Document
| Info |
|---|
For a given bibliographic record, only one of either oleHoldings or sourceHoldings can be used as the main holdings record. OLE will not support usage of both for a given record as that leads to overhead of managing data consistencies between the two sections. If an OLE Instance is initially created using oleHoldings, a staff user will be able to click a button in order to convert the oleHoldings to sourceHoldings via a mapping from one to the other. |
- oleHoldings: This section records "general" holdings information in a format specific to OLE.
- sourceHoldings: This section represents "specific" holdings information entered according to some standard external to OLE. Examples are MARC holdings, MODS holdings or any other format specific holdings.
- items: This section records information about 1 or more items.
| Info |
|---|
Information such as location, callNumbers etc are captured at the holdings level and linked items inherit those. Further the data is only recorded once and not copied at individual item levels unless applicable for a particular item. |
3. Business requirements/Workflows
More of business rules etc.. or links to google docs. Coming soon!
4.
Detailed information about the OLE Instance schema and the various parts.
5. Sample XMLs - (Books, Serials, Mutli-Part etc..)
6. Validation of Instance XML with the Schema
Visit W3C XML Schema (XSD) Validation online and paste the XML and the schema (from section 4 and 5 above) into text areas and click the 'Validate XML against XSD' button.
9. Storage
The OLE Instance document will be stored in ole-docstore in three separate documents namely, instance, holdings and items. Each of the documents gets a unique identifier generated by ole-docstore (Apache Jackrabbit).