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.
1129 results found
-
Reconvigure Search Algorithm to Highlight Subscription Databases
Some change in the Primo search algorithm now shows free sources, such as DOAJ, as not only the best source, but the only source for some articles, even though the article is available in several of our subscription databases. I always want students to utilize subscription databases over free sources, mostly because the subscription databases add value, such as citation help, and also, we pay for them and I want students to use them. I would like to see the algorithm highlight subscription databases regardless of whether a free source is available.
4 votes -
loan history lookup option
Loan history lookup options, such as, a search box, a year select box or a slider (of the return date), would be helpful for the users having hundreds of loan history records.
4 votes -
Searching special characters Ayin or Apostrophe in Primo
In Alma, you get the same results if you include or exclude the special character ayin or apostrophe in your search terms. However, in Primo searches you need to include these special characters. If they are missing, you will not find the same result.
Ayin is used in transliterated title of items in Hebrew, Arabic, Armaic, Syriac, and Korean languages. It is not on a standard US keyboard, so it is difficult for users to include it in the search.
Apparently, Alma uses a different indexing system. We would like Primo to be able to do the same as Alma…
4 votes -
PrimoVE : Allow splitting Dublin Core Fields
As we have set up Discovery import profiles to import Dublin Core data from other institutions into our PrimoVE instance, we have discovered a few institutions that concatenate the DC:CREATOR and DC:SUBJECT fields into a single field.
The ability to split these fields in normalization would be extremely useful in the Primo environment.
4 votes -
Dark mode for Primo
Users ask for a possibility to view the catalogue interface in dark mode. Could this be realized for Primo?
Thank you!4 votes -
Use non-LC call numbers for journal categories
This affects Primo/PrimoVE; but the job is in Alma.
The new feature (as of Nov 2019) to browse a list of journals by category depends on the 050$a. This should be expanded to use the 055$a, 060$a, 070$a, 080$a, 082$a, 083$a, 084$a, 085$a, and 086$a. Additionally, libraries should be able to pick which of the subfields to use.
This is an example of the lack of support for non-LC libraries.
** This idea cross-posted as Alma idea. **
4 votes -
Analytics: Add Referrer to the rest of the Primo Subject Areas
Referrer is only in the Primo Action Usage Subject Area. This field should be added to other subject areas as appropriate -- like Primo Sessions
4 votes -
Primo VE: subject searching with hyphens
When I click on a subject heading in a record in Primo VE (https://catalog.library.vanderbilt.edu/discovery/fulldisplay?docid=alma991029907089703276&context=L&vid=01VAN_INST:DIVINITY&search_scope=MyInstitution&tab=LibraryCatalog&lang=en), Primo VE does an exact subject search and gets no results, not even the record on which I clicked the subject heading. This only happens with some subject headings, not all. An example: the subject heading Self immolation -- Religious aspects -- Buddhism gives zero results (not even the record which contains the subject link I'm clicking on shows up, nor any other records with that subject heading -- 2 others); while the subject heading Buddhism -- China -- Customs and practices seems fine.…
4 votes -
Dedup process - Create Additional data PNX fied based on prefered record
In dedup process, all fields from Additional Data section are merged and duplicate fields are removed. This design choice cause some issues with Citation service. When you merge records from differents sources, there is a strong possibility that data are not exactly the same and some data are duplicated. This problem may often be solved by choosing fields from prefered records as it is the case for display section
4 votes -
add otb support for iso 639-3 languages in Primo
Primo currently supports iso 639-2 values for languages.
We would like a support for the broader iso 639-3.
Iso 639-3 is much richer.
For example in our library we have more and more materials written in Ladin of the Alps, which is not the iso 639-2 Ladino (a language with the same name but spoken in Spain) but is instead the Ladin lld in iso 639-3.
As a language iso 639-3 lld is a subset of the broader iso 639-2 roh family. But using just roh is quite a lack of granularity for us.Other customers around the world may…
4 votes -
showPnx page as XML
In the classic UI, if you added the parameter showPnx=true, in the address bar, to the URL of a record's full display, you were able to get an XML file with the PNX version of the record. In the NUI, on the contrary, the same parameter takes you to a web page containing the PNX record in a textarea.
The XML view of the PNX record was very much easier to manage: colouring of tags, open/close section as well as you need them, etc.
Why did you change this behaviour for worse?
Could we get back the XML version of…4 votes -
Primo Saved Search email - link color setting
Improve color customization of Saved Search Email Alerts
The February 2020 Primo feature does not allow us to customize the link text in the header (used for the terms of the saved search), which leads to contrast issues.
Similar to the "Unsubscribe" customization, there should be a similar component to set the color of link text in the header.
4 votes -
In CDI Non-OA items appearing with OA unlocked icon
We have results that are not open access leading users to paywalled articles, and since these are all 'link in record', it is/was nearly impossible to determine which collection is leading users astray.
Is a fix in the works? Right now the collection I suspect is European Union Publications, which has no Alma portfolios, shows as Type 'Selective package', and which shows the option to 'Remove CDI-only full text activation'. I have not yet clicked that.
I hope a fix is in the pipeline.
4 votes -
Pin Book resource type to top of resource facet list
In university libraries, a task for many users is to find books. However, because Primo VE with CDI returns so many electronic books, the Book resource type is dropped below the "Show more" fold. It would be helpful if Discovery Admin could pin some resource types to the top of the list to accelerate users in this task.
4 votes -
Direct linking for Digital Objects to have an order in case of several DOs
Currently direct linking for digital objects when there are more than one does not follow any order. Hence, when a record has several D.Os any of them could benefit arbitrarily of the direct linking.
For example, take an English record that is accompanied by several DOs of the document in different languages. The ideal scenario will be to have the English Record and Direct linking to the English D.O. and in the Full Display the options to see other language versions. Currently, the Direct Linking takes any D.O. , which could be confusing to users.
We would like to have…4 votes -
Browse by subject: visualize the 360 and 680 fields from the authorities records
It´s important for the users in order to navigate from one subject to other
4 votes -
Ability to see full bib info in Collection Discovery Resource Editor
Greetings,
We are using Collection Discovery to highlight new and significant items in the collection for medical specialties and topics, but the Collection Resource Editor doesn't show the pub date, making it hard to main maintain meaningful and up-to-date title lists. I'm talking about this (see attached). It would be helpful to see the publisher and pub date.
4 votes -
auto announcement for maintenance or outage
We would like to see built into Primo (all flavors NUI/VE etc) an auto announcement banner when there is scheduled maintenance or major outage.
We would also like the message that it displays to be customizable via a table in the back office.
This would help to alleviate an extremely manual process that we currently do with pulling the cloud notification emails and entering in text and dates manually to be displayed in Primo. It makes more sense to have this be an automatic process much like the emails sent out by cloud services.
4 votes -
Make location choice mandatory on the resource sharing form
If a user has the option of choosing between multiple pickup locations in their resource sharing form, make this field mandatory and the location drop down menu read:
Choose one: (<--- default choice is no choice)
Location 1
Location 2
Location 3
Etc.Right now, the default is based on a setting that could be, for example, the patron's home library. What I'm specifically requesting is that the default is "Choose one" and that the choosing be mandatory.
4 votes -
Option to change Dublic Core normalization rules for collections in BePress' Digital Commons
Currently items imported from Digital Commons do not display a date because out of the box normalization rules for Dublin Core records will not display the date if the date field ends in Z, which is a timestamp. Since BePress claims it is required to include a timestamp, I am requesting that we can modify normalization rules to display a date with a Z field.
4 votes
- Don't see your idea?