| Summary: | Allow ability to make OPAC hold pick-up location mandatory | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Lucas Gass (lukeg) <lucas> |
| Component: | OPAC | Assignee: | Owen Leonard <oleonard> |
| Status: | NEW --- | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | andrew |
| 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
Lucas Gass (lukeg)
2021-08-02 16:29:36 UTC
I'm curious, what is the motivation for forcing patrons to select a library? Under what circumstances is the user's home library not an appropriate default? (In reply to Owen Leonard from comment #1) > I'm curious, what is the motivation for forcing patrons to select a library? > Under what circumstances is the user's home library not an appropriate > default? Some librarians in multi-branch systems want users to consciously make a decision about where they will pickup the hold. I can see the utility of forcing a choice. As Lucas says, I've talked to libraries that want this. If we're creating a new syspref and monkeying with this field, could we go a step further and make the syspref something like OPACHoldPickupDefault with the options (Patron home library / Item home library / Item holding library / Force a choice). (In reply to Andrew Fuerste-Henry from comment #3) > I can see the utility of forcing a choice. As Lucas says, I've talked to > libraries that want this. > > If we're creating a new syspref and monkeying with this field, could we go a > step further and make the syspref something like OPACHoldPickupDefault with > the options (Patron home library / Item home library / Item holding library > / Force a choice). +1, I like this. |