Watch Folder moving/ingesting files

[Bryson Jones]

Could you give us some more info on the path? It seems that you are picking up the “enclosing folder” which we don’t do a lot (I’ve never used that myself actually) but it seems like Worker is taking the “enclosing folder” of the ingest/watch folder.

You can test this easily by putting a file directly in the watch and then in a couple of folders deep. If they show the same enclosing folder, you have your answer.

This looks like a good job for some variables. I’d get your integrator to show you how they work. It’s a powerful tool. Hope that helps a little.

bryson

bryson “at” northshoreautomation.com

northshoreautomation.com

[Betsy Meacham]

Don’t know if this helps but:
It starts here:

Ends here instead of in the 2014Q1 folder

[Bryson Jones]

I tested your action on a Mac worker and it worked as it should.

I put it 2 folders deep in the watch folder.

(watch/grandparent/parent/file)

and the Worker picked it up and moved it into the output folder bringing over the enclosing folder.

(output_folder/parent/file)

I’m wondering if this is a windows issue. As I said, I’d really try to use variables for this as in the long run it’s just a better method.

If you chose “expand variables” as an option, these would be the variables you need to put in the destination after the path to your output folder. (These are OS X paths obviously, but it all works in Windows too.)

/path/to/output_folder/$q/$f

$q = parent folder name

$f = file name with extension i.e file.jpg

Be careful and have fun.

But this behavior is potentially a bug that should be reported as well.

bryson

bryson “at” northshoreautomation.com

northshoreautomation.com