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

Juridiction field missing for bankrupcty and federal courts #78

Open
warrenronsiek opened this issue Oct 4, 2023 · 1 comment
Open

Comments

@warrenronsiek
Copy link

Many bankruptcy courts are missing the jurisdiction completely. I'm not sure what the right call is here. They aren't normal courts, so does a e.g. California bankruptcy court have "jurisdiction" in the same sense that a regular court does? Maybe not. However, it is located in California, and its rulings are still binding. I can see it go either way, and I'd like to populate those fields with something.

Similarly, federal courts are missing a jurisdiction field. I'd like them to be something like "FED".

As it stands, if you look at the jurisdiction field, federal courts get lumped into the NULL bucket along with e.g. state-level bankruptcy. That doesn't seem right.

Proposal:

  • State bankruptcy courts get the same jurisdiction as the state they are in.
  • All federal courts get the jurisdiction "FED" so as to disambiguate.

I'm happy to do the work if there is agreement on this point.

@mlissner
Copy link
Member

mlissner commented Oct 4, 2023

Funny timing, we've been working on this recently, but in a different way, by putting similar sorts of data into CourtListener.

I think for federal data, the jurisdiction field should probably say which states make sense. It should be an array of strings, so if you have the bankruptcy court of eastern CA, the jurisdiction is CA. If you have the bankruptcy appellate panel for the ninth circuit, the jurisdiction is [CA, NV, HI, WA, OR...].

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

No branches or pull requests

2 participants