Project

General

Profile

Actions

bug #7247

closed

TypeDesignationSetManager must not bundle NameTypes in workingset

Added by Andreas Kohlbecker about 5 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
Priority14
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

Related to EDIT - feature request #6718: Constistent TypeDesignation representation creation DuplicateAndreas Müller

Actions
Actions #1

Updated by Andreas Kohlbecker about 5 years ago

  • Subject changed from TypeDesignationManager must not bundle NameTypes in workingset to TypeDesignationSetManager must not bundle NameTypes in workingset
  • Description updated (diff)
Actions #2

Updated by Andreas Kohlbecker about 5 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 50
Actions #3

Updated by Andreas Kohlbecker about 5 years ago

  • Status changed from Resolved to Closed
  • % Done changed from 50 to 100
Actions #4

Updated by Andreas Kohlbecker about 5 years ago

Actions #5

Updated by Andreas Kohlbecker almost 2 years ago

  • Tags changed from phycobank to phycobank, type designation
Actions

Also available in: Atom PDF