-
Notifications
You must be signed in to change notification settings - Fork 37
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
PA courts scraper #239
Comments
@josh-chamberlain I talked with Max Chis and I'm interested in working through this issue. I'll message you on discord asking for the endpoint. |
@michaeldepace thanks! I shared details via DM, but putting here too: For starters, we would want to do a scraper in the scrapers repository, which writes to CSV or JSON or SQLite or something depending on what’s convenient for you. Once it works locally and seems to do what it needs to, we can worry about scale and stuff. For this case I’m not sure how often we need it to run. This is a complicated one—let me know if you want to chat or need anything! |
We got some info from a person who used a different endpoint previously to create a database with these tables:
Here's some edited explanation:
example docket table and cases table
corresponding raw JSON
|
Given the nested nature of the data and flexible nature of our questions + purposes, what if we just put the JSON, mostly unaltered, into a place where elasticsearch could get at it? We could even use elastic cloud to test it out, rather than hosting our own. |
Context
existing case search: https://ujsportal.pacourts.us/CaseSearch
endpoint:
only sharing with engaged volunteers
Initial work required
start date
andn
number of cases to getn
cases by docket number (reasonable timeout)n
cases?" (Y/n)next milestone
Risks
How to start
Related questions
All of these concern Allegheny County; we believe all of them can only be answered with the aid of court docket analysis.
The text was updated successfully, but these errors were encountered: