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.
402 results found
-
Journal coverage: show more label if there is more than one embargo
Since November 2021 journal coverage is shown in brief results (https://knowledge.exlibrisgroup.com/Primo/Release_Notes/002Primo_VE/2021/010Primo_VE_2021_Release_Notes#Show_Journal_Coverage_Dates_in_Brief_Results_and_Journal_Search_).
This is very good, but there is one rule that is not the best solution. It is stated: "Coverage information may include a single embargo, and if multiple embargoes exist, only one of them will appear in the coverage."
Now, embargoes of different portfolios may contradict each other. So, if the user only see the first one, he may erraneously believe he has no access. Therefore, as soon as there is more than one embargo, the more label should get added to the journal coverage in the…10 votes -
My Library Card: Option to hide Personal Details
It should be possible to hide Personal Details section under My Account in Primo VE.
We are able to disable the labels in the following, but seems no option to hide the Personal Details section. Even if we disabled the labels for this tab, it is not completely disable from appearing or being clickable.
- Configuration > Discovery > Display Configuration > Labels > All code Tables > Library card Labels
- Configuration > Discovery > Library Card Configuration > Personal Details Configuration
Also, Primo Technical Support Analysts already confirmed the personal details section cannot be hidden using CSS. So we post…
9 votes -
Allow creating "NonFullText" electronic collections (as the "getCitedJournal" in SFX).
We would like Primo VE to allow creating "NonFullText" electronic collections, following the SFX model where the "getCitedJournal" service type exists.
This would allow managing lists of notes and/or service access urls, complementary to the other FullText collections.
Currently it is not possible to do these loads without confusing users in the results view, since when treating it as full text objects it shows them as "Available online".
This option would be complementary and more flexible than the "General electronic services", which are very limited since it does not allow adding particular notes and the URL must be homogeneous.
See…
9 votes -
Enhance Primo Subject to Track the usage statistics by MMS ID and country
Enhance Primo subject to track the usage statistics (specifically downloads and views) by MMS ID and country of download.
9 votes -
Make the login help link language sensitive
In Alma Configuration it is possible to define Login page help links for Primo VE and to translate the label to another language, but it is not possible to have separate URLs for help pages in different languages.
We would like the URL to be customizable per language the same way the label is.
8 votes -
Block free text input functon in Resource Sharing Form
When users request items with multiple volumes in the resource sharing form (NERS Enhancement - Request ID #4856), they can select a specific volume from the pull down list, also freely enter the volume information in the box. Errors of manual input may lead to in inefficient or failure of handling the requests, e.g. user input “1” in the text box instead of selecting “v.1” from the list, the request can be created successfully, but the description cannot be shown in “Borrowing Requests” of Borrowing Library or “Pick from the shelf” of Lending Library, the libraries need to spend extra…
8 votes -
Add enabling/disabling OpenURL as option in Direct Linking Configuration
Some libraries (like mine) would appreciate the ability to disable direct linking for incoming OpenURL searches while enabling direct linking for other functions (such as direct linking from results list). We would like this flexibility because we find that direct linking from the results list saves the time of our users, but direct linking from incoming OpenURL searches is more confusing. We don't want to have to turn off direct linking altogether to help solve this confusion, but have no choice with current settings. Other libraries may desire the opposite settings: disabling direct linking from results list but enabling for…
8 votes -
Adding fields to purchase form
Currently the purchase form in Primo has a limited number of fields. We want to see the class/course name and professor and campus name as fields so we can better plan collection development.
8 votes -
Enable the addition of referencing style to the results list by email
In Summon, you can select the format of your results list before emailing it to yourself or another person. Eg. You want to view your search results in APA format, or AGLC, etc., and also have the link sent to you for each item in the list.
This functionality would be a great addition to Primo VE.
8 votes -
Allow Local Fields as filters for NZ Search Scopes
When setting up a custom scope we found the "Local fields" option was not available in the dropdown list if we choose scope population "Entire Network".
The "Local fields" option is available in the dropdown list if we choose scope population"My Institution".We think the "Local fields" option should be available for scope population "Entire Network" as well because we can set up up to 10 local search fields in the NZ and they would be used in the scope definition.
This would allow consortia to exclude specific resources from the NZ scopes based on values in the NZ local…
8 votes -
Improved Support of multilingual elements for external data sources in Primo VE
For Dublin Core and Generic XML records that contain multilingual content, Primo VE should display the values of the associated fields according to the user's language when the language code is available as an attribute in the Dublin Core elements.
For instance:
<dc:subject xml:lang="fre">Phonotèque/dc:subject <dc:subject xml:lang="ita">Fonoteca/dc:subject8 votes -
Display Logic Rule: hide multiple links to same Interface
Where there are multiple links from the same Interface, provide a way for a Display Logic rule to be added that only shows the first of links from the same interface, and hides the rest.
Often we have multiple links on the same interface (to different Ebsco, Proquest, Gale collections) with identical access.
Currently it does not appear possible to add a display logic rule to do this.
8 votes -
Quotation marks: align the behavior of Alma and CDI records
When using quotation marks in a search, Alma and CDI records behave differently:
CDI records:
« » → not considered for the search
„ “ → considered for the search only for some languages
“ ” → considered for the search only for some languages
" " → considered for the searchFor local records:
« » → not considered for the search
„ “ → not considered for the search
“ ” → not considered for the search
" " → considered for the searchWith this idea exchange we propose to align the behavior of Alma and CDI…
8 votes -
Provide LibGuides Type Functionality in Studio
Expand the new Primo Studio functionality to include an ability to create content like many of us are using through LibGuides. A simple content management system that would allow us to create simple web pages would allow us to replicate things like subject guides directly in Primo. If that content can also be indexed and searchable through the Primo VE search box that would be even better! This would avoid the need for seperate systems like LibGuides.
7 votes -
Allow configuration of call numbers in virtual browse
If you choose to display electronic materials in Virtual Browse Primo VE only allows 050 Library of Congress call numbers.
It would be good to have the option to choose between 050 or 082, so we could display Dewey to clients instead.7 votes -
Possibility to disactivate related link to physical holding (based on ISSN) for articles
On Primo VE, when a CDI record contains an ISSN that matches physical holdings (ie. the catalog contains a physical version of the journal that contains this article), it will automatically add on this record a GetIt section with the related physical holdings.
Example:
This can be disturbing for the user (and even for librarians), as the get it section shown for this article record contains all the issues in the holding associated with the ISSN, and not only the one containing the article. When the library detains many items in the related physical holding, it doesn't help much…
7 votes -
Calculated availability for non-full text records in digital imports from repositories
In Primo VE, institution repositories are limited to one label. For example, a link to the full online resource or a link to the physical resource are both labelled as ‘Full Text Available’.
This is a problem, as not all repositories are the full text, some repositories may just be an abstract.
Primo's label options are better, it is clearer to the user by the various different labels, for example ‘Full text available’ or ‘No full text’.
We would like Primo VE to have the various different labels, like Primo.
Please vote for our NERS request.
NERS Request ID: 7842
7 votes -
Allow Bibtex information to be copied and pasted rather than only downloaded
Currently, Primo requires that users download Bibtex and other citation data to their computers, and then upload or copy it from a document. This takes up valuable memory. Google Scholar has a feature that allows you to copy and paste the Bibtex citation directly from the browser rather than needing to download it, saving space and the hassle of saving and uploading a list of resources to their computers. Could a similar functionality be created for Primo VE where Bibtex information can be copied and pasted rather than just downloaded?
7 votes -
Allow Database Facet/Filter/Limiter in Primo VE
We would like the ability to filter results by database in Primo VE. For example, if someone searches "biology", but has been instructed to only use articles from our Academic Search Premier database, there would be a way to limit to both articles and the Academic Search Premier database.
7 votes -
Change handling of MARC fields 100 and 700 in citation styles in Primo VE
Handling of MARC fields in citation styles should be changed as follows:
1. If there are relator codes in $4, only $4 aut and cmp should be considered as author, relator codes $4 edt, ill, ivr, trl and drt should be treated as contributors. Entries with other $4 codes should be ignored for citation.
2. If there are no relator codes $4 in the record, field 100 should be considered as author, field 700 as contributor.
Benefits: Citiation styles get independent from cataloguing language as they are now by using $e. Also citation styles work independent from the fact, if…7 votes
- Don't see your idea?