-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
QA for protest-related documents #5055
Labels
Comments
InaraFernandez
added
Department: Police Oversight
Office of Police Oversight content and services
Team: Dev
labels
Oct 20, 2020
Yeah, I can definitely search the summaries and make sure all the documents with terms in your list make it on the correct collection. Assign this to me when you're ready! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
The issue:
We now have a specific document collection for all formal complaints relating to the 2020 protests. These formal complaints should belong to three different document collections:
As we are unbatching the batched protest documents for the month of June, we are manually assigning them to the correct collections. The issue is with one-off non-batched protest complaints that have been trickling in since June. For these, I was writing in the "note" section of each document page the word "protest" as a tag so that they could be sorted into the protest-related doc collection. Since several people have been working on these since June, I don't think every protest complaint is appropriately tagged.
I'd like to set up a QA process to search for protest-related terms within the summaries of each document page in order to catch and assign any rogue complaints. Would this be possible to do if I were to give you a list of terms to search for?
Terms include:
Another ask is to be able preview all of the complaints matching the search before pushing to production just in case there are a couple of complaints that shouldn't be there.
cc: @toribr
The text was updated successfully, but these errors were encountered: