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 |
|---|---|---|---|---|---|
| 1633 | INT - Interfaces, Ancilliary Products | batch delete |
Ability to run mass deletions without significantly impacting system performance. |
KCLS | |
| 1636 | INT - Interfaces, Ancilliary Products | SIP2 and NCIP2 support |
System supports SIP2 and NCIP2 for interfacing with external applications. Support standard SIP2 and NCIP2 messages, and provide capacity for adding additional messages as formats evolves. |
KCLS | |
| 1637 | INT - Interfaces, Ancilliary Products | telephone notices: call grouping |
Telephone notifications are grouped, so that patrons receive a maximum of one call per notice type per day. |
KCLS | |
| 1638 | INT - Interfaces, Ancilliary Products | telephone notices: prioritization |
Telephone notifications can be prioritized by several criteria, including the type of notification; the number of notifications that will be included in a single call; and whether previous call attempts have failed. Call queue is prioritized prior to beginning the day's calls. |
KCLS | |
| 1652 | INT - Interfaces, Ancilliary Products | ecommerce error messages |
The system is able to parse vendor error codes, in order to provide specific and user-friendly error messages. |
KCLS |