Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor to Open States backend #1

Open
grgcombs opened this issue Feb 16, 2013 · 0 comments
Open

Refactor to Open States backend #1

grgcombs opened this issue Feb 16, 2013 · 0 comments
Assignees
Milestone

Comments

@grgcombs
Copy link
Contributor

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
@ghost ghost assigned grgcombs Feb 16, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant