-
Notifications
You must be signed in to change notification settings - Fork 21
Duplicates of 2015 candidates who have stood down #193
Comments
Could add a “These candidates from 2015 are known to have stood down” section (or similar) |
The only complicated thing about doing this is in order to avoid doing a second query from PopIt (using the search endpoint on |
Good example, @sjorford, RichCBury1 added him using the dailyecho source, he was deselected and no longer appears on http://www.ukipsoutheast.com/constituencies.html, and then RichCBury1 added him again using the same dailyecho source! @mhl If it's complex to implement, I'd say it has low priority since it can be fixed by looking for dupes. |
Sorry – hadn’t realised it was an issue at PopIt level. “NotACandidate” doesn’t sound ideal :\ |
…lock-data-migration Fix a stupid error in the SuggestedPostLock data migration
While dupe hunting I've found a few cases where a candidate was added as a new 2015 candidate but was subsequently stood down for some reason. Another editor then finds the original source of their candidacy and re-adds the person, not realising that they'd already been added and removed.
These are fairly easy cases to handle, since they will have the same name, and appear in the same constituency with the same sources, so you can verify that they're the same person for merger, but it is a case of data quality not necessarily increasing over time.
For example:
https://yournextmp.com/person/6109
The text was updated successfully, but these errors were encountered: