-
-
Notifications
You must be signed in to change notification settings - Fork 32
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
Discuss test data sets #87
Comments
(Just splitting this off here, so we can keep the other issue narrow.) @step21, if you're just looking for some simple datasets to play with you could use the API at https://api.case.law or you can use the API at https://www.courtlistener.com/api/. The other thing is, if you are just experimenting for the sake of the JOSS review, you could just copy/paste some legal text and throw eyecite at it. For example, you could grab some text from here a recent SCOTUS opinion: https://www.supremecourt.gov/opinions/slipopinion/20 Does that help? |
Here's an example of extracting cites from all of the case.law cases for New Mexico, if it helps to have a larger dataset to play with:
|
Thanks! It's doing things, so that's a good start. It was mostly for the review and I am mostly satisfied, but just to be sure I ran this anyway, and it got a key error. As this key is not in your code, it must be sth else...?
|
Looks like models.py at line around 201 needs some guard code to ensure the "reporter" key is present. Something along the lines of
I'd have to look closer at what's calling that section of code to see what assumptions that breaks though. |
Yeah, seems like a good one to fix. Worth yanking into its own issue though, if you don't mind. |
Also, apart from running the included tests, do you have a test dataset you can recommend?
Originally posted by @step21 in #86 (comment)
The text was updated successfully, but these errors were encountered: