1. A community-maintained data store for descriptions of library resources Global Open Knowledgebase (GOKb)

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

3. electronic library collections 33

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

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

6. Community solution to a common problem Value proposition for a community source solution 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 General recognition of the problem Neither libraries nor vendors of these products is happy with the current state Cloud potential Cloud potential New model is possible, inexpensive and performant 6

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

8. Knowledge Base+ 8 Centrally Maintained KB+ Focused on UK Verifying – Normalising – Updating – Sharing Publication Information Over 12,000 titles Titles Package Platform Coverage Subscription Data Entitlements Core/Subscribed Notice Periods Renewal Dates Licences Key Values Walk-In Users Course Packs ILL Remote access Post- Cancellation access Shared Knowledge Add documents notes and alerts Status Updates Generate reports

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

10. 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. Kuali OLE / JISC collaboration Kuali OLE / JISC collaboration Andrew W. Mellon Foundation funded project (June 2012-June 2014) 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+ Open to all, but targeted to integrate with Kuali OLE and JISC’s Knowledge Base+ Global Open Knowledgebase (GOKb)

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. 13

14. What does the data look like?

15. 15 GOKb architecture

16. GOKb Key Deliverables GOKb will 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

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

18. GOKb will be OLE’s knowledge base A library management system must have an integrated knowledge base A library management system must have an integrated knowledge base GOKb data services GOKb data services (e.g.) Get PACKAGE header Get PACKAGE with its TITLES For a PACKAGE, get selected (not all) TITLES Push back TITLE addition/deletion to GOKb 18

19. 19 Engaging subject matter experts

20. Lead SMEs Lead SMEs OLE SME community OLE SME community OLE and GOKb integration Top 7 Providers Change Management Strike Teams ( Metadata / Rules / etc. ) Broader community Broader community 20

21. Why this is a hard problem: Part1 Data is *very* messy Data is *very* messy Data providers aren’t incentivized to make it better (yet) 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 Community is engaged but does not want to manage data in two (or more) places 21

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

23. Library Book LifeCycle 23 Buy Circulate Preserve

24. Library E-Content Lifecycle 24 Create bundle LicensePurchase Manage access Manage changes Evaluate Archival access

25. 25 Questions?

26. How will OLE use GOKb?