Page layout

[SamuelWardPhD]

Currently we have the three pages: Problems | Downloads | About. The page 'problems' has a table of problems. The page 'downloads' has a table of datasets and also the dropdown+button to download a whole "problem collection".

I suggest the three pages should be: Problems | Datasets | About.

Problems:

• Header
• Description paragraph
• Search bar and filter by category
• Table of problems
• dropdown+button to download all problems

Datasets:

• Header
• Description paragraph
• Search bar and filter by associated problem.
• Table of datasets
• dropdown+button to download all datasets

This layout seams neater to me. The current download page with "Problem collections" and "table of datasets" seem like too unrelated functionalities to have side by side. Please feel free to criticize. Also @jdjfisher please don't feel any pressure to implement this if you don't have the free time - you've contributed far more than we've paid you for. I'm just recording my ideas while I think them :).

[SamuelWardPhD]

I will move the Download all button for datasets to the top for some symmetry.

[jdjfisher]

Ah yeah, when I was prototyping I did wonder if it should be this way. At the time I wasn't sure how much dataset content there would be so I grouped this all together on one downloads page so things didn't look too sparse. This could be reworked where the download page becomes "Datasets" and the "Download all problems" could be moved onto the "Problems" page.

Shouldn't take too long is just a matter of making everything look niceish.

[SamuelWardPhD]

Most datasets should be cited to either a paper or a repository. I have added the field "citation" which can store a BibTeX key. I run a script that looks up the reference.bib file to get the title/authors/year/... and produces a plain text reference. This is string is stored in the field "note". For this reason, it is important that the note is displayed with the datasets. I have achieved this in the Problems page. I am documenting this here in case of future work on a Datasets page. See below.