The Verde Implementation Project Presenter: Charles Woods, on behalf of the Verde Implementation Team: Linda Day, Wayne Johnston, Don Hamilton, Greg Sennema, Carol Stephenson, Debbie Tytko 1

Agenda Goal of the Verde Implementation project What is an ERM system What is Verde Background to the selection process Components of the Verde Implementation Project A brief demo Resources Questions 2

Goal of The Verde Implementation Project Simply put, the mandate of the Verde Implementation Group is to, “…oversee the acquisition, installation and configuration of the Verde ERM system; local programming to supplement the product; and staff training.” …and by December, too! 3

Sometimes it helps to sit down and think about the problem: What are we talking about? 4

What is Electronic Resource Management? Electronic Resource Management (ERM) is a term that refers to the practice of managing data and metadata about electronic resources acquired by libraries. 5

ERM (continued) What information is managed? Electronic Resource Management systems manage data about: e-resource trials the process of getting a license agreement negotiated and signed the content of the signed license agreement, such as usage restrictions the URL of the e-resource the location of the license agreement itself or a digital copy acquisition of the e-resource, such as subscription periods, invoices, and payment information contact information with the publisher or vendor usage access problems 6

What is Verde? Verde is the ERM system written and managed by ExLibris Part of the ExLibris approach to Unified Resource Management – the creation of an ILS that manages materials no matter the format a module that integrates with the overall information architecture of the traditional ILS, and with new information-discovery tools 7

Background 1.OCUL-ERM review in 2005 (including Linda Day, Nick Dobbin and Charles Woods) which inventoried needs and assessed vendor products, and made a qualified recommendation for Verde 2.TUG ERM Group, Phase 1 (Fall ‘06) Inventory of TUG ERM needs, and assess state of ERM technology Core recommendation: replace the current TUG ERM system with a state-of-the art ERM system 3.TUG ERM Group, Phase 2 (Spring ‘07) Match local requirements with available systems and recommend a choice Core recommendation: acquire and install 3 instances of Verde, one each for Guelph, Laurier and Waterloo, on the OCUL Verde server 8

Members of the Verde Implementation group Linda Day and Wayne Johnston of the University of Guelph Don Hamilton and Greg Sennema of Wilfred Laurier University, and now Carol Stephenson Debbie Tytko and Charles Woods of the University of Waterloo. …and a cast of hundreds! …and Screechy Scaly 9

TUG Requirements that had to be met… Acquire a system scalable to the demands of electronic resource management, no matter the media Reduce or eliminate redundant record maintenance amongst the ERM, SFX and TRELLIS systems Acquire a system that supports staff workflows and the natural life cycle of an electronic resource from trial through to evaluation and selection, acquisitions and purchase, and ultimately into production Acquire a system that better integrates with our ILS system, SFX, and Scholars Portal 10

Why Verde? Verde was recognized as best-of-class by the OCUL and TUG review groups, and by your participation in the vendor demonstrations Verde has been deployed by several of our OCUL partners – we have a community of users who can share discussions on common problems and solutions It is a hosted solution: management of the hardware, operating system and application software is performed by the OCUL support team in Toronto. 11

Why Verde (cont’d) OCUL (and TUG) already share the OCUL SFX system in Toronto The Verde and SFX systems manage complimentary knowledge databases that can be automatically synchronized, and … Will be merged into one database in 2008, eliminating duplicate record management. There will be links between the Verde ERM system and the TRELLIS ExLibris system and SFX 12

Sometimes it helps to sit down and think about the problem: What are the stages of the Implementation? 13

14 Project Planning Installation Training Customization Data Migration STP

Some Components of the Fall ‘07 Verde Implementation Project Knowledge Base issues (Linda, Don and Charles): The initial Verde KB for each institution will be converted from their SFX KB on the OCUL server Issues to identify, quantify and resolve: Records on the TUG ERM KB that are not on SFX and will not be converted Records on SFX that have not been activated and will not be converted Records on SFX with holdings that are not current State of TRELLIS cataloguing records etc… Identify means of updating/cleaning records via import and export loaders 15

Project Components (cont’d) Training and Workflows (Carol, Debbie and Linda) Two days of training by ExLibris in October or November 15 training slots, with auditing by others Investigation and familiarization with the Verde KB and the hierarchy of e-products: E-Interface E-Package E-constituent E-standalone Analysis of staffing and workflow changes required when the system goes live. Development of new procedures and policies Sourcing documentation from the vendor, OCUL and other friendly libraries. 16

Project Components Public Access (Wayne Johnston and Greg Sennema) Issues: Inventory current public interfaces to TUG ERM Plan means to replace and improve these interfaces to data from Verde and SFX Investigate possible interim options if the former takes time to implement (eg. The SFX A-Z list) consult with users to fine tune interfaces Develop the programming infrastucture to support interface development for Verde and other TUG initiatives. Planning documents and methodology are rapidly emerging on the TUG ERM wiki… fresh material just posted by Wayne and Greg 17

Project Components Communications (Charles, Don) Identify all the people and resources available for the project Identify particularly the support roles of staff at ExLibris and OCUL Participate vigorously in the OCUL-Verde listserv Communicate regularly with staff about the progress of the project, including postings to the new Tug Initiatives blog Encourage participation by staff where-ever possible 18

All of which should result in… A Verde instance for each TUG institution on the OCUL Verde server, appropriated configured for each institution, with a converted database, by December Post-implementation tasks: Update records and create records for local titles Continue refining public interfaces Investigate report and statistics capabilities Work on loader issues Decommission TUG ERM 19

Where are we right now? The contract has been signed Training dates are being arranged Instances are to be set up shortly, with Verde KBs being created from SFX KBs SFX cleanup already in progress with title/package activation Vigorous planning and analysis ongoing… 20

Lets sit back and look at Verde… 21

Verde demo 22

The new vocabularies 23

Verde Demo User: TST_administrator 24

A snapshot of a search … 25

26

All this results in Bach-like TUG Polyphony… 27

…and TUG Harmony ! 28

Verde Implementation Project Some Resources Tug Initiatives Page at Verde Implementation Project page Verde Implementation Project page on the TUG Wiki OCUL-Verde list OCUL Verde project documentation centre ExLibris documentation centre 29