Project

General

Profile

Actions

task #8047

closed

Remaining issues in TaxDistributionEditor

Added by Andreas Müller about 5 years ago. Updated over 1 year ago.

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

100%

Estimated time:
Severity:
normal

Description

Copied from #7854

  • Correct tooltips for "Add Source" and "Remove sources"
  • Disable "Add Source" or "Remove Source" depending on the current state of source selection
  • Use icon (delete icon) for "Remove Source" and move button down beside the label for the selected source
  • ... or alternatively to all the above use only 1 button which changes label and functionality depending on a source already being selected or not, either "add" or "remove"
  • Make the number of dropdown items (for status selection) configurable (see #7854#note-66)
  • Try to optimize the column width at start or after area selection. Details may be discussed. We have/had a similar discussion for the bulk editor in some other ticket. / der Verbreitungseditor erinnert sich auch nicht, wenn ich die Spaltenbreite verändert habe. Könnte man ihn dazu bringen, die Spaltenbreite automatisch an die Länge der Bezeichnungen in der Kopfzeile anzupassen? (see description in #7854 and #7854#note-20
  • In preferences translate possible configuration terms "ID in Vocabulary" => "ID im Vokabular"
  • Multiple cell selection in table is currently possible. As there is no function related to this we should remove this feature for now.
  • Think about synchronization strategies for name editor and distribution editor
  • Documentation e.g. how to use only with keystrokes (#7854#note-80)
  • implement comparator which is related to the tree structure in the navigator, so children of a taxon come first though they have a lower rank, but best ordering should be configurable (let the user choose from the 3 typical ordering + the ordering described here - which has again 2 versions, alphabetic or rank + alphabetic) #7854#note-87
  • warning before opening if number of opened taxa is large (e.g. >200), this may take time
  • handling of factual data view when switching between name editor and distribution editor #7854#note-85
  • If no area is selected add a message to the white space beside the table to choose an area first. Or, alternatively, automatically open the area selection dialog or open a dialog that asks you if you want to open the area selection because no area is selected yet
  • Check performance with large datasets (and related to this) #6159#note-9
  • Allow multi-select when opening the distribution editor to better define the taxon sets to work with (important for flat hierarchies) - #7860
    • if selected nodes have children ask whether they should be opened too or not
    • open selected taxon
  • Filtering for taxon names works only after leaving the cell, better would be after key stroke + delay
  • Filter: use same label as shown in the cells, currently it shows same value as in the dropbox of cells (also needs discussion if the cell label should also be shown (additionally) in the dropbox
  • Preferences: Group preferences for areas together and preferences for status together each with an according title
  • Show also taxon name in details view
  • Sort status in drop down alphabetically
  • possibility to configure the label in status drop down

Also interesting:

  • editing multiple status (currently multiple status are only displayed, is there a way to edit multiple status?)

Files

picture589-1.png (10.6 KB) picture589-1.png Andreas Müller, 03/21/2020 12:20 PM

Related issues

Related to EDIT - bug #6159: improve distribution editor in TaxEditorClosedKatja Luther

Actions
Related to EDIT - feature request #7860: [Master] Remaining E+M editor issuesNewKatja Luther

Actions
Related to EDIT - bug #8939: Exception when opening Distribution Editor because of missing PreferenceClosedKatja Luther

Actions
Copied from EDIT - task #7854: Open issues in TaxDistributionEditor ClosedKatja Luther

Actions
Copied to EDIT - feature request #8889: Remaining issues for distribution editor - continueIn ProgressKatja Luther

Actions
Actions #1

Updated by Andreas Müller about 5 years ago

  • Copied from task #7854: Open issues in TaxDistributionEditor added
Actions #2

Updated by Andreas Müller about 5 years ago

  • Description updated (diff)
Actions #3

Updated by Andreas Müller about 5 years ago

  • Description updated (diff)
Actions #4

Updated by Andreas Müller about 5 years ago

  • Description updated (diff)
Actions #5

Updated by Andreas Müller about 5 years ago

  • Description updated (diff)
Actions #6

Updated by Andreas Müller about 5 years ago

  • Description updated (diff)
Actions #7

Updated by Katja Luther about 5 years ago

  • Description updated (diff)
Actions #8

Updated by Andreas Müller about 5 years ago

  • Description updated (diff)
Actions #9

Updated by Andreas Müller about 5 years ago

  • Description updated (diff)
Actions #10

Updated by Andreas Müller about 5 years ago

  • Description updated (diff)
Actions #11

Updated by Andreas Müller about 5 years ago

  • Description updated (diff)
Actions #12

Updated by Andreas Müller about 5 years ago

  • Description updated (diff)
Actions #13

Updated by Andreas Müller about 5 years ago

  • Description updated (diff)
Actions #14

Updated by Andreas Müller about 5 years ago

  • Related to bug #6159: improve distribution editor in TaxEditor added
Actions #15

Updated by Andreas Müller about 5 years ago

  • Description updated (diff)
Actions #16

Updated by Andreas Müller about 5 years ago

  • Description updated (diff)
Actions #17

Updated by Andreas Müller about 5 years ago

  • Description updated (diff)
Actions #18

Updated by Andreas Müller about 5 years ago

  • Description updated (diff)
Actions #19

Updated by Katja Luther about 5 years ago

  • Priority changed from New to Highest
  • Target version changed from Release 5.6 to Release 5.7
Actions #20

Updated by Andreas Müller about 5 years ago

Actions #21

Updated by Andreas Müller about 5 years ago

  • Description updated (diff)
Actions #22

Updated by Katja Luther almost 5 years ago

  • Target version changed from Release 5.7 to Release 5.8
Actions #23

Updated by Katja Luther almost 5 years ago

  • Description updated (diff)
Actions #24

Updated by Katja Luther almost 5 years ago

  • Description updated (diff)
Actions #25

Updated by Andreas Müller over 4 years ago

  • Target version changed from Release 5.8 to Release 5.10
Actions #26

Updated by Katja Luther over 4 years ago

  • Target version changed from Release 5.10 to Release 5.11
Actions #27

Updated by Andreas Müller over 4 years ago

  • Target version changed from Release 5.11 to Release 5.12
Actions #28

Updated by Katja Luther about 4 years ago

  • Target version changed from Release 5.12 to Release 5.13
Actions #29

Updated by Katja Luther about 4 years ago

  • Description updated (diff)
Actions #30

Updated by Katja Luther about 4 years ago

  • Description updated (diff)

Disable "Add Source" or "Remove Source" depending on the current state of source selection

  • Use icon (delete icon) for "Remove Source" and move button down beside the label for the selected source

  • ... or alternatively to all the above use only 1 button which changes label and functionality depending on a source already being selected or not, either "add" or "remove"

Now I implemented it in a way that the remove button is disabled if no source is selected, but the select source button is still enabled when a source is selected to have the possibility to change the selection.

Actions #31

Updated by Katja Luther about 4 years ago

  • Description updated (diff)
Actions #32

Updated by Katja Luther about 4 years ago

  • Description updated (diff)
Actions #33

Updated by Katja Luther about 4 years ago

  • Description updated (diff)
Actions #34

Updated by Katja Luther about 4 years ago

  • Description updated (diff)
Actions #35

Updated by Katja Luther about 4 years ago

  • Sort status in drop down alphabetically

I think a few weeks ago we decided to sort the status by the id in Vocabulary. I have to search for the ticket entry.

Actions #36

Updated by Katja Luther about 4 years ago

  • Description updated (diff)
Actions #37

Updated by Andreas Müller about 4 years ago

Katja Luther wrote:

  • Sort status in drop down alphabetically

I think a few weeks ago we decided to sort the status by the id in Vocabulary. I have to search for the ticket entry.

The sorting (if alphabetically) should always depend on the representation used. Which one to use is defined in the preferences. So we can't say it is always "by idInVoc" or always by "label".

Actions #38

Updated by Katja Luther about 4 years ago

  • Description updated (diff)
Actions #39

Updated by Katja Luther about 4 years ago

  • Description updated (diff)
Actions #40

Updated by Katja Luther about 4 years ago

  • Description updated (diff)
Actions #41

Updated by Katja Luther about 4 years ago

  • Status changed from New to Resolved
  • Assignee changed from Katja Luther to Andreas Müller

for the missing issues created a new ticket #8889 and close this ticket.
please review.

Actions #42

Updated by Andreas Müller about 4 years ago

Actions #43

Updated by Andreas Müller about 4 years ago

  • Status changed from Resolved to Feedback
  • Assignee changed from Andreas Müller to Katja Luther

"Choose Source" does not change label if a source is already selected. It may change label to "Change source" (and back if source is deleted).

Actions #44

Updated by Andreas Müller about 4 years ago

Make the number of dropdown items (for status selection) configurable

The field in the preferences is not a pure integer field, but it also allows characters like "a". Generally it should allow only numbers or at least an error should be shown when trying to save a value like 'aaa20'
Also the field could be a bit wider to make sure all numbers are shown and not only hidden.

Actions #45

Updated by Andreas Müller about 4 years ago

  • % Done changed from 0 to 40

Also the width of the field differs in DB prefs and in local prefs. In DB prefs it is definetely to small as only 1 number is fully shown.

Actions #46

Updated by Andreas Müller about 4 years ago

... no it looks like the 2 influence each other. If I store a new value in DB prefs this value is also shown in local prefs but should not. So override does not work. Please check functionality and independency of both values.

Actions #47

Updated by Andreas Müller about 4 years ago

Allow multi-select when opening the distribution editor to better define the taxon sets to work with (important for flat hierarchies)
if selected nodes have children ask whether they should be opened too or not

The later issue seems not to be implemented yet. If I select Arenaria serpyllifolia the children are automatically opened without asking if this should happen.

Actions #48

Updated by Katja Luther about 4 years ago

Andreas Müller wrote:

Allow multi-select when opening the distribution editor to better define the taxon sets to work with (important for flat hierarchies)
if selected nodes have children ask whether they should be opened too or not

The later issue seems not to be implemented yet. If I select Arenaria serpyllifolia the children are automatically opened without asking if this should happen.

this is part of the follow up ticket.

Actions #49

Updated by Katja Luther about 4 years ago

Andreas Müller wrote:

... no it looks like the 2 influence each other. If I store a new value in DB prefs this value is also shown in local prefs but should not. So override does not work. Please check functionality and independency of both values.

This is only the case if the local value was not set before so the default value is shown and this is the db value.

But the field was not disabled if allowOverride was false, this is fixed.

Actions #50

Updated by Katja Luther about 4 years ago

Katja Luther wrote:

Andreas Müller wrote:

... no it looks like the 2 influence each other. If I store a new value in DB prefs this value is also shown in local prefs but should not. So override does not work. Please check functionality and independency of both values.

This is only the case if the local value was not set before so the default value is shown and this is the db value.

But the field was not disabled if allowOverride was false, this is fixed.

Now also the exception label is shown correctly when something else then a number is entered.

Actions #51

Updated by Katja Luther about 4 years ago

Andreas Müller wrote:

"Choose Source" does not change label if a source is already selected. It may change label to "Change source" (and back if source is deleted).

this is implemented now.

Actions #52

Updated by Katja Luther about 4 years ago

  • Status changed from Feedback to Resolved
  • Assignee changed from Katja Luther to Andreas Müller

please review the issues, mentioned above

Actions #53

Updated by Andreas Müller about 4 years ago

  • Assignee changed from Andreas Müller to Katja Luther

The number field in the preferences is still not wide enough

Actions #54

Updated by Andreas Müller about 4 years ago

Katja Luther wrote:

Katja Luther wrote:

Andreas Müller wrote:

... no it looks like the 2 influence each other. If I store a new value in DB prefs this value is also shown in local prefs but should not. So override does not work. Please check functionality and independency of both values.

This is only the case if the local value was not set before so the default value is shown and this is the db value.

But the field was not disabled if allowOverride was false, this is fixed.

Now also the exception label is shown correctly when something else then a number is entered.

This is already better as it shows that there is an error. But some open issues:

  • The label should be red as for other such error messages (e.g. URLs)
  • The label should say "... positive integer" instead of "... number"
  • negative numbers are still allowed but shouldn't
  • if an incorrect "number" is entered, e.g. 1,3 saving is still possible but instead 13 is persisted which is not correct; saving should not be possible if an error exist

In general I think it is a better solution for number fields to not allow entering anything else than numbers while entering data. So if someone tries to enter a letter or anything else it should simply not be shown (not be entered). This is quite easy for positive integer fields and a bit more complicated for decimal numbers or negative numbers. Isn't it possible to define a regex or something similar for such text fields or are there predefined textfields for such cases? Entering pos. is a very basic issue so others may also have the same problem (and solutions).
Note: for dates we have a limited number of characters that can be entered maybe this shows how to solve such issues (but unfortunately also there it is still possible to enter something else then numbers, so this should also be fixed if possible).
Of course this may be moved to a new ticket if it is not easy to fix.

Actions #55

Updated by Andreas Müller about 4 years ago

Andreas Müller wrote:

The number field in the preferences is still not wide enough

The problem is it changes the size according to the previous value. This does not make sense or should be implemented in a way that entering data is also possible if you want to more digits. But here we can simply use a fixed width as we do not expect more than 2 digits. So with a width showing a max of 3 digits we are always on the save side.

Actions #56

Updated by Andreas Müller about 4 years ago

It is not possible to define "use default" for the number of dropdown items, neither for DB prefs nor for local prefs.

Actions #57

Updated by Andreas Müller about 4 years ago

Try to optimize the column width at start or after area selection. Details may be discussed. We have/had a similar discussion for the bulk editor in some other ticket. / der Verbreitungseditor erinnert sich auch nicht, wenn ich die Spaltenbreite verändert habe. Könnte man ihn dazu bringen, die Spaltenbreite automatisch an die Länge der Bezeichnungen in der Kopfzeile anzupassen?

To me it looks like this is not yet implemented though it is crossed out and also not moved to the follow up ticket.
If it is implemented can you please explain what the current expected behavior is if you open the distribution editor or if you selected a new set of areas

Actions #58

Updated by Andreas Müller about 4 years ago

  • Status changed from Resolved to Feedback

Currently it is not possible to enter the status in the details view (the field is disabled). I do not fully remember if this was always the case. In general there is no reason for disabling this field (other then the area and taxon name field which should be fixed as they are fixed in the table itself.
If this is a regression or if there is no technical reason for disabling we should enable the field, otherwise we can leave it as it is as it is not an urgent issue.

Actions #59

Updated by Andreas Müller about 4 years ago

Sort status in drop down alphabetically

This mostly seems to be fixed but I found 1 case in rem_conf_am where it was not correct:

Actions #60

Updated by Andreas Müller about 4 years ago

Andreas Müller wrote:

Sort status in drop down alphabetically

This mostly seems to be fixed but I found 1 case in rem_conf_am where it was not correct:

Sorry I did not see that the ordering is configurable now. So this issue is solved (only we could discuss what the default should be - idInVoc or label, but this is of minor importance)

Actions #61

Updated by Andreas Müller about 4 years ago

Andreas Müller wrote:

Andreas Müller wrote:

Sort status in drop down alphabetically

This mostly seems to be fixed but I found 1 case in rem_conf_am where it was not correct:

Sorry I did not see that the ordering is configurable now. So this issue is solved (only we could discuss what the default should be - idInVoc or label, but this is of minor importance)

hmm, probably the best default (and also still missing alternative) is to always sort according to the label shown in the dropdown. It does not make sense to order alphabetically by something which is not shown (so ordering by idInVoc does not make sense if the term.label or term.symbol or something else is shown in the dropdown). Is it possible to implement it this way? (we may move this to the follow up ticket)

=> moved to #8889

Actions #62

Updated by Andreas Müller about 4 years ago

  • % Done changed from 40 to 60

This ticket is now fully reviewed. Only the issues I mentioned are still open (as far as I can see).

Actions #63

Updated by Katja Luther about 4 years ago

Andreas Müller wrote:

Currently it is not possible to enter the status in the details view (the field is disabled). I do not fully remember if this was always the case. In general there is no reason for disabling this field (other then the area and taxon name field which should be fixed as they are fixed in the table itself.
If this is a regression or if there is no technical reason for disabling we should enable the field, otherwise we can leave it as it is as it not an urgent issue.

this was never possible. the distribution part of the details view was completely disabled.

Actions #64

Updated by Katja Luther about 4 years ago

Andreas Müller wrote:

Try to optimize the column width at start or after area selection. Details may be discussed. We have/had a similar discussion for the bulk editor in some other ticket. / der Verbreitungseditor erinnert sich auch nicht, wenn ich die Spaltenbreite verändert habe. Könnte man ihn dazu bringen, die Spaltenbreite automatisch an die Länge der Bezeichnungen in der Kopfzeile anzupassen?

To me it looks like this is not yet implemented though it is crossed out and also not moved to the follow up ticket.
If it is implemented can you please explain what the current expected behavior is if you open the distribution editor or if you selected a new set of areas

Remembering the size is still missing, but adapting the width of the columns should work.

Actions #65

Updated by Katja Luther about 4 years ago

Andreas Müller wrote:

Andreas Müller wrote:

The number field in the preferences is still not wide enough

The problem is it changes the size according to the previous value. This does not make sense or should be implemented in a way that entering data is also possible if you want to more digits. But here we can simply use a fixed width as we do not expect more than 2 digits. So with a width showing a max of 3 digits we are always on the save side.

this should be fixed.

Actions #66

Updated by Andreas Müller almost 4 years ago

  • Related to bug #8939: Exception when opening Distribution Editor because of missing Preference added
Actions #67

Updated by Andreas Müller over 1 year ago

  • Tags set to distributionEditor
Actions #68

Updated by Andreas Müller over 1 year ago

Katja Luther wrote in #note-64:

Andreas Müller wrote:

Try to optimize the column width at start or after area selection. Details may be discussed. We have/had a similar discussion for the bulk editor in some other ticket. / der Verbreitungseditor erinnert sich auch nicht, wenn ich die Spaltenbreite verändert habe. Könnte man ihn dazu bringen, die Spaltenbreite automatisch an die Länge der Bezeichnungen in der Kopfzeile anzupassen?

To me it looks like this is not yet implemented though it is crossed out and also not moved to the follow up ticket.
If it is implemented can you please explain what the current expected behavior is if you open the distribution editor or if you selected a new set of areas

Remembering the size is still missing ...

Moved to #8889

Actions #69

Updated by Andreas Müller over 1 year ago

  • Status changed from Feedback to Closed
  • % Done changed from 60 to 100

I close this ticket. All open issues were moved to #8889 as far as I can see.

Actions

Also available in: Atom PDF