Report from IUG 2005

Inn Reach: De –

Mystified???Niamh Walker-Headon BA H Dip Lis

Systems Librarian, IT Tallaghtniamh.walker@it-tallaght.ie

What is InnReach• A Direct Consortial Borrowing System

– It creates a ‘Union Catalogue’ providing searchable access to materials held by the member libraries

– Patron Initiated direct requesting to member libraries.

– Since 1991, there are 20 InnReach systems• Ohiolink is the oldest InnReach consortium

Why use InnReach?• Cost Effective:

– Reminder - Why Resource Sharing?• You don’t own all material wanted by your patrons • you don’t have enough funds to buy everything • you don’t have space to house it all• you don’t have the staff to buy, process, catalogue, and

shelve it all

• Research: Association of Research Libraries Study in 2004 showed INN Reach is the cheapest option by far for filling ILLs

– Online Reference

Who can partake in InnReach?• INN-Reach Usage:

– All Types of Libraries – Academic, Public, Special, School

– In various locations – US, Andalusia, Hong Kong, UAE and New South Wales

– Various Library Management Softwares: Millennium, Dynix, Sagebrush, Follett, Sirsi, Horizon and TLC

• Uses NCIP interchange with non-Innovative ILS – (Michigan e-library)

• You don’t have to be a formal consortium to use InnReach

Aims

• The INN-Reach aims to provide Patron-Initiated Resource Sharing, via seamless integration with staff modules like Circulation, which is:– automated– with un-mediated processing– cost and time effective

Architecture

• The architecture of an Inn Reach System includes each library’s local server and the consortial server

• Searches and requests are facilitated via the Inn Reach server

• Patrons use the local server for validation and local branches for picking up materials

How does it happen?

• INN-Reach Request Process Steps:– Patron Searches– Patron Requests– Lending Library Supplies– Borrowing Library Receives– Item Circulates to Patron– Borrowing Library Returns Item– Lending Library Receives Item

How does work?

• It allows patrons from one library to request and borrow materials belonging to another library, unmediated by either library– Library staff need only take the book off the

shelf as a result of staff module integration

How Does it work?• Patron Status, is controlled locally, as

there are data protection issues about sending records to external servers that other institutions have access to– InnReach requests are integrated into local

patron records– InnReach is integrated with MILCIRC so

there is no need to learn a new interface– A virtual record is created for the item for

InnReach borrowing

What about lost materials?

• Loss of materials can be traced via the inbuilt reporting mechanisms

• Local agreement is needed on reimbursement– InnReach system can impose a higher loss

fee on the patron if you want

Pre-Implementation Requirements

• Put in place pre-agreed documents and policies such as:– Cataloguing agreements– Loan Rules and Parameters– Inter Library Loan agreements– Formal agreement to become a consortium

– if needed– Library Priority has to be decided by the consortia– Decide what parts of your local collection you

want to contribute to the consortium and all other parts can be suppressed within the InnReach Union Catalogue

Other Requirements

• System Administration and Coordination• Central server • Location and network configuration• System administration• Project leader• Overall coordinator/primary liaison to Innovative

More requirements…

• Representatives from each member system for Working committees

• Documentation and policies as required locally. • Catalogue creation• Circulation and document delivery• Public relations• Target dates for live usage by patrons• Implementation outline• Initial project consultation

So how long does it take?

• The time required to put the preparitory documents and the server in place– Staffing needs to be addressed, as does

training for the implementors• 3 months to implement the software• Relevant training time for local staff

– III provide on-site hands-on training

So how is the software implemented?

– Month 1: • Hardware and software setup• Innovative configures central server OS and software• Default INN-Reach profile established

– Month 2: • Sample catalogue• Consortia review and modify default profile

– Month 3: • Record load and circ setup• Records loaded from each local system• Catalogue built • Circulation profile configured• Training • Live

On going commitments

• Inn Reach is an ongoing project • Requires a staff commitment both

centrally and locally• For example - InnReach pick up notices are

sent the same as local ones• The working committees will also need

to stay in place, so the implementation of updates and changes is assured, timely and relevant– On-going revision of policy

Anything else commitment wise?

• Implementation of new features, product functionality and system options

• Updating the INN-Reach database is on going, constant and almost instantaneous

• Training• Staffing to look after Co-ordination,

WebOPAC development /Administration of other tasks– Most consortia seem to locate these staff

centrally

Other Modules and Services

• InnReach can or may in the future be able to work with– My Millennium

• Looks very different for InnReach– Inventory Express– FRBR (Functional Requirements for Bibliographic Records)

– Electronic Resource Management

• More Information– Presentation given at IUG 13– Online Manual Page # 105089– Users list– See live examples at OhioLink, and MeL

• Final proposal:• Work with whole of the third level education

sector and the public library sector on this project.

The End!