Katie Wallis
My feedback
12 results found
-
28 votes
An error occurred while saving the comment -
56 votes
An error occurred while saving the comment We'd like this ability, too! We'd like to be able to have a different courtesy notice for faculty than we send for students. Right now there's only one notice template and it's either on for everyone or off for everybody.
-
42 votes
-
228 votes
An error occurred while saving the comment Does this happen when using "change date" instead of "renew"? Because I thought being in recall status did prevent an item from being renewed.
-
4 votes
-
58 votes
An error occurred while saving the comment This would be really great. Inventory is important for finding missing items, but as it is now, it's so cumbersome.
-
94 votes
An error occurred while saving the comment This would be really great to have.
-
149 votes
An error occurred while saving the comment Absolutely this should be enacted! Besides being a featured that's needed- allowing patrons to set their own password from Primo- it's also confusing that it reads like it already is a function but isn't.
I assumed 'force password change on next login" meant in Primo for patrons. I couldn't figure out why it wouldn't work until doing an Ex Libris support ticket where I found out it (inexplicably) only applied to Alma. Alma accounts are only library staff. Sure that's good, but what about the majority of users, the patrons- who only use the Primo side. Everything else about the user account in Alma is available in Primo to the patron- their name, email, address, loans, overdues, etc.
I realized I'm talking about what could be 2 separate things- 1) being able to change the password from one's own Primo patron account and 2) the function of Primo forcing a password change. As far as I know, neither of these are true. But they should be.
-
156 votes
An error occurred while saving the comment This is a very important part of doing inventory of a collection! Please add this function.
In addition, the wording on the Ex Libris documentation for "Shelf Report" <https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/Physical_Resource_Management/016Managing_Physical_Resources/Managing_Physical_Item_Inventory_Using_Shelf_Reporting> makes it sound like you can already do this: "you are able to manage Physical Inventory to see if items are in place, misshelved, or missing." It is not until you actually use Shelf Report that you realize what you call "misshelved" is not what the documentation means by "misshelved".
-
156 votes
Hi,
This is to update that this issue is still not planned to be developed in the current road map. We will continue to evaluate it for a future release.
Therefore we are keeping this under "Under review" status.
Best regards,
Yael.
An error occurred while saving the comment This would be really great.
-
299 votes
An error occurred while saving the comment Oh, this would be fabulous.
-
51 votes
An error occurred while saving the comment Report failure and zero usage are two VERY different things, and we need to know which it is. We want to know when a database zero usage, and we need to know that's specifically what it is. Not to mention, no one wants to waste time trying to fix a SUSHI report only to find out there's nothing wrong at all except that no one has used the database during that time period.
"How to prevent printing specific slips and notifications at specific locations" would be a useful workaround for this except that making use of these instructions results in flagging any unsent messages as errors even though it's working as you intended by inserting the bit of XSL. Which means you can no longer tell real errors from the "errors" created by XSL working as intended. I submitted a support ticket to Ex Libris and they said that these error flags were working as intended. Therefore the solution described at <https://knowledge.exlibrisgroup.com/Alma/Knowledge_Articles/How_to_prevent_printing_specific_slips_and_notifications_at_specific_locations> is not a viable solution until the error messages stop showing up because of XSL working correctly.
So we're definitely interested in having this feature to enable/disable letters at the library level.