You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Below is a catalogue of the different feedbacks provided by the crowd during the 2019 Data for Good Exchange at Bloomberg NYC.
Note: This is meant to be as representative as possible of the Developer session but I think that I still miss some information here.
Need to open the platform to non-scientists:
This will ensure more data is fed into the platform, which is key to its success. People who always go on vacation to the same area, or amateur diver would typically fall under that new user-group.
This involves the creation of at least 3 additional features:
Non-scientifc user flagging : The user should be identified as scientific or non-scientific in order to provide the ability to filter only credible sources during analysis.
Embedded training on the platform: In order for more non-scientific users to contribute, there need to be some onboarding material for new users who want to start contributing without a PhD. (Mention of Fish IDs)
Picture upload: User should be able to provide picture of corrals and fishes he would have taken when unaware of the species's name for instance, so other users can label it afterward.
Need to tailor the UI to each decision makers profile:
There are at least 3 identified map version that we could think of which would appear depending on the user's profile:
Donor / Country Government specific view: This view provide filters/highlights only the regions and associated KPIs that the donor has made contribution to or for which the country's government is interested into.
General User view: No filtering on the sites and/or country.
Media UI: providing almost ready to be used KPIs on specific regions for the media to report - an easy sharable feature on Facebook, Instagram, Linkedin etc could be straightforward to implement for instance.
Need to enrich the data sets to deliver analytics services:
The long term plan of the dashboard should follow something along this line:
Phase 1) Data Acquisition - mainly generated by the platform's users.
Phase 2) Data Enrichment - through 3rd party API providing information about temperature evolution, storms and hurricanes, Ocean currents, satellite imagery etc providing deeper analysis.
Phase 3) Analytics services resulting from Phase 1) 2) providing systematic prioritisation of actions on sites, alerts system, prediction on future degradation etc. These services could potentially be monetized as part of maintaining the platform.
Other interesting points
Need to link the data to the sites, not to the users.
Fish IDs
Need ensure that the metadata / user provided inputs are standardized while leaving room for additional information and columns for instance
The text was updated successfully, but these errors were encountered:
Below is a catalogue of the different feedbacks provided by the crowd during the 2019 Data for Good Exchange at Bloomberg NYC.
Note: This is meant to be as representative as possible of the Developer session but I think that I still miss some information here.
Need to open the platform to non-scientists:
This will ensure more data is fed into the platform, which is key to its success. People who always go on vacation to the same area, or amateur diver would typically fall under that new user-group.
This involves the creation of at least 3 additional features:
Need to tailor the UI to each decision makers profile:
There are at least 3 identified map version that we could think of which would appear depending on the user's profile:
Need to enrich the data sets to deliver analytics services:
The long term plan of the dashboard should follow something along this line:
Phase 1) Data Acquisition - mainly generated by the platform's users.
Phase 2) Data Enrichment - through 3rd party API providing information about temperature evolution, storms and hurricanes, Ocean currents, satellite imagery etc providing deeper analysis.
Phase 3) Analytics services resulting from Phase 1) 2) providing systematic prioritisation of actions on sites, alerts system, prediction on future degradation etc. These services could potentially be monetized as part of maintaining the platform.
Other interesting points
The text was updated successfully, but these errors were encountered: