706 results found

1. Make MyInstitution configurable: allow excluding specific record sets

   SUMMARY

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

   PROBLEM

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

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

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

   • Requires duplicating and maintaining multiple configurations

   • Leads to inconsistent behaviour across tabs and profiles

   • Breaks existing permalinks that rely on the standard search profiles

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

   PROPOSED SOLUTION

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

   For example:

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

   • Subtract a defined collection or scope from MyInstitution

   • Apply global filters across all search profiles using MyInstitution

   BENEFIT

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

   SUMMARY

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

   PROBLEM

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

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

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

   • Requires duplicating and maintaining multiple configurations

   • Leads to inconsistent behaviour across tabs and profiles

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

   26 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

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

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

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

   SUMMARY

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

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

   PROBLEM: THUMBNAILS DO NOT SUPPORT TEXT-BASED COLLECTIONS

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

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

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

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

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

   USER STORIES: METADATA-DRIVEN DISCOVERY

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

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

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

   USE CASE: CURRENT VS DESIRED BEHAVIOUR

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

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

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

   PROPOSED SOLUTION

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

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

   SUMMARY

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

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

   PROBLEM: THUMBNAILS DO NOT SUPPORT TEXT-BASED COLLECTIONS

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

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

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

   •  

   29 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

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

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Provide confirmation when item has been added to a reading list

   In both Primo VE and Primo NDE, no confirmation is given to the user after adding a title to a reading list. The Add to Reading List box simply closes with no indication about what has occurred.

   Recommend adding a status message so that users are aware the item has been successfully added, avoiding uncertainty and potential repeated actions.

   3 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  ·  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. Option to have more than 5 results from Primo Research Assistant query

   In the current release of Primo Research Assistant, it provides the 5 most relevant results with an instant overview. Sometimes, a query returns more than five highly relevant results. Hopefully, the Research Assistant will offer users the option to view more than 5 results in the future.

   1 vote

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

5. Further Customization of "Service Temporarily Unavailable" Message

   In Alma, a "Service Temporarily Unavailable" message can be configured for electronic collections that will display in Primo. While the message itself can be customized, it's not very eye catching for users in Primo.

   We would love for this to be able to be customized in regards to colour, font size, highlighting, etc. Or display on the main search page rather than needing to click on the title to see it.

   3 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  ·  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. Re-design NDE Get it section

   Our suggestion (see attached file and image) is to re-design the get it section for the NDE, so that it become more compact and reduce the number of clicks needed to display all information.

   In this idea it remains fundamental that libraries can configure which information display and in which order, that is optimized also for mobiles, that it works well with journals and that "filter" by number or year option keep on working
   The status of the items could also be indicated using colors: for example, Item in Place in green, Out of Library in grey, ...

   Note: we did add also "loan" and "digitization" options at item level in this mockup, but we strongly believe that these should moved in the "Request" section.

   Our suggestion (see attached file and image) is to re-design the get it section for the NDE, so that it become more compact and reduce the number of clicks needed to display all information.

   In this idea it remains fundamental that libraries can configure which information display and in which order, that is optimized also for mobiles, that it works well with journals and that "filter" by number or year option keep on working
   The status of the items could also be indicated using colors: for example, Item in Place in green, Out of Library in grey, ...

   Note: we… more

   • 

   •  

   4 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

7. PRIMO Advanced Search: Reduced Usability After Latest Update

   Hello,

   In the latest PRIMO update, the Advanced Search has become less efficient and less intuitive for daily use.

   Previously, it was possible to quickly edit search fields directly within the interface. Now, even small changes (such as editing a title) require reopening the edit screen, which adds extra steps and slows down the workflow.

   For librarians who rely on Advanced Search, this reduces usability and productivity. I would appreciate it if you could consider restoring the previous, more intuitive and streamlined editing experience.

   Thank you.

   •  

   •  

   2 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

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

   1 vote

   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  ·  Integration with other systems  ·  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

9. Change how the 541 holding field displays in Primo VE

   Primo VE users would benefit from improved readability of descriptive metadata in library records. Currently, MARC 541 fields display each subfield (such as c; a; d. on separate lines, which fragments the information and makes it harder to interpret.

   This proposal suggests enabling a configuration option in Primo VE to display the entire 541 field as a single, continuous line with appropriate punctuation between subfields. Presenting the field in this way would preserve the contextual relationships within the data, reduce visual clutter, and make acquisition and provenance information clearer and more accessible to users.

   •  

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

10. Add the funtionality of Add Row to all Labels

    As of now it possible to create copies of Labels to be used in specific views, so that the Label better correlate with the intended user group for that view, by the funtion Add Row.

    However, this isn't an option an all different kind of labels. We suggest that this functionality should be available on all labels, so that the library better can customize their different views.

    4 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  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Suppress controlled vocabulary expansion notification when expansion has no impact on results

    When a search triggers controlled vocabulary expansion but the expansion term contributes zero results, Primo VE still displays the message informing the user that the search has been expanded, and offers a link to disable the expansion (conVoc=false).

    Clicking this link produces no observable change in the result set, since the expansion was not contributing any results in the first place.

    This creates a confusing experience for the user:
    1. The system implies the search was meaningfully expanded
    2. The user is offered the option to opt out
    3. Opting out has no visible effect

    Proposed improvement:
    The expansion notification and opt-out link should only be displayed when the controlled vocabulary expansion actually contributes results. If the expansion term returns zero results, the notification should be suppressed — or alternatively, the UI should clearly communicate that the expansion had no impact on the current result set.

    This would make the interface more transparent and trustworthy, and avoid users wondering whether the opt-out functionality is broken.

    When a search triggers controlled vocabulary expansion but the expansion term contributes zero results, Primo VE still displays the message informing the user that the search has been expanded, and offers a link to disable the expansion (conVoc=false).

    Clicking this link produces no observable change in the result set, since the expansion was not contributing any results in the first place.

    This creates a confusing experience for the user:
    1. The system implies the search was meaningfully expanded
    2. The user is offered the option to opt out
    3. Opting out has no visible effect

    Proposed improvement:
    The expansion notification… more

    3 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

12. Remove harvest date from CONTENTdm import profiles so it can be scheduled

    Currently, an import profile for CONTENTdm cannot be scheduled as there is a bug that prevents the job from running if the harvest date is populated. Please remove the harvest date input.

    1 vote

    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  ·  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. NDE- Links should be visually different from regular text (for example, with underlines) so users can clearly identify clickable elements.

    Primo NDE - The linked values in records, for example under “Creator” and “Subject” are not visually differentiated from plain text. Consider underlining hyperlinks (or applying another consistent link style) so users can more easily identify interactive elements.

    1 vote

    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

14. PRIMO NDE - enable selecting Excel export fields for records from search results

    PRIMO NDE - enable selecting Excel export fields for records from search results

    1 vote

    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

15. Metadata from Database Link Resolver into the Resource Sharing request form

    Allow more metadata from Database Link Resolver into the Resource Sharing request form to ensure the library staff can more easily fulfill the request and patrons are well-informed through notifications of the exact item they have requested - for example a specific chapter from a multi-chapter book written or edited by someone other than the chapter's author. Having the Book Title, Chapter Title, Book Editor/Author, and Chapter Author would be helpful especially for our faculty patrons.

    4 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Provide method for users to opt out of Mixpanel tracking (NDE)

    Users should be able to opt out of Mixpanel data tracking. Although the data sent to Mixpanel is appropriately anonymized, libraries tend to want to allow users to opt out of various tracking mechanisms. Opt-out should be persistent across sessions via a browser cookie or local storage.

    3 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 Functionality  ·  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

17. Black theme for customization color theme

    In the customization color theme of Primo NDE, black (hex #000000) is not one of the 17 colors you can choose.
    Many institutions will have black as the main color in their designguide - for menu, text, icons, element details etc.
    Please develop this option in customizatition color theme.

    3 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  ·  Administrative Tools  ·  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

18. PRIMO - Campo 774 MARC21- manter ordem dos campos catalogados=maintain the order of the cataloged fields

    Gostaria de porpôr a configuração da visualização do campo 774 marc21. No caso de uma miscelânea que tem vários títulos queríamos preserver a ordem dos títulos que estão catalogados. O PRIMO não os apresenta como são catalogados no ALMA, ele ordena-os por ordem alfabética. Seria exelente ter uma opção que respeitasse a catalogação de origem. Ou uma regra que permita a escolha de uma das opções.

    I would like to propose a configuration for the display of MARC21 field 774. In the case of a miscellany with multiple titles, we would like to preserve the order in which the titles are cataloged. PRIMO does not display them as they are cataloged in ALMA; instead, it sorts them alphabetically. It would be excellent to have an option that respects the original cataloging. Or a rule that allows us to choose one of the options.

    Gostaria de porpôr a configuração da visualização do campo 774 marc21. No caso de uma miscelânea que tem vários títulos queríamos preserver a ordem dos títulos que estão catalogados. O PRIMO não os apresenta como são catalogados no ALMA, ele ordena-os por ordem alfabética. Seria exelente ter uma opção que respeitasse a catalogação de origem. Ou uma regra que permita a escolha de uma das opções.

    I would like to propose a configuration for the display of MARC21 field 774. In the case of a miscellany with multiple titles, we would like to preserve the order in which the titles… more

    • 

    1 vote

    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  ·  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. Primo NDE: Full Record Services - split up View It/Get It into its separate sections to allow reordering

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

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

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

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

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

    •  

    43 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Allow Independent Configuration of “Fine” and “Potential Fine” in NDE Loan Displays

    As a Primo administrator, I would like independent configuration control for “Fine” and “Potential Fine” in the NDE loan displays so that libraries can manage Brief and Detailed loan information consistently and transparently.

    Current behavior in NDE is unclear and differs from existing Primo VE behavior:

    • When “fine” is enabled in the Loans Detailed Display configuration, both “Potential Fine” and “Fine” appear as separate labels to users, even though only one configuration option exists.
    • When “fine” is removed from the Detailed Display configuration, both “Potential Fine” and “Fine” are removed from both the Brief and Detailed loan displays in NDE.

    Requested enhancement:

    • Clarify the intended relationship between “Fine” and “Potential Fine” in the configuration.
    • Allow Brief and Detailed loan displays to be configured independently, consistent with current Primo VE behavior.
    • Provide separate configuration options for “Fine” and “Potential Fine,” or clearly document why both labels are displayed from a single configuration setting.

    This enhancement would improve configuration transparency and provide libraries with more precise control over the patron loan display experience.

    As a Primo administrator, I would like independent configuration control for “Fine” and “Potential Fine” in the NDE loan displays so that libraries can manage Brief and Detailed loan information consistently and transparently.

    Current behavior in NDE is unclear and differs from existing Primo VE behavior:

    • When “fine” is enabled in the Loans Detailed Display configuration, both “Potential Fine” and “Fine” appear as separate labels to users, even though only one configuration option exists.
    • When “fine” is removed from the Detailed Display configuration, both “Potential Fine” and “Fine” are removed from both the Brief and Detailed loan displays in NDE.

    … more

    •  

    1 vote

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