Open mlissner opened 1 year ago
Before we choose option 1, we should at least see how the BCB1 did this. It'd be nice to add SCOTUS dockets to CL though.
The BCB1 supports SCOTUS, and I guess BCB2 should too, eh?
Shoot, I don't know about this, actually. I just read through pretty much all of the https://github.com/bdheath/Big-Cases/ code and didn't see any code references to SCOTUS. The one thing I saw was a handful of cases in the list that the bot was following, but I have no idea how those cases are followed. It could be that code was never checked in, if it ever worked.
Maybe Brad can chime in about whether this ever existed? It's something we could/should do, but it's less of a priority if BCB1 never did it. @bdheath, do you know/remember? The readme says BCB1 supports SCOTUS, but I can't find any code that actually does.
Hmm. See the last part of this comment:
https://github.com/bdheath/Big-Cases/pull/5#issuecomment-361735513
Nice find. The relevant part from @johnhawkinson (of course) reads:
Well, the code currently doesn't do anything with the SCOTUS cases after loading them into cases_sct, and I've never seen @Big_Cases tweet a SCOTUS case, and the SCOTUS RSS implementation (if we can call it that) is structured totally differently. So in part they're probably in a different dict because they don't work :)
Cool. I'm moving this from the post-launch milestone to the someday milestone. It's hard and nobody is missing it. But we should do it someday!
See https://github.com/freelawproject/foresight/issues/20 for the discussion of scraping SCOTUS that's a prerequisite to this.
The BCB1 supports SCOTUS, and I guess BCB2 should too, eh?
There are two ways to do this:
Number two is faster, number one is a better investment and architecture. Which will we choose?