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
2 results found
-
Include the item barcode as part of the data published from Alma to Primo in the AVA field to improve item search in Primo
Request for Alma item barcode be included in the data that is published to Primo as part of the Alma publishing functionality to enable barcode searchability in the Primo keyword search. We have discovered that items migrated from our previous ILS do contain the item barcode(s) in the MARC 945 $$i and is written to the search:general field of the PNX. As such, those items are keyword searchable via their barcode in Primo. However, for items created in Alma, the item barcode is not written to the bib record and is therefore not searchable in Primo. Adding the item barcode manually to the bib 945$$i for each item as part of our processing is not a viable alternative.
We would like an enhancement to Alma publishing that would add the item barcode to the data published in the "AVA" field. This functionality would improve workflow for staff when they need to search a record in Primo without having to navigate out of the items screen in Alma to retrieve the OCLC number, the MMSID or the ISBN, or to pull up the record in Primo when the book is in-hand without needing to key in the title or ISBN.
Examples of migrated records with the item barcode in the 945 $$i:
http://alliance-primo.hosted.exlibrisgroup.com/CC:cc_alma:CP71153242760001
http://alliance-primo.hosted.exlibrisgroup.com/CC:cc_alma:CP71188416360001451Request for Alma item barcode be included in the data that is published to Primo as part of the Alma publishing functionality to enable barcode searchability in the Primo keyword search. We have discovered that items migrated from our previous ILS do contain the item barcode(s) in the MARC 945 $$i and is written to the search:general field of the PNX. As such, those items are keyword searchable via their barcode in Primo. However, for items created in Alma, the item barcode is not written to the bib record and is therefore not searchable in Primo. Adding the item barcode…
468 votes -
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 results and consolidate the FRBR groups?
Examples of duplicate records:
Accuracy of prediction of gene content in large animal populations and its use for candidate gene detection and genetic evaluation
3 results (2 FRBR groups):
- TNproquest195858157 and TNfaoagrisUS201300875183
- TNcrossref10.3168/jds.2007-0231, TNscopus2-s2.0-42449094585, TNsciversesciencedirectelsevierS0022-0302(08)71293-1, TNmedline18349258
- TNorbi2268/23076Linguistic symbiosis between event loop actors and threads
2 results (1 FRBR group):
- TNsciversesciencedirectelsevierS1477-8424(08)00024-9
- TNscopus2-s2.0-51649125887 and TNcrossref10.1016/j.cl.2008.06.005Efficient control of transient wave forms to prevent spreading depolarizations
2 results (1 FRBR group):
- TNarxiv0705.3398
- TNscopus2-s2.0-39649117125, TNsciversesciencedirectelsevierS0022-5193(07)00579-6, TNcrossref10.1016/j.jtbi.2007.11.019, TNmedline18177900Le traitement de la modalité épistémique dans les traductions françaises de On the Origin of Species de Charles Darwin
3 results:
- TNerudit1038687ar
- TNscopus2-s2.0-85017546223
- TN_proquest1870219718Primo 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 votesHi all,
We are moving this idea to "Closed" to release your votes, as it is no longer relevant with CDI.
Best regards,
Yael.
505 results found
-
Can Note be added to the list of field search options in Advanced Search in Primo?
Adding Note to the field search options filter would enable patrons to more effectively search for titles. For example, someone searching for materials in languages not currently available for limiting searches could select Note and write Text in Tagalog or similar to refine their search. Keyword searching does this, but the results lack context and are much less helpful.
1 vote -
Stop the Alma link resolver from matching e-books and print bibs that aren't the same ed.
At present, if we have a 2nd ed e-book and a 2nd ed print (that is 2nd ed., EMEA ed.) of the same title, Primo is linking them when they are actually different editions. Ex Libris says this is because of matching via title and author and that the option to cancel this kind of match of a specific record isn't available. it would be good if we could unlink them in the Primo record
1 vote -
Dublin Core field to display external links (like an 856)
We would like to have a way to link users to external resources from a Dublin Core record, similarly to how an 856 is used in MARC. Example: a digital object in Alma could link to a related finding aid in ArchivesSpace.
Perhaps the field(s) most appropriate to display in this manner would be dc:relation, dcterms:isPartOf, dcterms:replaces, dcterms:requires, dcterms:conformsTo and dcterms:isVersionOf.. but only if those fields utilize (dcterms:URI). If any of those fields are not tagged as a URI, that field should display as it does now.We are agnostic to whether such hyperlinks should be displayed in the "links" area where 856's are displayed, or if they should be shown in the "details" area. Perhaps other institutions have a stronger preference, or perhaps one is easier to implement than the other.
We would like to have a way to link users to external resources from a Dublin Core record, similarly to how an 856 is used in MARC. Example: a digital object in Alma could link to a related finding aid in ArchivesSpace.
Perhaps the field(s) most appropriate to display in this manner would be dc:relation, dcterms:isPartOf, dcterms:replaces, dcterms:requires, dcterms:conformsTo and dcterms:isVersionOf.. but only if those fields utilize (dcterms:URI). If any of those fields are not tagged as a URI, that field should display as it does now.We are agnostic to whether such hyperlinks should be displayed in the "links"…
8 votes -
Resource Type Filter Bar buttons: users expect them to unclick if they change the search scope dropdown
Users raised that they would like the Resource Type Filter Bar buttons to reset themselves to "All" when they repeat their search in a different dropdown scope.
This is especially relevant when the new combination of search scope and resource type doesn't give any hits, e.g. searching the print catalogue scope with the button clicked to see only electronic articles.
1 vote -
Only show "request other issue" for serials.
Presently if a title has a holdings statement attached (holdings 866 I think) or it has a description in an item record, and if the fulfillment rules allow for patron physical requesting, then in addition to item-level request links there will be a "Request other issue" link. The resulting form allows the patron to fill in additional values for chapter, page, volume, issue, part and date. Documentation refers to this as a "Request for a Non-Cataloged Serial Item." However, the link presently appears on non-serial items. Ex: https://librarysearch.williams.edu/permalink/01WIL_INST/1faevhg/alma991013241589702786
Given that this link takes you to a form focused on serials-related metadata, we think this link should only appear on serial titles that meet the other criteria (holdings statement, description, requestable).
Thanks for considering!Presently if a title has a holdings statement attached (holdings 866 I think) or it has a description in an item record, and if the fulfillment rules allow for patron physical requesting, then in addition to item-level request links there will be a "Request other issue" link. The resulting form allows the patron to fill in additional values for chapter, page, volume, issue, part and date. Documentation refers to this as a "Request for a Non-Cataloged Serial Item." However, the link presently appears on non-serial items. Ex: https://librarysearch.williams.edu/permalink/01WIL_INST/1faevhg/alma991013241589702786
Given that this link takes you to a form focused on serials-related…3 votes -
Being able to choose "emailing and printing exporting actions" fields
The print and export options are currently limited.
It would be a lot of help if we could choose the fields that are being exported to excel (or at least add the location field there), and which are being printed. Currently, in the print version there a lot of fields (all of the get it fields) and it takes a lot of space in a printed list for a patron. 4-5 pages for 15 results. The minimum is that there will be a long version and a short one to print, but better of if we could choose which fields to print or configure them up-front.The print and export options are currently limited.
It would be a lot of help if we could choose the fields that are being exported to excel (or at least add the location field there), and which are being printed. Currently, in the print version there a lot of fields (all of the get it fields) and it takes a lot of space in a printed list for a patron. 4-5 pages for 15 results. The minimum is that there will be a long version and a short one to print, but better of if we could choose which fields…8 votes -
Allow suppression of citation action based on resource type.
Some resource formats, such a patents from CDI, lack crucial information so that the generated citation is inaccurate and unhelpful. For instance, patents lack the patent number, which is present int the record but which doesn't display to patrons. We'd like to be able to suppress the citation action in Primo VE based on certain resource types.
3 votes -
Customize Facet List - Advanced Search
It would be helpful for our users to be able to select locations from a list of library locations. For instance, we have a library in the system with a specific archive of local history collections and it would be beneficial to restrict a search to those locations rather than sifting through similar titles in the overall collection
1 vote -
Do not show availability for CDI/Alma records with matching GTI ID
Occasionally, CDI records will show availability for physical items (holdings/digitization offers via Rapido), and the physical records will show online availability. To our understanding, this is due to a matching GTI ID. We were informed in a SF case that it is currently not possible to resolve this. As this leads to confusion for our libraries (mainly digitization requests for an electronic resource) we would be glad if a solution could be found to no longer show these incorrect availabilities (or at least for the digitization requests to show the physical record they were actually placed on).
Example: https://ubs.swisscovery.slsp.ch/permalink/41SLSP_UBS/giv3ks/cdi_askewsholts_vlebooks_97835404884916 votes -
Resource Recommender Statistics for Individual Items
Primo Analytics for Resource Recommender analytics currently shows only number of selections by resource category but not for individual records within each category. We would like to use detailed statistics for annual usage review and and RR maintenance. Particularly for databases, we would like a more straightforward option to see clicks through RR.
From two previous ideas that were both closed: https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/30982855-better-analytics-for-resource-recommender-to-tell#{toggle_previous_statuses}
https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/45030058-resource-recommender
17 votes -
Add 'Review articles' as an option for the Resource Type Filter Bar
Currently, the only option we can set is 'Reviews' for the Resource Type Filter Bar, but that is not the same as 'Review articles', which are a CDI document attribute used as a facet, as described here:
5 votes -
Newest Edition Flag in Primo
Similar to the Newest Edition flag in Rialto search results, having an indicator in Primo which shows the user which edition of the book is the most recently published/newest edition. Picture included of the Rialto example.
1 vote -
Set default of language in vocie search
When in voice search using customized languages (not UI supported languages because it influences the language options in My Account) it is not possible to set a default language: https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/Primo_VE_(English)/050Display_Configuration/010Configuring_Discovery_Views_for_Primo_VE#Defining_a_View
I suggest it should be possible to set the default language of Voice Search (as once was possible in earlier versions of VE)1 vote -
Show “display fields” and “General electronic services” in a DEDUP record
We show print records when records are DEDUPed (Availability: ALMA-P).
When there is a display field created for an e-record it will not show up when the record is deduped with the print record. Neither will so called “General electronic services” created for the e-record show up.3 votes -
Do not index preprint articles in CDI until they are published
Preprint articles are showing up in EBSCOhost collections via CDI records before the articles are published. This makes things confusing for users when they find an article that is not actually available yet.
Please consider working with this provider to distinguish this content and/or not index them in CDI until the articles are published. Thank you!
1 vote -
Interaction between Unpaywall and View-it Section
In some cases the Unpaywall API returns a link but the View-it section of the record shows "No full text available". Customer support explained the beahviour as follows:
"Currently the Unpaywall API used by the Alma ViewIt checks for a direct link to the PDF of the article. In some cases, Unpaywall's API might return a link to a landing page - a webpage in which details on the resource appear as well as option for download. In that case, the ViewIt will not present a link.
The Primo 'Get PDF' link uses a different mechanism, which does support links to Landing Pages - this is why you see the link in the "Get PDF" Primo functionality, but in the Alma ViewIt."It would be great if The ViewIt section could receive the Unpawall link and display it. Or maybe the View-it section could be supressed in these cases, so that only the "View online" and "Get PDF" links remain.
The current situation where "View online" and "Get PDF" are being displayed alongside "No fulltext available" in the View-it section is confusing for patrons.
In some cases the Unpaywall API returns a link but the View-it section of the record shows "No full text available". Customer support explained the beahviour as follows:
"Currently the Unpaywall API used by the Alma ViewIt checks for a direct link to the PDF of the article. In some cases, Unpaywall's API might return a link to a landing page - a webpage in which details on the resource appear as well as option for download. In that case, the ViewIt will not present a link.
The Primo 'Get PDF' link uses a different mechanism, which does support links…3 votes -
Primo VE item filter by ChronJ item field
In Primo VE, in the Get it section, button "location item filter" we can see and filter the items associated to an specific holding. Sometimes, for example with daily newspapers, there are lots of items associated to a holding.
We have the issue's year codified in chronI field, following ExLibris recommendations, month in chronJ field and day of the month in ChronK field.If users want to reach, say, an issue dated July 16th, they should select the corresponding year and Primo VE loads the first ten issues of the year, starting in January. Now, user should be clicking many times “Show more ítems” button to load ten issues more and so on, so it will be cumbersome to reach finally July’s issues.
So, adding chronJ to filter item functionality would be very useful for daily newspapers users.
ThanksIn Primo VE, in the Get it section, button "location item filter" we can see and filter the items associated to an specific holding. Sometimes, for example with daily newspapers, there are lots of items associated to a holding.
We have the issue's year codified in chronI field, following ExLibris recommendations, month in chronJ field and day of the month in ChronK field.If users want to reach, say, an issue dated July 16th, they should select the corresponding year and Primo VE loads the first ten issues of the year, starting in January. Now, user should be clicking many…
1 vote -
Allow Indexing and Display of 788 Field
Would like for the indexing and display of 788 field in Primo VE.
The 788 field allows catalogers to make discoverable parallel descriptions in another language https://www.loc.gov/marc/bibliographic/bd788.html and https://www.oclc.org/bibformats/en/7xx/788.html
1 vote -
Harvard Business Review Digital Articles
Indexing Harvard Business Review Digital Articles for Primo
3 votes -
Enable more fields for export to Mendeley, at least the permalink to the record
It would be very helpful for users if the permalink to the record could be exported to Mendeley.
2 votes
- Don't see your idea?