Sept 24 NISO Virtual Conference: Library Data in the Cloud
•Transferir como PPTX, PDF•
1 gostou•1,742 visualizações
eResource Management in the Cloud Jeffrey D. Kuskie, Electronic Resource Manager, Dr. C.C. and Mabel L. Criss Library, University of Nebraska at Omaha
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Destaque
Semelhante a Sept 24 NISO Virtual Conference: Library Data in the Cloud
Semelhante a Sept 24 NISO Virtual Conference: Library Data in the Cloud (20)
Mais de National Information Standards Organization (NISO)
Mais de National Information Standards Organization (NISO) (20)
Último
Último (20)
Sept 24 NISO Virtual Conference: Library Data in the Cloud
- 1. eResource Management in the Cloud Jeff Kuskie University of Nebraska Omaha NISO Library Data in the Cloud September 24, 2014 * 2:45-3:15
- 2. Polls: • Using traditional ILS/ERM? • Multiple products/vendors to manage e-resources? • Using cloud-based system?
- 3. Where we’re going today: • Context • Global Aspects • Advantages/Challenges
- 4. University of Nebraska Omaha • Metropolitan campus • 15,000+ Students • Criss & UNO-Kaneko Libraries • 1.2M vols.
- 5. Migration • Old system: III Millennium/Encore • New system: OCLC WMS/WCL • August 2012 • Live March 1, 2013 • 1M+ e-resource titles • 100 License agreements
- 6. Traditional eResource Management (ILS/ERMs/etc) • Vendor (s) • ILS • Discovery • ERM • Link Resolver • A-Z List • Remote access Authentication • Locally created & Maintained records • May or may not have a bib record • eresource record • Order info, bib data, access info, Administrative info, change info, coverage data, stats, contact info, license info.
- 7. Global eResource Management • Unified Framework = WCKB • ILS, Discovery, ERM, Link resolver, A-z List • Global files: • Acquisitions Management: vendor/Contact info • Resource Metadata • License Management • Automated Coverage & Metadata updates • Cooperative Data Management Capabilities
- 8. WorldCat Knowledge Base • *As of August 2014; 11,900 collections from 6,098 providers • Combines metadata & access • A-Z List • OpenURL resolution • License Management • Automatic coverage & metadata updates • Cooperative Data Management * Source: https://oclc.org/knowledge-base.en.html
- 9. Combined metadata/access: public view
- 10. A-Z List
- 11. Link Resolver
- 12. Global License Mgt • Derive local licenses from global templates • License info viewable by staff • Eventually will be able to make elements of license data viewable publicly, if desired
- 13. General ProQuest Electronic Product License Agreement
- 14. Search to see if a license template exists
- 16. Automatic coverage data & record updates • OCLC: Collection data • EBL: Purchased titles • EBL: DDA Titles • PubGet WorldCat KB Holding Program ( http://pubget.com/ ) • e-resource holdings tool • How can it help you?
- 18. Local collection maintenance history
- 19. Public view of PubGet updated resource in WCL
- 20. Cooperative Management • Approve or deny global data changes • Contribute title changes to existing collections • Add new title to global KB collection • Add a new collection to global KB
- 27. & delete
- 29. Challenges of Cooperative/Cloud eResource Mgt • Lack of best practices • Less local control • Reliance on automatic updates/loads can mean delayed exposure of newly added contents. • Figuring out what’s included in “automatic” features—like the A-Z list, etc. • Lack of best practices
- 30. Advantages of eResource MGT in the Cloud • Unified Service platform • Acquisitions/Administration/Liscense management all-in-one • Select/Activate Discovery Access Immediately • No more manual coverage & MARC record loads • Community participation in data quality assurance & maintenance
- 31. Contact Info: Jeff Kuskie jkuskie@unomaha.edu University of Nebraska Omaha Criss Library
Notas do Editor
- I wanted to get an idea of how everyone else is managing their electronic resources. I thought that would be interesting to see what other people are doing and it gives me a sense of how many of you are still using a traditional ERM and how many have switched to a cloud based system.
- Context = will tell you who we are and how we got here Global aspects of a cloud-based system Some of the advantages/challenges of managing e-resources in a global, cloud-based platform.
- Who are we?
- What brought us to the cloud-based system we use today? -We were using III’s Millennium for our ILS and Encore for our discovery platform We started Migrating to OCLC’s cloud based WorldShare Management system and Worldcat local in August 2012. So, we were using a traditional ERMs within an ILS….
- Like many of you noted in the poll you just filled out, @ UNO we also used multiple vendors for different aspects of our eresource management, because not all ILSs / ERMs included every component of eResource management (like a link resolver, A-Z list, Remote access authentication software) The one thing that is consistent across traditional ERMs is EVERY library adds every piece of the data reflected in the ERM tools.
- Now, in global e-resource management environment our ILS, Discovery Platform, link resolver, all of our e-resource management is on one unified platform… There is information that can be shared globally in this cloud-based system. Such as vendor contact information, resource metadata and license templates.
- If you are an OCLC member, you have access to the KB and can request KB setup from OCLC. As of August 2014, WCKB included more than 11,000 collections from about 7,000 providers The WCKB combines metadata & access, A-Z list functionality, Open URL resolution and license management in a unified framework. In addition, automatic coverage and metadata updates and cooperative data management is possible within the global, cloud-based platform.
- When a title is added to the Knowledge Base and holdings are set, it is IMMEDIATELY exposed within the public interface. Metadata can be created locally, however, most often you are able to simply select titles/collections that are available within the global KB. Once a title is selected within the KB, there is no need to “activate” a link, or load a URL anywhere—simply add a title and it is accessible…
- Adding a title also automatically populates the A-Z list, exposing titles/collections to users.
- With full-text access provided by the built-in link resolver. The link resolver and A-Z list provide local access to global collections/titles—all within a unified framework.
- Much like global metadata creation/maintenance, global license management in a cloud-based system allows you to capitalize on work done by other members of the cooperative (in this case OCLC members). Local license records can be derived from global license templates. Creating/Maintaining licenses in a global platform provides full exposure to staff (with appropriate credentials) and allows exposure of some elements to the public.
- For example, here is a local iteration of the over-arching ProQuest license agreement.
- Capitalizing on work done by another member of the global community, I can derive a local license record from the global template.
- I have “localized” the record by associating the license with 4 collections and defining 3 local terms of use.
- Another feature of a cloud-based, globally accessible e-resource management tool is the ability to take advantage of automatic coverage/data loads done by other entities. OCLC Collection data is updated by OCLC. OCLC is working with publishers to develop automatic record loads. For example, we currently get automatic loads from EBL of our purchased titles as well as our DDA titles. Another partnership OCLC developed is with PubGet….
- PubGet is an eresource holdings tool.
- Regardless of platform, global, cloud-based discovery systems have a mechanism to find out which loads are done, when. So, you can see what has been added/updated to your local iteration.
- You have the metadata AND access points automatically exposed within the public interface.
- So, just like the global metadata, license and automatic updates, the cloud-based system allows us to work in concert with other cooperative members to manage the global WC KB.
- Phase 1 of cooperative data management was implemented earlier this year and allows member libraries to approve/deny changes before they are made.
- Phase 2 allowed members to make changes to existing KB records.
- Phase 3 allows libraries to add and delete records and collections to the KB.
- The ability to capitalize on work done by the global community is ONLY possible in a cloud-based e-resource management platform. In locally controlled/exposed traditional ERMs, things like coverage/record loads were not automatic/seamless—they required us to manually load records. ALL work whether it was license record creation, updating titles in a collection, had to be done locally. However, cloud-based systems also present unique challenges…
- …these challenges are of particular interest to groups like NISO…