Skip to content

Primo

Your feedback matters to us. Help us improve Primo by telling us what you’d like to see using the message areas below. You can also can support something already posted.

We would love to be able to respond to every idea that is submitted, but this is not feasible. We are, however, committed to responding to the most popular ideas—those that have received the most points.

For more information please review our FAQ and guidelines. Thank you.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

647 results found

  1. Users should be able to request individual volumes from multi-volume record

    We have a record that has multiple volumes of the same manga in it.

    https://wisconsin-uwp.primo.exlibrisgroup.com/discovery/fulldisplay?context=PC&vid=01UWI_PL:PARK&search_scope=DN_and_CI&tab=default_tab&docid=cdi_globaltitleindex_catalog_113538775

    The individual volumes are impossible to request for the user. This has to be done on the Alma side by a staff person. We would like records like this that have multiple volumes to have requestable individual volumes.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Primo VE  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. IZ level view configuration

    As a library network with a large number of Primo views, it can be extremely laborious to update every single view for configuration options that are identical in each view. These include in particular all configuration options that can be found in the General, Links, Advance Search, Brief results, Brief record display and Full Record Services tab of the view configuration menu.

    This kind of centralised view management would need to be available at the IZ level as it does not fulfil the same purpose as the possibility to distribute configuration from the the Network Zone to the various Institution…

    79 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Primo VE  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Person entity - add an option for users to request more information about a person

    Many Person Info Cards have little/no information. An option for users to request more information about a person would give user communities agency to prioritize authority work by information professionals.

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Primo VE  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Person entity - add an expandable text option that can be customized by institution

    Add an option to add explanatory text to the Person Info Card and Person Page, so that institutions can provide users with more details about these features in the interface. Transparency around the data presented by libraries in discovery interfaces is increasingly important with the proliferation of ai-generated content and users' understandable lack of trust.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Primo VE  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  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…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Primo VE  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Pair display of 880 fields with their linked MARC field

    When a record includes multiple 880 fields paired with multiple entries from the same MARC field, for example multiple 700 and 880-700 fields, Primo VE displays all the 700 fields and then all the 880-700 fields. This display loses the link between the two fields, and a user cannot easily connect the non-Latin script (in the 880 field) with the paired Romanised form (in the 700 field).

    In the MARC record the link between fields, such as a 700 and its paired 880-700, is coded in the $6. If the Primo VE display normalisation rules syntax allowed you to compare…

    115 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Primo VE  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Primo VE  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. please add pick up library in purchase request form for patron to choose if checking "reserve"

    Hi, sir,
    There is purchase request library in primo VE purchase request form.
    But usually the request library is not same as user pick up library, if patron check "reserve", that mean once the purchase is accepted and book send to library ,alma will generate a reserve for this request.
    but now has no patron's pick up library for reference.
    so please add a pick up library filed in purchase request form if checking "reserve".
    Thanks ~

    20 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Show the date/time a question is asked in the AI research assistant, and in the copied result.

    The date/time a question was asked is only visible when hovering over the question in the research history sidebar. This is a problem especially when working with history items that have multiple questions.
    Scenario: User asks a question on something contemporary. They want to ask the same question in 3 months and then again in 6 months as more sources become available.

    From the history they open their previous question and use the "Try again" function. In another few weeks they do this again.

    The question responses do not indicate when each iteration of the question was asked.
    If they…

    11 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Provide option to remove 490 field from Browse Index

    We would like the option to remove the 490 series description field from the Browse index. Because we use 490 for series description and 8XX for the authorised form of series in the same record, the browse series feature in Primo counts one record twice. If we could have the option to remove this from the Browse index, this would solve the problem. It would need to be optional as it is clear that some Primo Libraries rely on the 490 for this purpose.

    22 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Primo VE  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Support for Numeric Subfields (e.g., $0, $1) in MARC to PNX Mapping in Primo VE

    Currently, numeric subfields such as $0 and $1 are excluded from Primo VE’s standard MARC to PNX mapping. This prevents institutions from displaying and passing on crucial metadata, such as authority IDs, in/from the Primo VE UI.

    Please map at least subfields $0 and $1 to PNX
    This would greatly benefit libraries that rely on authority control and linked data, ensuring that identifiers like VIAF and GND IDs can be used for enhanced metadata display and linking within Primo VE as provided for by the MARC standard .

    Use Case Example:
    A record with multiple subject headings (650 fields) includes…

    23 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Primo VE  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Primo VE  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. CSL Data (Citation Style Language) in Primo Search API

    Primo uses Citation Style Language to generate citations for bib records. Presumably the bibliographic metadata is at some point converted to a csl-data object. https://github.com/citation-style-language/schema/blob/master/schemas/input/csl-data.json

    It would be helpful if that csl-data JSON object was available through the Primo Search API. This could be a additional information one could request from the API. https://developers.exlibrisgroup.com/primo/apis/docs/primoSearch/R0VUIC9wcmltby92MS9zZWFyY2g=/

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Allow Digital Viewer to use different View than Primo

    When viewing digital representations in the Digital Viewer, Alma-D uses the same Primo VE View; however, this can cause some difficulties when configurations ideal for Primo don't translate well to the Viewer.

    For example, we have a pop-up chat icon in Primo VE for patrons to chat with librarians; because this is configured in View, it's also present in the Digital Viewer, but the icon ends up obscuring parts of the representation's image and metadata.

    We'd like to be able to point the Digital Viewer to a different View entirely than the one Primo VE is currently using.

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Primo VE customize logo tooltip/description

    Allow tooltip/description text to be added to the uploaded logo in the Primo VE view customization, similar to the "Links Menu" customization description.
    This is a basic usability feature that should be easy to configure.
    Our usability testing showed that about half the users expected the logo to go back to the main Primo VE search landing page rather than the library's home page (as many libraries have configured). Having a description on hovering would help clarify for users.

    8 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Primo VE  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. 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…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Primo VE  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Track the positions of selected records in search result list

    As a Discovery & Systems Librarian, I monitor the relevance ranking configuration and the boosting configuration in blended search profiles on our site. It will be tremendously helpful if the positions of selected records in search result list are tracked. For example, higher positions says the relevance ranking is working well than lower in the list.
    Selecting a record includes actions such as clicking on permalink, clicking on quick links, clicking on any OpenURLs, e-mail, citation, print, save to e-shelf, and for physical items, request item from the library.

    8 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Improve Primo VE drool editor messaging to display an error if the rules fail

    Currently the Primo VE drool editor will not display error messages in some situations where the rules crash and fail.
    Instead the Discovery Administrator flows through the process of updates believing that their changes to the rules are correct and have taken effect, only to find perhaps much later after reindexing request that they have not.
    Actually what happens is that if the rules fail, there is no error shown, and the entire ruleset fails back to the out-of-the-box rules.
    This is a considerable hindrance given the situation of no option to test display rules.

    Ex Libris advised in a…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Journal Title Facet Should Include Local Records in Blended Scopes

    Currently, the Journal Title facet in Primo only applies to records from the Central Discovery Index (CDI), excluding locally cataloged article records and those imported from external sources such as institutional repositories. This behavior leads to inconsistent and confusing results for end users, especially when using a blended scope that includes both CDI and local records.

    Problem:
    Users conducting searches—particularly in the local language—often retrieve a significant number of local article records. Despite these articles being published in journals, their journal titles do not appear in the Journal Title facet.
    Users are unaware of the distinction between CDI and local…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. AI based tool for suggesting alternative search queries to users with saved searches and email alerts

    I was wondering if there could be an AI based tool for suggesting alternative search queries to users who have saved searches and have set email alerts. When they receive an email alert they could be suggested an AI generated search query (similar to what the AI Research Assistant could elaborate, with synonyms and boolean operators) to be checked for more results.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Primo VE  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Feedback and Knowledge Base