AMICUS Circulation module, whose functions are defined according to different levels of permissions,manage users archives, check-in and charge-out functions, item status, fines policy, a loanreservation, inventory, various kinds of statistics.

LibriQuest (ILL)

The module allows system networked libraries, as well external librariest to share document deliveryservices and interlibrary loan functions, ina simplified and intuitive mode, through web technology.With LibriQuest is possible to create, validate, monitor and manage the flow of requests fordocuments in various formats and media, whether paper or digital.

RFID library management system

The integrated system that uses radio frequency inventory management procedures, shoplifting,circulation of documents, user management and reading rooms.

Overdue

Provides

a

complete

management

reminders

system,

including

notification

of

delay,

the

display

and

printing

of

items

borrowed,

reserved

and

in

transit

and

the

management

of

actions

to

be

taken

against

users

insolvent,

according

to

the

policies

set

up

by

each

single

branch

of

the

library.

Communications to library users (sms, e-mail, prints, …)(SMS Library)

Specialized application integrated with AMICUS, LibriQuest and Overdue, replaces the forms ofcommunication with the end users. These applications require the communications service, sendingrequests through the Internet connection. Compared to the ‘native’ system of communication, hasbeen added SMS (Short Message Service) and have been improved the existing procedures (e-mailand regular mail). It enables each library, with complete autonomy, to define the sending modalitiesto suit its own needs and policies. Also the end user has the ability to access his profile, and changehis personal data or to authorize a sending mode.

Copyright 2010 @CULT. All rights reserved

4

CIRCULATION

Current Circulation platform(3/3)

Copyright 2010 @CULT. All rights reserved

5

New Circulation platform

WELOAN

Copyright 2010 @CULT. All rights reserved

6

Target system

With contribution of Trento Province and

kind sponsorship of Luiss University

A

new

more

cohesive

(loose

coupling)

architecture,

through

a

system

refactoring:

•Service

oriented,

where

services

are

identified

as

the

main

reference

unit

of

the

system

•With

a

unified

and

centralized

presentation

layer

(thin

web-based

client

application,

browser

compatible).

•Built

on

an

Application

Server,

to

ensure

system

requirements

(e.g.

scalability,

security,

transactional,

robustness,

…)

•Standardized

communication

protocols

to

achive

the

highest

level

of

system

interoperability

•Full

usage

of

JEE

platform

components

to

provide

a

business

layer

with

high

degree

of

robustness

Copyright 2010 @CULT. All rights reserved

7

SOA-enabled architecture

Copyright 2010 @CULT. All rights reserved

8

Service Oriented Architecture (SOA)

What is a Service Oriented Architecture?

An SOA is a design model with a deeply rooted concept ofencapsulating application logic within services that interact via acommon communication protocol.

When services are implemented as “Web Services” and are usedto establish this communication framework, they basicallyrepresents a web-based implementation of a SOA.

Copyright 2010 @CULT. All rights reserved

9

Service Oriented Architecture (SOA)

What is a web service?

“A Web service is a software system designed to supportinteroperable machine-to-machine interaction over a network. Ithas an interface described in a machine-processable format(specifically WSDL). Other systems interact with the Web servicein a manner prescribed by its description using SOAP messages,typically conveyed using HTTP with an XML serialization inconjunction with other Web-related standards.”

Cite taken from http://www.w3.org/TR/ws-gloss/

Copyright 2010 @CULT. All rights reserved

10

SOA Roles

Copyright 2010 @CULT. All rights reserved

11

A SOA blueprint

Copyright 2010 @CULT. All rights reserved

12

An example (1)

Source: OLE Project

Deliver Entity

Process Module: Deliver Entity

Definition: The Deliver Entity component describes processes that track the request and supply

of a resource. It includes processes that initiate and receive the request, identify the user

requesting the resource, check and verify the user’s credentials, and determine availability and

terms of use of the resource requested. A message is sent to the user whenever a condition is

not met. The resource is supplied if all conditions are met.

Workflow / Process Diagrams:

Request Service

Identify User

Identify Terms of Use

Supply Entity

Use Cases: Request being created will take into account the completeness of the request, user

eligibility, and preconditions of use.

A user placing the request is authenticated and authorized. The user could be a person using a

computer, the computer itself, or a computer program and could use protocols such as LDAP,

Shibboleth, Secure Shell Keys, and Certificates.

The resource could be print or electronic, both returnable and consumable, an original or a copy,

local, consortial, purchased on demand or external to institutional ownership, retrieved from the

library and checked-out onsite or delivered to another location (library, office, desktop, off-campus

site.)

The requested resource is checked for availability, access attributes, and usage fees. For

example, do the resource attributes allow access by the requestor, such as enrollment in a

course or membership in a university or consortium? Must the resource be returned within a

specified timeframe or used in the library? Are there other preconditions such as copyright, usage

fees, or limits on number of simultaneous uses?

Copyright 2010 @CULT. All rights reserved

13

Process Module: Deliver Entity

Process Title: Request Service

Definition: Describes the process where a user submits a request for a service or resource. The

user may submit the request in person at a circulation desk, directly from a metadata record in a

licensed or open access database, or by filling out a free text web form.

Use Cases: A user is conducting research in a bibliographic database and identifies an article

she would like to read. The full text of the article is not available online in the database. She

clicks on a request button and submits a request for access to the entire article.

A professor recommends an article to a student. The student goes to his library’s website,

locates and fills out an interlibrary loan web request form, and submits a request for the article.

A student is searching his library’s catalog and locates a book that’s located in a remote storage

facility. He clicks on a request button and submits a request to have the book delivered to his

local campus library.

A student is searching WeCat and locates a resource that is not owned by his college library.

He clicks on a request button and submits a request to have another copy of the resource

delivered to his local campus library.

A professor is searching a regional consortia catalog with holdings from other college and

university libraries in his state. He identifies a copy of a resource owned by his university library

but it is checked out to another borrower. He clicks on a button and submits a request to have

another library’s copy delivered to his local campus library.

A student is searching Google and discovers a restricted audio resource in another university’s

digital repository. He clicks on a request button and submits a request to gain online access to

the resource.

An alumnus pulls a book from his college’s book stacks, takes it to the circulation desk, and asks