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
Currently the data comes from my own MySQL server ... Manually collated from Open States, various Texas House and Senate publications, and previously Vote Smart before they monetized their data.
As such, data updates are slow to put together and the users get cranky.
I'm thinking that I should convert the data framework to a newer RestKit, switch to using Open States's primary keys and then use Open States server as the primary provider in the app. Then secondary/auxiliary details will be filled in by my MySQL server.
Open States Data:
Basic Legislator details
District office contact details
Basic Committee details
All bill tracking (done)
All district maps
All events/meetings (done)
Capitol maps
TexLege Data:
Legislator partisanship scores
Legislative email info
Committee staff and contact info
Legislative staff and contact info
The text was updated successfully, but these errors were encountered:
Currently the data comes from my own MySQL server ... Manually collated from Open States, various Texas House and Senate publications, and previously Vote Smart before they monetized their data.
As such, data updates are slow to put together and the users get cranky.
I'm thinking that I should convert the data framework to a newer RestKit, switch to using Open States's primary keys and then use Open States server as the primary provider in the app. Then secondary/auxiliary details will be filled in by my MySQL server.
Open States Data:
TexLege Data:
The text was updated successfully, but these errors were encountered: