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. bad link reporter

    Bad Link Reporter

    This tool would work while librarians are searching Primo. An addon tool for Primo that looks at results when the following condition exists: a link is clicked and user gets an error, (no full text available or other Primo error messages) there would be a popup or message asking “report this bad link?”. You click on the button, it goes away allowing librarian to continue their work but clicking the button reports the permalink, search details and bad link error message including eresource used. This option only occurs for library staff. Ordinary users would not see it.

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

    108 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. EZProxy (Primo institution wizard) more granular application against specific collections

    Currently in Primo institution wizard (Primo Home > Ongoing Configuration Wizards > Institution Wizard > Delivery Base URLs) you can enter an EZProxy base URL. If a proxy is added it will be applied to all Link in Record type resources (though there is the option to exclude OA collections). I would like more granularity so that we could choose to apply the proxy to certain Link in Record type collections, but not to apply the proxy to others.

    86 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. Make configurable preference of source in deduplication

    Preference of records coming from differente sources in deduplication is hardcoded in Primo and it causes undesired situations, for example poor SFX records have preference over rich ILS records and the information from ILS records is discarded. Order of preference of sources should be configurable through Primo Admin interface instead of being hardcoded

    74 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  5. Show the terms added to the patron's query by the linguistic features (i.e. stemming, synonyms etc.)

    As default behavior, Primo not only looks for the patron's query, but enriches the original keywords of the user with additional terms, in order to improve the performance.

    The system first tries to guess the language of the query, and then tries to enrich it, using a variety of steps described in the Linguistic Features section of the documentation: https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/Technical_Guide/120Linguistic_Features

    For example, a query for the string: Birne
    if recognised as German, is enriched with following synonyms (dictionary file as to March 2017):

    gluehbirne(normal),gluehlampe(normal),lampe(normal),leuchte(normal),leuchtkoerper(normal),haupt(normal),kopf(normal),ruebe(normal),schaedel(normal)

    The point is that the whole thing is a blackbox for both the librarian and the…

    58 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  6. Generate a report of the MMSID's harvested by Primo Back Office

    We would like to be able to generate a report of the MMSID's harvested by Primo Back Office.

    58 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  7. View Primo as someone else / different types of users

    View Primo as "someone else". It would be useful to view our Primo-page as different types of users. Being able to view Primo as an internal user, or a student, or staff member, or an external user, would help us troubleshoot configuration and settings in Alma. Have we activated the right functionality for the different user groups? Have we hidden what we want to hide?

    tl;dr: Facebook's "View as" functionality in Primo.

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

    54 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  9. Allow libraries to review PCI metadata in collections

    We would like the ability to not only see more information about the collections (which is already another idea on here) but also the ability to see the metadata for each collection. For example, for Kanopy, we have loaded the MARC records into Alma, but would like to review what the metadata for the PCI collection looks like so we can make a decision about whether or not to enable it. We have no way to know what the PCI collection will add or do until we turn it on in production Primo.

    52 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  10. Add MODS template as Date Source for OAI-PMH harvest

    Currently, there is no MODS template for OAI-PMH harvesting of external collections. As an example, we have many collections in an Islandora repository and have very rich metadata in MODS format. We lose most of that metadata when the collection is harvested because we must use the DC template as the Source format.

    50 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  11. Allow to delete records in Primo BE ( included dedup records )

    Right now the only way to delete a record in Primo is to refer to a KB Article [1] explaining how to write an xml OAI-PMH record with status 'deleted' and let the xml file to be ingested by a pipe. The procedure is cumbersome and error prone (e.g. issues with compression of the file on non linux machines etc.) and it does not always work properly. For example, dedup records are not properly deleted by this procedure.

    It would be good to provide a feature in the Primo BE allowing to look for specific PNX and to delete it.…

    49 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  12. Copy parts of Normalization Rules Sets to other fields in the same set

    It would be very useful to be able to copy subsets/blocks of a Normalization Rule Set to other blocks/fields in the same set, instead of manually copying very complicated rules. This was a NERS request from the Free University of Bozen (4440), but it did not receive enough votes.

    43 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  13. Dedup and FRBR cluster monitoring

    Since BIRT reports in back office are being deprecated and they are not available in VE, those who implement Dedup or FRBR will have no way to monitor the clusters that goes beyond what's currently in analytics (just a report of cluster sizes). Size of clusters is important, but when "impossibly large" clusters form (we recently noticed many, up to 89 members!), we need to be able to see the records forming the cluster in order to diagnose problems. The BIRT tool is way too slow and unwieldly for this purpose but provides useful information: contents of the fields that…

    40 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  14. Include all fields in PCI Activation Center download option

    Please include all fields present in the PCI activation center when downloading/exporting.

    Currently the only fields exported are:

    Provider name
    Collection name
    Newspaper search
    Search
    Full Text
    Link to Full Text
    Active for Search
    Central Update frequency
    Description

    We would like to see all available fields exported, including:
    Added On:
    Last Activated On:
    Resource Types:
    Local Note:

    39 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  15. We would like the ability to weight certain PCI results higher than others (ie. Hathitrust)

    We have an example journal of Index Medicus. When we search this record in our blended local and PCI search the hathitrust PCI record does not display until the 3rd-4th page: https://purdue-primo-prod.hosted.exlibrisgroup.com/primo-explore/search?query=any,contains,index%20medicus&tab=default_tab&search_scope=everything&sortby=rank&vid=PURDUE&mode=Basic&offset=0

    If we want to withdraw the print record, because it is available in hathitrust, having this on the 3rd-4th page is not acceptable. We would like the ability to boost or weight certain PCI resources, based on the collection name, higher within our results.

    This request seems somewhat related to:
    https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/16944994-provide-institutions-with-the-ability-to-systemati
    https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/16945003-provide-institutions-with-the-ability-to-systemati

    Although this request to me is more generic than both of those, but seemingly related.

    Thanks!

    35 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  16. Add functionality in relevancy ranking for Primo to adjust according to full text criteria

    We would like to be able to adjust the relevancy ranking of the results page to display full-text versions above duplicate results that show no full text available.

    Example:
    This would be most helpful for sources coming from ProQuest Dissertations & Theses (PQDT), where the PQDT result shows as full-text available but results from other PCI sources (ERIC, ProQuest, etc.), show the source as "no full text available."

    We think this would be helpful for other situations, too.

    33 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  17. Ability to administer synonyms via BO

    The systemSynonyms and userSynonyms files are only available via the command line so SaaS customers have to request changes be made via SalesForce.

    It would be easier to administer if the ability to view systemSynonyms and download/upload/deploy userSynonyms be in the BO.

    29 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  18. Send email when pipe finishes with errors.

    When a pipe finishes normally, but some records did not load due to errors, right now the only way to find out whether that happened or not is to go into the back office, Monitor Primo Status, Pipe Monitoring, and click on "Errors" next to the pipe (and a futher step to get to "History" if the pipe is not the last one run).

    We run four Alma pipes a day, and around a half dozen other pipes once a day. WE DON'T HAVE TIME TO DO THIS and I bet a lot of other customers don't either.

    But we…

    23 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  19. Delete uploaded items from file uploader

    Add an option to delete files that were uploaded using the file uploader.

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  20. Multilingual CT and MT: Configure inherited languages

    Right now most CTs and MTs in the Backoffice are configured in a multitude of languages. The possibility to configure the languages needed by the instance and/or institution would make the usage more convenient and also save disk space.

    OTB-Tables could stay the same as they are now, of course. But for at least the instance – if not even single institutions – a set of needed languages should be configurable.

    20 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
← Previous 1 3 4
  • Don't see your idea?

Feedback and Knowledge Base