Knowledge base group2CUL TSI Knowledge Base Task Force
Membership: Adam Chandler, Susan Marcin, Jesse Koennecke, Evelyn Ocken , Jesse Koennecke
Charge:
Definition of a Knowledge Base (KB):
(draft) A knowledge base is a singular place to track resources/titles (items). The act of tracking items extends beyond the item itself and includes the ability to assign meaningful and relevant associated information about that item and to perform actions upon the item. This includes assigning licensing information and documents, troubleshooting information, administrative and statistical logins, and associated contact(s) and pertinent information/notes about the item. And it also includes populating front-end systems and services, such as MARC records, OpenURL systems, database pages, e-journal pages, Web discovery systems, and possibly patron authentication.
(consulting basis)
Sponsors: ????
DRAFT Charge:
The team will examine the Knowledge Bases (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 services across 2CUL. The urgency for this comes from the assumption that the Alma knowledge base KB is expected to handle a number of functions services 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 team will examine the current and future landscape of KBs in use at each CUL. Additionally, the team will provide the 2CUL Alma negotiating team has with 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:
...
, and recommend some specific requirements and milestones for Alma regarding knowledge base quality, functionality, and interoperability with third party systems.
The team will produce a brief (less than 10 page) report, by April 1, 2014 addressing the following:
- Inventory of KB-dependent services at each CUL and which KBs are central to each service
- Identify dependencies on core KBs, such as Serials Solutions
- Explore harmony and discord across KBs generally and specific to our environments including workflow and input/output streams.
- What changes to the above are expected with Alma as a central KB
- Alma negotiation questions – Identify any specific KB questions and milestones that should be part of the Alma negotiating
...
- 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.
...
- team’s specifications