Open mhl opened 9 years ago
A summary of the progress so far (in 1594-django-popolo-migration):
popolo.models.{Organization,Person,Post}
have been created as pombola.core.Popolo{Organization,Person,Post}
with the missing fields added.core.Organisation.name
needed 200 chars but popolo.Organization.name
is defined with 128 max_length
, and you can't redefine fields in model subclasses so we're using our own fork of django-popolo with max_length
set to 4000 for a few fields.ContactDetail
model).I have been keeping some notes whilst working through the process.
@dracos points out that mysociety/sayit@46b4dc8bbc66741fbcf203e46dd735b80b52e089 might be handy, too.
@duncanparkes and I have done some more work on the data migration, adding migrations for the rest of Person's relationships as well as Position, Organisation, Identifier, and AlternativePersonName.
Those that still need attention include:
After a quick survey, the other models that refer to the core objects that are being changed in this migration are:
Things to check:
I'm creating this new ticket to more accurately represent the work involved in this. (We had been using https://github.com/mysociety/pombola/issues/1551 as a placeholder for this job.) This plan probably needs some work.
The great advantage in doing this is that SayIt, when embedded in Pombola, and the rest of Pombola's code would use to the same Person objects. This would remove complex layers of indirection and state, and be a good step in reducing the complexity of maintaining the Pombola ZA scrapers. It's also a good move in terms of code reuse and moving Pombola to be more like a collection of components.
class Person: pass