How to Develop Functionality Around the Voyager System - or why you never should reconsider your...

19
How to Develop Functionality Around the Voyager System - or why you never should reconsider your workflow issues Tomas Friberg / LIBRIS

Transcript of How to Develop Functionality Around the Voyager System - or why you never should reconsider your...

Page 1: How to Develop Functionality Around the Voyager System - or why you never should reconsider your workflow issues Tomas Friberg / LIBRIS.

How to Develop Functionality Around the Voyager System

- or why you never should reconsider

your workflow issues

Tomas Friberg / LIBRIS

Page 2: How to Develop Functionality Around the Voyager System - or why you never should reconsider your workflow issues Tomas Friberg / LIBRIS.

History of LIBRIS

• Why this lecture? - Inspiration• Workflow issues and the Clash of Cultures• Tradition & Openness• 1975– Mainframe for cataloguing• 1987– National ILL System• 1998–2000 Dynix Horizon• January 2002 Live with voyager• National issues & Customer demands

Page 3: How to Develop Functionality Around the Voyager System - or why you never should reconsider your workflow issues Tomas Friberg / LIBRIS.

LIBRIS structure

• App. 9 million bib, 16 million MFHD• Some 350 libraries in LIBRIS• Co-operative cataloguing• ”Everyone” catalogues in LIBRIS• Every location is a library

– Or a bibliography

• No items• LIBRIS export data to local systems

Page 4: How to Develop Functionality Around the Voyager System - or why you never should reconsider your workflow issues Tomas Friberg / LIBRIS.

LIBRIS department• A project based working environment

– 5 Programmers/developers

– 2 Systems Librarians

– 2 Information

– 2 Support

– 1 Senior system administrator

– 1 Unix System Administrator

– 1 Technician

– 1 Training and ILL

– 1 Bibliographic questions

– 1 Deputy Director

– 1 Director

• Development– Java , XML & XSLT

– Visual basic, ASP

Page 5: How to Develop Functionality Around the Voyager System - or why you never should reconsider your workflow issues Tomas Friberg / LIBRIS.

Voyager system

Acquisitions

Circulation

WebVoyáge

Z39.50-serverILL

Cataloguing

Sysadmin

X X XXX

?Oracle DB Marcexport

X

ReporterCallslipXX

Page 6: How to Develop Functionality Around the Voyager System - or why you never should reconsider your workflow issues Tomas Friberg / LIBRIS.

LIBRIS system

TONE

WebSearch

LIBRIS ILL

LIBRIS XPLISENSE

Cataloguing

Sysadmin Oracle DBStatistics &

New Acq.

Support appl.

LIBRIZ

Library DB

Page 7: How to Develop Functionality Around the Voyager System - or why you never should reconsider your workflow issues Tomas Friberg / LIBRIS.

LIBRIS WebSearch

• Our equivalent of WebVoyage (1997-)

• Java, XML, XSLT on top of BRS

• App. 5 million records

• Nightly batch-export• Accessibility data (Loan status information)

• TONE - LIBRIS Z39.50 server– z3950.libris.kb.se:210/LIBR

Page 8: How to Develop Functionality Around the Voyager System - or why you never should reconsider your workflow issues Tomas Friberg / LIBRIS.

LIBRIS ILL

• Developed in 2001 by LIBRIS

• Webb and windows version

• App. 500.000 requests/year

• Some 1300 libraries use

• Retrieves bibrecords from voyager

Page 9: How to Develop Functionality Around the Voyager System - or why you never should reconsider your workflow issues Tomas Friberg / LIBRIS.

LIBRIS XP

• Some 15 different library systems• Export records

– Nightly batch export– Via LIBRIS XP (Windows)– Via a special web interface– Via Tone– Via WebSearch

• Conversions– Characters VRLIN, Latin-1 or Unicode– MARC manipulations– Information enhancement

Page 10: How to Develop Functionality Around the Voyager System - or why you never should reconsider your workflow issues Tomas Friberg / LIBRIS.

Import

• MatchMaker– Creation of MFHDs from a text file

• Regular import – LC, BNB & DB

• Deduplication program

• LISENSE & ZHarvester

• Web cataloguing

Page 11: How to Develop Functionality Around the Voyager System - or why you never should reconsider your workflow issues Tomas Friberg / LIBRIS.

Statistics & New Acquisitions

• Not sufficient to customer demands

• MySQL database (a Copy)– Data retrieved from voyager– Data processed– Data stored in ”presentation tables”

Page 12: How to Develop Functionality Around the Voyager System - or why you never should reconsider your workflow issues Tomas Friberg / LIBRIS.
Page 13: How to Develop Functionality Around the Voyager System - or why you never should reconsider your workflow issues Tomas Friberg / LIBRIS.
Page 14: How to Develop Functionality Around the Voyager System - or why you never should reconsider your workflow issues Tomas Friberg / LIBRIS.

Statistics & New Acquisitions

• Not sufficient to customer demands• MySQL database (a Copy)

– Data retrieved from voyager– Data processed– Data stored in ”presentation tables”

• New Books List / Michael Doran

• Swedish specific issues

• Generate reports on the fly

Page 15: How to Develop Functionality Around the Voyager System - or why you never should reconsider your workflow issues Tomas Friberg / LIBRIS.

Support applications

• LIBRIZ– A ”copy” of LIBRIS in MySQL

• Copy BibID

• ISSN-harvester

• Dewey/SAB concordance

• CXZ-listserv

Page 16: How to Develop Functionality Around the Voyager System - or why you never should reconsider your workflow issues Tomas Friberg / LIBRIS.

For and Against

• Vulnerability – Shovelling of data

• The right staff– Maintain their competence

• Control– Machines– Develop functionality– Customer needs

Page 17: How to Develop Functionality Around the Voyager System - or why you never should reconsider your workflow issues Tomas Friberg / LIBRIS.

Future

• A new cataloguing client– Project with Stockholm university library– Replace voyager cataloguing client and the

local systems cataloguing client

Page 18: How to Develop Functionality Around the Voyager System - or why you never should reconsider your workflow issues Tomas Friberg / LIBRIS.

Future system

Voyager cat client

Voyager DB

Local cat client

Local system DB

Page 19: How to Develop Functionality Around the Voyager System - or why you never should reconsider your workflow issues Tomas Friberg / LIBRIS.

Future system

LIBRIS Cat client

Voyager cat clientX

Voyager DB

Local cat client

XLocal system DB

LIBRIZ DB