UI - improvements

[Jarek-Rolski]

Bellow is the aggregated feedback from my team on the additional UI changes we would like to see:

Error message:

• Column mismatch error message is a bit long though. It would be good if it could just display the incorrect columns. e.g. The schema expects column [''profession'] but your file has ['prof']. Check that all required columns are present and no extra columns have been added. For users that was the most common error they got usually because they were using an old template or had overwritten one of the column names and it is difficult to see which column is wrong in the long version
• The non-nullable error I think is very difficult for non-technies, wb ‘The column <> does not accept empty cells.’

Additional UI functionality:

• In UI it is not possible to select dataset versions on upload and download if there are different schema versions.
• Dataset domain is now freetext, would be good to have a dropdown or suggestions based on what's there, as introduces possibility during upload of wrong dataset domain in UI just being a typo
• Jobs would be good if they showed who did the upload
• If version means a change to the columns, is it just a case of having to create a new dataset unlike before where would have the version but could add/remove new columns
• Jobs page good if could be sorted by last upload/query, currently doesn’t appear to be

Other improvements:

• In Admin on Create user, I would change ‘Name’ to ‘User Name’ (I initially thought this meant my name). Maybe in the prompt we can put Firstname_Lastname too to nudge people into keeping things consistent and readily identifiable.
• ‘Add New Dataset’ sounds like it means ‘upload' to me - what about 'Define new dataset' or similar?
• Is there a way to make the upload section prominent on the homepage? One less thing to explain to users.
• Spectacularly nit-picky, but 'Fix my dataset' sounds like the fix might be automatic (even though the text makes it clear it's not). I'm not super sure how to reword this.
• Can we do some minor rewording, or put the layperson terms in brackets after the technical term (int, string, series), as I think our commission's users will find the current wording difficult;