October 1, 2019

API:

  • Elasticsearch
    • We've switched the back end of the cases endpoint to Elasticsearch. We tried to maintain the same API interface and output that older Postgres back end had, but please let us know if anything is broken. This update will:
      • increase performance
      • pave the way for lots of new features and functionality
      • increase the length of cursor strings
      • invalidate old Postgres cursor strings
  • New IDs
    • We've started including some new IDs in our API's case output. Volumes now include a unique 'barcode' value which (usually) corresponds to the barcode in our library's cataloging system. Reporter entries now include the reporter ID. These values were previously only available as part of the URL value. Thanks to Mike Lissner for pointing this one out.

Data:

  • Nominative Reporters
    • We've cleaned up the nominative entries in our reporters table! This affects not only the reporters table but also corrects citations and volume metadata.

Website:

  • New Gallery Entries
    • We've been adding some new entries to our Gallery Page so head on over and check 'em out.

July 31, 2019

Website:

  • Improved case display at cite.case.law:
    • Cases include images for non-textual regions (figures and illustrations) (example)
    • Case text includes italics, where detected by OCR
    • Case text includes pin cites, i.e. page breaks that can be linked to (example)

API:

  • Removed from /cases/ endpoint:
    • In full case responses with JSON format, ["casebody"]["data"]["parties"] is no longer included. The ["name"] attribute provides the same information in a cleaner format.
    • Queries for CaseXML documents (/cases/<id>/?full_case=true&format=xml) will return only <casebody>, and not the entire CaseXML file. The outer wrapper had no useful information other than to estimate the location of page breaks, which are now precisely marked by <page-number> elements.

Data format:

  • Added to case HTML and XML:
    • <img> tags to show images for non-textual regions (figures and illustrations)
    • <em> tags to show italics detected by OCR
    • <page-number> (in xml) or <a class="page-number"> (in html) tags to mark page breaks
  • Removed from case XML:
    • The pgmap attribute was removed. It was confusing, because it referred to the page-side index in the physical volume rather than to the printed page label, and it did not allow for precise placement of page breaks within a paragraph. The replacement is to use <page-number> elements to infer the correct page number for each element.

June 19, 2019

Website:

API: