91 results found

1. Let patrons choose anonymize or keep their *Historical loans*

   We are anonymizing patron's historical records by the job.
   On the other hand, some of patrons want to keep their loan records.
   So primo should let patrons choose to keep or delete them.

   3 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  User Functionality  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. enable a search of parentheses () in middle of word

   Currently, Primo is unable to retrieve titles containing parentheses in the middle of a word (eg א(י)מניות : אימהות מביאות אמנות לעולם). It seems elementary that Primo should be able to retrieve any record based on its exact title.

   See the following links displaying the issue:

   the search with parentheses:
   https://haifa-primo.hosted.exlibrisgroup.com/primo-explore/search?query=any,contains,%D7%90(%D7%99)%D7%9E%D7%A0%D7%99%D7%95%D7%AA%20:%20%D7%90%D7%99%D7%9E%D7%94%D7%95%D7%AA%20%D7%9E%D7%91%D7%99%D7%90%D7%95%D7%AA%20%D7%90%D7%9E%D7%A0%D7%95%D7%AA%20%D7%9C%D7%A2%D7%95%D7%9C%D7%9D&tab=default_tab&search_scope=books_and_more&vid=HAU&lang=iw_IL&offset=0

   without parentheses:
   https://haifa-primo.hosted.exlibrisgroup.com/primo-explore/search?query=any,contains,%D7%90%D7%99%D7%9E%D7%A0%D7%99%D7%95%D7%AA%20:%20%D7%90%D7%99%D7%9E%D7%94%D7%95%D7%AA%20%D7%9E%D7%91%D7%99%D7%90%D7%95%D7%AA%20%D7%90%D7%9E%D7%A0%D7%95%D7%AA%20%D7%9C%D7%A2%D7%95%D7%9C%D7%9D&tab=default_tab&search_scope=books_and_more&vid=HAU&lang=iw_IL&offset=0

   3 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  User Functionality  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Journal Title Facet Should Include Local Records in Blended Scopes

   Currently, the Journal Title facet in Primo only applies to records from the Central Discovery Index (CDI), excluding locally cataloged article records and those imported from external sources such as institutional repositories. This behavior leads to inconsistent and confusing results for end users, especially when using a blended scope that includes both CDI and local records.

   Problem:
   Users conducting searches—particularly in the local language—often retrieve a significant number of local article records. Despite these articles being published in journals, their journal titles do not appear in the Journal Title facet.
   Users are unaware of the distinction between CDI and local records and perceive the facet as broken or unreliable. This undermines user trust and the usability of the facet as a filtering tool.

   Our question is to
   - extend facet generation logic to include journal titles from local records (Alma-records and imported via import profile)
   - or if this is not possible, allow customers to customize the facet in order to include local records.

   This would ensure:
   - Consistent and complete facet behavior across all indexed content.
   - Improved user experience and trust in the system.
   - Better support for institutions that rely heavily on local cataloging or repository imports.

   Currently, the Journal Title facet in Primo only applies to records from the Central Discovery Index (CDI), excluding locally cataloged article records and those imported from external sources such as institutional repositories. This behavior leads to inconsistent and confusing results for end users, especially when using a blended scope that includes both CDI and local records.

   Problem:
   Users conducting searches—particularly in the local language—often retrieve a significant number of local article records. Despite these articles being published in journals, their journal titles do not appear in the Journal Title facet.
   Users are unaware of the distinction between CDI and local… more

   3 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  User Functionality  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Increase the maximum number of viewable records

   Currently the max number of viewable records is 2000. If the number of search results exceeds 2000, paging beyond the first 2000 records is prevented.

   If the limit is increased, users can continue to view search results beyond the first 2000 records without having to try and refine their search which may be difficult to do.

   2 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  User Functionality  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Primo NDE – Natural Language Search – Support Searching by Physical Location

   Enable Natural Language Search in Primo NDE to take physical inventory and library location into account when answering queries.

   For example:

   "Find physical books about physics in the Harman Science Library"

   The search should be able to identify relevant physical books and limit the results to items available at the specified library or physical location.

   2 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  User Functionality  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Primo NDE – Natural Language Search – Support Searching by Course Reserves

   Enable Natural Language Search in Primo NDE to search for resources based on Course Reserves information available in Alma.

   For example:

   "Find all books for course XXXX."

   The search should be able to identify books and other resources associated with a specific course based on Course Reserves information available in Alma.

   2 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  User Functionality  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Add an "audiobook" indicator to CDI records

   We want to make it possible for our users to facet to and search more effectively for audiobooks.
   In CDI records, both non-musical and musical audio materials have the same resource type, audio, and there is no way to distinguish between non-musical and musical audio materials. Our researchers have identified this as an accessibility issue and barrier for use because they are not able to identify audiobooks in our Primo catalog. Locating audiobooks is important both for general research and to provide access for those needing audio formats.
   For local records, we can identify audiobooks by creating local/secondary resource types and assigning genre headings. These resource types and headings can then be used within pre-filters, facets, and field searching. We cannot enhance CDI records locally, so we would like the audiobook indicator to be added to and made available for faceting or other search features within CDI records.

   We want to make it possible for our users to facet to and search more effectively for audiobooks.
   In CDI records, both non-musical and musical audio materials have the same resource type, audio, and there is no way to distinguish between non-musical and musical audio materials. Our researchers have identified this as an accessibility issue and barrier for use because they are not able to identify audiobooks in our Primo catalog. Locating audiobooks is important both for general research and to provide access for those needing audio formats.
   For local records, we can identify audiobooks by creating local/secondary resource types… more

   1 vote

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  User Functionality  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Add a Collection title field for Collection Discovery, for full record display and search

   Adding records to a collection in Collection Discovery automatically adds them to the out-of-the-box Digital Collections facet in main Primo by the Collections title value.
   It would be a significant boost to discovery of these resources both individually and collectively in the main Primo environment if there was also a Collection title field available to be added to the full record display, which could be configured as a lateral hypertext link, and searchable by the collection title as keywords.
   This would marry together the main Primo environment with the Collection Discovery environment, with the ability to travel between each to find the related content, and taking advantage of options in main Primo such as saving the collection title query as a saved search alert, navigating by the next and previous result arrows through the collection content, filtering by facets such as author or subject, and exporting all the records.

   Use case: I am an academic looking to add works by Aboriginal and Torres Strait Islander authors to my teaching materials for my courses. I’d like to be able to search Primo by keywords for my course content as well as the terms like Aboriginal and Torres Strait Islander authors, find a record and open it to review the details, and click on the lateral hypertext link for the Aboriginal and Torres Strait Islander authors collection to find all the content available for review.
   Another use case is the same scenario but for academics looking for Open Educational Resources to add to their course content, for many libraries who use Collection Discovery to bring together OER content in their collections.

   Note: This is not currently possible to do by a local field as the Collection ID is not available as a bibliographic record data reference to map in the Collection Title to each record PNX. A local field can be used in a very manual way by adding rules for mapping the harvest point for a record and then adding the collection title, but this limits collection content to bibliographic data and does not leverage the ability to manage collections by logical sets using physical titles in location codes and all works with specific Authority IDs.

   Adding records to a collection in Collection Discovery automatically adds them to the out-of-the-box Digital Collections facet in main Primo by the Collections title value.
   It would be a significant boost to discovery of these resources both individually and collectively in the main Primo environment if there was also a Collection title field available to be added to the full record display, which could be configured as a lateral hypertext link, and searchable by the collection title as keywords.
   This would marry together the main Primo environment with the Collection Discovery environment, with the ability to travel between each to… more

   1 vote

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  User Functionality  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Change CDI handling of Language data for Primo

   CDI Language data in handled in ways which have undesirable impact on patrons in Primo, such as:
   • A default language is applied to all records in a CDI feed for use in Primo in the Language field display, search, and facet. This may be done when the CDI provider feed has no record-specific Language information available automatically and the provider has not otherwise advised that all the records are in a specific known language and confirmed that this Language can be applied to the records in CDI
   • Records may be allowed to merge into a CDI logical record even when the Language data differs across participant records. All of the participant record Language values are then included in the Language facet bar ‘outlier’ languages stripped out, and then one Language value may be selected to display in the record according to library full text activations, even if it contradicts the Language facet value

   It is understood that the CDI is a massive index and that strategies such as collection level normalisation rules are necessary in order to manage this scale of data.
   However, it is feared that the experience of individual users is inappropriately de-prioritised and lost in these decisions focused on “acceptable” percentages of impact, which may seem tiny relative to the size of the index, but may be significant to actual people using our discovery layer.
   The practical reality is that such handling of Language information at a broad scale in CDI causes a negative impact for people using Primo, as the information is clearly incorrect and features cannot be used as expected.
   It may be argued that patrons are unlikely to encounter such issues on a regular basis, but this also ignores common knowledge of human nature that even one or two experiences of being presented with clearly false information is enough to build distrust in all future experiences.

   For example, the Language facet cannot be used when a patron is specifically trying to target results in a certain language, when they know in advance or learn from initial results that their search term may return records for multiple languages with different meanings.
   ISSUE
   “Persona” has different meanings in Spanish and English and the patron wants the English variation.
   STRATEGY
   With a search by “personas school principals” the patrons deliberately selects to include only the Language facet value of English and exclude the Language facet value of Spanish.
   BUT
   Ex Libris has applied Language facet value of English broadly as a default in the CDI provider feed and/or has artificially selected a Language from participant records to display in the record regardless of the Language in the facet.
   RESULT
   The patron sees in their results many records stating English when they are clearly in Spanish in both the metadata and full text.
   Examples (screenshots attached):
   • cdicrossrefprimary105944reopvol30num1201925194
   • cdiunpaywallprimary1014295idonlinev15i583330
   • cdijstorprimary_40654076
   OUTCOME
   This patron may then submit a complaint to the library or simply decide that their library provides a poor service and stops using our discovery layer in favour of other options.

   When opening a case to report such patron complaints with examples of unexpected incorrect information in Primo, it is advised that this behaviour is expected and that current handling was chosen over other options to mitigate the impact of insufficient provider CDI metadata in Primo.
   This could be by including a Language information in the records of ‘No linguistic content’ or ‘Undetermined’ to ensure a facet count matched to a result count, not allowing records to merge when there are Language differences, and not presenting Language facet values which do not match Language display values.

   Ex Libris considers it a “resolution” to such cases for defect reports to document this behaviour, shifting responsibility to their library customers to explain to complaining patrons.

   This approach focusing on quantity over quality does not centre the individual user as a person, and disregards the harm to the professional reputation of libraries, degrading the trust our patrons place in our services and which we are responsible to provide for our institutions, to support teaching, learning, and research.

   Now that such behaviours have been documented over time as “expected”, this issue moves from hope it is resolved as a defect, to a product enhancement request that Ex Libris change the current design decisions causing this problem.

   This submission requests that Ex Libris reconsider and change these practices with the individual user in mind, committing to align Language data across display, search, and facets and to consistently present only accurate Language information in the Primo discovery layer.

   CDI Language data in handled in ways which have undesirable impact on patrons in Primo, such as:
   • A default language is applied to all records in a CDI feed for use in Primo in the Language field display, search, and facet. This may be done when the CDI provider feed has no record-specific Language information available automatically and the provider has not otherwise advised that all the records are in a specific known language and confirmed that this Language can be applied to the records in CDI
   • Records may be allowed to merge into a CDI logical record… more

   •  

   1 vote

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  User Functionality  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. In Primo Research Assistant, please add the ability to pre-select filters. Specifically, we need to pre-select the available online filter.

    In Primo Research Assistant, please add the ability to pre-select filters. Specifically, we need to pre-select the available online filter. Our students are often frustrated when the results include resources that must be requested.

    1 vote

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  User Functionality  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Landolt-Börnstein collection

    Can you please add the Landolt-Börnstein collection since it isn't available in SFX? Our library has the entire collection through Springer Materials. Thank you

    1 vote

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  User Functionality  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating