390 results found

1. Primo VE - Linked open data person entity - option to display additional authority record fields

   We contribute to the Library of Congress Names Authority and add associated group fields (MARC 373) with iwi affiliations for Māori authors and creators. Currently this field is not displayed in Person entity cards. Could this and other authority data be made configurable for display?

   60 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   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

2. Calculate and display physical availability on brief display for CDI records

   For Primo VE/NDE, please calculate and display the physical availability on the brief display for CDI records.

   Currently, in the results page, many records that are print plus online show only their online holdings in the results page for the brief records.

   When a user opens one of these records, only then are the physical holdings calculated and displayed. Then when the user goes back to the results page, the physical holdings are now displayed in the brief record, but only after they have viewed the full record, not before.

   This is an inconsistent user experience which is likely to cause confusion.

   Consistently displaying the physical availability alongside the online availability on the initial results page at the brief record level, instead of only the online availability, would create a more consistent user experience as users review potential relevant records.

   Thanks for considering. Sandra.

   For Primo VE/NDE, please calculate and display the physical availability on the brief display for CDI records.

   Currently, in the results page, many records that are print plus online show only their online holdings in the results page for the brief records.

   When a user opens one of these records, only then are the physical holdings calculated and displayed. Then when the user goes back to the results page, the physical holdings are now displayed in the brief record, but only after they have viewed the full record, not before.

   This is an inconsistent user experience which is likely to… more

   40 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  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 configuring default view (List vs Thumbnail) in Collection Discovery

   SUMMARY

   The default Thumbnail view does not support effective browsing for text-based collections in Primo NDE.

   Currently, libraries cannot configure the default display mode (Thumbnail view vs. Detailed/List view) for Collection Discovery pages. We request the ability to define List view as the default, or to configure this per view or collection.

   PROBLEM: THUMBNAILS DO NOT SUPPORT TEXT-BASED COLLECTIONS

   Thumbnail view prioritizes visual browsing, but many collections do not contain meaningful or distinctive visual material.

   This applies in particular to:
   - Student theses
   - Scholarly publications
   - Institutional repository content

   Thumbnails are often missing, non-informative (for example showing the first page of a PDF), or highly similar across records.

   As a result, the interface shows very limited metadata, often only the title. Important information for selection and comparison is not visible, such as:
   - Publication year
   - Availability status (open access, embargo, or restricted)
   - Abstract or summary
   - Author information

   This makes browsing inefficient and forces users to open multiple records to find relevant items.

   USER STORIES: METADATA-DRIVEN DISCOVERY

   1. Student (exploratory browsing)
      As a student exploring theses or scholarly publications, I want to quickly scan metadata such as year, topic and availability, so that I can identify useful examples without opening each item.

   2. Academic staff
      As an academic staff member reviewing output, I want to see structured information (year, title, supervisor, completeness) directly in the results list, so that I can efficiently assess coverage and quality.

   3. Researcher
      As a researcher browsing a publication collection, I want to compare items using metadata, so that I can identify relevant materials without relying on visual cues.

   USE CASE: CURRENT VS DESIRED BEHAVIOUR

   A user opens a thesis or publication collection in Primo NDE.

   In the current Thumbnail view:
   - Only titles are clearly visible
   - Thumbnails are absent or not meaningful
   - Key metadata is hidden
   - The user must open multiple records

   In a Detailed/List view:
   - Multiple metadata elements are immediately visible
   - Users can scan and compare efficiently
   - Fewer clicks are required
   - The browsing experience matches the content type

   PROPOSED SOLUTION

   • Allow configuration of the default display mode for Collection Discovery (Thumbnail view or List view)
   • Allow configuration per collection or per view, so institutions can match the view to the content type (e.g. images vs text-based collections)

   This flexibility would significantly improve usability and reduce the need for local customizations.

   SUMMARY

   The default Thumbnail view does not support effective browsing for text-based collections in Primo NDE.

   Currently, libraries cannot configure the default display mode (Thumbnail view vs. Detailed/List view) for Collection Discovery pages. We request the ability to define List view as the default, or to configure this per view or collection.

   PROBLEM: THUMBNAILS DO NOT SUPPORT TEXT-BASED COLLECTIONS

   Thumbnail view prioritizes visual browsing, but many collections do not contain meaningful or distinctive visual material.

   This applies in particular to:
   - Student theses
   - Scholarly publications
   - Institutional repository content

   Thumbnails are often missing, non-informative (for example showing the first… more

   •  

   31 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  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. 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

   83 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  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. Make MyInstitution configurable: allow excluding specific record sets

   SUMMARY

   Libraries cannot currently exclude specific record sets from the out-of-the-box MyInstitution scope in Primo VE / NDE.

   PROBLEM

   MyInstitution (and derived profiles such as MyInstandCI) is a fixed, all-inclusive scope that cannot be modified.

   This makes it impossible to centrally exclude a specific set of records (e.g. a whole digital collection) across all search profiles and views.

   The recommended workaround is to create custom scopes and search profiles (e.g. “MyInstitution minus X”). However, this:

   • Requires duplicating and maintaining multiple configurations

   • Leads to inconsistent behaviour across tabs and profiles

   • Breaks existing permalinks that rely on the standard search profiles

   This last point is especially critical, as Ex Libris recommends permalinks for stable access and sharing. Replacing out-of-the-box profiles can result in links that no longer resolve correctly or display the intended content.

   PROPOSED SOLUTION

   Allow institutions to exclude specific record sets from MyInstitution, either either by configuration (e.g. based on metadata or collections) or by allowing controlled adjustments to the scope itself.

   For example:

   • Exclude records based on specific fields (e.g. MARC 990)

   • Subtract a defined collection or scope from MyInstitution

   • Apply global filters across all search profiles using MyInstitution

   BENEFIT

   This would enable consistent, scalable control over content visibility without breaking existing links, and remove the need for complex and fragile workarounds.

   SUMMARY

   Libraries cannot currently exclude specific record sets from the out-of-the-box MyInstitution scope in Primo VE / NDE.

   PROBLEM

   MyInstitution (and derived profiles such as MyInstandCI) is a fixed, all-inclusive scope that cannot be modified.

   This makes it impossible to centrally exclude a specific set of records (e.g. a whole digital collection) across all search profiles and views.

   The recommended workaround is to create custom scopes and search profiles (e.g. “MyInstitution minus X”). However, this:

   • Requires duplicating and maintaining multiple configurations

   • Leads to inconsistent behaviour across tabs and profiles

   • Breaks existing permalinks that rely on the standard search… more

   26 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  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. 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 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   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. 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

   44 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   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. 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.

   56 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   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

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

   90 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  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. Primo NDE - Display Availability and Access Rights Indicators on Brief Result Cards in Collection Discovery

    User Story:
    As a library user browsing digital collections,
    I would like to see availability statuses and access rights indicators (e.g., "Open Access", or a restricted access icon) directly on the brief result cards (thumbnail and list views) in the Collection Discovery lobby,
    so that I know immediately if a digital file is accessible to me without having to click through to the Full Record Display.

    Current Problem:
    Currently, brief result cards for Alma-D records in Collection Discovery lack any visual indicators regarding an item's availability. Users frequently click on items only to discover they do not have the rights to view the content because it is closed or under embargo.

    This limitation creates a frustrating user experience filled with unnecessary clicks and dead ends. While Ex Libris Support suggested adding a general disclaimer to the collection description (e.g., "Please note not all items are available"), this does not solve the navigation friction at the individual item level.

    Proposed Solution:
    Please introduce a configuration option in Alma/Primo NDE that allows institutions to display availability statuses and access rights indicators directly on the brief result cards within the Collection Discovery interface. Bringing this visibility forward to the first point of contact will significantly streamline the user journey.

    User Story:
    As a library user browsing digital collections,
    I would like to see availability statuses and access rights indicators (e.g., "Open Access", or a restricted access icon) directly on the brief result cards (thumbnail and list views) in the Collection Discovery lobby,
    so that I know immediately if a digital file is accessible to me without having to click through to the Full Record Display.

    Current Problem:
    Currently, brief result cards for Alma-D records in Collection Discovery lack any visual indicators regarding an item's availability. Users frequently click on items only to discover they do not have the rights… more

    •  

    •  

    28 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  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. 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 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  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. 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

    •  

    42 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    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

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

    61 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    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

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

    • 

    38 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  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. Primo VE - Advanced search on multiple languages

    Add Language to the list of indexes available for use in the Search Field dropdown list for advanced search. This would allow multiple languages to be searched for, for example, English AND Samoan

    6 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    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 provide a job forcing a reindex recalculating also FRBR / View all versions grouping for a set of records or the whole catalogue

    Sometimes wrong FRBR grouping are created and stay in the system until the scheduled six months indexing is performed.

    There is a tool for fixing single records ( Dedup and FRBR Test Utility ) but a) it works for one record at time b) one needs to know exactly and in advance what records are wrong (and usually this is not the case).

    We need therefore a job forcing a reindex and recalculating Dedup + FRBR / View all versions grouping for a set of records or the whole catalogue.

    9 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    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

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

    27 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    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. Ability to sort/filter according to item status

    Ability to sort/filter according to item status

    The display order of item records in Primo is the same order in which they appear on the Alma record. Although we can sort them within Alma according to Library/Location, from a user perspective it would be helpful if they had the ability to apply a filter/sort to see first only the itens that are available to borrow

    11 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    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

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

    59 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    4 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. 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 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    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