Notice about behavior change when processing UFDR files with version 4.x

[lfcnassif]

Hello all,

I would like to warn about a behavior change not listed in the release notes. In 3.x versions, passing the UFDR parent folder to -d parameter used to work non intentionally. In version 4, to make behavior consistent across input formats, now it is mandatory to pass the UFDR file itself to -d parameter to ingest it correctly. Passing the parent folder would not work fine, the UFDR file would be processed like a generic ZIP file, not like an UFDR file.