Joe Montibello
My feedback
28 results found
-
7 votes
-
37 votes
An error occurred while saving the comment -
18 votes
An error occurred while saving the comment 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.
-
81 votes
An error occurred while saving the comment This 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.
-
3 votes
An error occurred while saving the comment This is spam and should be deleted.
-
47 votes
An error occurred while saving the comment This feels more like a bug than an enhancement request. I hope it can get enough attention to get it fixed.
-
55 votes
-
34 votes
An error occurred while saving the comment 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
-
135 votes
-
317 votes
-
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?
-
72 votes
-
81 votes
-
70 votes
-
1 vote
-
6 votes
-
5 votes
-
14 votes
-
12 votes
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.)