Allow admins to merge 2 organisations to remove duplicates
10770
Reporter: mdoering
Type: NewFeature
Summary: Allow admins to merge 2 organisations to remove duplicates
Priority: Major
Resolution: WontFix
Status: Closed
Created: 2012-02-03 16:28:38.362
Updated: 2013-12-16 17:51:03.183
Resolved: 2013-12-10 12:07:35.523
Author: ahahn@gbif.org
Created: 2012-02-03 16:41:51.181
Updated: 2012-02-03 16:42:07.981
Needs to support:
- viewing available metadata of both versions, decide which one to keep (copy-paste is good enough)
- merge datasets to connect to the one entry that is supposed to remain
- transfer technical endpoints
-- with the latter two, it is highly desirable to maintain all information that allows an indexer/crawler to keep track of the moved datasets, so that they are not treated as new (-> delete one at a, add another at b), but as reconnected to a different provider entity.
Need to clarify: how is a crawler supposed to follow up on a merged publisher entry?
Author: mdoering@gbif.org
Created: 2012-02-03 17:07:16.058
Updated: 2012-02-03 17:07:16.058
Endpoints should be linked to either technical installations or datasets, so we don't need to worry I think.
But technical installations and datasets need to be relinked to the merged organisation. They won't change their uuids though.
Would the remaining organization have a new id or reuse one of the existing two? Id think we should reuse one, maybe even automatically select the older one?