FileBot

My understanding is that FileBot saves only the file original name, the file original directory and the destination in the history file, bundling elements into sequences in case a single run processes more files.
My question would then be: is it possible to modify this behavior in some way to allow the collection of arbitrary information on processed files in the history file?
In case this isn't, can a similar result be achieved via the exec command? For example by committing certain information to an sqlite or csv file, or even better, to a temporary one?

devster wrote: ↑17 Apr 2018, 11:38 In case this isn't, can a similar result be achieved via the exec command? For example by committing certain information to an sqlite or csv file, or even better, to a temporary one?

Yes, absolutely. I'd love it if people could start writing and sharing --def exec scripts:
If you wanted to get the full original path in your --def exec that's not really supported though (but possible via internal API calls).

What's the information within the json?

All the object metadata that is stored as xattr, like movie name/year/id/etc.