François Renaville
My feedback
32 results found
-
53 votes
An error occurred while saving the comment -
176 votes
An error occurred while saving the comment François Renaville
commented
We also have tens of thousands outdated user notes created on Aleph. Too many for a systematic manual cleaning!
I think that we would have never migrated all these user notes if Ex Libris implementation team would have told us that it was not possible to run batch deletion jobs on them... We would have cleaned our user records in Oracle before the final migration. :-(
François Renaville
supported this idea
·
-
94 votes
An error occurred while saving the comment François Renaville
commented
I agree with this suggestion.
I think it should not only be limited to the PO Line and invoice attachments, but to all attachments in general in Alma. I find it really odd for example that someone with a Circulation Desk Operator - Limited role can delete attachments from a User record tab.François Renaville
supported this idea
·
-
59 votes
An error occurred while saving the comment François Renaville
commented
Agreed!
We have been using the "Return Receipt Letter" since 2015. We were considering disabling this letter since all loan/return actions are stored in Alma and available to patrons in their MyAccount. Before disabling the letter, we decided however to run a survey and to ask our patrons about it and if they find it useful. 30% replied they would prefer not to receive such a letter anymore while 66% replied they like it and appreciate to receive a return confirmation by email. Since there is no opt-in/opt-out possibility for this letter, we have no real good option for our patrons.
Among the 30% who would prefer not to receive the "Return Receipt Letter", several pointed out that:
(1) they receive already many emails,
(2) this is overcommunication from the library,
(3) it is useless energy consumption.François Renaville
supported this idea
·
-
35 votesFrançois Renaville
supported this idea
·
-
60 votes
An error occurred while saving the comment François Renaville
commented
Some configuration possibilities for the limitation of the length would indeed be great!
-
80 votes
An error occurred while saving the comment François Renaville
commented
Thanks a lot, Ulrich! It works perfectly! I have just added some similar lines for Bibtex in custom.js:
app.component('prmExportBibtexAfter', {
bindings: { parentCtrl: '<' },
controller: function() { this.parentCtrl.encodingVal = 'UTF-8'; },
template: ''
});and both do the job! :-) Thanks again!!
François Renaville
supported this idea
·
-
73 votesFrançois Renaville
supported this idea
·
-
41 votes
An error occurred while saving the comment François Renaville
commented
Generally speaking, behavior should normally always be the same in the front-end wherever records are from (Alma or Aleph records vs PCI vs external harvested sources). Patrons should ideally not suffer from the origin of the records to have Primo functionalities working as expected (i.e. as they think they should work). Functionalities that are limited to a part of the whole content (e.g. Browse) are rarely understandable for patrons…
François Renaville
supported this idea
·
-
8 votesFrançois Renaville
supported this idea
·
-
99 votes
An error occurred while saving the comment François Renaville
commented
@Laura: Some weeks ago, a Primo customer (not on Primo VE) showed me a usage comparison of the "Send To" functionality Primo Classic UI vs Primo New UI. While the usage of "Send To" was very limited in the Classic UI, it was incredibly massive on the New UI! This was really a big surprise for everyone! So, the current position of "Send To" may meet a real demand from the patrons that librarians are not always aware of. Libraries with some months of experience with the New UI may be interested in comparing the usage of "Send To" in Primo Classic UI vs New UI before deciding to put it at a less visible place. My 2 cents…
-
19 votesFrançois Renaville
supported this idea
·
I agree with Jessie. Completed purchase requests (rejected or approved) should ideally not be visible in the MyAccount. It does not make sense to display them while completed and canceled Resource Sharing or Hold requests are not. This is something that patrons are claiming about.