| Summary: | Ability to specify sequence of items placed on hold (cascading holds) | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Nicole C. Engard <nengard> |
| Component: | Hold requests | Assignee: | Bugs List <koha-bugs> |
| Status: | NEW --- | QA Contact: | |
| Severity: | new feature | ||
| Priority: | P5 - low | CC: | gmcharlt, jrobb, kyle, magnus |
| Version: | Main | ||
| Hardware: | All | ||
| OS: | All | ||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Comma delimited list of Sponsors: | |
| Crowdfunding goal: | 0 | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
|
Description
Nicole C. Engard
2012-09-24 11:35:45 UTC
Nicole mentions items connected to the same record, but Cascading Holds could also be something to think about accross records, when you have e.g. a series of books that patrons might want to read in sequence. Series statements in 490 (in MARC21) would come into play here, I guess: https://www.loc.gov/marc/bibliographic/bd490.html |