Generated with poetry export: $ poetry export --without-hashes -f requirements.txt > requirements.txt $ poetry export --without-hashes --dev -f requirements.txt > requirements-dev.txt I am trying `--without-hashes` to work around an error on pip install when running in CI: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
|2 weeks ago|
|.github/workflows||6 months ago|
|csv_metadata_quality||3 months ago|
|data||1 month ago|
|tests||6 months ago|
|.drone.yml||6 months ago|
|.flake8||2 years ago|
|.gitignore||2 years ago|
|CHANGELOG.md||5 months ago|
|CITATION.cff||2 months ago|
|LICENSE.txt||2 years ago|
|README.md||6 months ago|
|poetry.lock||2 weeks ago|
|pyproject.toml||2 weeks ago|
|pytest.ini||9 months ago|
|requirements-dev.txt||2 weeks ago|
|requirements.txt||2 weeks ago|
|setup.cfg||2 years ago|
|setup.py||6 months ago|
A simple, but opinionated metadata quality checker and fixer designed to work with CSVs in the DSpace ecosystem (though it could theoretically work on any CSV that uses Dublin Core fields as columns). The implementation is essentially a pipeline of checks and fixes that begins with splitting multi-value fields on the standard DSpace "||" separator, trimming leading/trailing whitespace, and then proceeding to more specialized cases like ISSNs, ISBNs, languages, unnecessary Unicode, AGROVOC terms, etc.
Requires Python 3.7.1 or greater (3.8+ recommended). CSV and Excel support comes from the Pandas library, though your mileage may vary with Excel because this is much less tested.
If you use the DSpace CSV metadata quality checker please cite:
Orth, A. 2019. DSpace CSV metadata quality checker. Nairobi, Kenya: ILRI. https://hdl.handle.net/10568/110997.
- Validate dates, ISSNs, ISBNs, and multi-value separators ("||")
- Validate languages against ISO 639-1 (alpha2) and ISO 639-3 (alpha3)
- Experimental validation of titles and abstracts against item's Dublin Core language field
- Validate subjects against the AGROVOC REST API (see the
- Validation of licenses against the list of SPDX license identifiers
- Fix leading, trailing, and excessive (ie, more than one) whitespace
- Fix invalid and unnecessary multi-value separators (
- Fix problematic newlines (line feeds) using
- Perform Unicode normalization on strings using
- Remove unnecessary Unicode like non-breaking spaces, replacement characters, etc
- Check for "suspicious" characters that indicate encoding or copy/paste issues, for example "foreˆt" should be "forêt"
- Check for "mojibake" characters (and attempt to fix with
- Remove duplicate metadata values
- Check for duplicate items, using the title, type, and date issued as an indicator
The easiest way to install CSV Metadata Quality is with poetry:
$ git clone https://github.com/ilri/csv-metadata-quality.git $ cd csv-metadata-quality $ poetry install $ poetry shell
Otherwise, if you don't have poetry, you can use a vanilla Python virtual environment:
$ git clone https://github.com/ilri/csv-metadata-quality.git $ cd csv-metadata-quality $ python3 -m venv venv $ source venv/bin/activate $ pip install -r requirements.txt
Run CSV Metadata Quality with the
--help flag to see available options:
$ csv-metadata-quality --help
To validate and clean a CSV file you must specify input and output files using the
-o options. For example, using the included test file:
$ csv-metadata-quality -i data/test.csv -o /tmp/test.csv
Invalid Multi-Value Separators
While it is theoretically possible for a single
| character to be used legitimately in a metadata value, in my experience it is always a typo. For example, if a user mistakenly writes
Kenya|Tanzania when attempting to indicate two countries, the result will be one metadata value with the literal text
Kenya|Tanzania. This utility will correct the invalid multi-value separator so that there are two metadata values, ie
This will also remove unnecessary trailing multi-value separators, for example
You can enable several "unsafe" fixes with the
--unsafe-fixes option. Currently this will remove newlines, perform Unicode normalization, and attempt to fix "mojibake" characters.
This is considered "unsafe" because some systems give special importance to vertical space and render it properly. DSpace does not support rendering newlines in its XMLUI and has, at times, suffered from parsing errors that cause the import process to fail if an input file had newlines. The
--unsafe-fixes option strips Unix line feeds (U+000A).
Unicode is a standard for encoding text. As the standard aims to support most of the world's languages, characters can often be represented in different ways and still be valid Unicode. This leads to interesting problems that can be confusing unless you know what's going on behind the scenes. For example, the characters
é look the same, but are not — technically they refer to different code points in the Unicode standard:
éis the Unicode code point
éis the Unicode code points
Read more about Unicode normalization.
Encoding Issues aka "Mojibake"
Mojibake is a phenomenon that occurs when text is decoded using an unintended character encoding. This usually presents itself in the form of strange, garbled characters in the text. Enabling "unsafe" fixes will attempt to correct these, for example:
- CIAT PublicaÃ§ao → CIAT Publicaçao
- CIAT PublicaciÃ³n → CIAT Publicación
Pay special attention to the output of the script as well as the resulting file to make sure no new issues have been introduced. The ideal way to solve these issues is to avoid it in the first place. See this guide about opening CSVs in UTF-8 format in Excel.
You can enable validation of metadata values in certain fields against the AGROVOC REST API with the
--agrovoc-fields option. For example, in addition to agricultural subjects, many countries and regions are also present AGROVOC. Enable this validation by specifying a comma-separated list of fields:
$ csv-metadata-quality -i data/test.csv -o /tmp/test.csv -u --agrovoc-fields dc.subject,cg.coverage.country ... Invalid AGROVOC (dc.subject): FOREST Invalid AGROVOC (cg.coverage.country): KENYAA
Note: Requests to the AGROVOC REST API are cached using requests_cache to speed up subsequent runs with the same data and to be kind to the system's administrators.
You can enable experimental support for validating whether the value of an item's
dcterms.language field matches the actual language used in its title, abstract, and citation.
$ csv-metadata-quality -i data/test.csv -o /tmp/test.csv -e ... Possibly incorrect language es (detected en): Incorrect ISO 639-1 language Possibly incorrect language spa (detected eng): Incorrect ISO 639-3 language
- Reporting / summary
- Better logging, for example with INFO, WARN, and ERR levels
- Verbose, debug, or quiet options
- Warn if an author is shorter than 3 characters?
- Validate DOIs? Normalize to https://doi.org format? Or use just the DOI part: 10.1016/j.worlddev.2010.06.006
- Warn if two items use the same file in
- Add an option to drop invalid AGROVOC subjects?
- Add tests for application invocation, ie
- Validate ISSNs or journal titles against CrossRef API?
- Add configurable field validation, like specify a field name and a validation file?
- Perhaps like --validate=field.name,filename
- Add some row-based item sanity checks and fixes:
- Warn if item is Open Access, but missing a filename or URL
- Warn if item is Open Access, but missing a license
- Warn if item has an ISSN but no journal title
- Update journal titles from ISSN
This work is licensed under the GPLv3.
The license allows you to use and modify the work for personal and commercial purposes, but if you distribute the work you must provide users with a means to access the source code for the version you are distributing. Read more about the GPLv3 at TL;DR Legal.