Collection order is ~~the reverse of what is expected~~ not obvious

Datasets in a collection are ordered by dataset index in reverse:


If I now use the collection in a tool which depends on collection order, the datasets will be ordered as they are shown above, i.e. the first dataset is 153, the second is 152, etc. This is unexpected.

Start by reproducing the collection ordering shown in the issue and trace where dataset indexes are used to present or pass collection members to a tool. Done means the displayed and tool-consumed order is explicitly consistent with the expected first-to-last dataset order.

Written by the indexing model from the issue text.