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
-
Display import profile name also for for failed import jobs
Currently, the scheduled job "Import Data to Primo VE" gives us the name of the import profile/external data source that was harvested, but only if the job ran successfully. If not, only the name of the job will be given, but not which profile it ran on. This is true both in Alma and for the corresponding e-mail notifications. We would be glad if this could be changed so that the profile name is always displayed, as the current behaviour is making troubleshooting issues with the import profiles quite cumbersome, especially if several are affected at once.
40 votes -
Primo VE mobile device enhancement
When using Primo VE on a mobile device, such as a mobile phone, if you change from portrait to landscape and then back to portrait, half of the page will become blank, which is not conducive to readers' viewing.
103 votes -
Enable person entity functionality at the view level
The new feature (May 2024) for person entities is either on or off for all views.
For some special-purpose views it may be inappropriate to display person entity cards. At present the library would have to deploy a customisation package to allow it to show on some views, but hide it on others. It would be simpler to enable via check boxes in a view's general tab.
Libraries should be able to configure whether or not the results returned in the carousels on a person entity page are controlled by the view's search scopes. e.g. titles that are excluded from that view should display or not.
The new feature (May 2024) for person entities is either on or off for all views.
For some special-purpose views it may be inappropriate to display person entity cards. At present the library would have to deploy a customisation package to allow it to show on some views, but hide it on others. It would be simpler to enable via check boxes in a view's general tab.
Libraries should be able to configure whether or not the results returned in the carousels on a person entity page are controlled by the view's search scopes. e.g. titles that are excluded from…
61 votes -
Improve Citation Action
We would like to summarize in this idea exchange several issues we have run into with the citation action that inhibit the usefulness of the functionality for our customers greatly. Most of these relate to a lack of language sensitivity on the incoming side of the citation action. We would think it would be good if Ex Libris could work towards an improvement here, maybe together with the Citation Styles Language Project.
The formatting for the page count should be p.DDD-DDD or p. DDD-DDD in 773 $$g according to Ex Libris. The issue with this is that when our cataloguing language is German, we consequently capture the pages with “S.” for “Seiten” instead of “p.” for “pages”, meaning the page count will not be displayed. Here we would be glad if Ex Libris could build an improvement that allows for the abbreviation for “pages” to be in languages other than English
In the citation, the pages, volume and issue are always given in English. Support informed us that this would need to be addressed by the Citation Styles Language Project but as we would like the information to be given according to the UI language set in Primo, we believe it would be best if Ex Libris would look into this together with the CSL.
The required formatting for the relator codes is too inflexible and conflicts with our cataloguing rules. For the desired solution a separate Idea Exchange was already opened: https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/46780609-change-handling-of-marc-fields-100-and-700-in-cit. To summarize: We would prefer if the relator was taken from $4 instead of $e, making it independent of the cataloguing language used. Also, all relators other than auth. and comp. should be considered contributors instead of creators.
As these issues have the potential to majorly affect our customers in a negative way (Students not checking their citations carefully and getting worse grades due to incorrect citation, possibly up to accusations of plagiarism) we would appreciate if Ex Libris could consider an improvement or more configuration possibilities for these issues.
We would like to summarize in this idea exchange several issues we have run into with the citation action that inhibit the usefulness of the functionality for our customers greatly. Most of these relate to a lack of language sensitivity on the incoming side of the citation action. We would think it would be good if Ex Libris could work towards an improvement here, maybe together with the Citation Styles Language Project.
The formatting for the page count should be p.DDD-DDD or p. DDD-DDD in 773 $$g according to Ex Libris. The issue with this is that when our cataloguing…
54 votes -
Use "Receiving Date" as a search facet to allow for the configuration of "New Arrivals" pages/searches.
being allowed to use the "receiving date" field, rather than the "creation date" as a facet will help libraries to be able to display new arrivals to the collection; items that are actually in the library and read to circulate. As the "creation date" is often the date of the order, these items are not available for use for many months depending on the supply chain.
10 votes -
Open Access articles to display in full text results
Currently, if only displaying CDI results with full text, articles tagged as open access aren't included. These are only displayed if the user toggles to show results with no full text.
Ideally, articles tagged Open Access would also be included when displaying results with full text. The tag would need to bypass the link resolver process so those results are also included.
This would reduce the number of users putting in ILL requests when they didn't realised the article was available OA.
20 votes -
Primo VE, Quicklinks and "Available Online" indication
We’d like the "Available Online" text in be suppressed if Quicklinks are displayed for the citation in the brief results display.
As the librarians put it:
"to turn off the "Available Online"
link/message if the quick links are available. “And alternately, "... make the "Available Online" link go directly to the article like the "Read PDF" Quicklink option does? "
Reducing the number of possible links to click on would improve Primo VE.
Thanks.9 votes -
FRBR generic: make display of the generic record customizable
We use FRBR generic (in Primo VE) because we deem FRBR preferred to be too confusing for our patrons.
We can't fix the duplicate display of contributors' names.
Example:
https://basel.swisscovery.org/discovery/search?query=any,contains,Homer%27s%20Iliad%20translated%20by%20Richmond%20Lattimore&tab=UBS&search_scope=UBS&vid=41SLSP_UBS:live&lang=en&offset=0, see also screenshot.Lattimore is displayed three times, Martin twice.
As this is supposed to be a generic display, no contributors should be displayed here.
We got the following response from Ex Libris in our case:
"
With the 'Generic record' option enabled, when conducting a search in Primo, in the list of results for a FRBR group, you will see a very generic record which is hardcoded and cannot be modified. This record will contain work-level metadata and will serve as a placeholder for the group. It won't include the data and functionality that is relevant to a specific record, only indicating that multiple versions of the title have been found. The generic FRBR display consists of :The first row - as per View configuration.
The second row is hard coded to display the fields - display/creator and display/contributor.
...The current design of Primo is to always display creator and contributor in the 2nd line of the FRBR record if the generic record is selected. If you want to remove the contributor from the generic record, the next step is to pursue this as an enhancement.
"We use FRBR generic (in Primo VE) because we deem FRBR preferred to be too confusing for our patrons.
We can't fix the duplicate display of contributors' names.
Example:
https://basel.swisscovery.org/discovery/search?query=any,contains,Homer%27s%20Iliad%20translated%20by%20Richmond%20Lattimore&tab=UBS&search_scope=UBS&vid=41SLSP_UBS:live&lang=en&offset=0, see also screenshot.Lattimore is displayed three times, Martin twice.
As this is supposed to be a generic display, no contributors should be displayed here.
We got the following response from Ex Libris in our case:
"
With the 'Generic record' option enabled, when conducting a search in Primo, in the list of results for a FRBR group, you will see a very generic record which is hardcoded and…33 votes -
Make DOIs active links in full record display
It would help users connect to content if the DOI in the Identifier field were an active link. This could either be through adding "https://doi.org/" in front of the DOI to display a complete URL, or by simply adding that to build active links behind the scenes. For example, use https://doi.org/10.48331/scielo.LS5RKD rather than DOI: 10.48331/scielo.LS5RKD
This would be especially helpful for open access content in the CDI that is often displayed to users without any links to follow. Copying and pasting the DOI by itself into a browser search produces inconsistent results that often fail to go to the right document.
It would help users connect to content if the DOI in the Identifier field were an active link. This could either be through adding "https://doi.org/" in front of the DOI to display a complete URL, or by simply adding that to build active links behind the scenes. For example, use https://doi.org/10.48331/scielo.LS5RKD rather than DOI: 10.48331/scielo.LS5RKD
This would be especially helpful for open access content in the CDI that is often displayed to users without any links to follow. Copying and pasting the DOI by itself into a browser search produces inconsistent results that often fail to go to…
3 votes -
Create/add in the ability to show and filter ALL content by place of publication and other data point relevant for decolonising collections
With linked data being such a big part of what has being talked about so far in relation to NDE and AI being used in some new projects such as Primo:Research Assistant, we feel that it's the best time to think about using this data and the data in the CDI records to try and develop tools to identifying, show, filter place of publication or nationality of authors.
We have developed our own facet using local fields, regular expressions and information in the MARC 008 to display the place of publication for items in our collection and filter by facet on them too. This was based on instructions found here : https://knowledge.exlibrisgroup.com/Primo/Knowledge_Articles/How_to_create_a_dynamic_facet_in_Primo_VE
Our Primo instance with it added can be found here : https://shu.primo.exlibrisgroup.com/discovery/search?vid=44SHU_INST:44SHU_VU2
This was developed following requests and with great interest and appetite from our (subject) librarians for more tools to help with decolonising and diversifying our collection. However, because of using the local field creation this is only working for our local records and can't be applied to the everything search option that encompasses CDI records. Something that would work for all records would be our preference.With linked data being such a big part of what has being talked about so far in relation to NDE and AI being used in some new projects such as Primo:Research Assistant, we feel that it's the best time to think about using this data and the data in the CDI records to try and develop tools to identifying, show, filter place of publication or nationality of authors.
We have developed our own facet using local fields, regular expressions and information in the MARC 008 to display the place of publication for items in our collection and filter by facet…
5 votes -
Include authentication in QR Code link for favourites
On Primo VE you can generate a QR Code for the page you are viewing.
If the page is a search the QR Code link works, once scanned the search is replicated.
If the page is from your account, LibraryCare, My Loans, My Requests, when the code is scanned it invokes authentication.However, for Favourites, when the code is scanned it shows a "blank" screen if the user isn't already authenticated on the scanning device.
I would like to propose that the link generated for Favourites invokes authentication in the same way as pages for Loans, Requests etc,
1 vote -
Add clickable logo option next to search bar
Some libraries like UCLA have edited their customization packages with custom javascript, CSS, and HTML to add a logo with an embedded link that will take the user back to the main Primo page. This is a useful feature, especially if the default upper left logo is pointed at a library's main web page instead of to Primo, but implementing similar code in other institutions' customization packages can be challenging--especially if it interferes with existing code for other functions. Having a second default logo with link option in this Primo location would be helpful for libraries that want this configuration option.
Some libraries like UCLA have edited their customization packages with custom javascript, CSS, and HTML to add a logo with an embedded link that will take the user back to the main Primo page. This is a useful feature, especially if the default upper left logo is pointed at a library's main web page instead of to Primo, but implementing similar code in other institutions' customization packages can be challenging--especially if it interferes with existing code for other functions. Having a second default logo with link option in this Primo location would be helpful for libraries that want this configuration…
10 votes -
Allow fields available in the CTO to be used in General Electronic Services (GES)
Fields found in the CTO should be available to use in url templates and service availability rules within General Electronic Services (GES).
We use some GES's to link out to our resource sharing system that uses OpenUrl parameters in the url template. We've discovered that many books only have editors and don't include that information in the general author attributes within the CTO. Instead, the editor gets added to rft.sau in the CTO and it is the only field in the record that contains editor information. If you add this field to the url template in the GES and you get an error (error message = "The URL Template you entered contains invalid parameters: rft.sau").
I submitted a support case through Alma, which got transferred to the Primo team, and was closed with a comment about Alma not being designed to do this and to submit an idea exchange.
Here are some examples where any author related information is only available in the rft.sau field.
Finally, because these are not local records, there is no workaround to add the editor field to other fields and get used within other existing and working openurl fields.
Fields found in the CTO should be available to use in url templates and service availability rules within General Electronic Services (GES).
We use some GES's to link out to our resource sharing system that uses OpenUrl parameters in the url template. We've discovered that many books only have editors and don't include that information in the general author attributes within the CTO. Instead, the editor gets added to rft.sau in the CTO and it is the only field in the record that contains editor information. If you add this field to the url template in the GES and you…
5 votes -
book reviews- link to book
Book reviews can be useful, but frustrating for the patron. I would like to see the actual book info linked from the review, so the patron can request a purchase or ILL easily.
4 votes -
Que Primo tenga en cuenta todos los tipos de comillas posibles
Actualmente sólo el carácter UTF-8 22 (UNICODE 0022) se considera como comilla en las búsquedas Primo. Se trata del carácter ", accesible mediante Mayúsculas-2 en la mayoría de los teclados.
Pero otros dispositivos y telcados utilizan otros tipos de caracteres, que Primo no tiene en consideración a la hora de ejecutar las búsquedas, y así, cuando se introduce una búsqueda entre comillas, los resultados varían según el dispositivo que utilice cada usuario, porque si Primo no detecta que esos caracteres son comillas, combina las palabras de búsqueda con el operador OR.
Entendemos que es necesario que Primo tenga en cuenta todos los tipos posibles de comillas para facilitar a los usuarios que obtengan los resultados que están buscando, y no otros, cuando lanzan su búsqueda entre comillas, sea cual sea el teclado que utilicen.Actualmente sólo el carácter UTF-8 22 (UNICODE 0022) se considera como comilla en las búsquedas Primo. Se trata del carácter ", accesible mediante Mayúsculas-2 en la mayoría de los teclados.
Pero otros dispositivos y telcados utilizan otros tipos de caracteres, que Primo no tiene en consideración a la hora de ejecutar las búsquedas, y así, cuando se introduce una búsqueda entre comillas, los resultados varían según el dispositivo que utilice cada usuario, porque si Primo no detecta que esos caracteres son comillas, combina las palabras de búsqueda con el operador OR.
Entendemos que es necesario que Primo tenga en cuenta…1 vote -
Add a top-level "Discipline" facet based on the complete HILCC Hierarchy
I see that a "Journals by Category" feature was recently added, but it only appears on the journal search screen, and appears to omit much of the HILCC - for example, there is no category for "Performing Arts", much less for specific performing arts like "Dance" which we're used to seeing in Summon.
1 vote -
Inform patrons about Pick from Shelf
This is something we are really missing since we switched to Primo VE.
I find a book I want to borrow, my library has it, but it's open stacks, which means I can't request it online to be picked up in the owning library.
In our older catalog we had a pop up message to inform the patrons that they can fetch the item from the shelf themselves.
DTU (https://findit.dtu.dk) solves it like this, which is exactly what we need - see screenshot dtu1.png
Under B, we'd show the possible pickup locations, as we do now.
A is missing in Primo VE.
How it looks before I click on Borrow: see dtu2.png
You don't have to be a member of DTU to open a patron account.
This is something we are really missing since we switched to Primo VE.
I find a book I want to borrow, my library has it, but it's open stacks, which means I can't request it online to be picked up in the owning library.
In our older catalog we had a pop up message to inform the patrons that they can fetch the item from the shelf themselves.
DTU (https://findit.dtu.dk) solves it like this, which is exactly what we need - see screenshot dtu1.png
Under B, we'd show the possible pickup locations, as we do now.
A is…
36 votes -
Add "read more" button to allow for collapsing of long collection descriptions in collection discovery
Many of our contributors use the collection description field to provide detailed information about the materials within, some are over 5-6,000 characters. Descriptions this long force the banner image to become stretched and visibly unappealing; it also pushes the records down to where the user needs to scroll to see them. It would be great if there were a collapsable carrot or "..." or "Read More" button at the end of some predetermind amount of characters to shorten descriptions by default, but also allow users to read the entire piece of text if so desired.
3 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 -
Highlight OCR text within image in Viewer, not just in full text field
Digital representations seen in the Alma-D Viewer, accessed through Primo, are often PDFs with OCRed text. These items have a "Full Text" field with this text displayed with the item's metadata in the side pane, and using a browser's "CTR+F" function will highlight results for a searched word, but this functionality would be helpful if it also extended to highlighting the word in the image as well. In dense newspapers, for example, the user may find the needed word in the block of full text, but he would then need to examine the image carefully to track down the instance of its original appearance.
Digital representations seen in the Alma-D Viewer, accessed through Primo, are often PDFs with OCRed text. These items have a "Full Text" field with this text displayed with the item's metadata in the side pane, and using a browser's "CTR+F" function will highlight results for a searched word, but this functionality would be helpful if it also extended to highlighting the word in the image as well. In dense newspapers, for example, the user may find the needed word in the block of full text, but he would then need to examine the image carefully to track down the instance…
2 votes
- Don't see your idea?