digitized_image_validation

Validator for incoming digitized still image and textual assets.

Getting Started

If you have git and Docker installed, using this repository is as simple as:

git clone https://github.com/RockefellerArchiveCenter/digitized_image_validation.git
cd digitized_image_validation
docker build -t digitized_image_validation .
docker run digitized_image_validation

Usage

This repository is intended to be deployed as an ECS Task in AWS infrastructure.

Expected Package Structure

This validator expects to receive valid BagIt bags serialized as a single .tar.gz file. The bag name should correspond to the ArchivesSpace refid for the archival object they represent. The payload directory is expected to contain master, master_edited and service_edited directories. The master and master_edited directories should contain TIFF files, and the service_edited directory is expected to contain a single multipage PDF:

Audio packages

/refid
    tagmanifest-sha512.txt
    tagmanifest-sha256.txt
    bag-info.txt
    bagit.txt
    manifest-sha512.txt
    manifest-sha256.txt
    data/
        master/
            refid_0001.tiff
            refid_0002.tiff
            ...
            refid_0104.tiff
        master_edited/
            refid_0001.tiff
            refid_0002.tiff
            ...
            refid_0104.tiff
        service_edited/
            refid.pdf

License

This code is released under the MIT License.

Contributing

This is an open source project and we welcome contributions! If you want to fix a bug, or have an idea of how to enhance the application, the process looks like this:

1. File an issue in this repository. This will provide a location to discuss proposed implementations of fixes or enhancements, and can then be tied to a subsequent pull request.
2. If you have an idea of how to fix the bug (or make the improvements), fork the repository and work in your own branch. When you are done, push the branch back to this repository and set up a pull request. Automated unit tests are run on all pull requests. Any new code should have unit test coverage, documentation (if necessary), and should conform to the Python PEP8 style guidelines.
3. After some back and forth between you and core committers (or individuals who have privileges to commit to the base branch of this repository), your code will probably be merged, perhaps with some minor changes.

This repository contains a configuration file for git pre-commit hooks which help ensure that code is linted before it is checked into version control. It is strongly recommended that you install these hooks locally by installing pre-commit and running pre-commit install.

Tests

New code should have unit tests. Tests can be run using tox.