659 results found

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

   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

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

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

   49 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

5. 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!

   53 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

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

7. Sort Favorites by Call Number, Library & Location

   Patrons often use the Primo My Favorites function to build lists of titles that they want to retrieve from library stacks. Currently, the only sort options for these lists are Date Added, Title, and Author—none of which are particularly helpful for retrieval. Please consider expanding sort options to include Call Number, Library and Location?

   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…)
   0 comments  ·  User Functionality  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

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

   • 

   144 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

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

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

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

12. Allow view configuration to exclude retracted and withdrawn articles from results list

    The CDI Document Types labels and facets are valuable information. Now that we have that information, and the Document Types are also facets, can we please get the ability to set our discovery views to exclude these Retracted and Withdrawn articles (similarly to how we have the ability to set a view to exclude CDI ebook records)?

    I set up our custom primo search box widget on our library website to exclude these two resource types by default, and I locked those facets so they aren't lost on the next search. You can search the Combined Search box on our library site to try it out: https://www.normandale.edu/current-students/academic-resources/library/index.html

    But it's not a good work around. First, any time the user clicks on the New Search link in the menu, the facets are cleared. Second, when a user navigates from a CDI search to a local search (like our book search) or journal search the excluded facets are sticky in those searches too, even though they have no effect in those contexts. Also, by using the facet functionality to exclude these resource types, we are also in effect drawing extra attention to the existence of these unreliable sources in the library's collections.

    Although not a preferred solution because they would still be discoverable, I thought about possibly down boosting these two resource types. Currently, CDI document attributes are not boostable.

    The CDI Document Types labels and facets are valuable information. Now that we have that information, and the Document Types are also facets, can we please get the ability to set our discovery views to exclude these Retracted and Withdrawn articles (similarly to how we have the ability to set a view to exclude CDI ebook records)?

    I set up our custom primo search box widget on our library website to exclude these two resource types by default, and I locked those facets so they aren't lost on the next search. You can search the Combined Search box on our… more

    20 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  ·  Administrative Tools  ·  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. 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

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

15. Responsive label "item in place/not in place" for open shelf items

    Our available items in open rack cannot be requested for local pickup but this is confusing for patrons as there is a physical request button (only for a Transit request - the Owning Library is missing as pickup location). Only for items NOT in place and items in STACKS, the Owning Library is an additional Pickup location.

    As the option for local pickup for open shelf items depends on the availability and location (item in place/item not in place), we would like to change this label and add information about requestability and access to items (see image attached). But this status has to be mapped to the Holding Location (or item policy?), to distinguish between open shelf and stacks:

    • items in OPEN SHELF that are NOT available (on loan): requestable for local pickup and transit
    • items in OPEN SHELF that are available: only requestable for transit)
    • items in STACKS that are available/not available: requestable for local pickup and transit

    Is it possible to have a "responsive" status label, but only for items in open shelf?

    Our available items in open rack cannot be requested for local pickup but this is confusing for patrons as there is a physical request button (only for a Transit request - the Owning Library is missing as pickup location). Only for items NOT in place and items in STACKS, the Owning Library is an additional Pickup location.

    As the option for local pickup for open shelf items depends on the availability and location (item in place/item not in place), we would like to change this label and add information about requestability and access to items (see image attached). But this… more

    •  

    73 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

16. Primo VE : Alignment of Unimarc normalization rules with Marc21 normalization rules for the creation of the author facet

    The current OTB normalization rules for the creator/contributor facet in Primo VE differ between Marc21 and Unimarc records. Unimarc rules consider more elements than Marc21, leading to inconsistencies and duplicate facets for the same author.
    For example, from personal name fields (fields 70#), Exlibris uses the entry element, the part of name, the qualifier, Roman numerals and dates (a, b, c, d, f) for “Personal name” responsibility statements. In Marc 21, only the entry element is retained (a).

    Key Issues:

    1- Duplicate Facets: Two facets are created for the same author, one based on Unimarc and the other on Marc21.
    2- Search Inconsistencies: The facets do not filter search results uniformly, with Unimarc facets often limiting searches to printed documents and Marc21 facets refining searches for online resources.
    

    Proposed Solution:

    Align the Unimarc and Marc21 normalization rules to simplify the author facet. This pragmatic approach will improve search functionality until authority identifiers are widely adopted.

    Please refer to the attached document for more details and proposed modifications to the Unimarc standardization rules.
    Thank you in advance for any support you can give to this idea.

    Alexandre Faure
    Université de Bordeaux

    The current OTB normalization rules for the creator/contributor facet in Primo VE differ between Marc21 and Unimarc records. Unimarc rules consider more elements than Marc21, leading to inconsistencies and duplicate facets for the same author.
    For example, from personal name fields (fields 70#), Exlibris uses the entry element, the part of name, the qualifier, Roman numerals and dates (a, b, c, d, f) for “Personal name” responsibility statements. In Marc 21, only the entry element is retained (a).

    Key Issues:

    1- Duplicate Facets: Two facets are created for the same author, one based on Unimarc and the other on Marc21.

    … more

    • 

    73 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

17. Display ebook reading format (HTML, EPUB, PDF etc.) in Primo (VE) full display

    When displaying links to Ebook providers in Primo (VE) full display it would be suitable to have a notice of what ebook reading formats accessible for each provider. Instead of having to click further to the each provider to retrieve the information. Even information about online reading and/or download option would be suitable.

    44 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. Enable Custom Configuration of Primo Normalization Rules for Local Authority Search

    Current Situation: Local authority search records are currently displayed with hard-coded normalization rules (NRs).

    Proposed Change: Allow users to configure Primo normalization rules for local authority search. This flexibility will enable us to normalize authority records and display fields according to our specific needs.

    128 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…)
    6 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. ORCID iD Integration in Info Card for Contributor Page in Alma

    Background: In August, ExLibris implemented the Info Card feature for contributor pages in Alma, which appears under specific conditions related to linked authority records. This enhancement has significantly improved the visibility of contributor information.

    Current Conditions for Info Card Display:

    • A person is linked to an LC Names authority for a personal name.
    • A person is linked to a Name authority that exists in VIAF and can be linked to an LC Name authority for a personal name.
    • Information on the person exists in LC Names and Wikidata, with at least two fields containing information beyond the name of the person.
    • Wikidata cache is updated in Alma on a weekly basis.

    Enhancement Request: We propose an additional feature to further enrich the Info Card functionality. Specifically, we request that when an ORCID iD in the form of a URI is present in either the LC name authority record or Wikidata for the author, the following should occur:

    • Display the ORCID iD URI: The ORCID iD URI should be prominently displayed in the Info Card.
    • Make the ORCID iD URI Resolvable: The URI should be clickable and resolvable directly within the Info Card in both Alma and Primo.

    Benefits: Integrating ORCID iD URIs will enhance the discoverability of author contributions and facilitate seamless access to their research profiles, thereby improving the overall user experience.

    Thank you for considering this enhancement to the Info Card feature. We believe this addition will greatly benefit users and contribute to the ongoing development of Alma and Primo.

    Background: In August, ExLibris implemented the Info Card feature for contributor pages in Alma, which appears under specific conditions related to linked authority records. This enhancement has significantly improved the visibility of contributor information.

    Current Conditions for Info Card Display:

    • A person is linked to an LC Names authority for a personal name.
    • A person is linked to a Name authority that exists in VIAF and can be linked to an LC Name authority for a personal name.
    • Information on the person exists in LC Names and Wikidata, with at least two fields containing information beyond the name of the… more
    202 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  ·  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
    AdminAdina Marciano (Admin, Ex Libris) responded

    Thank you for the suggested idea. We see its value and will consider it in the future. This development requires integration with third-party providers, and we will need to investigate the possibility of this development.

20. Include subfield k from 245 in title index (important for manuscripts/archives)

    Subfield k of the 245 title field should always be indexed. Currently, it is only indexed when subfield a is absent. OCLC makes clear that both subfields may be used together: "Use subfield ǂk also to indicate "form" even if a formal title is given in subfields ǂa, ǂb, and ǂc." From: https://www.oclc.org/bibformats/en/2xx/245.html

    This subfield is important for manuscripts and archives. Examples from OCLC:

    245 ǂa Four years at Yale : ǂk diaries, ǂf 1903 September 16-1907 October 5

    245 ǂa The charity ball : ǂb a comedy in four acts : ǂk typescript, ǂf 1889 / ǂc by David Belasco and Henry C. DeMille

    Subfield k of the 245 title field should always be indexed. Currently, it is only indexed when subfield a is absent. OCLC makes clear that both subfields may be used together: "Use subfield ǂk also to indicate "form" even if a formal title is given in subfields ǂa, ǂb, and ǂc." From: https://www.oclc.org/bibformats/en/2xx/245.html

    This subfield is important for manuscripts and archives. Examples from OCLC:

    245 ǂa Four years at Yale : ǂk diaries, ǂf 1903 September 16-1907 October 5

    245 ǂa The charity ball : ǂb a comedy in four acts : ǂk typescript, ǂf 1889 / ǂc by David… 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