DSpace CSV Metadata Quality Checker

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 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.

Functionality

• 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 --agrovoc-fields option)
• Fix leading, trailing, and excessive (ie, more than one) whitespace
• Fix invalid and unnecessary multi-value separators (|) using --unsafe-fixes
• Fix problematic newlines (line feeds) using --unsafe-fixes
• 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"
• Remove duplicate metadata values
• Perform Unicode normalization on strings using --unsafe-fixes

Installation

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

Usage

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 -i and -o options. For example, using the included test file:

$ csv-metadata-quality -i data/test.csv -o /tmp/test.csv

Unsafe Fixes

You can enable several "unsafe" fixes with the --unsafe-fixes option. Currently this will attempt to fix invalid multi-value separators and remove newlines.

Invalid Multi-Value Separators

This is considered "unsafe" because it is theoretically possible for a single | character to be used legitimately in a metadata value, though 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. The --unsafe-fixes option will correct the invalid multi-value separator so that there are two metadata values, ie Kenya||Tanzania.

This will also remove unnecessary trailing multi-value separators, for example Kenya||Tanzania||.

Newlines

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 Normalization

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 é and é look the same, but are not — technically they refer to different code points in the Unicode standard:

• é is the Unicode code point U+00E9
• é is the Unicode code points U+0065 + U+0301

Read more about Unicode normalization.

AGROVOC Validation

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.

Experimental Checks

You can enable experimental support for validating whether the value of an item's dc.language.iso or 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

This currently uses the Python langid library. In the future I would like to move to the fastText library, but there is currently an issue with their Python bindings that makes this unfeasible.

Todo

• 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 dc.rights field against SPDX? Perhaps with an option like -m spdx to enable the spdx module?
• 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 filename column
• Add an option to drop invalid AGROVOC subjects?
• Add tests for application invocation, ie tests/test_app.py?
• Validate ISSNs or journal titles against CrossRef API?
• Better ISO 8601 date parsing (currently only supports simple dates, perhaps we need to use dateutil.parser.parseiso())
• Fix lazy date check (assumes field name has "date" but could be dcterms.issued etc!)

License

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.