-
-
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
Handle statutory short cites #77
Comments
I believe this would also apply here:
If the first If the format of the short cite is different, such as something like |
Correct citation for U.S.C. is < title > U.S.C. § < section > according to the 21st Edition of the BlueBook @ R 12, but yeah there are some crazy citation forms out there. |
Yes, I think we're all comfy around here with the fact that cites U.S.C. mean different things on different days of the week (practically), but we'd still like to be able to find them in a block of text. The challenge of linking them to the correct place is real, but not one that eyecite tries to do. That's up to the library that's calling eyecite. |
Good point! I deleted my previous comment. 2 years of Law School being so competitive has done a number on my netiquette and I need to remember to slow down and breathe before responding. I can see clearly now that I somehow misread what was being said. Sorry if I've been coming off condescending. That's not my goal. You guys have done a great job and I'm here to contribute code to a project I believe in. |
Noooo worries! |
Here's an example of statutory short cites:
When we see just "§ " we should potentially fill in the part before § with the previous cite containing §, so "§§ 24" becomes "12 U. S. C §§ 24".
This is interesting because it's not a short cite for clustering purposes ... we want to fill in what is probably the completion of the citation, but not treat them like citations to the same document.
The text was updated successfully, but these errors were encountered: