Primo
Your feedback matters to us. Help us improve Primo by telling us what you’d like to see using the message areas below. You can also can support something already posted.
We would love to be able to respond to every idea that is submitted, but this is not feasible. We are, however, committed to responding to the most popular ideas—those that have received the most points.
For more information please review our FAQ and guidelines. Thank you.
- or
3 results found
-
Include the item barcode as part of the data published from Alma to Primo in the AVA field to improve item search in Primo
Request for Alma item barcode be included in the data that is published to Primo as part of the Alma publishing functionality to enable barcode searchability in the Primo keyword search. We have discovered that items migrated from our previous ILS do contain the item barcode(s) in the MARC 945 $$i and is written to the search:general field of the PNX. As such, those items are keyword searchable via their barcode in Primo. However, for items created in Alma, the item barcode is not written to the bib record and is therefore not searchable in Primo. Adding the item barcode manually to the bib 945$$i for each item as part of our processing is not a viable alternative.
We would like an enhancement to Alma publishing that would add the item barcode to the data published in the "AVA" field. This functionality would improve workflow for staff when they need to search a record in Primo without having to navigate out of the items screen in Alma to retrieve the OCLC number, the MMSID or the ISBN, or to pull up the record in Primo when the book is in-hand without needing to key in the title or ISBN.
Examples of migrated records with the item barcode in the 945 $$i:
http://alliance-primo.hosted.exlibrisgroup.com/CC:cc_alma:CP71153242760001
http://alliance-primo.hosted.exlibrisgroup.com/CC:cc_alma:CP71188416360001451Request for Alma item barcode be included in the data that is published to Primo as part of the Alma publishing functionality to enable barcode searchability in the Primo keyword search. We have discovered that items migrated from our previous ILS do contain the item barcode(s) in the MARC 945 $$i and is written to the search:general field of the PNX. As such, those items are keyword searchable via their barcode in Primo. However, for items created in Alma, the item barcode is not written to the bib record and is therefore not searchable in Primo. Adding the item barcode…
465 votes -
Less duplicate records in Primo Central Index results
Primo Central grouping is based on the existing FRBR workflow, including the grouping process at the database level (the way the Search engine handles grouping) and the Front End functionality. It is used to prevent duplicate records in the results list.
Unfortunately, many records are not added to FRBR groups because the system considers the metadata are not rich enough. With the increase of records provided by (Open Access) aggregators and repositories, the number of duplicate records will certainly not decrease.
Could Ex Libris improve the FRBR workflow for Primo Central records in order to reduce the number of duplicate results and consolidate the FRBR groups?
Examples of duplicate records:
Accuracy of prediction of gene content in large animal populations and its use for candidate gene detection and genetic evaluation
3 results (2 FRBR groups):
- TNproquest195858157 and TNfaoagrisUS201300875183
- TNcrossref10.3168/jds.2007-0231, TNscopus2-s2.0-42449094585, TNsciversesciencedirectelsevierS0022-0302(08)71293-1, TNmedline18349258
- TNorbi2268/23076Linguistic symbiosis between event loop actors and threads
2 results (1 FRBR group):
- TNsciversesciencedirectelsevierS1477-8424(08)00024-9
- TNscopus2-s2.0-51649125887 and TNcrossref10.1016/j.cl.2008.06.005Efficient control of transient wave forms to prevent spreading depolarizations
2 results (1 FRBR group):
- TNarxiv0705.3398
- TNscopus2-s2.0-39649117125, TNsciversesciencedirectelsevierS0022-5193(07)00579-6, TNcrossref10.1016/j.jtbi.2007.11.019, TNmedline18177900Le traitement de la modalité épistémique dans les traductions françaises de On the Origin of Species de Charles Darwin
3 results:
- TNerudit1038687ar
- TNscopus2-s2.0-85017546223
- TN_proquest1870219718Primo Central grouping is based on the existing FRBR workflow, including the grouping process at the database level (the way the Search engine handles grouping) and the Front End functionality. It is used to prevent duplicate records in the results list.
Unfortunately, many records are not added to FRBR groups because the system considers the metadata are not rich enough. With the increase of records provided by (Open Access) aggregators and repositories, the number of duplicate records will certainly not decrease.
Could Ex Libris improve the FRBR workflow for Primo Central records in order to reduce the number of duplicate
…203 votesHi all,
We are moving this idea to "Closed" to release your votes, as it is no longer relevant with CDI.
Best regards,
Yael.
-
Ensure that CZ & CDI Metadata is Linked Data Ready
I was advised by the Linked Data Group to post this idea here because I submitted the following for the LOD Working Group webinar in December:
Broader strategic and commercial alliances required to ensure that data is ready to be linked?
To engender confidence in CZ and make it linked-data ready, why don’t the Company do business with e.g. Backstage Library Works for authority control clean-up and maintenance?
Metadata is a global commodity so all stakeholders have responsibility for creating, sharing, enriching and maintaining it, and of course there are costs for all of these elements which we could share.
Isn’t this the best way to ease the burden on libraries and leverage our metadata improvements for mutual and sustainable benefit?
I note that this document alludes to the Company taking a lead in creating a new open metadata platform and preserved data in an open format.
https://knowledge.exlibrisgroup.com/Alma/Product_Materials/010Roadmap/Linked_Open_DataPreserving metadata is not the same thing as maintaining it because metadata evolves e.g. authorities are deleted, changed and new ones created.
In light of this I would ask that the Company explore strategic commercial partnerships to ensure that any metadata that they manage (knowledgebases, platforms) is properly maintained.
Jane
I was advised by the Linked Data Group to post this idea here because I submitted the following for the LOD Working Group webinar in December:
Broader strategic and commercial alliances required to ensure that data is ready to be linked?
To engender confidence in CZ and make it linked-data ready, why don’t the Company do business with e.g. Backstage Library Works for authority control clean-up and maintenance?
Metadata is a global commodity so all stakeholders have responsibility for creating, sharing, enriching and maintaining it, and of course there are costs for all of these elements which we could…
16 votes
647 results found
-
Add Journal Read and Publish Details to Alma and Make Them Discoverable in Primo
As libraries continue to add more read and publish journal agreements, it’s important that researchers are able to easily discover which journals are part of these agreements, the open access article publishing charges that are and are not covered by these agreements, and other relevant details related to open access publishing from the library’s read and publish agreements.
There are several open access journal discovery products that provide end users with this kind of information, but they must perform searches on separate platforms, and library staff must maintain these holdings outside of Alma.
Examples include:
ChronosHub: https://stanford.chronoshub.io/?q=%220021-9371%22&journaltitle=Journal%20of%20British%20Studies
Open Journal Finder by Consortia Manager:
The above products use data from a variety of sources, such as publishers, OpenAlex, etc., to gather journal APC costs, publishing activity at the library’s university, and more. Libraries can add notes about their read and publish agreements that display in the corresponding journal records. And journals whose APCs are included in a library’s read and publish agreements prominently indicate that there are no costs for researchers to publish open access articles.
This would need to be a cross-product enhancement involving Primo for end user discovery, Alma for electronic resources management and licensing aspects of transformative agreements, Alma Analytics for tracking publishing usage of these agreements and combining it with COUNTER read data, and content operations for the metadata for APC costs, institutional publishing activity, etc.
As in the examples above, some read and publish/APC metadata will appear in brief search results (e.g., whether the APC is covered by the library agreement). At the same time, more details would be available in full journal records (such as Creative Commons licenses, a publisher description of the journal’s scope so authors can determine relevant journals for their research, unique details about the read and publish agreements that the library can customize from within Alma, publishing activity in that journal at that institution, open access publishing instructions for authors (customizable by library), etc.. Researchers would need to be able to use facets to limit their search results to journals whose APCs are covered by their library’s read and publish agreements.
Use Cases:
Researchers wanting to find open access journals without any author fees could search Primo using limiters for journals included in their library’s read and publish agreements and subject areas. Libraries could achieve a greater return on investment from their read and publish agreements by making their offerings more visible at the point of need. The information would be easy for researchers to understand, reducing the need for library staff to respond to questions about eligible journals and OA author publishing costs. Researchers would not need to search a third-party platform; they could simply use Primo to find this information, a tool they are already familiar with. Library staff would not need to maintain read and publish holdings in a separate system; they would be managed in Alma alongside the library’s other electronic resources. Library staff could run Analytics reports on their researchers’ utilization of the publishing parts of read and publish agreements to more easily assess their return on investment and inform renewal decisions.Justification
Libraries are investing more and more of their acquisitions budgets in read and publish journal agreements, and researchers need the ability to easily discover these details via Primo searches. Providing details about whether or not researchers need to pay to publish open access articles helps researchers make informed decisions on where to publish and better comply with government open access mandates across the world. It could also help libraries achieve a greater return on investment from these agreements and more easily assess them to make data-informed renewal decisions.
As libraries continue to add more read and publish journal agreements, it’s important that researchers are able to easily discover which journals are part of these agreements, the open access article publishing charges that are and are not covered by these agreements, and other relevant details related to open access publishing from the library’s read and publish agreements.
There are several open access journal discovery products that provide end users with this kind of information, but they must perform searches on separate platforms, and library staff must maintain these holdings outside of Alma.
Examples include:
ChronosHub: https://stanford.chronoshub.io/?q=%220021-9371%22&journaltitle=Journal%20of%20British%20Studies
Open Journal Finder…
85 votes -
Primo NDE: Make the display of user initials independent of the sort order for user names in Alma
In Primo NDE, when a user is logged in, the initials are displayed according to the sort order for user names defined in Alma (Configuration > User Management > User Details > User Name Display). If the sort order is set to "lastName, firstName" ("Smith, John") in Alma the initials will display as "SJ" in Primo.
We think it should be possible to configure these two appearences indenpendently. It should be possible to sort user names as "lastName, firstName" in Alma, but display the initials in Primo as "firstName lastName".
64 votes -
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…
3 votes -
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.
4 votes -
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…
29 votes -
Allow view configuration to exclude retracted and withdrawn articles from results list
The CDI Document Types labels and facets are valuable information. Now that we have that information, and the Document Types are also facets, can we please get the ability to set our discovery views to exclude these Retracted and Withdrawn articles (similarly to how we have the ability to set a view to exclude CDI ebook records)?
I set up our custom primo search box widget on our library website to exclude these two resource types by default, and I locked those facets so they aren't lost on the next search. You can search the Combined Search box on our library site to try it out: https://www.normandale.edu/current-students/academic-resources/library/index.html
But it's not a good work around. First, any time the user clicks on the New Search link in the menu, the facets are cleared. Second, when a user navigates from a CDI search to a local search (like our book search) or journal search the excluded facets are sticky in those searches too, even though they have no effect in those contexts. Also, by using the facet functionality to exclude these resource types, we are also in effect drawing extra attention to the existence of these unreliable sources in the library's collections.
Although not a preferred solution because they would still be discoverable, I thought about possibly down boosting these two resource types. Currently, CDI document attributes are not boostable.
The CDI Document Types labels and facets are valuable information. Now that we have that information, and the Document Types are also facets, can we please get the ability to set our discovery views to exclude these Retracted and Withdrawn articles (similarly to how we have the ability to set a view to exclude CDI ebook records)?
I set up our custom primo search box widget on our library website to exclude these two resource types by default, and I locked those facets so they aren't lost on the next search. You can search the Combined Search box on our…
20 votes -
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…6 votes -
Natural language search in NDE should support customized local resource types
Some of our consortium members who are testing Primo NDE have discovered that our custom resource types do not work with Ask Anything (the natural language search) in Primo NDE. For example:
The search "i need print books about water" returns only ebooks. Due to our custom "print books" resource type, only e-books remain in the OTB "books" resource type in Primo.
The search "i need audiocassettes on bach" returns only audio CDs, as we have custom resource types for other audio formats (audiocassettes, lp records, etc.).
The search "i need videocassettes on figaro" returns only streaming videos, as we use custom resource types for physical video formats (videocassettes, DVDs, Blu-Ray, etc.).
In general, none of the custom resource types is selected - instead, the natural language search appears to default to the OTB resource types (if there is one).
Users who interact with our catalogs on a daily basis are used to seeing resource type labels that are often customized to our collections. So it's understandable that they will use those resource type names in their natural language searches. NDE's natural language search should be able to transform those phrases into searches for the accurate resource type - especially since the customized resource types appear in (working) facets that are available for Primo users who are not employing natural language search.
Some of our consortium members who are testing Primo NDE have discovered that our custom resource types do not work with Ask Anything (the natural language search) in Primo NDE. For example:
The search "i need print books about water" returns only ebooks. Due to our custom "print books" resource type, only e-books remain in the OTB "books" resource type in Primo.
The search "i need audiocassettes on bach" returns only audio CDs, as we have custom resource types for other audio formats (audiocassettes, lp records, etc.).
The search "i need videocassettes on figaro" returns only streaming videos, as we…
72 votes -
Enhancing visibility of Open Access indication for CDI article records
Problem:
[see 1OAPrimo.png] Currently, the Open Access indication appears under a title in Primo for Open Access CDI article records, which can confuse library users. They might think that all collections under "View Online" are all full-text open access.Idea: To enhance clarity for users, we recommend first configuring Alma settings to control the display of the Open Access indication, followed by adjustments in Primo.
[In Alma] [see 2OAPrimo.png] We propose adding a tick box or a dedicated field within the service level settings to indicate open access. When enabled, this setting will control whether the OA indication appears.
[In Primo] [see 3OAPrimo.png] Once configured in Alma, the OA indication can be displayed clearly in front of the collection name under "View Online," helping library users easily identify Open Access resources.
Problem:
[see 1OAPrimo.png] Currently, the Open Access indication appears under a title in Primo for Open Access CDI article records, which can confuse library users. They might think that all collections under "View Online" are all full-text open access.Idea: To enhance clarity for users, we recommend first configuring Alma settings to control the display of the Open Access indication, followed by adjustments in Primo.
[In Alma] [see 2OAPrimo.png] We propose adding a tick box or a dedicated field within the service level settings to indicate open access. When enabled, this setting will control whether the OA indication appears.
[In…
3 votes -
FRBR/Dedup reports and overviews
Experimenting with FRBR/Dedup currently requires finding ad hoc examples of records that might be frbrized or deduped. This complicates the administration of this feature as it is not possible to get an overview which records might be affected by some kind of setting.
It would be very helpful of it would possible in some way to get an overview of:
- Which records have any type of deduping
- Which records have any type of FRBR-ization
- Which records have been suppressed from FRBR/Dedup
Currently this is only possible to check on a record by record basis. The backend could improve by, for instance, creating a report, export, analysis, or any way to get an overview of records with these features.
Experimenting with FRBR/Dedup currently requires finding ad hoc examples of records that might be frbrized or deduped. This complicates the administration of this feature as it is not possible to get an overview which records might be affected by some kind of setting.
It would be very helpful of it would possible in some way to get an overview of:
- Which records have any type of deduping
- Which records have any type of FRBR-ization
- Which records have been suppressed from FRBR/Dedup
Currently this is only possible to check on a record by record basis. The backend could improve by, for…
5 votes -
My Library Card: date of the last renewal
We suggest that the "Date of the last Renewal" field should only update when a successful renewal happens, rather than when the courtesy letter is sent.
It happens in local loan and in Rapido, and it is confusing for patrons. We would like this workflow was adjusted.
42 votes -
Allowing to opt out of loading OAI Repository records into Discovery Network
Allowing to opt out of loading OAI Repository records into Discovery Network
1 vote -
Use all occurrences of a bibliographic field within GES Bib Field Enrichment
Institutions can define which fields are extracted from the bibliographic record metadata to be used in General Electronic Services by adding fields to the GES Bib Fields Enrichment mapping table. However, if the bibliographic field occurs multiple times in the record, only the first occurrence of the field is used. This means that the GES is not calculated for any subsequent occurrences of the field. For example, if I want a GES to be displayed based on a particular value in a 590 local note, the GES will only display if that value occurs in the first of what may be many 590 local note fields. I request that all occurrences of the fields defined in the GES Bib fields enrichment mapping table be used in GES calculation for display in Primo records.
Institutions can define which fields are extracted from the bibliographic record metadata to be used in General Electronic Services by adding fields to the GES Bib Fields Enrichment mapping table. However, if the bibliographic field occurs multiple times in the record, only the first occurrence of the field is used. This means that the GES is not calculated for any subsequent occurrences of the field. For example, if I want a GES to be displayed based on a particular value in a 590 local note, the GES will only display if that value occurs in the first of what may…
1 vote -
Restore One-Click Permalink Access in NDE Brief and Full Record Displays
As a library staff member and end user, I would like direct, one-click access to copy a permalink from both the brief and full record displays so that I can quickly and efficiently share stable links to resources without navigating through multiple menu layers.
Description:
In the original Primo VE UI, both brief and full record displays include a dedicated permalink button that allows users to access a permanent link to a resource with a single click. This streamlined access is essential for common workflows including:
- Reference and instruction staff sharing resources with students and faculty
- Liaison librarians embedding links in course management systems
- Researchers capturing citations and sharing resources with colleagues
- Students bookmarking materials for later access
In the NDE UI, the permalink functionality has been moved behind a "Share" button, requiring users to:
- Click the Share button
- Identify and select the permalink option from a menu
- Then copy the link
This additional step creates friction in a high-frequency task and reduces discoverability of this essential feature—particularly for users who may not intuitively associate "sharing" with generating a permanent link for personal use or citation purposes.
Requested Enhancement:
Restore a dedicated, top-level permalink button (or clearly labeled "Copy Permalink" option) in both brief and full record displays in the NDE UI.
This should be:
- Visible without requiring interaction with another button
- Enabled by default in new NDE views (the "share options" button is disabled by default at time of writing)
- Positioned prominently alongside other primary record actions
This change would maintain feature consistency with the original UI and support established user workflows without requiring retraining or workarounds.
As a library staff member and end user, I would like direct, one-click access to copy a permalink from both the brief and full record displays so that I can quickly and efficiently share stable links to resources without navigating through multiple menu layers.
Description:
In the original Primo VE UI, both brief and full record displays include a dedicated permalink button that allows users to access a permanent link to a resource with a single click. This streamlined access is essential for common workflows including:
- Reference and instruction staff sharing resources with students and faculty
- Liaison librarians embedding links…
75 votes -
Incorporate a systematic review content type/filter into Primo
Systematic reviews are key to evidence based medicine practice. They “... establish whether scientific findings are consistent and can be generalised across populations, settings, and treatment variations, or whether findings vary significantly by particular subsets (Mulrow, 1994).” They also identify existing gaps in the literature requiring further research. The number of systematic reviews published has grown from less than 50 a year in the early 1990s to almost 36,000 in 2022 (Brignardello-Petersen, 2025) Health sciences researchers, clinicians and students would benefit from the ability to efficiently limit search results to systematic reviews in Primo with a corresponding content type/filter. Currently users must search for “systematic review” as keywords or subject terms which are inconsistently applied across CDI sources. Similar filters exist in other search platforms including PubMed and EBSCOhost CINAHL and Medline.
https://www.elsevier.com/connect/why-systematic-reviews-matter
Mulrow CD. Rationale for systematic reviews. BMJ. 1994 Sep 3;309(6954):597-9. doi: 10.1136/bmj.309.6954.597.
Brignardello-Petersen R, Santesso N, Guyatt, GH. Systematic reviews of the literature: an introduction to current methods. American Journal of Epidemiology, 2025 Feb; 194(2):536–542 doi:10.1093/aje/kwae232
Systematic reviews are key to evidence based medicine practice. They “... establish whether scientific findings are consistent and can be generalised across populations, settings, and treatment variations, or whether findings vary significantly by particular subsets (Mulrow, 1994).” They also identify existing gaps in the literature requiring further research. The number of systematic reviews published has grown from less than 50 a year in the early 1990s to almost 36,000 in 2022 (Brignardello-Petersen, 2025) Health sciences researchers, clinicians and students would benefit from the ability to efficiently limit search results to systematic reviews in Primo with a corresponding content type/filter. Currently…
163 votes -
Journal Title Facet Should Include Local Records in Blended Scopes
Currently, the Journal Title facet in Primo only applies to records from the Central Discovery Index (CDI), excluding locally cataloged article records and those imported from external sources such as institutional repositories. This behavior leads to inconsistent and confusing results for end users, especially when using a blended scope that includes both CDI and local records.
Problem:
Users conducting searches—particularly in the local language—often retrieve a significant number of local article records. Despite these articles being published in journals, their journal titles do not appear in the Journal Title facet.
Users are unaware of the distinction between CDI and local records and perceive the facet as broken or unreliable. This undermines user trust and the usability of the facet as a filtering tool.Our question is to
- extend facet generation logic to include journal titles from local records (Alma-records and imported via import profile)
- or if this is not possible, allow customers to customize the facet in order to include local records.This would ensure:
- Consistent and complete facet behavior across all indexed content.
- Improved user experience and trust in the system.
- Better support for institutions that rely heavily on local cataloging or repository imports.Currently, the Journal Title facet in Primo only applies to records from the Central Discovery Index (CDI), excluding locally cataloged article records and those imported from external sources such as institutional repositories. This behavior leads to inconsistent and confusing results for end users, especially when using a blended scope that includes both CDI and local records.
Problem:
Users conducting searches—particularly in the local language—often retrieve a significant number of local article records. Despite these articles being published in journals, their journal titles do not appear in the Journal Title facet.
Users are unaware of the distinction between CDI and local…3 votes -
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 -
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…
21 votes -
Implementation of CDI rights at the article level and not just at the database and title levels
CDI knows that a given article belongs to a given journal and knows that we have a subscription to it for this year (based on our SFX subscriptions). CDI therefore displays the article citation as part of the content to which we subscribe and creates an OpenURL link based on the citation metadata. If the citation in CDI is correct but this content does not exist on the platform, this generates errors in our catalogue and returns results that we do not have access to.
ExLibris does not have rights at the article level (only at the database and title level), so Primo has no way of knowing that a particular article is not available on the platform.
CDI knows that a given article belongs to a given journal and knows that we have a subscription to it for this year (based on our SFX subscriptions). CDI therefore displays the article citation as part of the content to which we subscribe and creates an OpenURL link based on the citation metadata. If the citation in CDI is correct but this content does not exist on the platform, this generates errors in our catalogue and returns results that we do not have access to.
ExLibris does not have rights at the article level (only at the database and title…
1 vote -
Primo VE Permalink Verification Process
We would like a process to verify a file of Primo Permalinks are still valid for our institution.
Our librarians and professors place Permalinks in online documents for our patrons. As the documents age and portfolio IDs change the links can fail. This is very frustrating for our patrons.
The only link verification method today is to manually click on each permalink. This tedious and time consuming process is not cost effective when there are hundreds of links to check. Using standard web link checkers that operate in batch only establishes that a page does not result in an HTTP error.
An Alma-specific verification process would help ensure the usability of web content that links to Primo. Ideally, a user could upload or paste a list of URLs into a tool, which would then check that each link resolves to a valid Alma or CDI record. As this relies on knowledge of both Alma and CDI record IDs, an external tool does not make as much sense as an ExLibris maintained solution.
We would like a process to verify a file of Primo Permalinks are still valid for our institution.
Our librarians and professors place Permalinks in online documents for our patrons. As the documents age and portfolio IDs change the links can fail. This is very frustrating for our patrons.
The only link verification method today is to manually click on each permalink. This tedious and time consuming process is not cost effective when there are hundreds of links to check. Using standard web link checkers that operate in batch only establishes that a page does not result in an HTTP…
1 vote
- Don't see your idea?