Migrate from popit-django to django-popolo.

[dracos]

This involves six migrations:

• Add new PopoloSpeaker table
• Add speaker_new columns to Speech and RecordingTimestamp
• Migrate all speaker data from Speaker/Person tables to PopoloSpeaker
• Remove the old Speaker table and speaker columns
• Rename the speaker_new columns to speaker
• Rename the PopoloSpeaker table to Speaker

[lfalvarez]

Hey there I've a question. Does this migration from popit-django to django-popolo include a tool to populate from popit? does it make sense to have a migration?

[dracos]

Hi @lfalvarez - if you had already been using SayIt before this change, then your data would be converted automatically by the database migration, yes. This pull request was simply about how the underlying data is stored in SayIt. If you mean a way to import data from a PopIt instance into SayIt, then there are two related tickets:

• General popolo JSON import script #310 is to have a general Popolo import script - there are existing particular scripts such as https://github.com/mysociety/sayit-philadelphia/blob/master/bin/import-people.py and https://github.com/opennorth/openhousens.ca/blob/master/legislature/management/commands/load_popolo.py which can be adapted currently, and we (or perhaps someone else :) ) will create a central one at some point
• Add feature to let me add names from one or more popit instances #231 is to have a front end web interface for basically the same functionality, allowing you to specify data in some way (Popolo JSON URL, PopIt URL, etc) to be imported.

[lfalvarez]

Thanks @dracos this was exactly what I was asking for =).