If I add the same picture twice by accident, I don't get a notification, the picture is just uploaded twice.

Comments

juliapradel created an issue.

miro_dietiker’s picture

I like this one a lot.

Since if a collection is well managed, it does not make sense to store the same image twice. Still it indeed happens a LOT that the media collection contains the same images again and again.

My proposal would be that Media Entity even could try to support deduplication based on a file hash. If the same image is uploaded again, it simply reuses the entity that is already existing.

Now this leads to a problem if you do cropping or want to have multiple different media metadata for differenz usages. The system would need to offer you a way to easily clone a media if you intentionally really want to create a second version of the same record. Otherwise if you change the crop or the metadata, it affects all previous usages.

The relevant metric here is usage count. So if we do deduplication and want to easily allow cloning, we would need to tell the user for instance that an image is used ready at other locations. We could display a usage count on top of the image thumbnail and offer actions such as clone on hover. This makes the cloning UI more a browser thing. Or we could even extend the browser in a way to display some media metadata of the most recent selected entry in a separate area?

Possible next steps: Create a related issue in media entity for deduplication and an issue for cloning in the browser to discuss further.