The National Archives: Find Case Law
This repository is part of the Find Case Law project at The National Archives. For more information on the project, check the documentation.
Python Utilities
This repository predominantly contains information about the courts in the Find Case Law project.
pypi name: ds-caselaw-utils
python import name: ds_caselaw_utils
Examples
from ds_caselaw_utils import neutral_url
neutral_url("[2022] EAT 1") # '/eat/2022/4'
from ds_caselaw_utils import courts
courts.get_all() # return a list of all courts
courts.get_by_param("ewhc/ch") # get a court by its parameter value
courts.get_selectable() # returns a list of all courts that are whitelisted to
# appear as searchable options
courts.get_selectable_groups() # returns a grouped list of all courts and tribunals
# that are whitelisted as searchable options
courts.get_grouped_selectable_courts() # returns selectable courts grouped for display
courts.get_grouped_selectable_tribunals() # returns selectable tribunals grouped for display
courts.get_listable_groups() # returns a grouped list of courts that are whitelisted to
# be listed publicly
courts.get_grouped_listable_courts() # returns listable courts grouped for display
courts.get_grouped_listable_tribunals() # returns listable tribunals grouped for display
courts.get_listable_courts() # returns a list of all *courts* (ie not tribunals)
# which are whitelisted to be listed publicly
courts.get_listable_tribunals() # return a list of all *tribunals* which are
# whitelisted to be listed publicly
The list of courts is defined in src/ds_caselaw_utils/data/court_names.yml. The format is as follows:
- name: high_court # Internal name of a group of courts to be displayed together
display_name: "High Court" # An optional public facing name for this group.
is_tribunal: false # Whether this group contains courts or tribunals
courts: # List of courts to be displayed under this group
- # An internal code for this court:
code: EWHC-SeniorCourtsCosts
# The public facing name of the court:
name: High Court (Senior Courts Costs Office)
# An optional alternative wording for use when displayed in grouped format (defaults to 'name'):
grouped_name: Senior Court Costs Office
# A URL to link to for more information on this court:
link: https://www.gov.uk/courts-tribunals/senior-courts-costs-office
# A regex matching neutral citations for this court's judgments:
ncn: \[(\d{4})\] (EWHC) (\d+) \((SCCO)\)
# The canonical parameter value used in searches for this court:
param: "ewhc/scco"
# Any additional parameter aliases which display judgments from this court:
extra_params: ["ewhc/costs"]
# The year of the first judgment we have on file for this court:
start_year: 2003
# The year of the last judgment we have on file for this court
# (optional, defaults to current year):
end_year: ~
# Whether to expose this court publicly as selectable in search filters:
selectable: true
# Whether to expose this court publicly in listings:
listable: true
# Whether this court has ended yet
ended: false
# Whether this court is a court of record (optional):
court_of_record: true
Requirements
The environment you develop this repo in requires the following to be installed:
python 3.12(as the project is pinned to python 3.12)poetry(as this is used for depdenency management and virtual environment management)pre-commit(to install git hooks defined in.pre-commit-config.yaml)
Getting set up
- Run
pre-commit installinside the root directory of the repo to install the git hooks defined in.pre-commit-config.yaml.
$ poetry shell
$ poetry install
Testing
While in a poetry shell:
$ poetry run pytest
Building
$ rm -rf dist
$ poetry build
$ python3 -m twine upload --repository testpypi dist/* --verbose
Release process
When making a new release, update the changelog in the release pull request.
The package will only be released to PyPI if a new tag is created. A merge to main alone will not trigger a release to PyPI.
If the release fails to push to PyPI, you can delete the tag with git pull, git push --delete origin v1.2.3 and try again.
To create a release:
- Update the version number in
pyproject.toml - Create a branch
release/v{major}.{minor}.{patch} - Update
CHANGELOG.mdandpyproject.tomlfor the release - Commit and push
- Open a PR from that branch to main
- Get approval on the PR
- Tag the HEAD of the PR
v{major}.{minor}.{patch}and push the tag - Merge the PR to main and push
- Add a new release to Github for that tag for consistency's sake
5 maintainers
Metadata
5 maintainers
Release files for ds-caselaw-utils 4.10.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| ds_caselaw_utils-4.10.0.tar.gz | 27.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ds_caselaw_utils-4.10.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 59.4 kB
Release files / ds_caselaw_utils-4.10.0.tar.gz
| Download URL | ds_caselaw_utils-4.10.0.tar.gz |
|---|---|
| Size | 27.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dd0b009eccbf7705f291bcc78c20392f319e1892aa2e2b62e7ccb6b06ea994e1
|
|
BLAKE2b-256 checksum How to use checksums |
4f061e6472144bbf50fbba5cefb882ebf350d73ebcd3330fc7e1774bc1478d01
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 8, 2026.
Transparency logRelease files / ds_caselaw_utils-4.10.0-py3-none-any.whl
| Download URL | ds_caselaw_utils-4.10.0-py3-none-any.whl |
|---|---|
| Size | 31.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dead1f9418a6a9c92e8fb8efbfa96843ac064ed545059df4038a4d69f33dc332
|
|
BLAKE2b-256 checksum How to use checksums |
294b04825665b61d33f05c56785a95cf38d5fd9daf98c9289b8907166435e387
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 8, 2026.
Transparency log
