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

    160 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  2. Allow reader to sort the values in a facet by A-Z or by number of records.

    Most databases such as Web of Science or Ebsco Discovery tool allow the user to determine how to sort the values in a facet (see screenshot)

    158 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. 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…

    153 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. configure the order of the holdings records in the GetIt tab

    It would be very useful to have an option to configure the order of the holdings records to be displayed in Primo (e.g. according to the loan period) as opposed to the current situation where the order is random.

    144 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  5. Primo VE: add peer-reviwed and open access facet values to local records

    In Primo VE you can add an OpenAccess indicator to the records, but it should also be possible to add a value (bases on normalization routines) that includes these records into the OA facet value in the top-level facets, so they are included when using this filter. This option should apply to both Alma records and external data records.

    The same normalization option should be available for the Peer-reviewed indicator and facet value

    139 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Primo VE  ·  Admin →
  6. Review content type in Primo is confusing

    Currently the Review content type in Primo / Primo Central seems to contain both Book Reviews such as
    http://shu-primo.hosted.exlibrisgroup.com/44SHUVU1:defaultscope:TNsciversesciencedirectelsevierS0261-5177(06)00203-2

    and Review Articles such as
    http://shu-primo.hosted.exlibrisgroup.com/44SHUVU1:defaultscope:TN_proquest1373464971

    It would be better if these were in separate content types.

    136 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  7. Add 'search' feature in e-shelf

    Users should be able to search for references in their eShelf lists based of any <search> field contents in the PNX and wherever the references may be (not sensitive to folders).

    135 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  8. Add an Abstract resource type for the Primo Central Index

    Primo Central Index contains many records for abstracts of conference papers that have been published in journal issues/supplements.

    These records are given the Article resource type in Primo. This confuses users, who when they find these items expect a full-length article instead of a short abstract.

    It also creates problems with link resolvers, which attempt to generate article-level links and fail (publishers usually do not provide these abstracts as individual articles).

    To fix this, Primo Central should be given a new resource type for abstracts.

    The sources for these records are usually large indexes such as Scopus or Web of…

    133 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Other  ·  Admin →
  9. 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.

    133 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  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.

    131 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  11. My Library Account: add Recalled Loans Tab

    It would be very beneficial for library patrons to be able to view their recalled loans, at a glance, when checking their library account in Primo; please could you add a Recalled Loans tab to the Overview section of My Library Account

    132 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  12. Move Peer Reviewed into it's own facet group

    The Peer Reviewed facet is currently grouped in the Availability facet group. It has nothing to do with Availability or the other things in the Availability facet group. Not seeing another facet group that makes sense, Peer Reviewed should be in it's own facet group. This will make more sense to the user, allow more flexibility in controlling the placement and the look and feel of these individual facets.

    128 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  13. Bib MARC field 505$t should be indexed in the Primo PNX file as a title entry

    The MARC 505$r is indexed in the PNX as Creator and contributor. The MARC 505$t is not similarly indexed in the PNX as an added or alternate title.

    123 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Primo VE  ·  Admin →
  14. Primo Central Index ( PCI ) - more granularity in excluding content from activated resources - e.g. exclude from index by resource type

    Right now in Primo Central Index the customer can either activate or not a resource. But sometimes more granularity would be appreciated. Namely adding a filter by resource type allowing inclusion or exclusion in the index would be very useful. Please note: it's not a matter of adding a resource type in PCI. It's a matter of excluding records with a specific resource type from activated resources.

    For example, some resources/data sources contains not only articles, but also journals and other resource types we actually catalogue. Since right now dedup does not work between local records and PCI, this ends…

    122 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Other  ·  Admin →
  15. warning message when unpinning a record from the favorites page

    It would be very useful if upon clicking on the unpin icon in the favorites screen, Primo will display a warning message stating that the user is about to delete the marked record/s.
    Currently, clicking willingly or inadvertently on the unpin icon will immediately and irreversibly delete the record/s.

    122 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  16. Add a field ISSN and E-ISSN that are separated but can be matched for Dedup / F

    For more efficient DEDUP of ejournal and print journal.
    The dedup test mach ISSN, but the ISSN of printed journal record is usually different from the e-ISSN of the electronic journal record, thus there is no match between two these numbers.

    118 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Admin →
  17. Add starts with functionality to Call Number field in the advanced search

    "starts with" functionality should be added to the Call Number field in the advanced search in Primo.

    117 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  18. Add Australian language codes to Primo Back Office

    We would like Austlang (Australian language) codes added to the out of the box language code and mapping tables in Primo and for this coding to map to language facets and language display without any additional intervention by institutions. These language codes, used by many Australian libraries, are recorded in the 041$a field(s) of the bibliographic record. These codes do not conform to the three alpha character coding found in ISO639-2 or 639-3. Australian libraries would expect to use these codes in addition to the standard language coding currently available.
    The full list of Austlang codes can be downloaded from…

    114 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  19. 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.

    113 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  20. 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…

    112 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Primo VE  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base