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 |
|---|---|---|---|---|---|
| 7408 | WEB - Web Services | hold status visibility |
Ability to configure which hold statuses are visible to patrons. |
KCLS | |
| 7411 | WEB - Web Services | 'not wanted after' holds |
Patrons have the ability to manage their holds calendar. For each hold or group of holds, a patron may specify a date after which the item(s) will not be wanted. A hold will be cancelled automatically if it is not delivered by the designated date. |
KCLS | |
| 7412 | WEB - Web Services | freezing holds |
Patrons can freeze any hold at any time, except those on the hold shelf. Hold continues to move up within the queue but will not trigger while frozen. Patron can specify a date to 'unfreeze' the hold. |
KCLS | |
| 7410 | WEB - Web Services | default hold pickup location |
When placing a hold in the OPAC, the pickup location defaults to the patron's home branch. A drop-down list allows the patron to change the hold location for each hold or group of holds. |
KCLS | |
| 7218 | WEB - Web Services | holds ready for pickup |
The patron holds list displays the date by which each hold must be picked up. |
KCLS |