In the brief and full display pages, libraries can display information contained in data fields (such as the title, author, and creation date) from the source record. This information helps users to differentiate records quickly. In some cases, there can be a lot of information that is displayed. This is particularly the case when Contributor is added: all 7XX fields are added, and in their entirety (see for example in the attached screenshot).

We would like an option that would allow the library to either limit the number of fields to display (for example max 3 7XX fields) or to only display fields based on the content of some subfields (for example: only display 7XX where $$e equals 'editor', 'publishing director ', 'translator', 'Director', 'film director'...).

En los casos en que disponemos de un registro bibliográfico con ejemplares en formato impreso, copia electrónica activada en la "Comunity Zone", y además se ha activado también en Primo Central para garantizar la indexación y la capacidad de recuperación a nivel de texto completo, el registro bibliográfico se visualiza en Primo VE como si fueran dos registros bibliográficos exactamente con la misma información (códigos de barras, signaturas y ubicaciones duplicados).

Según nos dicen desde SalesForce, debido a limitaciones/arquitectura del sistema, no es posible combinar el registro de Primo Central con los registros locales en Alma, lo cual crea confusión entre nuestro personal y usuarios.

Adjunto una copia de pantalla para que lo véais.

When our users look for a book in the Primo Search Portal they expect that the Primo Search behaves like a Google Search, i.e. they expect that Primo finds books with titles or metadata containing words similar to those in their query. Unfortunately, the Primo Search is very sensitive to the exact spelling of the words in the query. If the search query is slightly inaccurate, the book is not found in Primo. I tried such unsuccessful search queries on www.amazon.de, and Amazon usually found the correct book: Amazon showed the correct hit on top of the list (see attachment). This shows that the search algorithms of Amazon are clearly superior to those of Primo. I feel that Ex Libris should take steps to keep up with modern search technologies.
Some, but not all, of Primo’s shortcomings seem rather easy to fix. Primo fails to take word flexions in non-English languages into account. Since the endings of German words not only depend on plural and singular but also on the context, Primo’s search results for German queries are overly sensitive to word flexions. However, some of the English examples indicate that improving Primo’s dictionaries will not be sufficient. Over the long term, ExLibris may consider to team up with a specialized search provider.

Similar proposals in ExLibris idea exchange
https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/37586617-increase-primo-search-capability-to-support-major
https://ideas.exlibrisgroup.com/forums/564566-summon/suggestions/17415091-automatically-searching-for-the-corrected-spelling

HAL https://hal.archives-ouvertes.fr/ is one of the major open repository in French.
Some publications give full text access, others not. See screenshot attached.
We did activate for search Hyper Article en Ligne (HAL) in PCI.
Our concern is that all HAL publications in PRIMO display with "full text access" link even when there is no full text.

Please have a look to the example : Reconceptualizing the classification of PNAS articles.
This issue generates lots of complains from our final users. HAL is very well used in French speaking countries.

so could you fix this and indicate "full text access" when this is appropriate, and "bibliographic record access" when this is no full text ?

Thank you for your support.

Currently we have print books with digital representations attached in Alma, for use in Leganto. We suppress these representations from Primo by using a note and display logic as this is the only option currently available. However this means that the book in Primo shows an "available online" status in the brief results, and when the full record is opened there is a View Online (GetIT tab) section that is just blank. Returning to the brief results then shows "Check available services". This is very confusing to users. We would like to have a different method of suppressing that means the GetIt tab isn't invoked in Primo and/or the option to switch the GetIt tab off for certain records.

It would be useful if item policy could be configured as a field to display in either the brief or full item display. Currently, the loanable indicator is defined by the fulfillment terms of use, which is dependent on users signing in in order for Primo to calculate the loan policy specifically for that user.

Having the option to display the item policy from Alma as a field in Primo would be beneficial as this does not change dependent on the user type or fulfillment rules. It would also provide more information to users irrespective of whether they are able to sign into Primo (e.g. users not affiliated to the institution will be unable to sign in) and makes it clearer and easier for staff to explain to customers why a particular item can/cannot be borrowed.

We are disappointed with the technical support service provided by Ex Libris. We strongly believe that Ex Libris should provide customers with more effective, prompt and interactive service.

There should be an option to call or chat online in real time with a support person who has a sound understanding of the product in question. This would be in line with all system vendors we have previously dealt with.

We appreciate that there will be some issues that are designated as bugs or enhancements and will require more in depth investigation. However, a direct call/chat option with a properly trained support analyst would quickly and efficiently separate these issues from more general product queries. We are aware that there are many call-logging options used widely by other companies, such as FastCall, TenFold and RingDNA, which can be used to allow customer calls/chats to be registered directly in Salesforce. We believe that Ex Libris should implement this improvement as soon as possible.

Please vote to show your support for this idea and feel free to add comments relating to your experience of this issue.

In Primo VE, only one of “vocabulary” is available - “Library of Congress Subject Headings.” The choice to use this “vocabulary” is automatically made for you when you choose “Browse by Library of Congress Subject.” The index “Library of Congress name authority records for 651” is not available through this search as it is through the Metadata Editor via Alma. Thus, many, many LC subject headings cannot actually be browsed in Primo VE. Example, you can find NO headings beginning with “Colombia – Commerce,” because there is no LC subject authority for “Colombia – Commerce” or for any further subdivision of that heading. You CANNOT find the heading “Colombia – Commerce – History” by browse in Primo. Browse by subject gives incomplete results - nearly half the records are not discoverable using this method. Many researchers use this method to find their materials.

In Primo, customers could customize the RIS export table, to determine what PNX fields should be used for RIS fields. In Primo VE this is not possible:

The mapping of the RIS fields to PNX fields is as follows:
IS addata/issue
TY addata/ristype
N2 addata/abstract
N1 addata/notes
PB addata/publisher
A2 display/contributor
ET addata/edition
KW display/subject
EP addata/epage
DO addata/doi
PY addata/date ; display/creationdate
JA addata/stitle
VL addata/volume
CY addata/cop
AU display/creator
T3 addata/seriestitle
T2 addata/addtitle
T1 display/title
SP Addata/spage
JF Addata/jtitle
ID Alma MMS ID
SN Addata/issn; addata/isbn; addata/eissn; addata/eisbn

As most reference managers will read A2 as Series Editor, it would be helpful if the display/contributor could be conditioned to map to AU instead. This is just one example - and why the mapping should be customizable.

At time, in Primo VE, it is only possible to create a link to the resource and a link to the thumbnail in the Import Profile for external data sources. In Primo with a BO, however, it is possible to create nearly as many links in the PNX links section as you like. We use these links a lot for the records of our many different data sources, e.g. create links to an abstract or tables of content, links to related titles, and many mores. These links help to enrich metadata and are user friendly. Therefore, we suggest that in Primo VE, there should be an option to define at least three additional links per external data source. As in Primo with a BO, the link URL should be taken either from a template or from a source field. Customers should be able to freely determine and translate the names of the links.