Document SCAM workflow

[jimk-bdrc]

As a digital archivist at BDRC, I would like to asses SCAM and compare the costs of its workflow against the outside vendor that BDRC uses. (@jimk-bdrc - write DDD workflow rubric).

To do that, AO needs to walk through the complete cycle of SCAMming a work, without being interrupted for training in how to use it.

A User's Guide to SCAM would facilitate this process. It should document:

1. preparation requirements - what folder structures, how to prepare for transmission
2. Sending to scam:

• format
• authorization private (Not public in the repo)
• location - private

3. Invoking scam

• endpoint/resource URI (may be private)
• credentials - private
• invocation

4. Reviewing output:

• endpoint/resource URI - private
• credentials - private
• invocation

5. Downloading / transferring

• endpoint/resource URI
• credentials
• invocation

6. Define resulting format