OrcaHello summary page

[akashmjn]

This issue is describing a summary/landing page for the portal http://orcahello.ai4orcas.net. This is a high-level outline that will need to be broken down into various sub-issues @micya.

Why

When pointing someone to this project, there is a need for a page on the OrcaHello portal that summarizes key metrics for an interested person with something they can quickly listen to/engage with.

Since it went live in September 2020, it has enabled 24×7 monitoring of 3 hydrophone locations by significantly reducing moderation time to an average of 10 minutes/day. So far, this has allowed experts to issue over 60 notifications of the whales’ approximate location to partner organizations, to inform vessel traffic slow-downs or halt construction. [FOR DETAILS SEE LINK]

i.e. in addition to the description on https://ai4orcas.net/ it is:

• a "for details see link" page that someone can quickly browse and get the impression this is actually live
• for a broader audience that wants to quickly learn more and get an idea how it's been working (not a deep analysis dashboard)
• a share-able snapshot of key metrics important for the project

Making it easy to put this together will likely also help streamline other areas of the project

What

Ideally it is the landing page for the portal on http://orcahello.ai4orcas.net containing the following:

1. Introductory text context
2. Summary of key metrics:
   a. daily detections requiring moderation (avg in minutes)
   b. number of confirmed alerts issued (1 for each event)
   c. hit rate (% of known events caught)
3. Latest Notifications/Greatest Hits: section to engage and listen to latest detected alerts, additionally a curated collection of other interesting sounds (e.g. humpbacks, otters, boats/ships)
4. Follow up text content (e.g. contact info for alerts, Github link for contribs, success stories)

Item breakdown

• nit: the portal currently resides at https://aifororcas.azurewebsites.net , @micowan doable to actually have it at http://orcahello.ai4orcas.net without redirect?
• items 1, 3 and 4 are largely independent from 2. mainly need a page and decent (doable by @scottveirs) way to author/update it
• item 2 will take more work as the data isn't as readily accessible or aggregated. a good first step is being able to manually generate a table by running a single python script
• for 2b confirmed detections need to be aggregated (i ended up searching gmail threads to get the 60+ number above)
• for 2c this spreadsheet contains a lot of reference info but needs to be structured and accessible via script. at minimum a table with time ranges and location for all known SRKW events
• (nice to have) for 3 a way to link to / browse an "event" (a collection of detections) like it’s done for individual detections

[catskids3]

I think most of this is doable with the information we are already collecting. Some things to consider:

1. The latest notifications/greatest hits, would that be a manually curated list or an automated one (say show the last 5 confirmed detections)? If manually curated, would that be a separate process from moderating the calls or part of the same process?

2. The other interesting sounds list, would that be a manually curated list or an automated one (say show the last 5 for the following tags). If manually curated, would that be a separate process from moderating the calls or part of the same process?

3. The introductory and follow up text, would that be fixed/hardcoded, or should be editable by moderators/administrators?

I think it would be a good idea to get Claire or another UI person to work with Scott and/or Dave to mock this up for discussion and approval.

These are just my thoughts.

[catskids3]

BTW. This is Mike Cowan. catskids3 is my GitHub account.