-
-
Notifications
You must be signed in to change notification settings - Fork 111
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
Disambiguate ohioctapp
docket numbers
#1135
Comments
Thanks for spinning this off into its own issue. That's a nasty one. I guess the solution is to include the county information in our Ohio look ups? Do we even have that in the docket? |
Currently we are not saving anything related to the county on the Docket, but the county listed in the HTML can be used to build a court name that would go in Independently from that, we could tweak the docket number as seen in the source, appending the district / circuit number and some letters from the county to make them unique. What do you think @flooie ? |
Tweaking docket numbers is probably not something we can do. People would be upset. Happy to hear @flooie's thoughts though. |
oh thats fun. |
I think we should call the court tomorrow to get clarification on whether these are full docket numbers or if they have an extended version we could decipher and use. I think speaking to a clerk would help understand how they do this in practice. |
Numbers are not unique to district court of appeals but unique to the district + county. So in theory you could have 14 22CA10's just from the fourth district. I use fourth because that is who I spoke to this morning. Also some courts and districts do different things. |
A possible solution:
If there are no repeated county names across districts, that would make the lookup unique |
their should be no repeated county names. |
Will help solve freelawproject#1135 - Now parsing lower_court for disambiguating docket numbers across ohioctapp dockets - Now parsing per_curiam - Now parsing parallel_citation for `ohio` - Updated example files - Refactored some xpaths
Will help solve freelawproject#1135 - Now parsing lower_court for disambiguating docket numbers across ohioctapp dockets - Now parsing per_curiam - Now parsing parallel_citation for `ohio` - Updated example files - Refactored some xpaths
Will help solve freelawproject#1135 - Now parsing lower_court for disambiguating docket numbers across ohioctapp dockets - Now parsing per_curiam - Now parsing parallel_citation for `ohio` - Updated example files - Refactored some xpaths
ohioctapp_{1 to 12}
opinions may share the same docket number across counties, even in the same circuit. Example 1, 2 . This has been causing incorrect docket matching, and there is no direct way to disambiguate with the current docket number. An example of many cases with a single docket number22CA15
From freelawproject/courtlistener#4256
The text was updated successfully, but these errors were encountered: