72 results found

1. My Library Card: add sort by date option to requests list

   it is currently only possible to sort the requests list within My Library Card by status or title - our users would very much appreciate the option to sort by request date as well - thanks for considering!

   9 votes

   Vote 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

2. A new type of search - Authority Search

   Add Authority Search as a new type of search in Primo. The new feature will enable both patrons and librarians to search the authors and topical subjects from their authority records and link to the related records in their local catalog(s) and preferably also CDI.
   The search will be based on alma's authority files and Linked Open Data.

   This development was part of the Primo roadmap for 2021 and was removed.

   A similar search option was implemented at the University of Haifa using local customizations and a dedicated search scope + view.
   It enables to search a term only on authority records and displays double-sided links: from the term's authority record to its occurrences as authors or subjects in the bibliographic records, and from a bibliographic record (in the regular Primo search) to the authority terms in the authority scope.

   A short video for a demonstration: https://shellyaridor-haifauniv-lib.tinytake.com/msc/Njg0MTgwNl8xOTQ5NzQ5MA

   (*) To support this feature also in Primo via Back Office, Alma APIs should publish authority information as XML records Primo can use.

   Add Authority Search as a new type of search in Primo. The new feature will enable both patrons and librarians to search the authors and topical subjects from their authority records and link to the related records in their local catalog(s) and preferably also CDI.
   The search will be based on alma's authority files and Linked Open Data.

   This development was part of the Primo roadmap for 2021 and was removed.

   A similar search option was implemented at the University of Haifa using local customizations and a dedicated search scope + view.
   It enables to search a term only on… more

   48 votes

   Vote 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
   Planned  ·  AdminYael (yael.shahar@clarivate.com, Ex Libris) responded

   Hi,

   This is to update that we plan to develop a new type of search for Authorities. We will update with the specific release date.

   
   

   Best regards,

   Yael.

3. My Favorites load automatially as user scrolls down

   In a recent student survey we had feedback that users would like their complete list of Favorites to be more accessible and visible. In particular, users requested that instead of choosing 'Load more results' after every ten My Favorites, that their My Favorites list auto-loaded as they scrolled down the page.

   8 votes

   Vote 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

4. "Feedback Tool" for the New Primo UI: insert the e-mail of the logged in user automatically

   Currently the field "e-mail" in the Feedback form is defined as optional.

   As well as with the current e-mail functionality of bibliographic citations, we would expect the e-mail to be automatically pre-filled when a user is logged in. But unfortunately this does not happen.

   Please insert the e-mail of the logged in user automatically or at least give us the possibility to set this option in the Primo backend.

   Thank you in advance!

   P.S.: Please see also this Idea:
   Feedback Tool for Primo VE - allow user's email as addressFrom in Report a Problem Letter
   https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/45350419-feedback-tool-for-primo-ve-allow-user-s-email-as

   19 votes

   Vote 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

5. Add Generic Record Actions

   In View Configuration > Brief Record Display > Record Actions, implement the function of adding generic icons to the Full Display.

   It should be possible to add:
   - An icon file
   - A label
   - A URL template(if possible using variables)

   This would decrease the amount of programming necessary to add new features and expand on the amount of information that can be added(Eventhough you can already add a lot of features)

   9 votes

   Vote 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

6. Enable search and browse also for item call numbers, not only holdings

   Hi

   We switched to Primo VE some months ago and are really missing a call number index that shows all our call numbers, in items as well as in holdings.

   https://slidetodoc.com/three-types-of-call-numbers-in-alma-yoel

   "Item Call Number – is it in Primo VE search indexes?
   • The item call number cannot be added as a Primo VE search index.
   • Of the three call numbers only the “Holding Call Number” can be added as a Primo VE search index."

   Our call number index is set to "callnumber.4 – Shelving control number call number", our item call numbers are type 4, but they are missing in the call number index.

   https://basel.swisscovery.org/discovery/browse?vid=41SLSP_UBS:live

   ---

   Examples:

   https://slsp-ubs.primo.exlibrisgroup.com/permalink/41SLSP_UBS/mmbbsj/alma9920741170105504

   No hit in call number index search for
   UBH Bc I 50
   UBH Bc I 51
   UBH Bc I 52

   ---

   https://basel.swisscovery.org/permalink/41SLSP_UBS/mmbbsj/alma9910081250105504

   Can not be found in the call number index under UBH AL VII 42:1993

   ---

   We know that it can be done in Alma (see screenshot), but we need the function also in Primo.

   ---

   In addition to the index search, please also index the item call numbers for simple and advanced search.

   Hi

   We switched to Primo VE some months ago and are really missing a call number index that shows all our call numbers, in items as well as in holdings.

   https://slidetodoc.com/three-types-of-call-numbers-in-alma-yoel

   "Item Call Number – is it in Primo VE search indexes?
   • The item call number cannot be added as a Primo VE search index.
   • Of the three call numbers only the “Holding Call Number” can be added as a Primo VE search index."

   Our call number index is set to "callnumber.4 – Shelving control number call number", our item call numbers are type 4, but they are… more

   521 votes

   Vote 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…)
   3 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

7. Enable retrieval with/without/compound hyphens in Hebrew

   It is very important to enable the search in Primo with and without hyphen to retrieve all relevant records (with hyphen, without hyphen and as compound words).
   Some examples of current discrepancies in retrieval are:

   צפון-קרוליינה retrieved 2 results
   צפון קרוליינה retrieved 486 results

   עת-מול retrieved zero results
   עת מול retrieved 83 results, including the title עת-מול : עתון לתולדות ארץ ישראל ועם ישראל. ‬

   searching using the pre-filter Title and limiting to 2010-2021 for
   ארצות הברית retrieves 71 results
   ארצות-הברית

   96 votes

   Vote 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…)
   7 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

8. "Feedback Tool" for the New Primo UI: possibility to define the e-mail field as a mandatory field

   We have been using the feedback tool for a few weeks now and have unfortunately received many requests where the users did not provide an e-mail address.
   As a result, we have no way to ask a question or explain the reported behaviour (as it is correct).

   Therefore, we would be glad if the e-mail field can be defined as a mandatory field in the Primo back office.
   A user can of course still enter a fake e-mail address, but then this is a deliberate action.

   Thank you in advance!

   13 votes

   Vote 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

9. Primo does not work with some date formats used for old material and rare books.

   Primo does not work with some date formats used for old material and rare books. The biggest problem is that Primo only recognises 4-digit dates and does not accommodate date searches for pre-1000 dates that have 3 digits or less. This issue greatly inhibits searches for a significant number of users of archives and rare material collections.

   Primo also does not work well with dates in square brackets that include text and unknown dates that have a question mark or dash instead of the wildcard character ‘u’ - e.g. [i.e. 1973], [between 1772 and 1802?], 195? or 195-. These are all valid date formats that follow international bibliographic standards and are frequently found in bibliographic records. It would be beneficial to our users if these issues could be addressed and fixed.

   Primo does not work with some date formats used for old material and rare books. The biggest problem is that Primo only recognises 4-digit dates and does not accommodate date searches for pre-1000 dates that have 3 digits or less. This issue greatly inhibits searches for a significant number of users of archives and rare material collections.

   Primo also does not work well with dates in square brackets that include text and unknown dates that have a question mark or dash instead of the wildcard character ‘u’ - e.g. [i.e. 1973], [between 1772 and 1802?], 195? or 195-. These are… more

   51 votes

   Vote 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…)
   2 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

10. Hide digitization button when items of a title are on loan / unavailable

    We would like to suggest the option to hide the digitzation button when all items of a title are on loan / unavailable.
    Currently, titles can be requested for digitization while all items corresponding to a title are on loan or unavailable, which can result in significant waiting periods between requesting a title for digitization and the fulfillment of said request.
    Therefore, we propose that the digitization button only appears when an item is available for the title in question. This would benefit patrons, since they can assume that if a request can be made, it will be processed right away.

    We would like to suggest the option to hide the digitzation button when all items of a title are on loan / unavailable.
    Currently, titles can be requested for digitization while all items corresponding to a title are on loan or unavailable, which can result in significant waiting periods between requesting a title for digitization and the fulfillment of said request.
    Therefore, we propose that the digitization button only appears when an item is available for the title in question. This would benefit patrons, since they can assume that if a request can be made, it will be processed right… more

    89 votes

    Vote 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

11. Remove CDI constant expansion of results

    PCI results respect that a user knows what they want, but help with expansion when necessary, such as by stemming when there are very few results returned by the exact query. A user has autonomy also to target their results with techniques such as quotation marks, Boolean operators, and Advanced Search.

    In CDI, expansion is constant, by term inflection applied to all searches, as well as higher recall in general by design. This cannot be prevented by features such as Boolean operators, quotation marks or Advanced Search, and is illogical in conjunction with other features like 'Did you mean'.
    Note: It is recognized that these may represent different underlying mechanisms, but it is the user outcome which is key.

    Ex Libris states that CDI behaviour "does not affect precision" because of Verbatim Match Boost, which will rank more highly the exact search query, but they have designed this as also meaning "near verbatim", completely undermining this concept.

    Use case: If a user searches for ATLA, then they expect only results for ATLA and not atlas. CDI returns 7 of 10 first page results which are clearly returned on the basis of atlas by term highlighting, even at No.1, and yet also offers a "Did you mean: atlas", which barely changes the results when clicked.

    Use case: If a user searches for a DOI, then they expect only that specific resource. CDI returns dozens of results with often no indication by term highlighting or snippets to explain why. This is discovered only after a timeconsuming check on the full text to be because the DOI is in the Reference List. There is no clear pathway to the actually correct known item, and this is not consistently fixed just by ranking changes. For example, if we do not hold that article in full text, the user sees dozens of results, none of which are correct, instead of the expected pathway of the Zero results message, using the expansion checkbox, and then leveraging the metadata in the 'No full-text' citation to prefill an ILL form.

    This is the opposite of precision.

    The design should centre the user and the needs they directly express when entering their search query, allowing the choice to both target their search by the techniques above, as well as giving the option of expanding their search, which is even more important given the larger CDI index.
    One option could be returning the expected targeted results matching the user query, and then offering a suggestion similar to a clickable Did you mean or Controlled Vocabulary features, such as: "Results also referencing [query]"

    PCI results respect that a user knows what they want, but help with expansion when necessary, such as by stemming when there are very few results returned by the exact query. A user has autonomy also to target their results with techniques such as quotation marks, Boolean operators, and Advanced Search.

    In CDI, expansion is constant, by term inflection applied to all searches, as well as higher recall in general by design. This cannot be prevented by features such as Boolean operators, quotation marks or Advanced Search, and is illogical in conjunction with other features like 'Did you mean'.
    Note:… more

    753 votes

    Vote 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…)
    15 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
    Planned  ·  AdminAmy Pemble (Admin, Ex Libris) responded

    This improvement is planned for the 2024 Roadmap.

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

13. Allow patrons to disable FRBR + disable FRBR in advanced search

    Hi

    Our patrons run into a lot of problems caused by FRBR.

    Please
    – Add a checkmark to allow the patrons to disable FRBR per search, no matter if logged in or not.
    (like "Include articles without fulltext")

    – Make it a parameter in the patron settings

    – Disable FRBR as default in advanced search

    ---

    This could also be used as a feeble workaround for the missing exact search https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/18579556-add-a-true-exact-search-to-advanced-search-type

    116 votes

    Vote 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…)
    19 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
    Under Review  ·  AdminNili Natan (Product Manager, Ex Libris) responded

    Thank you for posting this idea. We are considering to have a new toggle 

    ""group versions together"  where users can choose to if to have search results grouped by versions or turn it off.  

14. Alerts in a consortium with NZ: send alerts for records added to the inventory of the institution of the user

    The alert functionality is not really functional in a library network with a Network Zone. Users get an alert when a new bibliographic record is created in the Network Zone, but most users don't care about new acquisitions in other institutions. What they want is to be alerted on new acquisitions in their own institution. This means: to get an alert when a new bibrecord is added to the inventory of of their IZ (not only by creating a new record but also by adding a holding or portfolio to an existing record in the NZ).
    Our request is to allow for alerts at the institution level in a consortium with NZ.

    The alert functionality is not really functional in a library network with a Network Zone. Users get an alert when a new bibliographic record is created in the Network Zone, but most users don't care about new acquisitions in other institutions. What they want is to be alerted on new acquisitions in their own institution. This means: to get an alert when a new bibrecord is added to the inventory of of their IZ (not only by creating a new record but also by adding a holding or portfolio to an existing record in the NZ).
    Our request is to… more

    98 votes

    Vote 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…)
    3 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

15. Include call number for physical items in Excel / CSV Export

    Thank you for adding the option to export results in Primo to Excel and CSV.

    Please could the call number for physical items be added as an extra column in the export. When clients export results from Primo, their intention is also to look for those items that are physical on the shelves and without the call number, they again have to access each record's link to obtain the call number.

    231 votes

    Vote 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…)
    19 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

16. Reconcile top-level facet selection (one by one vs. multiple)

    Currently, if you select top-level facets one by one (e.g. "Peer-reviewed Journals" then "Full Text Online"), you get different results than if you select both facets at once (using the checkboxes and clicking "Apply Filters".) The first applies a boolean AND and the second applies a boolean OR.

    Ex Libris support has confirmed that this intended and expected behavior.

    This functionality seems confusing to both our patrons and staff. I think I can see the argument if this occurs within certain other facets (e.g. Resource Type), but because this happens with top-level facets that do not otherwise seem like the same sort of facet (e.g. "Peer-reviewed Journals" and "Full Text Online"), our patrons and staff have been finding this to be unexpected behavior.

    Requesting that this functionality be revisited, especially when it comes to top-level facets.

    Currently, if you select top-level facets one by one (e.g. "Peer-reviewed Journals" then "Full Text Online"), you get different results than if you select both facets at once (using the checkboxes and clicking "Apply Filters".) The first applies a boolean AND and the second applies a boolean OR.

    Ex Libris support has confirmed that this intended and expected behavior.

    This functionality seems confusing to both our patrons and staff. I think I can see the argument if this occurs within certain other facets (e.g. Resource Type), but because this happens with top-level facets that do not otherwise seem like the… more

    63 votes

    Vote 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…)
    4 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

17. "Search within results"

    We would like to propose a "Search within results" option for Primo. "Search within results" would be a keyword search across all fields present in a user's results list. This is an option offered in common databases, such as Web of Science, so it is something users expect. We feel this search function would increase Primo's usability particularly for inexperienced users.

    111 votes

    Vote 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…)
    2 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

18. Alternative Coverage & Newspaper Search in PCI/CDI

    We rely on PCI alternative coverage for maintaining the best discovery layer as this enables full text access to results obtained from known-item searches and topic searches. Using both PCI alternative coverage and the Newspaper Search together present challenges. Using both of these options together result in too many false positives; false positives disappoint users and erode their trust in our discovery system.

    Please consider including the Newspaper Search with the regular Primo Central updates that are compared against our institutional electronic holdings file so the Availability statements are correct. As we look ahead to the introduction of CDI, please consider including the Newspaper Search with the regular CDI updates in comparison against our institutional electronic holdings file as well.

    We rely on PCI alternative coverage for maintaining the best discovery layer as this enables full text access to results obtained from known-item searches and topic searches. Using both PCI alternative coverage and the Newspaper Search together present challenges. Using both of these options together result in too many false positives; false positives disappoint users and erode their trust in our discovery system.

    Please consider including the Newspaper Search with the regular Primo Central updates that are compared against our institutional electronic holdings file so the Availability statements are correct. As we look ahead to the introduction of CDI, please… more

    61 votes

    Vote 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

19. Add a multilingual keyboard to the User Interface

    Our patrons want to search in multiple languages in Primo, e.g. Chinese, Russian, Arabic, etc. When they come to the library they are often limited, because of the local keyboards. A virtual multilingual keyboard would be an ideal solution to support their needs.
    Portal Judaica (cf. screenshot attached) provides an example of how to implement this in the user interface. The website https://www.lexilogos.com/ supports a variety of languages to give you an idea of which languages should be supported by the virtual keyboard. Thank you for voting.

    [internal reference PRM-252]

    •  

    31 votes

    Vote 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

20. View user request history

    We would love to be able to view a user's request history in the Requests tab of their account. You can view Returns and Fines histories so why not Requests?
    This would be very useful for students and staff! Thanks.

    226 votes

    Vote 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…)
    21 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
    Accepted  ·  AdminYael (yael.shahar@clarivate.com, Ex Libris) responded

    Hi all,

    This is to update that we are planning to develop this option in the Primo Next Discovery Experience User Interface.

    More details on the new interface planning can be found here - 

    https://knowledge.exlibrisgroup.com/Primo/Product_Materials/010_Primo_Next_Discovery_Experience_User_Interface.

    
    

    Best regards,

    Yael.