Closed neil-ices-dk closed 2 years ago
First draft of the dashboard: https://cetaceans.ices.dk/dashboard
really good visual summary Carlos đź‘Ť
Thanks @cmspinto! Nice to have something to work with - @NikiClear and I have added some thoughts to this doc to consider/discuss... Dashboard_NT_NC.docx
- Can we remove the two graphics that refer to access type – I don’t want to highlight how much data is restricted… :)
i think we need to discuss justification of surpressing this info, what is it we are afraid of?
- Can we remove the two graphics that refer to access type – I don’t want to highlight how much data is restricted… :)
i think we need to discuss justification of surpressing this info, what is it we are afraid of?
Happy to discuss - it's not about supressing the info, it's about choosing where we highlight it. The dashboard is an engagement tool for this db and highlighting how much data are restricted is a bit of a kick in the teeth against what we are trying to achieve. By not having a graphic here, we are not hiding the fact there are restricted data in the system, that is clear throughout the process docs and download system. But in the engagement tool where we are trying to support the JCDP and highlight the great steps forward in making data accessible - it's not great to have a graphic that shouts out much of the data are (currently) restricted and I don't feel we need to refer to this here.
- Can we remove the two graphics that refer to access type – I don’t want to highlight how much data is restricted… :)
i think we need to discuss justification of surpressing this info, what is it we are afraid of?
Happy to discuss - it's not about supressing the info, it's about choosing where we highlight it. The dashboard is an engagement tool for this db and highlighting how much data are restricted is a bit of a kick in the teeth against what we are trying to achieve. By not having a graphic here, we are not hiding the fact there are restricted data in the system, that is clear throughout the process docs and download system. But in the engagement tool where we are trying to support the JCDP and highlight the great steps forward in making data accessible - it's not great to have a graphic that shouts out much of the data are (currently) restricted and I don't feel we need to refer to this here.
I understand this, but one could argue that the dashboard is a visualization tool for the database, not just an engagement one. I think not showing how much restricted data we have in the dashboard is dishonest, if I'm being blunt. While we're not denying that restricted data exists, we are hiding it in a way, because we are making this fact less visible. I'm not sure if it's good policy for ICES to do this. Also, while I understand why we wouldn't want to highlight this, as a user I would be extremely irritated if I looked at the dashboard before trying the download, because I would be convinced the data are open and then I'd find out most of them aren't.
- Can we remove the two graphics that refer to access type – I don’t want to highlight how much data is restricted… :)
i think we need to discuss justification of surpressing this info, what is it we are afraid of?
Happy to discuss - it's not about supressing the info, it's about choosing where we highlight it. The dashboard is an engagement tool for this db and highlighting how much data are restricted is a bit of a kick in the teeth against what we are trying to achieve. By not having a graphic here, we are not hiding the fact there are restricted data in the system, that is clear throughout the process docs and download system. But in the engagement tool where we are trying to support the JCDP and highlight the great steps forward in making data accessible - it's not great to have a graphic that shouts out much of the data are (currently) restricted and I don't feel we need to refer to this here.
I understand this, but one could argue that the dashboard is a visualization tool for the database, not just an engagement one. I think not showing how much restricted data we have in the dashboard is dishonest, if I'm being blunt. While we're not denying that restricted data exists, we are hiding it in a way, because we are making this fact less visible. I'm not sure if it's good policy for ICES to do this. Also, while I understand why we wouldn't want to highlight this, as a user I would be extremely irritated if I looked at the dashboard before trying the download, because I would be convinced the data are open and then I'd find out most of them aren't.
Surely the 'dashboard' or data summary is whatever we want it to be on a project by project basis? This element is an addition to the landing page and search/download pages, which fulfil the needs of the project. The data summary graphics are additional as an engagement tool (at least in the case of the JCDP - it may differ for other projects?). There are many graphics we could choose to include (or exclude) but elsewhere were we refer to restricted data, we have the space to explain that this doesn't mean they are not accessible. IN a single visual graphic, I think it could look like restricted data (that are currently making up most of the JCDP, until we can get more data in!) are not available and be off-putting for users.
But, lets pick this up in our next meeting :)
@cmspinto
[x] ### for first ballon:
fix typos in title (travelled and specimen)
make at species level only
title: "average distance travelled from all surveys before sighting the species"
[x] ### survey effort
title: "Total survey effort in kilometres per year"
@cmspinto to check the unit (KMs or M?)
[x] ### observations
title: "Number of species observations per year"
legend: "Number of observations"
[x] ### balloon observations for species
restrict to species level
different colour by family
[x] ### number of xx per year
remove obs pie chart from dash
remove survey pie chart from dash
[x] ### number of xx per institute
remove pie survey
remove pie obs
[x] ### access type
remove no. obs per access type
change colour i.e. to two shades of the same colour (not red or angry colours)
labelling: restricted = "on request" public = "open access"
[x] ## number of species pies
remove number of species per survey
remove number of observations per species
add vertical bar chart of observations per species
could also add: Average of Species Observed by survey Average of KM travelled by survey Average of Surveys per year Average of Observations per survey
By the way, it is confirmed, the distance was in Meters.
I like the green boxes :)
label: "Number of data providers" label: "Number of unique species" all numbers to be in format xxx xxx 123 456
I'm not sure the averages are necessary as they are covered in the plots, and this might get too busy with too many stats
Brilliant! Thanks @cmspinto. These are great.
Agree with Neil's header tweaks
I’m not sure the averages will add much so happy to stick with actuals.
Do we need some sort of metadata to go with the dashboard, so we can provide some further information as to what is making up the numbers? E.g. is the number of species observations the number of sightings recorded, or the total number of animals recorded?
headline stats
Carlos to put at top of page (as separate page) and then we can also test adding to landing page
all numbers to be in format xxx xxx 123 456 Done: https://cetaceans.ices.dk/dashboard
for first ballon:
* fix typos in title (travelled and specimen) * make at species level only * title: "average distance travelled from all surveys before sighting the species"
Done
balloon observations for species
restrict to species level
different colour by family
Put a different color for all of them, I can try to put similar colors by family, just not sure that will be clear!
@cmspinto
[x] label: 'current data providers' (headline green box)
[x] reword: 'In this page you can explore the dashboard of cetaceans database' -> 'overview of data holdings in the JCDP data portal'
[x] move 'average distance travelled balloon' to the bottom
[x] look to see if it is possible to wordwrap the species names, so they fit within the bubbles
[x] to test a horizontal line to make a clearer visual break between charts
[x] centre justify the access pie chart
[x] REMOVE - bubble chart
abel: 'current data providers' (headline green box)
reword: 'In this page you can explore the dashboard of cetaceans database' -> 'overview of data holdings in the JCDP data portal'
move 'average distance travelled balloon' to the bottom
look to see if it is possible to wordwrap the species names, so they fit within the bubbles
to test a horizontal line to make a clearer visual break between charts
centre justify the access pie chart
REMOVE - bubble chart
@neil-ices-dk to link https://cetaceans.ices.dk/dashboard to the landing page
have added a new section
for public dashboard: generic statistics (aggregation of inventory) - no of surveys, KM's of effort, temporal coverage, species coverage - records of species (mix of charts and stats)
Originally posted by @neil-ices-dk in https://github.com/ices-tools-dev/cetaceans/issues/126#issuecomment-1149845759