-
-
Notifications
You must be signed in to change notification settings - Fork 34
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
Statutory and regulatory citations from the Indigo Book #48
Comments
We've now added T1. Federal Judicial and Legislative Materials in #56, and T3. U.S. States and Other Jurisdictions in #51. What's missing still is T2. Federal Administrative and Executive Materials. There's a lot of interesting stuff in there, but with so many edge cases I'm not yet picking it up for the moment. For example:
A lot of that is obviously important like C.F.R. and Fed. Reg. In addition to T2, there are some other sections that still look valuable to mine for sources, with their own edge cases:
|
I would be happy to take a stab at adding treaties (T6). Are people ok with them going in laws.json? |
PR #121 adds treaties. I am planning to do arbitral reporters and state constitutions next. |
Related to #13 about adding law review abbreviations, what do you think of adding all of the non-case citation formats (statutes and regulations) from the Indigo Book's tables? (Or from another source if there's something easier to extract data from than that, though it doesn't look too bad.)
With the new
regexes
field and with eyecite where it is, I think there's some low hanging fruit at this point to expand what we're extracting. We could get fancy, but it could be as easy as adding some new"cite_type": "statute|law_review|..."
values to reporters.json, dropping in regexes extracted from Indigo Book, and having eyecite inspectcite_type
to emitStatuteCitation
orRegulationCitation
orLawReviewCitation
instead ofFullCaseCitation
."reporters-db" starts to become a little inaccurate at this point, but not sure if that's really an issue ...
The text was updated successfully, but these errors were encountered: