Details
-
Type: Improvement
-
Status: Closed (View Workflow)
-
Priority: Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 9.0.1 Minor Release
-
Labels:None
-
Story Points:3
-
Sprint:Fall 2017
Description
Currently, when a new track is added, a row is inserted in the data management table at some random position.
There is code for ordering the rows, but it is not implemented effectively.
Current task:
Fix the existing method to
a) make slightly more sense,
b) actually work
The position of a new track added to the table should be consistent and predictable.
This ordering is handled by featureTableComparator in DataManagementTableModel.java.
When datasets are initially passed to DataManagementTableModel functions, the datasets are ordered alphabetically. This order may is then lost when we pass it through a hash map in the function feature2StyleReference.
Ideally, the order would reflect the order in which tracks were added, but that is a larger scope and a separate issue (see related issues).
Attachments
Issue Links
- relates to
-
IGBF-1133 ideal row ordering for data management table
- To-Do
This is an example of the new row ordering.
Notice that the top several rows are features from the same group (same folder) and they are ordered alphabetically, which is immediately intuitive.
The lower rows are from the IGB Quickload set, and some are in a folder "TAIR 10 other annotations" which puts them together as a group in the middle of the other datasets from the same source.
This is not ideal. But it is better than the previous system which did not enforce any logical row ordering.