Formatting XML Files for Holdings Records Updates
You can update LIB HAS fields in holdings/checkin records by using an XML file. An XML file can contain updates for one or more holdings/checkin records. The XML file must conform to Innovative's Electronic Holdings Update DTD.
This page describes the formatting of an XML file for updating LIB HAS fields in holdings/checkin records.
To format an XML file for updating coverage data, see Formatting XML Files for Coverage Data. To format a XML file for updating both coverage data and LIB HAS fields in holdings/checkin records, see Formatting XML Files for Simultaneous Holdings Records and Coverage Data Updates.
When updating holdings statements from an XML file, enter the identifier in the SUPPLIER element.
If URLs are entered in the XML file, convert special characters in URLs to XML entity references.
To create an XML file for updating holdings statements, follow these steps:
- The first two lines identify the version of XML, the encoding, and the DTD. These lines will be the same for every XML file used for holdings updates. The first two lines are:
<?xml version="1.0" encoding="UTF-8" ?>
<ElectronicHoldingsUpdate>
- The third line is the identifier. Identifiers are used to find the correct copies of the serials to be updated. Only one identifier per XML file is allowed. Tag the identifier by using the <Supplier></Supplier> tags:
<Supplier>example_identifier</Supplier>
- Open a ServiceObject:
<ServiceObject>
- The Vendor ID within the ServiceIdentifier is a required element of the XML file. For holdings updates, Vendor IDs are used to label tabs in the EHoldings Load function. They are for display purposes only and are not saved or used to process the file. Enter any character string between the <VendorId></VendorId> tags.
<ServiceIdentifier>
<VendorId>first tab label</VendorId>
<DatabaseId></DatabaseId>
</ServiceIdentifier>
- Open an ObjectDescription:
<ObjectDescription>
- The ObjectDescription contains optional elements. These elements are the checkin record fields the system will use to find serials to update. For example:
<Title>serial name</Title>
<ISSN>xxxx-xxxx</ISSN>
<Holdings>03/1993-present</Holdings>
- Continue to add ServiceObject and ObjectDescription elements as necessary for each serial to be updated.
The XML file can contain more than one ServiceObject. Multiple ServiceObjects create multiple tabs in the EHoldings Load function. All tabs are processed when you process the file.
- Close the ObjectDescription and ServiceObject elements:
</ObjectDescription>
</ServiceObject>
- Close the file:
</ElectronicHoldingsUpdate>
- Save the XML file in plain text format.
Example of an XML File for Updating Holdings (LIB HAS)
<?xml version="1.0" encoding="UTF-8" ?> <ElectronicHoldingsUpdate> <Supplier>identifier</Supplier> <ServiceObject> <ServiceIdentifier> <VendorId>first tab label</VendorId> <DatabaseId></DatabaseId> </ServiceIdentifier> <ObjectDescription> <Title>Duke Journal of Comparative and International Law</Title> <ISSN>1053-6736</ISSN> <Holdings>03/1993 - present</Holdings> </ObjectDescription> <ObjectDescription> <Title>Journal of Gender Studies</Title> <ISSN>0958-9236</ISSN> <Holdings>03/1992 - present</Holdings> </ObjectDescription> </ServiceObject> <ServiceObject> <ServiceIdentifier> <VendorId>second tab label</VendorId> <DatabaseId></DatabaseId> </ServiceIdentifier> <ObjectDescription> <Title>Immunity</Title> <ISSN>1074-7613</ISSN> <Holdings>01/1996 - present</Holdings> </ObjectDescription> </ServiceObject> </ElectronicHoldingsUpdate>