Occurrence download fieldnames

"As anyone, I can easily understand what field names in observation data mean"
"As anyone, I can find documentation about the field names in plain text in Finnish and English"
"As a public authority, I want the data download to include fields that are relevant to my work and nothing more, so that I can easily find the information I'm looking for"
As anyone exporting data (citable download), I get it in a easily understandable, documented and usable format, and containing all relevant fields, so that it's easy to use.
Good titles, possibly multiple titles in different languages
Descriptions of different fields, like coordinates
No need to go through multiple steps to get special characters and numbers to work correctly in Excel.
Showing location accuracy and real geometries
Relevant fields (depends on data and use cases)
Removing points from titles

Fields that users have requested:

[ ] LajiGIS bird of prey breeding success
[ ] Vihko Bird status (multiple value sin one field)
[ ] Original location geometry
[ ] Verbatim coordinates, usually YKJ grids
[ ] Location accuracy
[ ] "All Vihko fields"
[ ] If a field has multiple values, include all of them semicolon-separated
[ ] Original coordinates - not just verbatim, but original string (Geojson or whatever)
[ ] Higher taxonomy: genus, family, order, class ...
[ ] Maybe: informal name groups in separate fields, so that filtering and sorting is easier.
[ ] Regulatory status (hallinnollinen asema) – to be added in full downloads and as a selectable field in lite download
[ ] Taxon ID – as selectable field in lite download
[ ] Informal groups – as selectable field in lite download
[ ] Location accuracy – as an obligatory default field in lite download to make sure that users will notice that the location is not necessary accurate
[ ] Taxon primary habitat
[ ] To think about: some fields in current downloads rarely contain data and some may not be necessary at all – at least for public authorities. Lots of complains about too many and unnecessary fields in data downloads.

Discussion on Slack Oct 11 2024:

Adopt DwC standard terms as much as possible.
Make fields user selectable.
- Improved documentation what the fields mean, so users know what to select
- Better UI, e.g. to to have sensible defaults, ordering, remembering selections (if we include every field we have, including facts, there will be more than 1000 of them)
Offer DwC archive as a download format for users comfortable with that (DwC archive v2 is coming soon with an updated schema)
Offer a "Simple Download" format based on single flat table (could be excel file, could be plain txt).
For (4) Map DwC normative terms to non-technical-user versions and localise them to Finnish, Swedish and English