Currently, an order is applied to the rows and this order does not take into account the order in which datasets were added.

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 row order in the data management table would reflect the order in which the datasets were added. When a track is added, it should be added to the top of the table, where it is most likely to be visible. Tracks in main view are added at the top, so by default, tracks will be added in the same order in both locations. The table will keep the order-of-adding and the main view order can be changed by the user.

At the moment, I don't know of any structure that holds information about the order in which datasets are added. We also don't know if any other features depend on the alphabetical ordering that the list of datasets comes with.