Skip to content
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

Previously, we went by the jurisction of the containing CIPRS record … #471

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

georgehelman
Copy link
Contributor

…when determining the jurisdiction of the offenses. However, it is possible for a CIPRS record to contain both district and superior court offenses in cases where the offense has a superseding indictment. We should always go by which section the offense is in (District Court Offense Information vs Superior Court Offense Information) when determining the offense's jurisdiction.

@georgehelman georgehelman force-pushed the correct_petition_district_allocation branch 2 times, most recently from 979c95b to 06d5a5c Compare March 23, 2024 22:39
…ns because the filter condition was using the jurisdiction fo the CIPRS record rather than the jurisdiction of the record. I suspect this is an artifact of the time when we thought a CIPRS record had only one jurisdiction. We now know that it is possible for a CIPRS record to have both in the case of superseding indictments. The convictions petitions should go by the jurisdiction of the offense, rather than the CIPRS record
@georgehelman georgehelman force-pushed the correct_petition_district_allocation branch from 06d5a5c to 870427e Compare March 23, 2024 22:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant