Free Law Project Joins Request for Access to Offline PACER Documents

A recent announcement on the federal PACER website indicated that PACER documents from five courts prior to certain dates (pre-2010 for two courts, pre-2012 for one court, etc.) would no longer be available on PACER. The announcement was reported widely by news organizations, including the Washington Post and Ars Technica. The announcement has now been changed to explain, “As a result of these architectural changes, the locally developed legacy case management systems in the five courts listed below are now incompatible with PACER; therefore, the judiciary is no longer able to provide electronic access to the closed cases on those systems.” See a screenshot of the earlier announcement without this explanation:

Original PACER announcement

Original PACER announcement

This morning, Free Law Project signed on to five letters from the non-profit, Public.Resource.Org, headed by Carl Malamud, asking the Chief Judge of each of these five courts to provide us with access to these newly offline documents. The letter proposes that we be provided access in order to conduct privacy research, particularly with respect to the presence of social security numbers in court records, as Public.Resource.Org has done previously in several contexts. In addition we offer to host all the documents in a free public archive, at the Internet Archive, as we do now with RECAP documents. Free Law Project would also plan, ultimately, to incorporate the documents into our CourtListener platform, for even easier full-text searching and public accessibility.

The National Law Journal collected various tweets from lawyers and academics upset over the PACER announcement, and the general reaction to the surprise decision has been dismay, as many of these practitioners and professors rely on these documents for their work. We hope the Chief Judges we have reached out to today will agree to our request and allow us to get these documents back online for the public as soon as possible.

13 Responses to Free Law Project Joins Request for Access to Offline PACER Documents

  1. David Swink says:

    In 2006-2009, I worked as a contractor for the US District Court in DC — one of 94 Courts in the US and its territories. The Court had been manually posting copies of post-able opinions and indexing them on its web server — a time-consuming process. PACER was deemed not acceptable at the time.

    As for the AO, they would never listen to our complaints or suggestions, so the Courts had to take it upon themselves to develop anything new.

    After familiarizing myself with CM/ECF, I wrote a Perl/CGI script that gave access automatically to all opinions the judge had designated as ‘public’, creating the index page ‘on demand’ by year. I see that Court has gone back and made ‘public’ opinion going back to 2005. Example: https://ecf.dcd.uscourts.gov/cgi-bin/Opinions.pl?2006 . Via internal internet, I made the code available to all the courts, and currently a number District and Bankruptcy Courts have utilized this script. (And btw, a Google search will find the opinions linked on these dynamically-created index page.)

    So the problem has long been resolved. It’s just that the AO won’t act to promote and distribute proven production code.

  2. […] is nominated for higher office? Unless PACER officials make some accommodation, such as the one we asked for yesterday, researchers and the public will face the daunting task of requesting these materials individually, […]

  3. […] PACER mess, several organizations, including the Free Law Project and Public.Resource.Org, have sent letters to the Chief Judge of each affected court, requesting the removed records so they can make them […]

  4. […] PACER mess, several organizations, including the Free Law Project and Public.Resource.Org, have sent letters to the Chief Judge of each affected court, requesting the removed records so they can make them […]

  5. […] PACER mess, several organizations, including the Free Law Project and Public.Resource.Org, have sent letters to the Chief Judge of each affected court, requesting the removed records so they can make them […]

  6. […] PACER mess, several organizations, including the Free Law Project and Public.Resource.Org, have sent letters to the Chief Judge of each affected court, requesting the removed records so they can make them […]

  7. […] PACER mess, several organizations, including the Free Law Project and Public.Resource.Org, have sent letters to the Chief Judge of each affected court, requesting the removed records so they can make them […]

  8. […] PACER mess, several organizations, including the Free Law Project and Public.Resource.Org, have sent letters to the Chief Judge of each affected court, requesting the removed records so they can make them […]

  9. […] this is exactly what Public.Resource.Org and Free Law Project, using its CourtListener platform, suggested should happen in its August 27 letters to the affected courts. And perhaps such a move could set a […]

  10. […] this is exactly what Public.Resource.Org and Free Law Project, using its CourtListener platform, suggested should happen in its August 27 letters to the affected courts. And perhaps such a move could set a […]

  11. […] this is exactly what Public.Resource.Org and Free Law Project, using its CourtListener platform, suggested should happen in its August 27 letters to the affected courts. And perhaps such a move could set a […]

  12. […] this is exactly what Public.Resource.Org and Free Law Project, using its CourtListener platform, suggested should happen in its August 27 letters to the affected courts. And perhaps such a move could set a […]

  13. […] this is exactly what Public.Resource.Org and Free Law Project, using its CourtListener platform, suggested should happen in its August 27 letters to the affected courts. And perhaps such a move could set a […]

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>