1 / 21

HERMES: An integrating approach to managing electronic resources

HERMES: An integrating approach to managing electronic resources. Sue Woodson Johns Hopkins University ACRL 2003 – Charlotte, NC. HERMES. H OPKINS E LECTRONIC R ESOURCE M ANAG E MENT S YSTEM. The Challenges. What do we have? Where do we get it? Who can use it? Where? How?

brittany-graves
Télécharger la présentation

HERMES: An integrating approach to managing electronic resources

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. HERMES:An integrating approach to managing electronic resources Sue Woodson Johns Hopkins University ACRL 2003 – Charlotte, NC

  2. HERMES HOPKINS ELECTRONIC RESOURCE MANAGEMENT SYSTEM

  3. TheChallenges • What do we have? • Where do we get it? • Who can use it? Where? How? • Who bought out what company last week?

  4. TheChallenges (contd) • Multiple sources of data about what we have • How do we get all that in one place?

  5. Hopkins environment—not quite a consortium Multiple Libraries Geographically dispersed Distinct budgets Distinct clientele Scattered IP ranges

  6. HERMES — Institution-wide system for sharing data • Patrons: aids identify and access online resources • Staff: facilitates stewarding • Select • Acquire • Support

  7. Public Display Project Resource Tracking Project Birth of HERMES

  8. Integrating the 2 projects • Extensive conversations • Staff from across libraries • Led by Web Developer/Librarian • Discovering what we wanted

  9. Before we built it… • Clarifying the workflow • Defining relationships among data elements

  10. Key Features—beyond the data • Web based (view & edit) • Role based access • Integrates with other systems

  11. Key Features—beyond the data (contd) • No duplicate data entry • Catalog is authority for bib data • Ability to migrate data and grow system

  12. What’s new? • Auto load from catalog • New roles EXAMPLE • Publisher – Modern Language Association • Provider – SilverPlatter • Vendor – PALINET

  13. HERMES — current state • Coding complete • Successfully extracted catalog data • First round of testing complete • Database moved from development to production server (testing again) • Reviewing subject classification procedures

  14. OK…So What? Beyond ‘How I Did it Good’

  15. Q #1: What is the librarians’ role in product development • Identifying and articulating needs • Advocating for standards • Efficient and effective sharing of projects in development • e.g., Web Hub project

  16. Q #2: What kinds of management systems do we want? • Buy the whole thing • Select by modules

  17. Integrated Systems Integrating Systems In other words…

  18. ILS – Are they past their prime? • Overly complex • Not standards based • Tie librarians to a single system with modules of varying quality • Migration nightmares

  19. Integrating Systems • More choices—cafeteria style choosing • Easier migration of data • More flexible integration with a variety of data sources • Better bang for our bucks

  20. Stand alone systems? • SFX • E-resource management system • Next?

  21. Sue Woodson woodson@jhu.edu Johns Hopkins University ACRL 2003 – Charlotte, NC

More Related