-
Notifications
You must be signed in to change notification settings - Fork 4
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
No uploads for 5th Circuit since 2017? #299
Comments
Unfortunately, we don't support appellate courts yet. That's the heart of the issue. This is a dup of: #83. It's in our backlog, but we haven't been able to get to it, unfortunately. Closing as a dup, but thank you for filing. |
Is that new? It's listed here: ... and this page: says "The archive also includes every free PACER opinion." Can the docs for the extension (i.e. in the Google store, for non-techies that have no idea what GitHub is) and at free.law be updated so that is more clear? Also, it wouldn't hurt to have that information listed on the error page received (since the appellate court is listed right in the url): P.S. Thanks for all of your hard work on this project - it is an amazing public service! |
Edit: Ahh, 'new' as of late 2017. That explains why some appellate data exists. |
Website FAQ updated via pull request: freelawproject/free.law#67 |
I've noticed that RECAP (Edge, Chrome, nor Firefox) has not been uploading dockets or case documents that I have purchased from the US Court of Appeals for the Fifth Circuit.
This issue is especially notable for 5th circuit docket 21-50949, United States v. Texas, as it is in the popular news right now:
All searches of the main CourtListener site to find that docket have failed.
Because there's nothing recent in the archive, I'm assuming there's nothing wrong with my specific configuration.
Is this a problem with:
If there is a hole in RECAP collection is more than a temporary (few days?) outage, we should probably add that to the docs somewhere, right?
(cross-posted to freelawproject/courtlistener#1786, since I'm not 100% sure this belongs here)
The text was updated successfully, but these errors were encountered: