EDItEUR logo

ONIX Serial Products and Subscriptions Message Formats

Product List Priced

Version 0.91 User Guide

Date issued: January 2007

This User Guide has been prepared for the EDItEUR / NISO Joint Working Party for the Exchange of Serials Subscription Information by Katharina Klemperer, David Martin and Francis Cave. It is designed to accompany a machine-readable specification of the formats written in XML Schema, which has been developed by Francis Cave.

Copyright © 2004-2006 EDItEUR Limited. All rights reserved.

The structural diagrams have been produced using XML Spy™ from Altova GmbH.

General guidance on schema use

This schema provides a formal specification of what constitutes valid use of XML to construct an ONIX Serials Products and Subscriptions (SPS) message of type Product List Priced. A complete list of schemas in the SPS family is given below.

As well as specifying the XML tags that may be used and in what sequence, it also specifies valid ranges of data values for data contained in XML elements, i.e. between matching pairs of XML tags.

The schema to which this document refers comprises two files, which together form an XML document that conforms to the XML Schema Recommendation of the World Wide Web Consortium (W3C). The two files are:

Filename  

Description of content

ONIX_SPSProductListPriced_Vn.n.xsd  definitions of the message-level element and of complex types specific to this type of message (the number 'n.n' is the version number of this schema)
ONIX_Serials_CodeLists.xsd  definitions of datatypes common to all ONIX Serials schemas.

For further information see XML Schema Part 1: Structures and XML Schema Part 2: Datatypes.

It is intended that this schema be used to guide implementation of systems for either originating or receiving SPS messages. Used in conjunction with a suitable “schema parser” it may also be used to validate the structure and contents of an individual message.

This schema defines how the substance, or “payload”, of SPS messages are to be represented in XML, but is silent on the question of how this message is to be conveyed from originator to recipient. It is likely that supply chain partners will need to adopt different approaches to message transport, packaging and delivery, depending upon the specific business systems in which this message format is being implemented.

Guidance on reading the message format specifications

In this user guide each successive XML element is illustrated by a graphic which shows any “child” elements. Clicking on any “child” element will take you to the description of that element. Clicking “Back” will return you to the “parent”.

If a “child” element is shown with a solid outline, the element is mandatory in any occurrence of the “parent”. If it is shown with a dotted outline, it is conditional in this context. If it is repeatable, the element box has the legend “1..∞” or “0..∞” immediately below it, indicating “mandatory and repeatable” or “conditional and repeatable”.

All data types are based upon built-in primitive data types defined in XML Schema Part 2: Datatypes. The names of all pre-defined data types are prefixed by “xs:” and include:

xs:stringa string of characters
xs:decimala number that may have a decimal part
xs:intan integer between -2147483648 and +2147483647 inclusive

Introduction

The ONIX Serials Products and Subscriptions (SPS) format defines a family of messages used for transmitting information about Serial Subscription Products, with or without price information, and with or without subscription information relating to a particular subscriber. The four messages currently defined are:

Typically, the sending organisation will be a publisher or subscription agent. Recipients can include university or corporate libraries, agents, consortia, or indeed a “broadcast” customer base for priced product lists.

Release 0.91 is the version which is currently being piloted. On completion of the pilots, and the incorporation of any consequent changes, EDItEUR will issue a first full Release, to be numbered 1.0, after which every effort will be made to maintain upwards compatibility in future revisions.

Related Documents

Please refer to the following documents for a more detailed introduction to the SPS format:

SPS Outline Specification Release 0.91
(http://www.editeur.org/onixserials/060411_ONIX_SPS_overview_0.91.pdf)
ONIX Serials Glossary
(http://www.editeur.org/onixserials/060411_ONIX_Serials_glossary.pdf)

ONIX SPS Product list priced

<ONIXSPSProductListPriced>

The <ONIXSPSProductListPriced> message is a list of subscription products offered by a publisher, subscription agent, online publisher, content hosting service, or any other party that sells subscriptions, with price information. It is identical to the unpriced product list message, except for the inclusion of catalog prices.

<ONIXSPSProductListPriced>
<Header>

Mandatory in every ONIX SPS message.

Not repeatable

 

The <Header> contains administrative information including metadata and contact information about the sender and the addressee(s) of the message; optional default publisher and subscription agent; and “housekeeping” information such as message number and date and time sent.

 

<ONIXSPSProductListPriced> <Header>
<Sender>

Mandatory within <Header>

Not repeatable

 

Identification of the organization that is sending the message.

Must contain either <SenderIdentifier> or <SenderName> or both.

 

 

Example:

<Sender>

     <SenderIdentifier>

          <SenderIDType>07</SenderIDType>     07 = “SAN”

          <IDValue>1234567</IDValue>

     </SenderIdentifier>

     <SenderName>Oxford University Press</SenderName>

     <SenderContact>Subscriptions Department</SenderContact>

     <SenderEmail>subscriptions@oupjournals.org</SenderEmail>

</Sender>

<ONIXSPSProductListPriced> <Header> <Sender>
<SenderIdentifier>

Optional within <Sender>

Repeatable for identifiers with different SenderIDTypes

 

Identification of the sender using a value from a standard or proprietary identification scheme.

<Sender> must contain either <SenderIdentifier> or <SenderName> or both.

 

<ONIXSPSProductListPriced> <Header> <Sender> <SenderIdentifier>
<SenderIDType>

Mandatory within <SenderIdentifier>

Not repeatable

 

<SenderIDType> is a code indicating the scheme or standard from which the sender identifier is taken. If <SenderIDType> is 01 (proprietary), then the name of the scheme should appear in <IDTypeName>.

 

Permissible code values:

01 Proprietary

06 EAN-UCC GLN

07 SAN

08 MARC21 organizations code

09 ISIL

<ONIXSPSProductListPriced> <Header> <Sender> <SenderIdentifier>
<IDTypeName>

Optional within <SenderIdentifier>

Not repeatable

 

The name of the identification scheme from which the <IDValue> is taken, used only when <SenderIDType> is “01” (proprietary).

 

<ONIXSPSProductListPriced> <Header> <Sender> <SenderIdentifier>
<IDValue>

Mandatory within <SenderIdentifier>

Not repeatable

 

An identifier of the type specified in <SenderIDType>

 

<ONIXSPSProductListPriced> <Header> <Sender>
<SenderName>

Optional within <Sender>

Not repeatable

 

The text name of the sending organization.

 

<Sender> must contain either <SenderIdentifier> or <SenderName> or both.

 

<ONIXSPSProductListPriced> <Header> <Sender>
<SenderContact>

Optional within <Sender>

Not repeatable

 

The name of a contact person or group at the sending organization.

 

<ONIXSPSProductListPriced> <Header> <Sender>
<SenderEmail>

Optional within <Sender>

Not repeatable

 

An email address that may be used to contact the sending organization.

 

<ONIXSPSProductListPriced> <Header>
<Addressee>

Optional within <Header>

Repeatable

 

Identification of the intended recipient organization(s) for the message.

 

May be omitted from broadcast messages or those intended for general distribution.

May be repeated if the same message is sent to multiple recipients

Must contain either <AddresseeIdentifier> or <AddresseeName> or both.

 

Example:

<Addressee>

     <AddresseeIdentifier>

          <AddresseeIDType>07</AddresseeIDType>     07 = “SAN”

          <IDValue>1234567</IDValue>

     </AddresseeIdentifier>

     <AddresseeName>Sample University Library</AddresseeName>

     <AddresseeContact>John Q. Librarian</AddresseeContact>

     <AddresseeEmail>jlibrarian@sampleuniv.edu</AddresseeEmail>
</Addressee>

<ONIXSPSProductListPriced> <Header> <Addressee>
<AddresseeIdentifier>

Optional within <Addressee>

Repeatable for identifiers with different AddresseeIDTypes

 

Identification of an Addressee using a value from a standard or proprietary identification scheme.

Must contain either <AddresseeIdentifier> or <AddresseeName> or both.

 

<ONIXSPSProductListPriced> <Header> <Addressee> <AddresseeIdentifier>
<AddresseeIDType>

Mandatory within <AddresseeIdentifier>

Not repeatable

 

A code indicating the scheme or standard from which the Addressee identifier is taken. If <AddresseeIDType> is “01” (proprietary), then the name of the scheme should appear in <IDTypeName>.

 

Permissible code values:

01 Proprietary

06 EAN-UCC GLN

07 SAN

08 MARC21 organizations code

09 ISIL

<ONIXSPSProductListPriced> <Header> <Addressee> <AddresseeIdentifier>
<IDTypeName>

Optional within <AddresseeIdentifier>

Not repeatable

 

The name of the identification scheme from which <IDValue> is taken, used only when <AddresseeIDType> is “01” (proprietary).

 

<ONIXSPSProductListPriced> <Header> <Addressee> <AddresseeIdentifier>
<IDValue>

Mandatory within <AddresseeIdentifier>

Not repeatable

 

An identifier of the type specified in <AddresseeIDType>.

 

<ONIXSPSProductListPriced> <Header> <Addressee>
<AddresseeName>

Optional within <Addressee>

Not repeatable

 

The text name of the sending organization.

<Addressee> must contain either <AddresseeIdentifier> or <AddresseeName> or both.

 

<ONIXSPSProductListPriced> <Header> <Addressee>
<AddresseeContact>

Optional within <Addressee>

Not repeatable

 

The name of a contact person or group at the recipient organization.

 

<ONIXSPSProductListPriced> <Header> <Addressee>
<AddresseeEmail>

Optional within <Addressee>

Not repeatable

 

An email address that may be used to contact the recipient organization.

 

<ONIXSPSProductListPriced> <Header>
<MessageNumber>

Optional within <Header>

Not repeatable

 

<MessageNumber> carries a sequence number for ONIX messages of this type sent as part of a series of such messages. The element is optional and non-repeating, but its use is recommended to underpin process integrity and to act as a check against missed or repeated messages.

 

Example:

<MessageNumber>1</MessageNumber>

<ONIXSPSProductListPriced> <Header>
<MessageRepeat>

Optional within <Header>

Not repeatable

 

A sequence number showing how many times this particular message has been sent, starting with “1” for the first transmission of the message.

 

Example:

<MessageRepeat>1</MessageRepeat>

<ONIXSPSProductListPriced> <Header>
<SentDateTime>

Mandatory within <Header>

Not repeatable

 

A date/time stamp, showing when the message was sent. The following formats may be used:

 

YYYYMMDD

YYYYMMDDTHHMM

YYYYMMDDTHHMMZ (universal time)

YYYYMMDDTHHMM±HHMM (time zone)

 

where “T” and "Z" are constants; that is, the letters T and Z. The recommended form is YYYYMMDDTHHMMZ, using universal time (UTC/GMT).

 

Example:

<SentDateTime>20051020T1550Z</SentDateTime>

<ONIXSPSProductListPriced> <Header>
<MessageNote>

Optional within <Header>

Not repeatable

 

A free-text note about the message.

 

Example:

<MessageNote>This message includes all subscription products available from OUP for subscription year 2007</MessageNote>

<ONIXSPSProductListPriced> <Header>
<DefaultCurrencyCode>

Optional within <Header>

Not repeatable

 

The currency in which prices are given in the message. This element may be included when all or most of the prices in the message are given in the same currency. It may be overridden by the appearance of a <CurrencyCode> element in any of the <TotalPrice> composites in the message.

Permissible code values:

Currency code - ISO 4217

 

Example:

<DefaultCurrencyCode>EUR</DefaultCurrencyCode>

<ONIXSPSProductListPriced> <Header>
<DefaultPublisher>

Optional within <Header>

Not repeatable

 

The publisher whose subscription products are listed in the message. This composite may be used when the message applies wholly or mainly to a single publisher. It may be overriden by the presence of one or more <Publisher> composites in <SubscriptionProductRecord> <SerialVersion> <SerialWork>.

 

<DefaultPublisher> must contain either <PublisherIdentifier> or <PublisherName> or both.

 

Example:

<DefaultPublisher>

     <PublishingRole>01</PublishingRole>               01 = “Publisher”

     <PublisherIdentifier>

          <PublisherIDType>07</PublisherIDType>     07 = “SAN”

          <IDValue>1234567</IDValue>

     </PublisherIdentifier>

     <PublisherName>Oxford University Press</PublisherName>

</DefaultPublisher>

<ONIXSPSProductListPriced> <Header> <DefaultPublisher>
<PublishingRole>

Mandatory within <DefaultPublisher>

Not repeatable

 

The role of a publisher. In this context, the value will always be “01” (publisher); that is, publisher of the intellectual content.

 

Permissible code values:

01 Publisher

<ONIXSPSProductListPriced> <Header> <DefaultPublisher>
<PublisherIdentifier>

Optional within <DefaultPublisher>

Repeatable if there are multiple identifiers with different PublisherIDTypes.

 

Identification of a publisher using a value from a standard or proprietary identification scheme.

 

<DefaultPublisher> must contain either <PublisherIdentifier> or <PublisherName> or both.

 

<ONIXSPSProductListPriced> <Header> <DefaultPublisher> <PublisherIdentifier>
<PublisherIDType>

Mandatory within <PublisherIdentifier>

Not repeatable

 

A code indicating the scheme or standard from which the publisher identifier is taken. If <PublisherIDType> is “01” (proprietary), then the name of the scheme should appear in <IDTypeName>.

 

Permissible code values:

01 Proprietary

06 EAN-UCC GLN

07 SAN

<ONIXSPSProductListPriced> <Header> <DefaultPublisher> <PublisherIdentifier>
<IDTypeName>

Optional within <PublisherIdentifier>

Not repeatable

 

The name of the identification scheme from which the <IDValue> is taken, used only when <PublisherIDType> is “01” (proprietary).

 

<ONIXSPSProductListPriced> <Header> <DefaultPublisher> <PublisherIdentifier>
<IDValue>

Mandatory within <PublisherIdentifier>

Not repeatable

 

An identifier of the type specified in <PublisherIDType>.

 

<ONIXSPSProductListPriced> <Header> <DefaultPublisher>
<PublisherName>

Optional within <DefaultPublisher>

Not repeatable

 

The text name of the default publisher.

 

<DefaultPublisher> must contain either <PublisherIdentifier> or <PublisherName> or both.

 

<ONIXSPSProductListPriced> <Header>
<DefaultAgent>

Optional within <Header>

Not repeatable

 

The subscription agent though whom subscription products listed in the message are supplied. May be omitted if the agent is the sender, or if there is no agent involved.

 

Example:

<DefaultAgent>

     <AgentIdentifier>

          <AgentIDType>07</AgentIDType>     07 = “SAN”

          <IDValue>1234567</IDValue>

     </AgentIdentifier>

     <AgentName>Sample Agent</AgentName>

</DefaultAgent>

<ONIXSPSProductListPriced> <Header> <DefaultAgent>
<AgentIdentifier>

Optional within <DefaultAgent>

Repeatable if there are multiple identifiers with different AgentIDTypes.

 

Identification of an agent using a value from a standard or proprietary identification scheme.

 

<DefaultAgent> must contain either <AgentIdentifier> or <AgentName> or both.

 

<ONIXSPSProductListPriced> <Header> <DefaultAgent> <AgentIdentifier>
<AgentIDType>

Mandatory within <AgentIdentifier>

Not repeatable

 

A code indicating the scheme or standard from which the AgentIdentifier is taken. If <AgentIDType> is “01” (proprietary), then the name of the scheme should appear in <IDTypeName>.

 

Permissible code values:

01 Proprietary

06 EAN-UCC GLN

07 SAN

<ONIXSPSProductListPriced> <Header> <DefaultAgent> <AgentIdentifier>
<IDTypeName>

Optional within <AgentIdentifier>

Not repeatable

 

The name of the identification scheme from which the <IDValue> is taken, used only when <AgentIDType> is “01” (proprietary).

 

<ONIXSPSProductListPriced> <Header> <DefaultAgent> <AgentIdentifier>
<IDValue>

Mandatory within <AgentIdentifier>

Not repeatable

 

An identifier of the type specified in <AgentIDType>

<ONIXSPSProductListPriced> <Header> <DefaultAgent>
<AgentName>

Optional within <DefaultAgent>

Not repeatable

 

<DefaultAgent> must contain either <AgentIdentifier> or <AgentName> or both.

 

The text name of the default agent.

 

<ONIXSPSProductListPriced> <Header>
<SubscriptionPeriodDefinition>

Optional within <Header>

Repeatable for multiple subscription periods

 

A period for which a subscription product may be purchased.

 

All subscription periods used in the message are defined in the header and then referred to by label in the body of the message; therefore, there must be a <SubscriptionPeriodDefinition> for each unique subscription period used in the message.

 

Note that <SubscriptionPeriod> is not used for describing the coverage of electronic serial versions, but rather for indicating the volumes/issues expected to be published during the subscription period.

 

Example: In this example, two subscription periods are defined, one for a one-year subscription, and one for a 3-year subscription.

 

<SubscriptionPeriodDefinition>

     <SubscriptionPeriodLabel>2006</SubscriptionPeriodLabel>

     <StartDate>20060101</StartDate>

     <EndDate>20061231</EndDate>

</SubscriptionPeriodDefinition>

<SubscriptionPeriodDefinition>

     <SubscriptionPeriodLabel>2006-2008</SubscriptionPeriodLabel>

     <StartDate>20060101</StartDate>

     <EndDate>20081231</EndDate>

</SubscriptionPeriodDefinition>

<ONIXSPSProductListPriced> <Header> <SubscriptionPeriodDefinition>
<SubscriptionPeriodLabel>

Mandatory within <SubscriptionPeriodDefinition>

Not repeatable.

 

An arbitrary label assigned to a subscription period by the sender and referred to in the body of the message. Each <SubscriptionPeriodLabel> in the Header must be unique.

 

<ONIXSPSProductListPriced> <Header> <SubscriptionPeriodDefinition>
<StartDate>

Mandatory within <SubscriptionPeriodDefinition>

Not repeatable.

 

The first day of the subscription period being defined.

Always takes the form YYYYMMDD.

 

<ONIXSPSProductListPriced> <Header> <SubscriptionPeriodDefinition>
<EndDate>

Mandatory within <SubscriptionPeriodDefinition>

Not repeatable.

 

The last day of the subscription period being defined.

Always takes the form YYYYMMDD.

 

<ONIXSPSProductListPriced> <Header>
<CompleteFile>

Optional within <Header>

Not repeatable

 

An empty element indicating that this message is a complete replacement list.

 

Each message must contain either <CompleteFile/> or <DeltaFile/> but not both.

 

Example:

<CompleteFile/>

<ONIXSPSProductListPriced> <Header>
<DeltaFile>

Optional within <Header>

Not repeatable

 

An empty element indicating that the message carries an incremental update list, consisting of new, updated and deleted subscription product records, as indicated in <SubscriptionProductRecord> <NotificationType>. Note however that each subscription product record must itself be complete, since there is no provision for updating at the element level.

 

Each message must contain either <CompleteFile/> or <DeltaFile/> but not both.

 

Example:

<DeltaFile/>

<ONIXSPSProductListPriced>
<SubscriptionProductRecord>

Mandatory within the message

Repeatable

 

Details of a subscription product; that is, a group of one or more serial versions that is sold as a single subscription. A subscription product may consist of one or more manifestations of the same serial work, or it may contain one or more manifestations of multiple works.

 

Every SPS message must contain at least one Subscription Product Record.

 

 

Example 1: This example shows the top-level information that applies to the entire subscription product, for a print-plus-online subscription product.

 

<SubscriptionProductRecord>

     <NotificationType>00</NotificationType>          01 = “unspecified”

     <SubscriptionProductIdentifier>

          <SubscriptionProductIDType>01</SubscriptionProductIDType>     01 = “proprietary”

          <IDTypeName>Agent’s product ID</IDTypeName>

          <IDValue>ACT013680</IDValue>

     </SubscriptionProductIdentifier>

     <SubscriptionProductName>Acta Oncologica, print plus online</SubscriptionProductName>

     <SubscriptionProductDescription>Includes print plus sitewide online access</SubscriptionProductDescription>

     [2 Serial version composites would appear here]

</SubscriptionProductRecord>

 

Example 2: This example shows the top-level information that applies to the entire subscription product, for a collection of online journals from the same content hosting system and online publisher. The Content Hosting System and Online Publisher shown here apply to all online serial versions in this subscription product.

 

<SubscriptionProductRecord>

     <NotificationType>00</NotificationType>          01 = “unspecified”

     <SubscriptionProductIdentifier>

          <SubscriptionProductIDType>01</SubscriptionProductIDType>     01 = “proprietary”

          <IDTypeName>Publisher’s product ID</IDTypeName>

          <IDValue>99999999</IDValue>

     </SubscriptionProductIdentifier>

     <SubscriptionProductName>eDuke Scholarly Collection</SubscriptionProductName>

     <SubscriptionProductDescription>Sitewide online access to twenty-nine Duke humanities and social science journals</SubscriptionProductDescription>

     <ContentHostingSystem>HighWire Press</ContentHostingSystem>

     <OnlinePublisher>

          <PublishingRole>05</PublishingRole>

          <PublisherName>Stanford University Libraries</PublisherName>

     </OnlinePublisher>

     [29 Serial version composites would appear here]

</SubscriptionProductRecord>

<ONIXSPSProductListPriced> <SubscriptionProductRecord>
<NotificationType>

Mandatory within <SubscriptionProductRecord>

Not repeatable

 

Indicates whether this <SubscriptionProductRecord> is a new record, a deletion, or an update.

 

If <CompleteFile/> is present in the message header (that is, this is a complete replacement file), then <NotificationType> will always be “00”.

 

If <DeltaFile/> is present in the message header (that is, this message is an update file), then <NotificationType> will be either “05” to indicate that the subscription product is to be deleted; “06” to indicate that this is a new subscription product, or “07” to indicate that this subscription product record is a replacement of a previously transmitted subscription product record.

 

Note that each subscription product record must itself be complete, since there is no provision for updating at the element level.

 

Permissible code values:

00 Unspecified

05 Delete

06 New

07 Update (complete replacement)

<ONIXSPSProductListPriced> <SubscriptionProductRecord>
<SubscriptionProductIdentifier>

Optional within <SubscriptionProductRecord>

Repeatable if there are identifiers with different IDTypes

 

Identification of a subscription product, using a value from a standard or proprietary identification scheme.

<SubscriptionProductRecord> must contain either <SusbcriptionProductIdentifier> or <SusbcriptionProductName> or both.

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SubscriptionProductIdentifier>
<SubscriptionProductIDType>

Mandatory within <SubscriptionProductIdentifier>

Not repeatable

 

A code indicating the scheme or standard from which the Subscription Product identifier is taken. If <SubscriptionProductIDType> is “01” (proprietary), then the name of the scheme should appear in <IDTypeName>.

 

 

Permissible code values:

01 Proprietary

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SubscriptionProductIdentifier>
<IDTypeName>

Optional within <SubscriptionProductIdentifier>

Not repeatable

 

The name of the identification scheme from which the <IDValue> is taken, used only when <SubscriptionProductIDType> is “01” (proprietary).

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SubscriptionProductIdentifier>
<IDValue>

Mandatory within <SubscriptionProductIdentifier>

Not repeatable

 

An identifier of the type indicated in <IDTypeName>

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord>
<SubscriptionProductName>

Optional within <SubscriptionProductRecord>

Not repeatable

Has “language” attribute.

 

The name given to the subscription product by the sender.

 

<SubscriptionProductRecord> must contain either <SusbcriptionProductIdentifier> or <SusbcriptionProductName> or both.

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord>
<SubscriptionProductDescription>

Optional within <SubscriptionProductRecord>

Not repeatable

 

Free text description of the subscription product.

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord>
<ContentHostingSystem>

Optional within <SubscriptionProductRecord>

Not repeatable

 

The name of the system through which all online serial versions in this subscription product are available. Used only when all online serial versions are available through a single content hosting system. If present, there will be no <ContentHostingSystem> elements in the serial versions in this <SubscriptionProductRecord>.

 

This could be used, for example, when a subscription product consists of a number of online serial versions accessible through one content hosting system, as in the case of a hosted collection. It could also be used when a subscription product consists of a mix of online and print serial versions, and all the online serial versions are accessible though the same content hosting system.

 

Please refer to the ONIX Serials Glossary for definitions of terms.

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord>
<OnlinePublisher>

Optional within <SubscriptionProductRecord>

Not repeatable

 

The organization that hosts or distributes the online serial versions in this subscription product. This may or may not be the same organization as the publisher of the works, and it may or may not have the same name as a content hosting system.

 

This could be used, for example, when a subscription product consists of a number of online serial versions hosted by the same organization, as in the case of a hosted collection. It could also be used when a subscription product consists of a mix of online and print serial versions, and all the online serial versions are hosted by the same organization.

 

<OnlinePublisher> must contain either <PublisherIdentifier> or <PublisherName> or both.

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <OnlinePublisher>
<PublishingRole>

Mandatory within <OnlinePublisher>

Not repeatable

 

The role of the publisher; in this context, always “05” (host/disributor on electronic content)

 

Permissible code values:

05 Host/distributor of electronic content

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <OnlinePublisher>
<PublisherIdentifier>

Optional within <OnlinePublisher>

Repeatable if there are multiple identifiers with different PublisherIDTypes.

 

Identification of a publisher using a value from a standard or proprietary identification scheme.

 

<OnlinePublisher> must contain either <PublisherIdentifier> or <PublisherName> or both.

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <OnlinePublisher> <PublisherIdentifier>
<PublisherIDType>

Mandatory within <PublisherIdentifier>

Not repeatable

 

A code indicating the scheme or standard from which the publisher identifier is taken. If <PublisherIDType> is “01” (proprietary), then the name of the scheme should appear in <IDTypeName>.

 

Permissible code values:

01 Proprietary

06 EAN-UCC GLN

07 SAN

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <OnlinePublisher> <PublisherIdentifier>
<IDTypeName>

Optional within <PublisherIdentifier>

Not repeatable

 

The name of the identification scheme from which the <IDValue> is taken, used only when <PublisherIDType> is “01” (proprietary).

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <OnlinePublisher> <PublisherIdentifier>
<IDValue>

Mandatory within <PublisherIdentifier>

Not repeatable

 

An identifier of the type specified in <PublisherIDType>.

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <OnlinePublisher>
<PublisherName>

Optional within <OnlinePublisher>

Not repeatable within <OnlinePublisher>

 

<OnlinePublisher> must contain either <PublisherIdentifier> or <PublisherName> or both.

 

The name of the online publisher

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord>
<SerialVersion>

Mandatory within <SubscriptionProductRecord>

Repeatable for each serial version included in the subscription product

 

Details of a serial version included in the subscription product. There will be at least one serial version in each subscription product. A serial version is a manifestation of a work.

 

Either <SerialVersionIdentifier> or <SerialWork> must always be present in <SerialVersion>.

<SerialVersionForm> must always be present in <SerialVersion>.

 

 

Example: this example includes 2 Serial Versions, for a subscription product that includes the print plus online versions of a journal. The first Serial Version is for the print version, and the second for the online version.

 

<SerialVersionName> has been omitted. Examples of <SerialWork>, <PhysicalVersionScope> and <OnlineVersionScope> may be found later in this document.

 

<SerialVersion>

     <SerialVersionIdentifier>

          <SerialVersionIDType>07</SerialVersionIDType>     07 = “ISSN”

          <IDValue>13679430</IDValue>          ISSN for the print version

     </SerialVersionIdentifier>

     <SerialWork>

          [Serial Work information would appear here]

     </SerialWork>

     <SerialVersionForm>JB</SerialVersionForm>     JB = “Printed Serial”

     <PhysicalVersionScope>

          [Physical Version Scope information would appear here]

     </PhysicalVersionScope>

</SerialVersion>

<SerialVersion>

     <SerialVersionIdentifier>

          <SerialVersionIDType>07</SerialVersionIDType>     07 = “ISSN”

          <IDValue>14691795</IDValue>          ISSN for the online version

     </SerialVersionIdentifier>

     <SerialWork>

          [Serial Work information would appear here]

     </SerialWork>

     <SerialVersionForm>JD</SerialVersionForm>     JD = “Electronic serial distributed online”

     <OnlineVersionScope>

          [Online Version Scope information would appear here]

     </OnlineVersionScope>

</SerialVersion>

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion>
<SerialVersionIdentifier>

Optional within <SerialVersion>

Repeatable for identifiers with different IDTypes

 

A coded identifier of a serial version.

 

Either <SerialVersionIdentifier> or <SerialWork> must always be present in <SerialVersion>.

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <SerialVersionIdentifier>
<SerialVersionIDType>

Mandatory within <SerialVersionIdentifier>

Not repeatable

 

A code indicating the scheme or standard from which the serial version identifier is taken. If <SerialVersionIDType> is “01” (proprietary), then the name of the scheme should appear in <IDTypeName>.

 

An ISSN (IDType = “07”) should identify the serial version in question. An ISSN for a print version should not be used to identify an electronic version, and vice versa.

 

ISSNs are always sent in their unhyphenated form in ONIX.

 

Permissible code values:

01 Proprietary

06 DOI

07 ISSN (always sent unhyphenated in ONIX)

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <SerialVersionIdentifier>
<IDTypeName>

Optional within <SerialVersionIdentifier>

Not repeatable

 

The name of the identification scheme from which the <IDValue> is taken, used only when <SerialVersionIdentifier> is “01” (proprietary).

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <SerialVersionIdentifier>
<IDValue>

Mandatory within <SerialVersionIdentifier>

Not repeatable

 

An identifier of the type specified in <SerialVersionIDType>.

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion>
<SerialVersionName>

Optional within <SerialVersion>

Not repeatable

Has “language” attribute.

 

Name of the serial version. Used when the serial version has a unique name (different from the title of the serial work)

 

Example: <SerialVersionName>Science News Online</SerialVersionName>

[The work is titled “Science News”]

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion>
<SerialWork>

Optional within <SerialVersion>

Not repeatable

 

The work of which the <SerialVersion> is a manifestation.

 

Either <SerialVersionIdentifier> or <SerialWork> must be present in <SerialVersion>.

 

Example:

This Serial Work has 2 publishers with different Publishing Roles. It is published by one organization on behalf of another.

The <Imprint> and <MirrorSite> composites have been omitted.

 

<SerialWork>

     <SerialWorkIdentifier>

          <WorkIDType>01</WorkIDType>      01 = “proprietary”

          <IDTypeName>Agent’s product dentifier</IDTypeName>

          <IDValue>ANI0001</IDValue>

     </SerialWorkIdentifier>

     <Title>

          <TitleType>01</TitleType>               01 = “cover title”

          <TitleText>Animal Conservation</TitleText>

          <Subtitle>Quantitative studies for the conservation of populations, species and communities</Subtitle>

     </Title>

     <Imprint> may appear here

     <Publisher>

          <PublishingRole>01</PublishingRole>     01 = “Publisher”

          <PublisherIdentifier>

               <PublisherIDType>07</PublisherIDType>     07 = “SAN”

               <IDValue>1234567</IDValue>

               <PublisherName>Blackwell Publishing</PublisherName>

          </PublisherIdentifier>

     </Publisher>

     <Publisher>

          <PublishingRole>06</PublishingRole>     06 = “Published on behalf of”

          <PublisherIdentifier>

               <PublisherIDType>07</PublisherIDType>     07 = “SAN”

               <IDValue>1234567</IDValue>

               <PublisherName>Zoological Society of London</PublisherName>

          </PublisherIdentifier>

     </Publisher>

     <Website>

          <WebsiteRole>04</WebsiteRole>          04 = “Journal Home Page”

          <WebsiteDescription>Journal home page</WebsiteDescription>

          <WebsiteLink>http://www.blackwellpublishing.com/submit.asp?ref=1367-9430</WebsiteLink>

          <MirrorSite> may appear here

     </Website>

</SerialWork>

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <SerialWork>
<SerialWorkIdentifier>

Optional within <SerialWork>

Repeatable if there are multiple identifiers with different SerialWorkIDTypes.

 

Identification of a serial work using a value from a standard or proprietary identification scheme.

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <SerialWork> <SerialWorkIdentifier>
<SerialWorkIDType>

Mandatory within <SerialWorkIdentifier>

Not repeatable

 

A code indicating the scheme or standard from which the serial work identifier is taken. If <SerialWorkIDType> is “01” (proprietary), then the name of the scheme should appear in <IDTypeName>.

 

Permissible code values:

01 Proprietary

06 DOI

08 CODEN

11 ISTC

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <SerialWork> <SerialWorkIdentifier>
<IDTypeName>

Optional within <SerialWorkIdentifier>

Not repeatable

 

<IDTypeName> is the name of the identification scheme from which the <IDValue> is taken, used only when <SerialWorkIDType> is “01” (proprietary).

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <SerialWork> <SerialWorkIdentifier>
<IDValue>

Mandatory within <SerialWorkIdentifier>

Not repeatable

 

An identifier of the type specified in <SerialWorkIDType>

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <SerialWork>
<Title>

Mandatory within <SerialWork>

Repeatable for different types of the title

Has “language” attribute.

 

The title of the work of which the serial version is a manifestation.

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <SerialWork> <Title>
<TitleType>

Optional within <Title>

Not repeatable.

 

A code showing the type of title. If omitted, the title type defaults to “00” (undefined).

 

Permissible code values:

00 Undefined

01 Cover title

09 Sender's catalog title

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <SerialWork> <Title>
<TitleText>

Mandatory within <Title>

Not repeatable.

Has “language” attribute.

 

The text of the title, excluding subtitle. If multiple types of title are sent, the entire <Title> composite is repeated.

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <SerialWork> <Title>
<Subtitle>

Optional within <Title>

Not repeatable.

Has “Language” attribute.

 

The text of the subtitle, if there is one.

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <SerialWork>
<Imprint>

Optional within <SerialWork>

Not repeatable

 

The imprint under which the work is published.

May only appear if <Publisher> also appears within <SerialWork> or if <DefaultPublisher> appears in <Header>.

Must contain either <ImprintIdentifier> or <ImprintName> or both.

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <SerialWork> <Imprint>
<ImprintIdentifier>

Optional within <Imprint>

Repeatable if there are multiple identifiers with different ImprintIDTypes.

 

Identification of an imprint using a value from a standard or proprietary identification scheme.

 

<Imprint> must contain either <ImprintIdentifier> or <ImprintName> or both.

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <SerialWork> <Imprint> <ImprintIdentifier>
<ImprintIDType>

Mandatory within <ImprintIdentifier>

Not repeatable

 

<ImprintIDType> is a code indicating the scheme or standard from which the imprint identifier is taken. If <ImprintIDType> is “01” (proprietary), then the name of the scheme should appear in <IDTypeName>.

 

Permissible code values:

01 Proprietary

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <SerialWork> <Imprint> <ImprintIdentifier>
<IDTypeName>

Optional within <ImprintIdentifier>

Not repeatable

 

<IDTypeName> is the name of the identification scheme from which the <IDValue> is taken, used only when <ImprintIDType> is “01” (proprietary).

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <SerialWork> <Imprint> <ImprintIdentifier>
<IDValue>

Mandatory within <ImprintIdentifier>

Not repeatable

 

An identifier of the type specified in <ImprintIDType>

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <SerialWork> <Imprint>
<ImprintName>

Optional within <Imprint>

Not repeatable

 

The text name of the imprint.

 

<Imprint> must contain either <ImprintIdentifier> or <ImprintName> or both.

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <SerialWork>
<Publisher>

Mandatory within <SerialWork>, unless <DefaultPublisher> appears in <Header>

Repeatable for co-publishers or different Publisher Roles.

 

Publisher of the intellectual content of the work, if no <DefaultPublisher> was specified in <Header>, or if different from the default specified in <Header>; repeatable if there are co-publishers or if there are different Publisher Roles. If <SerialWork> <Publisher> appears, then <DefaultPublisher> will be ignored by the receiving system, for that <SerialWork>.

 

Must contain either <PublisherIdentifier> or <PublisherName>.

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <SerialWork> <Publisher>
<PublishingRole>

Mandatory within <SerialWork> <Publisher>

Not repeatable.

 

The role of the publisher. If a Serial Work has multiple co-publishers, then there will be multiple occurrences of <Publisher>, each with a Publishing Role of “02” (co-publisher). If a Serial Work has multiple publishers with different roles; e.g., published by one organization on behalf of another, then there will be multiple occurrences of <Publisher> with different Publishing Roles.

 

Permissible code values:

01 Publisher

02 Co-publisher

06 Published for/on behalf of

07 Published in association with

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <SerialWork> <Publisher>
<PublisherIdentifier>

Optional within <DefaultPublisher>

Repeatable if there are multiple identifiers with different PublisherIDTypes.

 

Identification of a publisher using a value from a standard or proprietary identification scheme.

 

<DefaultPublisher> must contain either <PublisherIdentifier> or <PublisherName> or both.

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <SerialWork> <Publisher> <PublisherIdentifier>
<PublisherIDType>

Mandatory within <PublisherIdentifier>

Not repeatable

 

A code indicating the scheme or standard from which the publisher identifier is taken. If <PublisherIDType> is “01” (proprietary), then the name of the scheme should appear in <IDTypeName>.

 

Permissible code values:

01 Proprietary

06 EAN-UCC GLN

07 SAN

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <SerialWork> <Publisher> <PublisherIdentifier>
<IDTypeName>

Optional within <PublisherIdentifier>

Not repeatable

 

The name of the identification scheme from which the <IDValue> is taken, used only when <PublisherIDType> is “01” (proprietary).

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <SerialWork> <Publisher> <PublisherIdentifier>
<IDValue>

Mandatory within <PublisherIdentifier>

Not repeatable

 

An identifier of the type specified in <PublisherIDType>.

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <SerialWork> <Publisher>
<PublisherName>

Optional within <Publisher>

Not repeatable

 

The text name of the publisher of the work.

 

<Publisher> must contain either <PublisherIdentifier> or <PublisherName> or both.

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <SerialWork>
<Website>

Optional within <SerialWork>

Repeatable if there is more than one website related to the serial work, other than mirror sites

 

Details of a website for the serial work as a whole; that is, the serial’s “home page.”

 

Example: This is the journal home page for the American Journal of Clinical Nutrition, which has a mirror site for access outside North America.

 

<Website>

     <WebsiteRole>04</WebsiteRole>          04 = “Journal home page”

     <WebsiteLink> http://www.ajcn.org/</WebsiteLink>

     <MirrorSite>

          <WebsiteDescription>For faster access from Australia, Brazil, China, France, Germany, Hong Kong, Ireland, Israel, Italy, Japan, Mexico, Russia, Singapore, South Africa, South Korea, Spain, Sweden, Switzerland, Taiwan, The Netherlands, UK<WebsiteDescription>

          <WebsiteLink> http://intl.ajcn.org/</WebsiteLink>

     </MirrorSite>

</Website>

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <SerialWork> <Website>
<WebsiteRole>

Mandatory within <Website>

Not repeatable

 

The role of a website. In this context, always “04” (journal home page).

 

Permissible code values:

04 Journal home page

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <SerialWork> <Website>
<WebsiteDescription>

Optional within <Website>

Not repeatable

 

A free-text description of the nature or function of a website.

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <SerialWork> <Website>
<MirrorSite>

Optional within <Website>

Repeatable for multiple mirror sites

 

Details of a site that mirrors a <Website>.

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <SerialWork> <Website> <MirrorSite>
<WebsiteDescription>

Optional within <Website>

Not repeatable

 

A free-text description of the nature or function of a website.

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion>
<SerialVersionForm>

Mandatory within <SerialVersion>

Not repeatable

 

A code indicating the medium in which the <SerialVersion> is delivered.

 

Permissible code values:

JB Printed serial

JC Serial distributed electronically by physical media such as CDROM

JD Electronic serial distributed online

MA Microform

MB Microfiche

MC Microfilm

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion>
<PhysicalVersionScope>

Optional within <SerialVersion>

Repeatable for multiple subscription periods.

 

Details of the range of issues included in a subscription to a printed or other physical serial version (eg CD-ROM) for a specified subscription period.

 

This composite will appear only if the <SerialVersionForm> is a physical medium; that is, “JB” (print), “JC” (physical electronic media), “MA” (microform), “MB” (microfiche), or “MC” (microfilm).

 

Either <PhysicalVersionScope> or <OnlineVersionScope>, but not both, may appear in a <SerialVersion>

 

Example:

This <PhysicalVersionScope> represents vol 9 no 1 (Feb 2006) through vol 9 no 4 (Nov 2006)

The <SubscriptionPeriodLabel> was set up in the message Header.

<JournalIssueDesignation> has been omitted from this Physical Verson Scope example.

 

<PhysicalVersionScope>

     <SubscriptionPeriodLabel>2006</SubscriptionPeriodLabel>

     <IssuesPerYear>4</IssuesPerYear>

     <JournalIssue>          First issue of the subscription period

          <JournalIssueRole>04</JournalIssueRole>          04 = “Start of range”

          <JournalVolumeNumber>9</JournalVolumeNumber>

          <JournalIssueNumber>1</JournalIssueNumber>

          <JournalIssueDate>

               <Calendar>00</Calendar>                    00 = “Gregorian”

               <DateFormat>01</DateFormat>          01 = “YYYYMM”

               <Date>200602</Date>

          </JournalIssueDate>

     </JournalIssue>

     <JournalIssue>          Last issue of the subscription period

          <JournalIssueRole>05</JournalIssueRole>          04 = “End of range”

          <JournalVolumeNumber>9</JournalVolumeNumber>

          <JournalIssueNumber>4</JournalIssueNumber>

          <JournalIssueDate>

               <Calendar>00</Calendar>                    00 = “Gregorian”

               <DateFormat>01</DateFormat>          01 = “YYYYMM”

               <Date>200611</Date>

          </JournalIssueDate>

     </JournalIssue>

</PhysicalVersionScope>

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <PhysicalVersionScope>
<SubscriptionPeriodLabel>

Mandatory within <PhysicalVersionScope>

Not repeatable

 

The subscription period to which this scope composite applies, using a label defined in the header. <SubscriptionPeriodLabel> must match a <SubscriptionPeriodLabel> found in a <SubscriptionPeriodDefinition> defined in <Header>.

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <PhysicalVersionScope>
<IssuesPerYear>

Optional within <PhysicalVersionScope>

Not repeatable

 

The number of issues published or expected to be published each year.

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <PhysicalVersionScope>
<JournalIssue>

Optional within <PhysicalVersionScope>

Repeatable

 

A range of issues included in the subscription period, specified in terms of the enumeration and/or chronology of the start and end of the range.

 

This composite is optional, but if it appears, there must be exactly 2 occurrences, one for the beginning and one for the end of the range.

 

At least one of <JournalVolumeNumber> or <JournalIssueNumber> or <JournalIssueDate> or <JournalIssueDesignation> must appear in <JournalIssue>.

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <PhysicalVersionScope> <JournalIssue>
<JournalIssueRole>

Mandatory within <JournalIssue>

Not repeatable

 

A code indicating whether this occurrence of <JournalIssue> specifies the beginning (“04”) or the end (“05”) of a range of issues.

 

Permissible code values:

04 From

05 To

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <PhysicalVersionScope> <JournalIssue>
<JournalVolumeNumber>

Optional within <JournalIssue>

Not repeatable

 

Volume number of the beginning or end of the range.

 

At least one of <JournalVolumeNumber> or <JournalIssueNumber> or <JournalIssueDate> or <JournalIssueDesignation> must appear in <JournalIssue>.

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <PhysicalVersionScope> <JournalIssue>
<JournalIssueNumber>

Optional within <JournalIssue>

Not repeatable

 

Issue number of the beginning or end of the range.

 

At least one of <JournalVolumeNumber> or <JournalIssueNumber> or <JournalIssueDate> or <JournalIssueDesignation> must appear in <JournalIssue>.

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <PhysicalVersionScope> <JournalIssue>
<JournalIssueDesignation>

Optional within <JournalIssue>

Not repeatable

 

Free-text description of the enumeration of the beginning or end of the range.

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <PhysicalVersionScope> <JournalIssue>
<JournalIssueDate>

Optional within <JournalIssue>

Not repeatable

 

Cover date of the beginning or end of the range of issues.

 

At least one of <JournalVolumeNumber> or <JournalIssueNumber> or <JournalIssueDate> or <JournalIssueDesignation> must appear in <JournalIssue>.

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <PhysicalVersionScope> <JournalIssue> <JournalIssueDate>
<Calendar>

Optional within <JournalIssueDate>

Not repeatable

 

A code indicating the calendar in which the date is given. If omitted, the default is "00” (Gregorian).

 

Permissible code values:

00 Gregorian (default)

01 Hebrew

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <PhysicalVersionScope> <JournalIssue> <JournalIssueDate>
<DateFormat>

Mandatory within <JournalIssueDate>

Not repeatable

 

A code indicating the format in which the date is given. Codes 06-11 are used in the case where the cover date of an issue is a range of dates.

 

Permissible code values:

00 YYYYMMDD

01 YYYYMM

02 YYYYWW

03 YYYYQ

04 YYYYS

05 YYYY

06 YYYYMMDDYYYYMMDD

07 YYYYMMYYYYMM

08 YYYYWWYYYYWW

09 YYYYQYYYYQ

10 YYYYSYYYYS

11 YYYYYYYY

12 Text string

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <PhysicalVersionScope> <JournalIssue> <JournalIssueDate>
<Date>

Mandatory within <JournalIssueDate>

Not repeatable

 

A date, or spread of dates, in the specified calendar and format.

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion>
<OnlineVersionScope>

Optional within <SerialVersion>

Repeatable for multiple subscription periods.

 

Details of the range of issues, online location(s), and completeness of content included in a subscription to an online serial version for a specified subscription period.

 

Must include <SubscriptionPeriodLabel> and <OnlinePackage>.

 

If an online serial version contained in a subscription product is available from multiple content hosting systems, then <OnlinePackage> will be repeated.

 

This composite will appear only if the <SerialVersionForm> is “JD” (electronic serial distributed online).

 

Either <PhysicalVersionScope> or <OnlineVersionScope>, but not both, may appear in a <SerialVersion>.

 

 

Example:

The <SubscriptionPeriodLabel> value was set up in the message Header.

Example of <OnlinePackage> may be found later in this document.

 

<OnlineVersionScope>

     <SubscriptionPeriodLabel>2006</SubscriptionPeriodLabel>

     <IssuesPerYear>4</IssuesPerYear>

     <OnlinePackage>

          [Online Package information would appear here]

     </OnlinePackage>

</OnlineVersionScope>

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <OnlineVersionScope>
<SubscriptionPeriodLabel>

Mandatory within <PhysicalVersionScope>

Not repeatable

 

The subscription period to which this scope composite applies, using a label defined in the header. <SubscriptionPeriodLabel> must match a <SubscriptionPeriodLabel> found in a <SubscriptionPeriodDefinition> defined in <Header>.

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <OnlineVersionScope>
<IssuesPerYear>

Optional within <PhysicalVersionScope>

Not repeatable

 

The number of issues published or expected to be published each year.

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <OnlineVersionScope>
<OnlinePackage>

Mandatory within <OnlineVersionScope>

Repeatable if the serial version is available through multiple content hosting systems or from multiple online publishers.

 

Details of online content for the specified serial version from a specified content hosting system or online publisher.

 

Example: This Online Package describes an online serial version available on Blackwell Publishing’s “Blackwell Synergy” platform, for subscription period “2006,” which was defined in the <Header>.

 

Examples of <PackageDetail> and <Embargo> may be found later in this document.

 

<OnlinePackage>

     <ContentHostingSystem>Blackwell Synergy</ContentHostingSystem>

     <OnlinePublisher>

          <PublishingRole>05</PublishingRole>          05 = Host/distributor of electronic content

          <PublisherIdentifier>

               <PublisherIDType>07<PublisherIDType>     07 = “SAN”

               <IDValue>1234567<IDValue>

          <PublisherName>Blackwell Publishing</PublisherName>

     </OnlinePublisher>

     <Website>

          <WebsiteRole>05</WebsiteRole>     05 = “Online journal 'available contents' page”

          <WebsiteLink>http://www.blackwell-synergy.com/loi/acv</WebsiteLink>

     </Website>

     <SubscriptionPeriodCoverage>     The issues made available during the subscription period.

          <JournalIssue>                    First issue of the subscription period

               <JournalIssueRole>04</JournalIssueRole>          04 = “Start of range”

               <JournalVolumeNumber>9</JournalVolumeNumber>

               <JournalIssueNumber>1</JournalIssueNumber>

               <JournalIssueDate>

                    <Calendar>00</Calendar>               00 = “Gregorian”

                    <DateFormat>01</DateFormat>          01 = “YYYYMM”

                    <Date>200602</Date>

               </JournalIssueDate>

          </JournalIssue>

          <JournalIssue>                    Last issue of the subscription period

               <JournalIssueRole>05</JournalIssueRole>          04 = “End of range”

               <JournalVolumeNumber>9</JournalVolumeNumber>

               <JournalIssueNumber>4</JournalIssueNumber>

               <JournalIssueDate>

                    <Calendar>00</Calendar>               00 = “Gregorian”

                    <DateFormat>01</DateFormat>          01 = “YYYYMM”

                    <Date>200611</Date>

               </JournalIssueDate>

          </JournalIssue>

     </SubscriptionPeriodCoverage>

     <PackageDetail>

          [<PackageDetail> information would appear here.]

     </PackageDetail>

     <Embargo>

          [<Embargo> information would appear here.]

     </Embargo>

</OnlinePackage>

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <OnlineVersionScope> <OnlinePackage>
<ContentHostingSystem>

Optional within <OnlinePackage>

Not repeatable

 

The name of the content hosting system through which the serial version is available. Will not appear if <ContentHostingSystem> has been specified at the product level, at the beginning of <SubscriptionProductRecord>.

 

Either <ContentHostingSystem> or <OnlinePublisher> or both may appear in <OnlinePackage>.

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <OnlineVersionScope> <OnlinePackage>
<OnlinePublisher>

Optional within <OnlinePackage>

Not repeatable

 

The organization that operates a content hosting system through which the serial version is available. Will not appear if <OnlinePublisher> has been specified at the product level.

 

Either <ContentHostingSystem> or <OnlinePublisher> or both may appear in <OnlinePackage>.

 

<OnlinePublisher> must contain either <PublisherIdentifier> or <PublisherName> or both.

 

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <OnlineVersionScope> <OnlinePackage> <OnlinePublisher>
<PublishingRole>

Mandatory within <OnlinePublisher>

Not repeatable

 

The role of the publisher; in this context, always “05” (host/disributor on electronic content)

 

Permissible code values:

05 Host/distributor of electronic content

<ONIXSPSProductListPriced> <SubscriptionProductRecord> <SerialVersion> <OnlineVersionScope> <OnlinePackage> <OnlinePublisher>
<PublisherIdentifier>

Optional within <OnlinePublisher>

Repeatable if there are multiple identifiers with different PublisherIDTypes.

 

Identification of a publisher using a value from a standard or proprietary identification scheme.

 

<OnlinePublisher> must contain either <PublisherIdentifier> or <PublisherName> or both.