1 / 53

Verde An Introduction to Version 2 Taipei, June 2006

Verde An Introduction to Version 2 Taipei, June 2006. Ted Koppel Verde Product Manager, Ex Libris. Agenda . Verde’s architectural context Current status of product Verde Version 2 – new features Some words about Consortia ERM standards relevant to Verde Future plans for Verde

lamar
Download Presentation

Verde An Introduction to Version 2 Taipei, June 2006

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Verde An Introduction to Version 2Taipei, June 2006 Ted Koppel Verde Product Manager, Ex Libris

  2. Agenda • Verde’s architectural context • Current status of product • Verde Version 2 – new features • Some words about Consortia • ERM standards relevant to Verde • Future plans for Verde • Demonstration of version 2 • Q&A Taipei, June 2006

  3. Hierarchical Data Structure Based On e-Product Interface Print Standalone Package Constituents (e-journals, e-books) Taipei, June 2006 3

  4. e-Product info Lower levels inherit Acquisitions Interface Access Licensing Package Costs Trial Use Constituent Administration Usage Taipei, June 2006

  5. 3rd party applications Web Services (SOAP) Verde Architecture OpenURL Staff interface Taipei, June 2006 5

  6. What Verde Isn’t • A bibliographic maintenance system • A full scale acquisitions and payments system • An OpenURL resolver • An A-to-Z list provider • A Public Access Catalog • An Interlibrary Loan system • A public interface However, Verde works with all of the above supplying ERM information to these applications Taipei, June 2006

  7. Verde – Overview of Customer Base Taipei, June 2006

  8. Verde Customers – Individual Institutions • 61 Sales as of June 2006 • China • Tsinghua University (III) • Denmark • Novo-nordisk • Spain • Residencia de Estudiantes (Ex Libris) • Universidad de Navarro (III) • Switzerland • Hoffman-La Roche Ltd. • United Kingdom • Cranfield University (SirsiDynix) • Liverpool John Moores University (Ex Libris) • Nottingham Trent University (Ex Libris) • University of Nottingham (Ex Libris) Taipei, June 2006

  9. Verde Customers – Individual Institutions • United States • Bristol Myers-Squibb • Centers for Disease Control & Prevention (Endeavor) • Harvard University (Ex Libris) *DEV. PARTNER • Massachusetts Institute of Technology (Ex Libris) *DEV. PARTNER • Memorial 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) Taipei, June 2006

  10. 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 Taipei, June 2006

  11. 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 Taipei, June 2006

  12. Version 2 major enhancements • Role Based Authentication, Task Permissions, and Profile Assignment • Workflow Management • Verde Tasks and Alerting • Copy and Paste • License Attachment Uploads • Multi-instance searching • Reports and Batch Task scheduling • Local product Wizard • Incident and Breach Logging • Non-Roman language display Taipei, June 2006

  13. 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 Taipei, June 2006

  14. Verde’s approach to Workflow Workflow Engine (task manager) Roles assigned and tasks allowed Alerts and E-mail Taipei, June 2006

  15. 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 Taipei, June 2006

  16. Workflows and tasks • Verde ships with three workflows • Acquisitions • Licensing • Renewal/Review • Each workflow has several tasks pre-defined • All workflows and tasks can be configured by the customer Taipei, June 2006

  17. Workflows and tasks • Tasks can be internal or external to Verde • Internal: complete acquisitions record and approve it • External: 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 Taipei, June 2006

  18. 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 Taipei, June 2006

  19. 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 interface • New interface e-product record • New package e-product record • All linked together as a logical group Taipei, June 2006

  20. 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 Taipei, June 2006

  21. Search/retrieval changes • Single instance: Local or Global checkbox • Multi-instance: One, Some, All, +/- Global • New column displays holdings • Consortium navigation Taipei, June 2006

  22. Choose which instances to search Taipei, June 2006

  23. Multiple instances retrieved Taipei, June 2006

  24. Breach and incident logs Taipei, June 2006

  25. Breaches and Incidents • Expansion of DLF specification • Can be attached to any level of record • Collects what the problem was, timestamp, responsible person, disposition, and notes • Next step: allowing breach/incident log entry to automatically create email to vendor Taipei, June 2006

  26. Other changes in version 2 • Improved/enhanced batch job and report scheduler • Additional reports, including consortium • Various invisible infrastructural changes • Better sharing with SFX • More efficient indexing and updating on large sets • Minor menu and screen changes for ergonomic reasons Taipei, June 2006

  27. Consortial Models Taipei, June 2006

  28. Parallel Consortium Model 1 2 3 4 5 Taipei, June 2006

  29. Parallel Model • Share the same server(s) • Share the same Oracle installation But … • Each instance has its own configurations, users, etc. • Secure ‘walls’ between instances • Almost complete autonomy if desired • May allow read-only access if desired • “Good fences make good neighbors” Taipei, June 2006

  30. Top-down model (central authority) Central management of some sort 1 2 3 4 5 Taipei, June 2006

  31. Top-down management • Many different flavors • Central authority can be • purchasing agent (and bill for costs) • funding agent • Hardware/software host • Database quality – consistency manager • Various combinations of the above Taipei, June 2006

  32. Top down model • Central instance that does something • Multiple individual instances • Depending on flavor, the individual instances may show • Only what the specific instance has bought for itself • Everything bought by Central on behalf of the individual instance Taipei, June 2006

  33. Hybrid top down model Central management of some sort 6A 1 2 3 4 5 6B 6C Taipei, June 2006

  34. 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 Taipei, June 2006

  35. No two consortia are alike !!! • Acquisitions and Purchasing roles • Messaging and availability to public • Cost sharing formulas • Role and influence of central authority • SFX and Metalib use and structure • Etc. • Verde’s goal: build in configurability and flexibility within certain basic frameworks. Taipei, June 2006

  36. Why choose one model over another? • Service delivery - identity of library versus identity of consortium • Management needs (reporting, fiscal) • Purchasing model; financial support from central authority • Atmospherics – do consortial members get along? • Atmospherics 2 - do the libraries’ parent institutions prefer individual attention and recognition? Taipei, June 2006

  37. Why choose? (2) • Economics – cost of ERM installation as individuals versus as consortium • Existing software (SFX, for example) model Taipei, June 2006

  38. Verde version 2 Consortial Features • In top-down model • Merged Master database of all holdings, all instances • Ability to search one, all, or any combination of instances, + or – GKB, in one operation • Ability to see merged (automatically deduplicated) results labeled with instance(s) that own specific e-journals • Ability to jump from one instance’s holdings to another without having to re-execute search • Various navigational short-cuts (breadcrumbs, filters, etc.) • ..more.. Taipei, June 2006

  39. 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 Taipei, June 2006

  40. Cross instance reporting • Management reports that count individual factors, collect and aggregate • Subject to same permissions/rules as real-time access Taipei, June 2006

  41. 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 Taipei, June 2006

  42. 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 (!) Taipei, June 2006

  43. Standards of relevance to Verde • Digital Library Federation Electronic Resources Management Initiative Specification (DLF-ERMI) • Published 2004 • Specifies Data elements, functions, interrelationships • Revision / expansion began 2006 • COUNTER (Counting Online User NeTwork Electronic Resources) • Defines data elements and XML format for usage statistics collection and distribution • 7+ reports detailing different statistical measures Taipei, June 2006

  44. Standards in Process • SUSHI (Standardized Usage Statistics Harvesting Initiative) • Web service; describes protocol for request and receiving COUNTER-format statistics from publishers • Development 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 libraries • Led by DLF/ERMI2 and EDItEUR; 60+ members • Builds on ONIX schemas • First draft: summer/fall 2006 Taipei, June 2006

  45. Version 2.5 – Early 2007 • Statistics • Automated Retrieval (SUSHI) • Vertical Analysis Tools (InterfacePackageConstituent) • Horizontal Analysis Tools (all use of Journal X regardless of how delivered) • Single and Multiple Instance Taipei, June 2006

  46. Version 2.5 (2) • Multi-Language Support • Underlying structure already in version 2 • Adding 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) Taipei, June 2006

  47. Version 2.5 (3) • Workflow enhancements • Application of rules at attribute level – when is a task considered complete? • Additional Role Based Authentication enhancements • Consortium Functionality • Voting mechanism • Group roles for cross-instance editing and function • Cost splitting and billing • License and SOAP responses based on incoming IP address Taipei, June 2006

  48. Verde 2.5 (4) • Minor GUI enhancements • History dropdown • Autocomplete in search • Choice of # of results to be displayed • “CLEAR” button • Set dates manually • New fields: impact factor, etc. • Add HH:MM where necessary Taipei, June 2006

  49. 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 (!) Taipei, June 2006

  50. 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 Taipei, June 2006

More Related