Open derrickmehaffy opened 7 years ago
I thought about doing this in a slightly different way.
One idea we already have had is to make entries in the API DB crowd-sourced anyways. This would introduce a global reporting / verification function for any entry in the database (systems, bodies, obelisks, ruins, etc.).
This way we don't have to track a manually entered boolean flag (verified, reported as wrong), but we would have a track record of every single operation (marked as verified, marked as wrong), with detailed information on when this was done by whom (at least with the anonymous OAuth Id).
This would also offer us more reporting possibilities:
Entries with no additional verifications could be shown a "To verify" list. Entries that are marked as 'false info' could then be highlighted with a "needs additional verification" flag on that list. Entries with 3 verifications and no report for false info would automatically be listed in the normal API answers.
Would like to request an option under the admin view to mark an obelisk are Confirmed -not- to work, as we currently have the verified tag (meaning at least 3 people have checked it) but would also like to have one where we can mark as confirming it does not work, should be a simple database addition to add a "BIT" column.