Actions
bug #9701
closedOrder and display of different typifications for one name in one reference
Status:
Closed
Priority:
Highest
Assignee:
Category:
cdm-vaadin
Target version:
Start date:
Due date:
% Done:
100%
Estimated time:
Severity:
normal
Found in Version:
Description
Correct: When a type specimen editor entry has a holotype and isotypes, the display and order is correct in Vaadin.
Bug: When e.g. a name has a holotype (1. entry), a paratype from a differen locality/date (2. entry), and a second paratype from a third locality/date, PhycoBank has the following demands:
- show complete type information for each entry, in case different type specimen forms have been used.
- Use the order, the data entry was performed, users are beginnen with the most important type (e.g. holotype)
Please check also minor formatting issues.
Files
| picture714-1.png (38.6 KB) picture714-1.png | |||
| picture866-1.png (82.8 KB) picture866-1.png |
Related issues
Updated by Andreas Kohlbecker about 3 years ago
- Related to bug #9302: Phycobank related issues for TypeDesignation formatting added
Updated by Andreas Kohlbecker about 3 years ago
- Target version changed from Unassigned CDM tickets to Release 5.51
Updated by Andreas Kohlbecker almost 3 years ago
- File picture866-1.png picture866-1.png added
Other display issues, related to #9308, can be seen here:
Updated by Andreas Kohlbecker almost 3 years ago
- Related to task #9308: Supress "designated by" reference in portal in registration ListView and RegistrationWorkingSetEditor added
Updated by Andreas Kohlbecker almost 3 years ago
- Status changed from New to Resolved
- Assignee changed from Andreas Kohlbecker to Wolf-Henning Kusber
- % Done changed from 0 to 50
please review
Updated by Wolf-Henning Kusber almost 3 years ago
- Assignee changed from Wolf-Henning Kusber to Andreas Kohlbecker
- % Done changed from 50 to 100
Working not exactly as expected, but a little bit better :)
The colours are nice, the plural thing is also solved.
The Types are exactly in the right order.
Test system 102734 (I reproduced the problem from the production system). So this ticket can be closed.
Updated by Andreas Kohlbecker almost 3 years ago
- Status changed from Resolved to Closed
Updated by Andreas Müller almost 3 years ago
- Target version changed from Release 5.51 to Release 5.27
Actions