Skip to content

Latest commit

 

History

History
executable file
·
114 lines (74 loc) · 3.68 KB

README.md

File metadata and controls

executable file
·
114 lines (74 loc) · 3.68 KB
Raw

preshus

PREServation Hash UtilitieS

or: tools for using checksums in preservation workflows

Here's a list of tools available in this repo

  • hashsync
  • hashmaker
  • hashchecker

hashsync

What Is It?

hashcopy is a tool that moves files from one directory or volume to another with logged checksum verification. The verification performed by hashcopy is done using checksums held in sidecar files. Here is the workflows

  • check to see if sidecar files exist for source file(s)
  • if sidecar files don't exist, make them
  • if sidecar files are out of date (modified date is earlier than modified date of parent file), remake them
  • move all files and sidecar files
  • validate any non-sidecar file once it is moved

What Is A Sidecar File?

A sidecar file is a plaintext file that contains the checksum of it's parent file, as well as the relative path to the parent file. Here's is the sample nesting of a sidecar file1

Directory
│
├── sample_file.mov
│
└── sample_file.mov.md5

here is the sample contents of the above sidecar file

d025ffdc24da6411ee12caf23b2f0616 *sample_file1.gif

the * character refers the fact that the path is relative. Since the sidecar file is nested next to the file there is nothing but the filename. This is useful for validation with other preservation tools, but isn't necessary or currently used by any preshus tools

Logging

It's very important for us to know if something failed. However, in some cases hundreds or thousands of files are being moved. In order to make it easier to see if there are failures, a log is created in the destination folder. The user can search for the text "ERROR" or "WARNING" to see if something went wrong. Here is the meaning of these messages

  • WARNING
    • A source checksum was found to be out of dated and was recreated
  • ERROR
    • A checksum was invalid after moving a file. this is very bad

General Usage

python hashsync.py [flags] [any number of source directories or source file full paths] [destination parent directory full path]

to copy a file (windows filepath)

python hashmove.py C:/path/to/file.ext C:/path/to/parent/dir

to copy a directory (unix filepath)

python hashmove.py /home/path/to/sourceDir/ /home/path/to/destDir/

to copy two files and a directory (unix filepath)

python hashmove.py /home/path/to/sourceDir1/file1 /home/path/to/sourceDir2/ /home/path/to/sourceDir3/file3 /home/path/to/destDir/

hashmaker

hashmaker creates and validates sidecar checksum files

General Usage

python hashchecker.py [flags] [any number of source directories or source file full paths]

Important Details

  • In order to use hashmaker you'll need to give it either the -m flag (make mode) or -v flag (verify mode). You cannot run the script without one of these flags, and you cannot run it with both of them at the same time.
  • In make mode hashmaker will recreate a sidecar file if it's out of date. It will report this as a WARNING.

hashchecker

hashchecker will validate sidecar checksum files against checksums stored in Salesforce. This script is built to work with BAVC's Salesforce implementation, so it's not very extensible. However, it may be helpful for people trying to work with the Salesforce API.

Credentials Setup

In order to use this you'll need to create a config.py file with the following format:

username = "[email protected]"
password = "yourpassword"
security_token = "yourAPIkey"

Required Libraries

You'll need to install simple_salesforce. You can do so with the following command

pip3 install simple_salesforce

General Usage

python hashchecker.py [any number of source directories or source file full paths]