Usage notes 2023 05 17 - ironwoodcall/TagTracker GitHub Wiki

using TagTracker during an afternoon shift TG shared with DS. Used csv2tracker to convert morning gsheet, then played catch-up.

• make in/out confirmations more visually distinct. Even after using TT sometimes someone would forget to register a check-in, which meant that when we went to check them out the system registered that as a check-in. The more different they look the more likely a person will twig to it
• Recent -- put "--------" at block boundaries
• allow "e" to create a tag (check-in) entry. definitely.
• if there's an 'unknown' bike tag, would it be reasonably to allow a person to (with confirmation) override it? This might be tricky since system wouldn't know if they're regular or oversize
• make "y/n" prompts always have the same default (probably "n"). Working as valet is on ones feet and glancing at the screen, very different than sitting at a desk. Same would cut down on surprises.
• "c" could show colour codes (w white, k black b blue, etc)
• DS says JM would like it to list retired tags. System can certainly do that, but what is the process to keep the retired tags config up to date?
• able to share a drive between chromebook linux and chrombook google drive. Put sharing to JH, TG on that folder. SUGGEST moving all data files to a "data" (not "logs") folder, which is symlink to the shared area. (That way, can remotely update configs.) Also maybe whole TT dir, can then update the program as well. URL of logs data (not live)
• y/n "sameness" of time confirmations:
  • when try to check something in when already have, always asks if sure. Surely we can simply say "ignoring repeated check-in of {tag}, use 'edit' command if you really want to check it out now" if it's less than 5(?) minutes
  • lower "sameness" for y/n confirmation from 30' to 15'
• colours went funny at some point. This was because somehow ended up with text as 'selected' and there is specific way (click outside the selected area -- typically the far R of the screen) to make it stop
• need to think through, document, and prob train for common workflow issues. Noted today:
  • checking out, discovered it wasn't checked in.
    • <tag> to go ahead with the check in
    • e <tag> i
    • <tag> to check out
  • checking in, tag is "unrecognized" [i.e. not in the tag cfg files]
    • right now, that's hand-edit
  • checking out, is already checked out.
• I wanted to do "tag [time]" or tag [i|o] [time]. Why can't I?
• BUG was unable to delete tag wa7 which was checked in but not out
• "stats" should probably default to end of day

If I open a logfile from an earlier date then TT might start to muck with it, and put its own datestamp in there. Yuck. Maybe have TT read and write datestamp from file, and not muck with it. Add command to set date.