View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000030 | FileSieve | Plugin | public | 2018-10-05 23:13 | 2021-01-27 22:29 |
Reporter | BootBlock | Assigned To | BootBlock | ||
Priority | none | Severity | minor | Reproducibility | N/A |
Status | assigned | Resolution | open | ||
Summary | 0000030: Plugins need to dictate to FS what ultimately happens with files | ||||
Description | Rather than just indicating what should happen to source items via the Copy Mode, plugins need to have the ultimate say in what happens to items/files during processing. For example, the Archive Modifier compresses items into the destination location and the original file needs to either ignored (if Copy Mode is set to Copy), or deleted (if Copy Mode is set to Move). The plugin(s) will then need to say “Okay, ignore/delete the original file but count it as being processed”. The Delete functionality is implemented via the Item.DeletionMode property that is set via plugins, but this more than likely needs to be rolled into a general ProcessMode property to incorporate different types of outcomes that the plugin requires and FileSieve knows about. The status of this issue can be tracked here on the FileSieve Github repository. | ||||
Tags | Processing | ||||