Let me think about this. Some data, such days to hatching, max length at various ages, etc., will be tied together based on feeding, crowding and temperature parameters with each each spawn. Those don't intrinsically represent reproducible data but might be left as a single number such as (what is the largest size achieved at age for all your spawns). In other words, so fish grow slower one spawn and faster the next; that doesn't change what they're capable of doing, so that can be a single number which the user is encouraged to update if it changes from spawn to spawn.
But variables that are not linked from spawn to spawn such as tank size, temp, pH, hardness, conductivity, number of males/females and body length of smallest parent; body length specifically also influences gonad size and will therefore have some correlation with # eggs laid; as parents grow, so too might clutch size increase with successive spawns. I know I've observed that with many species from "first" spawn to later spawns.
So these are the types of data that are probably worth collecting in such a table form.
Thinking of the display of a BLOG page as it exists now, for any BLOG reporting a single spawn, I see no reason to reorganize the page display. But for multiple spawns, instead of itemizing dates (as is the current display for multiple spawns), could we build an expanding table with a single row of headings?
In such a case with repeated spawns, maybe it would be fine to report singular temperature, hardness, conductivity and pH values rather than ranges as is the case now. Readers can still infer the ranges by looking at variation between single values for the different events. The rest of the BLOG (remaining data and narratives) can still be displayed in text entries as they are now in current displays.
- table.png (7.11 KiB) Viewed 107 times
This is an incomplete thought on my part. Work is rather busy as end of semester approaches. But these are my initial thoughts without filter.
Cheers,
Eric
