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
  1. Do Not Highlight Stop Words in the Results of a Keyword Search

    There is no value to highlighting words in the search results of a keyword search that were considered STOP words when the search was conducted.

    Words such as AND, THE, OR, IN, TO, etc., provide no value on their own and should not be highlighted. Not only does highlighting them add visual noise to the search results, it sends the wrong message to users about how to construct a strong search string.

    As the screenshot shows, the highlighting is only adding noise.

    260 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Primo VE  ·  Admin →
  2. Improve Primo Search Algorithms

    When our users look for a book in the Primo Search Portal they expect that the Primo Search behaves like a Google Search, i.e. they expect that Primo finds books with titles or metadata containing words similar to those in their query. Unfortunately, the Primo Search is very sensitive to the exact spelling of the words in the query. If the search query is slightly inaccurate, the book is not found in Primo. I tried such unsuccessful search queries on www.amazon.de, and Amazon usually found the correct book: Amazon showed the correct hit on top of the list (see…

    252 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 →
  3. Make it possible to add or exclude records from the OTB resource display types based on locally-defined conditions

    We would like to have more flexibility with Primo VE resource types and the related facet and prefilter values. There are situations in which we would like to be able to add records to an OTB resource display type that don't meet the OTB conditions. For example, for certain textual integrating resources that users are likely to think of as books, we use conditions based on the presence of form/genre headings to add them to the OTB ""book"" display type in Primo BO (e.g., open textbooks that are periodically updated: https://searchit.libraries.wsu.edu/permalink/f/j5jme3/CP71251613210001451). Conversely, we would sometimes like to be able…

    252 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 →
  4. course reserve

    Course Reserves:
    Requested Enhancement: Offer interface with drop-down menus for Course Title, Course Department, and Course Instructor (similar to drop-down menus in Voyager)

    Currently users can search for course reserves, but there is not a good mechanism to browse. Offering drop-down menus would easily allow users to see what was currently on course reserve by course title, department and instructor.

    Thank you for considering

    251 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  5. Limit autocomplete-suggestions from PCI/CDI to activated sources

    In Primo you can activate autocomplete to get suggestions for search-queries based on what the end-user begins to type in the search-box.

    We have tested the functionality and see that it could be useful for the end user to get these suggestions. However we see that the suggestions from the central index in some cases are a little strange and that you get suggestions from the entire index and not only the sources the institution has activated. This means that the end-user could get suggestions that gives 0 results.

    If you get a suggestion that leads to nothing you will…

    247 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  6. Display 6XX fields with $v form subdivisions intact

    Primo VE is configured to map 6XX $v form subdivisions to a separate display field, breaking the subject string. In some cases, the form subdivision is plucked out of the 6XX, leaving the surrounding string incomplete. For example:

    600 10 $aO'Keeffe, Georgia, $d1887-1986 $vExhibitions
    displays in Primo VE as:

    Subject O'Keeffe, Georgia, 1887-1986

    Genre Exhibitions

    651 #0 $aRome (Italy) $vMaps $vEarly works to 1800
    displays in Primo VE as:

    Subject Rome (Italy)

    Genre Maps
    Early works to 1800

    And so on, for all 6XX $v form subdivisions. This cannot be reconfigured. Additionally, each occurrence of the form subdivision is displayed…

    240 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 →
  7. Allow libraries to configure the Brief Record Display with more flexibility

    In the brief and full display pages, libraries can display information contained in data fields (such as the title, author, and creation date) from the source record. This information helps users to differentiate records quickly. In some cases, there can be a lot of information that is displayed. This is particularly the case when Contributor is added: all 7XX fields are added, and in their entirety (see for example in the attached screenshot).

    We would like an option that would allow the library to either limit the number of fields to display (for example max 3 7XX fields) or to…

    230 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Primo VE  ·  Admin →
  8. Wrong holdings information for FRBR-grouped books outside of IZ

    An institution owns a specific edition of a book, ex:https://bibsys-almaprimo.hosted.exlibrisgroup.com/primo-explore/fulldisplay?docid=BIBSYS_ILS71566408110002201&context=L&vid=SSHF&search_scope=default_scope&isFrbr=true&tab=alle_bibliotek&lang=no_NO

    When extending the search scope to other libraries, they may find other editions of the book, which they don’t own (https://bibsys-almaprimo.hosted.exlibrisgroup.com/primo-explore/fulldisplay?docid=BIBSYS_ILS71566408110002201&context=L&vid=SSHF&search_scope=blended_scope&isFrbr=true&tab=alle_bibliotek&lang=no_NO ).

    The original/owned book's barcode is shown for the other edition(s) as well. This is unfortunate as it is quite confusing (contradictory messages, give the impression the library owns resources it doesn’t), and can lead the user to order the wrong book.

    The availability status is correct but the holdings information is not. The ISBN should be used here to prevent tis from happening, instead of the…

    224 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  9. Display related holdings for monographs only for the 773 $w relation and not for the 8xx $w relation

    When filtering to a certain location via facets, you often get results from other locations too, which is unexpected from patrons perspective in many cases. This is caused by the current related records setting which is also taking locations with related records into account. The display is correct for analytical records without inventory (book chapters and articles), but not for the other monographical resources.

    What we wish to achieve is the following:

    When the record of a book chapter, journal issue or journal article (i.e. a record containing a 773 field with $w) is viewed in Primo, the holding of…

    223 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Primo VE  ·  Admin →
  10. Full integration of Syndetics enrichment content

    Syndetic Solutions enrichment content should be indexed in Primo, to aid the retrieval of books (especially by chapter titles in TOCs) and displayed inline in the new Primo UI. The acquisition of Ex Libris by Proquest should make this commercially easier to arrange, and it should be technically easier on the Primo "cloud" platform.

    209 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  11. Allow for consistant customizations in the new UI

    The open discovery of the new UI allows customers to customize the new UI, extend its functionalities, and connect Primo with external services.
    This framework can offer an important added value to institutions; it can enable them to respond to specific needs of their user community.
    We want to implement extensions for functionalities like:
    • Offer a button “report a problem” that allows a user to report a broken link or another problem with a specific source he found. The form sends this message to our helpdesk, together with useful debug info like : is the user on or off…

    205 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  12. my account - loans sort options

    User should be able to sort their loans not only by title and due date, but also by author, location, maximum renewal date and status (renewable or not) -> all columns shown should be sortable.

    204 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  13. Separate language menu

    In August release 2018, there is finally a good improvement in the sign in area, but unfortunately the language selection is now inside a personal menu. If guests user enters Primo which by default is not in his native language, they wouldn't know what to do. There is a nice solution created by Manneheim University, and I hope Exlibris will take it as an example:

    https://primo-49man.hosted.exlibrisgroup.com/primo-explore/search?vid=MAN_UB&sortby=rank&lang=de_DE

    Naomi

    202 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  14. Increase Primo search capability to support major common search expansions on synonyms.

    Salesforce case #00583901 refers (unpublished)

    Ex Libris advises that, due to performance considerations, Primo search is unable to support the search expansion for the spelling variants that include the use of 's' or 'z' within a word. This is a common trans-Atlantic spelling variation, and omitting it has a significant impact on search results.

    Example: a search for the terms “practice globalisation” produces 441,248 results, but by changing the 's' in globalisation to a 'z', Primo produces an additional 12,000 search results.

    202 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  ·  Other  ·  Admin →
  15. Find e-Journal by Title search

    Add the following radio buttons to the Find e-Journal by Title search:

    *Contains
    *Starts with
    *Exact

    187 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  16. Search Slot/Scope/Profile Usage in Primo Analytics

    We would like to be able to report the total number of searches that have been performed in each search/slot/scope/profile that we have configured in Primo. Currently the only report in Analytics that has Search Scope search information is the Zero Results Report.

    This information will provide invaluable information about our user behaviour and will help us in the customization of the Primo interface to meet the needs of our clients by assisting in decisions regarding adding or removing search profiles/scopes.

    186 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  17. text

    Allow users to text themselves call number/location for an item

    182 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  18. Less duplicate records in Primo Central Index results

    Primo Central grouping is based on the existing FRBR workflow, including the grouping process at the database level (the way the Search engine handles grouping) and the Front End functionality. It is used to prevent duplicate records in the results list.

    Unfortunately, many records are not added to FRBR groups because the system considers the metadata are not rich enough. With the increase of records provided by (Open Access) aggregators and repositories, the number of duplicate records will certainly not decrease.

    Could Ex Libris improve the FRBR workflow for Primo Central records in order to reduce the number of duplicate

    177 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  19. Browses: add See Also and Usage info from authority headings

    Primo supports display of See references (not same as See Also) in browse headings, if those cross-references are in the bibliographic data ingested by Primo. There is no capacity to display See Also and Usage info from authority records, which are important so that users understand how and why certain terms, especially subjects, may be used.

    We propose that See Also and Usage info display in the Browse headings.

    Example headings and See Also and Usage info that does NOT currently display in Primo:

    Blacks:

    Search also under: subdivision Blacks under individual wars, e.g. World War, 1939-1945--Blacks; and headings beginning…

    175 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  20. Collection Discovery usage in Primo Analytics

    Currently, Analytics possibilities for "Collection Discovery" are rather limited. With action “Display a Collection”, you can for example see how many times your collections (all together) have been displayed, added to favorites... in a period of time, but you cannot see which collections are the most and the less successful, what materials should maybe be more promoted, which collection should maybe be removed because its content is maybe of too little interest, which collections are added to favorites, etc.

    Therefore, we would like Collection IDs and Collection Names to be transferred to Primo Analytics. Additionally, if this could also be…

    174 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  • Don't see your idea?

Feedback and Knowledge Base