647 results found

1. Limit Research Assistant results to resources patrons can access

   It would be nice at a configuration level to be able to limit the Research Assistant results to those within an institution's collection and OA as the default setting, rather than the entire CDI as it is currently.
   Users could then select to expand their search to the CDI, like they currently do when searching Primo.

   45 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  ·  Primo VE  ·  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. Apply Display Logic Rules to CDI direct linking records

   Currently, records that provide full text solely via a CDI link-in-record URL are not subject to Display Logic Rules (see documentation note below). This leads to inconsistent behavior and display compared to other CDI records.

   For example, our article ILL General Electronic Service is configured not to display when there is full-text available on a record. This works as expected for records that have full-text provided via the link resolver, but for CDI direct linking records, the ILL GES displays alongside the full-text link. This confuses our patrons, who think that the presence of the ILL link means the full-text link isn't working.

   We request the capability to apply display logic rules to CDI direct linking (link-in-record) records as we can do for CDI records with link resolver full-text.

   Documentation note, added due to case #06712066: "Display logic rules are only applied when the Alma link resolver provides the links. CDI direct linking records are not generated by the Alma link resolver mechanism; therefore, Display logic rules are not applied for them."
   https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/Primo_VE_(English)/080Configuring_Delivery_Services_for_Primo_VE/Configuring_Discovery_Interface_Display_Logic_for_Primo_VE

   Currently, records that provide full text solely via a CDI link-in-record URL are not subject to Display Logic Rules (see documentation note below). This leads to inconsistent behavior and display compared to other CDI records.

   For example, our article ILL General Electronic Service is configured not to display when there is full-text available on a record. This works as expected for records that have full-text provided via the link resolver, but for CDI direct linking records, the ILL GES displays alongside the full-text link. This confuses our patrons, who think that the presence of the ILL link means the full-text… more

   •  

   •  

   94 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  ·  Primo VE  ·  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. Fix Export and Print Problems with My Library Card in Primo VE and NDE

   Background:
   When a user goes to their My Library Card in Primo VE they can see all the items that they have checked out. However, if the user tries to print or export this list, it excludes any suppressed bib records. Interlibrary loan records are usually suppressed because we don't want our search results to return titles we don't own. As a result, the user can see the interlibrary loan titles they have checked out, but they cannot print or export them.

   We reported this problem to Ex Libris, after a graduate student noticed the discrepancy and reported it to us. We escalated our ticket several times. However, Ex Libris is choosing not to fix this issue. They expect this will also be a problem in the NDE.

   Impact:
   Users cannot effectively track what they've borrowed and are also unable to export their list to citation management software for their research work. Heavy ILL users are most impacted by this design defect.

   Request:
   When a user exports and prints the My Library Card list, it should include all items they have checked out, even if the bib is suppressed.

   Additional Information:
   Ticket numbers: 07738988 and 07805073

   Ex Libris Documentation: https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/Primo_VE_(English)/150End_User_Help/12Exporting_Records_from_Primo_VE#Exporting_Records

   Background:
   When a user goes to their My Library Card in Primo VE they can see all the items that they have checked out. However, if the user tries to print or export this list, it excludes any suppressed bib records. Interlibrary loan records are usually suppressed because we don't want our search results to return titles we don't own. As a result, the user can see the interlibrary loan titles they have checked out, but they cannot print or export them.

   We reported this problem to Ex Libris, after a graduate student noticed the discrepancy and reported it to… more

   35 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…)
   5 comments  ·  User Interface  ·  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. Add a language limiter to the Journal Search

   Adding a language limiter to the Journal Search in Primo (VE or NDE) would be immensely helpful to students who need to find journals in specific subject areas.

   4 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  ·  Other  ·  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. Consistent display of the "Search Inside" feature for Journal, Magazine, and Newspaper records

   Primo VE was developed in 2017 with a "Search Inside" feature, originally appearing only on Journal type records. In 2019 when CDI was developed Newspaper and Magazine types were added to the discovery environment.
   Unfortunately It appears that Ex Libris forgot to consider local records holistically, despite that Newspaper is an out-of-the-box configured type for Alma in Primo VE and many of their customers offer a blended search experience for their patrons.
   This is evidenced in an inconsistency that Search Inside displays on Newspaper records from CDI and fails to display on Newspaper records for local records. It will also not display on Magazine type local records, if a site chose to configure this.

   Ex Libris initially advised that they would consider correcting this, as part of a SalesForce case seeking to have the current functionality explained and documented. Finally after 10 months it was explained why the feature appearance was found to be inconsistent:
   “Local records—If the record has an ISSN (contains an addata/issn or addata/eissn field) and is a journal. To identify a journal, the display/type field must start with the word journal, or the record must contain an addata/jtitle field (not an addata/btitle or addata/atitle field).
   CDI records—If the record has an ISSN (contains an addata/issn or addata/eissn field) and is a periodical. To identify a periodical, the display/type field must start with the word journal, or the record must contain an addata/jtitle field (not an addata/btitle or addata/atitle field), or the addata/format and addata/genre fields must be set to journal. If the above criteria are met for CDI records, this section may also appear for magazines and newspapers.”

   These varying conditions mean that the feature does not display in Alma Newspapers, because the addata/jtitle field is not currently populated, as there is only as stitle not only for Newspaper type content, and there is no addata/format and addata/genre populated.
   Primo VE customers have no configuration options to fix this, with no access to addata PNX rules.
   And to add insult to injury, this inconsistent Search Inside feature also cannot be disabled by configuration, only by custom code application, for which Ex Libris explicitly does not provide support.

   Unfortunately Ex Libris ultimately advised after a year of the case being open that they would not fix this situation, documented the current inconsistency for Search Inside, and refused to engage further.

   This enhancement request is for the Search Inside development to be addressed holistically and simply, to display Search Inside consistently by the display type of Magazine, Newspaper or Journal regardless of data source, when the record contains an ISSN/EISSN.

   Primo VE was developed in 2017 with a "Search Inside" feature, originally appearing only on Journal type records. In 2019 when CDI was developed Newspaper and Magazine types were added to the discovery environment.
   Unfortunately It appears that Ex Libris forgot to consider local records holistically, despite that Newspaper is an out-of-the-box configured type for Alma in Primo VE and many of their customers offer a blended search experience for their patrons.
   This is evidenced in an inconsistency that Search Inside displays on Newspaper records from CDI and fails to display on Newspaper records for local records. It will also… more

   1 vote

   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 Interface  ·  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. Add a uniqueness comparison check for local fields in a dedup record, and only display one instance of a non-unique field

   It became possible in November 2024 to display instances of a local field from all records in a Dedup record in Primo VE (Configuration > Discovery > Other > Local fields to display from all dedup members).
   The feature displays up to 10 instances of a field from records in the dedup group.
   This is a useful and welcome development to ensure patrons have access to all the metadata of the work.
   However, there is an issue that the data displays regardless if it is exactly the same in multiple records, despite that there is no usefulness for a patron to display the exact same data more than once, and it looks like an error to do so.
   Unfortunately Ex Libris has advised this is “expected” from the perspective that they have not developed this feature to do a comparison check to prevent multiple instances of display when the data in a field is exactly the same in multiple records dedup’d.
   Note: This is not an issue in Primo BO, where only one field displays when the content is not unique.
   This submission is for Primo VE to perform a uniqueness comparison check and only display one instance of the local field in a dedup record if the metadata is exactly the same.

   It became possible in November 2024 to display instances of a local field from all records in a Dedup record in Primo VE (Configuration > Discovery > Other > Local fields to display from all dedup members).
   The feature displays up to 10 instances of a field from records in the dedup group.
   This is a useful and welcome development to ensure patrons have access to all the metadata of the work.
   However, there is an issue that the data displays regardless if it is exactly the same in multiple records, despite that there is no usefulness for a patron… more

   1 vote

   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 Interface  ·  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 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 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. Converting Greek letters in queries for local materials

   When queries include Greek letters with diacritics, the retrieval omits many local records, as there is no conversion in Primo VE between letters with or without diacritics, or with different diacritics.

   Example:
   Searching ἄγω or αγω gives different results. CDI records are retrieved regardless, while local records can only be retrieved in the exact manner they were cataloged.

   Using a blended search (local+CDI) can confuse patrons, as it may lead them to believe the library does not have certain materials. Using a local search scope, patrons sometimes receive zero results, so many records are hidden from them.

   Greek is not only a modern language. It is a fundamental ancient language used in classical studies in many academic institutions. Therefore, the omission of the libraries' collections/items must be corrected.

   We request the addition of a conversion between characters for Greek, so that results can be retrieved regardless of whether you search with or without diacritics, and whether a record came from a local catalog or CDI.

   The attached file is an offered conversion table. Each color represents one letter, so all characters in that color should retrieve the same results.

   When queries include Greek letters with diacritics, the retrieval omits many local records, as there is no conversion in Primo VE between letters with or without diacritics, or with different diacritics.

   Example:
   Searching ἄγω or αγω gives different results. CDI records are retrieved regardless, while local records can only be retrieved in the exact manner they were cataloged.

   Using a blended search (local+CDI) can confuse patrons, as it may lead them to believe the library does not have certain materials. Using a local search scope, patrons sometimes receive zero results, so many records are hidden from them.

   Greek is not… more

   • 

   38 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  ·  Primo VE  ·  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. Fix Core Flaw: (VE / NDE) Holdings Configurations Must Apply to All Locations, including Temporary Locations

   Description:
   This request is being submitted at the direction of the support team, although it addresses a critical flaw in core functionality, not a new enhancement or feature.

   The flaw exists in Primo VE and Support will not confirm that the flaw will not be carried over into the Next Discovery Experience (NDE).

   Problem:
   Primo VE effectively ignores the configurations for holdings field display when an item is moved to a temporary location. Only the default holdings statement automatically generated from the item records is displayed. Due to other known issues, this auto-generated statement presents potentially inaccurate information to library patrons.

   Expected Outcome:
   The core function of a discovery system is to accurately reflect the library's holdings. We expect configurations for metadata display to apply to all items, regardless of whether they are in a temporary or permanent location. The launch of the NDE presents the ideal opportunity to correct this long-standing flaw, ensuring the new product is built correctly from the start and can offer a more reliable user experience than competing discovery platforms.

   References:

   Support Ticket: 07849390 (original) / 07956870 (cloned) - Inconsistent Holdings Display Configuration in Primo VE - Permanent vs. Temporary Locations

   Configuration Documentation: https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/Primo_VE_(English)/080Configuring_Delivery_Services_for_Primo_VE/Configuring_Holdings_Display_Fields_for_Primo_VE

   Description:
   This request is being submitted at the direction of the support team, although it addresses a critical flaw in core functionality, not a new enhancement or feature.

   The flaw exists in Primo VE and Support will not confirm that the flaw will not be carried over into the Next Discovery Experience (NDE).

   Problem:
   Primo VE effectively ignores the configurations for holdings field display when an item is moved to a temporary location. Only the default holdings statement automatically generated from the item records is displayed. Due to other known issues, this auto-generated statement presents potentially inaccurate information to library… more

   15 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  ·  Other  ·  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. Recommendation system for learning and research resources

    Academic libraries increasingly act as an ecosystem for learning and research resources. Therefore, they need a platform that can serve as an ecosystem to guide academic users.

    Target: Incorporate into Primo VE a recommendation system that, based on users' searches, gives recommendations at the resource level (e.g., article, book, book chapter, case study, image, thesis, etc.).

    Output: After the user searches, Primo VE provides a list of prioritized learning or research resources, sorted by their thematic relevance or visualisation-based popularity.

    Parameters: The recommendation system should match the query with the users' profile (e.g., career, under|postgraduate level, etc.) after they log into the system.

    Academic libraries increasingly act as an ecosystem for learning and research resources. Therefore, they need a platform that can serve as an ecosystem to guide academic users.

    Target: Incorporate into Primo VE a recommendation system that, based on users' searches, gives recommendations at the resource level (e.g., article, book, book chapter, case study, image, thesis, etc.).

    Output: After the user searches, Primo VE provides a list of prioritized learning or research resources, sorted by their thematic relevance or visualisation-based popularity.

    Parameters: The recommendation system should match the query with the users' profile (e.g., career, under|postgraduate level, etc.) after they log… more

    1 vote

    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  ·  Primo VE  ·  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. Add Shibboleth/SSO functionality to CDI "Link in Record" links

    Statista recently announced that they are ending IP authentication on Dec. 31, 2025. https://www.statista.com/site/IP-Access

    All of the CDI records for Statista are "Link in Record" links that rely on a proxy prefix. There is currently no way to configure settings for Shibboleth (or any other SSO client like OpenAthens) to make these types of links work. Please add this functionality, so we are all prepared if more vendors start moving in this direction. As it stands, we will have to deactivate the Statista collection at the end of the year if no new functionality is released. Thanks!

    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…)
    3 comments  ·  Integration with other systems  ·  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

12. Add an option to move the "Show more" link above the "Additional Services" link for "Display All Links in Full Display for CDI. "

    Current design: Additional services will appear before "Show more" link when "Display All Links in Full Display for CDI ." See the documentation here: https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/Primo_VE_(English)/030Primo_VE_User_Interface/Display_All_Links_in_Full_Display_for_CDI.

    Suggestion: add an option to change the order of the links,

    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  ·  Primo VE  ·  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

13. Allow Digital Viewer to use different View than Primo

    When viewing digital representations in the Digital Viewer, Alma-D uses the same Primo VE View; however, this can cause some difficulties when configurations ideal for Primo don't translate well to the Viewer.

    For example, we have a pop-up chat icon in Primo VE for patrons to chat with librarians; because this is configured in View, it's also present in the Digital Viewer, but the icon ends up obscuring parts of the representation's image and metadata.

    We'd like to be able to point the Digital Viewer to a different View entirely than the one Primo VE is currently using.

    5 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  ·  Other  ·  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

14. Instant Insight into FRBR Versions in the Search Results

    We have received feedback from our users that they would like to get an initial overview of a FRBR group’s contents directly in the results list. When encountering the representative record of a FRBR group, they want to immediately see how many online resources and physical copies are included, along with other useful details such as publication dates or resource types.
    A straightforward implementation could be to enhance the link to the versions list so that it not only shows the total number of versions but also indicates how many available online (consortia: only online resources that are available in the respective IZ / no viewit_other) and print resources are included. More advanced solutions could go further by displaying additional information about each version.
    We believe this enhancement would improve both the generic and the preferred FRBR display, as it would reduce unnecessary clicks and help users assess relevant resources more efficiently and even prevent users from overlooking relevant resources.

    We have received feedback from our users that they would like to get an initial overview of a FRBR group’s contents directly in the results list. When encountering the representative record of a FRBR group, they want to immediately see how many online resources and physical copies are included, along with other useful details such as publication dates or resource types.
    A straightforward implementation could be to enhance the link to the versions list so that it not only shows the total number of versions but also indicates how many available online (consortia: only online resources that are available in… more

    30 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 Interface  ·  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

15. Keywords entered should be carried over from the basic search field to the advanced search field

    In Primo NDE keywords entered should be carried over from the basic search field to the advanced search field as in Primo VE

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

    We will revisit this and will consider adding this to support user continuity

16. Improve Primo VE searching in non-roman script so definite article prefixes are appropriately counted as non-filing characters

    Arabic and Hebrew print titles beginning with the definite article prefix (like English "the") cannot be retrieved in Primo VE unless that initial definite article is included in the search. This is true even when the linked 880 with non-roman script has the number of nonfiling characters coded correctly in the subfield indicator in the bibliographic record

    Example:

    245 13$6880-02 $aal-Mabānī al-Kanʻānīyah fī Filasṭīn / $cNimr Sirḥān.
    880 12$6245-02/(3/r $aالمباني الكنعانية في فلسطين / $cنمر سرحان.

    Without the initial definite article, the search comes up empty or retrieves only records from the CDI, but not the sought print materials present in our Alma IZ.

    Arabic and Hebrew print titles beginning with the definite article prefix (like English "the") cannot be retrieved in Primo VE unless that initial definite article is included in the search. This is true even when the linked 880 with non-roman script has the number of nonfiling characters coded correctly in the subfield indicator in the bibliographic record

    Example:

    245 13$6880-02 $aal-Mabānī al-Kanʻānīyah fī Filasṭīn / $cNimr Sirḥān.
    880 12$6245-02/(3/r $aالمباني الكنعانية في فلسطين / $cنمر سرحان.

    Without the initial definite article, the search comes up empty or retrieves only records from the CDI, but not the sought print materials present… more

    25 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  ·  Primo VE  ·  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

17. Discovery collections per library and unfiltered view

    In our consortium we have some mixed IZs, which means different libraries, mostly in the same geographical area, that are part of the same IZ.
    Users accessing via the local library interface are interested mainly in that specific library Discovery collection. But at the same time they might be also interested to know if a resource is available in the near by libraries, as it could be easily accessible physically or to request it.
    We have activated the relevant configurations and Discovery collections displays correctly for the specific libraries only. But when the view is filtered and "Local copy unavailable" displayed, the user might overlook that there is the item near by and that it can be requested.
    We would like to have a configuration that keeps the get it section display as it is per default (with the "view _ to _ libraries _ for _ collection _ discovery" parameter turned to false), but at the same time displays the collections only for the relevant libraries (as we have when "view _ to _ libraries _ for _ collection _ discovery" parameter is set to true).

    In our consortium we have some mixed IZs, which means different libraries, mostly in the same geographical area, that are part of the same IZ.
    Users accessing via the local library interface are interested mainly in that specific library Discovery collection. But at the same time they might be also interested to know if a resource is available in the near by libraries, as it could be easily accessible physically or to request it.
    We have activated the relevant configurations and Discovery collections displays correctly for the specific libraries only. But when the view is filtered and "Local copy unavailable"… more

    28 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  ·  Primo VE  ·  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

18. Person entity - add an option for users to request more information about a person

    Many Person Info Cards have little/no information. An option for users to request more information about a person would give user communities agency to prioritize authority work by information professionals.

    5 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  ·  Primo VE  ·  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

19. Person entity - add an expandable text option that can be customized by institution

    Add an option to add explanatory text to the Person Info Card and Person Page, so that institutions can provide users with more details about these features in the interface. Transparency around the data presented by libraries in discovery interfaces is increasingly important with the proliferation of ai-generated content and users' understandable lack of trust.

    6 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  ·  Primo VE  ·  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

20. search profile slot drag and drop

    Like many other Primo VE libraries, we have a single search profile slot (Everything) with a lot of difference search profiles (105 in total). Whenever a new search profile is created, it will be at the bottom and since you can only move item by clicking up & down each times, for libraries that have a lots of profiles, it is a nightmare. Imaging moving just 1 item to the top will take 105 clicks. It would be very helpful if it can be drag & drop instead to change position of an item on the list.

    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  ·  Primo VE  ·  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