Ability to Configure Borrowing Requests Status in Primo
The status of borrowing requests is displayed in the user's account (MyLibrary) in Primo. The statuses are not very user-friendly as they are the Alma statuses that are meant for staff. For example, "Locate failed" is quite disturbing for a user to see when checking the status of their resource sharing borrowing request.
We have been told that these values are in a hidden table in Alma and cannot be translated. We would like to be able to configure this table, or be able to map these statuses in a better way.
-
The June 2018 Release now included a new option: The borrowing request statuses code table is now available for customization and translation. The customized values are displayed in Primo and in the requests list on the Patron Services page. See here for more details https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/030Fulfillment/080Configuring_Fulfillment/090Resource_Sharing#Configuring_Borrowing_Request_Statuses
-
Esther Arens commented
Brilliant!
-
karen.danbolt@ub.uio.no commented
Yes, agreed!
-
Turid Næss commented
Yes
-
Alea Henle commented
Also agreed -- customization is necessary. The existing language is not user-friendly. And because different libraries use different workflows (with or without integration of ILL software with Alma), we each need the ability to specify the language for the phases most likely to appear for our patrons.
-
K. Colburn commented
Agreed, Anything "failed" is poor terminology for a patron-facing (even a staff-facing) message or label. "In progress" or "awaiting status" - though not my first choice - would be better. Customization is quite necessary when it involves what patrons see.
-
Esther Arens commented
There's another status label we'd like to change that's hard-coded too, so maybe we could widen this idea to make all patron-facing label customisable?
Thanks!
-
Glenn Karlsen Bjerkenes commented
This would be a great change. We receive a lot of questions from worried users on why their request is "locate failed" when we haven't even started working on it yet. At the very least the statuses should be translated into something else in Primo, if we can't change it ourselves.