Annual Reviews 2015-2017 packages

The title lists for the Jisc Collection Annual Review package are now available on KB+, please remember that your access will depend on which collection you have subscribed to and also, when the initial subscription was taken.

Those institutions who subscribed after 2008 will have different access entitlements to those who subscribed before 2008 as per the licence. I have added this identifier in the package name for example –

Annual Reviews:Jisc Collections:Biomedical/Life Sciences Collection (22 titles):2015-2017 (post 2008 subscribers)

Annual Reviews:Jisc Collections:Biomedical/Life Sciences Collection (22 titles):2015-2017 (pre 2008 subscribers)

If you subscribe to one of the Annual views packages outside the Jisc Collection offer and would like to see these added to KB+ then please let the KB+ team know.

What does KB+ do today?

I’ve been getting myself up to speed with KB+ developments in preparation for a talk I’m giving and thought I’d share my notes on what KB+ does now (based on Liam’s presentation to JISC Collections). Respect to the implementation team!

  • Replaces manual records and filing cabinets for ERM
  • Maintains local subscription data in one place (currently nesli2 deals)
  • Populated from generic, verified subscription information held by JISC Collections
  • Maintains list of journal entitlements for ‘big deals’ (packages) for each year
  • Enables packages to be linked with one or more publisher or aggregator platforms
  • Can edit start dates and end dates for individual journal titles (useful for keeping link resolvers up-to-date)
  • Enables ‘core’ titles to be identified for each subscription year (the titles that are so often ‘in dispute’ with publishers at renewal)
  • Links journal subscription data and entitlements to the relevant licenses
  • Provides summary license terms ‘at a glance’, showing ‘rights’: e.g. Coursepacks, Interlending, Walk-in, Partners, etc.
  • Allows original licenses (documents) to be uploaded
  • Allows for local and shared Notes to be added
  • When changes are made to generic subscription data or licenses, library staff are alerted to accept (or reject) local changes
  • Journal titles and entitlements can be edited individually or in batches to suit local needs
  • Packages can be copied to act as templates for new packages or created from scratch

Editorial on KB+ for UKSG eNews

We put together an overview of KB+ for UKSG eNews.

It provides a good overview of the project aims, outputs and plans for the future as of July 2012.

The article is available at: Knowledge Base+ for UKSG subscribers, or on the JISC Collections web site a:

Maximising the Knowledge Base

Last week we completed three days of meetings in London (6-9 July) bringing together expertise from the JISC Collections KB+ and Global Open Knowledgebase (GOKb – project partners from North Carolina State University and the University of Pennsylvania plus technology partners Knowledge Integration (

GOKb was funded in June 2012 by the Andrew W. Mellon Foundation to build a community-sourced knowledgebase for access to e-resource metadata. It aims to enhance the supply chain lifecycle for libraries in managing e-resources, mobilizing community effort to add quality, timeliness and economies to the library management environment. The project is a joint international initiative between Kuali OLE partners (including Chicago, Duke, Penn and NC State) and JISC Collections.

The UK KB+ project is focused primarily on developing trusted data and workflows for locally negotiated e-resource packages. KB+ recognizes the value of the GOKb international effort in establishing the same quality of data for global titles and packages, covering e-journals and looking beyond to e-books.

The two projects are therefore working together in detail to address globally-identified operational problems, including common transfer formats (KBART-based), data models, rules engine and re-use of the Kuali OLE Document Store repository (

The meeting was focused on defining key joint tasks for coming months:

  • Identification and classification of sources of periodic information within the publishing supply chain – for example publisher title lists. Whilst this may sound obvious and straightforward, practitioners are keenly aware of issues regarding format, content and provenance that differ from source to source.
  • Definition of rules and remedial actions relating to the processing of source data – which will range from format standardisation (such as dates) to much more complex update conditions.
  • Specification of an end to end process model and toolset to ingest, transform and process updates with a minimum of human intervention, whilst recognizing the points at which such expertise will be essential (at least in the formative period of operation where rules will need to be optimised and ‘learned’ by the system).
  • Design of a shared data model so that KB+ and GOKb are able to share code (such as the rules base), to present a one-stop approach to import/export in common formats and to identify opportunities for shared services based on once-only management of data.

The partners left London sensing there is even greater scope for collaboration and shared services than was originally envisaged. The challenge will be to convert that opportunity into quality data, code and services, starting with the next joint working group in Chicago in August.

David Kay

KB+ and GOKb project teams in discussion

Testing KB+

Today is an important day in phase 1 as we start the process of testing KB+ with institutions.

We’ll be holding a workshop in London to:

To brief the 10 supporting institutions on development scope and progress

  • To show the results of the work so far
  • To kick start the reports definition work
  • To highlight the work to be undertaken by libraries in the period to mid-July
  • To introduce the means of communication and sharing files

As you can see below It will be a fairly intense day of activity covering the entirety of the data collection and development process to date and what we’ll be looking for the testing institutions to do over the next 6 weeks:

The Data –

  • The model
  • The collection and ingest process
  • What has been entered
  • The review application
  • How libraries can help – checking data (Testers, perhaps everyone), checking the model (SMEs)

Authentication, Authorisation & Access to KB+ –

  • The approach adopted
  • What libraries need to do to get log ins

Introduction to the User Interface development –

  • What have we prioritised and why
  • The things JISC Collections will maintain
  • Repeated concepts – Type, Status, Organisations,
  • Generic operations – Documents & Alerts, Combinations
  • Achieving the right look and feel – Mickey & Mallory

User Interface demo –

  • The Review Application
  • Licenses
  • Subscriptions
  • Entitlements
  • Adding documents
  • Making combinations

Working Groups –

  • Reports
  • User Interface
  • Workflow

Review & Testing Process –

  • Accessing supporting documents
  • Reporting problems
  • Documenting feedback

Reports Design –

  • Fixed development budget
  • Discussion of reports we have in mind
  • Design and testing process

Next Steps –

  • Reviewing the data
  • Accessing the UI
  • Checkpoint conference calls
  • Next Meeting – 9 July

I don’t know about the rest of the team, but I am both very excited that we have managed to get to this point in such a short period of time, but also nervous about what ‘real’ users will say when they see the data that has been collected and how it has been structured.

The project team has always looked at how to improve the data it has available and constantly improving it in response to our own discussions and critiques, putting it in front of the people who we hope will make use of KB+ in the long term is an essential part of the process, but also a moment of truth.

Knowledge Base+ at Day One

We’ve reached the point in the development of KB+ where we are pretty confident about what we’ll deliver on day one 1st September 2012.

I’ve divided it all up into the data that will be there, the services that will be provided and what libraries and suppliers can do.

We’d really welcome comments…

What data will be there?

Functionality in Place

Activity Undertaken by JISC Collections

Opportunity for Users to Add Data

Title, package, platform and coverage for the current NESLi2, SHEDL, WHEEL and JISC eCollections agreements – in excess of 12,000 titles

Wherever possible institutional entitlements to the above (based on JISC Collections data and local institutional data)

Licence information covering key values such as authorised user, remote access, ILL, use in course packs, post-cancellation access

Non-JISC Collections agreements. Currently we have IEEE publication information, we hope that institutions will add more data on agreements during the testing phase


What services will be available?

Functionality in Place

Activity Undertaken by JISC Collections

Opportunity for Users to Add Data

Additions and changes will be made centrally by JISC Collections in the initial phase, based on information sourced from the community

Monthly usage statistics will be automatically visible as they are collected by JUSP

New licence information will be added as agreements are made available in elcat


What can a library team do?

Functionality in Place

Activity Undertaken by JISC Collections

Opportunity for Users to Add Data

Add records of institutional licences and entitlements through data entry and/or upload


Access and compare key licence terms and related notes


Enter and access current alerts, notes and documents, such as the status of negotiations, issues and guidance with licences, service availability. Including display of current alerts.


Share intelligence (issues, queries, knowledge and responses) across the community


Set privacy levels for your data and documents


Produce reports such as A-Z lists, licence information, renewal dates etc


What can suppliers do?

Functionality in Place

Activity Undertaken by JISC Collections

Opportunity for Users to Add Data

Provide feeds of new records and updates by arrangement with JISC Collections  

Receive feeds of accurate contextualised deal information on publications and associated licences for the agreements covered by KB+ for use in their own knowledge bases