yadayada
Allow md5 duplication to cause file move or symlink creation
According to docs, when uploading a file acd_cli has the option to not allow duplicate uploads based on the md5 hash of the file. In my system, some files are downloaded, then moved to their eventual destination, sorted, re-moved (not removed), resorted before finding a permanent home.
Would it be possible to change this behavior? I'll try to lay out my logic tree:
Attempt to upload /bar/foo Duplicate md5 found on server /baz/foo Check if /baz/foo still exists locally If so, server-side symlink /bar/foo to /baz/foo If not, server-side move /bar/foo to /baz/foo
I plan on taking a stab at this myself, but I am sure even if successful, I will more than likely create some python abomination no one would ever allow in to the release code.
OK, I tried and failed miserably. Very miserably. I don't know python and diving into the code didn't work. If anyone picks up the torch, it would be awesome.
I read through the link you posted, and as you say, there does not seem to be a sampling function. It does seem some sort of folder linking exists: "A folder can share multiple parent folders." There is also a reference to nodes being able to having multiple parents. I don't know if these can be exploited to provide syncing functionality.
Even if not, the ability to move the position instead of re-upload or upload failed would be nice.