Joe Montibello
My feedback
33 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 commentedI 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 · -
7 votesJoe Montibello supported this idea ·
-
37 votes
An error occurred while saving the comment Joe Montibello commentedThis 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.)
-
18 votes
An error occurred while saving the comment Joe Montibello commentedThis 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 · -
84 votes
An error occurred while saving the comment Joe Montibello commentedThis is a great idea. I have a report to tell me if any configuration changes have happened, but most of the time it gets me an attachment with just the words "The query resulted in no rows". This is not at all helpful and makes it difficult for me to sort out when configuration changes actually happened.
I also agree that it should be optional, so that some reports would be sent even if empty or in error.
Joe Montibello supported this idea · -
3 votes
An error occurred while saving the comment Joe Montibello commentedThis is spam and should be deleted.
-
47 votes
An error occurred while saving the comment Joe Montibello commentedThis feels more like a bug than an enhancement request. I hope it can get enough attention to get it fixed.
-
55 votesJoe Montibello supported this idea ·
-
34 votes
An error occurred while saving the comment Joe Montibello commentedOut 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 votesJoe Montibello supported this idea ·
-
135 votesJoe Montibello supported this idea ·
-
317 votesJoe Montibello supported this idea ·
-
66 votesJoe Montibello supported this idea ·
-
114 votes
We are exploring options for this idea. The priority of the results is set by either Primo or Summon, so we cannot simply show the newest edition first unless the discovery ranking changes. However, we could potentially develop an option using the Questions feature in which the system could recognize that the instructor has added something which has other editions. The library could then configure a question for the instructor to understand if they want that edition, any edition, or the newest edition, for example. Would this help meet the need?
Joe Montibello supported this idea · -
72 votesJoe Montibello supported this idea ·
-
81 votesJoe Montibello shared this idea ·
-
70 votesJoe Montibello supported this idea ·
-
1 voteJoe Montibello shared this idea ·
-
6 votesJoe Montibello shared this idea ·
-
5 votesJoe Montibello shared 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.