...
- When the module is disabled, we could offer an e-mail based strategy to process archive request process requests (as in "Completed Work" above)
- To enable the module, configure one or more backup extractors (possibly in an array in the configuration?)
- When the module is enabled, unarchived files offer an "Archive" option in the UI - when pressed, config is checked for which extractor should be used for archival and request is sent
- If useful, this could potentially offer multiple archive targets if more than one is configured - e.g. S3, NFS, Glacier, etc
...
- Is this new optional functionality a Play! Framework "module"? Perhaps this is something entirely different?
- Should we support multiple archive options simultaneously (similar to the proposed Multiple Storage Backend feature)?
- Could we easily provide a common pattern for extractor developers to use as a base for such archive/unarchive extractors?
- Would such a pattern require two different extractors? Could we easily parameterize the `process_message` call?
- Should the backup extractors also be listed in the Manual Submission view with the other extractors?
- This could confuse end users, but as long as extractor is SAFE this should be ok - this may take careful design