https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27340 --- Comment #15 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- (In reply to Marcel de Rooy from comment #14)
Reading this a bit late after the discussion..
I think the current concept of desk and pickup_location is confusing. Pickup location currently is just a subset of branches. A branch/pickup_location may have multiple desks. As I understand, there is a need for multiple pickup locations per branch.
The recent desks feature is very limited though. It only records a checkin in a confirmed hold. I would have expected it too in the issue for instance. (At which desk was the item checked in and checked out?) The patron does only see a reference to a desk on opac-user for waiting holds.
I found this description in kohastructure: `desk_id` int(11) DEFAULT NULL COMMENT 'foreign key from the desks table defining which desk the patron should pick this hold up at', So I am wondering why we do not inform the patron in the HOLD notice about that desk? (Kind of unfinished development?) Note that it looks like desk actually is a pickup location here?
I think the development base is good, but yes, there are definitely missing features to make it more useful. I think in at least some use cases, we'd also like the patrons to be able to pick the desks for pick-up. But at least they should be informed on where the item is waiting exactly.
And adding yet another use case: I would need a pickup location for patron type A (employees) within branch X and a pickup location for patron type B (external patrons) within X. This second pickup location does not make much sense as a separate branch. So, I could switch to 'desks'. But limiting desks is far out of reach?
What do you mean with limiting desks - a limit by patron category? -- You are receiving this mail because: You are watching all bug changes.