Open beidelson opened 3 months ago
Shoot, that's not great. It's entirely possible that this is a parser error while ingesting the data.
It looks like we've got about 200 judges in D.D.C: https://www.courtlistener.com/?type=p&q=&type=p&order_by=score%20desc&court=dcd
And 12 in D.C. Circuit: https://www.courtlistener.com/?q=&type=p&order_by=score%20desc&court=cadc
I guess the easiest thing to do would be to pull up all of the DC Circuit court judges from another list (or maybe the FJC judge database), and then go through each and fix if needed. Might not be too hard.
Hi, it looks like many (perhaps most) judges on the D.C. Circuit are misclassified in the
positions
data as judges of the D.C. district court (D.D.C.) instead. Is this a known issue? I haven't investigated it systematically at all but I wonder if there was a parsing problem whenever you ingested this data—maybe related to the "District of Columbia" figuring in both names and/or the courts' jurisdictions being coextensive. I haven't checked if similar issues arise anywhere else.Here are a few examples chosen at random: https://www.courtlistener.com/api/rest/v3/positions/?person=1155 (Merrick Garland) https://www.courtlistener.com/api/rest/v3/positions/?person=3065 (Sri Srinivasan) https://www.courtlistener.com/api/rest/v3/positions/?person=2263 (Patricia Millett)
Thanks!