354 results found

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

2. Disabling automatically generated links for related records if the associated NR is disabled.

   Primo VE is capable to automatically create links to related records via MARC 7xx fields.
   As these links where not working well for us, we were looking to turn them off with a NR, by setting “set pnx."display"."relation" to "N/A"” for 776 specifically.
   Unfortunately, this turned out not to work in all cases. As Ex Libris explained this is because
   - in the related records, they differentiate between child records and parent records
   - for child records, as the specific relation field is included, Display NR takes effect
   - for parent records, as the specific relation field is not included, and the opposite link is added automatically, Display NR cannot have any effect

   This means we can only disable links from child to parent records but not the other way around. What we would like to see is that, if a relation from a child to a parent record is supressed, the automatically added opposite link should also be supressed.

   Primo VE is capable to automatically create links to related records via MARC 7xx fields.
   As these links where not working well for us, we were looking to turn them off with a NR, by setting “set pnx."display"."relation" to "N/A"” for 776 specifically.
   Unfortunately, this turned out not to work in all cases. As Ex Libris explained this is because
   - in the related records, they differentiate between child records and parent records
   - for child records, as the specific relation field is included, Display NR takes effect
   - for parent records, as the specific relation field is not included,… more

   90 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Primo VE  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

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

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

   Example:

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

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

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

   Example:

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

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

   25 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Primo VE  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Primo VE facet for collections regardless of inventory type

   I would like to propose an out of the box facet for collections that can include all 3 inventory types.

   We have users that need to be able to filter their search results by ‘collections’ or groupings that contain physical, electronic and digital resources. For example, our Original Materials ‘collection’ is made of physical items, digital items and electronic items that we have catalogued in local electronic collections.

   Currently, there are OOTB facets based on physical inventory (Library and Location) but none that combine all 3 inventory types.

   As a workaround, we have utilised the digital collection facet for this purpose. Although it is primarily used for digital records, it does support any type of record. However, this means that our Collection Discovery pages contain all of our collection items and some physical and electronic items without cover images or thumbnails. It also results in our Original Materials collection including 272,505 items instead of being used to showcase select resources as the functionality intended. We have to manually update these collections regularly as new items are catalogued.

   The creation of this facet type would improve collection discovery for uses by allowing libraries to create collections of resources regardless of inventory type.

   I would like to propose an out of the box facet for collections that can include all 3 inventory types.

   We have users that need to be able to filter their search results by ‘collections’ or groupings that contain physical, electronic and digital resources. For example, our Original Materials ‘collection’ is made of physical items, digital items and electronic items that we have catalogued in local electronic collections.

   Currently, there are OOTB facets based on physical inventory (Library and Location) but none that combine all 3 inventory types.

   As a workaround, we have utilised the digital collection facet for this… 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

5. Copy text from digital viewer

   When reading documents in the digital viewer, it would be nice to have the ability to copy text directly from the page. You can do this if you download the document. I was attempting to do this with a larger file that mentioned other reports I wanted copy the name of a report to view/search for in the catalogue; however, the digital viewer does not allow users to select text from the document.

   13 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   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. Add Due Date to Real Time Availability Status in Brief Records

   We would like to be able to see the status messages to include Due Dates, where applicable.
   Example: add date to Not available - Loan message, something along the lines of Not available - Checked out until {date}.

   8 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Primo VE  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Improved Display of Coverage Statements for Taylor and Francis Journals autoholdings collection.

   Taylor and Francis adds multiple coverage rows to reflect the different purchasing methods. For example, one line may represent perpetual access while another indicates current access. This is why some coverage statements appear to overlap.
   We propose to:
   1. Retain the purchase type (e.g., perpetual, current) for each coverage statement within Alma.
   2. Present only non-overlapping coverage statements to users in primo.
   This enhancement is planned as an upgrade to the current functionality, but there is no set release date as of now.
   To help expedite this enhancement, the support team suggested to open an idea exchange to encourage all users to vote for this idea. The votes can help prioritize this enhancement and contribute to improving user experience.

   Taylor and Francis adds multiple coverage rows to reflect the different purchasing methods. For example, one line may represent perpetual access while another indicates current access. This is why some coverage statements appear to overlap.
   We propose to:
   1. Retain the purchase type (e.g., perpetual, current) for each coverage statement within Alma.
   2. Present only non-overlapping coverage statements to users in primo.
   This enhancement is planned as an upgrade to the current functionality, but there is no set release date as of now.
   To help expedite this enhancement, the support team suggested to open an idea exchange to encourage all… more

   68 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

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

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

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

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

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

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

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

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

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

   If an IZ uses IMGr in Alma… more

   • 

   8 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Primo VE  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Do not show availability for CDI/Alma records with matching GTI ID

   Occasionally, CDI records will show availability for physical items (holdings/digitization offers via Rapido), and the physical records will show online availability. To our understanding, this is due to a matching GTI ID. We were informed in a SF case that it is currently not possible to resolve this. As this leads to confusion for our libraries (mainly digitization requests for an electronic resource) we would be glad if a solution could be found to no longer show these incorrect availabilities (or at least for the digitization requests to show the physical record they were actually placed on).
   Example: https://ubs.swisscovery.slsp.ch/permalink/41SLSP_UBS/giv3ks/cdi_askewsholts_vlebooks_9783540488491

   71 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   3 comments  ·  Primo VE  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Related titles in Primo VE records display: separate window

    When records have bib-to-bib relationships via 8XX (or 7XX), the list of related titles is displayed in the Details section of the series/host record. Unfortunately, the list is currently sorted alphabetically by the title, which is very user-unfriendly with a large number of linked titles.

    This behavior has already been criticized in this idea. Unfortunately, it is still not possible to sort the related titles logically by sequence or volume.

    The Austrian Library Association (OBV) uses Primo BO and has implemented a user-friendly solution for displaying related titles:
    In the case of multi-volume works and series, the individual volumes are displayed via a link in a separate window. There the volumes can be sorted by publication date, relevance etc.

    Example: Opere di Francesco de Sanctis, https://permalink.obvsg.at/AC01614297

    Austria is working with PLK fields for their solution. During the publishing process from Alma to Primo, the related records are added as PLK fields to the source record. For an example, please see here the source record for Opere.

    In Primo VE we would like to be able to add the relationships to the source data set, as it is the case in Primo BO with the PLK fields.

    When records have bib-to-bib relationships via 8XX (or 7XX), the list of related titles is displayed in the Details section of the series/host record. Unfortunately, the list is currently sorted alphabetically by the title, which is very user-unfriendly with a large number of linked titles.

    This behavior has already been criticized in this idea. Unfortunately, it is still not possible to sort the related titles logically by sequence or volume.

    The Austrian Library Association (OBV) uses Primo BO and has implemented a user-friendly solution for displaying related titles:
    In the case of multi-volume works and series, the individual volumes are… more

    •  

    146 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Primo VE  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Resource Recommender by user group or campus

    Resource Recommender in Primo VE can only show suggestions based on search tags or “Display Always.”
    There’s no way to show recommendations based on who the user is — for example, their user group, campus, or department.
    This means libraries can’t personalize results - such as:
    Business students see business databases

    This would make the discovery experience more relevant and user-friendly.

    7 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Primo VE  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Integrated Library Mapping and Analytics for Primo VE

    Develop an integrated library mapping module for Primo VE featuring interactive floor plans with clear, step-by-step directions. Seamlessly integrate this module into Primo VE's existing infrastructure, ensuring a user-friendly interface accessible to all patrons.

    Benefits:
    • Enhanced user experience: Streamline the path from digital search to physical item retrieval, reducing frustration and improving overall user satisfaction.
    • Valuable collection analytics: Gain insights into patron behavior, optimize collection placement, and make data-driven decisions about space allocation.
    • Streamlined workflow: Replace third-party solutions, reducing complexity and simplifying library operations.
    • Improved accessibility: Ensure all users can easily navigate the library by providing clear navigation for all users, regardless of mobility.
    Additional Details:
    • Provide an option to upload location maps into Alma, associating them with call number ranges for stacks or shelves.
    • Display the relevant map within Primo VE search results for physical items based on call number, with clear directions to the shelf.

    Conclusion: This integrated library mapping solution will change the way patrons interact with physical collections, bridging digital search and physical retrieval, while gaining deeper insights into libraries' collection usage.

    Develop an integrated library mapping module for Primo VE featuring interactive floor plans with clear, step-by-step directions. Seamlessly integrate this module into Primo VE's existing infrastructure, ensuring a user-friendly interface accessible to all patrons.

    Benefits:
    • Enhanced user experience: Streamline the path from digital search to physical item retrieval, reducing frustration and improving overall user satisfaction.
    • Valuable collection analytics: Gain insights into patron behavior, optimize collection placement, and make data-driven decisions about space allocation.
    • Streamlined workflow: Replace third-party solutions, reducing complexity and simplifying library operations.
    • Improved accessibility: Ensure all users can easily navigate the library by providing… more

    112 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

13. Allow institutions to exclude the 776 from the CDI holdings file

    Proposal: allow institutions to exclude the 776 from the CDI holdings file

    Problem: sometimes local services for book title X in a series get matched to CDI records for book title Y (a different title in the series). Users click on the service and are taken to the wrong book, which is frustrating. According to Ex Libris, Alma uses the 776 field to generate the holdings file that is sent to CDI to calculate availability, and this is what causes the incorrect matching.

    The solution of removing identifiers from the 776 as outlined in this Knowledge Article is not feasible, because it goes against correct cataloging practice. Even if we were to remove the 776 in our local bib, it would get overwritten with the next bib update.
    Why Do CDI Records for Book Series Titles Appear Incorrectly as "Full Text Available"? How Can I Correct This? - Ex Libris Knowledge Center https://knowledge.exlibrisgroup.com/Alma/Knowledge_Articles/Why_Do_CDI_Records_for_Book_Series_Titles_Appear_Incorrectly_as_%22Full_Text_Available%22%3F_How_Can_I_Correct_This%3F

    The 776 should not be used to calculate availability, as it is not an indicator of whether a particular institution has access to the alternative format, only that the alternative format exists. Therefore, institutions should have the ability to exclude the 776 from the holdings file published to CDI.

    Proposal: allow institutions to exclude the 776 from the CDI holdings file

    Problem: sometimes local services for book title X in a series get matched to CDI records for book title Y (a different title in the series). Users click on the service and are taken to the wrong book, which is frustrating. According to Ex Libris, Alma uses the 776 field to generate the holdings file that is sent to CDI to calculate availability, and this is what causes the incorrect matching.

    The solution of removing identifiers from the 776 as outlined in this Knowledge Article is not feasible,… more

    86 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

14. Improve Browse with 505 $$t subfield

    Ex Libris technicians report that currently only the first occurrence of 505 $t is included in the Title index. As a result, if you Browse by a title listed further within the 505, the results don't supply a matching record. All $$t subfields in the 505 (and any other fields recording titles) should be included in the Title index to avoid this issue.

    2 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

15. Primo NDE - Option to Display Cover Thumbnail Alongside Embedded Digital Viewer

    Problem Summary

    Currently, when an embedded digital viewer is present on a record, the system intentionally hides the cover thumbnail. Network calls confirm that the thumbnail is no longer requested once the viewer loads. While this is expected behavior, it can create a less optimal user experience in situations where the viewer does not display the actual cover or full document—for example, when it opens on a table of contents or another non-cover view. In these cases, users lose quick visual context provided by the cover image.

    Description:
    Requesting the addition of a configurable option that allows the cover thumbnail to remain visible even when the embedded digital viewer is loaded. This would be particularly helpful when the viewer displays content other than the cover (e.g., table of contents, metadata views, or alternate document sections). Providing the thumbnail alongside the viewer would enhance user context, improve navigation clarity, and offer a more consistent visual experience.

    Proposed Behavior:

    • Add a setting or toggle to optionally retain the cover thumbnail when the digital viewer loads.

    • Ensure the thumbnail can appear in a consistent location

    • Maintain current behavior as the default to preserve backward compatibility.

    Rationale / Benefits:

    • Improves user context when viewer content differs from the cover.

    • Enhances UX without disrupting existing workflows.

    • Offers institutions more flexibility in how records are presented.

    Thanks

    Problem Summary

    Currently, when an embedded digital viewer is present on a record, the system intentionally hides the cover thumbnail. Network calls confirm that the thumbnail is no longer requested once the viewer loads. While this is expected behavior, it can create a less optimal user experience in situations where the viewer does not display the actual cover or full document—for example, when it opens on a table of contents or another non-cover view. In these cases, users lose quick visual context provided by the cover image.

    Description:
    Requesting the addition of a configurable option that allows the cover thumbnail… more

    6 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Primo VE  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Users should be able to request individual volumes from multi-volume record

    We have a record that has multiple volumes of the same manga in it.

    https://wisconsin-uwp.primo.exlibrisgroup.com/discovery/fulldisplay?context=PC&vid=01UWI_PL:PARK&search_scope=DN_and_CI&tab=default_tab&docid=cdi_globaltitleindex_catalog_113538775

    The individual volumes are impossible to request for the user. This has to be done on the Alma side by a staff person. We would like records like this that have multiple volumes to have requestable individual volumes.

    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Primo VE  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

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

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

    5 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Primo VE  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

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

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

    6 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Primo VE  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. IZ level view configuration

    As a library network with a large number of Primo views, it can be extremely laborious to update every single view for configuration options that are identical in each view. These include in particular all configuration options that can be found in the General, Links, Advance Search, Brief results, Brief record display and Full Record Services tab of the view configuration menu.

    This kind of centralised view management would need to be available at the IZ level as it does not fulfil the same purpose as the possibility to distribute configuration from the the Network Zone to the various Institution Zones (in our context, we have two IZs for different types of libraries, with different configuration requirements).

    Indeed, this could be of interest not only to a library consortium but to any standalone library that manages several views.

    As a library network with a large number of Primo views, it can be extremely laborious to update every single view for configuration options that are identical in each view. These include in particular all configuration options that can be found in the General, Links, Advance Search, Brief results, Brief record display and Full Record Services tab of the view configuration menu.

    This kind of centralised view management would need to be available at the IZ level as it does not fulfil the same purpose as the possibility to distribute configuration from the the Network Zone to the various Institution… more

    75 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Primo VE  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Granular Control for Alma Viewer and Digital Versions Tab in Primo NDE

    Description:

    In Primo NDE, the rule “Hide service: Representation Delivery Service” affects both alma-viewer-content and the Digital Versions tab (nde.brief.results.tabs.digitalVersions). In contrast, Primo VE allows institutions to independently control visibility of the Alma Viewer and the Digital Versions tab.

    This enhancement request seeks to restore this level of granular control in Primo NDE. Specifically, institutions should be able to:

    Hide the Alma Viewer for certain representations (e.g., auxiliary or restricted content)

    Still display the Digital Versions tab for those same representations

    This would provide the flexibility needed for managing multiple representations of a record while ensuring users can discover digital content, even when the viewer is suppressed.

    Use Case:

    • Hide viewer for auxiliary representations

    • Keep the Digital Versions tab visible for those representations

    Benefit:

    Restoring this functionality would align Primo NDE with Primo VE, improving user experience and enabling finer control over digital content visibility.

    Description:

    In Primo NDE, the rule “Hide service: Representation Delivery Service” affects both alma-viewer-content and the Digital Versions tab (nde.brief.results.tabs.digitalVersions). In contrast, Primo VE allows institutions to independently control visibility of the Alma Viewer and the Digital Versions tab.

    This enhancement request seeks to restore this level of granular control in Primo NDE. Specifically, institutions should be able to:

    Hide the Alma Viewer for certain representations (e.g., auxiliary or restricted content)

    Still display the Digital Versions tab for those same representations

    This would provide the flexibility needed for managing multiple representations of a record while ensuring users can discover digital… more

    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Primo VE  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating