Closed stenington closed 9 years ago
I'm thinking about writing a management command to import data from the greatschools API to a School model, and then referencing those from the other models. For new schools that don't exist in the greatschools data or haven't yet been imported, I'm not sure if it's better to create a new School model with some flag indicating it as "unofficial" or to keep that data in a freeform field on the Student or ParentGuardian model or whatever. Allowing the creation of School models by hand would mean potential dupes or conflicts when importing from greatschools and that adds a bunch of complexity.
I think the interim plan will be to import keytag schools, present a dropdown on Person, and add a "Notes" field or some such thing to capture any data that needs to be captured in the moment and fixed up later, like the name of a school not yet in the system.
Looks like the keytag data already has duplicate schools, so de-duping will already need to happen. 2/3 of all entries don't seem to include any sort of useful unique identifier.
Actually there only seem to be about 31 school sites and 2 non-school sites in the old keytag data (although I'm not sure I'm looking at 100% recent data). Maybe it's worth being strict about site data in the new app to prevent dupes from happening, even if it means doing some manual lookup to find school ids or something.
Although then people in the system have been associated with more like 131 schools, it seems?
First pass at this is going live. Will open new ticket if it needs more.
We might be able to use values from http://greatschools.org but sometimes new schools aren't in there, so an 'Other' field or way to expand the list would need to be included.
However students should be associated with a school, and it might be useful to associate parents with multiple schools.