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:
- preparation requirements - what folder structures, how to prepare for transmission
- Sending to scam:
- format
- authorization private (Not public in the repo)
- location - private
- Invoking scam
- endpoint/resource URI (may be private)
- credentials - private
- invocation
- Reviewing output:
- endpoint/resource URI - private
- credentials - private
- invocation
- Downloading / transferring
- endpoint/resource URI
- credentials
- invocation
- Define resulting format
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: