395 results found

1. Rank records within FRBR group by relevancy to search terms (not just highlight one preferred record)

   Description:

   This is a follow-up to a previously "completed" idea: "Relevancy sorting in FRBR version list display should use terms searched" (209 votes). That idea was addressed only for Preferred Record mode, by highlighting a single matching record at the top of the version list. We don't think this fully solves the underlying problem, in either display mode.

   The problem:

   A FRBR group can contain several records that are all relevant to the user's original search terms. For example, multiple translations by the same translator, or several relevant editions.

   In Generic mode, opening the group shows an unranked list of all versions. Relevant matches can be buried many pages deep, with no connection to the original search.

   In Preferred Record mode, the fix implemented only surfaces one matching record. This can make the problem less visible: a user sees one confidently displayed match and has no indication that 2-3 more equally (or slightly less) relevant versions exist inside the group. It looks solved, but the ranking problem is just hidden rather than fixed.

   Grouping records according to FRBR principles in general is good and something we want to keep recommending to our institutions. However, if it negatively affects users’ attempts to reach a known item or semi-known items by placing these unintuitive roadblocks in their way, it is not good enough. In many cases, the user would be better off if the search had never been FRBR’ized.

   The proposed solution:

   Rank/sort the records within the FRBR group itself by relevancy to the original search terms, in both Generic and Preferred Record display modes. That way, the user will immediately spot the relevant results after opening the FRBR group but will still enjoy the benefits of a less cluttered initial results list.

   Example:

   Searching "Iliad Richmond Lattimore" returns a FRBR group for Homer's Iliad. Opening the group should surface Richmond Lattimore's translations at or near the top based on its relevance to the search the user made, not require paging through many unrelated editions/translations to find them.

   We hope that you will vote for this suggestion! Feel free to add other examples in the comments below.

   -The BIBSYS-consortia

   Description:

   This is a follow-up to a previously "completed" idea: "Relevancy sorting in FRBR version list display should use terms searched" (209 votes). That idea was addressed only for Preferred Record mode, by highlighting a single matching record at the top of the version list. We don't think this fully solves the underlying problem, in either display mode.

   The problem:

   A FRBR group can contain several records that are all relevant to the user's original search terms. For example, multiple translations by the same translator, or several relevant editions.

   In Generic mode, opening the group shows an unranked list of… more

   176 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

2. DOI autofill on the Book Chapter request Resource Sharing form

   We would like a DOI autofill feature for Book Chapter requests on the stand-alone Resource Sharing form on Primo NDE.
   This already exists on the Article request RS form.

   3 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  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Hold and Booking Request Form Needs More Customization

   The Hold and Booking Request Form should have more customization options or branching logic to help libraries that have multiple branches.

   For example, we have a main library and three branch libraries that are all on the same Primo discovery (we also have a law library that is on their own Primo). Our main library branch got book lockers last year for our users so they can easily pick up their holdings. However, user services noticed that some patrons were struggling to access higher or lower lockers. They asked if we could have a check box on the holdings request form to indicate that they want a more accessible locker. However, we ended up finding a couple of issues with this request.

   1.) Due to the way the form is built, it is all or nothing. Our Fine Arts Library does not have lockers, so the check box appears when users select their library for book pickup, even though they don't have lockers. We worry that this will cause some confusion for both the users and the branch libraries (see image below). Ideally, the form should be able to change based on the chosen location.

   2.) The verbage from the check box appears along with additional comments made by the requester. When we receive the request, everything is jumbled into the request notes field, making it messy, and quite frankly, a little ugly. 😆 (see image below)

   If even one of these changes could be made, that would be amazing!

   The Hold and Booking Request Form should have more customization options or branching logic to help libraries that have multiple branches.

   For example, we have a main library and three branch libraries that are all on the same Primo discovery (we also have a law library that is on their own Primo). Our main library branch got book lockers last year for our users so they can easily pick up their holdings. However, user services noticed that some patrons were struggling to access higher or lower lockers. They asked if we could have a check box on the holdings request… more

   •  

   •  

   3 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. Improve Database material type assignment in a Network Zone Consortia

   Problem description

   In a Network Zone consortium, bibliographic records are shared across all member institutions. Currently, the "Database" material type in Primo VE is assigned to a bibliographic record whenever that record is linked as the descriptive/display record for any Electronic Collection with a populated Level URL. This includes Local Electronic Collections created by a single member institution in their own Institution Zone.

   Because the underlying bibliographic record is shared in the NZ, this single institution's local configuration choice changes the material type of the record for every institution in the consortium, even though only one institution actually intended the title to function as a database entry. This creates a situation where a shared title (e.g. a journal) can unexpectedly display under "databases" instead of its correct material type in another institution's discovery layer, with no clear explanation available to that institution.

   Impact

   Member institutions have no visibility or diagnostic tool to determine why a shared title unexpectedly displays with the wrong material type. A single institution's local Electronic Collection setup can silently override discovery behavior for the entire consortium, with no warning, log, or notification to affected institutions.

   Troubleshooting is currently difficult. Only the consortium's network administrators have a way to identify the source, but it requires checking every library that has the record in their IZ.

   Suggested improvement

   We would like Clarivate to investigate ways of making this behavior more transparent and manageable in an NZ consortium setting. One option would be through better visibility into cross-institution record usage, or some form of notification when a shared record's material type is affected by another institution's configuration. An even better solution would be to change the underlying approach to how the "Database" resource type is determined for shared NZ records in a way that would let each IZ control the behaviour in their own IZ. Such a solution would increase the customizability of the database list for each individual IZ without risking resource type contamination across the consortia.

   Problem description

   In a Network Zone consortium, bibliographic records are shared across all member institutions. Currently, the "Database" material type in Primo VE is assigned to a bibliographic record whenever that record is linked as the descriptive/display record for any Electronic Collection with a populated Level URL. This includes Local Electronic Collections created by a single member institution in their own Institution Zone.

   Because the underlying bibliographic record is shared in the NZ, this single institution's local configuration choice changes the material type of the record for every institution in the consortium, even though only one institution actually intended the… more

   147 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

5. show notice in GetIt when patron is blocked from requesting

   This is also CERV PENH-I-28495.

   Currently, users with item or global blocks can have their request permissions removed, and the physical and digital request buttons for local materials can be hidden (similar to Rapido for resource-sharing requests). Rapido allows users to communicate a reason why they might not be able to make a request. We believe we should display a similar HTML-based message/banner for requesting local materials, without needing interface customization.

   This follows the design principle of "instruction at the point of need". We have had patrons with blocks think that items are not requestable when they are, but just not to them. The goal is to encourage patrons to resolve their blocks, not just keep them from requesting more. Ideally, request buttons should be made inactive rather than hidden, as this would indicate the request status of the item/title while still communicating to the patron that there is an issue with their library account.

   This is also CERV PENH-I-28495.

   Currently, users with item or global blocks can have their request permissions removed, and the physical and digital request buttons for local materials can be hidden (similar to Rapido for resource-sharing requests). Rapido allows users to communicate a reason why they might not be able to make a request. We believe we should display a similar HTML-based message/banner for requesting local materials, without needing interface customization.

   This follows the design principle of "instruction at the point of need". We have had patrons with blocks think that items are not requestable when they are, but just… more

   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…)
   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. Priority of pickup locations

   We would like to have the possibility to set the order of pickup locations. Now the owning library is always on the first place. We would appriciate the possibility to put other pickup location at the firt place intead of the owning library e.g. the library box as the first possibility to pickup the resource.

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

7. NDE - Configuration option for whether a search is invoked on changing scope

   Currently, if there is text in the search input field and you make a selection in the scope drop-down, a search is invoked automatically (without the user selecting the search button).

   This even occurs on the Library Search home page (when no search has yet been performed).

   There is no indication to users that a search will be triggered after changing their selection in that drop-down.

   Compare this behaviour to the 'Browse' search, which has a drop-down for the search field - users can change that value as needed yet a new search will only be performed when they select the 'Search' button. This is the expected behaviour - where a form (such as this search form) is only submitted once the user selects to submit it, rather than it submitting when a single field within the form is changed.

   This was raised as an issue with Ex Libris, but they said it was the intended functionality.

   Given the inconsistency in user experience and lack of notification to the user that a new search will be performed, I think there should be a configuration option in the view to prevent the search being automatically invoked when the scope is changed.

   Currently, if there is text in the search input field and you make a selection in the scope drop-down, a search is invoked automatically (without the user selecting the search button).

   This even occurs on the Library Search home page (when no search has yet been performed).

   There is no indication to users that a search will be triggered after changing their selection in that drop-down.

   Compare this behaviour to the 'Browse' search, which has a drop-down for the search field - users can change that value as needed yet a new search will only be performed when they select… more

   • 

   7 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

8. NDE My Account Loans: Option to show more than 10

   In the previous UI for VE, users were able to load more of their loans when viewing their account. This list could then exported. In the NDE users are limited to viewing 10 loans at a time, thus they can only export 10 at a time. Either the loans list should be updated to allow the user to increase the number of loans viewable at a time (up to 50, similar to search results), or have an option to generate a list of loans either in the browser or as an export.

   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…)
   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. In Primo Research Assistant, please add the ability to pre-select filters. Specifically, we need to pre-select the available online filter.

   In Primo Research Assistant, please add the ability to pre-select filters. Specifically, we need to pre-select the available online filter. Our students are often frustrated when the results include resources that must be requested.

   1 vote

   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  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

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

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

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

    41 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

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

    32 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

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

    •  

    37 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. Provide confirmation when item has been added to a reading list

    In both Primo VE and Primo NDE, no confirmation is given to the user after adding a title to a reading list. The Add to Reading List box simply closes with no indication about what has occurred.

    Recommend adding a status message so that users are aware the item has been successfully added, avoiding uncertainty and potential repeated actions.

    3 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  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Option to have more than 5 results from Primo Research Assistant query

    In the current release of Primo Research Assistant, it provides the 5 most relevant results with an instant overview. Sometimes, a query returns more than five highly relevant results. Hopefully, the Research Assistant will offer users the option to view more than 5 results in the future.

    2 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

17. Re-design NDE Get it section

    Our suggestion (see attached file and image) is to re-design the get it section for the NDE, so that it become more compact and reduce the number of clicks needed to display all information.

    In this idea it remains fundamental that libraries can configure which information display and in which order, that is optimized also for mobiles, that it works well with journals and that "filter" by number or year option keep on working
    The status of the items could also be indicated using colors: for example, Item in Place in green, Out of Library in grey, ...

    Note: we did add also "loan" and "digitization" options at item level in this mockup, but we strongly believe that these should moved in the "Request" section.

    Our suggestion (see attached file and image) is to re-design the get it section for the NDE, so that it become more compact and reduce the number of clicks needed to display all information.

    In this idea it remains fundamental that libraries can configure which information display and in which order, that is optimized also for mobiles, that it works well with journals and that "filter" by number or year option keep on working
    The status of the items could also be indicated using colors: for example, Item in Place in green, Out of Library in grey, ...

    Note: we… more

    • 

    •  

    5 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

18. Change how the 541 holding field displays in Primo VE

    Primo VE users would benefit from improved readability of descriptive metadata in library records. Currently, MARC 541 fields display each subfield (such as c; a; d. on separate lines, which fragments the information and makes it harder to interpret.

    This proposal suggests enabling a configuration option in Primo VE to display the entire 541 field as a single, continuous line with appropriate punctuation between subfields. Presenting the field in this way would preserve the contextual relationships within the data, reduce visual clutter, and make acquisition and provenance information clearer and more accessible to users.

    •  

    2 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  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Suppress controlled vocabulary expansion notification when expansion has no impact on results

    When a search triggers controlled vocabulary expansion but the expansion term contributes zero results, Primo VE still displays the message informing the user that the search has been expanded, and offers a link to disable the expansion (conVoc=false).

    Clicking this link produces no observable change in the result set, since the expansion was not contributing any results in the first place.

    This creates a confusing experience for the user:
    1. The system implies the search was meaningfully expanded
    2. The user is offered the option to opt out
    3. Opting out has no visible effect

    Proposed improvement:
    The expansion notification and opt-out link should only be displayed when the controlled vocabulary expansion actually contributes results. If the expansion term returns zero results, the notification should be suppressed — or alternatively, the UI should clearly communicate that the expansion had no impact on the current result set.

    This would make the interface more transparent and trustworthy, and avoid users wondering whether the opt-out functionality is broken.

    When a search triggers controlled vocabulary expansion but the expansion term contributes zero results, Primo VE still displays the message informing the user that the search has been expanded, and offers a link to disable the expansion (conVoc=false).

    Clicking this link produces no observable change in the result set, since the expansion was not contributing any results in the first place.

    This creates a confusing experience for the user:
    1. The system implies the search was meaningfully expanded
    2. The user is offered the option to opt out
    3. Opting out has no visible effect

    Proposed improvement:
    The expansion notification… more

    3 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

20. Remove harvest date from CONTENTdm import profiles so it can be scheduled

    Currently, an import profile for CONTENTdm cannot be scheduled as there is a bug that prevents the job from running if the harvest date is populated. Please remove the harvest date input.

    1 vote

    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  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating