Summary: | Add Granular options to CircConfirmItemParts | ||
---|---|---|---|
Product: | Koha | Reporter: | Lisette Scheer <lisettepalouse+koha> |
Component: | Circulation | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | andrewfh, bugzilla, clackman, gmcharlt, kebliss, kyle.m.hall, lisettepalouse+koha, lucas, rcoert, wdeschamps |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Bug Depends on: | 25261 | ||
Bug Blocks: |
Description
Lisette Scheer
2021-03-17 18:32:15 UTC
+1 on this! This is a great new feature, but it's really easy to come up with scenario's like Lisette's in which a library would like this for only certain item types, collections, etc. Being able to turn this on/off per itype would be a great next step. We'd also love to be able to limit the verification to just checkin, as opposed to both checkin and checkout. We work on the assumption that if an item's been checked in, then it's been checked for all its parts and so we don't need to do that again when checking the item out. It also prevents items with multiple parts from being checked out by patrons at the self-checks, which can be irritating for them. Yes!!! 1) Re: Lisette; control feature via itype or ccode would be helpful. 2) We use/want this at check-in. We, too, operate assuming the item is good to go at check-out, so confirmation is unnecessary. But having a toggle to decide if we'd like it to operate at only check-in, or only check-out, or both would be a great "feature." This would be an extremely helpful feature! Agree with the group that limiting by itemtype would be the preferred way to do this. |