KCLS Requirement Status
Below is a list of requirements/features/enhancements that are KCLS published when they began their road down Evergreen. Some requirements are in active development. Some have been deferred. Still others are already part of Evergreen (this was a list of requirements, not a gap analysis). As time permits, the KCLS team will be updating each requirement with its status so the rest of the community knows what they've got actively on their plate.
| ID | Functional Area |
Short name |
Description | Contributor | KCLS Status |
|---|---|---|---|---|---|
| 6026 | INT - Interfaces, Ancilliary Products | transactional communication |
System supports transactional communication with external services, for example providing APIs to read and update patron records, bibliographic records, item records, etc. |
KCLS | |
| 2154 | ACQ - Acquisitions - Selection and Ordering | transactions post in real time |
All transactions post in real time: including purchase orders, invoices, fund balances, vendor balances, vendor statistics and history, etc. |
KCLS | |
| 5628 | MGT - Management | transactions report |
The system can generate a report of transactions (holds placed, holds filled, and check-outs) per patron, per branch, per cluster, per system, per county, per GIS sector, and per library jurisdiction. The system displays the number of check-outs and placed holds per patron. Holds are subtotalled by type, e.g. active, frozen, and frozen-until holds. |
KCLS | |
| 5255 | ACQ - Acquisitions - Selection and Ordering | transfer holds between bibliographic records |
Ability to transfer holds from one bibliographic record to another, singly or in batch, sorting by date of original hold request. |
KCLS | |
| 2495 | ACQ - Acquisitions - Selection and Ordering | transfer records between bibliographic records |
Ability to transfer item records, order records, and holds from one bibliographic record to another (e.g. when duplicate records are merged). |
KCLS |