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 ~
647 results found
-
My Library Account: add Recalled Loans Tab
It would be very beneficial for library patrons to be able to view their recalled loans, at a glance, when checking their library account in Primo; please could you add a Recalled Loans tab to the Overview section of My Library Account
168 votes -
Optimize call number Advanced Search
Currently you can conduct an advanced call number search, but there are a few issues with it:
-It doesn't properly search the entry as a call number like the Browse function does. It treats it like a regular word which results in severely incomplete results. For example, if I do advanced search > call number > contains > MT, I receive 90 results, though we have 3,578 items with call numbers that begin with MT.
-The only way to see a mostly accurate number of holdings is to search partial numbers + an asterisk. For example, MT* returns most of our 3,578 items. Most users would not think to search with an asterisk.
-When limiting an Advanced Search by Call Number, the only limiters available are Contains and Is(exact). Starts With appears to be an option until you click on it, and then Call Number changes to Title which becomes unavailable to change. Starts With would be the best and most logical limiter for users for a call number search, but it's not available.
-The Contains limiter does not appear to function correctly. For example, I receive results when searching Advanced Search > Call number > Contains > M1003 .H64, but no results when I search M1003 .H.
(I submitted ticket 00523629 regarding these requests, and was advised to post them to the Idea Exchange.)
Currently you can conduct an advanced call number search, but there are a few issues with it:
-It doesn't properly search the entry as a call number like the Browse function does. It treats it like a regular word which results in severely incomplete results. For example, if I do advanced search > call number > contains > MT, I receive 90 results, though we have 3,578 items with call numbers that begin with MT.
-The only way to see a mostly accurate number of holdings is to search partial numbers + an asterisk. For example, MT* returns most of…
72 votes -
Numerical order for Search by list
We would like the list search in Primo to show the results in numerical and not just alphabetical order.
For example, for call numbers the number 101 should appear before the number 1000.
Thank you and good day.
Alberto (Italy)43 votes -
Allow admin to select in what order Resource Types are displayed
Currently the Resource Types can only be arranged alphabetically or by count (how often the type appears in search results). We would like to be able to preference certain types above others (for example, books, ebooks, articles...over things like Text Resources. So that for any search, the Resource Types are always arranged the same way and in a way that is most helpful for users.
58 votes -
An option to move the send-to section in Primo VE
We would like to be able to control the location of the send-to section in the Primo VE full record display.
101 votes -
Ability to share favorites
We'd like to see a more robust favorites area, with more options for configuration. One thing in particular we'd like would be the ability to organize lists of favorites, then to share those with other users. This has been brought up by librarians who'd like to work on lists collaboratively and then share those lists with students or instructors.
51 votes -
Browses: add See Also and Usage info from authority headings
Primo supports display of See references (not same as See Also) in browse headings, if those cross-references are in the bibliographic data ingested by Primo. There is no capacity to display See Also and Usage info from authority records, which are important so that users understand how and why certain terms, especially subjects, may be used.
We propose that See Also and Usage info display in the Browse headings.
Example headings and See Also and Usage info that does NOT currently display in Primo:
Blacks:
Search also under: subdivision Blacks under individual wars, e.g. World War, 1939-1945--Blacks; and headings beginning with the word Black
Here are entered works on blacks as an element in the population. Theoretical works discussing the black race from an anthropological point of view are entered under Black race.It's possible this enhancement could be achieved through application of an API that interacts with Library of Congress systems. Display of narrow/broader terms would also be highly valuable.
Primo supports display of See references (not same as See Also) in browse headings, if those cross-references are in the bibliographic data ingested by Primo. There is no capacity to display See Also and Usage info from authority records, which are important so that users understand how and why certain terms, especially subjects, may be used.
We propose that See Also and Usage info display in the Browse headings.
Example headings and See Also and Usage info that does NOT currently display in Primo:
Blacks:
Search also under: subdivision Blacks under individual wars, e.g. World War, 1939-1945--Blacks; and headings beginning…
202 votes -
Improve usability of exclude/include facet options
Based on recent usability testing of the new UI we have found that our users appeared to be confused about how to include and exclude facet options from their results set. One of the main pain points seemed to be that they did not know that they were able to exclude a specific facet option (for example to exclude English items from the results set most of our users ticked all options under the language facet other then English rather then just excluding the English option).
At the moment the option to exclude only appears when someone hovers over the facet option, and it appears on the right of the text of the facet option. Although the option to include a facet also only appears when the mouse hovers over the text of the facet option because it appears on the left of the text it is more obvious, as users will be reading left to right, then something that appears after the text.
We feel the overall usability of the exclude/include facet option functionality could be improved by:
- Moving the exclude option so it is next to the include option on the left of the facet options
- Both options are made static so users are aware there are filtering options without the need to hover over the text of the facet option.
- Currently a tool tip exists for the exclude option, but there isn't a equivalent tool tip for include. We would like a tool tip to be available for both options.
Based on recent usability testing of the new UI we have found that our users appeared to be confused about how to include and exclude facet options from their results set. One of the main pain points seemed to be that they did not know that they were able to exclude a specific facet option (for example to exclude English items from the results set most of our users ticked all options under the language facet other then English rather then just excluding the English option).
At the moment the option to exclude only appears when someone hovers over the…
121 votes -
Add 245 subfield c to Primo display
Please add the 245 subfield c to the display in Primo. It does display in Alma. In the example below, you are not able to determine the author/creator's responsibility for the work - Author vs. forward vs. photographer.
We would love to have more granularity in general for what fields/subfields display in Primo for our specific institution.
Thank you!
87 votes -
Generate a report of the MMSID's harvested by Primo Back Office
We would like to be able to generate a report of the MMSID's harvested by Primo Back Office.
56 votes -
Embargoed resources displaying in Primo
Currently records from within an embargo period are discover-able to end-users via Primo.
The user then thinks we have access to the records and selects it only to be presented with No full text available.
Embargoed records are outside of our coverage range and should not display in our discovery interface.60 votes -
EZProxy (Primo institution wizard) more granular application against specific collections
Currently in Primo institution wizard (Primo Home > Ongoing Configuration Wizards > Institution Wizard > Delivery Base URLs) you can enter an EZProxy base URL. If a proxy is added it will be applied to all Link in Record type resources (though there is the option to exclude OA collections). I would like more granularity so that we could choose to apply the proxy to certain Link in Record type collections, but not to apply the proxy to others.
120 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
308 votes -
Put useful data into the RSS feeds created by Primo
Technically RSS feeds created by Primo are working. But from a content perspective the feed is a mess.
Let's start with the feed header:
Primo delivers <rss version="2.0">
The standard specification are at http://www.rssboard.org/rss-specification . It was published in August 2002. The RSS 2.0 specification is copyrighted by Harvard University and is frozen. Please use RFC 4287 also known as Atom.
https://tools.ietf.org/html/rfc4287
It is simply the better option for may reasons.
http://www.intertwingly.net/wiki/pie/Rss20AndAtom10ComparedThe description of the feed is <title>Records from Primo</title> .
As a user I would like to see my search terms in the feed title - like in the brief result screen in the web interface. At minimum it should be the name of the service where this feed is coming from. The name of software used to create the feed is useless to a reader.The link to the source is pointing back to the Primo main page with the classic user interface. But that's confusing for institutions using the new user interface!
Let's have a look to a feed item:
A cruical element of RSS feeds is the
<pubDate>Thu, 09 Nov 2017 16:25:22 GMT</pubDate>
The specification says: "Its value is a date, indicating when the item was published." In a Primo feed this is always the same date; I assume it is the time stamp when the feed was created. Please change this immediately. RSS management software cannot handle it because the pubDate is used for chronological sorting and to find out what's new. What's needed is the publication date of the publication or second best the date and time when the record was added to the Primo index.The delivered link in the link field is "the URL of the item". It's pointing back to the full view of the record in Primo. That makes sense. But if available I would like to get the OpenURL here because I want to connect my users to the article or the service page and not to the Primo record again. It's fulfillment at this point!
Why the same link is also in guid is a mystery to me. RSS standard says: "guid stands for globally unique identifier. It's a string that uniquely identifies the item. When present, an aggregator may choose to use this string to determine if an item is new." What about the PNX ID?
Last not least the description:
<description>Plasmodium Falciparum -- Analysis ; Proteases -- Analysis ; Proteins -- Analysis ; Phosphates -- Analysis ; Malaria -- Analysis;</description>
Often it incorporates only "N/A" or sometimes subject headings. But the description should include the same information as the brief view in the web interface of Primo like bibliographic information, identifier, subject headings, language, etc. This is what the user will see in his feed reader of choice or what a feed aggregation system can use to give meaningful context for the title of this item. Of course it's tricky because a Primo search delivers very different types of content with very different metadata. Books have authors; journals have not. Articles are published in a journal and pictures have a resolution and digital objects have a file format.Today there are no customization options for the feed content. If the settings of the brief view are applied to the feed too, it would improve the item description massively and solve the description problem. This need is solved for the export to a reference management software. The RSS feed for a query is not so much different from that.
Technically RSS feeds created by Primo are working. But from a content perspective the feed is a mess.
Let's start with the feed header:
Primo delivers <rss version="2.0">
The standard specification are at http://www.rssboard.org/rss-specification . It was published in August 2002. The RSS 2.0 specification is copyrighted by Harvard University and is frozen. Please use RFC 4287 also known as Atom.
https://tools.ietf.org/html/rfc4287
It is simply the better option for may reasons.
http://www.intertwingly.net/wiki/pie/Rss20AndAtom10ComparedThe description of the feed is <title>Records from Primo</title> .
As a user I would like to see my search terms in the feed title - like in…55 votes -
“My Favorites” pin should indicate number of records in favorites
In the Primo New UI, there is the “my favorites” pin icon at the top right of the screen (screenshot below of the pin). We ran some usability surveys and found that users would like an indication, via the icon, that something is there. Like the number if pinned items and/or a different color indicating that something is there.
45 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
95 votesThis is currently not planned to be developed. We might evaluate it again in the future.
Currently we are removing the "Under review" status.
-
List of Loans - Indicate if item is Requested
It should be possible to indicate in the patron's List of Loans in the Library Account whether an item is requested, otherwise, it is not clear if the due date is sooner than on other loans because it is a Reserved item or because it was Requested by another reader.
54 votes -
Allow to delete records in Primo BE ( included dedup records )
Right now the only way to delete a record in Primo is to refer to a KB Article [1] explaining how to write an xml OAI-PMH record with status 'deleted' and let the xml file to be ingested by a pipe. The procedure is cumbersome and error prone (e.g. issues with compression of the file on non linux machines etc.) and it does not always work properly. For example, dedup records are not properly deleted by this procedure.
It would be good to provide a feature in the Primo BE allowing to look for specific PNX and to delete it. This should work with both plain records and dedup records.
Right now the only way to delete a record in Primo is to refer to a KB Article [1] explaining how to write an xml OAI-PMH record with status 'deleted' and let the xml file to be ingested by a pipe. The procedure is cumbersome and error prone (e.g. issues with compression of the file on non linux machines etc.) and it does not always work properly. For example, dedup records are not properly deleted by this procedure.
It would be good to provide a feature in the Primo BE allowing to look for specific PNX and to delete it.…
44 votes -
Primo Central Index ( PCI ) - more granularity in excluding content from activated resources - e.g. exclude from index by resource type
Right now in Primo Central Index the customer can either activate or not a resource. But sometimes more granularity would be appreciated. Namely adding a filter by resource type allowing inclusion or exclusion in the index would be very useful. Please note: it's not a matter of adding a resource type in PCI. It's a matter of excluding records with a specific resource type from activated resources.
For example, some resources/data sources contains not only articles, but also journals and other resource types we actually catalogue. Since right now dedup does not work between local records and PCI, this ends up leading to a lot of duplicated entries in the search results (1 for the journal in the catalogue + 1 for the same journal in PCI).
Allowing us to exclude Journals from PCI, thus having only articles, would greatly reduce noise and bias in the search results.Right now in Primo Central Index the customer can either activate or not a resource. But sometimes more granularity would be appreciated. Namely adding a filter by resource type allowing inclusion or exclusion in the index would be very useful. Please note: it's not a matter of adding a resource type in PCI. It's a matter of excluding records with a specific resource type from activated resources.
For example, some resources/data sources contains not only articles, but also journals and other resource types we actually catalogue. Since right now dedup does not work between local records and PCI, this ends…
100 votes -
Add a search results permalink to the New UI results page
When we do searches in Primo for patrons, we often want to be able to send them to a list of results, rather than a specific item.
There is a jquery customization the classic UI created by Western Washington University at https://www.orbiscascade.org/blog/9/?bid=121
However, that customization does not work on the new UI, and requires users to be able to create a SQL database to store redirects, and to store files on a local server.
Ideally, search results permalink functionality could be built into Primo's New UI.
The attached screenshot shows the WWU search results permalink in action.
39 votes
- Don't see your idea?