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

Don't set court='scotus' for South Carolina citations #84

Open
mattdahl opened this issue Jun 26, 2021 · 5 comments
Open

Don't set court='scotus' for South Carolina citations #84

mattdahl opened this issue Jun 26, 2021 · 5 comments

Comments

@mattdahl
Copy link
Contributor

Eyecite thinks that South Carolina citations are SCOTUS citations:

from eyecite import get_citations
text = 'Lee County School Dist. No. 1 v. Gardner,  263 F.Supp. 26 (SC 1967)'
cites = get_citations(text)
cites[0].metadata.court

# prints 'scotus'

The SC in the year could be ambiguous, but the F.Supp. reporter should automatically rule SCOTUS out as a possibility for the court here.

@mattdahl mattdahl changed the title Don't set court='scotus South Carolina cit Don't set court='scotus' for South Carolina citations Jun 26, 2021
@devlux76
Copy link

You will never see SC in the year field of a Supreme Court decision (if the person who wrote it is citing things properly).
The court is only included when the relevant court is unclear from the reporter cited.
The Supreme court will always be cited to the U.S. or the S.Ct. reporters unless it's a slip opininon, so there should never be any ambiguity.

Bluebook R. 10.4(b) State courts.

In general, indicate the state and court of decision. However, do not include the name of the court if the court of decision is the highest court of the state.
The Bluebook: A Uniform System of Citation R. 10.4(b), at 106 (Columbia L. Rev. Ass’n et al. eds., 21st ed. 2020).*

@mlissner
Copy link
Member

Thanks @devlux76. This looks like a great first bug. Any interest in trying to tackle it with a test and a fix?

@mlissner
Copy link
Member

That'd be a question for @jcushman, but I suspect he wouldn't know anymore. At this point, it's worth just running with the example he gave. I'd make a test using it, make sure the test fails, then write the code to fix it.

@mattdahl
Copy link
Contributor Author

The one I encountered it in was the Bowen case. Not sure if it got my version from Courtlistener or Lexis, but in the Courtlistener one you link you'll see it if you search 263 F. Supp. 26 (SC 1967). Thanks for working on this!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: General Backlog
Status: No status
Development

No branches or pull requests

3 participants