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
On an organizational/logic level, it is better to group by role/state/area rather than person, as the person can change but the position remains the same.
Potential idea: ability to filter based upon a specific office and read about the current & previous prosecutors. Can also help with identifying trends.
If you have any ideas, feel free to give this a shot.
The text was updated successfully, but these errors were encountered:
I'm looking at this issue, and I think I'm getting a little confused? The page already has this:
So I think what you want is to filter by AG in California for example? Or you want the filtering to happen inside a prosecutor's card? Because by region or state, I guess we could check one the current filter boxes, and then have a dropdown with state names for further filtering? Am I following your train of thought here?
@fedGL I wonder too. Maybe there's a case for re-structuring the data so that there's a one-to-many relationship where one role object has many prosecutors, with one flagged as current and using election date as the "default sort" on the rest of them? This may make continuity of a specific position a little more clear.
Resurrecting an old issue for Hacktoberfest 2020:
On an organizational/logic level, it is better to group by role/state/area rather than person, as the person can change but the position remains the same.
Potential idea: ability to filter based upon a specific office and read about the current & previous prosecutors. Can also help with identifying trends.
If you have any ideas, feel free to give this a shot.
The text was updated successfully, but these errors were encountered: