I support this idea. This is also problematic for OA records. We also chose to display print records, as we tend to have more local fields in print records than the electronic records that generally come from the CZ. However, if the electronic version is OA and the record includes a 506 field, the OA logo doesn't appear on the dedupped record unless the user limits to e-only (which few do).

Hi Stacey, so sorry I didn't see your answer. Better late than never… Here is an example of a deduped record (physical and electronic version of a book) where the difference is quite obvious : 1/ Record in our default search profile where the Alma-P record is displayed (without the OA logo on the Brief record display) https://renouvaud1.primo.exlibrisgroup.com/discovery/search?query=any,contains,Histoire%20du%20sport%20de%20l'Antiquit%C3%A9%20au%20XIXe%20si%C3%A8cle%201984&tab=Everything&search_scope=MyInst_and_CI&vid=41BCULAUSA_LIB:VU2 and 2/ Record in our e-resources search profile where the Alma-E record is displayed with the OA logo (added through a 506 field) : https://renouvaud1.primo.exlibrisgroup.com/discovery/search?query=any,contains,Histoire%20du%20sport%20de%20l'Antiquit%C3%A9%20au%20XIXe%20si%C3%A8cle%201984&tab=Online_resources&search_scope=ALL_RN&vid=41BCULAUSA_LIB:VU2 . We chose to display the Alma-P record in our default search profile as we find that our local records are usually better than CZ ones, but we would like that important information such as the OA logo be displayed as well.

There is still a preferred record display by cascade of preference by delivery category in Primo managed via Back Office. This will result in failure to display the fields from the non-preferred records when the field is duplicated, for example if the two records have a description field, then only the description from the preferred record displays.
It seems the difference with Primo VE is the dynamic nature of the deduplication, in this 'first record in the result list' aspect, as VE deduplicates at the point of search rather than the point of index, and therefore preferences to match the user query as primary.
I'd still really love to see an example of this variation in action, if you feel willing to provide one.

Hi Stacey, in Primo VE the fields are not merged, by default only the metadata of the first record in the result list is displayed, or the Alma-P/E/D record if you choose this option.

For example, we chose to display always Alma-P records because we think that our local fields have to be displayed no matter which keywords were searched, but it means that we loose all the metadata from the CZ records (like description in 520 fields). We think it would be more appropriate to display all the fields from merged records, not making it depend on search keywords.

Hi Floriane - can you provide an example, as I'm not sure what you mean for VE?

+1