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

Incorrect Reporter in Citation Data from Harvard import #4930

Open
flooie opened this issue Jan 15, 2025 · 1 comment
Open

Incorrect Reporter in Citation Data from Harvard import #4930

flooie opened this issue Jan 15, 2025 · 1 comment
Assignees

Comments

@flooie
Copy link
Contributor

flooie commented Jan 15, 2025

While answering a question for a client, I discovered an error in the citation data for at least one volume imported from Harvard’s dataset.

The issue involves an incorrect reporter being assigned to citations. For example, in the following case:

CL Campbell v. Blodgett
• The citation provided is: 978 F.3d 1502
• The correct citation should be: 978 F.2d 1502.

Upon reviewing the Harvard JSON data, it’s clear how this mistake occurred. The citation is incorrectly listed as F.3d, while the reporter associated with the volume is identified as the Federal Reporter 2d Series (F.2d). Here’s the relevant snippet from the JSON:

IA JSON:
Source JSON File

"citations": [
  {
    "type": "official",
    "cite": "978 F.3d 1502"
  }
],
"volume": {
  "url": "https://api.case.law/v1/volumes/32044057701377/",
  "volume_number": "978"
},
"reporter": {
  "url": "https://api.case.law/v1/reporters/980/",
  "full_name": "Federal Reporter 2d Series"
}

The citation here is mismatched:
• The volume and reporter belong to the Federal Reporter 2d Series (F.2d).
• The citation incorrectly references the Federal Reporter 3d Series (F.3d).

We already have this opinion in our database from a different source, with the citations correctly identified.

Research is needed to see how common this might be.

@flooie flooie moved this to January 27 to Feb 7 in Case Law Sprint Jan 15, 2025
@mlissner
Copy link
Member

Great details. Great explanation. Great triage for sprint. Lovely ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: January 27 to Feb 7
Development

No branches or pull requests

3 participants