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
No existing idea results
- ~ No ideas found ~
672 results found
-
Improving Pick Up Location Logic in Primo NDE
Purpose:
To reduce incorrect deliveries, avoid patron frustration, and create a smoother, more intuitive request workflow by improving how pick up locations are ordered and saved in Primo NDE.
- Organisation-Level Improvement: Custom Default Sorting of Pick Up Locations
Current Issue
In the current setup, the pick up location list is presented alphabetically/historical by default. This can place small or rarely used locations at the top of the list, even when they are not relevant for most patrons.
This increases the risk of accidental selection and leads to unnecessary delivery errors.Proposal:
Within Primo NDE, the institution should be able to:
• Define its preferred default pick up location
• Specify the initial sort order for the full location list
• Override alphabetical/historical sorting where it does not align with operational needsGoal:
Ensure that the institution's most relevant and commonly used pick up location appears first, thereby reducing mistakes and improving the patron experience.
- Patron-Level Improvement: Personal Preferred Pick Up Location
Current Issue
Patrons currently cannot save a personal, preferred pick up location in their account settings. This forces them to select a pick up location repeatedly - increasing the chances of choosing the wrong one.
Proposal
As part of Primo NDE, patrons should be able to:
• Select and save a personal favourite pick up location when logged in
• Have this preference automatically preselected for future requests
• Change their preferred location at any timeGoal
Provide a personalised and efficient workflow that supports patron needs and reduces errors caused by repeated manual selection.
Next Step
We request approval to include these two improvements in our Primo NDE configuration agenda. Together, they will enhance usability, reduce incorrect deliveries, and strengthen overall patron satisfaction.
Final Note:
This proposal aligns closely with an existing community request on the Ex Libris Ideas Exchange:
“Define preferred pickup location in Personal Details”
https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/44908411This demonstrates that many institutions experience the same challenge, and that we are not alone in requesting these improvements and indicates broader interest and shared benefits, and suggests that our needs are well understood in the community
Purpose:
To reduce incorrect deliveries, avoid patron frustration, and create a smoother, more intuitive request workflow by improving how pick up locations are ordered and saved in Primo NDE.
- Organisation-Level Improvement: Custom Default Sorting of Pick Up Locations
Current Issue
In the current setup, the pick up location list is presented alphabetically/historical by default. This can place small or rarely used locations at the top of the list, even when they are not relevant for most patrons.
This increases the risk of accidental selection and leads to unnecessary delivery errors.Proposal:
Within Primo NDE, the institution should be able to:
…
83 votes -
Allow customisation of BibTex data export
Currently, the BibTex data export from the full record review is non-customisable, no changes can be made to how the fields display in the exported data. This differs, for example, from other formats such as RIS and EndNote, which do have a mapping table in the configuration.
The issues we’ve encountered with this are:
1) Some fields have a custom display that we’d like to show on Primo but not in the exported data – e.g. we include author details in the Title display, but it is incorrect for this to show in the BibTex title field
2) Where we have custom resource types on Primo, these are not read at all by BibTex and come up as “@unknown”entry types
The lack of mapping options for this feature is causing significant issues for our users who need to use this referencing platform for their course. At our institution this includes Mathematics, Computer Science and Physics students, with one academic estimating that it could impact circa 650 students for the modules he is responsible for alone.
Any workarounds for it are limited and would involve fundamental changes to configuration in Primo VE, such as stopping using custom resource types at all.
It would be massively beneficial if we could define a custom mapping for this export, such as being able to map our own resource types onto the BibTex entry types, or control how each BibTex field is populated using fields in the PNX or Marc.
Currently, the BibTex data export from the full record review is non-customisable, no changes can be made to how the fields display in the exported data. This differs, for example, from other formats such as RIS and EndNote, which do have a mapping table in the configuration.
The issues we’ve encountered with this are:
1) Some fields have a custom display that we’d like to show on Primo but not in the exported data – e.g. we include author details in the Title display, but it is incorrect for this to show in the BibTex title field
2) Where we…
41 votes -
Add autocomplete to embedded searchbox
Please add autocomplete to the embedded searchbox API for a consistent user experience.
1 vote -
Display tag for Open Educational Resources for CZ and IZ records in Primo
Open Educational Resources tags in CDI records are clearly displayed in Primo VE (e.g. Pressbooks titles). I would like to see this tag extended to include CZ and IZ records for open educational resources in a similar way to how we make the Open Access icon display in Primo.
24 votes -
Certificate of No Outstanding Debts/ Certidão Negativa de Débitos
Create a "Certificate of No Debts" function within Primo, which will allow users to issue a document stating that they have no outstanding debts with the Library (loans, unpaid fines, unreturned books, item replacements in progress, and others). If there are any outstanding issues, the document will specify what those issues are, and the user will be instructed to contact the library.
This is a very useful feature. With translate to POrtuguese, please.6 votes -
Allow customization of the display on the Primo Services Page so that metadata from the OpenURL doesn't present as a matched resource
Currently, when a user follows an OpenURL link to a Primo Services page, the page takes the metadata fields from the OpenURL and presents them in a format that mirrors the "Brief record display" from Primo search results and full record displays. This is misleading to users, who assume that the OpenURL has found a match for a resource when in fact they may not have.
We would like to be able to configure a separate display for the Primo Services Page, so that we can make it clearer to users that what they are seeing is a formatted version of the metadata, and not necessarily a citation for a legitimate resource. The need for this has always existed, but we believe it is becoming more pressing as we are seeing increasing numbers of fake, AI-generated citations in databases that generate links to our Primo.
Currently, when a user follows an OpenURL link to a Primo Services page, the page takes the metadata fields from the OpenURL and presents them in a format that mirrors the "Brief record display" from Primo search results and full record displays. This is misleading to users, who assume that the OpenURL has found a match for a resource when in fact they may not have.
We would like to be able to configure a separate display for the Primo Services Page, so that we can make it clearer to users that what they are seeing is a formatted version…
165 votes -
Configure page metadata (browser tab title) across key pages independently from the main menu labels
In Primo NDE, the browser tab title (the HTML <title> element) for many pages uses the same label as the top menu, e.g., ILL request forms, Citation Linker, Collection Discovery, Purchase request form.
Screenshot with label codes toggled on to demonstrate the same label used for different functions
This means that the title in the tab cannot be independently customised to act consistently with other areas of Primo (search and my library account where separate labels can be managed). This creates issues:
Usability:
- Users with many collection discovery tabs open cannot distinguish which collection is in each tab. Users sharing a link to a featured collection (where the tab title is automatically used for the link name. e.g. pasting a URL into a Word document, email, or Teams) must edit the link to match the collection’s name or risk confusing the recipient.
Confusion as to why the tab titles appear differently in search and my library pages compared to these other pages.
- Branding & Clarity: Institutions cannot reflect their institutional names in the tab titles on these pages, which confuses users and reduces trust.
When links are shared to different collections, the link name is always identical and cannot feature the institution’s name. e.g. Featured collections vs Aboriginal and Torres Strait Islander Collection | Bond University
Screenshot showing that the collection name could be used in the tab title.When a link to the blank ILL form or purchase request form is shared via email, it appears with whatever is in the top menu, rather than Purchase request | Institution Name unless the link is edited before sending. E.g. Purchase request vs Purchase request | University of XYZ.
For users affiliated with multiple institutions, this can also be confusing, as it is unclear which institution the link pertains to.Affected pages
The <title> element uses the same label as the main menu option for:
- Collection Discovery (Highest priority for SEO and collection promotion) – it does append the query for search within collections, but being able to include the collection name and institution would be better
- Fetch Items (Citation Linker)
- ILL request
- Purchase request
- Newspapers search
- Journal search
- Browse search
- Database search
- Tags
- Research Assistant
- Authority Search
June 2025 release notes included:
“NDE UI - Enhanced Customization and Branding Options
Support Existing Header Labels – The NDE UI now supports the codes used to customize and translate the page titles in the browser.”
While this was an improvement, the flexibility to insert institutional names is not supported for the pages listed above. If the institution name is hard-coded into the relevant label, it also appears in the menu.Related CERV enhancement request: https://enhancements.exlibrisusers.org/ideas/PENH-I-28463
In Primo NDE, the browser tab title (the HTML <title> element) for many pages uses the same label as the top menu, e.g., ILL request forms, Citation Linker, Collection Discovery, Purchase request form.
Screenshot with label codes toggled on to demonstrate the same label used for different functions
This means that the title in the tab cannot be independently customised to act consistently with other areas of Primo (search and my library account where separate labels can be managed). This creates issues:
Usability:
- Users with many collection discovery tabs open cannot distinguish which collection is in each tab. Users sharing…
3 votes -
Continue as Guest link on the authentication page
To encourage more users to sign in to Primo, we would like to provide more links on our public website, in emails, and through signage that direct users to specific pages in Primo, such as the AI Research Assistant or My Library Account. These require authentication first. While this works for our current staff and students, such links may also be clicked by people who do not have an account.
In this scenario, they are stuck on the authentication page with no option to opt out and get to the landing page. There is no top menu for them to choose from.
An optional/configurable link that offers them a path to continue as a guest user and takes them to the landing page would be helpful.
While this might also affect the sign-in window, it would not hurt to be there. It differs from the Cancel link, which simply closes the authentication pop-up – it does not take them to the landing page.
In cases where we direct the user to a specific page via authentication, the same type of cancel link would not work. This enhancement would instead take them to the landing page, as they are not authorised to use these special areas of Primo.
Example links:
//DOMAIN/nde/login?vid={VID code}&toState=account/overview&toParams={"vid":"{VID code}","lang":"en"}
//DOMAIN/nde/login?vid={VID code}&toState=researchAssistant&toParams={"vid":"{VID code}","lang":"en"}
While these examples and screenshots are from NDE, this is something that we had previously wanted to do in Primo VE too.
Related CERV enhancement request: https://enhancements.exlibrisusers.org/ideas/PENH-I-28464
To encourage more users to sign in to Primo, we would like to provide more links on our public website, in emails, and through signage that direct users to specific pages in Primo, such as the AI Research Assistant or My Library Account. These require authentication first. While this works for our current staff and students, such links may also be clicked by people who do not have an account.
In this scenario, they are stuck on the authentication page with no option to opt out and get to the landing page. There is no top menu for them to…
1 vote -
Clickable logo single URL insufficient for multilingual institution
There is only one field available for association with the clickable library logo in Primo VE. This means that some users in a multilingual institution will always be directed away from their chosen language interface after clicking the logo. Please provide at least one other field that is sensitive to the interface language in which the logo is clicked so that Primo VE may fulfil its promise of multilingualism.
40 votes -
Display Number of Renewals on Patron Library Card in Primo VE
Currently, Primo VE does not display the number of renewals for a patron’s loans on the patron’s library card. We propose an enhancement to allow the number of renewals (used and/or remaining) to be displayed in Primo VE for patron loans. This should appear on the patron’s library card.
Providing this information directly in Primo VE would improve transparency for patrons.4 votes -
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…
117 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".
90 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.
7 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…
33 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…9 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
.png){kind=link}
- Don't see your idea?