Argument in favor of NOT reordering before or directly after setting or getting in LoadData(). This is a UI human preference issue and should be handled by a custom "order by" method in a client Utility folder.
Slowing the data processing of all other collections puts the burden of one collections organization unfairly on all the other collations being processed.
A separate utility method can be adjusted for any future collections to utilize.
Managing this utility separates it from the larger code base for any updates or testing.
Functionally, the same process would be implemented in the xmlwriter so this acts as template if a later move is desired later.
Just a thought.
Argument in favor of NOT reordering before or directly after setting or getting in LoadData(). This is a UI human preference issue and should be handled by a custom "order by" method in a client Utility folder.