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.
1103 results found
-
Library Card page
I think it would more user-focused if the "Library Card" dashboard listed all of the requests and loans in one spot, regardless of the lending library. Many users are unaware of which library they've requested an item through - it would be nice if there was only one dashboard for patrons to check on the status of everything in one spot.
762 votesThank you for this idea. We are currently reviewing it and discussing it also with the Alma team.
-
Remove CDI constant expansion of results
PCI results respect that a user knows what they want, but help with expansion when necessary, such as by stemming when there are very few results returned by the exact query. A user has autonomy also to target their results with techniques such as quotation marks, Boolean operators, and Advanced Search.
In CDI, expansion is constant, by term inflection applied to all searches, as well as higher recall in general by design. This cannot be prevented by features such as Boolean operators, quotation marks or Advanced Search, and is illogical in conjunction with other features like 'Did you mean'.
Note:…761 votes -
Possibillity to add print journal holdings to Primo holdings-file
In Primo only the electronic holdings for e-books and e-journals are taken into consideration when determining the availability for a record/article from the central index (PCI/CDI).
The libraries also have print/physical holdings of journals that can fulfill the needs of the end-user and that can fill gaps in the electronic coverage. If the user search for an article that the library only has as part of the physical journal holdings the availability of the article are set to "Not available" and dependig on the configuration the article might not even show up in the result-list.
This has been adressed in…
636 votes -
Display related holdings for monographs only for the 773 $w relation and not for the 8xx $w relation
When filtering to a certain location via facets, you often get results from other locations too, which is unexpected from patrons perspective in many cases. This is caused by the current related records setting which is also taking locations with related records into account. The display is correct for analytical records without inventory (book chapters and articles), but not for the other monographical resources.
What we wish to achieve is the following:
When the record of a book chapter, journal issue or journal article (i.e. a record containing a 773 field with $w) is viewed in Primo, the holding of…
581 votes -
Improve indexing of in press articles in CDI
The Central Discovery Index (CDI) includes many in press articles (i.e., articles that have been accepted for publication in a future issue). However, because these records do lack a pub date, volume, or issue number, the Alma link resolver cannot reliably determine whether an institution has access to these articles. We ask that Ex Libris improve they way in press articles are indexed in CDI so that the link resolver does not return false positives for content the library does not actually own.
476 votes -
Enable search and browse also for item call numbers, not only holdings
Hi
We switched to Primo VE some months ago and are really missing a call number index that shows all our call numbers, in items as well as in holdings.
https://slidetodoc.com/three-types-of-call-numbers-in-alma-yoel
"Item Call Number – is it in Primo VE search indexes?
• The item call number cannot be added as a Primo VE search index.
• Of the three call numbers only the “Holding Call Number” can be added as a Primo VE search index."Our call number index is set to "callnumber.4 – Shelving control number call number", our item call numbers are type 4, but they are…
453 votes -
Primo VE: Allow Exclusion of Institution Zone only records from Discovery Network/NZ Scope
In consortial environments, the Network Scope includes Institution Zone only records such as laptops, keys, etc.
We would like the capability to exclude IZ only records from a Discovery Network scope so that we can display only records that are NZ bibs, not local IZ with no NZ bibs.
414 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)
390 votes -
Primo VE: Ability to use norm rules to specify which 856 (Marc) fields display in Links service
In Primo Back Office (BO), it is possible to use normalization rules to specify which 856 Marc fields display in the "Links" section of the Primo full record view. (See attached screenshot.)
We would like the same functionality in Primo VE to choose which 856 links to display based on the 856 first and second indicators and/or the subfields of the 856 field. Thank you.
331 votesThank you posting this idea. Moving it to under review for further analysis.
-
Improve Primo Search Algorithms
When our users look for a book in the Primo Search Portal they expect that the Primo Search behaves like a Google Search, i.e. they expect that Primo finds books with titles or metadata containing words similar to those in their query. Unfortunately, the Primo Search is very sensitive to the exact spelling of the words in the query. If the search query is slightly inaccurate, the book is not found in Primo. I tried such unsuccessful search queries on www.amazon.de, and Amazon usually found the correct book: Amazon showed the correct hit on top of the list (see…
330 votes -
Ability to edit the OTB (Out-of-the-Box) search and facet rules in Primo VE
We would like to be able to edit the OTB search and facet rules. This is necessary for parity with PBO. There are several things that we were able to do in PBO that we cannot reproduce in VE because of the lack of this functionality. In the PBO OTB author search and facet, we were able to include dates and qualifiers from names in the LCNAF, which improved precision. In the OTB language facet, we were able to include intertitle, caption and audio description languages, which are not currently included in the VE OTB index. On the other hand,…
328 votes -
Make consistent the use of CDI record data in Primo UI
Current CDI design in Primo UI is to expose metadata from all participant records for both returning results from a search query, and in the values presented for selection in facet for filtering results, but the display of metadata within records is only by site-specific activations.
This means that a user can search for a term in Primo, have results returned on the basis of that term, select the value for the term in a facet, but then not see the term in the record display.The negative impact of this design decision includes:
* a user is confused by…313 votes -
Search Slot/Scope/Profile Usage in Primo Analytics
We would like to be able to report the total number of searches that have been performed in each search/slot/scope/profile that we have configured in Primo. Currently the only report in Analytics that has Search Scope search information is the Zero Results Report.
This information will provide invaluable information about our user behaviour and will help us in the customization of the Primo interface to meet the needs of our clients by assisting in decisions regarding adding or removing search profiles/scopes.
294 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.
288 votes -
course reserve
Course Reserves:
Requested Enhancement: Offer interface with drop-down menus for Course Title, Course Department, and Course Instructor (similar to drop-down menus in Voyager)Currently users can search for course reserves, but there is not a good mechanism to browse. Offering drop-down menus would easily allow users to see what was currently on course reserve by course title, department and instructor.
Thank you for considering
282 votes -
Primo VE: Ability to search by publisher (advanced search or facet)
The MARC 260b + 264b field is not included in the out-of-the-box indexing in Primo VE advanced search or facet as PUBLISHER. According to the documentation the publisher name is searchable only by general in the simple search and not in the advanced search, specific search for the publisher name. Readers want to limit the results by the name of the publisher.
280 votes -
Allow libraries to configure the Brief Record Display with more flexibility
In the brief and full display pages, libraries can display information contained in data fields (such as the title, author, and creation date) from the source record. This information helps users to differentiate records quickly. In some cases, there can be a lot of information that is displayed. This is particularly the case when Contributor is added: all 7XX fields are added, and in their entirety (see for example in the attached screenshot).
We would like an option that would allow the library to either limit the number of fields to display (for example max 3 7XX fields) or to…
268 votes -
Primo Name/Title Browse Searches
Primo Name/Title Browse Searches
As frequent Primo users searching for known music items, the Alma Music Users Group would like to propose that Ex Libris create a left-anchored browse search for name/title entries found in bibliographic records. An alphabetical left-anchored browse search is particularly helpful for known-item searches that are often used for music materials and prolific literary authors.
Currently, Primo provides browse search options for names (name portion only ($a,$q,$d)) and name/title headings used as subjects. For prolific authors, it is not unusual to find thousands of name/title headings lumped under the composers or authors name, with “20+ records”…
268 votes -
Can Ex_libris work with publishers to enable OA articles in hybrid journals to be discoverable ?
Currently if we do not subscribe to a journal (normally a hybrid OA titles) which has open access articles the article access is not discoverable as available during a search of Primo - is there any way to identify these articles as being available ?
265 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…
257 votes
- Don't see your idea?