@Monneyboi As I’ve been working through Poliloom for US politicians I’ve noticed there are two annoying behaviors.
-
When a statement is vague or hard to verify the accuracy skipping the response results in continuously having the unanswered statement presented over and over in the queue to the same user. It would be preferable to count the number of skips for a statement then not show that suggestion to the same user as they probably didn’t miss answering, but are unsure if it should be accepted or rejected. For instance Q111530119 is suggesting an island as the location matching “Long Island” for place of birth, but geographic features often have multiples of common names in an area so this is a hard question to answer without some GIS work to check if other “Long Island” locations exist or a more specific citation. Its not necessarily a reject, but more a hard to verify to accept.
-
For birth year extractions infrequently there have been inconsistencies within Wikipedia articles where the infobox has one date and the article body has a conflicting birth date and the citation is not clear on either. Importing both to Wikidata would be one approach, but maybe better would be to have a reject and add a template for citation needed or self contradiction for the statement in question. If not auto inserted this could be put in a queue to review the statement and fix the source or have the relevant template set to be added manually.
If either are on the roadmap, great. If not, these could be useful ways to improve the quality.

