Project

General

Profile

bug #7831

VALIDATE_AGAINST_HIGHER_NAME_PART specific epithet name is not exluded when changing species to subspecies

Added by Andreas Kohlbecker 2 months ago. Updated about 2 months ago.

Status:
Closed
Priority:
New
Category:
cdm-vaadin
Target version:
Start date:
10/17/2018
Due date:
% Done:

100%

Severity:
major
Found in Version:
Tags:

Description

Example:

Species Navicula bahusiensis being edited in TaxonNamePopupeditor with mode VALIDATE_AGAINST_HIGHER_NAME_PART (was originally implemented in #7338)

Chaning the rank to subspecies will correctly change the specific epithet field to a combobox. But the epithet bahusiensis is selectable even if the name will no longer exist as species once the editor is saved.

The same problem might also exist for genera

Soulution:

  • exclude the name being edited from the results in the comboboxes.

Associated revisions

Revision efc5d1e3 (diff)
Added by Andreas Kohlbecker 2 months ago

ref #7831 adding name exlude filter to TaxonNamePartsFilter

Revision db1db901 (diff)
Added by Andreas Kohlbecker 2 months ago

fix #7831 excluding the current name from the WeaklyRelatedEntityCombobox for genus name and specific epithet

Revision 2ac69f0c (diff)
Added by Andreas Kohlbecker about 2 months ago

ref #7831 using uuids in findTaxonNameParts() methods as name exclude filter

Revision f57aebc4 (diff)
Added by Andreas Kohlbecker about 2 months ago

ref #7831 using uuids in findTaxonNameParts() methods as name exclude filter - NPE fix

History

#1 Updated by Andreas Kohlbecker 2 months ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 50

#2 Updated by Andreas Kohlbecker about 2 months ago

  • Status changed from Resolved to Closed
  • % Done changed from 50 to 100

fully solved

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 40 MB)