Skip to content

François Renaville

My feedback

40 results found

  1. 62 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Primo » Primo VE  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    François Renaville supported this idea  · 
  2. 21 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    François Renaville shared this idea  · 
  3. 129 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    François Renaville supported this idea  · 
  4. 281 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Primo » Primo VE  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    François Renaville shared this idea  · 
  5. 53 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    François Renaville commented  · 

    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.

  6. 177 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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  · 
  7. 94 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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  · 
  8. 59 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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  · 
  9. 35 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    François Renaville supported this idea  · 
  10. 60 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    François Renaville commented  · 

    Some configuration possibilities for the limitation of the length would indeed be great!

  11. 123 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    François Renaville shared this idea  · 
  12. 79 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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  · 
  13. 73 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    François Renaville supported this idea  · 
  14. 41 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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  · 
  15. 219 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    François Renaville supported this idea  · 
  16. 206 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Hi,

    Makes sense ! Currently, the user information that is displayed in the user Ajax search results (e.g. patrons services WB) is hardcoded.

    A mapping table, similar to the one that configures the user pop up, will control the fields that show in this list. The mapping table will enable the same fields that the user pop up allows, and allow setting the order of the fields.

    Thanks,

    An error occurred while saving the comment
    François Renaville commented  · 

    It would be nice if this new mapping table would not only contain the existing values of the Contact Information Pop-Up configuration table (Email, Gender, Home Address, Name, Office Address, Preferred Identifier, Primary Identifier, Telephone, Title, and User Group), but *also* the ones already existing in the Display User Name configuration table where middleName, jobDescription, and userTitle can also be displayed (I’m echoing Chris’ comment here). Campus would certainly also make sense!

    In our case, we could display the jobDescription info via the Display User Name configuration table. This would be easy to distinguish A from B in the ajax listing of results. But this would also impact all letters where user’s <name> is used to be replaced by a <first_name> <last_name> combination.

    @Tammy: If you have in your user records a value in the ‘Middle name’ field, you can use it already for display with the Display User Name configuration table.

    An error occurred while saving the comment
    François Renaville commented  · 

    Thanks! :-)

    François Renaville supported this idea  · 
    An error occurred while saving the comment
    François Renaville commented  · 

    Hi Moshe,

    I think it does not. The configuration option via the "Contact Information Pop-Up" menu helpful when there is a user icon where staff can click on. The context of the original request is Fullfiment > Manage patron services where no such icon exists and where namesakes can hardly be differentiated https://www.screencast.com/t/qHBYkXVq

    Thanks.

    François

  17. 273 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    François Renaville commented  · 

    Thank you, Moshe!

    François Renaville shared this idea  · 
  18. 156 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    François Renaville commented  · 

    I agree that 'Peer Reviewed' is not really appropriate in an Availability facet group. Note however that the library changes the Facet Label from 'Availability' to for example 'Show only' or 'Keep only', incongruity disappears. This works also for 'Open Access'. My 2 cents...

  19. 99 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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…

  20. 510 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    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.

    An error occurred while saving the comment
    François Renaville commented  · 

    This would indeed safe time and make things clearer for customers. Thanks for submitting this idea.

    François Renaville supported this idea  · 
2 Next →

Feedback and Knowledge Base