736 results found

1. Enhancing visibility of Open Access indication for CDI article records

   Problem:
   [see 1OAPrimo.png] Currently, the Open Access indication appears under a title in Primo for Open Access CDI article records, which can confuse library users. They might think that all collections under "View Online" are all full-text open access.

   Idea: To enhance clarity for users, we recommend first configuring Alma settings to control the display of the Open Access indication, followed by adjustments in Primo.

   [In Alma] [see 2OAPrimo.png] We propose adding a tick box or a dedicated field within the service level settings to indicate open access. When enabled, this setting will control whether the OA indication appears.

   [In Primo] [see 3OAPrimo.png] Once configured in Alma, the OA indication can be displayed clearly in front of the collection name under "View Online," helping library users easily identify Open Access resources.

   Problem:
   [see 1OAPrimo.png] Currently, the Open Access indication appears under a title in Primo for Open Access CDI article records, which can confuse library users. They might think that all collections under "View Online" are all full-text open access.

   Idea: To enhance clarity for users, we recommend first configuring Alma settings to control the display of the Open Access indication, followed by adjustments in Primo.

   [In Alma] [see 2OAPrimo.png] We propose adding a tick box or a dedicated field within the service level settings to indicate open access. When enabled, this setting will control whether the OA indication appears.

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

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

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

4. Make "patron default sort" an optional feature

   Please allow customers to disable the Patron Default Sort feature. [1]

   Since this feature was added to Primo last year, we are regularly contacted by perplexed users wondering why relevancy ranking isn't working. Invariably, the users had selected a different sort option the last time they used Primo and did not realize that Primo would remember their sort options in the future.

   If there are no plans to implement this feature in NDE, please disregard this request.

   [1] https://knowledge.exlibrisgroup.com/Primo/Release_Notes/Primo/2025/Primo_2025_Release_Notes?mon=All#Patron_Default_Sort

   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

5. Make advanced search and natural language search terms visible for Primo NDE in portrait view of mobile phone devices

   At present, when a user undertakes a Natural Language search or Advanced Search in Primo NDE on a mobile phone in portrait mode, the search query is not displayed however this is being displayed when viewed in landscape mode.

   User's may not know to change the orientation of their device to see this information.

   Support case #10573480 created with ExLibris responding as follows:
   "Due to UX considerations and current UI limitations in the mobile view, the advanced query search terms are not displayed. This behavior also applies to natural language searches. At this time, there are no plans to change this behavior".

   At present, when a user undertakes a Natural Language search or Advanced Search in Primo NDE on a mobile phone in portrait mode, the search query is not displayed however this is being displayed when viewed in landscape mode.

   User's may not know to change the orientation of their device to see this information.

   Support case #10573480 created with ExLibris responding as follows:
   "Due to UX considerations and current UI limitations in the mobile view, the advanced query search terms are not displayed. This behavior also applies to natural language searches. At this time, there are no plans to change… 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…)
   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

6. DC record mapping to Journal Title, RIS Volume, Year, Issue

   Based on the current Primo VE documentation, both dcterms:isPartOf and dcterms:bibliographicCitation may be used in the mapping to the addata section. These fields can also be used for extracting host information, such as volume, issue, and year, when the value is formatted accordingly.

   The problem is with keeping the journal title in dcterms:isPartOf (for example, Technologies) and place the enumeration value (for example,14(2026)2) in dcterms:bibliographicCitation is that it override the Journal title in the RIS and display the enumeration instead. (See RIS export below). It is currently a limitation in mapping to extract Journal title to JF and volume, issue to the correct RSI field at the same time.

   <dc:date>2026/dc:date
   <dc:relation xsi:type="journal">Technologies/dc:relation
   <dc:relation xsi:type="volume">14/dc:relation
   <dc:relation xsi:type="issue_number">2/dc:relation

   TY - JOUR
   JF - 14(2026)2
   PB - MDPI
   Y1 - 2026
   ID - alma991027502611907026
   AU - Saleh, Omar A.
   AU - Rao, Saleem G.
   AU - Alghadeer, Mohammed
   AU - Omar, Ahmed A.
   AU - Felemban, Muhamad
   SN - 2227-7080
   T1 - Optimizing Interface Dielectric Loss in Superconducting Coplanar Waveguide Resonators for Improved Quantum Circuit Coherence
   ER -

   Primo VE documentation:
   https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/Primo_VE_%28English%29/120Other_Configurations/Mapping_to_the_Display%2C_Facets%2C_and_Search_Sections_in_the_Primo_VE_Record

   Based on the current Primo VE documentation, both dcterms:isPartOf and dcterms:bibliographicCitation may be used in the mapping to the addata section. These fields can also be used for extracting host information, such as volume, issue, and year, when the value is formatted accordingly.

   The problem is with keeping the journal title in dcterms:isPartOf (for example, Technologies) and place the enumeration value (for example,14(2026)2) in dcterms:bibliographicCitation is that it override the Journal title in the RIS and display the enumeration instead. (See RIS export below). It is currently a limitation in mapping to extract Journal title to JF and volume, issue… 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…)
   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

7. Make it possible to show suppressed bibliographic records in the collections lobby

   We have a large collection where we only want to make a select number of more academic titles discoverable in Primo search so that library users aren't overwhelmed with irrelevant content.

   It would still be good to make all titles in the collection discoverable through an alternate means, however it isn't possible to add these to the collections lobby without these appearing in Primo search. The collections lobby only shows titles with unsuppressed bibliographic records. Can we make an option to allow suppressed records to be viewed in the collections lobby?

   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

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

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

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

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

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

13. Restore the "Other" A–Z browse category for Journal Search in Primo VE/NDE

    Primo Classic Journal Search includes an Other browse category for journal titles beginning with punctuation or other non-alphabetic characters. Primo VE and the NDE Journal Search currently provide only 0–9 and A–Z, leaving journals whose titles begin with punctuation without an intuitive browse location. Please restore the Other browse option (or otherwise provide equivalent access) to maintain feature parity with Primo Classic and ensure all journal titles are discoverable through browsing.

    Some titles that might make good examples for this would be:

    @Tic : revista innovació educative

    +E

    # Tear

    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

14. In the NDE, reinstate the option to include a link to RefWorks in the User Account menu

    In Primo VE, the option exists to include a link to the RefWorks platform in the User Account menu drop-down. Ex Libris Support have confirmed that this is not currently an option in the Primo NDE

    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

15. Force user to scroll to the end of Copyright statement

    Hi,

    For a digital record in NDE, after expanding "Digital Content", it show a Copyright statement. User can tick the checkbox and click Confirm without scrolling the Copyright statement.

    Is it possible to force the user to scroll down to the end of the Copyright statement before the user can tick the checkbox?

    Example record:
    https://julac-cuhk.primo.exlibrisgroup.com/permalink/852JULAC_CUHK/1gglqj8/alma991040165302003407

    Thanks,

    Howard Lam
    CUHK Library

    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

16. Confusing screen navigation for digital file in Primo NDE

    Hi,

    For a digital file, e.g.
    https://julac-cuhk.primo.exlibrisgroup.com/permalink/852JULAC_CUHK/ljhnov/alma991040538347003407

    When clicking Online access, it jumps down to Digital Versions section. When clicking the digital viewer icon, it jumps up to Digital Content section. Screen navigation is very confusing.

    It is more natural that when clicking the digital viewer icon, the digital file (Digital Content section) can be shown below it, or somewhere related. But it is not possible to move the Digital Content section position at all.

    Please see attachment for details.

    Thanks,

    Howard
    CUHK Library

    • 

    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

17. Freeze the top level resource type filters on NDE so they continue to appear as the user scrolls through their search results

    Currently on NDE the top level availability facets are fixed in place even when a user scrolls down their results list, however the resource type facets above these disappear from view when the user scrolls down the page. We would suggest also keeping these fixed in place and visible to the user as they scroll so they have a constant quick visual reminder of what they have filtered to.

    • 

    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

18. Allow multiple custom CSS stylesheets per view

    At the Digital Theological Library, we have multiple campuses, each of which has its own view. All of the views use the same basic custom design, but each one needs its own specific CSS tweaks. Maintaining this would be much simpler if all of the views could have two custom CSS files: one with the basic design rules and one with the specific design tweaks. That way, when the base design is updated, the view-specific CSS can't accidentally be disturbed by copying and pasting within a single stylesheet, and Primo UI managers like me won't need to copy and paste across all of our views in the first place. The view-specific stylesheet would need to be listed after the main CSS in the <head> of the page to avoid incorrect cascading.

    Another option that would be even easier to use from my perspective but would probably be harder to implement would be to have a set of system-wide view styles that could then be overridden with individual custom.css stylesheets. Either solution would greatly improve my workflow for maintaining multiple views and would also benefit other Primo institutions with multiple campuses or customized views.

    At the Digital Theological Library, we have multiple campuses, each of which has its own view. All of the views use the same basic custom design, but each one needs its own specific CSS tweaks. Maintaining this would be much simpler if all of the views could have two custom CSS files: one with the basic design rules and one with the specific design tweaks. That way, when the base design is updated, the view-specific CSS can't accidentally be disturbed by copying and pasting within a single stylesheet, and Primo UI managers like me won't need to copy and paste… 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…)
    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

19. Add navigation to the top of the search results

    Currently users need to scroll down the full page of results before being able to move to the next page of results. This becomes laborious if users have chosen to display 25 or 30 results per page.

    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

20. Enable users to select records from multiple pages of results

    Currently if a user selects a few records from a page of results and then navigates to the next page they lose their record selection. This idea is to enable users to navigate through their results list, page by page selecting records as they go and then when finished complete the desired action on the selected records.

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