Open baschny opened 3 months ago
Another idea would be to introduce a new extractor_hash
field recording a hash of extracted information (i.e. a hash per field), so that on a later move or replace it can decide if the field was manipulated by an editor in the backend or not, and just "replace" information which was also originally extracted.
Problem
"Replaces" files do not get the new metadata extracted.
How to reproduce
sys_file_metadata.copyright
Debugging
Debugging shows that this happens due to this workaround, which was introduced here to cope with "moving" files: https://github.com/xperseguers/t3ext-extractor/commit/001a773e29a2a23d95745523b3d78dc8d153d85c due to this problem: https://forge.typo3.org/issues/91168
Reasoning
In our project, due to strict asset regulatory reasons, we have disabled all metadata to be edited in the backend ("readonly") and rely solely on the metadata from the files themselves, so that we need them to be always up-to-date.
So we do not have the problem of "overwriting" metadata which might have been manipulated manually, but we indeed want this to happen. Maybe introduce a switch to make this workaround optional, or have a way to cope with the "Replace" functionality differently than what happens in a "Move file" situation.