christian-rli
christian-rli
It's not clear what's more relevant. Create a concise list of more important fields and highlight those. Pro solution: prompt the user in descending order of importance.
There should either be a proper welcoming page or users should at least be brought to the profile page.It's confusing when new users are made to think they still need...
API should require setting a license, so that only (openly) licensed data is uploaded. That would require an extra field with e.g. with a link to the license and an...
It's possible to download datapackages and metadata json files via the API. However that function was no findable to test users. Decide on a good place to document.
When filling out metadata it's sometimes not clear what's required in a field. Mouse-over texts are helpful, but an additional help would be example values that appear in grey to...
The review process is too complicated, especially if to attract volunteers. Significant parts of it can be automated. All of that should be integrated into the oep. If it's easy...
It is not clear what tools, knowledge is necessary to work with data or what options are available. This should be linked to in the database view(s).
Add info on what data there is, how to open/use it or add that as an info section in the FAQ. This was requested by test users. Also see #737
Users found that documentation on factsheets was missing. Why are they there, how are they created and what's their relation to the data. Some, if not most of that information...
The data types in the column correspond to PostgreSQL data types. A dropdown list appears, but isn't explained. A simple table view with an explanation per data type for use...