FileSieve 4

  • Status Assigned
  • Percent Complete
  • Task Type Enhancement
  • Category Backend / Core
  • Assigned To
    Joseph Cox
  • Operating System All
  • Severity Medium
  • Priority Medium
  • Reported Version 4.00
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: FileSieve 4
Opened by Joseph Cox - 21 November 2016
Last edited by Joseph Cox - 20 June 2017

FS#33 - Plugins need to dictate to FS what ultimately happens with files

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.


Available keyboard shortcuts


Task Details

Task Editing