Issue 242 - Fix court detection when parenthetical includes date #243
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As described in #242, there is currently a problem in detecting the court in a full citation when the parenthetical includes the specific date on which the opinion was issued, e.g.,
(C.D. Cal. Feb. 9, 2015).The problem is that we currently treat everything before the year as a potential court string, so
C.D. Cal. Feb. 9in the example above. This causes the court lookup inhelpers.get_court_by_paren()to fail.This PR fixes this by modifying the
POST_FULL_CITATION_REGEXregex to include capturing groups for potential months and days. If these are present, we capture them so the<court>group remains pristine (i.e., onlyC.D. Cal.). If they are not present, the behavior should be the same as it currently is.