Django project and applications to ingest and display election results and force aspects of the political process to give each other a clean handshake ... with gloves on.
LAC/SOS are handling Supreme Court justice contests differently.
SOS scraper is creating a unique contest for each Supreme Court justice but only one contest for each Court of Appeal district, even though they are similar yes/no confirmation votes rather than competitive elections.
LAC scraper is now handling the Supreme Court and Courts of Appeal the same way, lumping together all candidates under one contest (so all SC candidates under one "Supreme Court" contest, all appellate candidates for district 2 under one "Courts of Appeal District 2" contest, etc.).
There's probably no right answer here, but we have to make a choice and stay consistent. I think it's probably a little neater to lump the judicial candidates into larger contests (i.e. Supreme Court, Court of Appeals 1, 2, etc), even though they're not actually competing against each other. On the other hand, it may be more accurate to break them out into separate contests, so it's clearer that these contests are not competitive.
This latter approach requires a little extra refactoring for both SoS and LAC scrapers.
Moved supreme court races in SoS to match others. Need a little more information about the "little extra refactoring for both SoS and LAC scrapers" that is required.
LAC/SOS are handling Supreme Court justice contests differently.
There's probably no right answer here, but we have to make a choice and stay consistent. I think it's probably a little neater to lump the judicial candidates into larger contests (i.e. Supreme Court, Court of Appeals 1, 2, etc), even though they're not actually competing against each other. On the other hand, it may be more accurate to break them out into separate contests, so it's clearer that these contests are not competitive.
This latter approach requires a little extra refactoring for both SoS and LAC scrapers.