Library Plan to Publish CRS Reports Falls Short of the Law, Is Unduly Expensive

Civil society, students, librarians, and the general public were elated when Congress decided to make the non-confidential non-partisan reports issued by the Congressional Research Service publicly available. These reports are often referred to as the gold standard for information concerning the issues before Congress.

We have obtained the Library of Congress’s implementation plan to make CRS reports available to the public, as required by 2018 Omnibus Appropriations Law. Unfortunately, it does not comport with the law or best practices for creating websites and is unusually expensive.

Today we release the Library’s May 22, 2018, CRS website implementation plan and civil society’s June 6, 2018 memo that responds to that plan. We hope that in doing so we will bring to the surface some of the problems with the CRS reports website’s proposed implementation so they can be fixed in time for the statutory deadline. (The Federation of American Scientists published on Friday a memo to congressional staff about the Library’s plans, but this is different from the implementation plan.)

The civil society response, co-authored by Daniel Schuman of Demand Progress, Kevin Kosar of the R Street Institute, and Josh Tauberer of, is based on our experiences of running, which is a website that publishes all current CRS reports online — more than 14,000 — including making appropriate redactions and additions to the reports prior to publication.

Our website cost under $20,000 to build and maintain with full functionality and fewer than 100 hours of programming time; the Library’s CRS website will cost $1.5 million, have limited functionality and suffer from significant design limitations, and not be completed for more than a year after the law was enacted and six months after the statutory deadline for completion.

Our nine page report makes the following recommendations:

With respect to compliance with the law:

  • The Library should update its implementation plan to publish all CRS reports — we believe there are many more than the 2,900 the Implementation Plan says will be published by Spring 2019 — by the statutory deadline of September 19 of this year. We request it aim for September 17th, which is Constitution Day. The Library’s implementation extends beyond April of next year.
  • The Library should update its implementation plan to include all CRS Reports, including insights, infographics, sidebars/legal sidebars, in focus, and testimony.
  • The Library should revisit its implementation plan to ensure that HTML versions of the reports are available to the public just as they are already available to Congressional staff.
  • The Library should review the code we published to see whether it would fit its purposes, in particular our automated author information redaction functionality, or whether it could develop code that would enable it to comply with the timeline.
  • The Library should review its implementation plan to include an index of CRS reports, in accordance with the law’s requirements.

With respect to the website design:

  • The Library should consult with the Government Publishing Office and the public on how best to implement bulk access.
  • The Library should develop a plan to respond to any initial heavy loads on the website.
  • The Library should implement a robust website search capability and develop a plan to do so.
  • The Library should create predictable URLs for CRS Reports and a landing page for a Report series, and set forth a plan to do so.
  • To keep down costs, the Library may wish to examine our approach to see whether it can review its own techniques or borrow some of our techniques to save money. Similarly, it may be worthwhile to engage an entity like the General Services Administration’s 18F to help keep down costs.

We have made several attempts to contact the Library on this and other technology issues, but have been unsuccessful in starting a conversation. We hope that we will be able to work with them on these issues.

Written by Daniel Schuman