Research duplicate handling #Help #Question

[ldexterldesign]

Hey @jmathai,

Thanks for invaluable software, as always

Hope you're well

I'm playing devil's advocate with elodie's duplicate handling tonight

In my [s]creencast I modify a file to emulate file corruption. The new (i.e. modified) file has an identical file name and so replaces the old (i.e. original, unmodified) file on (re)import. IMO this isn't desired behaviour. I would expect elodie to be smarter and notice some difference in the files even though they share an identical file name, and keep both.

I tested this use case by deleting hash.json, hoping the checksum would do this job, but it made no difference

How can/does elodie handle this use case, because unfortunately I think I'll have to use --alow-duplicates until this is addressed; handling those duplicates another way?

If you have any issues (e.g. questions/queries) then happy to help

Hope this helps and to hear back

Keep up sterling work!

Yours faithfully

s: https://drive.google.com/open?id=13LeQW52Sou6m97xD_KICg0nLeaJui4go

[jmathai]

Sounds like what you want is an --overwrite option which would let you avoid overwriting a file at the exact same location and decide how you want to handle that on your own?

[gti96]

I actually want to know more about this duplicate situation. Based on my test, it seems like Elodie by default would skip the files in question and if --trash is present, it would remove unimported source after check. Is that normal intended behaviour?

I am currently relying on this behaviour to remove duplicates and will soon be using this to check/import other directories potentially containing corrupted files. I definitely don't want corrupted files replacing my original copies.