Professional Documents
Culture Documents
Integration in Digital Library: Uniform Access To Loan Service
Integration in Digital Library: Uniform Access To Loan Service
Service
Ciro D'Urso
1 Introduction
2 Related Work
3 Background
Without loss of generality we can suppose that we deal with a consortium of libraries
supported by a central entity (Digital Libraries Center) in some general tasks (e.g.
management of consortium’s portal on the web with authentication and profiling
functions, provision of some common services such as digital imaging and centralized
billing). We state this hypotesis as H1:
H1 Membership and profiling. Each customer is associated to one and only one
library (called “personal library”), and the Digital Library Center (DLC) keeps
trace of this association. In addition the portal of DLC is able to profile the users
when they access the resource on the Web.
In the context that we are surveying, the scalability is a critical factor. We state
this requirement as R3:
R3 Support for evolution. The proposed architecture must be capable of adapting,
with minimum effort, to changes in the information systems of libraries connected
and to a growth of number of members.
When a user apply for a loan request, there could be some libraries not
connected to the system, because of network problems or maintenance activity.
Therefore the system must be able to queue events for disconnected clients until they
reconnect. We state this requirement as R4:
R4 Support for disconnection. The proposed architecture must assure message
delivery to subscribers even if they are disconnected.
4 Solution
4.1 Principles
P1 Multiple subscribers. All the libraries, connected to the P&S system and with
support of the loan functionality, are subscribers to events of the type “Request for
Loan” sent by the DLC.
P2 Single subscriber. Only the DLC is subscriber of events of the type “Response to
the Loan Request”, independently from which library has sent it.
In Figure 1 is depicted the logical view of the Loan System, notice that the P&S
system could be part of the Digital Library Center itself or could be managed by
another entity. In the context of a loan request, the interactions among user, DLC and
the P&S system, are the following (see the sequence numbers in Figure 1).
User Interface
1 Message
XML Parser Profiling
Generator
User 8 Engine
Library Selector
Publish/Subscribe System
3 5 4 6
Adapter Adapter
Digital Library Digital Library
A B
1: The user requests, by means of a single interface on the web, the availability of a
library item, using as identifier a unique code according to an international
standard (e.g. ISBN code);
2: The DLC acts as publisher and composes a “loan request” message, and assigns a
unique identifier to the request;
Integration in Digital Library: Uniform Access to Loan Service 5
3,4: All the libraries that can loan an item are subscribers to “loan request” event;
5,6: The adapter, after parsing the XML message, verifies the availability of the item
requested (e.g. the submission of a query SQL to the relational database
representing the catalogue), subsequently it publishes the response (item
available or not, from which library the message is sent, the identifier of the loan
request);
7: The DLC receives the events (according to P2 principle) and treats them, in order
to establish which library will be the lender. It stores all the responses for a
specific period of time (depending on the policy of consortium), afterwards it
processes them to find out the best choice in terms of time to delivery and costs;
8: The DLC sends an e-mail to user, telling if and when the item requested will be
available at the user’s personal library;
9: The library selected as lender sends the item to user’s personal library.
4.3 Adapter
The subjects cooperating through the P&S system can be outlined as domains with
own portfolio of applications and organizational rules. They interact through two
general entities: publication gate and subscription gate, as represented in Figure 2.
Broadly speaking the overall P&S system is constituted by the following components
(Figure 3):
• P&S Core System
• Publication Gate
• Subscription Gate
• Publication Gateway
• Subscription Gateway
The Core System is the heart of the P&S system, it realizes all the functionalities of
the model, providing the gates services of publication and subscription queue
management, administration services (definition of the events to be published,
subscription of particular events, modification of the subscription lists), and log
services. Therefore it consitutes a common component for the domains.
Publication and Subscription Gates decouple the domains from Core System. They
are developed, like the Core System, once for all and they do not need any
personalizations at application layer in order to install them in the particular domain
(typically they are developed in several versions only due to features of network and
trasport layers of each domains). They represent the standard interface with which
information systems of domains interact with Core System.
Publication and Subscription Gateway insulate the communication mechanism (the
gates) from the characteristics of each legacy system. Gateways act as the translator
between the legacy system and the gate, which in turn relays information to the core.
Because the gates are domain-independent, these gateways provide a coupling layer
between a particular legacy system’s characteristics and the generalities of the gate.
6 Ciro D'Urso
Publication Subscription
Gate Gate
P&S Core
System
Subscription Publication
Gate Gate
Domain A Domain B
Publication gates and gateways, along with subscription gates and gateways, are
the adapter for each domain. In publication, the adapter is responsible for composing
the message according to the established schema and delivering it to the core. In
subscription, on the other hand, the adapter picks up the message and processes it
based on its subject. The adapter is essential for integrating the publish-subscribe
system into the domain’s enviroment; it takes information in the form of data objects
that the core can use and converts it into data understood by the domain’s legacy
system, and vice versa.
PUBLISHER SUBSCRIBER
P S
U U
G G
L B B L
A A
E B S E
T T
G L. P&S Core C G
E E
A System R. A
W W
C G C
A A
Y A G Y
Y Y
T A
E T
E
DOMAIN A DOMAIN B
Adapter Adapter
Fig. 3. Layer view of event notification system and connection with domains.
Integration in Digital Library: Uniform Access to Loan Service 7
As general considerations about the model outlined so far, we have to take into
account at least two main issues: volume of data and metadata. Although the number
of messages distributed by the system doesn’t represent a problem due to scalable
solutions available as off-the-shelf software modules, the dimension of a single
message requires a detailed analysis based upon performance and capacity
requirements. Furthermore in order to effectively use the system, the actors have to
define some standards for the format of all possible messages and for the meaning of
each items in them. It is necessary an agreement about DTDs or XML Schemas,
meaning of each possible items in a message (e.g. items identification based on public
standards as, just to cite a few, ISBN, DOI, ONIX, ISRC, ISAN, ISMN), and each
possible types of message (e.g. agreement on all possible message subjects in an
subject-based implementation [9]). As an example of how the agreements could be
accomplished we can consider the principle P1 previously introduced. We can
insulate the main concepts to be analyzed in the definition of the structure of the
message "Request for Loan" considering the framework defined by the "Delos
reference model" [13]. In particular we have to deal with concepts of the Content
Domain such as Information Objects, so we consider some of the main characteristics
such as Resource identifier and Resource Format. Note that the identifier here is
referred to the library items and not to the corresponding metadata, however would be
also worth analyze the use of a common format based on standards such as URI (RFC
2396) for the identification of the metadata items in the repository of a generic library.
Furthermore similar characteristics have to be taken into account for the concepts
belonging to User Domain besides the Profile of the actors of the overall system. The
Policy Domain is also involved, in terms of Request Management Policies (e.g.
category of the request: normal, urgent). Therefore for the event "Request for Loan"
all the actors involved should be able to elaborate messages structured in accordance
with a kind of W3C XML Schema such as that represented in figure 4.
Fig. 4. Design view of the XML Schema of the message "Request for Loan".
8 Ciro D'Urso
The interaction steps described for dealing with a loan request have as a main aspect
the need to choose which library is the lender for a particular item. The elaboration is
based on the two parameters: time and cost. How do the two dimensions interact?
Time to deliver depends on the "distance" (in terms of physical space and means of
shipping) between the lender and the borrower, and also on the storing period applied
by the system (the average time the system waits before process a request, in order to
allow temporary disconnected library to respond, and in order to organize a shipping
with the optimal number of items). On the other hand cost parameter depends on the
same concept of "distance" and on the shipping policiy adopted. Therefore the system
has to calculate the trade-off between time and cost as functions of number of items
per shipping between one borrower and one lender, as depicted in figure 4.
Time
Cost
5 Conclusion
In this paper we described a system able to supply an uniform access to the loan
service. We stated some requirements and decided to base the system on P&S
paradigm. The implementation of logic flow is very simple, on the other hand
developement activities are necessary in order to design adapters for each library.
There are some issues related to Library Selector component (see Figure 1) that give
some grades of freedom in the choice of DLC policy (e.g. how long it waits before
sending an e-mail to user, what features have to be taken into consideration in order to
select the best lender). In addition the system proposed can be used for other
objectives involving asyncronous communications among libraries belonging to a
consortium.
Integration in Digital Library: Uniform Access to Loan Service 9
6 References
1. Goncalves, M.A., France, R.K., Fox, E.A., MARIAN: Flexible Interoperability for
Federated Digital Libraries. In Proceedings of the 5th European Conference on Research
and Advanced Technology for Digital Libraries, Darmsdadt, Germany, 2001
2. Khalil-Ibrahim, I., Schwinger, W., Data Integration in Digital Libraries: Approaches and
Challanges
3. Leiner, B.M., The NCSTRL Approach to Open-Architecture for Confederated Digital
Library. D-Lib Magazine, December, 1998
4. Levy, A.Y., Logic-Based Techniques in Data Integration. In Minker, J., Logic Based
Artificial Intelligence, Kluwer Publishers, 2000
5. Melnik, S., Garcia-Molina, H., Paepcke, A., A Mediation Infrastructure for Digital Library
Services. In Proceedings 5th ACM DigitalLibraries, San Antonio, 2000 pp. 123-132
6. Nelson, M., Maly, K., Zubair, M., Interoperable Heterogeneous Digital Libraries.
September, 1998
7. Oki, B., Pfluegl, M., Siegel, A., Skeen, D., The Information Bus – An Architecture for
Extensible Distributed Systems. In Proceedings of the 13th ACM Symposium on Operating
Systems Principles, Asheville, NC, December 1993, pp. 58-68
8. Paepcke, A., Chang, C.K., Winograd, T., Garcia-Molina, H., Interoperability for digital
libraries worldwide. Communications of the ACM, 41(4), 1998, pp. 33-42.
9. D. Powell. Group Communications. In Communications of the ACM, 39:4, pages 50-97,
April 1996.
10.ISO ILL Protocol Standards, http://www.nlc-bnc.ca/iso/ill/standard .htm
11.OCLC On Line Computer Library Center Inc., http://www.oclc.org.
12.Il Servizio di Prestito Interbibliotecario in SBN, http://www.iccu.sbn.it/servill.html.
13.The DELOS Digital Library Reference Model,
http://www.delos.info/index.php?option=com_content&task=view&id=345#reference_mod
el.