Knowledge base group
Membership: Adam Chandler, Susan Marcin, Evelyn Ocken, Jesse Koennecke
Charge:
[Definition of Knowledge Base (KB)]
The purpose of our group, as far as I am aware, is to examine the knowledge bases we maintain for e-resource related work and recommend some specific requirements and milestones for Alma regarding knowledge base quality, functionality, and interoperability with third party systems. The need for this comes from the assumption that the Alma knowledge base is expected to handle a number of functions that we currently rely on other knowledge bases for and it will likely act as the origin of knowledge base information for many third part services as well. We want to make sure the 2CUL Alma negotiating team has the information it needs to be able to push ExLibris to ensure certain quality and functionality is met. We also want to get a better handle on exactly what each knowledge base CUL currently manages. Below is a list (probably not complete) that I thought up a few weeks ago of systems in use at Cornell that require some sort of knowledge base or interaction with another knowledge base to function.
Possible outcomes:
- Alma negotiation – Identify any specific KB needs and milestones that should be part of the Alma negotiating team's specifications. (needed soon)
- Inventory of current KBs and the services that rely on them - what is good, what is bad, what is needed?
- Recommendations for KB needs between now and Alma
Deliverable: A report about the knowledge bases we use, with special attention placed on the dependencies we have on the Serials Solutions KB. Harmony and discord across knowledge bases generally. Workflow. Raise questions. Input/output streams. For example, authorities. Write it quickly, less than 10 pages.
Deadline:July 15