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.
1136 results found
-
Improve Display Logic in Alma Uresolver to show all variant coverage statements in a collapsed menu
Ideally, Alma should be able to display ALL unique variant coverage statements when showing a collapsed menu.
If a library uses the Display Logic rules to for example show Proquest as an option only once in a services menu, this works very well where a journal may be in 12 Proquest databases with the same coverage.
However, when the coverage varies significantly between these databases, Alma uresolver will still just show one of the coverage statements and a user will only see a subset of holdings and believe this is all the library has. (eg Nursing standard in Proquest is…
159 votes -
RefWorks export: the maximum amount of records that can be exported to Refworks from Primo is 30. Make this number configurable to allow mor
RefWorks export: the maximum amount of records that can be exported to Refworks from Primo is 30. Make this number configurable to allow more records.
5 votes -
Don't filter out Primo Central records after clicking Library facets
On a blended scope, when you search in the scope and click a library facet, all the Primo Central records are filtered out because Primo Central records do not have facets:library values in PNX. For example,
(1) Go to our Primo:
http://kosmos.lib.keio.ac.jp/primo_library/libweb/action/search.do?vid=KEIO
(2) For your convenience, click "English" as UI language on the upper-right corner.
(3) On the "All materials" tab, search "cancer" (without quotes). The "All materials" scope is a blended scope that contains both local records and Primo Central records.
(4) On the Library facets, click any library.
Then all the Primo Central records are filtered out. But…
4 votes -
Primo Analytics: extracts the usernames related to failed logins
It would be great -with Primo analytics- building an analysis that extracts the usernames related to failed logins
47 votes -
Send email when pipe finishes with errors.
When a pipe finishes normally, but some records did not load due to errors, right now the only way to find out whether that happened or not is to go into the back office, Monitor Primo Status, Pipe Monitoring, and click on "Errors" next to the pipe (and a futher step to get to "History" if the pipe is not the last one run).
We run four Alma pipes a day, and around a half dozen other pipes once a day. WE DON'T HAVE TIME TO DO THIS and I bet a lot of other customers don't either.
But we…
25 votes -
Backoffice REST API and Hooks
Alma provides a growing number of API's for process orchestration and Hooks will come soon.
Primo only provides REST API's which are mainly used for Frontend interaction.
Primo is missing API's and Hooks to control Tools, Pipes, Processes and Schedules to implement fully automated workflows for Alma or other ILS.
I would be great to see such API's and Hooks soon, please vote!
5 votes -
When there is more than one copy of a printed book, display the copy number in the call number. For example: N5300.S923 2008 v.1 c.2
We have two copies of vol. 1 of Stokstad's 3rd ed. of Art History. Thus, the call number for the second copy would display like this:
N5300.S923 2008 v.1 c.2
22 votes -
alerts based on a range of call numbers
We would like our users to be able to define an alert in primo, based on a range of call numbers – for example:
lc = "ds67->ds79.99" .37 votes -
Second sort in facets
Currently, Primo shows the items in the facets (e.g. the subjects facet) either sorted alphabetically or by the number of items.
However, it seems to order the items randomly when the number of items is identical for several different subject heading in the facet.
It would be beneficial to be able to configure a secondary sort option for these items (for example when using a multilingual subject heading system - to present the same subject in both language one after the other).83 votes -
Allow the view code field to be editable
To enable seamless updates to the Primo interface it would be useful for the Code for the view to be editable.
This would allow you to continue to use the same public address for your Primo instance, but switch the view to a new one by changing the code in the Back Office. For example, it would allow you to switch from a the current live view to a new one.
Currently the field cannot be edited (see screenshot).
0 votes -
Add RIS export to AngularJS Primo UI
Reference management options in the new Primo UI seem limited to RefWorks, EndNote, and EasyBib. I'd like an "Export RIS" option to support users of Zotero and Mendeley.
7 votes -
Add a list of suggestions to zero result searches in the A-Z Journals list
It is not possible to display a list of suggestions when a user retrieves zero results for a search in the A-Z Journals list. However, it is possible in Primo simple and advanced search. It would be beneficial to provide users with a distinct list of suggestions if they retrieve zero results in the A-Z journals list.
37 votes -
Make integration with Alma more seamless in regard to the PCI and Link Resolver
When we activate our Link Resolver databases in Alma, we have to do it all over again in the Primo PCI. This is redundant effort. Yes, it is one time, but new libraries have enough else to do to configure the system and this seems like an unnecessary step.
6 votes -
Please make the MARC bib. 245 subfield p from the bibliographic record available.
The MARC 245 subfield p from the bibliographic record is not exposed to Primo. This means that the data in the b245p is not available to display to users in the My Account section of Primo, as part of the requesting process and on pull slips for items. This becomes important when the items have 245a data that is the same. For example, when a video game has the same name with more info in the 245p like the ones below.
b245a b245p
Angry birds. Star Wars
Angry birds. Trilogy
Assassin's creed. Brotherhood
Assassin's creed. Revelations
Batman. Arkham Asylum
Batman.…118 votes -
Please make the MARC bib. 245 subfield p from the bibliographic record available.
The MARC 245 subfield p from the bibliographic record is not exposed to Primo. This means that the data in the b245p is not available to display to users in the My Account section of Primo, to letters sent to users, as part of the requesting process and on pull slips for items. This becomes important when the items have 245a data that is the same. For example, when a video game has the same name with more info in the 245p like the ones below.
b245a b245p
Angry birds. Star Wars
Angry birds. Trilogy
Assassin's creed. Brotherhood
Assassin's creed.…12 votes -
Export search results in ISBD format
It seems that Primo does not permit (as, I.E., Aleph) the export of a search in ISBD format: doing this would be a great thing at least for our patrons
3 votes -
Display e-book-only call numbers
Please have Primo display call numbers for items that are only available in electronic format. For example, if we have an item only as an e-book, no call number displays and that also means that the Virtual Browse function doesn't work. Even though the call number for an e-book might seem irrelevant, it's actually very useful in determining the focus of a book (e.g., a book about politics with a BF call number tells us it's looking at the topic from a psychological perspective). Thanks for considering.
18 votes -
Make configurable preference of source in deduplication
Preference of records coming from differente sources in deduplication is hardcoded in Primo and it causes undesired situations, for example poor SFX records have preference over rich ILS records and the information from ILS records is discarded. Order of preference of sources should be configurable through Primo Admin interface instead of being hardcoded
78 votes -
Configuring brief display for different formats
It would be useful to be able to configure different fields to display in the brief results for different formats within Primo.
60 votes -
They appear as "renewable" items that really aren't
In Primo, they appear as "renewable" copies really are not because they already have the maximum number of renovations. Why not say directly "not renewable"?
4 votes
- Don't see your idea?