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
Are meeting_date and meeting_time supposed to be local, or always UTC? In either case I think adding an optional meeting_tz field would be helpful, otherwise sorting across multiple jurisdictions becomes impossible. FWIW in openstates we landed on enforcing scraped dates to UTC, and including a timezone. This is also helpful in places like Kentucky with multiple timezones.
Adding an optional field for Opencividata division ID would allow this output to be mixed with other projects more easily.
If you're interested in either of these, I'd be willing to drop a PR. I can also potentially contribute some mappings of ocd-ids and timezones, since I know that the biggest hurdle there is mapping all that data.
The text was updated successfully, but these errors were encountered:
Hey @showerst Sure, those are both great ideas. Would you mind adding those as optional kwargs? Just want to make sure we have some flexibility going forward, especially with regard to the OCD IDs for bodies that aren't currently reflected in the standard. Thanks!
I have a few suggestions on the data model --
Looking at the Asset model:
meeting_tz
field would be helpful, otherwise sorting across multiple jurisdictions becomes impossible. FWIW in openstates we landed on enforcing scraped dates to UTC, and including a timezone. This is also helpful in places like Kentucky with multiple timezones.If you're interested in either of these, I'd be willing to drop a PR. I can also potentially contribute some mappings of ocd-ids and timezones, since I know that the biggest hurdle there is mapping all that data.
The text was updated successfully, but these errors were encountered: