9 Specifications and Mapping

Overview

ILL Direct Request recognizes five externals in the ILL-Request APDU. Externals are objects defined outside the ISO-ILL protocols either because they are specific to the responder or because they are extensions. Three of the externals are extensions to the ILL-Request. The externals are:

• responderSpecificService
• systemNo (part of itemId)
• AccessControlFormat-prompt-1 (extension)
• OCLCILLRequestExtension (extension)
• ILLSupplementalClientInfo (extension)

Table: Specifications and mapping

The following table details ASN.1 coding for OCLC’s version of the ISO ILL-Request. The table uses the following typographical conventions:

• All ASN.1 definitions, fields, tags, and values are shown in Courier type
  Example: deliveryAddress [6]

• The highest-level context-specific data fields appear in boldface for quicker visual reference
  Example: search type [12]

• Code in the table is within the context:
  ILL-Request [APPLICATION 1]
  SEQUENCE [UNIVERSAL 16]

• Tag numbers for ISO-10161 fields are shown in square brackets [ ] after the field name
  Example: deliveryAddress [6]

• Data represented by a code is shown with the definition in Courier followed by the value in parentheses
  Example: Loan (1)

• Definitions of externals and extensions appear in shaded boxes prior to the relevant coding

• An asterisk beside an OCLC ILL Field name denotes data supplied by the WorldCat bibliographic record matched during Direct-to-Profile processing. (Data in other fields is supplied by the ISO-10161 ILL-Request or constant data.)

ISO fields that are not mapped to the OCLC ILL workform or are not accompanied by Notes in this table are not used in OCLC’s application of the ISO ILL-Request, but must be present if required by the ILL-Request APDU. For example, requesterOptionalMessages is required, but not used.

Though not illustrated by this table, ILL Direct Request accepts GeneralString or EDIFACTString for the data type ILLString.

Client Extension

The following table lists each StandardClientInfoType defined by the client extension. For each, the table specifies:

• the ClientInfoContent choices for encoding it
• the OCLC ILL patron field to which it is mapped

Client Extension

The following table lists each StandardClientInfoType defined by the client extension. For each, the table specifies:

• the ClientInfoContent choices for encoding it
• the OCLC ILL patron field to which it is mapped

Additional rules for client data

Some other rules for mapping the client extension are:

• A ClientInfoData sequence with infoType local is ignored
• A ClientInfoData sequence with infoType standard is ignored if standard is set to an unsupported value
• If a ClientInfoData sequence has more than one infoContent, only the first supported one is retained
• A ClientInfoData sequence that does not include an infoContent supported for its infoType is ignored
• The value for statusCode is converted to its corresponding text

Precedence rules for client data

Client data may appear in 3 different locations in an ISO-10161 ILL-Request to OCLC:

• clientId
• ILLSupplementalClientInfo
• OCLCILLRequestExtension

In addition to the ILL-Request having more than 1 location for client data, the client extension itself can encode the same data many ways. If the same client data occurs more than once in the request, ILL Direct Request retains only one instance of it. The following table shows the order of precedence for the different forms and locations (ordered from highest to lowest).

Data from clientId takes precedence over data from ILLSupplementalClientInfo and data from ILLSupplementalClientInfo takes precedence over data from OCLCILLRequestExtension. The table also shows the concatenation rules for multiple pieces of data placed in the same field: order, labels, and punctuation.

Table: Precedence of Client Data

Maximum field lengths

The following table shows the maximum length of each OCLC ILL field to which ILL Direct Request maps data. Data that exceeds the maximum field length is truncated.