1. KB+ & GOKb: The Kuali OLE Community Model for E-Resources Management
Sponsored by
Owen Stephens – Owen Stephens Consulting
Michael Winkler – University of Pennsylvania

2. Overview What GOKb is and status of the project
How GOKb is working with Kuali OLE
The KB+ project - what it is and how it is working with GOKb
A look into GOKb
Next steps for GOKb

3. GOKb Partners

4. GOKb Timeline 2012 2013 2014 2015 2011 2016 And we are creating
GOKb Public Release
GOKb Phase I: Proof of Concept Release
GOKb and KB+ collaborate on data model
2012
2013
2014
2015
2011
2016
Community development New partners
Enhanced functionaity
Funded by Mellon Foundation & Kuali OLE Partnership
GOKb Phase II:
Partner Release
And we are creating
Data model
Software & workflow
Community of practice

5. GOKb in the Lifecycle of Licensed Content
Select
Package
Trial
License
Activate
Buy
Manage
Troubleshoot
Manage Changes
Assess
Measures of Value
Use
Costs
The Knowledgebase supports, at each stage, management of resources

6. Using GOKb Data Publishers National KBs Content Providers Catalogs
Subscription Agencies
Open Web
Vendor KBs
Library E-Resource Community
Library Management Systems

7. International Cooperation?

8. 3rd Party Systems & Services
GOKb in the Ecosystem
Publisher Data
Package information
Standard licences
Global (GOKb)
National/Consortial information
National licences
Central Services
National (KB+)
Local holdings
Financial information
Documentation
Local (OLE)
3rd Party Systems & Services

9. Kuali OLE & GOKb GOKb is the knowledgebase for Kuali OLE
Kuali OLE will consume data (and publish too) from GOKb RESTful interfaces
Kuali OLE partners are committed to the accuracy, timeliness, and maintenance of GOKb
GOKb is supported by Kuali OLE, but is an open resource to all
GOKb will bi-directionally integrate with Kuali OLE
Coordinated data model for mapping GOKb data into Kuali OLE – KBART-like, with extended data elements
Data contributors
Other editors
OLE Partner editors
GOKb Editors

10. Kuali OLE Workflow with GOKb
Provider Package File
Users
CRED Process
Select
Package
Trial
License
Activate
Buy
Manage
Troubleshoot
Manage Changes
Assess
Measures of Value
Use
Costs
GOKb
GOKb RESTful API
Request Process
Bib, Item, Platform, Requisitions
Discovery Process
Open Refine Editing
Update Process

11. Roadmap Synchronization
Kuali OLE 1.0: Integration Release
Kuali OLE 1.5: Early Adopter Release
Kuali OLE 0.8: Testing Release
Kuali OLE 2.0: Partner Release
2013
2014
2015
Kuali OLE – GOKb: Full Integration
2013
2014
2015
GOKB Phase 1: Proof of Concept Release
GOKB Phase 2: Partner Release
GOKB Public Release

12. KB+ A shared, open, knowledgebase for UK HE
Minimise duplication of effort across institutions
Data made available under CC0 declaration
Local institutional data as well as national and global data
Communication and Collaboration tools built in
SCONUL Shared Services study prioritises ERM Detailed business requirements developed through 16 detailed case studies in UK HE sector Jisc Collections leads project to establish KB+ as a shared service2012 August – KB+ goes into beta KB+ v3.3 released
Because framed as a shared service from day one, always about ‘above campus’ opportunities
Republish data about e-journal packages as CC0
Community features perhaps unique? 12

13. KB+ Datamodel Simplified KB+ data model
Currently team of data managers at Jisc populate the top half, while institutions can then use that information to setup details of subscriptions (or do so independently) 13

14. KB+ & GOKb Global (GOKb) National (KB+) Local (KB+)
Can see there is a general split between ‘above campus’ and ‘local’ - although with some overlap (e.g. organisations appear on both sides in various roles)
GOKb is in the top part - the Jisc data managers will be able to enter data directly into GOKb, and will be replicated in KB+ as necessary
May still be some ‘above campus’ details in KB+ - e.g. negotiated licences 14

15. A Look into GOKb 15

16. First screen is a dashboard - driven by data issues to review16

17. Can search by any of the key GOKb entities: Titles Packages
Organisations
Platforms
TIPPs
Users
etc. 17

18. Example Package - lots of detail - categorisation of Packages - question is which data to prioritise
Worked with Kuali OLE and KB+ to understand requirements of data to record 18

19. TIPPs - these are representations of ‘Titles in a Package on a Platform’ (Hence TiPP)19

20. Move to the ‘Title’ (or ‘TI’) level - includes publisher history, working on supporting title history. Lists all TIPPs - so from title you can see all packages that include the title 20

21. Organisations - authority list
Organisations have roles - not all Orgs can fulfill all roles
Includes ‘Office’ details for contacts etc.
From an Organisation record you can navigate easily to titles they publish, licences, packages etc. etc. 21

22. Open Refine & GOKb
After looking at a range of options, settled on Open Refine
Built an extension that:
Supports shared workspace
Enforces data integrity
Makes common operations easy to apply
Reviewed several ‘rule based’ software options
Decided Refine was best suited, Open Source, Active Community and established mechanism for extending
Built ‘GOKb Extension’ for Refine (also available as open source) 22

23. Shared workspace
Shared workspace with checkin/checkout workflow makes it easy to collaborate on projects 23

24. Data integrity
Active feedback on state of file at all times, highlighting errors and warnings 24

25. Data integrity
Ability to lookup values from GOKb ensures data quality and authority control on key entities 25

26. Data integrity
Ability to lookup values from GOKb ensures data quality and authority control on key entities 26

27. Quick resolution
All feedback comes with ‘quick resolutions’ to enable editors to resolve issues quickly and easily - especially where standard resolutions are known 27

28. Quick resolution
Example of a quick resolution - rename a column 28

29. Once file has no errors can import (aka ‘ingest’) to GOKb - either as incremental update (normal process) or as a ‘Replacement’ (used when you want to overwrite existing package completely) 29

30. An ingest from Refine typically creates data review tasks in GOKb - taking us back to the dashboard you see when you first login to GOKb. Expect to support more sophisticated task management in future releases 30

31. Next Steps for GOKb & Data, data, data! Continued software development
Recruiting a GOKb Editor
Community engagement:
Editorial workflows
Supply chain
Other projects
&
3 or 4 further releases by the middle of 2014
Including API for integration with Kuali OLE and KB+
the GOKb editor will be responsible for GOKb’s data quality and workflows, and be point person for community contacts about GOKb, including outreach and training. Based at the NCSU Libraries, the GOKb editor will be located in the Acquisitions and Discovery department, and will be one of a cohort of four electronic resources librarians.
Dialogue with the supply chain over real use cases for shared IDs and the GOKb co-referencing service
Develop understanding of community editorial workflows and how they can be enabled within and around GOKb
Appointment
Work with the ONIX-PL Encoding Project
Data, data, data! 31

32. Thank you & Questions Find out more: http://gokb.org
Owen Stephens:
Michael Winkler: