1 / 26

Global Open Knowledgebase ( GOKb )

Global Open Knowledgebase ( GOKb ). A community-maintained data store for descriptions of library resources. Growth of electronic library collections. Academic libraries spend over $3 billion/ yr on electronic resources. 2. electronic library collections. 3. Metadata supply chain.

artan
Download Presentation

Global Open Knowledgebase ( GOKb )

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. Global Open Knowledgebase(GOKb) A community-maintained data store for descriptions of library resources

  2. Growth of electronic library collections • Academic libraries spend over $3 billion/yr on electronic resources 2

  3. electronic library collections 3

  4. Metadata supply chain • Content providers • Publishers typically, but also other content aggregators. • Agents • Subscription agents, knowledge base providers, library system vendors • Data exchange standards • Editeur (ONIX). KBART.

  5. Metadata management • How do we do it now?

  6. Community solution to a common problem • Value proposition for a community source solution • We’re all managing the same stuff • Changes take too long to propagate • General recognition of the problem • Neither libraries nor vendors of these products is happy with the current state • Cloud potential • New model is possible, inexpensive and performant

  7. The UK Perspective • UK Institutions increasingly dissatisfied with quality of knowledgebases: • - Incorrect data • - Lack of interoperability with other systems • - Challenges around maintaining data across stakeholders • - Duplication of effort across sector • Increased interest in shared approached to managing KB data

  8. Knowledge Base+

  9. Why work with GOKB? • - Do Once and Share • - Make KB+ data available to GOKb • - Use GOKb data in KB+ • - Improve sustainability • - Reduce the duplication of effort further • - Increase range of data available • - Shared software development • - Speed pace of development • - Advocacy • - Open source • - Open data • - Improvement of metadata quality • - Promote the adoption of standards

  10. GOKb will be a freely available data repository that will contain key publication information about electronic resources as it is represented within the supply chain from content publishers to suppliers to libraries.

  11. Global Open Knowledgebase (GOKb) • Kuali OLE / JISC collaboration • Andrew W. Mellon Foundation funded project (June 2012-June 2014) • Open to all, but targeted to integrate with Kuali OLE and JISC’s Knowledge Base+

  12. GOKb Key Deliverables Open knowledge base using industry standard architecture User interface and APIs to maintain and use GOKb data in OLE and other systems Data covered by a CC0 license Expose as linked data

  13. What does the data look like?

  14. GOKb architecture

  15. GOKb Key Deliverables GOKbwill use a rules engine to cleanse and normalize ERM data from heterogeneous sources The rules engine will accept rules from the community of functional experts without coding! Code development has begun GOKb will be deployed as a cloud service

  16. GOKb as Central Data Source for Kuali OLE Kuali OLE Indiana University Kuali OLE NC State KB+ King’s College London Kuali OLE Univ Penn

  17. GOKb will be OLE’s knowledge base • A library management system must have an integrated knowledge base • GOKb data services • (e.g.) • Get PACKAGE headerGet PACKAGE with its TITLESFor a PACKAGE, get selected (not all) TITLESPush back TITLE addition/deletion to GOKb

  18. Engaging subject matter experts

  19. Engaging subject matter experts • Lead SMEs • OLE SME community • OLE and GOKb integration • Top 7 Providers • Change Management • Strike Teams ( Metadata / Rules / etc. ) • Broader community

  20. Why this is a hard problem: Part1 • Data is *very* messy • Data providers aren’t incentivized to make it better (yet) • Community is engaged but does not want to manage data in two (or more) places

  21. Why this is a hard problem: part 2 • No current system does it well; there is no model • KFS isn’t designed for library electronic resources • Entities and relationships are complex • Workflows can include just about everybody in the library

  22. Library Book LifeCycle

  23. Library E-Content Lifecycle

  24. Questions?

  25. How will OLE use GOKb?

More Related