Default digitisation department for digital request types
Ability to set a default digitization department for each digitization request type.
Currently in Leganto, you can set a default digitization department for readings digitization requests. What we would like to do is to set a default digitization department for the patron digitization requests, and staff digitization request types within fulfillment.
This is because when the patron request type is created within Primo, no managing department is set - unlike those same request types when lodged within Alma, where the managing department can be set.
When the request is lodged via Primo, it seems to pick the managing department based on alphabetical order, resulting in patron digitization requests being sent to the readings digitization department - just because of the order in the list of departments.
Being able to set the default digitization department based on the digitization request type - ie patron vs staff would ensure that the correct fall-back department is always set for requests made within the discovery layer, and in the case of staff digitization requests would ensure a supporting department gets the request in the case where the managing department wasn't set.
This assumes there is no current plans to add requesting TOUs to do the same thing, but might still be useful.
Matthew Hooper
shared this idea
Hello All,
This idea has been closed as part of a cleanup process for ideas older than two years with fewer than 20 votes.
This cleanup process is necessary to streamline our idea management process and ensure that the most relevant and impactful ideas receive the attention they deserve. If you still feel strongly about this idea, you may submit it via the NERS process.
We value your feedback and encourage you to continue submitting and voting for ideas that you believe will enhance Alma.
Alma Product Team
-
Julie Wright
commented
We have our Circulation desks support digitization so that patron digitization requests go to the relevant Circ desk for the item. If this suggestion was to go ahead we would not want our current workflow changed at all.