-
-
Notifications
You must be signed in to change notification settings - Fork 150
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
Judge is not being assigned to RECAP dockets. #2819
Comments
Hm, I see this is In Review? |
Oh, no sorry, I think it was a mistake while checking my backlog. This should be in the backlog column. I'll be working on it. |
Ok, I've reviewed this and it seems that this is not related to a current parsing issue. I examined some of the reported dockets, and after purchasing the docket in PACER, it displayed the assigned judge correctly: https://www.courtlistener.com/docket/38228028/linda-l-swilley/ The problem seems to be that the original source of these dockets was the RSS feed that doesn't contain the Judge's name. Since this issue is not a bug on our end, it could be closed. |
So just to make sure I understand, the judge name is not going to appear in the bulk data for this district? |
That's correct. These dockets won't show the judge's name until they are updated with a version that contains the judge's name. For instance, the dockets that I added in a comment above now include the judge's name. They will be shown in the next bulk data update. Correct me if I'm wrong, @mlissner, but if we pull iQuery data as you mentioned in #2820, we could obtain all of these judges too, and clean up the docket number as well, right? Since iQuery pages contain the judge's name, correct? |
I just confirmed that the judge's name is available on |
Sounds like this is largely resolved going forward. The issue is that:
The fix for the existing data is to do a mass iquery download and merge, but unfortunately, we don't have plans to do that any time soon. We could do it as a paid engagement, but we have a lot of irons in the fire right now, so we can't prioritize an iquery download just to fix this one jurisdiction. If this is something you'd like to discuss, @arharvard, let's get that conversation going via email. It shouldn't take a ton of work, but it may take some customization and monitoring. Sorry we don't have more resources to do more on this right now. We're really swamped, so we have to be a bit strategic in how we use our time. Happy to chat though. @albertisfu, do you see anything more to do on this issue, or do you think we can close it? |
Thanks you for the help and information. |
Interesting. Looks like it affects a number of bankruptcy courts. That's good, in that it isn't just a one-off, but too bad, since the impact is greater than we realized. I agree that it'd be really nice to do a big crawl to bring in this data, but we still don't have the resources to do so, unfortunately. (Affecting more cases is a double-edged sword—it means the problem is a bigger priority, but it also means it will be more work to do so.) Are you sure that's the exhaustive list, in case we do find time to look at this? |
Okay, thanks for letting me know. These are the districts with the biggest issue, the rest have judge assigned to at least 85% of cases. |
No, that's OK. I think having this list will be enough if/when we choose to return to this, but realistically it'll probably be a while until this happens. It's not something we do on a regular basis, unfortunately. |
While investigating #2817, we discovered that some of the RECAP dockets provided in the sample do not have an assigned judge. However, looking at these dockets in PACER, the judge's information is available.
It appears that we're parsing the judge information for district and bankruptcy dockets, but for some reason, it is not being saved in the docket.
An example:
https://www.courtlistener.com/docket/38228028/linda-l-swilley/
https://ecf.ilsb.uscourts.gov/cgi-bin/DktRpt.pl?260496784257687-L_1_0-1
The text was updated successfully, but these errors were encountered: