Joe Montibello
My feedback
30 results found
-
167 votes
Hi all,
This is planned to be handled in the Primo Next Discovery Experience User Interface.
More details on the new interface planning can be found here -
Best regards,
Yael.
An error occurred while saving the comment An error occurred while saving the comment Joe Montibello commented
I can't believe this has been a thing since 2017 and it still hasn't been fixed. This is not a good user experience at all.
Joe Montibello supported this idea ·
-
13 votes
Joe Montibello supported this idea ·
-
40 votes
An error occurred while saving the comment Joe Montibello commented
This is completely necessary. (having an import button on a page like this - which already has an export button - would allow libraries to readily update the whole table and be another solution to this problem.)
-
29 votes
An error occurred while saving the comment Joe Montibello commented
This should be simple to achieve - just add a parameter to the Citation Material Types Code table that allows us to set each type as belonging in the "most common" section or not. We have several material types that we'd like to add in that section.
Joe Montibello supported this idea ·
-
47 votes
An error occurred while saving the comment Joe Montibello commented
This feels more like a bug than an enhancement request. I hope it can get enough attention to get it fixed.
-
58 votes
Joe Montibello supported this idea ·
-
34 votes
An error occurred while saving the comment Joe Montibello commented
Out of votes but I like this one - we have code that can detect some duplicate user records, and being able to act on them via API would be great!
-
18 votes
Joe Montibello supported this idea ·
-
137 votes
Joe Montibello supported this idea ·
-
316 votes
Joe Montibello supported this idea ·
-
70 votes
Joe Montibello supported this idea ·
-
75 votes
Joe Montibello supported this idea ·
-
81 votes
Joe Montibello shared this idea ·
-
69 votes
Joe Montibello supported this idea ·
-
1 vote
Joe Montibello shared this idea ·
-
6 votes
Joe Montibello shared this idea ·
-
5 votes
Joe Montibello shared this idea ·
-
287 votes
An error occurred while saving the comment Joe Montibello commented
I wouldn't think that the change Moshe suggests would be very helpful here. Figuring out a percentage that would work for multiple different hourly loan values might be tricky, but most of all it would make it hard for staff to know right away when courtesy notices are expected to go out. Anything that makes it hard to predict what the system will do makes it much harder to troubleshoot when something goes wrong (whether it's a system problem, human error, or just the perception that "this isn't happening the way I expect it to").
Just my two cents' worth. Take care,
Joe Montibello -
510 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.
Joe Montibello supported this idea ·
-
12 votes
Joe Montibello supported this idea ·
Any update on this? The tooltip that was under review (in 2022) is now in place, as many others have commented, but it never addressed the idea that was raised back in 2017 - over six years ago.
Jesse Kruppa's comment from March 2023 explains in great detail why this behavior is broken for users.
This is pretty elementary user experience stuff that just needs to be fixed.