In some cases we need to preserve an image metadata information during processing. This patch allow this. Maybe this needs to be implemented at a core level or as a separate module, but this solution is acceptable on my opinion. And need to create tests for this.

Comments

cosolom created an issue. See original summary.

cosolom’s picture

Issue summary: View changes
StatusFileSize
new4.5 KB
steven jones’s picture

Status: Needs review » Postponed (maintainer needs more info)

Thanks very much for your contribution! It is much appreciated.

Yeah, separate module I reckon, although I get that you'd probably want to extend the pipeline entity rather than provide a simple processor.
Marking as postponed while we work out what to do with this.

cosolom’s picture

We can't use a processor because it has only an image url. And we can't determine a source for this image.

cosolom’s picture

Status: Postponed (maintainer needs more info) » Needs work
StatusFileSize
new5.64 KB

This patch preserve more informatin. And I hope that we can set the status "Needs work" so as not to lose sight of this task.

chrischaplow’s picture

This is a very useful project. Photographers are particularly interested to preserve Meta Data especially IPTC and Copyright info and status of images on the web. Whilst there is no clear evidence that Search Engines currently use Meta Data there is much debate in SEO circles about it.

jcisio’s picture

Status: Needs work » Needs review
StatusFileSize
new4.81 KB

I haven't tested yet but I like the approach. However I don't think Magick should be a requirement, it's only optional, so I remove composer.json from the patch.

Another question is, would it work with WebP module? I don't think so, unless we patch that module, too.