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
Create the summary data table and structure in the Aqualink survey section.
The data table in the survey section will look like 1a in this document. This data table will be scrollable, and the full table will look like 2a in the same document. Ideally, we would like to make the tables prettier than the two examples. I can work on some design ideas this week, but please share some suggestions if you have. On the data table, we will also need to add a button saying “VIEW DETAILS” that leads to the full data table on the Detailed Data Page.
(Same info below as the issue “Reef Check - Detailed Data Page”)
It’s important to note that we’ll focus on Reef Check’s Tropical Data here. Their Tropical Data has multiple regions (6 in total), and each region slightly differs from each other. For example, their Indo-Pacific region (78% of Tropical sites) differs slightly from the Atlantic region. Notice that the Atlantic region has Banded Coral Shrimp and Lionfis while the Indo-Pacific doesn’t, for example.
One thing that we should maybe have in mind is that this data comes from Excel sheets (unless we create an API from their database), and this might be a great opportunity to think even bigger than Reef Check. Most marine and coral scientists and organizations have different survey methods and data collection methods, which makes it very difficult to create a dashboard that suits them all. However, I believe that almost all of them are storing their data in Excel or CSV files. If it makes sense for us, we could create the data tables in a flexible way that not only works for one specific type of data but for many. This might mean that we can accommodate a large number of scientists and organizations.
Please have a look at the Reef Check Report to understand how this project will be built. If you have any questions, please email Caesar at [email protected].
The text was updated successfully, but these errors were encountered:
Create the summary data table and structure in the Aqualink survey section.
The data table in the survey section will look like 1a in this document. This data table will be scrollable, and the full table will look like 2a in the same document. Ideally, we would like to make the tables prettier than the two examples. I can work on some design ideas this week, but please share some suggestions if you have. On the data table, we will also need to add a button saying “VIEW DETAILS” that leads to the full data table on the Detailed Data Page.
(Same info below as the issue “Reef Check - Detailed Data Page”)
It’s important to note that we’ll focus on Reef Check’s Tropical Data here. Their Tropical Data has multiple regions (6 in total), and each region slightly differs from each other. For example, their Indo-Pacific region (78% of Tropical sites) differs slightly from the Atlantic region. Notice that the Atlantic region has Banded Coral Shrimp and Lionfis while the Indo-Pacific doesn’t, for example.
One thing that we should maybe have in mind is that this data comes from Excel sheets (unless we create an API from their database), and this might be a great opportunity to think even bigger than Reef Check. Most marine and coral scientists and organizations have different survey methods and data collection methods, which makes it very difficult to create a dashboard that suits them all. However, I believe that almost all of them are storing their data in Excel or CSV files. If it makes sense for us, we could create the data tables in a flexible way that not only works for one specific type of data but for many. This might mean that we can accommodate a large number of scientists and organizations.
Please have a look at the Reef Check Report to understand how this project will be built. If you have any questions, please email Caesar at [email protected].
The text was updated successfully, but these errors were encountered: