Interlibrary Loan Protocol
Implementors Group (IPIG)
DirectoryServices for InterlibraryLoan – Information Model
Diagrams
Proposal to generalise to provide
core information model for the
new ISO 2146 directories
standard
Version 3
7 January 2003
Directory Services for Interlibrary Loan – GENERALISATION PROPOSAL
Version 3 -–7 Jan 2002
2
ILL Policy Directory – GENERALISATION PROPOSAL
TABLE OF CONTENTS
1
SCOPE.......................................................................................................................................................................................... 1
2
OCCURRENCE SYMBOLS: ..................................................................................................................................................... 1
3
COLLECTINGAGENCYORGANISATIONALUNIT ............................................................................................................ 2
3.1
UNITNAME ............................................................................................................................................................................. 3
3.2
SERVICEROLES ....................................................................................................................................................................... 3
3.3
UNITSTATUS........................................................................................................................................................................... 3
3.4
SCOPENOTES .......................................................................................................................................................................... 3
3.5
SYMBOLCODES....................................................................................................................................................................... 4
3.6
ALIASES ................................................................................................................................................................................. 4
3.7
CONTACTINFORMATION .......................................................................................................................................................... 5
3.8
AFFILIATIONS ......................................................................................................................................................................... 5
3.9
INFOPOINTERS ........................................................................................................................................................................ 6
3.10
UNITDESCRIPTORS.................................................................................................................................................................. 6
3.11
SERVICES ............................................................................................................................................................................... 7
3.11.1
servicesSupportedSummary ......................................................................................................................................... 7
3.11.2
policyMatrix ................................................................................................................................................................. 8
3.11.3
serviceTimes................................................................................................................................................................. 9
3.11.4
protocolInformation ................................................................................................................................................... 10
3.11.5
requestsAcceptedFrom ............................................................................................................................................... 11
3.11.6
illServiceDescriptions ................................................................................................................................................ 12
3.11.7
illServicePolicies........................................................................................................................................................ 13
3.11.7.1
loanPolicy ......................................................................................................................................................... 14
3.11.7.2
copyPolicy......................................................................................................................................................... 15
3.11.7.3
locationsPolicy .................................................................................................................................................. 16
3.11.7.4
estimatesPolicy.................................................................................................................................................. 17
3.11.7.5
responderSpecificServicePolicy ........................................................................................................................ 18
3.11.8
serviceCharges........................................................................................................................................................... 19
3.12
NOTES .................................................................................................................................................................................. 20
3.13
COMMON DATA OBJECTS .................................................................................................................................................... 21
3.13.1
any ............................................................................................................................................................................. 21
3.13.2
billingMethod ............................................................................................................................................................. 21
3.13.3
ContactDetails ........................................................................................................................................................... 22
3.13.4
copyMethodAndMedium ............................................................................................................................................ 23
3.13.5
deliveryMethod .......................................................................................................................................................... 23
3.13.6
exclude ....................................................................................................................................................................... 23
3.13.7
mediumType ............................................................................................................................................................... 24
3.13.8
paymentMethod .......................................................................................................................................................... 24
3.13.9
requestMethod ........................................................................................................................................................... 24
3.13.10 seqLangString ............................................................................................................................................................ 25
4
DATA TYPES ............................................................................................................................................................................ 26
Version 3 -–7 Jan 2002
i
ILL Policy Directory – GENERALISATION PROPOSAL
Change Control
Date
7/1/03
Who
KB
Version 3 -–7 Jan 2002
What
Change repeats on notes in requests accepted from to 0-1
ii
1
Scope
This document contains the graphical information models for the ILLPolicy Directory incorporating proposals for generalising the
information model to provide the core information model for the new ISO 2146 directory standard. The information models profiles
2146 for ILL Services
2
Occurrence Symbols:
none
The element must appear once and only once.
MinOccurs=1
MaxOccurs=1
?
The element (or group of elements) may appear zero or one times.
The element is optional, but is only allowed to appear once.
MinOccurs=0
MaxOccurs=1.
+
The element (or group of elements) must appear one or more
times. The element is required to appear at least once, but multiple
consecutive occurrences may be present.
MinOccurs=1
MaxOccurs=*
*
The element (or group of elements) may appear zero or more
times. The element can appear as many times consecutively as
needed, or even zero times.
MinOccurs=0
MaxOccurs=*
{}
The element (or group of elements) must appear within the
specified range.
Version 1.1/ 29 August 2002
.
Set occurrence range
Set occurrence range.
1
ILL Policy Directory – GENERALISATION PROPOSAL
3
CollectingAgencyOrganisationalUnit
(CollectingAgencyOrganisation included for information)
No
Name
Req
Mult
1
unitName
M
1
2
serviceRoles
M
1
3
unitStatus
M
1
4
scopeNotes
O
0-1
5
symbolCodes
M
1
6
aliases
O
0-1
6
contactInformation
M
1
7
affiliations
O
0-1
8
infoPointers
O
0-1
9
unitDescriptors
M
1
10
services
M
1
11
Notes
O
0-1
Version 3 -–7 Jan 2002
2
ILL Policy Directory – GENERALISATION PROPOSAL
3.1
unitName
3.2
serviceRoles
3.3
unitStatus
3.4
scopeNotes
Version 3 -–7 Jan 2002
3
ILL Policy Directory – GENERALISATION PROPOSAL
3.5
symbolCodes
3.6
aliases
Version 3 -–7 Jan 2002
4
ILL Policy Directory – GENERALISATION PROPOSAL
3.7
contactInformation
(See Contact Details for full expansion of addresses)
3.8
affiliations
Version 3 -–7 Jan 2002
5
ILL Policy Directory – GENERALISATION PROPOSAL
3.9
infoPointers
3.10 unitDescriptors
Version 3 -–7 Jan 2002
6
ILL Policy Directory – GENERALISATION PROPOSAL
3.11 services
3.11.1
servicesSupportedSummary
Version 3 -–7 Jan 2002
7
ILL Policy Directory – GENERALISATION PROPOSAL
3.11.2
policyMatrix
Version 3 -–7 Jan 2002
8
ILL Policy Directory – GENERALISATION PROPOSAL
3.11.3
serviceTimes
Version 3 -–7 Jan 2002
9
ILL Policy Directory – GENERALISATION PROPOSAL
3.11.4
protocolInformation
Version 3 -–7 Jan 2002
10
ILL Policy Directory – GENERALISATION PROPOSAL
3.11.5
requestsAcceptedFrom
Version 3 -–7 Jan 2002
11
ILL Policy Directory – GENERALISATION PROPOSAL
3.11.6
illServiceDescriptions
(See Common Data Objects for full expansion of method objects)
Version 3 -–7 Jan 2002
12
ILL Policy Directory – GENERALISATION PROPOSAL
3.11.7
illServicePolicies
Version 3 -–7 Jan 2002
13
ILL Policy Directory – GENERALISATION PROPOSAL
3.11.7.1
loanPolicy
Version 3 -–7 Jan 2002
14
ILL Policy Directory – GENERALISATION PROPOSAL
3.11.7.2
copyPolicy
Version 3 -–7 Jan 2002
15
ILL Policy Directory – GENERALISATION PROPOSAL
3.11.7.3
locationsPolicy
Version 3 -–7 Jan 2002
16
ILL Policy Directory – GENERALISATION PROPOSAL
3.11.7.4
estimatesPolicy
Version 3 -–7 Jan 2002
17
ILL Policy Directory – GENERALISATION PROPOSAL
3.11.7.5
responderSpecificServicePolicy
Version 3 -–7 Jan 2002
18
ILL Policy Directory – GENERALISATION PROPOSAL
3.11.8
serviceCharges
(See Common Data Objects for full expansion of Charge Description objects)
Version 3 -–7 Jan 2002
19
ILL Policy Directory – GENERALISATION PROPOSAL
3.12 notes
Version 3 -–7 Jan 2002
20
ILL Policy Directory – GENERALISATION PROPOSAL
3.13 Common Data Objects
3.13.1
any
3.13.2
billingMethod
Version 3 -–7 Jan 2002
21
ILL Policy Directory – GENERALISATION PROPOSAL
3.13.3
ContactDetails
The context of the address must be able to be discovered unambiguously. Eg distinguished by Physical Address Types or by dates
that are different.
Version 3 -–7 Jan 2002
22
ILL Policy Directory – GENERALISATION PROPOSAL
3.13.4
copyMethodAndMedium
3.13.5
deliveryMethod
3.13.6
exclude
Version 3 -–7 Jan 2002
23
ILL Policy Directory – GENERALISATION PROPOSAL
3.13.7
mediumType
3.13.8
paymentMethod
3.13.9
requestMethod
Version 3 -–7 Jan 2002
24
ILL Policy Directory – GENERALISATION PROPOSAL
3.13.10 seqLangString
Version 3 -–7 Jan 2002
25
ILL Policy Directory – GENERALISATION PROPOSAL
4
Data Types
The data types are presented here in alphabetical order
Name:
Definition:
Example Data Element:
boolean
Supports the mathematical concept of binary-logic, having a value of either TRUE or FALSE.
ILLActiveStatus
Name:
Definition:
DateTime
DateTime epresents a specific instant in time. The value space of dateTime is the space of the
combinations of date and time of day from Section 5.4 of ISO 8601.
Representation:
A single lexical representation, which is a subset of the lexical representations defined by ISO 8601, is
allowed. This lexical representation is the ISO 8601 extended format CCYY-MM-DDThh:mm:ss.sss
where “CC” represents the century , “YY” the year, “MM” the month, and “DD” the day, preceded by
an optional leading sign to indicate a negative number. If the sign is omitted, “+” is assumed. The letter
“T” is the date/time separator, and “hh”, “mm” and “ss.sss” represent hour, minute, and second
respectively. Additional digits may be used to increase the precision of fractional seconds if desired.
To accommodate year values greater than 9999 additional digits may be added to the left of this
representation. The year 0000 is prohibited.
This representation MUST be followed immediately by a “Z” to indicate Coordinated Universal Time
(UTC). To indicate a specific time zone, i.e., the difference between local time and Coordinated
Universal Time, the difference immediately follows the time and consists of a sign (“+” or “-”)
followed by hh:mm.
Example Usage:
Example Data Element:
2000-06-15T11:30Z
2000-11-10T12:20:30.1Z-05:00
2000-09-14T18:49:12.061Z+02:00
ValidTo
Name:
Definition:
Day
Day represents a day of the week. The value space of day is the day of the week from Section 5.2.3 of
ISO 8601.
Lexical Representation:
Day of the week is represented by one decimal digit. Monday shall be defined as day [1] of any
calendar week, and subsequent days of the same week shall be numbered in ascending sequence to
Sunday (day [7])
Example Usage:
Example Data Element:
5
DayofWeek
Name:
Definition:
Decimal
Decimal represents arbitrary precision decimal numbers. The ·value space· of decimal is the set of the
values i × 10^-n, where i and n are integers such that n >= 0. The ·order-relation· on decimal is: x < y
iff y - x is positive.
Representation:
Decimal has a lexical representation consisting of a finite-length sequence of decimal digits (#x30#x39) separated by a period as a decimal indicator. An optional leading sign is allowed. If the sign is
omitted, "+" is assumed. Leading and trailing zeroes are optional. If the fractional part is zero, the
period and following zero(es) can be omitted.
Example Usage:
0.5
+4
IncrementQuantity
Example Data Element:
Version 3 -–7 Jan 2002
26
ILL Policy Directory – GENERALISATION PROPOSAL
Name:
Definition:
Example Data Element:
Name:
Definition:
Empty
An element that contains no data and indicates, by its presence or absence, a predefined condition or
situation. For example, the empty element NoServiceOffered in ILLServices indicates that this ILL
Procesing Unit does not provide any ILL services.
Any
Example Data Element:
PositiveInteger
PositiveInteger is an integer whose minimum value is a positive 1. The value space of positiveInteger
is the infinite set of positive numbers {1,2,3,…}.
15
200
PreferenceSequenceNo
Name:
String
Definition:
a string of letters, numbers, and punctuation, without any predefined properties for the processing of
the data
library
money
Smith
Surname
Example Usage:
Example Usage:
Example Data Element:
Name:
Definition:
Representation:
Example Usage:
Example Data Element:
Time
Time represents an instant of time that recurs every day. The ·value space· of time is the space of time
of day values as defined in Section 5.3 of ISO8601. Specifically, it is a set of zero-duration daily time
instances.
The lexical representation for time is the left truncated lexical representation for dateTime:
hh:mm:ss.sss. This representation MUST be followed immediately by a “Z” to indicate Coordinated
Universal Time (UTC). To indicate a specific time zone, i.e., the difference between local time and
Coordinated Universal Time, the difference immediately follows the time and consists of a sign (“+” or
“-”) followed by hh:mm.
13:20:00Z-05:00
18:49:12Z+02:00
ServiceHoursStartTime
Name:
Definition:
uriReference
uriReference represents a Uniform Resource Identifier Reference (URI). This type should be used to
specify the intention that the value fulfills the role of a URI as defined by [RFC 2396], as amended by
[RFC 2732].
Representation:
The ·lexical space· of anyURI is finite-length character sequences which are legal URIs according to
[RFC 2396], as amended by [RFC 2732]. NOTE: Spaces are, in principle, allowed in the ·lexical
space· of anyURI, however, their use is highly discouraged (unless they are encoded by %20).
http://www.nlc-bnc.ca/iso/ill/main.htm
http://www.nla.gov.au
URI
Example Usage:
Example Data Element:
Version 3 -–7 Jan 2002
27