ruthmoog / bee Goto Github PK

Fix needed: Somehow static assets are being cached so that after we deploy we don't get the new stuff (which is annoying! :D)

Meta data for a walk should include weather information

• sunshine (sunny OR sunny/cloudy OR cloudy)
• Temperature (°C)
• Windspeed (Beaufort scale 0-6)
  
  ^{↑ windspeed descriptions summarised from Beaufort scale}

^{↑ form fields when submitting Bee Walk data}

• These metadata could be automatically logged when a user starts a walk #7
  • Met Office APIs are not free but there are some free APIs out there that might be ok?
  • Weather API
  • Open Meteo
• Fields should be editable incase the API data is not accurate
• When walking manually I would set the data here at the beginning of the walk. I would only change that if the weather changed dramatically, or changed for the the majority of the walk
• Walks only take place in reasonable weather conditions

• Clearing data
• page refresh

At the moment the wind speed field is editable as free text. This is ok, but there should be a drop down available for the user to select one of the Beaufort scale items incase the data from the weather API is not accurate.

• Wind speed has a Select of options when in edit mode

Snippet of windSpeed text from src/weather.js

export const unableToFetchWindSpeed = "Unable to fetch wind speed";
export const calm0 = "0 <dfn>Smoke rises vertically</dfn>";
export const lightAir1 = "1 <dfn>Slight smoke drift</dfn>";
export const lightBreeze2 = "2 <dfn>Wind felt on face, leaves rustle</dfn>";
export const gentleBreeze3 = "3 <dfn>Leaves and twigs in slight motion</dfn>";
export const moderateBreeze4 = "4 <dfn>Dust raised and small branches move</dfn>";
export const freshBreeze5 = "5 <dfn>Small trees in leaf begin to sway</dfn>";
export const strongBreeze6 = "6 <dfn>Large branches move and trees sway</dfn>";
export const highWind7toHurricaneForce12 = "⚠️ Avoid or abandon in bad weather";

• Unit tests
• Browser tests
• Deploy to fly.io

Would be useful if touching the bee name when the walk has finished, strikes-through the text in the table - makes it easier to see which rows of data have been entered into the survey data system.

• Touching a bee name will strike through the row text when a walk is finished
• Touching elsewhere in the row will let the user view and edit comments as normal

ie not like this:

Number of bees: {"Tree":7,"Common Carder":5,"Shrill Carder":39}

GitHub Dev Hackathon blog post

Have an option to view and log bees by common name (eg red-tailed bumblebee) or scientific Latin name (eg B. Lapidarius).

related to #10

User should be able to delete entries if they made a mistake, or update the number in the cell in edit mode, and save changes

When you do a bee walk, you go through a fixed "transect" which has sections. It would be nice if whilst walking around, when you make a sighting, it knows which section you're on

We can easily get the location from the browser, and then we have to somehow know "this geolocation maps to this section"

Whilst doing raw JS is fun and rock and roll, in practice we're going to have to render stuff in the DOM fairly dynamically and that can get a bit unwieldy.

React is maybe a bit heavy for this, but maybe something like Svelte could be worth a spike to see if it can make things simpler

• Space between lines of sections
• Line wrap for weather scale
• Table falling off edge of screen

would be nice to have some visual feedback on the buttons when pressed, the bee caste buttons in particular

• position of the save/discard comments buttons should be relative to the text area so they don't appear off the screen
• Add text to inform clicking a row will allow adding comments

User should be able to add comments to the observations table.
Perhaps to save real estate, rows with comments should show a speech bubble symbol, which displays a text field on tap?

Currently the list of species is hardcoded in the HTML:

<fieldset>
    <legend>Choose a species:</legend>
    <select id="species">
        <option>Bumblebee Bombus</option>
        <option>Honeybee</option>
        <option>Common carder</option>
        <option>White-tailed agg.</option>
        <option>Red-tailed</option>
        <option>Early</option>
        <option>Buff-tailed</option>
        <option>White-tailed</option>
        <option>Garden</option>
        <option>Tree</option>
        <option>Brown-banded carder</option>
        <option>Moss carder</option>
        <option>Red-shanked</option>
        <option>Ruderal</option>
        <option>Shrill carder</option>
        <option>Short-haired</option>
</select>
</fieldset>

• This list could be brought in dynamically
• Maybe it can be searchable, ie filters in matches when you start typing
• It could also be ordered based on locale and scarcity (so that the most likely seen/recorded bees are at the top of the list)

related to #14

Replace

let thing = // some code
if(!thing) {
   thing = {some: default}
}

with

const thing = // some code ?? {some:default}

Meta data for a walk should include the start time and end time:

^{↑ form fields when submitting Bee Walk data}

• The start and end time should be recorded in the local storage
• Walker should click a button to start their walk
• Could potentially be combined with GPS to end the timer when walker crosses the point where the final section of their walk ends
• The start and end time should be displayed so the walker knows it's being recorded

eg API selects 'cloudy' weather but user can change it to cloudy/sunny if thats more accurate - assume all fields should be editable

In the submission system, Temp is a drop down of whole numbers in Celcius. At the moment in Bee, a temp can be displayed with a decimal point.

• Temp should be rounded and displayed as a whole number.

I've added a test bee.spec.js/Change walk meta data which is testing the edit/save metadata functionality, however negating the toBeEditable method is not working how I expected. It seems correct in the UI but the not isn't getting passed playwrights checks

        await expect(endTime).not.toBeEditable();

https://playwright.dev/docs/api/class-locatorassertions#locator-assertions-not