Dataset Key

[MortenHofft]

Essential

• We also need taxonomy as a tab for checklists. This should allow users to explore the taxonomy and view individual taxa while staying on the dataset page. This is different from gbif.org where we treat all checklists the same as the backbone taxonomy (gbif core one we use to organise occurrences against). This is a cause of confusion. To make the datasets more complete and self contained we add a taxonomy tab instead. For now we will use gbif APIs not ChecklistBank
• taxon details: Either show inline or as a drawer. Keep it as a fairly raw dump of the provided data. Link to checklistbank.
• Trusted contacts - On gbif.org we have the concept of trusted contacts. When a user is logged in with an email that appear as a dataset contact they get extra information. I suggest to strike that part and just keep the link to the registry https://registry.gbif.org/dataset/50c9509d-22c7-4a22-a47d-8c48425ef4a7 . This spares us having an authenticated proxy for crawling. It is a left over from when we didn't have a public registry.
• current metrics tab: metrics tab with taxonomy metrics + occ metrics.
• activity tab or similar (download list + citation metrics). Ideally some downloadable roll ups

Also important, but I would assume above are more essential

• We probably need a more prominent map. Might be worth asking others.
• ebird has that special rule that shows publishing countries, see gbif.org for example
• phylogeny tab (same styling concerns as for the occurrence details)
• phylo tree loader
• phylo tree how does it work with multiple trees (i notice that the tab is plural so i assume it can have many)? how should they be navigated. Should the tree be in a card perhaps? A TOC?
• mobile layout of sidebar. (slidein? expand? inline? metrics section?)
• check edge cases, with no data, no occurrences, checklists etc.
• events tab . suggest we postpone this for a while, but at some point we need to add this as well. We have an API, but I'm mot sure about the state of it. We haven't added it to graphql either yet.
• html encoded characters do not show nicely. We should decide if this is reasonable data or not before trying to fix anything. example: /dataset/87ed95eb-4ead-465e-9c3a-7d9e9be4035d