2020 June 28
1. One thought: when entering a series that is already on the list, it would be nice if the list automatically scrolled down to the right position. Or maybe it could appear in the dropdown, highlighted, and then if it is selected, the list scrolls so it is at the top.
I agree - particularly when the number of species shown is long, I can type in the letters for a new moth to find it missing in the list - which is odd, and then I remember it already exists in the list. I can probably make it behave as you suggest - potential with the option of greying the species already included, so the user isn't surprised when it jumps.
2. New species turn green and then red as you describe. Had you considered whether the species should return to green if the count is then reduced to zero again? Also, I just accidentally added 3 to Heart & Club instead of Heart & Dart, changed it back to zero, but Heart & Club remains red. Should really go back to black as it was not a species I added.
I was in two minds about this. Going back to black is probably the more natural behaviour.Moving to a different date and back works - data is retained.
3. Moving to a different url and back: initially, count column is blank, although species with non-zero count are still red. Also, date field shows dd/mm/yyyy. Refreshing the page by going back a day then forward again restores everything as it should be.
Good catch - this was a surprise. Then I realised you probably used the back/previous button in the browser (quite naturally) after thinking about this for a couple of minutes I believe I know the root cause - and hopefully is an easy fix.
4. Having submitted one day’s records, moving on day by day, after 4 days (i.e. submitted for 14th, move to 18th) the list shrinks a lot, but ’nan’ appears in it.
The list shrinking is most likely to do with the species caught prior to that date, so at the start of using the software, scrolling back will reduce the list. However the "nan" (Not a Number) is strange. Can you send me a screen shot or cut and paste the table into an email (don't worry if the formating gets messed up, I will work it out)
5. I mentioned this before: species column is very wide, making it difficult to read across to the count column.
I've attached a screenshot from my laptop. Is this what you see? Do you have the stripped rows? I'm just wondering what would be the easiest way for you to tell me the column layout that would work for you. Perhaps you could take a screen shot and then overlay some lines in a picture editor to show where you feel the columns should be?
6. Another thought - maybe guilding the lily here, but I have yet to set a challenge you don’t rise to! Wold be nice to see what the last data entry was, at least the species, so for those of us who get interrupted whilst entering a long list days later, and who have what I can only describe as a transient memory, we can remember where we got to. This may not seem that important, but as I am entering data from two traps, I can’t simply look at what is red in the list as I may have the same species in both traps.
I think you've realised I love challenges. From a database point of view, this is really easy - it, what was my last entry (Date, species, count). Would a menu item to go to last entry be of help - this would jump to the date of the last entry. Combining with 1. above it would then be possible to scroll to that entry. Does that work?
7. As ‘latest catches’ only covers the two weeks prior to the current date, it only contains one day for me as I’m a bit behind. Cold there be an option to change the range covered by this?
Thanks - with me trapping everyday, I don't have the discontinuity of records that shows this kind of thing up. I'm reluctant to put in configurable options if I can avoid it. There are a couple of reasons. a) It's all too easy to use these as get out of jail free cards, and avoids the designer (me) thinking about the use-cases properly. b) It adds more degrees of freedom to break things, c) I have a pathologic hate of system options that get buried in layers of badly designed menus.
I have an open issue to improve the latest catches page, as it looks awful, and I want to augment the table with highlights for FFY, First time, Earliest catch, etc.
As a counter proposal - how about, instead of the last 14 days, I list the last 14 catches, this means no configuration option needed?
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent