Project

General

Profile

Actions

bug #9419

open

Typespecimen display in Vaadin when two designations having different field units are related to one name in one publication

Added by Wolf-Henning Kusber about 3 years ago. Updated almost 3 years ago.

Status:
New
Priority:
Priority14
Category:
cdm-vaadin
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Severity:
normal
Found in Version:
Tags:

Description

Test System as of 25 JAn 2021:
Typespecimen display in Vaadin is not correct when two designations are related to one name in one publication.

There are two problems:

  1. sorting
  2. display of data (incorrect displays marked with an arrow)

Currently the system expects only one field unit. This is only true for a type and its duplicates (this is the most common case in the description of new taxa)

If there are two or more field untits involved, we need field unit plus specimen(with duplicates)separated.

This is why I typed in "unrelevant paratype locality" because there is also a holotype (not displayed) with a different field unit. I wonder, why the paratype find its way on top of the list, if a holotype is there.

Currently the type of a second with different field unit is given just as a number with end bracket, to be added to the first field unit with type.

The example was from "Kusber, W.-H., Testeinträge für Ticket 9408 in Zeitschrift für Tümpelkunde 1: 2-99"

The problem arises in the following cases:
holotype plus paratype
Syntype plus syntype plus n
Lectotype plus epitype
any type plus any ...paratype


Files

picture718-1.png (110 KB) picture718-1.png Wolf-Henning Kusber, 01/25/2021 11:18 AM
Actions #2

Updated by Andreas Müller about 3 years ago

  • Target version changed from Release 5.21 to Release 5.22
Actions #3

Updated by Andreas Kohlbecker almost 3 years ago

  • Target version changed from Release 5.22 to Release 5.46
Actions

Also available in: Atom PDF