662 results found

1. Allow icons display in database search

   Allow display of images in database search results view for showing databases icons.
   It's the only menu in Primo where it's not possible. Makes no sense !

   1 vote

   Vote 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  ·  Edit…  ·  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. Support turning on/off individual CDI document attributes

   Currently, CDI document attributes can only be turned on/off at the view label, and if there is a particular attribute that a library does not want to display, they cannot turn it off as a configuration.

   For example, a library may want to turn off the "Primary source" label because it causes confusion when patrons are searching both CDI and local records together.

   Please add the ability to enable or disable individual CDI document attributes for display in Primo.

   4 votes

   Vote 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. Configuration for cubicle or space reservations

   Currently, the resource and space reservation functionality in Primo VE is very limited. It is necessary to enable configurations that make the reservation process faster and simpler. Among the required improvements are:

   • Adjusting the available reservation times according to the Library's opening hours, avoiding displaying time slots that are not relevant.
   • Allowing the Library team to configure only certain days, instead of automatically enabling all days.
   • Unifying the calendar system so that a single calendar is used to select the reservation date, instead of one for the start and another for the end.

   1 vote

   Vote 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  ·  Edit…  ·  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. Additional Format options for resource sharing request form

   The resource sharing request form currently only allows selections of "Physical" and "Digital", but patrons might have both preferences and flexibility on the format of their requests. Additional options like "Physical Only, Digital Only, Physical preferred but digital accepted, or Digital preferred but physical accepted" would be helpful for both patrons and ILL staff.

   3 votes

   Vote 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. Purchase requests just in top menu (not in Get it section)

   We would like to suggest an option to offer the blank Purchase Request form in the Top Menu, while preventing the "Purchase Request" link from appearing in the "Get It" section of the record view.

   We want to avoid patrons requesting materials that we already hold or that can be obtained through resource sharing (Rapido).

   Currently, there is no configuration to separate these two access points. We tried using GES (General Electronic Services) logic, but it does not work for this specific purpose in Primo VE. The only workaround we found is hiding the link in the record view using CSS, which is not a robust solution.

   We suggest adding a native configuration to display the link only in the Main Menu.

   We would like to suggest an option to offer the blank Purchase Request form in the Top Menu, while preventing the "Purchase Request" link from appearing in the "Get It" section of the record view.

   We want to avoid patrons requesting materials that we already hold or that can be obtained through resource sharing (Rapido).

   Currently, there is no configuration to separate these two access points. We tried using GES (General Electronic Services) logic, but it does not work for this specific purpose in Primo VE. The only workaround we found is hiding the link in the record view using… more

   22 votes

   Vote 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

6. “Show more items”

   Trying to restart this effort-

   Add “Show All Items”

   Give patrons an option to “Show All Items in a record”. The option “show more items” is not user friendly when searching through long runs
   of serials.

   4 votes

   Vote 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

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

   • 

   10 votes

   Vote 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 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

8. Enable Pre-filter below the search term input field in NDE UI

   Background:
   In the previous Primo VE UI, users were able to apply Pre-filters directly below the search term input field. This functionality allowed for more precise and efficient searching without requiring access to Advanced Search.

   Proposal:
   We recommend implementing the same feature in the NDE UI, enabling users to select Pre-filters directly beneath the search term input field.

   Benefits:
   Users frequently use the "contains exact phrase" option or use the “begin with” option. (Especially for non-English speaking users like us.)
   Providing Pre-filter functionality in the brief search interface will allow users to execute advanced searches quickly and intuitively, without navigating to Advanced Search.
   This enhancement improves usability and aligns with user expectations based on previous UI behavior.

   Background:
   In the previous Primo VE UI, users were able to apply Pre-filters directly below the search term input field. This functionality allowed for more precise and efficient searching without requiring access to Advanced Search.

   Proposal:
   We recommend implementing the same feature in the NDE UI, enabling users to select Pre-filters directly beneath the search term input field.

   Benefits:
   Users frequently use the "contains exact phrase" option or use the “begin with” option. (Especially for non-English speaking users like us.)
   Providing Pre-filter functionality in the brief search interface will allow users to execute advanced searches quickly and intuitively, without navigating… more

   • 

   9 votes

   Vote 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

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

   218 votes

   Vote 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

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

    77 votes

    Vote 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

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

    26 votes

    Vote 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. Add autocomplete to embedded searchbox

    Please add autocomplete to the embedded searchbox API for a consistent user experience.

    1 vote

    Vote 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  ·  Edit…  ·  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. Display tag for Open Educational Resources for CZ and IZ records in Primo

    Open Educational Resources tags in CDI records are clearly displayed in Primo VE (e.g. Pressbooks titles). I would like to see this tag extended to include CZ and IZ records for open educational resources in a similar way to how we make the Open Access icon display in Primo.

    24 votes

    Vote 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. Certificate of No Outstanding Debts/ Certidão Negativa de Débitos

    Create a "Certificate of No Debts" function within Primo, which will allow users to issue a document stating that they have no outstanding debts with the Library (loans, unpaid fines, unreturned books, item replacements in progress, and others). If there are any outstanding issues, the document will specify what those issues are, and the user will be instructed to contact the library.
    This is a very useful feature. With translate to POrtuguese, please.

    •  

    •  

    6 votes

    Vote 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

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

    162 votes

    Vote 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

16. Configure page metadata (browser tab title) across key pages independently from the main menu labels

    In Primo NDE, the browser tab title (the HTML <title> element) for many pages uses the same label as the top menu, e.g., ILL request forms, Citation Linker, Collection Discovery, Purchase request form.

    Screenshot with label codes toggled on to demonstrate the same label used for different functions

    This means that the title in the tab cannot be independently customised to act consistently with other areas of Primo (search and my library account where separate labels can be managed). This creates issues:

    Usability:

    • Users with many collection discovery tabs open cannot distinguish which collection is in each tab. Users sharing a link to a featured collection (where the tab title is automatically used for the link name. e.g. pasting a URL into a Word document, email, or Teams) must edit the link to match the collection’s name or risk confusing the recipient.

    Confusion as to why the tab titles appear differently in search and my library pages compared to these other pages.

    • Branding & Clarity: Institutions cannot reflect their institutional names in the tab titles on these pages, which confuses users and reduces trust.

    When links are shared to different collections, the link name is always identical and cannot feature the institution’s name. e.g. Featured collections vs Aboriginal and Torres Strait Islander Collection | Bond University
    Screenshot showing that the collection name could be used in the tab title.

    When a link to the blank ILL form or purchase request form is shared via email, it appears with whatever is in the top menu, rather than Purchase request | Institution Name unless the link is edited before sending. E.g. Purchase request vs Purchase request | University of XYZ.
    For users affiliated with multiple institutions, this can also be confusing, as it is unclear which institution the link pertains to.

    Affected pages

    The <title> element uses the same label as the main menu option for:

    • Collection Discovery (Highest priority for SEO and collection promotion) – it does append the query for search within collections, but being able to include the collection name and institution would be better
    • Fetch Items (Citation Linker)
    • ILL request
    • Purchase request
    • Newspapers search
    • Journal search
    • Browse search
    • Database search
    • Tags
    • Research Assistant
    • Authority Search

    June 2025 release notes included:

    “NDE UI - Enhanced Customization and Branding Options
    Support Existing Header Labels – The NDE UI now supports the codes used to customize and translate the page titles in the browser.”
    While this was an improvement, the flexibility to insert institutional names is not supported for the pages listed above. If the institution name is hard-coded into the relevant label, it also appears in the menu.

    Related CERV enhancement request: https://enhancements.exlibrisusers.org/ideas/PENH-I-28463

    In Primo NDE, the browser tab title (the HTML <title> element) for many pages uses the same label as the top menu, e.g., ILL request forms, Citation Linker, Collection Discovery, Purchase request form.

    Screenshot with label codes toggled on to demonstrate the same label used for different functions

    This means that the title in the tab cannot be independently customised to act consistently with other areas of Primo (search and my library account where separate labels can be managed). This creates issues:

    Usability:

    • Users with many collection discovery tabs open cannot distinguish which collection is in each tab. Users sharing… more

    •  

    •  

    3 votes

    Vote 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. Continue as Guest link on the authentication page

    To encourage more users to sign in to Primo, we would like to provide more links on our public website, in emails, and through signage that direct users to specific pages in Primo, such as the AI Research Assistant or My Library Account. These require authentication first. While this works for our current staff and students, such links may also be clicked by people who do not have an account.

    In this scenario, they are stuck on the authentication page with no option to opt out and get to the landing page. There is no top menu for them to choose from.

    An optional/configurable link that offers them a path to continue as a guest user and takes them to the landing page would be helpful.

    While this might also affect the sign-in window, it would not hurt to be there. It differs from the Cancel link, which simply closes the authentication pop-up – it does not take them to the landing page.

    In cases where we direct the user to a specific page via authentication, the same type of cancel link would not work. This enhancement would instead take them to the landing page, as they are not authorised to use these special areas of Primo.

    Example links:

    //DOMAIN/nde/login?vid={VID code}&toState=account/overview&toParams={"vid":"{VID code}","lang":"en"}

    //DOMAIN/nde/login?vid={VID code}&toState=researchAssistant&toParams={"vid":"{VID code}","lang":"en"}

    While these examples and screenshots are from NDE, this is something that we had previously wanted to do in Primo VE too.

    Related CERV enhancement request: https://enhancements.exlibrisusers.org/ideas/PENH-I-28464

    To encourage more users to sign in to Primo, we would like to provide more links on our public website, in emails, and through signage that direct users to specific pages in Primo, such as the AI Research Assistant or My Library Account. These require authentication first. While this works for our current staff and students, such links may also be clicked by people who do not have an account.

    In this scenario, they are stuck on the authentication page with no option to opt out and get to the landing page. There is no top menu for them to… more

    •  

    1 vote

    Vote 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

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.

    34 votes

    Vote 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. Display Number of Renewals on Patron Library Card in Primo VE

    Currently, Primo VE does not display the number of renewals for a patron’s loans on the patron’s library card. We propose an enhancement to allow the number of renewals (used and/or remaining) to be displayed in Primo VE for patron loans. This should appear on the patron’s library card.
    Providing this information directly in Primo VE would improve transparency for patrons.

    4 votes

    Vote 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

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

    117 votes

    Vote 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