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.
24 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.
756 votesThank you for this idea. We are currently reviewing it and discussing it also with the Alma team.
-
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.
-
Less duplicate records in Primo Central Index results
Primo Central grouping is based on the existing FRBR workflow, including the grouping process at the database level (the way the Search engine handles grouping) and the Front End functionality. It is used to prevent duplicate records in the results list.
Unfortunately, many records are not added to FRBR groups because the system considers the metadata are not rich enough. With the increase of records provided by (Open Access) aggregators and repositories, the number of duplicate records will certainly not decrease.
Could Ex Libris improve the FRBR workflow for Primo Central records in order to reduce the number of duplicate
…203 votes -
The new Give Us Feedback Tool should provide information about the end users IP
Access to electronic resources our library subscribes to is IP-based. If the user's IP address belongs to the university's IP range, they are recognized when they go to the resource and do not experience any access problems. Most of the issues reported to our support team come from students who forgot to turn on the VPN. Adding the IP address information to the feedback message would save us a lot of time in processing such issues.
201 votesThank you for this idea.
We will consider adding the IP address to the Give us Feedback email.
Best regards,
Yael.
-
Primo VE: Re-instate the A-Z browse function for DATABASES
Re-instate an A-Z browse option for Primo VE Database Search, like the one available for Primo Classic.
197 votesThank you for this idea. We are currently examining it also as part of the NERS voting (7820).
-
View user request history
We would love to be able to view a user's request history in the Requests tab of their account. You can view Returns and Fines histories so why not Requests?
This would be very useful for students and staff! Thanks.193 votesThank you for this suggestion. we are checking the option to allow view history of requests same as we provide history of loans .
-
Move Peer Reviewed into it's own facet group
The Peer Reviewed facet is currently grouped in the Availability facet group. It has nothing to do with Availability or the other things in the Availability facet group. Not seeing another facet group that makes sense, Peer Reviewed should be in it's own facet group. This will make more sense to the user, allow more flexibility in controlling the placement and the look and feel of these individual facets.
160 votesHello,
Thank you for suggesting this idea - we are currently examining this option.
Best regards,
Yael.
-
Only show "starts with" for relevant fields
Currently, the "starts with" functionality is only available for title searching. There are already some posts here about adding it for other fields, like call number and subject, which I support. This post is about the current behavior though. If I choose to search by another field, such as author/creator or subject, then the next dropdown allows me to choose "starts with" even though it's not available, and it immediately switches to a title search. I'd prefer that, if a user has selected a field other than Title, that "starts with" just wouldn't show up at all. If the task…
160 votesThank you for this idea.
We are considering adding a tooltip to the "Starts with" search operator, rather than displaying it only for the "Title" field.
The tooltip will explain that this search option is available only for the "Title" field.
We believe that if we won't display this search operator at all for the other fields, the user will not know that this search option is possible, since the default search is usually done on the "Any" field.
Thanks
-
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.
147 votesThank you for this idea. We are currently reviewing the option to allow configuration of the "Course information" field.
-
Hide completed purchase requests from the Primo MyAccount
Completed purchase requests (rejected or approved) should not be visible in the Primo MyAccount.
143 votesThank you for posting this suggestion, we are considering the option to add a Request Type Filter to help users filtering requests by type (ILL, Purchase, Digitzation, Request ,… )
-
Review content type in Primo is confusing
Currently the Review content type in Primo / Primo Central seems to contain both Book Reviews such as
http://shu-primo.hosted.exlibrisgroup.com/44SHU_VU1:default_scope:TN_sciversesciencedirect_elsevierS0261-5177(06)00203-2and Review Articles such as
http://shu-primo.hosted.exlibrisgroup.com/44SHU_VU1:default_scope:TN_proquest1373464971It would be better if these were in separate content types.
142 votes -
Add a field ISSN and E-ISSN that are separated but can be matched for Dedup / F
For more efficient DEDUP of ejournal and print journal.
The dedup test mach ISSN, but the ISSN of printed journal record is usually different from the e-ISSN of the electronic journal record, thus there is no match between two these numbers.121 votesThank you for this idea. we are considering to add a new key to answer the needs, but first we would like to get examples where a separate key for ISSN and EISSN are needed
-
Generate citation on multiple pinned items
Our users make heavy use of the generate citation button, but they currently have to do this one record at a time. It would make things easier for them if they could pin all the relevant items, and then go into My Account, select all their pinned items, and generate a citation for all of them.
They can currently perform several actions by batch on all pinned items - email results, export to Refworks and so on - but the generate citation action is not yet available to them.
The citation that appears could be simply plaint text, with the…
119 votesThank you for posting this suggestion. I would like to get your input if this can be added as part of the email action where user can select in which citation style to send the selected records
-
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 -
Combining searches from search history into a new search
My colleagues misses the functionality from our previous discovery system to combine searches in the search history list into a new search in an easy way, e.g. S1 AND S3
92 votesThis is to update that this idea is currently under review (also as part of NERS voting - 8258).
-
Analytics - advanced search stastistics
Hi there,
According to SF case 422111 it's currently not possible to provide detailed statistics about advanced search field through OBI.
As for the facets, we would like to know the number of using field by field.
For example :
- We would like to know how many clicks were done on search field "Topic"
- We would like to know how many clicks were done on search field "Author"
- We would like to know in how many session the search field document type / books was used
- Which are the fields the most used in the advanced…81 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 votes -
Version control system for back office configuration
A version control system for back office configuration tables, pipes, normalization rules etc.
For files like Custom HTML, CSS, JS, PDS etc. we can manage change history and revert to older versions by using version control systems like Git, Subversion etc. For configuration managed via the web back office and database this is not possible, but it is a vital feature of professional system management. This will become more important in a full SaaS environment.63 votes -
Allow patrons to disable FRBR + disable FRBR in advanced search
Hi
Our patrons run into a lot of problems caused by FRBR.
Please
– Add a checkmark to allow the patrons to disable FRBR per search, no matter if logged in or not.
(like "Include articles without fulltext")– Make it a parameter in the patron settings
– Disable FRBR as default in advanced search
This could also be used as a feeble workaround for the missing exact search https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/18579556-add-a-true-exact-search-to-advanced-search-type
58 votesThank you for posting this idea. We are considering to have a new toggle
""group versions together" where users can choose to if to have search results grouped by versions or turn it off.
-
Show e-collections activated in the NZ in the Database Search of IZs
In our network we activate certain Open Access e-resources in the Network Zone. These e-collections are activated for every IZ without restriction. Some of our Institution Zones are using the Database Search to allow Patrons to search for their e-collections. Unfortunately, the Database Search is showing only e-collections that are activated and have inventory in the IZ. It does not show any of the Network Zone e-collections.
We would like to have the option to include the Network zone activated e-collections in the Database Search of the IZs.
53 votesThank you for posting this idea. We are checking the option to enhance Database Search scope to include also e-collections that are available for all not only for the specific IZ.
- Don't see your idea?