timetracker
timetracker copied to clipboard
anuko
Add GPS info to task and project
Additional GPS information aids project managers to assure that the work was done in specific location, e.g construction workers. It would be nice to also see the map with a pin while reviewing tasks afterwards.
This may make sense for orgs that must track user locations, in situations where IP is not enough, which is already included. If someone wants to implement this, I suggest making this and IP tracking option configurable (turned on or off) on group level, and introduce another table for tracking data only, this way we don't flood the database with unneeded data for groups that do not require location tracking.
Would it make sense to implement this as a plugin combined with supporting arbitrary attributes ("user-defined fields") to time events in core functionality? (i.e. The GPS plugin would create and populate a new user-defined attribute it would create during plugin setup. Cheers, Dale From: anuko Sent: Wednesday, January 9, 2019 8:41 AM To: anuko/timetracker Reply To: anuko/timetracker Cc: Subscribed Subject: Re: [anuko/timetracker] Add GPS info to task and project (#69) This may make sense for orgs that must track user locations, in situations where IP is not enough, which is already included. If someone wants to implement this, I suggest making this and IP tracking option configurable (turned on or off) on group level, and introduce another table for tracking data only, this way we don't flood the database with unneeded data for groups that do not require location tracking.
-- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/anuko/timetracker/issues/69#issuecomment-452741723
Unless I am missing something, and if I understand the GPS wish correctly, the idea is to use client-side HTML5 geolocation API, built into modern browsers. If users allow such tracking, then transmit and store coordinates and accuracy on the server in Time Tracker database for future reference, together with browser IP that we already provide.
User-defined fields are server-side things. In terms of implementation complexity, custom fields are more complex, as more fields would inevitably complicate reports queries (which are not simple already) and rendering, and other related things.
These two, in my opinion, do not belong together. Also this violates the Unix design principle "do one thing and do it well".
Unless I am missing something, and if I understand the GPS wish correctly, the idea is to use client-side HTML5 geolocation API, built into modern browsers. If users allow such tracking, then transmit and store coordinates and accuracy on the server in Time Tracker database for future reference, together with browser IP that we already provide.
Yes, I ment HTML5 geo API.