From 4db1086876eef747275080dd6600289c6e1fd2ce Mon Sep 17 00:00:00 2001 From: timo11 Date: Thu, 25 Jun 2020 12:23:14 -0500 Subject: [PATCH] doc note. #59 --- AggregationDoc.txt | 2 ++ 1 file changed, 2 insertions(+) diff --git a/AggregationDoc.txt b/AggregationDoc.txt index cedd795..35e5f53 100644 --- a/AggregationDoc.txt +++ b/AggregationDoc.txt @@ -2,6 +2,8 @@ How to Setup an Aggregated Portal These instructions assume a common mapping is being used for all collections. It is possible to use different mappings and to adjust the CSV file in step d to make the data fit into the mapping used by the Solr instance. +NOTE: Aggregation will only work if the "spid" value is unique for all rows in the aggregation. If all Specify CollectionObjects have GUIDs then spid will be unique. When a GUID is not available, CollectionObjectID is assigned to spid, which can result in duplication. + 1. Create a common mapping for the collections you want to be aggregated. The mapping must contain a field that identifies which collection a record belongs to. (See section e below.) 2. For one collection, use the Exporter App to build the mapping and export for the web portal, then use the web portal installer to set up Solr and the portal application. (See README.md)