2819 Fix insb and scb iquery pages parser #693
Merged
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.
This PR solves the issue described in freelawproject/courtlistener#2819 regarding the unparsed judge's name in SCB, as well as the issue detailed in freelawproject/courtlistener#2820 about the case name not being parsed in INSB.
Both issues were related to iquery pages for these two courts, which had different formats.
In the case of SCB, the judge's name was indeed parsed, but was added under the key
chief_judgeinstead ofassigned_to_strso it was not being recognized and assigned in Courtlistener. So I changed the key name toassigned_to_str.In INSB, the case name is within a
fonttag. So I added a new parsing method to properly handle this case.