August 28 2020
API:
- Cases Endpoint:
- Allow
ordering
by analysis fields.
- Allow
August 2020
API:
- Cases Endpoint:
- Added
last_updated
field and filters to get cases changed since date. - Added
analysis
field and filters to list extracted facts about case, such as word count. - Added
frontend_pdf_url
field. - Added
?format=pdf
query parameter for single-case endpoint.
- Added
- Volumes Endpoint:
- Added
frontend_url
field.
- Added
- Reporters Endpoint:
- Added
frontend_url
field.
- Added
Website:
- Non-API URLs such as Downloads now accept
Authorization: Token
header.
June 2020
Website:
- Moved bulk data releases from an API endpoint to the /download/ section.
Data:
- Removed a number of duplicate volumes (see bug #1322).
- Corrected a number of citations containing strange characters (see bug #960).
- 20200604 bulk data release including citation fixed, duplicate volume fixes, and cites_to field.
April 2020
Website:
- Linked citations in cases to cited case.
API:
- Cases Endpoint:
- Added
cites_to
field to list cases cited. - Added
cites_to
filter to find cases citing to a case.
- Added
Data:
- Added
/download/citation_graph/
folder.
March 2020
API:
- Cases Endpoint:
- Raise max results per request to 10,000.
Data:
- Merged duplicate New York reporters (see bug #1420).
February 2020
Website:
- Added /download/ section to download files.
- Added opt-in ability for user to track their previously-viewed cases.
- Cases now link to per-case PDFs.
Data:
- Added to Downloads section:
scdb/
folder with SCDB to CAP matchups.PDFs/
folder with full volume scans.illustrations/
folder with extracted figures and illustrations from cases.
API:
- Cases Endpoint:
- Removed the
format=html
andformat=xml
parameters, which previously caused the case detail endpoint to return either HTML or XML instead of JSON. API will always return JSON, with case body format still controllable viabody_format
. Requests forformat=html
will redirect to the frontend case browser, which shows identical contents to whatformat=html
used to return.
- Removed the
- Volumes Endpoint:
- Added pdf_url field to volumes endpoint.
- User History Endpoint:
- Added opt-in ability for user to retrieve their previously-viewed cases via API.
January 24, 2020
API:
- Cases Endpoint
- Default sort for full-text search is now relevance, rather than decision date.
- Search
- Default sort for full-text search is now relevance, rather than decision date.
- Added Sorting field to case endpoint searches. You can now sort by decision date, and relevance.
January 19, 2020
Security:
- Added a dmarc record for the case.law domain. Thanks to Kashif Shoukat for the suggestion!
January 16, 2020
Data:
- 99% of US Supreme Court cases have been matched to SCDB, and now have SCDB citations like "SCDB 1970-131" as well as parallel citations drawn from SCDB. Add a new "vendor" category of citations, used for citations to other vendors' databases.
- Include
<img>
tags in case XML output, identical to existing<img>
tags in HTML output.
Website:
- Case HTML pages now include a link to the case in the API.
January 9, 2020
API
-
Cases Endpoint
- Reverted to using a
decision_date
format that reflects the granularity of the original data. In the original data, some of the decision dates specify only a year and month, but not a day. To make these findable in a standardized date index, we set those to the first of the month. When we switched over to elasticsearch, we served the full date with the possibly inaccurate first-of-the-month date field indecision_date.
We've reverted to using the original date without the day. - New
preview
field. If you use the full-text search feature, you'll now get an array of matches in-context. The actual word or phrase match is surrounded in html emphasis tags. For example, if you performed a full-text search for the wordjudge
, the preview field in one of your hits would look like this:
[ "DEWEY, District Judge.", "Judge Reeves of Kansas City, Mo., in 1938, in a bankruptcy proceeding entitled “In the Matter of Irving" ]
- Reverted to using a
Website:
- Search Documentation
- Added search section documenting new features in our Elasticsearch-backed cases endpoint:
- Phrase Searching
- Search Exclusion
- Added search section documenting new features in our Elasticsearch-backed cases endpoint:
December 6, 2019
Website:
- API Documentation
- Added search section documenting new features in our Elasticsearch-backed cases endpoint:
- Phrase Searching
- Search Exclusion
- Sorting
- Added search section documenting new features in our Elasticsearch-backed cases endpoint:
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
- 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:
- 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:
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.
- In full case responses with JSON format,
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.
- The
June 19, 2019
Website:
- Started recording this public changelog.
- Added the historic trends tool.
API:
-
Find what you were looking for?
If you have suggestions for improving this documentation, let us know!