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. Display both link in record and links from link resolver in CDI

    When there are records in CDI that have link in record, but also would return links from the link resolver both types of links should be displayed to the end user.

    The challenges with the link in record are discussed in this idea: https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/40487230-preference-cdi-link-resolver-records-over-link-in

    They have a tendency to break and if the link for some reason do not lead to the full text the end user does not get any other way to the full text (as they do with the multiple links fromt he link resolver).

    We hope that Ex Libris enables the system to display both link…

    605 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    Thank you for suggesting this idea, the direction is to enable customers to show more links and offer some configuration options to set preferences.

    Note that this is not something that we can do in the near future since it is a complex change.

  2. Secondary sorting of records in the results list

    Primo is designed to sort the results list by one parameter only (relevancy, title etc.).
    Currently, it is not possible to define a secondary sort. Thus records with the same ranking will appear in no particular order.
    It would be beneficial to be able to configure a secondary and third sort options. For example, first sorting by Relevancy, secondary by Publishing Year and third by Title.

    567 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. Allow "best location" on brief results display to be configured by view

    A user viewing a view that is associated with a particular library or campus should be able to view availability of physical items at that library or campus libraries in the brief results layout. This idea is primarily for institutions with multiple libraries and, especially, multiple campuses. Campuses are associated with libraries, and typically a Primo view will be associated with a campus.

    Currently "best location" can only be set via the user's IP address. This approach works when users are at the location, but when a user is off-campus, the first location to show on brief results and full…

    322 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. Warn user to sign in when saving to favorites

    Primo (new UI) does not alert the user to sign in in order to save favorites. I suggest that when a user who has not logged in clicks the pushpin icon to save an item to Favorites, a modal appear to let them know they must sign in to save favorites, and give them an opportunity to do so.

    298 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  5. Hide DUE TIME in Primo

    It should be possible to hide DUE TIME in Primo, both in My Library Card and the item list. Many libraries do not offer loans by the hour and opening hours in Alma are not the same as the opening hours of the physical library. Therefore displaying the due time in Primo is often just noise.

    See attached screenshots.

    272 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  6. 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

    175 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  7. 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.

    140 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  8. Hide completed purchase requests from the Primo MyAccount

    Completed purchase requests (rejected or approved) should not be visible in the Primo MyAccount.

    127 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Primo VE  ·  Admin →
  9. Adding 'Issue' as a new resource type in Primo Central

    Resource types used in Primo Central are limited to 23 (book, article, journal, image...) [See pdf "Primo Central Index Resource Types" in the Documentation Center].

    For digitized journal issues, the type in use is 'journal'. Archive collections like HathiTrust may contain tens of thousands of digitized journal issues; institutional repositories may also contain complete issues… This is finally confusing for end-users for who see issues labelled as journals and for whom filtering by resource type has become useless.

    Adding a 24th type 'Issue' for this material would be welcome! ‘Journal’ would thus only remain for real journal records.

    96 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  10. Generate citation on multiple pinned items

    Our users make heavy use of the generate citation button, but they currently have to do this one record at a time. It would make things easier for them if they could pin all the relevant items, and then go into My Account, select all their pinned items, and generate a citation for all of them.

    They can currently perform several actions by batch on all pinned items - email results, export to Refworks and so on - but the generate citation action is not yet available to them.

    The citation that appears could be simply plaint text, with the…

    94 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  11. Primo VE: Ability to use norm rules to specify which 856 (Marc) fields display in Links service

    In Primo Back Office (BO), it is possible to use normalization rules to specify which 856 Marc fields display in the "Links" section of the Primo full record view. (See attached screenshot.)

    We would like the same functionality in Primo VE to choose which 856 links to display based on the 856 first and second indicators and/or the subfields of the 856 field. Thank you.

    86 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 →
  12. • Records without a date at the bottom of results list when sorting on date oldest

    At this moment, the sort option “Date oldest” displays the records without a date on top of the results list. This is confusing and not relevant for users; when there are several records without a Creation Date they probably conclude that sorting on date oldest doesn’t work. Our request is to display the records without a date always at the bottom of the results list when a sort option on date is used (thus as well for date oldest as for date newest)

    79 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  13. Analytics - advanced search stastistics

    Hi there,

    According to SF case 422111 it's currently not possible to provide detailed statistics about advanced search field through OBI.

    As for the facets, we would like to know the number of using field by field.

    For example :
    - We would like to know how many clicks were done on search field "Topic"
    - We would like to know how many clicks were done on search field "Author"
    - We would like to know in how many session the search field document type / books was used
    - Which are the fields the most used in the advanced…

    75 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  14. Collection Discovery: search in all sub-collections

    We would like to allow the user to use the Collection Discovery interface also for discovery. Currently, it is only possible to search at the collection level. It is important to enabling a search across all levels of all collections as the user cannot know in which collection/sub-collections to search for needed items.
    Following are a couple of user stories:
    * We have various collections of photos. We would like to allow the user to search across the various collections and sub-collections for the pictures of the Knossos temple. We have relevant photos in two different sub-collections.
    * We would…

    66 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  15. Version control system for back office configuration

    A version control system for back office configuration tables, pipes, normalization rules etc.
    For files like Custom HTML, CSS, JS, PDS etc. we can manage change history and revert to older versions by using version control systems like Git, Subversion etc. For configuration managed via the web back office and database this is not possible, but it is a vital feature of professional system management. This will become more important in a full SaaS environment.

    57 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  16. Customizable RIS mapping table for Primo VE

    In Primo, customers could customize the RIS export table, to determine what PNX fields should be used for RIS fields. In Primo VE this is not possible:

    The mapping of the RIS fields to PNX fields is as follows:
    IS addata/issue
    TY addata/ristype
    N2 addata/abstract
    N1 addata/notes
    PB addata/publisher
    A2 display/contributor
    ET addata/edition
    KW display/subject
    EP addata/epage
    DO addata/doi
    PY addata/date ; display/creationdate
    JA addata/stitle
    VL addata/volume
    CY addata/cop
    AU display/creator
    T3 addata/seriestitle
    T2 addata/addtitle
    T1 display/title
    SP Addata/spage
    JF Addata/jtitle
    ID Alma MMS ID
    SN Addata/issn; addata/isbn; addata/eissn; addata/eisbn

    As most reference managers will read A2 as Series Editor,…

    55 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Primo VE  ·  Admin →
  17. Tagging a Pinned item - stop forcing the entire page to reload each time

    Paraphrased omment from one of our patrons:
    - When I tag something I have pinned, the entire page has to refresh- which means it jumps all over as images come in etc and can take up to 5 seconds to fully load. Not all browsers act the same. Chrome gets me close to where I was while FireFox is a Magic 8 ball. One time I land back at the record I just tagged, the next, I am 6 records up the list. I'm working my way through my list trying to organize my articles for a lit review -…

    16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  18. Session Timeout Warning

    It would be most helpful if a 'Session Timeout' warning could be displayed a certain amout of time before the session actually ends. Included in the warning could be the options to 'keep me logged in' or 'log out now'.

    13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  19. Improve webhook availability/links display for Newsbank/Access World News

    Ex Libris has collaborated with Newsbank/Access World News to enable the use of a search webhook to enable content discovery within the Primo/Primo VE platform -- which is great! However, we are finding the current display of availability and links within the Newsbank webhook largely unusable, preventing us from implementing within our public production environment. The problem is that no online availability statement is displayed in results list nor brief record display, and no View Online area appears in the record. The results and records appear exactly the same as content outside of our full text results -- EXCEPT for…

    10 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  20. Display of 541 and 561 fields in holdings records should be determined by value in first indicator of the field

    Currently if display of 541 and/or 561 fields in holdings records is enabled in "Holdings Display Customization", 541 and/or 561 fields display in the GetIt section in Primo regardless of the value in the first indicator. If the value in the first indicator is zero then the 541/561 field should not be displayed - this is standard MARC coding (see https://www.loc.gov/marc/holdings/hd541.html and https://www.loc.gov/marc/holdings/hd561.html ).

    Ex Libris proposed a solution to us where when the holdings record is saved the a 541 and/or 561 field with first indicator empty or 1 is copied to a 999 field, and in the Holdings…

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

Feedback and Knowledge Base