1 / 48

Knowledge Bases and trends in Library Resource Management and Access

Marshall Breeding Independent Consultant Founder and Publisher, Library Technology Guides http://www.librarytechnology.org/ http://twitter.com/mbreeding. Knowledge Bases and trends in Library Resource Management and Access. An update on the current environment. 03 March 2014.

ona
Télécharger la présentation

Knowledge Bases and trends in Library Resource Management and Access

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. Marshall Breeding Independent Consultant Founder and Publisher, Library Technology Guides http://www.librarytechnology.org/ http://twitter.com/mbreeding Knowledge Bases and trends in Library Resource Management and Access An update on thecurrent environment 03 March 2014 NII ERDB Member Meeting

  2. Agenda • National Institute of Informatics • ERDB (Electronic Resources Database) • Summarize findings and analysis of the current state of the OpenURL Link Resolver and Knowledge Base arena

  3. General Observations • Both commercially produced and community-based projects underway • Commercial products currently are more comprehensive with more sophisticated support mechanisms • Commercial: • Serials Solutions: 360 Link / KnowledgeWorks • Ex Libris: SFX / SFX Global Knowledgebase • EBSCO: LinkSource / • OCLC: WorldCat knowledge base

  4. Non-commercial Products and projects • Simon Frasier University: • CUFTS / GODOT • Colorado Alliance of Research Libraries • Gold Rush • Kuali OLE Project • Global Open Knowledge Base (GOKb)

  5. Related Initiatives • KBART • More standardized approach for information providers to deliver representations of their content products to KB providers • Project Transfer • JISC initiative for shared services for electronic resource management • KnowledgeBase+ • Open Discovery Initiative • Specifically related to index-based discovery

  6. Future Directions

  7. Transition away from Standalone Products • Knowledge bases were originally developed for OpenURL link resolution • Increasing emphasis on knowledgebase as part of the infrastructure of broader strategic platforms • Ex Libris: SFX Global KnowledgeBase will become part of the Community Catalog of Alma • Serials Solutions: KnowledgeWorks will expand to include print and other materials in support of Intota • OCLC: WorldCat Link Manager already discontinued in favor of WorldShare License Manager, WorldShare Management Services • EBSCO: Platform consolidation already underway between LinkSource, EBSCO A-to-Z, and EBSCO Discovery Services. No announcement of broader strategy yet announced.

  8. Emerging Automation Models • New genre of Library Services Platforms replacing Integrated library Systems • Support for multiple formats: • Print and physical media • Electronic: subscribed and owned • Digital: local and external collections of images, digital recorded sound, video • Globally shared metadata models: knowledge bases that support appropriate formats • Deployed through multi-tenant software as a service platforms • Open API’s for interoperability and extensibility

  9. Policies $$$ Funds BIB Vendor Holding / Items CircTransact User Integrated (for print) Library System Public Interfaces: Staff Interfaces: Interfaces Circulation Cataloging Acquisitions Serials OnlineCatalog BusinessLogic DataStores

  10. Fragmented Library Management • LMS for management of (mostly) print • Duplicative financial systems between library and local government or other parent organization • E-book lending platform (multiple?) • Interlibrary loan (borrowing and lending) • Self-service and AMH infrastructure • Electronic Resource Management • PC Scheduling and print management • Event scheduling • Digital Collections Management platforms (CONTENTdm, DigiTool, etc.) • Discovery-layer services for broader access to library collections • No effective integration services / interoperability among disconnected systems, non-aligned metadata schemes

  11. Policies LicenseTerms BIB Vendors Holding / Items CircTransact User Vendor E-JournalTitles $$$ Funds LMS / ERM: Fragmented Model Public Interfaces: Staff Interfaces: ` Application Programming Interfaces Circulation Cataloging Acquisitions Serials OnlineCatalog E-resourceProcurement LicenseManagement Protocols: CORE

  12. BIB Holding / Items CircTransact User Vendor Policies $$$ Funds Common approach for ERM Public Interfaces: Staff Interfaces: Budget License Terms Application Programming Interfaces Circulation Cataloging Acquisitions Serials OnlineCatalog Titles / Holdings Vendors Access Details

  13. Comprehensive Resource Management • No longer sensible to use different software platforms for managing different types of library materials • ILS + ERM + OpenURL Resolver + Digital Asset management, etc. very inefficient model • Flexible platform capable of managing multiple type of library materials, multiple metadata formats, with appropriate workflows • Support for management of metadata in bulk • Continuous lifecycle chain initiated before publication

  14. Library Services Platform • Library-specific software. Designed to help libraries automate their internal operations, manage collections, fulfillment requests, and deliver services • Services • Service oriented architecture • Exposes Web services and other API’s • Facilitates the services libraries offer to their users • Platform • General infrastructure for library automation • Consistent with the concept of Platform as a Service • Library programmers address the APIs of the platform to extend functionality, create connections with other systems, dynamically interact with data

  15. Library Services Platform Characteristics • Highly Shared data models • Knowledgebase architecture • Some may take hybrid approach to accommodate local data stores • Delivered through software as a service • Multi-tenant • Unified workflows across formats and media • Flexible metadata management • MARC – Dublin Core – VRA – MODS – ONIX • Bibframe • New structures not yet invented • Open APIs for extensibility and interoperability

  16. New Library Management Model Unified Presentation Layer Search: Self-Check /Automated Return Library Services Platform ` Digital Coll Consolidated index Search Engine Discovery Service ProQuest API Layer StockManagement EBSCO … Enterprise ResourcePlanning Smart Cad / Payment systems JSTOR LearningManagement AuthenticationService Other Resources

  17. Library Services Platforms

  18. Library Services Platforms

  19. Web-scale Index-based Discovery ILS Data (2009- present) Digital Collections Search: Web Site Content Institutional Repositories Search Results Aggregated Content packages Consolidated Index Profile of Library Subscriptions Open Access … E-Journals CustomerProfile Usage-generatedData Reference Sources Pre-built harvesting and indexing

  20. Bento Box Discovery Model Aggregated Content packages Search: Open Access ILS Data VuFind / Blacklight E-Journals Consolidated Index Search Results Web Site Content Digital Collections Institutional Repositories Pre-built harvesting and indexing

  21. Evolving Role of Knowledgebases • Shift from multiple knowledge bases for different product categories to more consolidated approach • Support infrastructure for electronic resource management • Basis for reference linking in broader end-user access environment for scholarly content • Basis for smart or direct linking within discovery interfaces • Basis for scoping for index-based discovery services

  22. Continuity in the short term • All the vendors report that they will continue to offer stand-alone linking products and knowledge bases in the short term

  23. Product leverage • Initial acquisition of link resolver and KB  • Subsequent investment in discovery  • Subsequent investment in new automation products

  24. Decision drivers • In the past, link resolvers and their knowledge bases were mostly independent decisions • Today, knowledge bases and link resolvers are mostly tied to discovery strategies. Many libraries are shifting to new resolvers to accommodate changes that they have made in discovery products. • Using a link resolver from another provider may result in the need to operate multiple knowledge bases. Difficult to synchronize • In the next cycle, knowledge bases will also be associated with new library management products.

  25. Decision Drivers • Today and in previous years link resolvers were acquired on the basis of their functionality and knowledge base completeness • Increasingly the link resolver will come as components of broader systems. • Differentiation among knowledge bases will narrow as data becomes available more universally and consistently through KBART.

  26. Open Access Knowledge Bases? • Previous efforts of open access knowledge bases have not been sustained • JAKE • GODOT not competitive with current commercial offerings • Open access knowledge bases may pose more substantial competition • Global Open Knowledge Base (Kuali OLE / JISC) • KnowledgeBase+

  27. Commercial Products

  28. Comparison

  29. Comparison

  30. Comparing Comprehensiveness and Quality • Assessment of the scope of the products cannot be accomplished based on numerical comparisons • Numbers provided by each supplier not comparable • Process for how libraries localize their implementation for materials not covered differs • Quality and consistency as reported by supplier sometimes not entirely consistent with library perceptions

  31. Library Survey • Conducted a survey completed by over 500 libraries using link resolvers • Questions • How do you rate the overall performance of the Link Resolver and its Knowledge Base? • How do you rate the performance of the link resolver in its effectiveness of connecting users to appropriate copies of electronic resources? • How do you rate the comprehensiveness of the knowledge base relative to the number of e-journals and other electronic resources held by your library? • How do you rate the accuracy of the knowledgebase in representing electronic resources? • How do you rate the promptness in which errors reported by libraries are corrected in the knowledge base? • How do you rate the tools offered for the library to configure and administer the knowledge base and link resolver?

  32. Ex Libris SFX & Global KnowledgeBase • First to acquire and commercialize OpenURL link resolvers (Feb 2000) • Promoted OpenURL 0.1 as a de facto standard and OpenURL 1.0 as a NISO Standard • SFX Global KnowledgeBase • Most Installations worldwide • Many new customers associated with ongoing sales of Primo and Alma • Some erosion of customers to Serials Solutions

  33. Serials Solutions KnowledgeWorks and 360 Link • KnowledgeWorks a core product of Serials Solutions • Emerged from E-Journal lists • Original ArticleLinker became 360 Link • Multi-tenant software as a service for all products • Uses both automated processes and human intervention to maintain KB • Created Summon as the first index-based discovery service • Recently announced Intota as its comprehensive library management product

  34. OCLC WorldCat Knowledge Base • Originated from the 1Cate product acquired from Openly Informatics • Integrated into the WorldCat platform • Basis for WorldCat Link Manager • No longer a separate utility but provides the link resolution functionality of WorldCat Local • Part of the underlying infrastructure of WorldShare License Manager

  35. EBSCO LinkSource and Knowledge Base • EBSCO usesSmartLinks to create direct links within the EBSCOhost environment • LinkSource provides link resolution to content outside EBSCO products • Very large number of libraries use EBSCO A-to-Z • Recent product license changes makes LinkSource available to any library subscribing to A-to-Z

  36. Colorado Alliance of Research Libraries Gold Rush • Lower-level product • Smaller knowledge base with fewer automated processes for updates and management • Lower cost

  37. Simon Frasier University: CUFTS GODOT • Open source link resovler • Open access knowledge base • Maintained primarily by technical services group at Simon Frasier University • TrueSerials offers commercial subscriptions.

  38. Kuali OLE: Global Open Knowledge Base (GOKb) • Proposal to the Andrew W. Mellon Foundation • Submitted Jan 4, 2012 (Recently Approved) • $498,621 requested for 1-year project • April 1 2012 – March 31, 2013 • Collaboration between JISC and KualiOLE • Lead institution: North Carolina State University • Principal Investigators: • Susan Nutter (NCSU) • Rachel Bruce (JISC)

  39. Broad Objectives • Create an community supported knowledge base that can be used by multiple projects for the management of electronic resources • Initially for JISC and Kuali OLE, but also for other institutional and commercial uses • Hosted on a platform built on open source software • Deployed at multiple host sites (Initially Europe and US) • Data and services delivered through open API’s

  40. Addresses current problems • Insufficient data regarding publishers and providers; simplistic representation of relationships among content and provider roles • Absence of identifiers for entities in the supply chain • Inadequate normalization of data across or within systems • Inability for libraries to openly access and repurpose data within current knowledge bases • Inability to track changes over time of any given title or other entities over time

  41. Global Open Knowledge Base goals • A repository of high-quality metadata about the electronic resources and their representation across the supply chain from publisher to licensor to library vendor to library customer, including representation of marketing and packaging constructs as defined by the suppliers; • the ability to track changes to product entities and their associated organizations over time; • an open services platform that will enable libraries and others to employ that data in local systems. Quoted form the proposal to the Andrew W. Mellon Foundation

  42. Data needed for Electronic Resource Management • Publications & their packaging - E-resource titles and their associated packages and platforms as supplied by a given publisher or provider, associated with brief descriptive metadata, such as subject terms and identifiers • Actors - Information about organizations and their role in the supply chain (publisher, provider, licensor, subscriber) • Terms - Information about licensing, terms of acquisition, use and ongoing access • History - The historical record of changes in such as titles and organizational roles, against which license terms and institutional entitlements can be recorded • Local entitlements (holdings) - typically date ranges (in various formats) and statements about embargoes if applicable and access information (URL) Quoted form the proposal to the Andrew W. Mellon Foundation

  43. Proposed Solution • Bill of Materials data model • used in engineering and manufacturing sectors • Data for item can be exploded into constituent parts • Ensure compatibility with open linked data expectations through RDF data modeling • Relational RDMS as fallback

  44. Data Elements • Organization. Institutional entity with a role in the supply chain. • Elements: Names, roles (publisher, provider, licensor, vendor, subscriber), administrative information about organizations. • Standard numbers. Identifiers for the journal title. • Elements: ISSN, e-ISSN, ISSN-L, DOI • Collection (combination). A branded set of titles instances offered by a provider. • Elements: Names, title IDs, internal identifier. • Title instance (component). A title as supplied by a given licensor. • Elements: Names, identifiers, base URLs, terms under which a title is offered ("status"), entitlement offered • Platform. A software solution for hosting journal title instances. • Elements: Names, internal identifier. • Model license agreement. Terms of acquisition and use for a deal or titles instances as offered by the provider and prior to local negotiations. • Elements: Document, coded values, deal ID, title instance IDs, internal ID. Quoted form the proposal to the Andrew W. Mellon Foundation

  45. License for GOKb • Science Commons Protocol for Implementing Open Access Data • http://www.sciencecommons.org/projects/publishing/open-access-data-protocol/ • Open Data Commons Public Domain Dedication and License (ODC-PDDL) • Creative Commons CC0 waiver

  46. Sustainability and Data Maintenance • Project will produce initial population • Develop ongoing methods of updates

  47. KnowledgeBase+ •  develop a centralised, shared, above-campus knowledge base of data useful to electronic resources management (ERM) at institutional level • provide institutions, and the services they use, with timely, accurate, verified and structured ERM information, including e-resources publication, licensing, subscription and entitlements data • extend and enhance existing data and services rather than creating yet another silo

  48. SCONUL • Society of College, National and University Libraries • Funded a 2011 project to analyze use case process in UK Higher Education instiutions

More Related