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

2

2010/11 2011/120

2,000,000

4,000,000

6,000,000

8,000,000

10,000,000

12,000,000

Full-text journal downloads Database usePrint book circulations/renewals Digital collections requestsE-books Reserves

Print book circulation

Books

One-Time Purch

ases

E-Journals

E-Resources

Print S

erials

Other$0

$1,000,000

$2,000,000

$3,000,000

$4,000,000

$5,000,000

$6,000,000

$7,000,000

2012/2013 2011/2012

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

Knowledge Base+

8

Centrally Maintained KB+ Focused on UKVerifying – 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 - 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.

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+

Global Open Knowledgebase (GOKb)

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?

15

GOKb architecture

GOKb Key Deliverables

GOKb will use a rules engine to cleanse and normalize ERM data from heterogeneous sourcesThe rules engine will accept rules from the community of functional experts without coding!Code development has begunGOKb will be deployed as a cloud service

GOKb as Central Data Source for Kuali OLE

17

Kuali OLEIndiana

University

KB+King’s College

London

Kuali OLENC State

Kuali OLEUniv Penn

18

GOKb will be OLE’s knowledge base A library management system must have an integrated knowledge base

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

19

Engaging subject matter experts

20

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

21

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

22

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

Library Book LifeCycle

23

Buy

CirculatePreserv

e

Library E-Content Lifecycle

24

Create bundle

License

Purchase

Manage access

Manage changes

Evaluate

Archival access

25

Questions?

How will OLE use GOKb?