LCSH subject terms for InvenioRDM
Install this extension to get Library of Congress Subject Headings into your instance.
From your instance directory:
pipenv install invenio-subjects-lcsh
This will add it to your Pipfile.
This repository follows calendar versioning for year and month:
2021.06.18
is both a valid semantic version and an indicator of the year-month corresponding to the loaded terms.
18
here is a patch number (not a day).
So far the package is compatible with InvenioRDM 9.1+'s subjects "ABI". If there is a breaking change, a compatibility table will be provided to indicate which version is compatible with with InvenioRDM's "ABI".
There are 2 types of users for this package. Maintainers of the package and instance administrators.
For instance administrators, after you have installed the extension as per the steps above, you will want to reload your instance's fixtures: pipenv run invenio rdm-records fixtures
. This will install the new terms in your instance.
Updating existing terms currently requires manual replacement.
This package should probably be updated on a yearly basis. Here we show how.
- Install this package locally with the
dev
extra:
pipenv run pip install -e .[dev]
- Use the installed
galter-subjects-utils
tool to get the new list:
pipenv run galter-subjects-utils lcsh --output-file invenio_subjects_lcsh/vocabularies/subjects_lcsh.jsonl
This will
-
Download the new list(s)
-
Read it filtering for topics
-
Convert terms to InvenioRDM subjects format
-
Write those to the specified file
-
Check the manifest (it should typically be all good)
pipenv run inv check-manifest
- When you are happy with the list, bump the version and release it.
Install the project in editable mode with dev
dependencies in an isolated virtualenv ((venv)
denotes that going forward):
(venv) pip install -e .[dev]
# or if using pipenv
pipenv run pip install -e .[dev]
Run tests:
(venv) invoke test
# or shorter
(venv) inv test
# or if using pipenv
pipenv run inv test
Check manifest:
(venv) inv check-manifest
# or if using pipenv
pipenv run inv check-manifest
Clean out artefacts:
(venv) inv clean
# or if using pipenv
pipenv run inv clean