-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
Find short case names and linkify them #186
Comments
Here is a useful example.
from litowitz-v-litowitz
from litowitz-v-litowitz |
That's good. I think there are others that just say |
Related to #76 The solution seems clear to me now: we should enhance eyecite to search for Proposed Approach r {PLAINTIFF or DEFENDANT NAME} at \d+
This approach ensures we can accurately associate short citations with their corresponding full case citations. @mlissner what do you think. |
Hm, that's good, but what about when there's no page number? And are you envisioning a second pass with eyecite or that the first pass is able to accomplish all of this? Can you do some pseudocode of how it'd work? |
If I may, I suggest expanding We already support this list of short forms: Lines 472 to 484 in 5d3cf67
If we add regex for |
I envision something like this... if citations are returned
then we do a second pass in something like this
pass in the citations found and for each something like this
I dont know the citation token stuff that well so forgive me if this is bad pseudo code. @mattdahl I want to do it in one function call but we need to find plaintiff and defendant names first to find these short form citations. @mlissner can you clarify what you mean with ones without page numbers? like just straight up references ... like In XYZ - I think that should be done on CL or in some other function. |
@mattdahl - I think I wasn't clear in my response to you - I thought about using the |
Sorry Bill, can you go up a level for me and start with something like:
And end with the resolved short cases? I'm not so interested in the internal code. I'm thinking more about the API that a user would interact with. I think Matt is probably right that we can catch things like I'll also suggest that we can't always figure out the short case names correctly, so ideally this would be robust to that. For example in this case, the
And the So the spec is to find and figure out examples like:
|
If you have a full citation followed by a citation to simply "Roe", we should capture that second reference, and treat it like a supra reference.
There's some trickiness here, but we have some short case names in the DB, and others can be generated pretty well already. There's also spacey, which should be able to do entity extraction.
The text was updated successfully, but these errors were encountered: