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

28 results found

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

    57 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)
  2. 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.

    50 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)
  3. 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.

    56 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)
  4. 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.

    120 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)
  5. 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.…

    44 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)
  6. 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.

    38 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)
  7. 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…

    57 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)
  8. 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

    77 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)
2 Next →
  • Don't see your idea?

Feedback and Knowledge Base