So either the case is wrong (I haven't double checked) or reporters-db is wrong. Furthermore, it looks like we don't have the date-level granularity on the fields (it says Dec. 31 and Jan 1), so that'd be nice to fix.
Probably something we can do programmatically from the database, and that we might even be able to easily do for all keys in reporters DB?
I was just playing with the citation finder on CourtListener, and it failed to return a top result for this query:
https://www.courtlistener.com/?q=941%20F.2d%20309&type=o&order_by=score%20desc&stat_Published=on
That looks up 941 F.2d 309, and the reason that didn't find results is because the case is from 1991, while the key for F.2d says 1993:
So either the case is wrong (I haven't double checked) or reporters-db is wrong. Furthermore, it looks like we don't have the date-level granularity on the fields (it says Dec. 31 and Jan 1), so that'd be nice to fix.
Probably something we can do programmatically from the database, and that we might even be able to easily do for all keys in reporters DB?