OpenCivicData refactoring

[jpmckinney]

• Compare JSON results between Pupa 0.4 and Pupa 0.3 scrapers
• Compare CSV results between Pupa 0.4 and Pupa 0.3 scrapers
• patch_pupa.py local file

---

Decided against doing the items below. scrapers_ca_app is nicely Pupa-only code. represent-canada mixes represent-boundaries, represent-postcodes and represent-reps. scrapers_ca_app will eventually supercede the represent-canada API by adding an Imago API (#84), which replaces the represent-boundaries and represent-reps APIs. At that point, the represent-canada API will just be a backend service (since Imago API depends on represent-boundaries, and it's easier to load shapefiles on a private server), but we'll need to integrate the represent-postcodes API into the Imago API.

• Take the needed parts from scrapers_ca_app
  • reports app without represent view
  • scrapers_ca_app/settings.py (possibly)
  • scrapers_ca_app/urls.py
  • pupa_settings.py
  • README.md (submodule setup, management commands, boto/S3 setup, eliminating duplicates)
  • requirements.txt (logutils and -r scrapers/requirements.txt)
• Update represent-reps
  • reuse code in represent view from reports app
  • update represent-reps views.py to use OCD models
  • move represent-reps utils.py into views.py
  • delete represent-reps management command, admin.py, models.py, migrations, south_migrations
  • replace represent-reps management command in crontab
  • update representatives part of represent-postcodes
  • need an alternate way of checking whether a rep's boundary can be determined

[jpmckinney]

Skipped CSV validation, as lower demand.