more complaint data granularity

[rebeccawilliams]

If the following are captured w/ IA Pro it would be great to display it on this site and allowable by local law:

• officer name (consider unique IDs with common names) eg https://cpdb.co/data/bk42RA/citizens-police-data-project
• relationships between officers working together & complaints eg https://cpdb.co/data/bk42RA/citizens-police-data-project
• capture an anonymous complaint ID to capture community member that complain frequently; this might require harmonizing many complaint interfaces, eg in Baltimore there are 4 ways to complain: 311/911, walk-ins, civilian complaint review board, through PD IA
• complaint narrative information (w all PII redacted of course), eg http://www.consumerfinance.gov/data-research/consumer-complaints/

if they aren't captured by IA Pro, they should be included in updated contract requirements or cities should consider RFPS for alternative software.

[tmaybe]

Hi @rebeccawilliams thank you for the suggestions. We're definitely keeping additional data and relationships like this in mind.

One question: when you say "relationships between officers working together and complaints", do you mean "co-accused officers", as shown on the cpdb site?

[rebeccawilliams]

Thanks @tmaybe, yes that's what I was thinking of and from that example.

Other related items that would be interesting would be:

• what departments or forces an officer has been a part of - this would help show both internally and externally if an officer with a substantial complaint history was reassigned (potentially triggering earlier intervention if new complaints arise) and give context to why an officer may have a higher complaint count (field v desk work)