Reverse release.geneontology.org/ sort order, increase default display count for usability

[suzialeksander]

release.geneontology.org/ currently sorts old->new as default. Can we just flip this so it's new-> old?

Most users (including me) are more interested in releases from 2020-2021ish than the 2004 releases.

[pgaudet]

I would also like that!

[suzialeksander]

@lpalbou, two more related points:

• From manager's call, can you also remove the "show 50" default? We think "show 1000" as default will buy us a few years.

• The last thing mentioned at Manager's was to hide the fields that aren't really helpful to the user: Timestamp was the first field called out, but if the others (Last Modified, Size) are blank or generally unhelpful they also should be hidden. The Last Modified is misleading to users when it's showing the date we just added the file rather than the date the file was originally compiled (see http://release.geneontology.org/2004-06-01/annotations/index.html)

To clarify, Size is really helpful once in a directory, but on http://release.geneontology.org/ it's always blank. Can those blank fields be hidden on http://release.geneontology.org/ and only shown if there's info, on e.g. http://release.geneontology.org/2004-06-01/annotations/index.html

[lpalbou]

Since this now contains both the archive and the current releases, I also think it's more logical to have newer releases first.

Columns Last modified and Timestamps are now hidden since the "Last modified doesn't reflect the date of the release in any way and Timestamps is not really helpful either.

I have merged my code (https://github.com/lpalbou/aws-js-s3-explorer/pull/2) and you can see the resulting changes on my temporary site: http://release.geneontology.xyz/. To take effect on the go site, only @kltm can deploy the changes with the usual command line:

python3 s3_add_index.py -o <bucket_name>

[suzialeksander]

This looks better as far as hiding 'Last Modified'/etc. but on http://release.geneontology.xyz/ I only see three entries, and the releases appear to still be in old -> new order

[lpalbou]

@suzialeksander release.geneontology.xyz is my test site as I don't have the privileges to deploy on release.geneontology.org and indeed, I only added 3 releases there for the illustration so no issue here.

For still showing older releases first, you probably have to clear your cache as it does display the newer releases for me after a refresh:

Once @kltm deploy the changes to release.geneontology.org, you will see all the releases as usual.

[lpalbou]

Done.

[pgaudet]

Thanks !