You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unfortunately, JailTracker does provide datetime strings for important dates, but they don't seem to be timezone aware. For example, the special field "Booking Date" is provided as text "8/3/2024 4:30:00 AM" in the response JSON.
Date-only fields should be left as-is, since we don't know the local time on the date to then infer the date in UTC.
Datetime fields should be maintained as is, but each should also be converted to UTC+0000 and saved in a <fieldname>-UTC. Conversion should be done based on
This can be applied retroactively to existing data via a script, so this isn't so urgent.
Currently, JTT's queries are dumped to disk with a filename indicating the name of the facility and the date string (in UTC+0000). It would be helpful to know the more exact times the script began and ended, and have them saved at the top-level of the job's output JSON. This is more urgent, since we can't determine this retroactively.
Tasks:
Urgent: add job begin and end timestamps to JSON output.
Add UTCOffset field to JailConfig type.
Update all jail configs with state and UTC offset.
Using the facility's UTC offset, add -UTC datetime field for each existing datetime field.
Add script to update previous JSON outputs.
The text was updated successfully, but these errors were encountered:
Unfortunately, JailTracker does provide datetime strings for important dates, but they don't seem to be timezone aware. For example, the special field "Booking Date" is provided as text "8/3/2024 4:30:00 AM" in the response JSON.
<fieldname>-UTC
. Conversion should be done based onCurrently, JTT's queries are dumped to disk with a filename indicating the name of the facility and the date string (in UTC+0000). It would be helpful to know the more exact times the script began and ended, and have them saved at the top-level of the job's output JSON. This is more urgent, since we can't determine this retroactively.
Tasks:
UTCOffset
field toJailConfig
type.-UTC
datetime field for each existing datetime field.The text was updated successfully, but these errors were encountered: