Add "Scan In Items" functions to "Return Items" processing
We would like to build "Scan In Items" features to the "Return Items" function, i.e. "Return Items" should be able to process requests, expired holds, and items in transit between locations the same way as "Scan In Items" does. This includes the radio button for automatically printing slips (configuration should be able to define a default)
Simon Read
shared this idea
-
Nicolas C (Normandy)
commented
On a related subject, I suggested this idea 49523462-simplify-item-scanning-when-processing-is-complete
-
R Candrian
commented
Dear Simon, thank you for bringing up this issue (loooong ago). This is really something I keep on stumbling over when working at the desk. All the items that are returned at our library are scanned in using "return items". But when there is a reservation for an item, the slip that is printed for putting the item on hold is not the same as when I use the functionality "scan in items". With "return items" the letter "FulResourceRequestSlipLetter" is produced, whereas with "scan in items" the letter "FulHoldShelfRequestSlipLetter" is produced. As we have a hold shelf that our customers can access by themselves, we want the letters to be anonymized and looking the same for all reservations. We therefore anonymized the "FulHoldShelfRequestSlipLetter". But we don't want to repeat that with the "FulResourceRequestSlipLetter" as this letter is used in other situations, too (e.g. printing the slip for items on the list "pick from shelf").
I don't understand why there are two different letters. So, as Simon already wrote, sometimes "return items" is better and in other cases "scan in items" is better, but we do not know before scanning an item which option is better in this case. This is annoying. -
Simon Read
commented
Thanks Moshe,
We have logged a couple of cases in the past (167336 and 57810). For 57810 we got told to use scan in items and if we wanted it to work for return items that we should submit an enhancement/ideas exchange hence this post. Subsequently that decision has been reversed and some additional development has been committed to.
We hate having to say to staff they should use scan in items for some things and return items for others so we say to staff they should scan an item through return items to determine next steps. This almost always works but there have been a couple of exceptions in the past.
Any other voters for this request like to add an area where return items doesn't fill your needs and you have to use scan in items instead?
Simon
-
Hi,
The Return Items interface is intended to be the place where checked in items are wanded in, and are automatically moved on through their workflow by the system. That means that putting in transit or managing of personal delivery steps should happen in this interface just as it does in the Scan In Items interface. If this is not your experience, I suggest that you submit a case describing what you're seeing.
Thanks,
Moshe -
Simon Read
commented
An example of where this causes us problems is with the return of on loan items that have a Home Delivery request on them.
All loans are processed through Return Items to determine next steps - in the case of an item with a Home Delivery Request no Home Delivery slip prints. If, however, the item is scanned in via Scan in Items the Home Delivery slip is printed - this is counter intuitive as staff don't know which items have Home Delivery requests on them so they don't know they should scan them in via Scan in Items. It is very confusing for staff.
