verde an introduction to version 2 taipei, june 2006 ted koppel verde product manager, ex libris
TRANSCRIPT
Verde An Introduction to Version 2
Taipei, June 2006
Ted KoppelVerde Product Manager, Ex Libris
2
Taipei, June 2006
Agenda
Verde’s architectural contextCurrent status of productVerde Version 2 – new featuresSome words about ConsortiaERM standards relevant to VerdeFuture plans for VerdeDemonstration of version 2Q&A
3
Taipei, June 2006
Interface
Standalone Package
Constituents (e-journals, e-books)
3
Hierarchical Data Structure Based On e-Product
4
Taipei, June 2006
Lower levels inherit
Interface
Package
Constituent
Access
Licensing
Costs
Trial Use
Administration
Acquisitions
Usage
e-Product info
5
Taipei, June 2006
Verde Architecture
Staff interface
3rd partyapplications
OpenURL
Web Services (SOAP)
5
6
Taipei, June 2006
What Verde Isn’t
A bibliographic maintenance systemA full scale acquisitions and payments systemAn OpenURL resolverAn A-to-Z list providerA Public Access CatalogAn Interlibrary Loan systemA public interface
However,
Verde works with all of the above supplying ERM information to these
applications
7
Taipei, June 2006
Verde – Overview of Customer Base
8
Taipei, June 2006
Verde Customers – Individual Institutions
61 Sales as of June 2006China
Tsinghua University (III)Denmark
Novo-nordisk Spain
Residencia de Estudiantes (Ex Libris)Universidad de Navarro (III)
SwitzerlandHoffman-La Roche Ltd.
United KingdomCranfield University (SirsiDynix)Liverpool John Moores University (Ex Libris)Nottingham Trent University (Ex Libris)University of Nottingham (Ex Libris)
9
Taipei, June 2006
Verde Customers – Individual Institutions
United StatesBristol Myers-SquibbCenters for Disease Control & Prevention (Endeavor)Harvard University (Ex Libris) *DEV. PARTNERMassachusetts Institute of Technology (Ex Libris) *DEV. PARTNERMemorial Sloan-Kettering Cancer Center (III)Southern Adventist University (Ex Libris)University of Iowa (Ex Libris)Vanderbilt University (SirsiDynix)Virginia Commonwealth University (Ex Libris)Yale University (Endeavor)
10
Taipei, June 2006
Verde Customers - Consortia
California Digital Library (Various)11 Sites
Five Colleges Consortia (Ex Libris)5 Sites
Florida Center for Library Automation (Ex Libris)20 sites
KOBV – Berlin (Various)Ontario Council of University Libraries (Various)
14 Sites
University of Maryland System (Ex Libris)17 Sites
11
Taipei, June 2006
Verde Product Roadmap
Version 1.0 (August 2005)Version 1.1 (November 2005)Version 2.0 (June 2006)
Service packs
Next major release: approx 8-9 months
ERM is a rapidly changing environment
12
Taipei, June 2006
Version 2 major enhancements
Role Based Authentication, Task Permissions, and Profile AssignmentWorkflow ManagementVerde Tasks and AlertingCopy and PasteLicense Attachment UploadsMulti-instance searchingReports and Batch Task schedulingLocal product WizardIncident and Breach LoggingNon-Roman language display
13
Taipei, June 2006
Status of Version 2
Development is complete; documentation being proofread and prepared for release
Demo site up and sales/support being trained
Early adopter installation mid-June
Release shortly after
14
Taipei, June 2006
Verde’s approach to Workflow
Workflow Engine
(task manager)
Alerts and E-mail
Roles assigned and tasks allowed
15
Taipei, June 2006
Roles, Profiles, and Permissions
Roles: High Level functions that you are assigned (License Manager, Webmaster, Acq. processing). Used by Workflow Manager to identify appropriate staff to notify
Permissions: Specific tasks/duties that you have permission to perform (assigned by the administrator). Note: by default there is a direct relationship between ROLES and PERMISSIONS but the library can modify the default to create its on set of relationships.
Profiles: Groups of permissions (arbitrarily) bunched together and used by administrator to save time
16
Taipei, June 2006
Workflows and tasks
Verde ships with three workflowsAcquisitionsLicensingRenewal/Review
Each workflow has several tasks pre-defined
All workflows and tasks can be configured by the customer
17
Taipei, June 2006
Workflows and tasks
Tasks can be internal or external to VerdeInternal: complete acquisitions record and approve itExternal: send copy of license to Attorney
Libraries can add up to 10 additional tasks for each workflow
Additional default workflows will be added as libraries identify their needs
Tasks are “accepted” by staff, and then marked as “completed”; end of one task triggers notification that next task is ready to be fulfilled
18
Taipei, June 2006
Copy and Paste Attribute Data
From one level to another (Interface to Package or Constituent)
From one Package to another
One copy/paste per attribute
*Most useful* for license attribute
Does not carry dates across copy/paste
19
Taipei, June 2006
New record wizard
Fast, prompted method of adding new local records to Verde KnowledgeBase
Replaces previous 12-13 step process
Result of wizard:New work record(s): package and interfaceNew interface e-product recordNew package e-product recordAll linked together as a logical group
20
Taipei, June 2006
Upload an attachment to the license
Any level e-product record
Multiple documents can be stored per record
.DOC, .XLS, .PDF and similar file types automatically open (depends on your system)
Stored as part of Unix/Linux file system
21
Taipei, June 2006
Search/retrieval changes
Single instance: Local or Global checkbox
Multi-instance: One, Some, All, +/- Global
New column displays holdings
Consortium navigation
22
Taipei, June 2006
Choose which instances to search
23
Taipei, June 2006
Multiple instances retrieved
24
Taipei, June 2006
Breach and incident logs
25
Taipei, June 2006
Breaches and Incidents
Expansion of DLF specificationCan be attached to any level of recordCollects what the problem was, timestamp, responsible person, disposition, and notes
Next step: allowing breach/incident log entry to automatically create email to vendor
26
Taipei, June 2006
Other changes in version 2
Improved/enhanced batch job and report schedulerAdditional reports, including consortiumVarious invisible infrastructural changes
Better sharing with SFXMore efficient indexing and updating on large setsMinor menu and screen changes for ergonomic reasons
27
Taipei, June 2006
Consortial Models
28
Taipei, June 2006
Parallel Consortium Model
1 2 3 4 5
29
Taipei, June 2006
Parallel Model
Share the same server(s)Share the same Oracle installation
But …Each instance has its own configurations, users, etc.Secure ‘walls’ between instancesAlmost complete autonomy if desiredMay allow read-only access if desired“Good fences make good neighbors”
30
Taipei, June 2006
Top-down model (central authority)
1 2 3 4 5
Central management of some sort
31
Taipei, June 2006
Top-down management
Many different flavors
Central authority can bepurchasing agent (and bill for costs)funding agentHardware/software hostDatabase quality – consistency managerVarious combinations of the above
32
Taipei, June 2006
Top down model
Central instance that does somethingMultiple individual instancesDepending on flavor, the individual instances may show
Only what the specific instance has bought for itselfEverything bought by Central on behalf of the individual instance
33
Taipei, June 2006
Hybrid top down model
1 2 3 4 5
Central management of some sort
6A
6B
6C
34
Taipei, June 2006
Hybrid top down or hybrid parallel
Central may directly manage certain smaller libraries or subsets of institutions
Larger libraries act as normal top down or parallel entities
35
Taipei, June 2006
No two consortia are alike !!!
Acquisitions and Purchasing rolesMessaging and availability to publicCost sharing formulasRole and influence of central authoritySFX and Metalib use and structureEtc.
Verde’s goal: build in configurability and flexibility within certain basic frameworks.
36
Taipei, June 2006
Why choose one model over another?
Service delivery - identity of library versus identity of consortiumManagement needs (reporting, fiscal)Purchasing model; financial support from central authorityAtmospherics – do consortial members get along?Atmospherics 2 - do the libraries’ parent institutions prefer individual attention and recognition?
37
Taipei, June 2006
Why choose? (2)
Economics – cost of ERM installation as individuals versus as consortium
Existing software (SFX, for example) model
38
Taipei, June 2006
Verde version 2 Consortial Features
In top-down modelMerged Master database of all holdings, all instancesAbility to search one, all, or any combination of instances, + or – GKB, in one operationAbility to see merged (automatically deduplicated) results labeled with instance(s) that own specific e-journalsAbility to jump from one instance’s holdings to another without having to re-execute searchVarious navigational short-cuts (breadcrumbs, filters, etc.)
..more..
39
Taipei, June 2006
Verde Consortia (2) – All models
Authentication“Home” authority different from “guest” authority
“Guest” authority set by host instnace
Cross-instance permissions (read, write, approve)
Role Based Authentication
Cross – instance attribute sharing allowing Copy/Paste across libraries
40
Taipei, June 2006
Cross instance reporting
Management reports that count individual factors, collect and aggregate
Subject to same permissions/rules as real-time access
41
Taipei, June 2006
Future consortial work (Version 2.5+)
Not just screen/attribute level cross-instance edit authority, but field-by-field edit authority
Cross-instance workflow alerting and notification; cross instance assignment of tasks
Cross-instance finance: assessment of costs, creation of billing invoice, collection of funds for shared purchases
42
Taipei, June 2006
Future (2)
Shared vendor and organization files
Cross-instance trial results collection
Collection development aids: cross instance scenarios and voting for desired package
Cross-instance license library (!)
43
Taipei, June 2006
Standards of relevance to Verde
Digital Library Federation Electronic Resources Management Initiative Specification (DLF-ERMI)
Published 2004Specifies Data elements, functions, interrelationshipsRevision / expansion began 2006
COUNTER (Counting Online User NeTwork Electronic Resources)
Defines data elements and XML format for usage statistics collection and distribution7+ reports detailing different statistical measures
44
Taipei, June 2006
Standards in ProcessSUSHI (Standardized Usage Statistics Harvesting Initiative)
Web service; describes protocol for request and receiving COUNTER-format statistics from publishersDevelopment continues. DSFTU status mid-late 2006.Members: ILS Vendors, subscription agents, content providers
License Expression Working Group Goal: to develop a single standard for the exchange of license information between publishers and librariesLed by DLF/ERMI2 and EDItEUR; 60+ membersBuilds on ONIX schemasFirst draft: summer/fall 2006
45
Taipei, June 2006
Version 2.5 – Early 2007
StatisticsAutomated Retrieval (SUSHI)Vertical Analysis Tools (InterfacePackageConstituent)Horizontal Analysis Tools (all use of Journal X regardless of how delivered)Single and Multiple Instance
46
Taipei, June 2006
Version 2.5 (2)
Multi-Language SupportUnderlying structure already in version 2Adding CJK searching in service packs
Advanced Searching Capabilities“Find all titles where I paid more than $5000 that expire in June 2006 where I do not have the right to make digital copies”
SSL (Secure Sockets)
47
Taipei, June 2006
Version 2.5 (3)
Workflow enhancementsApplication of rules at attribute level – when is a task considered complete?Additional Role Based Authentication enhancements
Consortium FunctionalityVoting mechanismGroup roles for cross-instance editing and functionCost splitting and billingLicense and SOAP responses based on incoming IP address
48
Taipei, June 2006
Verde 2.5 (4)
Minor GUI enhancementsHistory dropdownAutocomplete in searchChoice of # of results to be displayed“CLEAR” buttonSet dates manuallyNew fields: impact factor, etc.Add HH:MM where necessary
49
Taipei, June 2006
Verde 3 and Beyond
Verde KB enhancement with databases information (MetaLib and other sources)
Automated Loading of License Data (License Expression Work Group)
Store and Use multiple default records
GUI enhancements for user convenience
Open Access journal model support (!)
50
Taipei, June 2006
Verde 3 and beyond (2)
Dynamic cost calculation when shared percentages change
Support for multiple currencies, including exchange rate, date, calculation
“My Verde” allowing person-based choices of what fields/attributes to display
Redesign and Improve ACCESS attribute
51
Taipei, June 2006
Verde 3 and beyond (3)
Smart system creates actionable URL based on incoming IP address and other data
Rolling holdings mechanism
UI for update engine management
UI for Workflow management
52
Taipei, June 2006
Verde 3 and beyond
Verde triggers Aleph to create or update 856 field with URL
External HTML page automatically sends SOAP message to create Trial report
..and many more.
53
Taipei, June 2006
Ted Koppel
Verde Product Manager
+1.617.332.8800 x601
Thank You!