TheyWorkForYou imports the alignment scores between representatives and policies through an XML file per policy, with a line per MP. This stores this in a big key lookup rather than a specific table.
Twfy-votes replicates the current XML from public whip using the same data. In principle, just changing the URL reference should feed in the new alignment information.
Currently this mirrors the public whip export in naming conversions (dream MP etc), and XML. We have the option of changing both ends if that makes sense at this point. A new JSON endpoint would be easy to make in twfy-votes, but it seems like there’s little benefit in making a big change here.
TheyWorkForYou imports the alignment scores between representatives and policies through an XML file per policy, with a line per MP. This stores this in a big key lookup rather than a specific table.
Twfy-votes replicates the current XML from public whip using the same data. In principle, just changing the URL reference should feed in the new alignment information.
Currently this mirrors the public whip export in naming conversions (dream MP etc), and XML. We have the option of changing both ends if that makes sense at this point. A new JSON endpoint would be easy to make in twfy-votes, but it seems like there’s little benefit in making a big change here.