Actions
bug #9349
openOpen issues for classification cloning
Start date:
Due date:
% Done:
0%
Estimated time:
Severity:
normal
Found in Version:
Description
- "Import Result" including count cloned taxa, synonyms, names, ... (do we need to merge UpdateResult and ImportResult?)
- handle as long running task
- finish tests
- support in TaxEditor (#4867)
- allow target to be a parent node, not necessarily a new classification
- use TaxonNodeFilter (requires creation of limited tree due to geo filtering)
move to taxon node service- allow moving to other parent, not only new classifications
- improve handling of name cloning (not really recommended as having name duplicates in databases is not recommended - e.g. selecting correct NameUsedInSource is difficult - and handling of names in name relationships is difficult; generally names that do also exist elsewhere in the cloned classification should be cloned but deduplicated; other related names e.g. homonyms may be cloned or not, depending on the use case). Generally there should be a configuration to clone ALL related names, to clone no related names or to clone only names that are part of the cloned classification as accepted names or synonyms (and misapplied names?); generally also other names like factual data names used in source need to be cloned then
Related issues
Actions