Table results ordering

[ThomasThelen]

In the main results table, the datasets aren't ordered by any field. This can be frustrating for users hoping to quickly navigate around the table pages. One suggestion was to order by the most recent events. I like this because anyone visiting will see how up to date the database is and it gives a clear ordering.

Hurdles may be query times. We're only fetching 20/50/100 results at a time. Sorting these is quick and easy-but may give inconsistent results when the next query at OFFSET 20/5/100 is made. Realistically, it might involve ordering all of the results which will most likely take far too long.

[amoeba]

This is a situation where a graph database can't do a great job but ElasticSearch can. I'd probably dig into that. We already index all phenomenonTime triples in ES, for example.