365 results found

1. Improving Pick Up Location Logic in Primo NDE

   Purpose:

   To reduce incorrect deliveries, avoid patron frustration, and create a smoother, more intuitive request workflow by improving how pick up locations are ordered and saved in Primo NDE.

   ---

   1. Organisation-Level Improvement: Custom Default Sorting of Pick Up Locations

   Current Issue

   In the current setup, the pick up location list is presented alphabetically/historical by default. This can place small or rarely used locations at the top of the list, even when they are not relevant for most patrons.
   This increases the risk of accidental selection and leads to unnecessary delivery errors.

   Proposal:

   Within Primo NDE, the institution should be able to:

   • Define its preferred default pick up location
   • Specify the initial sort order for the full location list
   • Override alphabetical/historical sorting where it does not align with operational needs

   Goal:

   Ensure that the institution's most relevant and commonly used pick up location appears first, thereby reducing mistakes and improving the patron experience.

   ---

   1. Patron-Level Improvement: Personal Preferred Pick Up Location

   Current Issue

   Patrons currently cannot save a personal, preferred pick up location in their account settings. This forces them to select a pick up location repeatedly - increasing the chances of choosing the wrong one.

   Proposal

   As part of Primo NDE, patrons should be able to:
   • Select and save a personal favourite pick up location when logged in
   • Have this preference automatically preselected for future requests
   • Change their preferred location at any time

   Goal

   Provide a personalised and efficient workflow that supports patron needs and reduces errors caused by repeated manual selection.

   ---

   Next Step

   We request approval to include these two improvements in our Primo NDE configuration agenda. Together, they will enhance usability, reduce incorrect deliveries, and strengthen overall patron satisfaction.

   Final Note:

   This proposal aligns closely with an existing community request on the Ex Libris Ideas Exchange:
   “Define preferred pickup location in Personal Details”
   https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/44908411

   This demonstrates that many institutions experience the same challenge, and that we are not alone in requesting these improvements and indicates broader interest and shared benefits, and suggests that our needs are well understood in the community

   Purpose:

   To reduce incorrect deliveries, avoid patron frustration, and create a smoother, more intuitive request workflow by improving how pick up locations are ordered and saved in Primo NDE.

   ---

   1. Organisation-Level Improvement: Custom Default Sorting of Pick Up Locations

   Current Issue

   In the current setup, the pick up location list is presented alphabetically/historical by default. This can place small or rarely used locations at the top of the list, even when they are not relevant for most patrons.
   This increases the risk of accidental selection and leads to unnecessary delivery errors.

   Proposal:

   Within Primo NDE, the institution should be able to:

   … more

   77 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

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

   •  

   •  

   115 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  ·  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. Allow customisation of BibTex data export

   Currently, the BibTex data export from the full record review is non-customisable, no changes can be made to how the fields display in the exported data. This differs, for example, from other formats such as RIS and EndNote, which do have a mapping table in the configuration.

   The issues we’ve encountered with this are:

   1) Some fields have a custom display that we’d like to show on Primo but not in the exported data – e.g. we include author details in the Title display, but it is incorrect for this to show in the BibTex title field

   2) Where we have custom resource types on Primo, these are not read at all by BibTex and come up as “@unknown”entry types

   The lack of mapping options for this feature is causing significant issues for our users who need to use this referencing platform for their course. At our institution this includes Mathematics, Computer Science and Physics students, with one academic estimating that it could impact circa 650 students for the modules he is responsible for alone.

   Any workarounds for it are limited and would involve fundamental changes to configuration in Primo VE, such as stopping using custom resource types at all.

   It would be massively beneficial if we could define a custom mapping for this export, such as being able to map our own resource types onto the BibTex entry types, or control how each BibTex field is populated using fields in the PNX or Marc.

   Currently, the BibTex data export from the full record review is non-customisable, no changes can be made to how the fields display in the exported data. This differs, for example, from other formats such as RIS and EndNote, which do have a mapping table in the configuration.

   The issues we’ve encountered with this are:

   1) Some fields have a custom display that we’d like to show on Primo but not in the exported data – e.g. we include author details in the Title display, but it is incorrect for this to show in the BibTex title field

   2) Where we… more

   41 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

4. Ability to boost Ranking of Search Results in Primo VE based on accessibility

   Some of our consortium libraries would like the ability to boost the ranking of books that readers can request from libraries.
   Currently, the Ranking Configuration page enables you to configure various aspects of the ranking algorithm based on Field Boosting, Date Boosting, Resource type Boosting, Institution Boosting, but not on accessibility.

   87 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

5. Allow users to customize PNX addata subfields

   Currently, the normalization rules for creating addata subfields are not available to users. As a result, redundant information is included in subfields intended for authors, creators or titles and as result the citations are inaccurate.

   82 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

6. My Library Card: date of the last renewal

   We suggest that the "Date of the last Renewal" field should only update when a successful renewal happens, rather than when the courtesy letter is sent.

   It happens in local loan and in Rapido, and it is confusing for patrons. We would like this workflow was adjusted.

   42 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

7. Improve advanced searching in non-Roman languages so a "Title" + "Starts with" search parameter queries the MARC 880 field

   When combined, the “Title” + “Starts with” advanced search parameters do not query the linked MARC 880 field. This prevents users from successfully using this index for non-Roman language search queries.

   When the ExLibiris Development Team reviewed this issue previously, they found that Primo VE's design excludes the 880 field from Title Starts With indexing due to index size limitations.

   We’ve been advised that “Title Contains” and “Title is Exact” do index the 880 field, and can serve as a workaround. However, users expect consistent search behavior across all indexes, regardless of language used in the search query.

   A few examples:
   1. Title: Война и мир (catalog record)
   Search term (first title word): Война

   1. Title: רחוב העצב החד־סיטרי (catalog record)
      Search term (first title word): רחוב

   2. Title: گلستان سعدى : مع فرهنگ (catalog record)
      Search term (first title word): گلستان

   When combined, the “Title” + “Starts with” advanced search parameters do not query the linked MARC 880 field. This prevents users from successfully using this index for non-Roman language search queries.

   When the ExLibiris Development Team reviewed this issue previously, they found that Primo VE's design excludes the 880 field from Title Starts With indexing due to index size limitations.

   We’ve been advised that “Title Contains” and “Title is Exact” do index the 880 field, and can serve as a workaround. However, users expect consistent search behavior across all indexes, regardless of language used in the search query.

   A few… more

   60 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

8. Display campus in Primo VE for unsuppressed e-Collections and databases

   In the consortial environment, we would like to take advantage of the new functionality of central NZ-activation (network zone) of e-collections working with IMGrs (inventory management groups). We have some institutions (not all IZs) which would like to work with IMGrs, some not, those who do, some do use campuses others do not.

   We would like to see in Primo VE the distinction per campus also for databases and for non-suppressed e-collections (if used), as it works for portfolios so to better guide the end-user which collection would be the one to use.

   If an IZ uses IMGr in Alma which are applied to campuses/library to distribute access for their e-collections, or if e-collections are centrally activated in the NZ, with IMGr, i.e. if a database or e-collection with portfolios in a consortial environment are centrally activated, and the e-collections are then visible in the Primo VE of the IZ, we would like to have an option which allows to display separately per campus the unsuppressed e-collections and databases in Primo VE. This should also be possible in the future NDE.

   Display of portfolios per campus must stay as today, i.e. display per campus, and be valid for portfolios of suppressed or unsuppressed e-collections.
   Please note that several Idea Exchanges on the topic was already brought up, but many of these Idea Exchanges were not retained due to lack of votes.

   This Idea Exchange is addressed in particular to consortial architectures who work with the new functionality to centrally activate e-collections and apply IMGrs to these in the NZ. Yet the feature of campus display for unsuppressed e-collections should be available also for e-collections which are not IZ activated.

   An idea for expected display and relevant status quo can be found in the attached file.

   In the consortial environment, we would like to take advantage of the new functionality of central NZ-activation (network zone) of e-collections working with IMGrs (inventory management groups). We have some institutions (not all IZs) which would like to work with IMGrs, some not, those who do, some do use campuses others do not.

   We would like to see in Primo VE the distinction per campus also for databases and for non-suppressed e-collections (if used), as it works for portfolios so to better guide the end-user which collection would be the one to use.

   If an IZ uses IMGr in Alma… more

   • 

   33 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. Include DOIs in references in APA 7th ed. format for records coded with Dublin Core.

   Exlibris has just updated the APA 7th ed. citation format settings to include the DOI for MARC21-encoded records (idea exchange: Improve APA citation format to include the DOI for an article), but we also want Exlibris performs the same process for Dublin Core-encoded records.

   Users are increasingly turning to PRIMO to obtain the citation reference of a record they are interested in and in many cases their metadata is in DublinCore format, as more and more catalogs integrate repositories that encode information following this format.

   101 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

10. Purchase requests just in top menu (not in Get it section)

    We would like to suggest an option to offer the blank Purchase Request form in the Top Menu, while preventing the "Purchase Request" link from appearing in the "Get It" section of the record view.

    We want to avoid patrons requesting materials that we already hold or that can be obtained through resource sharing (Rapido).

    Currently, there is no configuration to separate these two access points. We tried using GES (General Electronic Services) logic, but it does not work for this specific purpose in Primo VE. The only workaround we found is hiding the link in the record view using CSS, which is not a robust solution.

    We suggest adding a native configuration to display the link only in the Main Menu.

    We would like to suggest an option to offer the blank Purchase Request form in the Top Menu, while preventing the "Purchase Request" link from appearing in the "Get It" section of the record view.

    We want to avoid patrons requesting materials that we already hold or that can be obtained through resource sharing (Rapido).

    Currently, there is no configuration to separate these two access points. We tried using GES (General Electronic Services) logic, but it does not work for this specific purpose in Primo VE. The only workaround we found is hiding the link in the record view using… more

    22 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

11. Display tag for Open Educational Resources for CZ and IZ records in Primo

    Open Educational Resources tags in CDI records are clearly displayed in Primo VE (e.g. Pressbooks titles). I would like to see this tag extended to include CZ and IZ records for open educational resources in a similar way to how we make the Open Access icon display in Primo.

    24 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

12. Allow an institution (IZ) (Alma/Primo VE) to exclude in retrieval 7XX fields with $5 from another institution within the same Network Zone

    In our Network Zone, we work with unique bibliographic records shared by several institutions. The MARC21 7XX subfield $5
    is used to indicate local information specific to each IZ.

    Currently, in Alma and Primo VE searches, 7XX fields containing a $5 from other IZs are included in retrieval and affect
    the Dedup and FRBR grouping processes within an IZ. We can only hide these fields from user display by configuring Primo VE rules.
    As a result, records retrieved in a Primo VE view of one IZ may include data that are strictly local to another institution and may
    even influence FRBR version grouping, producing less relevant or confusing results for users.

    Requested Enhancement:
    We request the addition of a configuration option (at the IZ and/or NZ level) that allows:
    Excluding from search indexing and deduplication/FRBR logic any 7XX fields whose $5 does not correspond to the specific IZ, or
    At least preventing such fields from being used in retrieval and grouping criteria, while maintaining their local character.

    Benefit:
    This enhancement would respect the cataloging meaning of subfield $5, increase result relevance for each institution, and reduce undesired
    effects in the presentation of versions in Primo VE.

    In our Network Zone, we work with unique bibliographic records shared by several institutions. The MARC21 7XX subfield $5
    is used to indicate local information specific to each IZ.

    Currently, in Alma and Primo VE searches, 7XX fields containing a $5 from other IZs are included in retrieval and affect
    the Dedup and FRBR grouping processes within an IZ. We can only hide these fields from user display by configuring Primo VE rules.
    As a result, records retrieved in a Primo VE view of one IZ may include data that are strictly local to another institution and may
    even influence… 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  ·  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

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

    55 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

14. Put search/feedback links in logical order on mobile menu - NDE

    In NDE on small screens, the Advanced Search, Feedback (Report a problem) and Ask Anything (natural language search) links appear in the menu in that order - see screenshot attached.

    At minimum, the two search options should be adjacent, and in the order they appear on full screen. The feedback/report a problem should not be in the middle of them, as it is a completely different type of function.

    Some institutions may even wish to relocate the feedback option to the bottom of the top menu links.

    The original case response was to log here on the idea exchange, as there is no plan to address this.

    In NDE on small screens, the Advanced Search, Feedback (Report a problem) and Ask Anything (natural language search) links appear in the menu in that order - see screenshot attached.

    At minimum, the two search options should be adjacent, and in the order they appear on full screen. The feedback/report a problem should not be in the middle of them, as it is a completely different type of function.

    Some institutions may even wish to relocate the feedback option to the bottom of the top menu links.

    The original case response was to log here on the idea exchange, as… more

    •  

    24 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

15. Search should be more forgiving of spelling errors/incorrect searches

    We would like the search in Primo VE to be more forgiving in terms of spelling mistakes and incorrect searches, akin to other search engines, as this is what our users are mostly familiar with. For example, searching “Das Leid des jungen Werter” instead of “Die Leiden des jungen Werther” will find the searched for title on Google, Amazon as well as a local bookshops online platform, while on Primo VE, the book itself, of which we have several versions in our catalogue, is not found at all and only some related literature is shown. Another example would be “The count of Monte Christo”. Searching for “The count of montecristo” or “The count of monetchristo” will only bring up partially related literature. Again, other platforms will easily find the correct title.

    We would like the search in Primo VE to be more forgiving in terms of spelling mistakes and incorrect searches, akin to other search engines, as this is what our users are mostly familiar with. For example, searching “Das Leid des jungen Werter” instead of “Die Leiden des jungen Werther” will find the searched for title on Google, Amazon as well as a local bookshops online platform, while on Primo VE, the book itself, of which we have several versions in our catalogue, is not found at all and only some related literature is shown. Another example would be “The… more

    100 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  ·  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

16. NZ/IZ linking in consortia

    Background: MARC 776 is used to establish a link between related records (Also available in another form:). If a link cannot be established, a title search is started instead.

    In a consortial environment, there is an issue with this: Primo VE is only able to establish a link if both the linking and the linked-to title are available locally. This happens because Primo depends on Alma functionality for related records to establish a link and Alma is building them within institution scope only (Network is considered just another institution in this regard). This means that as soon as only the linking title is available in an IZ, a title search will be started.

    To give an example: We have a journal with the main title “Recht” (Law), which links to an electronic version of the same title. In IZ that do not have the electronic version, a title search for Recht/law will be started instead, leading to over 27’000 results – from a link that promised to lead to a different version of the same title. See also pdf below.

    This behaviour makes 776 largely unusable for consortia, where it would be important for that our patrons are able to find resources that are not available locally as well or where we’d at least want a system that can recognize if something is locally available and only displays the link in this case.

    Background: MARC 776 is used to establish a link between related records (Also available in another form:). If a link cannot be established, a title search is started instead.

    In a consortial environment, there is an issue with this: Primo VE is only able to establish a link if both the linking and the linked-to title are available locally. This happens because Primo depends on Alma functionality for related records to establish a link and Alma is building them within institution scope only (Network is considered just another institution in this regard). This means that as soon as only the… more

    • 

    145 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

17. Available online in Research assistant as default.

    It would be beneficial to be able to make what is under the refinement icon in the search box more visible. It would be even better if we could make the "Available online" button be checked by default.

    As it is now it is so hidden that users aren't aware that this is a possible feature. The fact that the user needs to select the refinement icon to see this possibility isn't optimal.

    58 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  ·  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. Open Access Indicator for Unimarc records

    Open Access Indication in Primo VE is currently supported for Marc21 and Dublin records : https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/Primo_VE_(English)/030Primo_VE_User_Interface/Open_Access_Indication_in_Primo_VE
    Please support Unimarc record, too !

    134 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. Ability to Configure Multiple Journal Searches

    Currently, Primo VE supports only one Journal Search configuration for an institution. While this works well for many institutions, some institutions oversee multiple libraries or campuses with distinct journal holdings (e.g., different licensing agreements, consortia memberships, or campus-specific subscriptions).

    We would like to request the ability to configure and offer multiple, separate Journal Searches within Primo VE.

    Each Journal Search should:

    • Be scoped independently (e.g., by IZ, NZ, or a specific library/campus)

    • Have customizable display labels and help text to clearly indicate which journal collection the search covers

    • Support direct linking to each Journal Search from library platforms

    Use Case:
    At multi-campus institutions, users often need to know which journals are available specifically through their home campus. Currently, this is difficult to implement since only one centralized Journal Search can be offered.

    Multiple Journal Searches would:

    • Reduce user confusion when different campuses/libraries have different subscriptions

    • Support institutions that are part of consortia but also maintain unique, local journal collections

    • Improve the patron experience by allowing clear pathways to the correct set of journals

    Impact:

    We believe this enhancement would significantly improve discoverability, align search results with basic Primo searches, reduce access confusion, and allow libraries to better serve diverse user groups with distinct e-resource entitlements.

    Currently, Primo VE supports only one Journal Search configuration for an institution. While this works well for many institutions, some institutions oversee multiple libraries or campuses with distinct journal holdings (e.g., different licensing agreements, consortia memberships, or campus-specific subscriptions).

    We would like to request the ability to configure and offer multiple, separate Journal Searches within Primo VE.

    Each Journal Search should:

    • Be scoped independently (e.g., by IZ, NZ, or a specific library/campus)

    • Have customizable display labels and help text to clearly indicate which journal collection the search covers

    • Support direct linking to each Journal Search from library platforms

    Use Case: … more

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