358 results found

1. Links in View It should be anchor links rather than buttons in NDE

   In the legacy version of Primo VE, links to remote resources in View It are anchors, allowing the user to see the destination in the browser and to copy it using a right-click. This ends up being critical for troubleshooting. In NDE instead there are only buttons as resource links, so that we need to work much harder to get the URL (e.g. using the "Display CTO" method). Given that these page elements are actually navigational--they are links to remote resources--it would be far more appropriate for them to be rendered as regular anchors/links rather than buttons (regardless of styling). Please enhance NDE so that View It links are rendered as anchors rather than buttons.

   In the legacy version of Primo VE, links to remote resources in View It are anchors, allowing the user to see the destination in the browser and to copy it using a right-click. This ends up being critical for troubleshooting. In NDE instead there are only buttons as resource links, so that we need to work much harder to get the URL (e.g. using the "Display CTO" method). Given that these page elements are actually navigational--they are links to remote resources--it would be far more appropriate for them to be rendered as regular anchors/links rather than buttons (regardless of styling).… 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  ·  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. 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

   •  

   •  

   2 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

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

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

5. Granular Control for Alma Viewer and Digital Versions Tab in Primo NDE

   Description:

   In Primo NDE, the rule “Hide service: Representation Delivery Service” affects both alma-viewer-content and the Digital Versions tab (nde.brief.results.tabs.digitalVersions). In contrast, Primo VE allows institutions to independently control visibility of the Alma Viewer and the Digital Versions tab.

   This enhancement request seeks to restore this level of granular control in Primo NDE. Specifically, institutions should be able to:

   Hide the Alma Viewer for certain representations (e.g., auxiliary or restricted content)

   Still display the Digital Versions tab for those same representations

   This would provide the flexibility needed for managing multiple representations of a record while ensuring users can discover digital content, even when the viewer is suppressed.

   Use Case:

   • Hide viewer for auxiliary representations

   • Keep the Digital Versions tab visible for those representations

   Benefit:

   Restoring this functionality would align Primo NDE with Primo VE, improving user experience and enabling finer control over digital content visibility.

   Description:

   In Primo NDE, the rule “Hide service: Representation Delivery Service” affects both alma-viewer-content and the Digital Versions tab (nde.brief.results.tabs.digitalVersions). In contrast, Primo VE allows institutions to independently control visibility of the Alma Viewer and the Digital Versions tab.

   This enhancement request seeks to restore this level of granular control in Primo NDE. Specifically, institutions should be able to:

   Hide the Alma Viewer for certain representations (e.g., auxiliary or restricted content)

   Still display the Digital Versions tab for those same representations

   This would provide the flexibility needed for managing multiple representations of a record while ensuring users can discover digital… 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  ·  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

6. Improve Browse with 505 $$t subfield

   Ex Libris technicians report that currently only the first occurrence of 505 $t is included in the Title index. As a result, if you Browse by a title listed further within the 505, the results don't supply a matching record. All $$t subfields in the 505 (and any other fields recording titles) should be included in the Title index to avoid this issue.

   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. Display campus in Primo VE for unsuppressed e-Collections and databases

   In the consortial environment, we would like to take advantage of the new functionality of central NZ-activation (network zone) of e-collections working with IMGrs (inventory management groups). We have some institutions (not all IZs) which would like to work with IMGrs, some not, those who do, some do use campuses others do not.

   We would like to see in Primo VE the distinction per campus also for databases and for non-suppressed e-collections (if used), as it works for portfolios so to better guide the end-user which collection would be the one to use.

   If an IZ uses IMGr in Alma which are applied to campuses/library to distribute access for their e-collections, or if e-collections are centrally activated in the NZ, with IMGr, i.e. if a database or e-collection with portfolios in a consortial environment are centrally activated, and the e-collections are then visible in the Primo VE of the IZ, we would like to have an option which allows to display separately per campus the unsuppressed e-collections and databases in Primo VE. This should also be possible in the future NDE.

   Display of portfolios per campus must stay as today, i.e. display per campus, and be valid for portfolios of suppressed or unsuppressed e-collections.
   Please note that several Idea Exchanges on the topic was already brought up, but many of these Idea Exchanges were not retained due to lack of votes.

   This Idea Exchange is addressed in particular to consortial architectures who work with the new functionality to centrally activate e-collections and apply IMGrs to these in the NZ. Yet the feature of campus display for unsuppressed e-collections should be available also for e-collections which are not IZ activated.

   An idea for expected display and relevant status quo can be found in the attached file.

   In the consortial environment, we would like to take advantage of the new functionality of central NZ-activation (network zone) of e-collections working with IMGrs (inventory management groups). We have some institutions (not all IZs) which would like to work with IMGrs, some not, those who do, some do use campuses others do not.

   We would like to see in Primo VE the distinction per campus also for databases and for non-suppressed e-collections (if used), as it works for portfolios so to better guide the end-user which collection would be the one to use.

   If an IZ uses IMGr in Alma… more

   • 

   29 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

8. Primo NDE - Option to Display Cover Thumbnail Alongside Embedded Digital Viewer

   Problem Summary

   Currently, when an embedded digital viewer is present on a record, the system intentionally hides the cover thumbnail. Network calls confirm that the thumbnail is no longer requested once the viewer loads. While this is expected behavior, it can create a less optimal user experience in situations where the viewer does not display the actual cover or full document—for example, when it opens on a table of contents or another non-cover view. In these cases, users lose quick visual context provided by the cover image.

   Description:
   Requesting the addition of a configurable option that allows the cover thumbnail to remain visible even when the embedded digital viewer is loaded. This would be particularly helpful when the viewer displays content other than the cover (e.g., table of contents, metadata views, or alternate document sections). Providing the thumbnail alongside the viewer would enhance user context, improve navigation clarity, and offer a more consistent visual experience.

   Proposed Behavior:

   • Add a setting or toggle to optionally retain the cover thumbnail when the digital viewer loads.

   • Ensure the thumbnail can appear in a consistent location

   • Maintain current behavior as the default to preserve backward compatibility.

   Rationale / Benefits:

   • Improves user context when viewer content differs from the cover.

   • Enhances UX without disrupting existing workflows.

   • Offers institutions more flexibility in how records are presented.

   Thanks

   Problem Summary

   Currently, when an embedded digital viewer is present on a record, the system intentionally hides the cover thumbnail. Network calls confirm that the thumbnail is no longer requested once the viewer loads. While this is expected behavior, it can create a less optimal user experience in situations where the viewer does not display the actual cover or full document—for example, when it opens on a table of contents or another non-cover view. In these cases, users lose quick visual context provided by the cover image.

   Description:
   Requesting the addition of a configurable option that allows the cover thumbnail… more

   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…)
   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. My Library Card: date of the last renewal

   We suggest that the "Date of the last Renewal" field should only update when a successful renewal happens, rather than when the courtesy letter is sent.

   It happens in local loan and in Rapido, and it is confusing for patrons. We would like this workflow was adjusted.

   42 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

10. Allowing to opt out of loading OAI Repository records into Discovery Network

    Allowing to opt out of loading OAI Repository records into Discovery Network

    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

11. Use all occurrences of a bibliographic field within GES Bib Field Enrichment

    Institutions can define which fields are extracted from the bibliographic record metadata to be used in General Electronic Services by adding fields to the GES Bib Fields Enrichment mapping table. However, if the bibliographic field occurs multiple times in the record, only the first occurrence of the field is used. This means that the GES is not calculated for any subsequent occurrences of the field. For example, if I want a GES to be displayed based on a particular value in a 590 local note, the GES will only display if that value occurs in the first of what may be many 590 local note fields. I request that all occurrences of the fields defined in the GES Bib fields enrichment mapping table be used in GES calculation for display in Primo records.

    Institutions can define which fields are extracted from the bibliographic record metadata to be used in General Electronic Services by adding fields to the GES Bib Fields Enrichment mapping table. However, if the bibliographic field occurs multiple times in the record, only the first occurrence of the field is used. This means that the GES is not calculated for any subsequent occurrences of the field. For example, if I want a GES to be displayed based on a particular value in a 590 local note, the GES will only display if that value occurs in the first of what may… 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  ·  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

12. Add Due Date to Real Time Availability Status in Brief Records

    We would like to be able to see the status messages to include Due Dates, where applicable.
    Example: add date to Not available - Loan message, something along the lines of Not available - Checked out until {date}.

    8 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

13. Put search/feedback links in logical order on mobile menu - NDE

    In NDE on small screens, the Advanced Search, Feedback (Report a problem) and Ask Anything (natural language search) links appear in the menu in that order - see screenshot attached.

    At minimum, the two search options should be adjacent, and in the order they appear on full screen. The feedback/report a problem should not be in the middle of them, as it is a completely different type of function.

    Some institutions may even wish to relocate the feedback option to the bottom of the top menu links.

    The original case response was to log here on the idea exchange, as there is no plan to address this.

    In NDE on small screens, the Advanced Search, Feedback (Report a problem) and Ask Anything (natural language search) links appear in the menu in that order - see screenshot attached.

    At minimum, the two search options should be adjacent, and in the order they appear on full screen. The feedback/report a problem should not be in the middle of them, as it is a completely different type of function.

    Some institutions may even wish to relocate the feedback option to the bottom of the top menu links.

    The original case response was to log here on the idea exchange, as… more

    •  

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

14. Copy text from digital viewer

    When reading documents in the digital viewer, it would be nice to have the ability to copy text directly from the page. You can do this if you download the document. I was attempting to do this with a larger file that mentioned other reports I wanted copy the name of a report to view/search for in the catalogue; however, the digital viewer does not allow users to select text from the document.

    13 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

15. Resource Recommender by user group or campus

    Resource Recommender in Primo VE can only show suggestions based on search tags or “Display Always.”
    There’s no way to show recommendations based on who the user is — for example, their user group, campus, or department.
    This means libraries can’t personalize results - such as:
    Business students see business databases

    This would make the discovery experience more relevant and user-friendly.

    7 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

16. Ability to boost Ranking of Search Results in Primo VE based on accessibility

    Some of our consortium libraries would like the ability to boost the ranking of books that readers can request from libraries.
    Currently, the Ranking Configuration page enables you to configure various aspects of the ranking algorithm based on Field Boosting, Date Boosting, Resource type Boosting, Institution Boosting, but not on accessibility.

    82 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. Allow users to customize PNX addata subfields

    Currently, the normalization rules for creating addata subfields are not available to users. As a result, redundant information is included in subfields intended for authors, creators or titles and as result the citations are inaccurate.

    79 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

18. Primo Research Assistant Recibir nuevos datos estadísticos

    Una de las recientes adquisiciones dentro del sistema ALMA tiene que ver con la integración del asistente de investigación, una inteligencia artificial que facilita la búsqueda de información por medio de consultas que el usuario hace, en la que la respuesta se sujeta con la documentación existente en el acervo electrónico del sistema bibliotecario.

    Al ser tan útil esta herramienta, en nuestra institución nos importa direccionar a los usuarios la información que más les puede resultar útil, y los resultados que ofrece el asistente de investigación pueden beneficiar a esta meta.

    Hemos explorado los reportes que Primo puede generar, en particular, “Primo Research Asistant”, sin embargo, esta información ofrece datos sobre las selecciones del usuario, si acceden o no al archivo.

    Nos interesa saber si podemos extraer otros datos dentro de la plataforma, como lo son:
    • Consultas dentro del asistente de investigación
    • Temática o documento que se muestra en los primeros resultados que muestra el asistente
    • Número de veces que el usuario hace copia de la información que el asistente de investigación genera
    • Número veces que se usa el asistente de investigación en un periodo específico de fechas
    • Datos del usuario que hace uso del asistente de investigación
    • Porcentaje de recursos institucionales y externos que muestra el asistente de investigación en la respuesta de un estudiante

    Una de las recientes adquisiciones dentro del sistema ALMA tiene que ver con la integración del asistente de investigación, una inteligencia artificial que facilita la búsqueda de información por medio de consultas que el usuario hace, en la que la respuesta se sujeta con la documentación existente en el acervo electrónico del sistema bibliotecario.

    Al ser tan útil esta herramienta, en nuestra institución nos importa direccionar a los usuarios la información que más les puede resultar útil, y los resultados que ofrece el asistente de investigación pueden beneficiar a esta meta.

    Hemos explorado los reportes que Primo puede generar, en… 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  ·  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

19. Ability to Configure Multiple Journal Searches

    Currently, Primo VE supports only one Journal Search configuration for an institution. While this works well for many institutions, some institutions oversee multiple libraries or campuses with distinct journal holdings (e.g., different licensing agreements, consortia memberships, or campus-specific subscriptions).

    We would like to request the ability to configure and offer multiple, separate Journal Searches within Primo VE.

    Each Journal Search should:

    • Be scoped independently (e.g., by IZ, NZ, or a specific library/campus)

    • Have customizable display labels and help text to clearly indicate which journal collection the search covers

    • Support direct linking to each Journal Search from library platforms

    Use Case:
    At multi-campus institutions, users often need to know which journals are available specifically through their home campus. Currently, this is difficult to implement since only one centralized Journal Search can be offered.

    Multiple Journal Searches would:

    • Reduce user confusion when different campuses/libraries have different subscriptions

    • Support institutions that are part of consortia but also maintain unique, local journal collections

    • Improve the patron experience by allowing clear pathways to the correct set of journals

    Impact:

    We believe this enhancement would significantly improve discoverability, align search results with basic Primo searches, reduce access confusion, and allow libraries to better serve diverse user groups with distinct e-resource entitlements.

    Currently, Primo VE supports only one Journal Search configuration for an institution. While this works well for many institutions, some institutions oversee multiple libraries or campuses with distinct journal holdings (e.g., different licensing agreements, consortia memberships, or campus-specific subscriptions).

    We would like to request the ability to configure and offer multiple, separate Journal Searches within Primo VE.

    Each Journal Search should:

    • Be scoped independently (e.g., by IZ, NZ, or a specific library/campus)

    • Have customizable display labels and help text to clearly indicate which journal collection the search covers

    • Support direct linking to each Journal Search from library platforms

    Use Case: … more

    31 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

20. Allow Print option in Primo VE to print Quick Access representation along with metadata

    When using the "Print" command in a Primo full view record, the print screen shows a record's metadata. However, if the record has a digital representation in the "Quick Access" section (as might be the case in a record managed by Alma-D), the image is not included in the print page. Having the option to include the representation would be helpful in cases where a printed image is needed alongside its metadata.

    2 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