feature request #9022
Implement lifespan for Person Details View
Start date:
05/19/2020
Due date:
% Done:
100%
Severity:
major
Description
Needed for internal and external data validation
Related issues
Associated revisions
ref #9022: add lifespan to person detail element
History
#1 Updated by Wolf-Henning Kusber over 1 year ago
Life span of a person, or date a person has published nomenclatural novelties, e.g.
1795-1876, 1961-, -2016, fl. 2020
PhycoBank: years only, fl. means a year the author has published, "fl." is part of the free text entry.
#2 Updated by Andreas Kohlbecker over 1 year ago
- Tags set to phycobank
#3 Updated by Katja Luther over 1 year ago
- Status changed from New to In Progress
The lifespan is added to the details view of persons, this is fixed, but there is a general problem with the time period element. Entering a year yields to recalculate the sizes of the textfields and the field of the year becomes smaller and the other two fields become wider. A new ticket for this issue: #9056
#4 Updated by Katja Luther over 1 year ago
- Status changed from In Progress to Resolved
- Assignee changed from Katja Luther to Andreas Kohlbecker
#5 Updated by Andreas Kohlbecker over 1 year ago
- Status changed from Resolved to Closed
- Assignee changed from Andreas Kohlbecker to Katja Luther
- Priority changed from New to Highest
- % Done changed from 0 to 100
works as expected, ticket can be closed
#6 Updated by Andreas Müller over 1 year ago
- Related to feature request #9078: Handle name parsing and deduplication on server side added
#7 Updated by Andreas Müller over 1 year ago
- Related to deleted (feature request #9078: Handle name parsing and deduplication on server side)
#8 Updated by Andreas Müller over 1 year ago
- Related to feature request #9085: Improve deduplication of parsed names added
