Ask again for reviews of a flag
Opens the review of one of your own flags whose review expired with no votes (review_outcome expired) for another 14 days, and asks every other organization to review it again. Only the organization that filed it, and only an expired review: one the votes decided stays decided, and more evidence is a new flag. Needs write on Registry.
Authorizations
Response
The flag, its review open again.
The identifiers as a reader sees them. Only the keys the flag was filed with are present.
Nothing hashed comes back (Phase 422). A microchip number, an email address, a phone number, a date of birth and a street address are stored ONLY as hashes, and those hashes are not returned: a date of birth has about 36,500 plausible values, a phone number with its area code has ten million, and a hash handed to a reader is one offline pass away from being the value itself. What you get instead is the part that was always meant to be read - the birth YEAR, the town and state, the name, the animal’s description.
To match what you already hold, SEND IT: GET /api/registry/search takes microchip_number, email, phone, date_of_birth, address and name_alias as plain values, hashes them the same way the flag was hashed, and answers with the flags that match. That is the whole bargain this registry works to - confirm what you hold, and do not harvest what you do not.
Null while the review is open, and when the votes made the flag active. not_corroborated: the review closed with as many or more votes to dispute it or say there is not enough evidence as to corroborate it (a tie included). expired: it closed with no votes; the organization that filed it can ask again. Either way the flag stays pending_review, is not a finding, and is open to nobody's review.
not_corroborated, expired, null 
