Warning: This page has not been updated in over over a year and may be outdated or deprecated.
indexing:deduplication
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
indexing:deduplication [2022/10/20 09:57] – Struct data changed emaijala | indexing:deduplication [2023/03/20 16:31] – [RecordManager] demiankatz | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Support for Deduplication ====== | ====== Support for Deduplication ====== | ||
- | // The features described on this page are available starting with VuFind | + | // The features described on this page are available starting with VuFind® |
+ | |||
+ | ===== Introduction ===== | ||
+ | |||
+ | The deduplication feature allows multiple records from multiple sources to be combined together and displayed as a single search result. It requires some extra setup and external tools to fully implement. Users who choose not to use deduplication may instead wish to configure the [[configuration: | ||
===== Solr Setup ===== | ===== Solr Setup ===== | ||
- | VuFind | + | VuFind® |
+ | |||
+ | ==== RecordManager ==== | ||
+ | |||
+ | [[https:// | ||
+ | |||
+ | Using RecordManager does offer some specific advantages: | ||
+ | - RecordManager can find the best record among the deduplicated records to use as the base record when creating a merged record. | ||
+ | - There' | ||
+ | - The records belonging to a dedup group can also be enriched with data from the merged record, so enrichment can be achieved in both directions. | ||
+ | - The mechanism can ensure e.g. that two records from the same data source never get deduplicated. This is a built-in assumption in RecordManager' | ||
==== Required Solr Fields in Merged Records ==== | ==== Required Solr Fields in Merged Records ==== | ||
indexing/deduplication.txt · Last modified: 2023/03/20 16:33 by demiankatz