François Renaville

My feedback

  1. 187 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Primo » Primo VE  ·  Admin →
    François Renaville supported this idea  · 
  2. 41 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    François Renaville supported this idea  · 
  3. 17 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Primo » Primo VE  ·  Admin →
    François Renaville commented  · 

    Agreed! External names for libraries would be really convenient.

    François Renaville supported this idea  · 
  4. 132 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Primo » Primo VE  ·  Admin →
    François Renaville commented  · 

    Very happy to see that Primo VE September 2019 release allows us now to display an Open Access indicator for Dublin Core records! Thanks a lot for this first step in the right direction! Kudos!
    (Note that only Display is effective, the OA Top Level facet does not keep dc records where dcterms.accessRights has been added.)

    Looking forward to seeing something similar for the Peer-reviewed indicator now! Hopefully, the Peer Reviewed Top Level facet will allow patrons to display only peer-reviewed records. Otherwise, it would really be misleading to display Peer-reviewed information and to exclude all concerned records when using the facet...

    François Renaville commented  · 

    Thanks for creating this idea!

    We removed the Open Access and Peer-reviewed facets from our Primo VE Top Level section precisely because external data and Alma records are automatically excluded when using these facets. It would really be great if NRs could allow this!

    That Alma records are excluded with the Open Access and Peer-reviewed facets is really incomprehensible: PCI Articles published in "Nature Communications" are flagged as Open Access and Peer-Reviewed, but the journal itself (Alma record) not, although fields 500 and 506 contain the expected values...

    François Renaville supported this idea  · 
  5. 17 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Primo » Other  ·  Admin →
    François Renaville commented  · 

    Yes! This would be so useful!

    François Renaville supported this idea  · 
  6. 43 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    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.

    François Renaville supported this idea  · 
  7. 78 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Alma » Fulfillment  ·  Admin →
    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  · 
  8. 69 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Alma » Acquisitions  ·  Admin →
    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  · 
  9. 26 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Alma » Fulfillment  ·  Admin →
    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  · 
  10. 60 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Alma » Fulfillment  ·  Admin →
    François Renaville commented  · 

    This is simply common sense!

    François Renaville supported this idea  · 
  11. 25 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Alma » Fulfillment  ·  Admin →
    François Renaville supported this idea  · 
  12. 50 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    François Renaville commented  · 

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

    François Renaville supported this idea  · 
  13. 199 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    François Renaville supported this idea  · 
  14. 27 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Alma » Acquisitions  ·  Admin →
    François Renaville shared this idea  · 
  15. 170 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    François Renaville commented  · 

    I agree. This would be a most welcome enhancement!

    François Renaville supported this idea  · 
  16. 51 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    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  · 
  17. 8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Alma » Fulfillment  ·  Admin →
    François Renaville supported this idea  · 
  18. 73 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    François Renaville supported this idea  · 
  19. 147 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    François Renaville supported this idea  · 
  20. 37 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    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  · 
← Previous 1

Feedback and Knowledge Base