You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Alphabetize the metadata categories (Legal case can/should be at bottom just before “related cases”)
On database filters page, display text for date filters is messed up: “took place between after” and “took place between before” (Switch to “took place after” and “took place before”)
Remove parenthetical “incl. legal case” from “leak prosecution” and “prior restraint”
Assault metadata
rename entry line from "physical assault" to just "assault"
Border Stop metadata
Remove: (will result in deleting this data from the database)
Stopped at border?
Did authorities ask for social media username?
Did authorities ask for social media password?
Were devices searched or seized?
Chilling Statement metadata (to be newly created) - [ ] Add 'actor': (politician / public figure) [no recording of name] - [ ] Add 'source of statement': (investigation / legal action / legislation / public statement / social media) Removed 2023-10-31 by @chigby for not being part of relevant Google doc
Rephrase existing language from 'Politicians or public officials involved' to 'Government agency or public official involved'
Equipment Damage metadata
Rename “Equipment Broken” to “Equipment Damaged”
Add actor (with the same general options that we use for assaults) above equipment entry (this should mirror equipment search/seizure)
Rename button from “add equipment broken” to just “add equipment” with matching display text
Equipment Search or Seizure metadata
Merge “Equipment Seizure or Damage” into the existing “Equipment Searched or Seized" menu
Rename button from “add equipment search or seized” to just “add equipment”
Remove 'Actor" as only actor viable for counting under the category is law enforcement
Prior Restraint metadata - [ ] Add date entry fields for date ordered and date lifted - If possible, we would love for this to essentially be used to field a "length of restraint" display metadata / potentially make "length of restraint" searchable. Date itself does not need to be added to filter. Moved to #1784
Add "Mistakenly released materials?" checkbox
Subpoena/Legal Order metadata For "subpoena of journalism" entry field
Rename as “Subpoena/legal order targeting journalist”
Akin to the arrest category changes: will have a "add legal order" button
From there, a “Select legal order type” [select one]: (motion to compel / subpoena / warrant / other)
Then, "Select information requested" : “communications or work product / testimony about confidential source / other testimony”
Status selection w/ date and button for adding additional statuses
For “Legal order for journalist’s records” entry field
Rename as "Subpoena/legal order to third party"
The text was updated successfully, but these errors were encountered:
In the vein of #1018, the Tracker team has reviewed the other categories as well and is requesting these updates (detailed in full here with draft mock-ups)
General asks:
Assault metadata
Border Stop metadata
Remove: (will result in deleting this data from the database)
Chilling Statement metadata (to be newly created)- [ ] Add 'actor': (politician / public figure) [no recording of name]- [ ] Add 'source of statement': (investigation / legal action / legislation / public statement / social media)Removed 2023-10-31 by @chigby for not being part of relevant Google doc
Denial of Access metadata
type_of_denial
under Denial of Access category #1781Equipment Damage metadata
Equipment Search or Seizure metadata
Prior Restraint metadata
- [ ] Add date entry fields for date ordered and date lifted- If possible, we would love for this to essentially be used to field a "length of restraint" display metadata / potentially make "length of restraint" searchable. Date itself does not need to be added to filter.Moved to #1784Subpoena/Legal Order metadata
For "subpoena of journalism" entry field
For “Legal order for journalist’s records” entry field
The text was updated successfully, but these errors were encountered: