Project

General

Profile

Actions

bug #6199

closed

Excluded note for excluded taxon nodes in TaxEdtior

Added by Andreas Müller over 7 years ago. Updated almost 7 years ago.

Status:
Closed
Priority:
Highest
Assignee:
Patrick Plitzner
Category:
taxeditor
Target version:
Start date:
Due date:
% Done:

50%

Estimated time:
Severity:
normal
Found in Version:

Description

See related ticket #5634 for more information.

We need to add a multi-language field here.


Related issues

Related to EDIT - feature request #6197: Move excluded and unplaced from Taxon to TaxonNode in TaxEditorClosedPatrick Plitzner

Actions
Related to EDIT - bug #6520: Improve taxon node wizardNewKatja Luther

Actions
Follows EDIT - feature request #5634: Excluded note for excluded taxa /taxon nodesClosedAndreas Müller

Actions
Precedes EDIT - bug #6228: Fix behavior of multi-language editingClosedKatja Luther

Actions
Actions #1

Updated by Andreas Müller over 7 years ago

  • Due date set to 05/03/2016
  • Start date changed from 11/14/2016 to 05/03/2016
  • Follows feature request #5634: Excluded note for excluded taxa /taxon nodes added
Actions #2

Updated by Andreas Müller over 7 years ago

  • Due date changed from 05/03/2016 to 11/30/2016
  • Start date changed from 05/03/2016 to 11/14/2016

Please ask Katja if unclear how to implement.

Actions #3

Updated by Patrick Plitzner over 7 years ago

  • Assignee changed from Patrick Plitzner to Andreas Müller
Actions #4

Updated by Patrick Plitzner over 7 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 50
Actions #5

Updated by Andreas Müller over 7 years ago

  • Status changed from Resolved to Feedback
  • Assignee changed from Andreas Müller to Patrick Plitzner

Looks like other additional languages are not stored correctly.

Also we may think about make it fully invisible as long as isExcluded is not checked. This may simplify the standard interface (feel free to make a new ticket for this if not easy to implement.

Actions #6

Updated by Patrick Plitzner over 7 years ago

While reviewing I saw that even the isExcluded is not persisted anymore. Have to recheck if anything has changed

Actions #7

Updated by Patrick Plitzner over 7 years ago

  • Assignee changed from Patrick Plitzner to Andreas Müller

Patrick Plitzner wrote:

While reviewing I saw that even the isExcluded is not persisted anymore. Have to recheck if anything has changed

Actually, the TaxonNodeService does not correctly load the boolean values of the TaxonNode. In the data base they are stored correctly.
@Andreas: Has there been any model or service changed related to these values?

Actions #8

Updated by Andreas Müller over 7 years ago

  • Assignee changed from Andreas Müller to Patrick Plitzner

Patrick Plitzner wrote:

Patrick Plitzner wrote:

While reviewing I saw that even the isExcluded is not persisted anymore. Have to recheck if anything has changed
Actually, the TaxonNodeService does not correctly load the boolean values of the TaxonNode. In the data base they are stored correctly.
@Andreas: Has there been any model or service changed related to these values?

I added a test in TaxonNodeDaoTest which proofs that reading works fine for excluded and unplaced and also for excludedNote (not fully complete). Please adapt test if you think something does not work.

Actions #9

Updated by Andreas Müller over 7 years ago

  • Related to feature request #6197: Move excluded and unplaced from Taxon to TaxonNode in TaxEditor added
Actions #10

Updated by Patrick Plitzner about 7 years ago

  • Assignee changed from Patrick Plitzner to Andreas Müller

I could only reproduce the strange behavior (TaxonNode excluded and unplaced flag not initialised) in one data source which may be corrupted during an too early schema update.
Anyway, I tested the multi language text fields also for description elements. It seems like it does not work there either or I do not know how it is supposed to work. @Andreas: Can you check?
If so, we can close this ticket and open a new one for this issue

Actions #11

Updated by Andreas Müller about 7 years ago

  • Precedes bug #6228: Fix behavior of multi-language editing added
Actions #12

Updated by Andreas Müller about 7 years ago

The open issues are general multi-language editor issues handled in a new ticket #6228.

Actions #13

Updated by Andreas Müller about 7 years ago

  • Assignee changed from Andreas Müller to Patrick Plitzner

Before we close this there is one remaining issue:

Please move the "Open in Editor Check box down to the very bottom. An even better solution would be to have 3 buttons: save (or finish), save and open, Cancel

The current implementation makes one think that Open in Editor is an Attribute, not a workflow information.

Actions #14

Updated by Patrick Plitzner almost 7 years ago

  • Assignee changed from Patrick Plitzner to Andreas Müller
Actions #15

Updated by Andreas Müller almost 7 years ago

  • Status changed from Feedback to Resolved
Actions #16

Updated by Andreas Müller almost 7 years ago

  • Status changed from Resolved to Closed
  • Assignee changed from Andreas Müller to Patrick Plitzner

A couple of layout and workflow issues for the node wizard are now handled in #6520. So we can close this ticket.

Actions #17

Updated by Andreas Müller almost 7 years ago

  • Related to bug #6520: Improve taxon node wizard added
Actions

Also available in: Atom PDF