Closed brianwc closed 1 year ago
Interesting. I just reuploaded this and it fixed it. Do you know how it was uploaded the first time? I wonder if this is an error in our RSS parser, perhaps?
Possibly another example here: https://www.courtlistener.com/docket/6486693/singleton-v-amita-health/#entry-136
Hm, I just wrote a test for RSS feeds, and that doesn't seem to be it. Looking at this more closely I see that most of its content is free opinions, so that could be the issue. I'll take a look there!
Well, I looked at the code that parses free opinion reports and it's fine too. So:
This docket was populated first by RSS and the opinion scraper, then later by me running the docket report.
I can't find the issue in either the opinion scraper or the RSS feeds
I also tried to find this problem by searching in RECAP, but nothing came up that way either.
So...I can't reproduce this and the code looks OK. Is it possible this was a data error that the court corrected?
I haven't seen this again in the last four years. Closing, but if it comes up again, please feel free to re-open or re-file.
It appears that the case name parser cannot manage ampersands from this result:
https://www.courtlistener.com/docket/4383223/house-of-bryant-publications-llc-v-a/
which should list the defendant as "A&E Television Networks"