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.
647 results found
-
Smart login messages - Do not show login message in the ViewIt for Open Access material
If a user is not logged in they get the Login message on the ViewIt and GetIt tab, whether they need to login to access that resource or not.
For example, Open Access material.
We have had many instances of users complaining that they have to login to access OA material. In fact they do not need to login to access this material. The Primo login message is confusing and misleading the user to think that they do need to login.
See for example the following Open Access material in our Primo instance.
https://primo-direct-apac.hosted.exlibrisgroup.com/primo-explore/fulldisplay?docid=RMIT_ALMA_DC11160517080001341&context=L&vid=RMITU&lang=en_USIn this example the resource is…
34 votes -
Configure fields included in Course Information
We would like to be able to modify the default configuration of Course Information field displayed in the details view of the full record in Primo VE, adding to or deleting the default elements (Course ID, Department Name, Course Instructor Name) or changing their order. For example, an institution may want to include only Course ID and Instructor Name but not Department Name here. This is not currently possible.
167 votesHi,
This is to update that this issue is still not planned to be developed in the current road map. We will continue to evaluate it for a future release.
Therefore we are keeping this under "Under review" status.
Best regards,
Yael.
-
Dedup and FRBR cluster monitoring
Since BIRT reports in back office are being deprecated and they are not available in VE, those who implement Dedup or FRBR will have no way to monitor the clusters that goes beyond what's currently in analytics (just a report of cluster sizes). Size of clusters is important, but when "impossibly large" clusters form (we recently noticed many, up to 89 members!), we need to be able to see the records forming the cluster in order to diagnose problems. The BIRT tool is way too slow and unwieldly for this purpose but provides useful information: contents of the fields that…
30 votes -
Use of initial articles in title starts with searches in Primo Advanced Search
Primo is currently unable to adequately accommodate initial articles (a, an, the etc.) when doing a title starts with search in Advanced Search.
The first title field that appears in the sort section of the PNX is used as the title that is matched against when doing a title starts with search but this leads to different outcomes depending on whether the records are indexed from PCI or Alma:
When the title field in the sort section of the PNX is created from Alma the default behaviour is to strip the initial article
When the title field in the sort…39 votes -
Do Not Highlight Stop Words in the Results of a Keyword Search
There is no value to highlighting words in the search results of a keyword search that were considered STOP words when the search was conducted.
Words such as AND, THE, OR, IN, TO, etc., provide no value on their own and should not be highlighted. Not only does highlighting them add visual noise to the search results, it sends the wrong message to users about how to construct a strong search string.
As the screenshot shows, the highlighting is only adding noise.
301 votes -
Change order of holdings for e-journals in ViewIt
Allow the institution to determine the ordering of resources in the ViewIt section of Primo. The single select options would include:
• By Date – Ascending
• By Date – Descending
• Alphabetical
• (Not sure if there are others)Currently e-journal titles with multiple holdings are displayed in alphabetical order. When each holding has a different date range, it can be difficult to scan quickly. This would allow each institution to select what works best for their users.
55 votes -
Primo Analytics - Ability to report on all search strings, not just Popular and Zero Results
Primo Analytics currently only includes search string data for Popular and Zero Results subject areas. It would be a vast improvement to be able to see all search string results.
Note: This functionality is available via BIRT, but only by individual reports by first letter of the alphabet, which are unwieldy and essentially unusable in loading so slowly (and often not at all).196 votes -
Adjust number of results Collection Discovery
Collection Discovery pages are great but loading 10 at a time is not enough. Would like to see adjustable results dial similar to what was recently released in Alma. Perhaps even up to 100 results on a page would be sufficient.
136 votes -
Display 6XX fields with $v form subdivisions intact
Primo VE is configured to map 6XX $v form subdivisions to a separate display field, breaking the subject string. In some cases, the form subdivision is plucked out of the 6XX, leaving the surrounding string incomplete. For example:
600 10 $aO'Keeffe, Georgia, $d1887-1986 $vExhibitions
displays in Primo VE as:Subject O'Keeffe, Georgia, 1887-1986
Genre Exhibitions
651 #0 $aRome (Italy) $vMaps $vEarly works to 1800
displays in Primo VE as:Subject Rome (Italy)
Genre Maps
Early works to 1800And so on, for all 6XX $v form subdivisions. This cannot be reconfigured. Additionally, each occurrence of the form subdivision is displayed…
255 votes -
Restrict discoverability of e-resources for walk in users to those resources they are licenced to use
We're looking to restrict the discoverability of electronic resources for walk in users to those resources they are licenced to use.
Ideally, Primo would identify that the walk in users were from a certain IP range and in combination with an Alma licence
condition which allowed walk-in use to the resources, it would allow them to discover the resource.38 votes -
Can Noodletools be added into Primo as a citation tool?
We want Noodletools added into Primo for citations
72 votes -
Subject Browse - allow merging of identical subject terms from different vocabularies
Right now, when I browse in my Primo by subject, I'm seeing a lot of subject headings repeated from different taxonomies. For example: Microbiology (EBPS), Microbiology (FAST), Microbiology (fast MESH), Microbiology (LCSH), Microbiology (LCSHKIDS FAST), Microbiology (MESH). This looks like a mess and is confusing for the user. I'd like to propose that where subject headings are identical between taxonomies, they be merged into one entry so the user doesn't have to check them all.
42 votes -
View Primo as someone else / different types of users
View Primo as "someone else". It would be useful to view our Primo-page as different types of users. Being able to view Primo as an internal user, or a student, or staff member, or an external user, would help us troubleshoot configuration and settings in Alma. Have we activated the right functionality for the different user groups? Have we hidden what we want to hide?
tl;dr: Facebook's "View as" functionality in Primo.
54 votes -
Sort purchase requests in Primo, by newest
It would be really helpful if user were able to sort their purchase requests in Primo by purchase-request creation date newest. Now Primo shows their purchase requests sorted by oldest, normally the user wants to see the follow up of the most recent.
55 votes -
Control Purchase Request Display in Primo by Material Type
Using display logic rules there is no easy way to show the Purchase Request link based on material type. We want to enable the purchase request link for ebooks, but not ejournals. I did come up with a hackey workaround by creating a GES that only does the identification of the journal and then a display logic rule to hide the purchase request if this GES is present, but there seems like there should be a better way to do this?
203 votes -
Allow reader to sort the values in a facet by A-Z or by number of records.
Most databases such as Web of Science or Ebsco Discovery tool allow the user to determine how to sort the values in a facet (see screenshot)
444 votesThis idea is under review for the NDE UI
-
Make the New Primo UI more CSS friendly
While the new Primo interface gave us more power to extend functionality via JavaScript it does not do the same for modifications via CSS due to the lack of properly marked up content.
In some parts of the New UI the content is well described, often with custom HTML elements, but there are also many places, often in the higher levels in the DOM tree, where better described selectors (preferably through classes) are needed.
For example, there is currently no selector that show the current system that is being displayed. The <prm-explore>-element could have the current system being shown as…
93 votes -
Add MODS template as Date Source for OAI-PMH harvest
Currently, there is no MODS template for OAI-PMH harvesting of external collections. As an example, we have many collections in an Islandora repository and have very rich metadata in MODS format. We lose most of that metadata when the collection is harvested because we must use the DC template as the Source format.
57 votes -
Displaying the pre-filters used, as the used facets are dispalyed
It would be very useful to display the pre-filters used in Primo New UI (from both simple search screen - as of May release and advanced search screen). Pre-filters used should be displayed in the brief results list just as the facets used are displayed, at the top of the column. Thus the patron can always see and be aware of all the active filters in the session
62 votes -
Allow libraries to review PCI metadata in collections
We would like the ability to not only see more information about the collections (which is already another idea on here) but also the ability to see the metadata for each collection. For example, for Kanopy, we have loaded the MARC records into Alma, but would like to review what the metadata for the PCI collection looks like so we can make a decision about whether or not to enable it. We have no way to know what the PCI collection will add or do until we turn it on in production Primo.
50 votes
- Don't see your idea?