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 ~
508 results found
-
In the Display Logic Rules, add the option to "hide service" with "Availability by the network" for Network Zone Resource Sharing
In the Display Logic Rules, add the option to "hide service" with "Availability by the network".
We are in a Network Zone consortium that does Resource Sharing. Right now, we can hide services like "Purchase Request" if the item with "Availability by the institution" or "Ownership by the Institution" is true, but we also want to hide it for availability in the network, so that patrons are forced to try Resource Sharing in our network first, rather than submit a Purchase Request.
14 votes -
Allow deduping between MARC and DC records with non-filing characters in title
It is currently not possible to dedup MARC and Dublin Core records if the title field contains non-filing characters.
Primo VE can perform deduplication between MARC records in Alma and DC records that are ingested via discovery import profiles. However, the dedup title keys that are generated for MARC records take into account if the title has non-filing characters (such as initial articles), as indicated in the 245 second indicator. It is not possible to indicate non-filing characters for DC records. Therefore, records that would otherwise be matches for deduplication have different titles.
For example, a record with the title “The Relationship Between Humans and Dogs” would have the title key “Relationship Between Humans and Dogs” for the MARC record and “The Relationship Between Humans and Dogs” for the DC record.
My preferred fix for this would be for the title key generation for DC records to automatically remove common articles from the beginning of titles. I could also see other possible solutions, like enabling a way to remove non-filing characters from DC fields via normalization rules or having a variation of the title key for MARC records that includes non-filing characters.
It is currently not possible to dedup MARC and Dublin Core records if the title field contains non-filing characters.
Primo VE can perform deduplication between MARC records in Alma and DC records that are ingested via discovery import profiles. However, the dedup title keys that are generated for MARC records take into account if the title has non-filing characters (such as initial articles), as indicated in the 245 second indicator. It is not possible to indicate non-filing characters for DC records. Therefore, records that would otherwise be matches for deduplication have different titles.
For example, a record with the title…
8 votes -
Index Item Description in Primo VE
We record the monographic titles of periodical issues only in the Item Description field and not in the periodical bibliographic record.
This item field is searchable in Alma but not in Primo VE.
We need that the Item Description field to also be searchable in Primo VE.41 votes -
Add Lateral Links (Hypertext link) to Journal Search/Database Search/Newspaper Search
Currently, the basic search and advanced search results provides journal, database, and newspaper records the ability to broaden the search by using lateral links. When the same records are displayed on the Journal Search, Database Search, and Newspaper Search pages, they do not have lateral links. This means there is no way to find more from the listed authors, subjects, related titles, etc. Please add lateral links to these pages for all fields available as in the basic search and advanced search.
6 votes -
Primo VE - Allow normalization of Esploro records
As a discovery tool Primo VE is supposed to deliver a unique gateway to many Library Resoures, including the a Institutional Repository (i.e. Esploro ).
To do so in a blended search one must be able to normalize records from different sources. We used to do that in Primo Classic, with a Pipe and a Normalization Rule. This is however not possible in the newer Primo VE.
Please allow manipulation and normalization of Esploro assets so that we can show them in the catalogue in a consistent way.42 votes -
Add IZ scope for e-resources activated for the IZ in the Network Zone.
SLSP activates a large amount of OA e-resources from the NZ. The use case is to save time and resources for the IZs.
The OA e-resources activated from NZ are searchable in the IZ-wide Search scopes when using the out-of-the-box scope MyInstitution and MyInstandCI. However, they are not searchable in IZ library / campus search profiles. There is no scope that would add NZ e-resources available for the IZ / library / campus to the Search Profile created for a specific library / campus within an IZ.
Library scope in an IZ with Inventory Management Groups (IMG)
If an IZ is using Inventory Management Groups, then we attach the library for which the view is created in the condition. This shows only e-resources of the IZ that are activated for the library or available for the whole IZ without restriction.Physical Availability – Library = library
OR Electronic Availability – Library = library
Library scope in an IZ without Inventory Management Groups
If the IZ is not using Inventory Management Groups, then we put a condition to display any e-resources in the IZ. This shows any activated e-resource in the IZ.Physical Availability – Library = library
OR Available Electronic Exists
Issue
The NZ e-resources activated with the IMG for the IZ / library / campus or without any IMG restrictions should be considered as the IZ / library / campus electronic inventory. There should be a possibility to add these e-resources to the scopes created for library / campus in the IZ views.SLSP activates a large amount of OA e-resources from the NZ. The use case is to save time and resources for the IZs.
The OA e-resources activated from NZ are searchable in the IZ-wide Search scopes when using the out-of-the-box scope MyInstitution and MyInstandCI. However, they are not searchable in IZ library / campus search profiles. There is no scope that would add NZ e-resources available for the IZ / library / campus to the Search Profile created for a specific library / campus within an IZ.
Library scope in an IZ with Inventory Management Groups (IMG)
If…6 votes -
Browse results based on Primo VE view
We have several different Primo VE views for different libraries & library collections. However, the Browse functionality includes all records/titles from across the institution. It's confusing to users to see results from different views when they are expecting results to be in the context of the view they are using.
6 votes -
Add label to view it section in front of service provider link
Add a label to the front of the service provider name in the view it section so that it can be made clearer that users should click on this to access the resource. At the moment we have to use a customization to add text but it would be easier to maintain if this was a standard label.
6 votes -
add in a optional conditional facet upon selecting Open Access - showing version options using unpaywall data
A major issue that the use of Open Access content such as unpaywall can have is the version and making people aware of the version they are seen/given them the choice of version (submitted/author accepted/version of record)
For institutions who have Unpaywall collection available and/or their institutional repository data being added in, use the metadata in the background of the record to identify the version that will be available from the link (signpost would also ideally be applied in the Brief record view and/or full record) and when Open Access facet is selected, it would automatically open an additional Facet for
- submitted
- accepted
- publishedto allow users to limit their results by version available within the unpaywall collection
A major issue that the use of Open Access content such as unpaywall can have is the version and making people aware of the version they are seen/given them the choice of version (submitted/author accepted/version of record)
For institutions who have Unpaywall collection available and/or their institutional repository data being added in, use the metadata in the background of the record to identify the version that will be available from the link (signpost would also ideally be applied in the Brief record view and/or full record) and when Open Access facet is selected, it would automatically open an additional Facet…11 votes -
unpaywall - collection separation
in the webinar : Yes, We’re Open! Open Access in Knowledgebases and Discovery 20231211 1501 1 1 (https://www.youtube.com/watch?v=WhZ34Y1Rzdo) Christine Stohn mentioned that Ex Libribs we interested in feedback to find out how people wanted UnPaywall content to be available, e.g. split up by version.
I would therefore like to proposed that the UnPaywall Collection be split into 3 separate collections, Submitted version, author accepted versions and Version of Record/Published version.
This would not only enable us to only enable the versions we want and avoid those we don't, but also allow us to potentially signpost the version types to our users/make then aware BEFORE they follow the link through that it may not be the version that they are anticipating.
in the webinar : Yes, We’re Open! Open Access in Knowledgebases and Discovery 20231211 1501 1 1 (https://www.youtube.com/watch?v=WhZ34Y1Rzdo) Christine Stohn mentioned that Ex Libribs we interested in feedback to find out how people wanted UnPaywall content to be available, e.g. split up by version.
I would therefore like to proposed that the UnPaywall Collection be split into 3 separate collections, Submitted version, author accepted versions and Version of Record/Published version.
This would not only enable us to only enable the versions we want and avoid those we don't, but also allow us to potentially signpost the version types…
12 votes -
Ask for confirmation when deleting saved searches
In “Saved searches” and “Search history” sections, when clicking on remove icon, the query is deleted immediately.
A popup asking for confirmation could help preventing unwanted deletions
3 votes -
Ability to sort or group online services by availability date
We would like the ability to sort or at least group the online services via the availability date. At the moment, I have to manually add and sort hundreds of ecollections to put the focus on these rather than our big packages (Proquest, Ebscohost, etc.)
We found that users generally click on the first few links despite what the availability dates are listed. Grouping by interface is available (https://developers.exlibrisgroup.com/blog/how-to-use-the-online-services-order-to-to-control-the-order-of-the-services-on-the-services-page-in-primo-after-clicking-available-online/?unapproved=1024&moderation-hash=5a646f643de45dfa00b8dbf001d0157f#comment-1024) so it would be nice to group titles in a similar fashion where we can group all ecollection with ongoing access at the top.3 votes -
Customise Purchase Suggestion Form material type list
The Purchase Suggestion Form in Primo VE currently offers a drop-down menu of all possible material types, including things like Ephemera, Toys, and Vinyl LP, which we don't want to turn off as a material type option but we also don't want to offer as a purchasing possibility. At the moment there's no way to switch off material types from that dropdown without removing them as an option for new items completely. We would like an option to customise this purchase suggestion form material type list with more flexibility.
47 votes -
purchase request form - expand where option of auto-populated form can appear
Currently with Purchase Request forms, if there is already a physical copy in stock, depending on the display logic rules set up - the purchase request form link will appear (useful for librarians wanting more copies) this will auto populate the form. However this will only appear when there is a physical copy as it appears in the get it section of the full record view.
For items available only electronically, I can add a GES to allow librarians to go to the blank purchase request form, but it won't auto populate.
This doesn't give parity or a similar experience for ALL of the content. As I also can't hide the purchase request link without affecting access to the blank form using a direct link - meaning that there isn't even another option to create consistency by removing the link.
Suggestion - Create a function where the purchase request form link will appear for electronic items (when display logic rules allow) AND it autopopulates the form. AND allow libraries to suppress the in record link to the form whilst making the blank form accessibly directly through a link.
Currently with Purchase Request forms, if there is already a physical copy in stock, depending on the display logic rules set up - the purchase request form link will appear (useful for librarians wanting more copies) this will auto populate the form. However this will only appear when there is a physical copy as it appears in the get it section of the full record view.
For items available only electronically, I can add a GES to allow librarians to go to the blank purchase request form, but it won't auto populate.
This doesn't give parity or a similar experience…
1 vote -
Pair display of 880 fields with their linked MARC field
When a record includes multiple 880 fields paired with multiple entries from the same MARC field, for example multiple 700 and 880-700 fields, Primo VE displays all the 700 fields and then all the 880-700 fields. This display loses the link between the two fields, and a user cannot easily connect the non-Latin script (in the 880 field) with the paired Romanised form (in the 700 field).
In the MARC record the link between fields, such as a 700 and its paired 880-700, is coded in the $6. If the Primo VE display normalisation rules syntax allowed you to compare values in the $6 from the 700 and 880-700 fields and create the pnx display fields for 700 and 880-700 in the same rule, then the linkage could be displayed through the ordering of the fields (i.e. 700, 880-700, 700, 880-700, …).
When a record includes multiple 880 fields paired with multiple entries from the same MARC field, for example multiple 700 and 880-700 fields, Primo VE displays all the 700 fields and then all the 880-700 fields. This display loses the link between the two fields, and a user cannot easily connect the non-Latin script (in the 880 field) with the paired Romanised form (in the 700 field).
In the MARC record the link between fields, such as a 700 and its paired 880-700, is coded in the $6. If the Primo VE display normalisation rules syntax allowed you to compare…
43 votes -
Primo Collections: Allow NZ records
For consortial users, it would be very helpful to be able to include NZ records in Primo Collections, instead of just IZ records.
3 votes -
Resource Recommender: allow users to dismiss
This is important especially on small screens, where RRs can get in the way when not pertinent to a user's needs.
4 votes -
Portfolio Order
Logic Rules often become complex in showing exactly which holdings to display. We would like to have the ability to rank(or order) portfolios based upon institutional needs and have an easier way to exclude portfolios that we do not want displayed, without creating an endless amount of display logic rules that can inevitably cause issues.
3 votes -
Allow lowercase Boolean operators
When searching in Primo VE, Boolean operators must be entered in all caps. Many databases and search engines allow either uppercase or lowercase Boolean operators, so this requirement may trip up users and prevent them from getting the results they were looking for.
3 votes -
Add Search within "Journals by Category" results
Journals by Category is less useful since each category could have hundreds of results. For example, searching by the category "Psychology" produces 623 journals. EDS' journal search allows you to search within that category--so in this case, you'd be able to search a specific topic among only the 623 psychology journals identified. We have professors who require students to find ten articles in Economics/Accounting journals that are published in the USA. A search within the category Economics journals for a topic, and perhaps even the location facet, would help these students out!
4 votes
- Don't see your idea?