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.
64 results found
-
Allow for consistant customizations in the new UI
The open discovery of the new UI allows customers to customize the new UI, extend its functionalities, and connect Primo with external services.
This framework can offer an important added value to institutions; it can enable them to respond to specific needs of their user community.
We want to implement extensions for functionalities like:
• Offer a button “report a problem” that allows a user to report a broken link or another problem with a specific source he found. The form sends this message to our helpdesk, together with useful debug info like : is the user on or off…205 votes -
Bib MARC field 561 should be indexed in the Primo PNX file
The MARC 561 field in the bib should be indexed in the Primo PNX file for searching by donors of collections and for patrons seeking metadata from those collections.
1 vote -
Allow requests or display request link without sign in
Some items (for us, things in our storage system) should be request-able for all patrons regardless of status. It would be nice if there was a way to specify, in Alma or in Primo, that some locations should always display a request link, even if a user is not logged in. Ideally, users would be able to request from these locations without requiring a login.
3 votes -
Allow for integration with the PaperPile citation manager to Primo VE
PaperPile is a citation manager that integrates with Google Docs. We'd love to see citations that are available to be scraped by it in Primo.
1 vote -
OAI Pipe date options to facilitate CONTENTdm automated harvesting
We would like our pipe that harvests the OAI feed from CONTENTdm to run automatically either weekly or monthly.
However it is a known bug with CONTENTdm that if the collection is large, and if a small date range is used with the OAI data feed, then the process is likely to hang.The current workaround with Ex Libris is to manually set the start date to 100 years ago, and then run the pipe.
The enhancement I would like is enhancing the pipe configuration to either add
a.) A checkbox which adds the option of not automatically updating the start…
25 votes -
Create link for patron to report issue with Primo Central Record
This idea comes from a ticket submitted by a professor last week regarding a journal article resource that was marked as "peer reviewed" in PCI incorrectly. She reported it to us and we reported it to ExLibris, but it would seem more efficient to include a link that could report the problem directly to ExLibris for PCI content. I imagine something similar to the "report an issue" link found in google books: https://www.screencast.com/t/BdLZo2tR6D
57 votes -
Ability to configure New Primo to force patrons to sign in
In the classic Primo, we were able to configure force login using the javascript in the KB Article https://knowledge.exlibrisgroup.com/Primo/Knowledge_Articles/How_to_configure_Primo_to_force_patrons_to_sign_in
The KB article is for classic UI only.
Due to security, we need to force user login.
17 votes -
Add a prm-alma-mashup-after angular directive
It's hard to work with the alma-mashup without the prm-alma-mashup-after directive and the lack of the directive is inconsistent with the rest of the markup in Primo.
21 votes -
Getit2 of PrimoCentral records lists irrelevant local resources (missing date check)
Records from Primo Central have a getIt2-Tab which lists print resources from local catalog for an article. The problem is that the publication date of the article and the listed resources do not match and therefore cause confusion. Think of an current article from a Journal and you get old volumes suggested from the library. Only print resources containing the article should be listed.
In other words: The function would be usable if the getit2 lists print resources with the same publication date.Suppressing the get-it tab according to the documentation (http://knowledge.exlibrisgroup.com/Alma/Knowledge_Articles/Remove_GetIT!_Tab_When_No_Print_Version%2C_Only_Electronic_Records_from_Alma) has no effect.
The issues were…
26 votes -
• Records without a date at the bottom of results list when sorting on date oldest
At this moment, the sort option “Date oldest” displays the records without a date on top of the results list. This is confusing and not relevant for users; when there are several records without a Creation Date they probably conclude that sorting on date oldest doesn’t work. Our request is to display the records without a date always at the bottom of the results list when a sort option on date is used (thus as well for date oldest as for date newest)
80 votesHi all,
This is to update that this is currently not planned to be developed. We might evaluate it again in the future.
Therefore we are removing the "Under review" status for now.
Best regards,
Yael.
-
Index Ebsco API "abstract" Results so they don't appear in Primo "Full-Text" Results
All Primo results from the EBSCO API are searched and displayed "on the fly," and there's no option to sort the abstract-only content from full-text in Primo results.
So even though our default in Primo is to display ONLY "full text" results -- Primo is returning EBSCO "abstract only" or "may be full text" links in our Full-Text searches. Our users are confused, and call us wondering why they don't have full-text access in our Primo full-text search results.
Finding a way to sort the Ebsco abstract-only content from the full-text content, so it's working correctly within the Primo search…
17 votes -
Create a Tableau Web Data Connector for Primo Analytics
Primo Analytics users who also use Tableau would benefit from a generic Tableau Web Data Connector (WDC) available via a Primo Integrations page to integrate Primo Analytics into Tableau vizes via the Ex Libris API.
The WDC could generate report-specific field structure based on the schema/xsd section of the API report XML, making the addition of Primo Analytics report data to Tableau as easy opening an Excel spreadsheet.
Since I do not have Primo, I have not been able to test these as I did with Alma, but this idea is based on the assumption that Primo Analytics reports API…29 votes -
Real Time Availability for Electronic Resources
If a resource from Alma is unavailable to a end user due to a campus or IP restriction and receives the "No Full Text available" message, then update the "Online Access" green dot to "No Full Text/Red Dot" or "Sign In for access options/ Yellow dot"
112 votes -
Add the 'until' argument to OAI-PMH pipe configuration
When creating a pipe to harvest using OAI, we can currently set the 'from' date but not an 'until' date. When harvesting from a large repository, this means we have to collect the whole set in one go - which may be a problem for Primo and/or the repository. We would prefer to process, say, three months data at a time.
6 votes -
Full integration of Syndetics enrichment content
Syndetic Solutions enrichment content should be indexed in Primo, to aid the retrieval of books (especially by chapter titles in TOCs) and displayed inline in the new Primo UI. The acquisition of Ex Libris by Proquest should make this commercially easier to arrange, and it should be technically easier on the Primo "cloud" platform.
208 votes -
Adding 'Issue' as a new resource type in Primo Central
Resource types used in Primo Central are limited to 23 (book, article, journal, image...) [See pdf "Primo Central Index Resource Types" in the Documentation Center].
For digitized journal issues, the type in use is 'journal'. Archive collections like HathiTrust may contain tens of thousands of digitized journal issues; institutional repositories may also contain complete issues… This is finally confusing for end-users for who see issues labelled as journals and for whom filtering by resource type has become useless.
Adding a 24th type 'Issue' for this material would be welcome! ‘Journal’ would thus only remain for real journal records.
93 votes -
Increase number of citations that can be pushed to citation manager tools
Our users would like to be able to send more than the current limit of 30 citations at a time to tools like Refworks and Easybib.
22 votes -
Different RTA status messages for items on loan and missing items
Today the message "All items checked out from ..." is shown both for items on loan and items with process status "Missing" in Aleph. We would like to have different messages reflecting the real process status of he item.
5 votes -
Add 562 data from holding record to Primo GetIt tab
Additional Holdings Information can be displayed in Primo GetIt tab, but only some fields of holding record can be used : 867-868-541-561-563-852t.
We would like to have also 562 holding field, which permit us to give a Copy and Version Identification Note for an item. (Subfields $a $b $c would be fine.)1 vote -
Export from SFX thru MARCIt and pipe up to Primo without the need to load SFX content into Catalog by Creating Normalization Rules
Instead of having to: load MARCIt-enhanced SFX e-records into our Library catalog every month, and then export them from our catalog up to Primo...
It would be more streamlined to have them: export from SFX > thru MARCIt (for extra indexing) > and then straight up to Primo where they'd be normalized and searchable.
This would reduce support time, and our catalog record load, while still having all our content indexed and searchable in Primo.
3 votes
- Don't see your idea?