Actions
bug #7247
closedTypeDesignationSetManager must not bundle NameTypes in workingset
Status:
Closed
Priority:
Priority14
Assignee:
Category:
cdm-vaadin
Target version:
Start date:
Due date:
% Done:
100%
Estimated time:
Severity:
normal
Found in Version:
Description
When two NameTypeDesignations for with the same typeName are related to a registration the TypeDesignationSetManager groups these names in a "workgingset".
The TypeDesignationSetManager should keep such NameTypeDesignations separate even if this is not a valid situation in terms of nomenclature.
Related issues
Updated by Andreas Kohlbecker about 6 years ago
- Subject changed from TypeDesignationManager must not bundle NameTypes in workingset to TypeDesignationSetManager must not bundle NameTypes in workingset
- Description updated (diff)
Updated by Andreas Kohlbecker about 6 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 50
Applied in changeset cdm-vaadin|843f448b234e1e763faf4d9b8485da2e3a4db45d.
Updated by Andreas Kohlbecker about 6 years ago
- Status changed from Resolved to Closed
- % Done changed from 50 to 100
Updated by Andreas Kohlbecker about 6 years ago
- Related to feature request #6718: Constistent TypeDesignation representation creation added
Updated by Andreas Kohlbecker almost 3 years ago
- Tags changed from phycobank to phycobank, type designation
Actions