François Renaville

My feedback

  1. 304 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    An error occurred while saving the comment
    François Renaville commented  · 

    Here is another example with CDI HathiTrust collections. None of the CDI HathiTrust collections are activated in our Alma production environment. However, we still get HathiTrust records in search results. I assume they are displayed because of the Match & Merge process, they are considered as records from an alternative collection. This is however very confusing for end-users since (most of the) HathiTrust journal records do have a volume and year indication at the end of the title and that it is most of the time incoherent with access information.

    For example:
    The Yale review. : n.s.,v.1 (Oct 1911-July 1912) (cdi_hathitrust_hathifiles_njp_32101076433117)
    View It: Wiley Online Library - Available from 1997 volume: 85 issue: 1.

    Journal of the Franklin Institute of the State of Pennsylvania. : v.182 (Jul-Dec 1916) (cdi_hathitrust_hathifiles_njp_32101073435453)
    View It: Elsevier ScienceDirect Journals - Available from 01/01/1995 volume: 332 issue: 1.

    Additionally, HathiTrust records are flagged as being in Open Access, which is obviously not always the case with the most recent issues being available with a library subscription!

    I provided the following scenario in case 00915010: https://www.screencast.com/t/Ur5ns6jAX
    1) Our library provides online access to the "Journal of dental research" (ISSN 1544-0591) from vol 78 (1999). SAGE Portfolio is activated in Alma.
    2) Beside the Alma record, there are 4 other HathiTrust records: 1 record per year from 1919 to 1922 (but we have NO access to years 1919-1922).
    3) When clicking on "Journal of dental research. : v.3 (1921)", View It says that the library provides access from 1999...
    --> This does not make sense at all from an end-user's perspective...

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

    Thanks for submitting this idea, Stacey! It would indeed be very nice if libraries could retain control over what CDI content appears in Primo. CRL Catalog is a real issue for us (#00889287): journal (!) records (in addition to the local Alma records, https://www.screencast.com/t/SggijMgE) and false positive linking (https://www.screencast.com/t/PhNpgdmDZup). Really annoying for a PCI/CDI collection that we have NEVER activated in the last 8 years…

    I wish there could be a way for a CDI Inventory Operator to exclude/blacklist some CDI Electronic Collections or some specific CDI records to prevent them to be displayed in Primo. We sometimes report major metadata or linking issues to Ex Libris that rely on vendor response. It can takes months and months before getting a solution (if any). If we could locally take action and hide problematic CDI records (a bit like the Suppress from publishing process), but we would at least be able to locally fix those issues for our patrons.

    François Renaville supported this idea  · 
  2. 25 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Primo » Primo VE  ·  Admin →
    François Renaville shared this idea  · 
  3. 87 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  · 
  4. 31 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Alma » Other  ·  Admin →
    An error occurred while saving the comment
    François Renaville commented  · 

    I completely agree! There should be a better distinction between the Main Menu and the Configuration Menu.

    François Renaville supported this idea  · 
  5. 19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Alma » Analytics  ·  Admin →
    François Renaville supported this idea  · 
  6. 50 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  · 
  7. 13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    An error occurred while saving the comment
    François Renaville commented  · 
  8. 288 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    24 comments  ·  Alma » Other  ·  Admin →

    Alma team has decided to provide the ability to choose a color scheme by the user.
    The user will be able to change the color scheme via the UI preference menu based on institution policy. The institution’s administrator will be able via “Alma Logo and Color Scheme” to enable or disable users to choose a color scheme. Also, there will be a special option for the administrator to provide the ability for a specific user to choose a color scheme via the user details screen. Another improvement Alma team plans to provide is a high contrast color scheme each user will be able to choose regardless of institution policy

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

    Thanks for the update!

    If I'm not mistaken, the new colors with the January 2020 release are still at the institutional level. So, there is no possibility (or not yet?) for staff user to define their own Color Theme, which is important in terms of Accessibility since color experience may be very different from one individual to another.
    Please correct me if I'm wrong.
    Kind regards,

    Fr.

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

    Thank you!

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

    Update: with the November 2017 release, we can now select one of 11 basic colors! Well, everything seems to be going in the right direction...

    François Renaville shared this idea  · 
  9. 40 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  · 
  10. 4 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  · 
  11. 626 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  · 
  12. 661 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    François Renaville shared this idea  · 
  13. 40 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. 70 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  · 
  15. 5 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  · 
  16. 134 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    François Renaville shared this idea  · 
  17. 19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    François Renaville shared this idea  · 
  18. 140 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. 74 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    An error occurred while saving the comment
    François Renaville commented  · 

    I support this very much!

    François Renaville supported this idea  · 
  20. 54 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    11 comments  ·  Alma » Other  ·  Admin →
    An error occurred while saving the comment
    François Renaville commented  · 

    Hi Rosemary,

    Several messages related to this topic were posted on the Alma list in January 2018.
    Subject: "ACQ: Interested In letter for e-books -- way to include URL?"
    https://exlibrisusers.org/private/alma/2018-January/

    François

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

    Hi Rosemary,

    Some customers added a URL to their Interested In letter. It might not be exactly what you need, but it takes a user to the appropriate MMS ID in Primo (deep link). The MMS ID was added in the XML outpout some months ago.

    Example for the Classsic UI:
    <a><xsl:attribute name="href">https://<BASE_URL>.exlibrisgroup.com/primo-explore/search?tab=default&vid=YOUR_VIEW_ID&query=any,exact,"<xsl:value-of select= '/notification_data/mms_id' />"</xsl:attribute> <xsl:value-of select="notification_data/title"/></a>

    Example for the New UI:
    <a><xsl:attribute name="href">https://<BASE_URL>.exlibrisgroup.com/primo_library/libweb/action/search.do?fn=search&amp;ct=search&amp;initialSearch=true&amp;mode=Basic&amp;tab=default_tab&amp;indx=1&amp;dum=true&amp;srt=rank&amp;vid=YOUR_VIEW_ID&amp;frbg=&amp;vl%28362751202UI1%29=all_items&amp;vl%281UI0%29=contains&amp;vl%28freeText0%29=<xsl:value-of select= '/notification_data/mms_id' /></xsl:attribute> <xsl:value-of select="notification_data/title"/></a>

    François Renaville supported this idea  · 
← Previous 1 3

Feedback and Knowledge Base