736 results found

1. Rank records within FRBR group by relevancy to search terms (not just highlight one preferred record)

   Description:

   This is a follow-up to a previously "completed" idea: "Relevancy sorting in FRBR version list display should use terms searched" (209 votes). That idea was addressed only for Preferred Record mode, by highlighting a single matching record at the top of the version list. We don't think this fully solves the underlying problem, in either display mode.

   The problem:

   A FRBR group can contain several records that are all relevant to the user's original search terms. For example, multiple translations by the same translator, or several relevant editions.

   In Generic mode, opening the group shows an unranked list of all versions. Relevant matches can be buried many pages deep, with no connection to the original search.

   In Preferred Record mode, the fix implemented only surfaces one matching record. This can make the problem less visible: a user sees one confidently displayed match and has no indication that 2-3 more equally (or slightly less) relevant versions exist inside the group. It looks solved, but the ranking problem is just hidden rather than fixed.

   Grouping records according to FRBR principles in general is good and something we want to keep recommending to our institutions. However, if it negatively affects users’ attempts to reach a known item or semi-known items by placing these unintuitive roadblocks in their way, it is not good enough. In many cases, the user would be better off if the search had never been FRBR’ized.

   The proposed solution:

   Rank/sort the records within the FRBR group itself by relevancy to the original search terms, in both Generic and Preferred Record display modes. That way, the user will immediately spot the relevant results after opening the FRBR group but will still enjoy the benefits of a less cluttered initial results list.

   Example:

   Searching "Iliad Richmond Lattimore" returns a FRBR group for Homer's Iliad. Opening the group should surface Richmond Lattimore's translations at or near the top based on its relevance to the search the user made, not require paging through many unrelated editions/translations to find them.

   We hope that you will vote for this suggestion! Feel free to add other examples in the comments below.

   -The BIBSYS-consortia

   Description:

   This is a follow-up to a previously "completed" idea: "Relevancy sorting in FRBR version list display should use terms searched" (209 votes). That idea was addressed only for Preferred Record mode, by highlighting a single matching record at the top of the version list. We don't think this fully solves the underlying problem, in either display mode.

   The problem:

   A FRBR group can contain several records that are all relevant to the user's original search terms. For example, multiple translations by the same translator, or several relevant editions.

   In Generic mode, opening the group shows an unranked list of… more

   176 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

2. Improve Database material type assignment in a Network Zone Consortia

   Problem description

   In a Network Zone consortium, bibliographic records are shared across all member institutions. Currently, the "Database" material type in Primo VE is assigned to a bibliographic record whenever that record is linked as the descriptive/display record for any Electronic Collection with a populated Level URL. This includes Local Electronic Collections created by a single member institution in their own Institution Zone.

   Because the underlying bibliographic record is shared in the NZ, this single institution's local configuration choice changes the material type of the record for every institution in the consortium, even though only one institution actually intended the title to function as a database entry. This creates a situation where a shared title (e.g. a journal) can unexpectedly display under "databases" instead of its correct material type in another institution's discovery layer, with no clear explanation available to that institution.

   Impact

   Member institutions have no visibility or diagnostic tool to determine why a shared title unexpectedly displays with the wrong material type. A single institution's local Electronic Collection setup can silently override discovery behavior for the entire consortium, with no warning, log, or notification to affected institutions.

   Troubleshooting is currently difficult. Only the consortium's network administrators have a way to identify the source, but it requires checking every library that has the record in their IZ.

   Suggested improvement

   We would like Clarivate to investigate ways of making this behavior more transparent and manageable in an NZ consortium setting. One option would be through better visibility into cross-institution record usage, or some form of notification when a shared record's material type is affected by another institution's configuration. An even better solution would be to change the underlying approach to how the "Database" resource type is determined for shared NZ records in a way that would let each IZ control the behaviour in their own IZ. Such a solution would increase the customizability of the database list for each individual IZ without risking resource type contamination across the consortia.

   Problem description

   In a Network Zone consortium, bibliographic records are shared across all member institutions. Currently, the "Database" material type in Primo VE is assigned to a bibliographic record whenever that record is linked as the descriptive/display record for any Electronic Collection with a populated Level URL. This includes Local Electronic Collections created by a single member institution in their own Institution Zone.

   Because the underlying bibliographic record is shared in the NZ, this single institution's local configuration choice changes the material type of the record for every institution in the consortium, even though only one institution actually intended the… more

   147 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  ·  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

3. 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

   • 

   358 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…)
   9 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

4. 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

   311 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

5. 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

   204 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

6. Primo VE - Linked open data person entity - option to display additional authority record fields

   We contribute to the Library of Congress Names Authority and add associated group fields (MARC 373) with iwi affiliations for Māori authors and creators. Currently this field is not displayed in Person entity cards. Could this and other authority data be made configurable for display?

   60 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

7. 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/

   218 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

8. 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

   41 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

9. Display the resource types filter bar in Primo NDE advanced search results

   In the pre-NDE UI of Primo VE, the resource types filter bar was displayed inside the basic search bar at the top of the page, just under the search term input field. It functioned primarily as a pre-search filter. As such, it made logical sense that one wouldn't see the filter bar after conducting an advanced search.

   But in NDE, the filter bar appears just above the search results. It only shows up once the results have loaded, so it's only possible to use it as a post-search filter. Despite this difference of use in NDE, the resource types filter bar only displays above search results when a basic search is conducted. It's absent when an advanced search has been conducted. This is confusing our users because while they expect a different search form for advanced search, they don't expect the results display to lack a familiar feature.

   As I understand it, the resource types filter bar did at one time display in NDE, but it was removed because it was causing problems. I don't know the nature of those problems, but if they could be resolved and the filter bar returned to the advanced search results display, it would improve the user experience greatly.

   In the pre-NDE UI of Primo VE, the resource types filter bar was displayed inside the basic search bar at the top of the page, just under the search term input field. It functioned primarily as a pre-search filter. As such, it made logical sense that one wouldn't see the filter bar after conducting an advanced search.

   But in NDE, the filter bar appears just above the search results. It only shows up once the results have loaded, so it's only possible to use it as a post-search filter. Despite this difference of use in NDE, the resource types filter… more

   27 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

10. 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".

    125 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…)
    8 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

11. 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

    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…)
    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

12. 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

13. 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

    125 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

14. 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

    •  

    37 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. NDE landing page labels

    With the new Landing Page configuration, it is now possible to customize the NDE starting page.

    Under Discovery Configuration > View Configuration > Landing Page > Links, it is possible to configure the labels for the Links section. However, other Landing Page labels are managed at IZ level under Discovery Configuration > Labels > Landing Page Labels.

    For consortia or institutions with multiple views, this creates a limitation: labels that are not part of the Links section cannot be customized per local view in the configuration menu, but only by creating view level labels in the code table. As a result, the usability of this solution is poor and the new Landing Page configuration is of limited use for our environment.

    Please make all Landing Page labels configurable at View level directly in the dedicated configuration menu.

    With the new Landing Page configuration, it is now possible to customize the NDE starting page.

    Under Discovery Configuration > View Configuration > Landing Page > Links, it is possible to configure the labels for the Links section. However, other Landing Page labels are managed at IZ level under Discovery Configuration > Labels > Landing Page Labels.

    For consortia or institutions with multiple views, this creates a limitation: labels that are not part of the Links section cannot be customized per local view in the configuration menu, but only by creating view level labels in the code table. As a… more

    21 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  ·  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

16. 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

    •  

    41 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

17. 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

    120 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

18. 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

    32 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

19. Integration of Institutional AI Research Tools with Primo Research Assistant

    Primo Research Assistant should support integration with external AI research platforms, such as LeapSpace, Scopus AI, Web of Science Research Assistant, Elicit, and other emerging research tools. This would enable researchers to access insights and capabilities from multiple AI-powered services through a single Primo interface, eliminating the need to switch between platforms.

    Currently, researchers often need to move between multiple AI platforms to access different features and content sources. Integrating these tools with Primo Research Assistant would create a more seamless research experience and position Primo as the central hub for AI-assisted discovery.
    Benefits of this enhancement include:
    • A single point of access to AI-assisted research services.
    • Reduced need for users to switch between multiple platforms.
    • Improved researcher productivity and workflow efficiency.
    • Better utilisation of institutionally licensed AI tools.
    • More comprehensive responses by drawing on multiple trusted scholarly sources.
    • Greater flexibility for institutions to integrate current and future AI research platforms.

    This enhancement would help libraries maximise the value of their AI investments while providing researchers with a more unified and efficient research experience.

    Primo Research Assistant should support integration with external AI research platforms, such as LeapSpace, Scopus AI, Web of Science Research Assistant, Elicit, and other emerging research tools. This would enable researchers to access insights and capabilities from multiple AI-powered services through a single Primo interface, eliminating the need to switch between platforms.

    Currently, researchers often need to move between multiple AI platforms to access different features and content sources. Integrating these tools with Primo Research Assistant would create a more seamless research experience and position Primo as the central hub for AI-assisted discovery.
    Benefits of this enhancement include:
    • A… more

    9 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…)
    10 comments  ·  Integration with other systems  ·  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. NDE My Account Loans: Option to show more than 10

    In the previous UI for VE, users were able to load more of their loans when viewing their account. This list could then exported. In the NDE users are limited to viewing 10 loans at a time, thus they can only export 10 at a time. Either the loans list should be updated to allow the user to increase the number of loans viewable at a time (up to 50, similar to search results), or have an option to generate a list of loans either in the browser or as an export.

    27 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