Katie Wallis
My feedback
19 results found
-
267 votesKatie Wallis supported this idea ·
-
28 votesKatie Wallis supported this idea ·
An error occurred while saving the comment -
56 votes
An error occurred while saving the comment Katie Wallis commentedWe'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.
Katie Wallis supported this idea · -
42 votesKatie Wallis supported this idea ·
-
544 votes
Dear all,
I believe we now understand the requirement better: To be able to paste a block of text in MARC 21 format, and have Alma parse it and populate the MARC tags, indicators and subfields accordingly.
This is a larger development, but we hope to be able to add a solution for it to our future roadmap.
Katie Wallis supported this idea · -
230 votesKatie Wallis supported this idea ·
An error occurred while saving the comment Katie Wallis commentedDoes this happen when using "change date" instead of "renew"? Because I thought being in recall status did prevent an item from being renewed.
-
4 votesKatie Wallis supported this idea ·
-
62 votesKatie Wallis supported this idea ·
An error occurred while saving the comment Katie Wallis commentedThis 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 Katie Wallis commentedThis would be really great to have.
-
149 votes
An error occurred while saving the comment Katie Wallis commentedAbsolutely 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.
Katie Wallis supported this idea · -
168 votes
The 'Claimed Returned' action will be available for lost loans. It will change the loan status to 'claimed returned'.
A customer parameter will determine whether the change to claimed returned should trigger a 'Find Item' action (and refund the lost item fees) + change to 'claim return', or only change to 'claim return'.
An error occurred while saving the comment Katie Wallis commentedWe can't mark it as found in order to mark it as claims returned. That would prompt an automatic notice to the patron that the item has been found! Which it clearly has not or else we wouldn't need claims returned! To do so would be confusing not just for us, but for our patrons, too.
Katie Wallis supported this idea · -
156 votesKatie Wallis supported this idea ·
An error occurred while saving the comment Katie Wallis commentedThis 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".
-
512 votes
We are investigating the options for enhancing the job reports as part of a general enhancement to the jobs UX, which will then allow gradually deploying report enhancements to the different jobs in Alma.
Katie Wallis supported this idea · -
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 Katie Wallis commentedThis would be really great.
Katie Wallis supported this idea · -
299 votesKatie Wallis supported this idea ·
An error occurred while saving the comment Katie Wallis commentedOh, this would be fabulous.
-
196 votes
Dear Community,
This is to update you that we plan to develop this requirement in a future Alma release.
The PO line price could be automatically copied to the item's "Replacement cost" field in the following scenarios:
- Upon PO line creation
- When changing the PO line price
- When adding or removing items to/from the PO line.
We plan to allow this by settings 2 customer parameters:
(1) One that will turn the functionality on and off, and will have the following values:
0- false
1- copy the price from the PO line's "List price" field
2- copy the price from the PO line's "Net price" field and divide by number of items in the "Ordered Items" section.
(2) Another that will allow to add or reduce amount from the PO line price when being copied to the "Replacement cost" field. This will allow:
- To add/decrease amount…An error occurred while saving the comment Katie Wallis commentedYes, I would also like to know when this will be done.
An error occurred while saving the comment Katie Wallis commentedI'm surprised this wasn't a function in Alma already. No one at our library even thought of this as having to be a separate step (it didn't seem to be so in Voyager) and hence none of the items we've added since migration have anything in the "replacement cost" field.
-
51 votes
An error occurred while saving the comment Katie Wallis commentedReport 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.
Katie Wallis supported this idea · -
236 votes
The proxy relation between two users will have an expiration date. After the expiration date, the proxy relation will be considered inactive, and be ignored by the system.
The date of expiry will be updateable in the Proxies tab of the user form.
Katie Wallis supported this idea · -
287 votes
We are considering incorporating the idea and effect both templates and rules editing permission
Katie Wallis supported this idea ·
"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.