Ability to dedup or FRBR between local data and CDI data
For Primo Central Index data collections, the PCI citation often represents a title that we also hold in our local data. The current inability to dedupe or cluster between PCI and local data means that users will always be presented with two hits when they are on the combined/everything scope.
With the new Central Discovery Index (CDI), we would like the ability to configure a deduping or clustering algorithm such that we only present one hit to the user.
ibrahim ali commented
This is really needed to omit the duplication between local and CZ records in Primo
Manu Schwendener commented
NERS voting second round open until 31.8.2020
6702 – Ability to dedup or FRBR between local data and CDI data
Katharina Wolkwitz commented
I wonder how to explain to our users that there are some clustered records of e.g. "Dubbel: Taschenbuch für den Maschinenbau" with different editions and years nicely sorted together under one entry (coming from our local library-catalog-data) and the exact same editions and years appear as single entries in the search-result-list from the CDI.
And the final fulltext-link ends up at the exactly same page.
If there ever was a need for FRBR this is it!
Laura Akerman commented
What I would hope is that a better "solution" than either dedup or FRBR could be found for bringing together different instances of the same "expression" or edition - same content - of a work.
How about - from any record, I'd like users to easily be able to see other records for other formats or issuances of the same content, whether physical or electronic, in CDI or local resources (whether from Alma or other sources). This would have to be based on identifiers, as it is now (the dedup and frbr processes create shared identifiers), but those identifiers, whether machine-generated or human generated, should be stored as part of the metadata in a way that allows customers to see what is happening and fix mistakes, at least on their end.
I hope Ex Libris is at least thinking in this direction. In the meantime, clustering (but not deduping please! Since we have no control over CDI metadata) local and CDI records would be of great value.
Jane Daniels commented
I don't have any votes left but would support this.
Longer term we should also consider why we have to contend with multiple records for the same resource and why Ex Libris have to maintain so many knowledge bases. I presume all the other companies vying for library business with web discovery layers are doing the same thing.
There is a real need to rationalise the current metadata workflows so that less time is spent on having to devise systems that match, merge or dedup records of varying quality and instead concentrates on using a single high quality record to further search & discovery experience for end-users.
Lars Iselid commented
The concept of local data excludes external data like repositories (from pipes) or am I wrong? But what if you import your repository in Alma. Will it be included in the concept "local data"?
Brenda Norton commented
This is one of the most-requested improvements that we receive from our clients.
Asbjørn Risan commented
We would also like to see this functionality. Its important this is supported also for non Primo VE institutions.
Manu Schwendener commented
Aya Steinig commented
extremely important for our patrons!
Très bonne idée
G. Marchais commented
Would be much appreciated. We absolutely need this option too
Sylvain Machefert commented
If what seems to be a huge project like CDI does not include this possibility, that would really be an error.
Thanks François for creating this suggestion.