"Skip location" in "Pickup from shelf"
We would like to be able to choose which location to send a request to when skipping a location in the "Pickup from shelf" task list.
On the Pick-Up Requested Resources page, if the Skip Location action is available (the request can be fulfilled by at least one other location that the request has not been previously assigned to), a Manual Skip Location action now displays in addition to the Skip Location action
For more information please see:
https://knowledge.exlibrisgroup.com/Alma/Release_Notes/010_2019/Alma_2019_Release_Notes#Select_Request_Locations
-
-
Gro Heidi commented
Is the url correct? Today, one month after publication of the answer/solution, I can't find any information at https://knowledge.exlibrisgroup.com/Alma/Release_Notes/010_2019/Alma_2019_Release_Notes#Select_Request_Locations
-
Maryke Barber, Hollins commented
Thank you for addressing this. We've been told the proposed solution will address an issue our library has encountered. In case an additional scenario is of use, I am posting it here:
Background: our library, Hollins University, shares a system and materials with Roanoke College. In addition to a main library, Hollins also has a separate Music Library. In Alma, the Music Library is included in the same campus as our main library, but has a separate Fulfillment Unit so that members of both schools/campuses can request materials from the Music Library (it has deliver to/circulate for relationships with both).
This Case: The attached request is from a Hollins patron, for an item owned by both our Music Library, and by Roanoke College. Apparently because Roanoke printed their request slips before us, the system sent the request to Roanoke - even though a library on the Hollins campus owns the requested item, and that item is on the shelf.
I would expect that Alma's selection algorithm, as described here: https://knowledge.exlibrisgroup.com/Alma/Product_Materials/Alma_FAQs/Fulfillment/Request_Management#How_does_Alma_'choose'_the_copy_that_will_fulfill_a_request.3F would include a parameter that would prioritize an item available on the same campus. However, that's not how the system behaved in this case. -
Esther Thegel commented
(I just wanted to add that we don't have any campus libraries, we just have one main library and two branch libraries, so this "same campus preference" wouldn't help us... We would need a possibility to configure a "preferred libraries" list. )
-
Esther Thegel commented
Hello,
We reported a case concerning requests in Sales Force and were told to write what we need in this Idea.Here's our problem:
We have three libraries, the main library (Huvudbiblioteket) and two branch libraries (Karlberg and HKV/Högkvarteret). If a book isn't available at one of the libraries and we make a request in Alma, we need to be able to configure which library that should be the preferred one, the one that the pick from shelf request should go to in the first place. We want to be able to make the request on the title level, but still choose the library that should get the request first, if it's available at two of them. This is because it always takes less time to order a book from the main library and it always takes quite a lot to time to order from the branch library Karlberg.
We thought that this could be made by configuring the "Transit time rules" in the Fulfillment configuration. We therefore put the "delivery time" to be 36 hours for the preferred transit and 48 hours for the not preferred transit. We then saw that this didn't work when I ordered four books for a patron to be picked up at one of our branch libraries (Karlberg). All four books were available at the main library, but Alma sent two of the requests to the main library (the books that were only available there) and the two other requests to the other branch library (the books were available both at the main library and at the other branch library). I then reported the case to Sales Force and was told to describe what we need here.
What we need is a possibility to configure to which library a request should go, if there are several items available at different libraries, but they have to be moved to the pickup location.
Here's the kind of preference list we would like to make in Alma (when the requested book is not already available at the pick-up location)
1. Main library (requests from the two branch libraries should always go to the main library first)
2. HKV branch library (requests from the main library should go here first, if the book is not available at the main library, but at the two branch libraries)
3. Karlberg library (since it takes a bit longer time for these books to be sent and this library is closed on Fridays, this library should be of least priority, if the books are available at another one of the libraries)So what is needed for us is a functionality where a library preference list can be made.
Best regards
Esther Thegel -
Gro Heidi commented
@Moshe "If all locations have been used and Skip Location is attempted, the system will warn the user and suggest to cancel the request"
--> Please (also) suggest "convert to resource sharing" -
Hi,
We would like to take the below approach to this issue:
1. The mechanism for automatically selecting the holdigns to fulfill a request makes use of the pickup location, preferring a holdings that is in the same library as the required pickup.
An additional consideration will also take into account the campus. Holdings in libraries of the same campus as the pickup location should be preferred.
2. The same considerations will be used by the Skip Location
3. Skip location will remember what locations were previously used, and not skip to them again. If all locations have been used and Skip Location is attempted, the system will warn the user and suggest to cancel the request
4. The transit time from the item library to the pickup location will also be cosidered (also when selecting the initial holding to fulfill the request)
Thanks,
Moshe -
Bente Hatlevoll commented
Absolute necessary. Several of our Campus Libraries are located many miles from each other and some are located in the nabohood. We would like to choose where to skip the request.
-
S. Kerber commented
Perhaps this feature will solve also our problems in the SNLP-workflow discussed in case #00406206 ("Unfortunately there isn't any configuration available in Alma that can be used in order to control the order of the owning libraries that can fulfill Lending Requests if multiple items exist in different libraries.")?
-
Hege Raklev commented
Hi Kjetil,
we tried to configure Transit Time, but that did not have any effect on Alma`s choice of pick up location. -
Kjetil Sletteland commented
Would/could configured Transit Time influence Alma's choice of pickup location?
-
LivB commented
Hei Moshe,
You asked: "In what scenarios would you like to have the operator explicitly select the next holdings ?"
We would like to select the next holding when we click on Skip Location from Pick From Shelf.
See the comment from Kjetil Sletteland, he explains this problem clearly. The point is to avoid sending books from a distant city (but still in the same institution), when a copy is available in a closer holding. -
Chris Jones commented
Hi Moshe,
Yes, that does sound sensible in terms of prioritisation for the skip option. Can see that perhaps see the holdings (perhaps analogous to Manage fulfillment option in lending requests?) might also be useful as an override for some users. -
Hi,
Perhaps improving the automatic skip selection would be best. For example, Alma should consider also the campus when selecting the hodings to skip to, so that an available library that is in the same campus as the pickup location should be preferred. Would that make sense ?
Thank you,
Moshe -
Marco Tomassini commented
In our university, shared in two different cities (Florence and Pisa) with different libraries belonging to the same library system, some scholars move from one location to another for didactical or research purposes. It can be useful for them to choose the pick up location for they move easily than the books!
-
Kjetil Sletteland commented
Moshe, some institutions have several campuses in one city (A), some of which have more than one library, and also campuses in other cities (B, C). Alma will often send requests from A to B or C, despite there being items available on shelf in city A, even in another library at the same campus.
-
Hi,
In order to achieve as much an automated process a possible, Alma attempts to implement automatic processes where possible rather than rely on manual ones.
For this reason, requesters and librarians do not choose the exact holdings to be used for fulfilling a request when a new request is created. Instead, the system does that automatically using some business logic, such as preferring available holdings that are shelved at the requested pickup location (minimizing the need for transit).
The same rationale is used for automatically selecting the next location when the current one needs to be skipped.
In what scenarios would you like to have the operator explicitly select the next holdings ?
Thank you,
Moshe