feature request #9324
closedEnable designation reference editing in name type designation
100%
Description
Main issues:
6: enable to select an available section (new names) or create a new section (for e.g. lecto- or neotypes) - SOLVED in #9301
7: no idea if we need the editon of references here (I would say: no). - see discussion below
8: citation detail --> is not needed for phycobank since we will create dedicated sections. Allow to hide this field per configuration parameter - TODO
Further issues:
1: This might be not a button, but an entry in the dropdown. Warning: if seleted, it can be combined with a type status
2: This might be not a button, but an entry in the dropdown (same warning)
3: This makes for PhycoBank not much sense, because then we have no data to enter. Possible usage, if a type is given, but not marked as "here designated" this structure might be used (discussion needed).
4: The dropdown may interfer with the buttons at the top.
5: If a status is selected this cannot be made undone. - SOLVED
Files
Related issues
Updated by Andreas Kohlbecker over 3 years ago
- Priority changed from Priority13 to Highest
- Target version changed from Unassigned CDM tickets to Release 5.19
Updated by Andreas Kohlbecker about 3 years ago
- Target version changed from Release 5.19 to Release 5.21
Updated by Andreas Kohlbecker about 3 years ago
- Related to bug #9290: stop setting Registration.citation as citation for TypeDesignations in all type editors by default added
Updated by Andreas Kohlbecker about 3 years ago
- Description updated (diff)
7: no idea if we need the editon of references here (I would say: no).
editing of references is enabled be default, but could be disabled if really needed.
Points 1 to 4 are subject to another ticket and should be discussed separately. @Hennnig: could you please open a new ticket for this?
Updated by Andreas Kohlbecker about 3 years ago
- Subject changed from Enable section in name type designation to Enable deignation reference editing in name type designation
- Status changed from New to Resolved
- Assignee changed from Andreas Kohlbecker to Wolf-Henning Kusber
- % Done changed from 0 to 50
allowing null selection for type status in name type designation editor implemented.
so this ticket can be reviewed
Updated by Wolf-Henning Kusber about 3 years ago
- Assignee changed from Wolf-Henning Kusber to Andreas Kohlbecker
- % Done changed from 50 to 70
Allowing null selection for type status in name type designation editor implemented.
Is functioning as expected.
Note 1: Rejected type and Conserved type have a reference.
Note 2: A reference given for e.g. a lectotype for a name type in preparation is safed. In a second step the status is set to orignial designation: The Reference disappears but, as far as I can see, this causes no problems.
Note 3: proposed types for rejection/conservation with references are missing.
Updated by Andreas Kohlbecker about 3 years ago
- Subject changed from Enable deignation reference editing in name type designation to Enable designation reference editing in name type designation
Updated by Andreas Kohlbecker about 3 years ago
- Status changed from Resolved to Feedback
- Assignee changed from Andreas Kohlbecker to Wolf-Henning Kusber
Wolf-Henning Kusber wrote:
Allowing null selection for type status in name type designation editor implemented.
Is functioning as expected.Note 1: Rejected type and Conserved type have a reference.
--> copied to #9453
Note 2: A reference given for e.g. a lectotype for a name type in preparation is safed. In a second step the status is set to orignial designation: The Reference disappears but, as far as I can see, this causes no problems.
OK, good!
Note 3: proposed types for rejection/conservation with references are missing.
These flags are separate from the states in the cdm model. As far as my understanding goes, these are not type status per se. Is the application of a type status and one of these two flags mutually exclusive? Does the same also account for "not designated"?
Updated by Andreas Kohlbecker about 3 years ago
- Copied to bug #9453: Implement NameDesignationBase.hasDesignationSource() which takes isRejected and isConserved into account added
Updated by Wolf-Henning Kusber about 3 years ago
example for Note 3: proposed types for rejection/conservation with references are missing.
species
Achnanthes quadricauda Turpin in Mém. Mus. Hist. Nat. 16: 311. 1828.
Typus: [specimen from strain] Hungary, Lake Belsö-tó, Hegewald 1971/256 (Kernforschungsanlage Jülich, Germany) (typ. cons.).
Genus
Astasia Dujard., Hist. Nat. Zoophyt.: 353, 356. 1841.
Typus: A. limpida Dujard. (typ. cons.).
Auricula Hill, Brit. Herb.: 98. 31 Mar 1756 [Angiosp.: Primul. / Primul.].
Typus: non designatus.
Updated by Andreas Kohlbecker about 3 years ago
- Status changed from Feedback to Closed
- % Done changed from 70 to 100
Note 3: proposed types for rejection/conservation with references are missing.
we (Henning & Andreas) decided to postpone this discussion.
So this ticket is complete.
Updated by Andreas Kohlbecker about 3 years ago
- Assignee changed from Wolf-Henning Kusber to Andreas Kohlbecker
Updated by Andreas Müller about 3 years ago
- Target version changed from Release 5.21 to Release 5.20
Updated by Andreas Müller 3 months ago
- Related to bug #9475: NameTypeDesignations for existing names in other nom acts can not be created added