| Summary: | Add ability for library staff to fill a hold with a specific item | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Nick Clemens (kidclamp) <nick> |
| Component: | Hold requests | Assignee: | Bugs List <koha-bugs> |
| Status: | NEW --- | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | andrew, gmcharlt, kebliss |
| 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
Nick Clemens (kidclamp)
2023-08-31 15:05:45 UTC
Can you explain the use case a bit more? Why would a return not trigger the hold for the item? (In reply to Katrin Fischer from comment #1) > Can you explain the use case a bit more? Why would a return not trigger the > hold for the item? The vagaries of cataloging often result in separate bibs for items that are functionally equivalent. For example, if a library maintain distinct bib records for different formats of the same work (paperback/hardcover/etc), the library may want to fill the hold with an available item on a different bib than was originally requested. |