Ability to merge deduped records in Primo VE
In Primo VE, you can currently choose to display a preferred dedup record (in the full and brief display), either from Alma-P, Alma-E or Alma-D (or none, and the first record to show up in the result list will display).
We would like to add the option to merge all local records. This is the default behaviour in Primo classic.
Floriane Pochon Levit
shared this idea
-
Stacey van Groll
commented
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. -
Floriane Pochon Levit
commented
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.
-
Stacey van Groll
commented
Hi Floriane - can you provide an example, as I'm not sure what you mean for VE?
-
Manu Schwendener
commented
+1