Right now we have officers and incidents grouped by agency. However, it might be useful to have other groupings of officers and incidents not necessarily related to their agency, which we'll call Collections.
The idea here is that collections could be related to events or investigations we want to highlight.
The collection would have a name and a slug, e.g. such that we can send folks to:
Similarly we could have a collection within a department, e.g. CPD officers that had X training:
openoversight.com/collections/X-training
Privileges are not obvious here. I think it makes sense that an administrator should make the collection, but who should be able to edit incidents/officers within the collection? If it's a collection within a department, then the area coordinator should handle it. If it's a collection that consists of multiple departments, I'm not sure how best to handle. Perhaps for now, collections should be administrator only.
Right now we have officers and incidents grouped by agency. However, it might be useful to have other groupings of officers and incidents not necessarily related to their agency, which we'll call Collections.
The idea here is that collections could be related to events or investigations we want to highlight.
The collection would have a name and a slug, e.g. such that we can send folks to:
openoversight.com/collections/2020-unrest
which e.g. could contain incidents from recent unrest: https://github.com/2020PB/police-brutality.
Similarly we could have a collection within a department, e.g. CPD officers that had X training:
openoversight.com/collections/X-training
Privileges are not obvious here. I think it makes sense that an administrator should make the collection, but who should be able to edit incidents/officers within the collection? If it's a collection within a department, then the area coordinator should handle it. If it's a collection that consists of multiple departments, I'm not sure how best to handle. Perhaps for now, collections should be administrator only.