[Koha-bugs] [Bug 31391] Staff-side recalls

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31391

--- Comment #16 from Aleisha Amohia <aleisha at catalyst.net.nz> ---
(In reply to David Nind from comment #14)
> Hi Aleisha.
> 
> Apologies for Failing QA on this again!
> 
> The previous issue reported is fixed (step 7 - can't cancel a recall from
> OPAC when RecallsInterface = staff interface only).
> 
> I've identified a new issue with step 5 - cancelling a recall from the
> recalls section for a record - record doesn't exist after cancelling a
> recall using the 'Cancel selected recalls' button and selecting the normal
> section. 
> 
> To replicate:
> 1. Place a recall
> 2. Go to the recalls section for the record on the staff interface
> 3. Using Actions > Cancel works as expected
> 4. Repeat steps 1 and 2.
> 5. Cancel the recall by ticking the box next to the item and then selecting
> 'Cancel selected recalls' button doesn't work as expected:
>    . The recall is cancelled
>    . URL = http://127.0.0.1:8081/cgi-bin/koha/recalls/request.pl
>    . Breadcrumb = Home > Catalog > No title > Place a recall 
>    . Click on the normal section:
>       message = The record you requested does not exist ().
>       URL =
> http://127.0.0.1:8081/cgi-bin/koha/catalogue/detail.pl?biblionumber=
> 
> I'm not sure if I tested this last time. I'm also sure I've seen this when
> testing something else a while ago, but can't remember or find what bug it
> was.

Fixed in latest follow-up

> 
> Also, for step 13 it is possible to have more than one recall for a record
> or item. Whose recall takes priority, and what is the workflow libraries
> would use to address this?
> - If a recall is already on the record (from the previous step), there are
> now two recalls (a record level one, and an item level one)
> - On the record page is shows "recalled by X on [date]" - for X it shows the
> person who made the latest recall, not the first person who place a recall.  
> - Is this an edge case to be resolved in a separate bug, or a non-issue? 
> - It seems logical that multiple patrons could make a recall request for the
> same record. What would the workflow be for libraries if they were in this
> situation, and how do they resolve this?
> 

I think that is outside of the scope of this particular ticket (because
fulfilling recalls via the staff interface came from the original Bug 19532)
but at the moment the oldest/earliest placed recall will be picked first, and
priority is given to item-level recalls over biblio-level recalls. A follow-up
to all of this would be to introduce a priority field like reserves has, but
that can come after we bring in functionality to place recalls via the staff
interface I think

> 
> David

-- 
You are receiving this mail because:
You are watching all bug changes.