Skip to content
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

Open
jcushman opened this issue May 25, 2021 · 5 comments
Open

Handle statutory short cites #77

jcushman opened this issue May 25, 2021 · 5 comments

Comments

@jcushman
Copy link
Contributor

Here's an example of statutory short cites:

Business activities of national banks are controlled by the National Bank Act (NBA or Act), 12 U. S. C. § 1 et seq., and regulations promulgated thereunder by the Office of the Comptroller of the Currency (OCC). See §§24, 93a, 371(a). As the agency charged by Congress with supervision of the NBA, OCC oversees the operations of national banks and their interactions with customers. See NationsBank of N. C., N. A. v. Variable Annuity Life Ins. Co., 513 U. S. 251, 254, 256 (1995). The agency exercises visitorial powers, including the authority to audit the bank’s books and records, largely to the exclusion of other governmental entities, state or federal. See § 484(a); 12 CFR § 7.4000 (2006).

The NBA specifically authorizes federally chartered banks to engage in real estate lending. 12 U. S. C. § 371. It also provides that banks shall have power “[t]o exercise ... all such incidental powers as shall be necessary to carry on the business of banking.” §24 Seventh. Among incidental powers, national banks may conduct certain activities through “operating subsidiaries,” discrete entities authorized to engage solely in activities the bank itself could undertake, and subject to the same terms and conditions as those applicable to the bank. See § 24a(g)(3)(A); 12 CFR § 5.34(e) (2006).

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.

@munyanjacob
Copy link

I believe this would also apply here:

34 Stat.1246'; U.S.C., § 682, Title 18, and § 345, Title 28; Acts January 31, 1928,

If the first U.S.C., § <section>, Title <title> format was recognized, adding what preceded the § in the full citation to subsequent short citations that begin with § would allow them to be recognized too (assuming that the short cites end in a format the regexes can match).

If the format of the short cite is different, such as something like U.S.C., § 682, Title 18, ... See § 459., then it could still be missed (the new citation U.S.C., § 459 wouldn't have a title). Perhaps trying to match with the full citation's beginning first, then a variation (e.g. 18 U.S.C. instead of just U.S.C.,) would match these? Or maybe saving the most recent reporter and title for when short cites are found?

@devlux76
Copy link

devlux76 commented Dec 21, 2021

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.

@mlissner
Copy link
Member

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.

@devlux76
Copy link

devlux76 commented Dec 21, 2021

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.

@mlissner
Copy link
Member

Noooo worries!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants