freelawproject
feat(pa): dynamic backscraper and update to new source
Implemented a new scraper targeting the API instead of the RSS feed. Since we needed to backscrape, that way we can target custom dates Also, updated the example files
Helps solve #967
This is indeed an enhancement we've been tracking for months. The OpinionCluster model has a one-to-many relation to the Opinion model, so it is what we should be doing. However, we would need to change both Juriscraper's OpinionSite(Linear) and cl_scrape_opinions for it to work. I bundled this and other changes into a proposed new scraper/site class some time ago, but is still pending of review. You can check it some more here https://github.com/freelawproject/juriscraper/issues/883#issuecomment-1981884866
@grossir can we figure out the conflicts here and does this need the enhanced v3 juriscraper?
To actually return and use OpinionClusters, we will indeed need a different approach both in juriscraper and courtlistener, and that's not ready yet
It seems there were no conflicts, I just merged main
@flooie I updated the PR with the suggested changes; also added support for getting "per_curiam"