709 results found

1. Support for Email Sending Without Using an Email Client in the NDE UI Email Share Action

   Background:
   In the previous Primo VE UI, it was possible to send emails using Primo VE’s built‑in email functionality when sharing records via email.
   However, in the NDE UI, this functionality has been removed, and the system has been changed so that an email client application must always launch to perform email-based record sharing.
   In this situation, shared public PCs in the library—used for search purposes—cannot run email client software, making it impossible to use NDE’s email sending feature.

   Proposal:
   To resolve this issue, we request support for sending emails using Primo VE’s built‑in functionality in the NDE UI as well.
   To reduce potential security concerns, we believe it would also be acceptable if this feature were only available when the user is logged in to Primo.

   Benefits:
   Users will be able to use Primo’s email-based record sharing feature even on shared public PCs where email client software cannot be used.

   Background:
   In the previous Primo VE UI, it was possible to send emails using Primo VE’s built‑in email functionality when sharing records via email.
   However, in the NDE UI, this functionality has been removed, and the system has been changed so that an email client application must always launch to perform email-based record sharing.
   In this situation, shared public PCs in the library—used for search purposes—cannot run email client software, making it impossible to use NDE’s email sending feature.

   Proposal:
   To resolve this issue, we request support for sending emails using Primo VE’s built‑in functionality in the NDE UI as… more

   • 

   347 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   7 comments  ·  User Functionality  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Make open access indicator appear for all appropriate resources

   Currently, the Primo VE "Open Access Indicator" icon does not appear for resources where the 506 $2 vocabulary value is not equal to "star". This creates a situation in which the open access indicator is not reliable to users as a way to identify freely-available resources.

   According to approved cataloging practice, there are a variety of valid vocabularies that open access 506 values can be taken from. In addition, the STAR (Standardized terminology for access restriction) vocabulary is no longer actively maintained, and its appearance in catalog records will likely diminish over time.

   The Access Restriction Term Source Code List (https://www.loc.gov/standards/sourcelist/access-restriction.html) provides multiple source codes that can be used for the 506 field:
   cc (Creative Commons)
   coarar (COAR Access Rights Vocabulary)
   rs (Rights Statements)
   star (Standardized terminology for access restriction)
   wikidata (Wikidata)

   Primo's open access indicator should also recognize these vocabulary codes as valid sources of information on access restrictions, and assign the open access indicator as appropriate to resources with the relevant codes from those vocabularies.

   Support has advised us that there is no way to locally configure the open access indicator to appear for resources with other vocabularies noted in the MARC 506 field. They have stated that an enhancement will be necessary to change the current logic behind which records get the open access indicator.

   Currently, the Primo VE "Open Access Indicator" icon does not appear for resources where the 506 $2 vocabulary value is not equal to "star". This creates a situation in which the open access indicator is not reliable to users as a way to identify freely-available resources.

   According to approved cataloging practice, there are a variety of valid vocabularies that open access 506 values can be taken from. In addition, the STAR (Standardized terminology for access restriction) vocabulary is no longer actively maintained, and its appearance in catalog records will likely diminish over time.

   The Access Restriction Term Source Code List… more

   302 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  User Interface  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Allow customization of the display on the Primo Services Page so that metadata from the OpenURL doesn't present as a matched resource

   Currently, when a user follows an OpenURL link to a Primo Services page, the page takes the metadata fields from the OpenURL and presents them in a format that mirrors the "Brief record display" from Primo search results and full record displays. This is misleading to users, who assume that the OpenURL has found a match for a resource when in fact they may not have.

   We would like to be able to configure a separate display for the Primo Services Page, so that we can make it clearer to users that what they are seeing is a formatted version of the metadata, and not necessarily a citation for a legitimate resource. The need for this has always existed, but we believe it is becoming more pressing as we are seeing increasing numbers of fake, AI-generated citations in databases that generate links to our Primo.

   Currently, when a user follows an OpenURL link to a Primo Services page, the page takes the metadata fields from the OpenURL and presents them in a format that mirrors the "Brief record display" from Primo search results and full record displays. This is misleading to users, who assume that the OpenURL has found a match for a resource when in fact they may not have.

   We would like to be able to configure a separate display for the Primo Services Page, so that we can make it clearer to users that what they are seeing is a formatted version… more

   206 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  User Interface  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Primo NDE UI: Introduce Dark mode

   Our users are complaining that the new UI is too bright and causes eyestrain and specifically requesting a Dark Mode option. We have also developed our new website using the same materials/components as are used in the NDE to align our visual identity so we know that it is possible with the tools at hand. Lastly, I recently saw this article and the first thing it mentioned is that young people want dark mode: https://www.choice360.org/libtech-insight/5-surprising-things-ive-learned-about-gen-z-college-students/

   213 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   6 comments  ·  User Interface  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Incorporate a systematic review content type/filter into Primo

   Systematic reviews are key to evidence based medicine practice. They “... establish whether scientific findings are consistent and can be generalised across populations, settings, and treatment variations, or whether findings vary significantly by particular subsets (Mulrow, 1994).” They also identify existing gaps in the literature requiring further research. The number of systematic reviews published has grown from less than 50 a year in the early 1990s to almost 36,000 in 2022 (Brignardello-Petersen, 2025) Health sciences researchers, clinicians and students would benefit from the ability to efficiently limit search results to systematic reviews in Primo with a corresponding content type/filter. Currently users must search for “systematic review” as keywords or subject terms which are inconsistently applied across CDI sources. Similar filters exist in other search platforms including PubMed and EBSCOhost CINAHL and Medline.

   https://www.elsevier.com/connect/why-systematic-reviews-matter

   1. Mulrow CD. Rationale for systematic reviews. BMJ. 1994 Sep 3;309(6954):597-9. doi: 10.1136/bmj.309.6954.597.

   2. Brignardello-Petersen R, Santesso N, Guyatt, GH. Systematic reviews of the literature: an introduction to current methods. American Journal of Epidemiology, 2025 Feb; 194(2):536–542 doi:10.1093/aje/kwae232

   Systematic reviews are key to evidence based medicine practice. They “... establish whether scientific findings are consistent and can be generalised across populations, settings, and treatment variations, or whether findings vary significantly by particular subsets (Mulrow, 1994).” They also identify existing gaps in the literature requiring further research. The number of systematic reviews published has grown from less than 50 a year in the early 1990s to almost 36,000 in 2022 (Brignardello-Petersen, 2025) Health sciences researchers, clinicians and students would benefit from the ability to efficiently limit search results to systematic reviews in Primo with a corresponding content type/filter. Currently… more

   171 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  User Functionality  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Restore One-Click Permalink Access in NDE Brief and Full Record Displays

   As a library staff member and end user, I would like direct, one-click access to copy a permalink from both the brief and full record displays so that I can quickly and efficiently share stable links to resources without navigating through multiple menu layers.

   Description:

   In the original Primo VE UI, both brief and full record displays include a dedicated permalink button that allows users to access a permanent link to a resource with a single click. This streamlined access is essential for common workflows including:

   • Reference and instruction staff sharing resources with students and faculty
   • Liaison librarians embedding links in course management systems
   • Researchers capturing citations and sharing resources with colleagues
   • Students bookmarking materials for later access

   In the NDE UI, the permalink functionality has been moved behind a "Share" button, requiring users to:

   • Click the Share button
   • Identify and select the permalink option from a menu
   • Then copy the link

   This additional step creates friction in a high-frequency task and reduces discoverability of this essential feature—particularly for users who may not intuitively associate "sharing" with generating a permanent link for personal use or citation purposes.

   Requested Enhancement:

   Restore a dedicated, top-level permalink button (or clearly labeled "Copy Permalink" option) in both brief and full record displays in the NDE UI.

   This should be:

   • Visible without requiring interaction with another button
   • Enabled by default in new NDE views (the "share options" button is disabled by default at time of writing)
   • Positioned prominently alongside other primary record actions

   This change would maintain feature consistency with the original UI and support established user workflows without requiring retraining or workarounds.

   As a library staff member and end user, I would like direct, one-click access to copy a permalink from both the brief and full record displays so that I can quickly and efficiently share stable links to resources without navigating through multiple menu layers.

   Description:

   In the original Primo VE UI, both brief and full record displays include a dedicated permalink button that allows users to access a permanent link to a resource with a single click. This streamlined access is essential for common workflows including:

   • Reference and instruction staff sharing resources with students and faculty
   • Liaison librarians embedding links… more

   •  

   •  

   •  

   •  

   157 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  User Interface  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Primo NDE: Make the display of user initials independent of the sort order for user names in Alma

   In Primo NDE, when a user is logged in, the initials are displayed according to the sort order for user names defined in Alma (Configuration > User Management > User Details > User Name Display). If the sort order is set to "lastName, firstName" ("Smith, John") in Alma the initials will display as "SJ" in Primo.

   We think it should be possible to configure these two appearences indenpendently. It should be possible to sort user names as "lastName, firstName" in Alma, but display the initials in Primo as "firstName lastName".

   112 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   6 comments  ·  User Interface  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Primo NDE: Full Record Services - split up View It/Get It into its separate sections to allow reordering

   When configuring a view (either NDE or VE) in the Full Record Services tab, getit_link1 (View It/Get It) includes BOTH of the sections View It (Default label: View Online) and Get It (Default label: Get It, sub label: Locations). The combined sections works in Primo VE because requests are included in Get It. However, now that NDE has a new separate Requests section, the original View It/Get It should be split into its separate sections to allow institutions to customize the order of all three sections.

   For our institution, we want View Online at the very top as online access is a priority for our users, but this forces us to have Locations above Requests. This ordering is confusing and looks especially wrong in records that are print only. Ideally we would like services ordered as View It (View Online), Requests, Get It (Locations), but this is not currently possible with View It/Get It combined as they are in Full Record Services.

   Ex Libris advised that we could customize the order using CSS, however, this approach is inaccessible, and introduces the potential for problems with ordering in future releases.

   When configuring a view (either NDE or VE) in the Full Record Services tab, getit_link1 (View It/Get It) includes BOTH of the sections View It (Default label: View Online) and Get It (Default label: Get It, sub label: Locations). The combined sections works in Primo VE because requests are included in Get It. However, now that NDE has a new separate Requests section, the original View It/Get It should be split into its separate sections to allow institutions to customize the order of all three sections.

   For our institution, we want View Online at the very top as online access… more

   •  

   43 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  User Interface  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. NDE UI - Improving UX locations section

   The request buttons on item-level are not easily found by our users.
   Please note, we have activated item-level requesting for all records, because it seems more logical and straightforward to have all the request buttons in one place. We do not believe returning to title-level requesting is the solution here, but enhancements in the locations section in the NDE UI could improve the experience.

   The various UX-issues of the locations-section are:

   1. The 'arrow' button is not a clear button
      Customers gave us feedback that they find it hard to see you can elapse or collapse cards. They blantly state that they can’t find certain services, not even noticing the arrows. There is no clear affordance that says "open me", nor labels to give it away.

   2. The positioning of the buttons is not logical
      The hierarchy and sequence of buttons is confusing. Your eye needs to jump from left-to-right all the time, thus it does not have a good visual hierarchy nor a logical focus point flow for your eyes. This results into people missing buttons, or being confused.
      The "Call to action"-arrow to open a card appears on two different locations as well, which does not help with discoverability or logical decision-making for the end-user (see point 1).

   3. The "elapse-collapse all" icon is not a universal sign

   Solving this with CSS has proven not to be a durable solution. CSS updates we have made (screenshots added below) are broken every month when Primo updates parts of the standard CSS. We have looked into the Angular components, but this solution is not stable enough to be trustworthy yet.

   Needed solutions are, in our opinion:

   1. Position all buttons to the right
      So your eyes do not need to go from left-to-right constantly, keeping focus and giving direction.
      The request buttons should also be grouped to the right, but the redesign of the html did not allow for us to do that any longer.

   2. Give the arrow a clear label
      In this case the call-to-action is viewing the services.

   3. Put the availability label next to the location button
      So it’s clear whether it is useful to go to the library in the first place.

   4. Add a label to the “expand all” button
      Just like “filter by”.

   5. Optionally: make the links less prominent, to reduce clutter.

   We believe that improvement to the section could be useful for all libraries using the NDE UI.

   The request buttons on item-level are not easily found by our users.
   Please note, we have activated item-level requesting for all records, because it seems more logical and straightforward to have all the request buttons in one place. We do not believe returning to title-level requesting is the solution here, but enhancements in the locations section in the NDE UI could improve the experience.

   The various UX-issues of the locations-section are:

   1. The 'arrow' button is not a clear button
      Customers gave us feedback that they find it hard to see you can elapse or collapse cards. They blantly state that… more

   •  

   •  

   •  

   •  

   •  

   •  

   •  

   •  

   59 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   7 comments  ·  User Interface  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Add Journal Read and Publish Details to Alma and Make Them Discoverable in Primo

    As libraries continue to add more read and publish journal agreements, it’s important that researchers are able to easily discover which journals are part of these agreements, the open access article publishing charges that are and are not covered by these agreements, and other relevant details related to open access publishing from the library’s read and publish agreements.

    There are several open access journal discovery products that provide end users with this kind of information, but they must perform searches on separate platforms, and library staff must maintain these holdings outside of Alma.

    Examples include:

    ChronosHub: https://stanford.chronoshub.io/?q=%220021-9371%22&journaltitle=Journal%20of%20British%20Studies

    Open Journal Finder by Consortia Manager:

    https://university-of-south-carolina-columbia.openjournalfinder.com/journals/yYP1r3?p=eyJxIjoiam91cm5hbCBvZiBicml0aXNoIHN0dWRpZXMifQ%3D%3D

    The above products use data from a variety of sources, such as publishers, OpenAlex, etc., to gather journal APC costs, publishing activity at the library’s university, and more. Libraries can add notes about their read and publish agreements that display in the corresponding journal records. And journals whose APCs are included in a library’s read and publish agreements prominently indicate that there are no costs for researchers to publish open access articles.

    This would need to be a cross-product enhancement involving Primo for end user discovery, Alma for electronic resources management and licensing aspects of transformative agreements, Alma Analytics for tracking publishing usage of these agreements and combining it with COUNTER read data, and content operations for the metadata for APC costs, institutional publishing activity, etc.

    As in the examples above, some read and publish/APC metadata will appear in brief search results (e.g., whether the APC is covered by the library agreement). At the same time, more details would be available in full journal records (such as Creative Commons licenses, a publisher description of the journal’s scope so authors can determine relevant journals for their research, unique details about the read and publish agreements that the library can customize from within Alma, publishing activity in that journal at that institution, open access publishing instructions for authors (customizable by library), etc.. Researchers would need to be able to use facets to limit their search results to journals whose APCs are covered by their library’s read and publish agreements.

    Use Cases:

    Researchers wanting to find open access journals without any author fees could search Primo using limiters for journals included in their library’s read and publish agreements and subject areas. 
    
    Libraries could achieve a greater return on investment from their read and publish agreements by making their offerings more visible at the point of need. The information would be easy for researchers to understand, reducing the need for library staff to respond to questions about eligible journals and OA author publishing costs. 
    
    Researchers would not need to search a third-party platform; they could simply use Primo to find this information, a tool they are already familiar with. 
    
    Library staff would not need to maintain read and publish holdings in a separate system; they would be managed in Alma alongside the library’s other electronic resources. 
    
    Library staff could run Analytics reports on their researchers’ utilization of the publishing parts of read and publish agreements to more easily assess their return on investment and inform renewal decisions. 
    

    Justification

    Libraries are investing more and more of their acquisitions budgets in read and publish journal agreements, and researchers need the ability to easily discover these details via Primo searches. Providing details about whether or not researchers need to pay to publish open access articles helps researchers make informed decisions on where to publish and better comply with government open access mandates across the world. It could also help libraries achieve a greater return on investment from these agreements and more easily assess them to make data-informed renewal decisions.

    As libraries continue to add more read and publish journal agreements, it’s important that researchers are able to easily discover which journals are part of these agreements, the open access article publishing charges that are and are not covered by these agreements, and other relevant details related to open access publishing from the library’s read and publish agreements.

    There are several open access journal discovery products that provide end users with this kind of information, but they must perform searches on separate platforms, and library staff must maintain these holdings outside of Alma.

    Examples include:

    ChronosHub: https://stanford.chronoshub.io/?q=%220021-9371%22&journaltitle=Journal%20of%20British%20Studies

    Open Journal Finder… more

    124 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Natural language search in NDE should support customized local resource types

    Some of our consortium members who are testing Primo NDE have discovered that our custom resource types do not work with Ask Anything (the natural language search) in Primo NDE. For example:

    The search "i need print books about water" returns only ebooks. Due to our custom "print books" resource type, only e-books remain in the OTB "books" resource type in Primo.

    The search "i need audiocassettes on bach" returns only audio CDs, as we have custom resource types for other audio formats (audiocassettes, lp records, etc.).

    The search "i need videocassettes on figaro" returns only streaming videos, as we use custom resource types for physical video formats (videocassettes, DVDs, Blu-Ray, etc.).

    In general, none of the custom resource types is selected - instead, the natural language search appears to default to the OTB resource types (if there is one).

    Users who interact with our catalogs on a daily basis are used to seeing resource type labels that are often customized to our collections. So it's understandable that they will use those resource type names in their natural language searches. NDE's natural language search should be able to transform those phrases into searches for the accurate resource type - especially since the customized resource types appear in (working) facets that are available for Primo users who are not employing natural language search.

    Some of our consortium members who are testing Primo NDE have discovered that our custom resource types do not work with Ask Anything (the natural language search) in Primo NDE. For example:

    The search "i need print books about water" returns only ebooks. Due to our custom "print books" resource type, only e-books remain in the OTB "books" resource type in Primo.

    The search "i need audiocassettes on bach" returns only audio CDs, as we have custom resource types for other audio formats (audiocassettes, lp records, etc.).

    The search "i need videocassettes on figaro" returns only streaming videos, as we… more

    118 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  User Functionality  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Apply the Primo NDE color theme to Primo Research Assistant

    In the Primo NDE interface, the selected UI color theme is not applied to the Primo Research Assistant (RA).

    Even when a custom theme color is configured for the NDE view (e.g., orange), several RA interface elements still appear in the default blue color, such as:
    - the AI stars icon
    - the "Start a new topic" button
    - navigation arrows in the RA interface.

    According to Clarivate support, this behavior is expected because the RA interface is controlled by CDI rather than Alma customizations.

    Expected behavior: The selected NDE UI color theme should also apply to the Primo Research Assistant interface, so that RA elements follow the same theme as the rest of Primo.

    Benefit: This would ensure visual consistency and institutional branding alignment across the entire Primo interface, including the Research Assistant.

    In the Primo NDE interface, the selected UI color theme is not applied to the Primo Research Assistant (RA).

    Even when a custom theme color is configured for the NDE view (e.g., orange), several RA interface elements still appear in the default blue color, such as:
    - the AI stars icon
    - the "Start a new topic" button
    - navigation arrows in the RA interface.

    According to Clarivate support, this behavior is expected because the RA interface is controlled by CDI rather than Alma customizations.

    Expected behavior: The selected NDE UI color theme should also apply to the Primo Research… more

    •  

    39 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    3 comments  ·  User Interface  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Improving Pick Up Location Logic in Primo NDE

    Purpose:

    To reduce incorrect deliveries, avoid patron frustration, and create a smoother, more intuitive request workflow by improving how pick up locations are ordered and saved in Primo NDE.

    ---

    1. Organisation-Level Improvement: Custom Default Sorting of Pick Up Locations

    Current Issue

    In the current setup, the pick up location list is presented alphabetically/historical by default. This can place small or rarely used locations at the top of the list, even when they are not relevant for most patrons.
    This increases the risk of accidental selection and leads to unnecessary delivery errors.

    Proposal:

    Within Primo NDE, the institution should be able to:

    • Define its preferred default pick up location
    • Specify the initial sort order for the full location list
    • Override alphabetical/historical sorting where it does not align with operational needs

    Goal:

    Ensure that the institution's most relevant and commonly used pick up location appears first, thereby reducing mistakes and improving the patron experience.

    ---

    1. Patron-Level Improvement: Personal Preferred Pick Up Location

    Current Issue

    Patrons currently cannot save a personal, preferred pick up location in their account settings. This forces them to select a pick up location repeatedly - increasing the chances of choosing the wrong one.

    Proposal

    As part of Primo NDE, patrons should be able to:
    • Select and save a personal favourite pick up location when logged in
    • Have this preference automatically preselected for future requests
    • Change their preferred location at any time

    Goal

    Provide a personalised and efficient workflow that supports patron needs and reduces errors caused by repeated manual selection.

    ---

    Next Step

    We request approval to include these two improvements in our Primo NDE configuration agenda. Together, they will enhance usability, reduce incorrect deliveries, and strengthen overall patron satisfaction.

    Final Note:

    This proposal aligns closely with an existing community request on the Ex Libris Ideas Exchange:
    “Define preferred pickup location in Personal Details”
    https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/44908411

    This demonstrates that many institutions experience the same challenge, and that we are not alone in requesting these improvements and indicates broader interest and shared benefits, and suggests that our needs are well understood in the community

    Purpose:

    To reduce incorrect deliveries, avoid patron frustration, and create a smoother, more intuitive request workflow by improving how pick up locations are ordered and saved in Primo NDE.

    ---

    1. Organisation-Level Improvement: Custom Default Sorting of Pick Up Locations

    Current Issue

    In the current setup, the pick up location list is presented alphabetically/historical by default. This can place small or rarely used locations at the top of the list, even when they are not relevant for most patrons.
    This increases the risk of accidental selection and leads to unnecessary delivery errors.

    Proposal:

    Within Primo NDE, the institution should be able to:

    … more

    83 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Primo VE  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Make MyInstitution configurable: allow excluding specific record sets

    SUMMARY

    Libraries cannot currently exclude specific record sets from the out-of-the-box MyInstitution scope in Primo VE / NDE.

    PROBLEM

    MyInstitution (and derived profiles such as MyInstandCI) is a fixed, all-inclusive scope that cannot be modified.

    This makes it impossible to centrally exclude a specific set of records (e.g. a whole digital collection) across all search profiles and views.

    The recommended workaround is to create custom scopes and search profiles (e.g. “MyInstitution minus X”). However, this:

    • Requires duplicating and maintaining multiple configurations

    • Leads to inconsistent behaviour across tabs and profiles

    • Breaks existing permalinks that rely on the standard search profiles

    This last point is especially critical, as Ex Libris recommends permalinks for stable access and sharing. Replacing out-of-the-box profiles can result in links that no longer resolve correctly or display the intended content.

    PROPOSED SOLUTION

    Allow institutions to exclude specific record sets from MyInstitution, either either by configuration (e.g. based on metadata or collections) or by allowing controlled adjustments to the scope itself.

    For example:

    • Exclude records based on specific fields (e.g. MARC 990)

    • Subtract a defined collection or scope from MyInstitution

    • Apply global filters across all search profiles using MyInstitution

    BENEFIT

    This would enable consistent, scalable control over content visibility without breaking existing links, and remove the need for complex and fragile workarounds.

    SUMMARY

    Libraries cannot currently exclude specific record sets from the out-of-the-box MyInstitution scope in Primo VE / NDE.

    PROBLEM

    MyInstitution (and derived profiles such as MyInstandCI) is a fixed, all-inclusive scope that cannot be modified.

    This makes it impossible to centrally exclude a specific set of records (e.g. a whole digital collection) across all search profiles and views.

    The recommended workaround is to create custom scopes and search profiles (e.g. “MyInstitution minus X”). However, this:

    • Requires duplicating and maintaining multiple configurations

    • Leads to inconsistent behaviour across tabs and profiles

    • Breaks existing permalinks that rely on the standard search… more

    26 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Primo VE  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Allow configuring default view (List vs Thumbnail) in Collection Discovery

    SUMMARY

    The default Thumbnail view does not support effective browsing for text-based collections in Primo NDE.

    Currently, libraries cannot configure the default display mode (Thumbnail view vs. Detailed/List view) for Collection Discovery pages. We request the ability to define List view as the default, or to configure this per view or collection.

    PROBLEM: THUMBNAILS DO NOT SUPPORT TEXT-BASED COLLECTIONS

    Thumbnail view prioritizes visual browsing, but many collections do not contain meaningful or distinctive visual material.

    This applies in particular to:
    - Student theses
    - Scholarly publications
    - Institutional repository content

    Thumbnails are often missing, non-informative (for example showing the first page of a PDF), or highly similar across records.

    As a result, the interface shows very limited metadata, often only the title. Important information for selection and comparison is not visible, such as:
    - Publication year
    - Availability status (open access, embargo, or restricted)
    - Abstract or summary
    - Author information

    This makes browsing inefficient and forces users to open multiple records to find relevant items.

    USER STORIES: METADATA-DRIVEN DISCOVERY

    1. Student (exploratory browsing)
       As a student exploring theses or scholarly publications, I want to quickly scan metadata such as year, topic and availability, so that I can identify useful examples without opening each item.

    2. Academic staff
       As an academic staff member reviewing output, I want to see structured information (year, title, supervisor, completeness) directly in the results list, so that I can efficiently assess coverage and quality.

    3. Researcher
       As a researcher browsing a publication collection, I want to compare items using metadata, so that I can identify relevant materials without relying on visual cues.

    USE CASE: CURRENT VS DESIRED BEHAVIOUR

    A user opens a thesis or publication collection in Primo NDE.

    In the current Thumbnail view:
    - Only titles are clearly visible
    - Thumbnails are absent or not meaningful
    - Key metadata is hidden
    - The user must open multiple records

    In a Detailed/List view:
    - Multiple metadata elements are immediately visible
    - Users can scan and compare efficiently
    - Fewer clicks are required
    - The browsing experience matches the content type

    PROPOSED SOLUTION

    • Allow configuration of the default display mode for Collection Discovery (Thumbnail view or List view)
    • Allow configuration per collection or per view, so institutions can match the view to the content type (e.g. images vs text-based collections)

    This flexibility would significantly improve usability and reduce the need for local customizations.

    SUMMARY

    The default Thumbnail view does not support effective browsing for text-based collections in Primo NDE.

    Currently, libraries cannot configure the default display mode (Thumbnail view vs. Detailed/List view) for Collection Discovery pages. We request the ability to define List view as the default, or to configure this per view or collection.

    PROBLEM: THUMBNAILS DO NOT SUPPORT TEXT-BASED COLLECTIONS

    Thumbnail view prioritizes visual browsing, but many collections do not contain meaningful or distinctive visual material.

    This applies in particular to:
    - Student theses
    - Scholarly publications
    - Institutional repository content

    Thumbnails are often missing, non-informative (for example showing the first… more

    •  

    29 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Primo VE  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Calculate and display physical availability on brief display for CDI records

    For Primo VE/NDE, please calculate and display the physical availability on the brief display for CDI records.

    Currently, in the results page, many records that are print plus online show only their online holdings in the results page for the brief records.

    When a user opens one of these records, only then are the physical holdings calculated and displayed. Then when the user goes back to the results page, the physical holdings are now displayed in the brief record, but only after they have viewed the full record, not before.

    This is an inconsistent user experience which is likely to cause confusion.

    Consistently displaying the physical availability alongside the online availability on the initial results page at the brief record level, instead of only the online availability, would create a more consistent user experience as users review potential relevant records.

    Thanks for considering. Sandra.

    For Primo VE/NDE, please calculate and display the physical availability on the brief display for CDI records.

    Currently, in the results page, many records that are print plus online show only their online holdings in the results page for the brief records.

    When a user opens one of these records, only then are the physical holdings calculated and displayed. Then when the user goes back to the results page, the physical holdings are now displayed in the brief record, but only after they have viewed the full record, not before.

    This is an inconsistent user experience which is likely to… more

    24 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Primo VE  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Increase Brief Item Display Field Limit in Primo NDE (Support item.brief.4+)

    In Primo VE, libraries can configure more than three fields in the Brief Item Display (e.g., item.brief.1–4), which allows key item-level information such as location, call number, availability, and Terms of Use to be shown clearly and separately.

    In Primo NDE, the Brief Item Display is currently limited to only three fields (item.brief.1–3), and the fourth field is not supported. This reduces configurability compared to Primo VE and forces institutions to combine multiple data points into a single field or omit information from the brief view.

    This limitation impacts usability, as important details like Terms of Use or item policy information cannot always be displayed in a clear and structured way. Workarounds such as merging fields or relying on expanded item views reduce readability and flexibility.

    We request that Primo NDE support at least four configurable Brief Item Display fields, to restore parity with Primo VE and better support institutions with richer item metadata needs.

    This enhancement would significantly improve flexibility while maintaining the clean design principles of NDE.

    In Primo VE, libraries can configure more than three fields in the Brief Item Display (e.g., item.brief.1–4), which allows key item-level information such as location, call number, availability, and Terms of Use to be shown clearly and separately.

    In Primo NDE, the Brief Item Display is currently limited to only three fields (item.brief.1–3), and the fourth field is not supported. This reduces configurability compared to Primo VE and forces institutions to combine multiple data points into a single field or omit information from the brief view.

    This limitation impacts usability, as important details like Terms of Use or item policy… more

    26 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    4 comments  ·  Primo VE  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Clickable logo single URL insufficient for multilingual institution

    There is only one field available for association with the clickable library logo in Primo VE. This means that some users in a multilingual institution will always be directed away from their chosen language interface after clicking the logo. Please provide at least one other field that is sensitive to the interface language in which the logo is clicked so that Primo VE may fulfil its promise of multilingualism.

    40 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  User Interface  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Apply Display Logic Rules to CDI direct linking records

    Currently, records that provide full text solely via a CDI link-in-record URL are not subject to Display Logic Rules (see documentation note below). This leads to inconsistent behavior and display compared to other CDI records.

    For example, our article ILL General Electronic Service is configured not to display when there is full-text available on a record. This works as expected for records that have full-text provided via the link resolver, but for CDI direct linking records, the ILL GES displays alongside the full-text link. This confuses our patrons, who think that the presence of the ILL link means the full-text link isn't working.

    We request the capability to apply display logic rules to CDI direct linking (link-in-record) records as we can do for CDI records with link resolver full-text.

    Documentation note, added due to case #06712066: "Display logic rules are only applied when the Alma link resolver provides the links. CDI direct linking records are not generated by the Alma link resolver mechanism; therefore, Display logic rules are not applied for them."
    https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/Primo_VE_(English)/080Configuring_Delivery_Services_for_Primo_VE/Configuring_Discovery_Interface_Display_Logic_for_Primo_VE

    Currently, records that provide full text solely via a CDI link-in-record URL are not subject to Display Logic Rules (see documentation note below). This leads to inconsistent behavior and display compared to other CDI records.

    For example, our article ILL General Electronic Service is configured not to display when there is full-text available on a record. This works as expected for records that have full-text provided via the link resolver, but for CDI direct linking records, the ILL GES displays alongside the full-text link. This confuses our patrons, who think that the presence of the ILL link means the full-text… more

    •  

    •  

    115 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Primo VE  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Allow customisation of BibTex data export

    Currently, the BibTex data export from the full record review is non-customisable, no changes can be made to how the fields display in the exported data. This differs, for example, from other formats such as RIS and EndNote, which do have a mapping table in the configuration.

    The issues we’ve encountered with this are:

    1) Some fields have a custom display that we’d like to show on Primo but not in the exported data – e.g. we include author details in the Title display, but it is incorrect for this to show in the BibTex title field

    2) Where we have custom resource types on Primo, these are not read at all by BibTex and come up as “@unknown”entry types

    The lack of mapping options for this feature is causing significant issues for our users who need to use this referencing platform for their course. At our institution this includes Mathematics, Computer Science and Physics students, with one academic estimating that it could impact circa 650 students for the modules he is responsible for alone.

    Any workarounds for it are limited and would involve fundamental changes to configuration in Primo VE, such as stopping using custom resource types at all.

    It would be massively beneficial if we could define a custom mapping for this export, such as being able to map our own resource types onto the BibTex entry types, or control how each BibTex field is populated using fields in the PNX or Marc.

    Currently, the BibTex data export from the full record review is non-customisable, no changes can be made to how the fields display in the exported data. This differs, for example, from other formats such as RIS and EndNote, which do have a mapping table in the configuration.

    The issues we’ve encountered with this are:

    1) Some fields have a custom display that we’d like to show on Primo but not in the exported data – e.g. we include author details in the Title display, but it is incorrect for this to show in the BibTex title field

    2) Where we… more

    44 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Primo VE  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating