7 comments

  1. Gunar,
    I have been in this conference, and you can actually see more of this panel question and answers on my channel at vimeo,
    http://vimeo.com/user2405549/videos

    Google could have saved the metadata out of the original images, but guess what the odds this image will appear anywhere in the relevant results, is really low. most of the images that are indexed by Google are from other sites who also never kept the metadata and might not even licensed the image

    in the video channel you can actually see the PicScout solution of the Problem as presented which call ImageExchange.

    so if an image buyer wants to know the easiest way to access content owner and licensor go and download the free ImageExchange add-on at http://www.picscout.com.

    if Content owners wants to make sure Every Image Gets its Credit they need to have their content within PicScout ImageIRC


  2. Gunar:

    Thanks for bringing this issue to light. Too many developers take the “easy way out” in regards to metadata preservation. I’ve been pushing this topic for the past five years or more.

    This was one of the original three principles of the “Metadata Manifesto” (“Ownership metadata must never be removed”) that was presented at the Microsoft Pro Photo Summit in 2006 (http://www.stockartistsalliance.org/metadata-manifesto-1).

    More recently, I’ve taken up the issue by promoting a “Survey regarding the Preservation of Photo Metadata by Social Media Websites” (http://www.controlledvocabulary.com/socialmedia/).

    A surprising number of photographers are unaware that sites like Facebook are stripping all their identification info from their images on upload, while others remove this vital information any time a “derivative” version is made. This might be smaller preview, thumbnail, or watermarked versions of the original. The site above explains how anyone can easily check to see if the site is preserving their metadata after upload using a simple online tool. In addition, there is a link to preliminary data on many of the more popular services. The results will likely surprise many.

    David


  3. […] Google in the hot seat for stripping metadata in image search results « From Gunar. […]


  4. […] Gunar Thoughts On Metadata « Google in the hot seat for stripping metadata in image search results What should Google do about media metadata? June 3, 2010 The recent controversy over […]


  5. This makes Google look kind of pathetic. Why is it that the obvious decision is not so obvious to some at times? Your last statement perfectly emphaticized (yes, I just made that up) the obvious wrongheadedness from the big G.

    On a related topic – anyone know of a good metadata tool for the Chrome browser?


  6. […] Metadata? posted a couple of days ago. In it she links to a couple of posts from the Gunar blog, Google in the hot seat for stripping metadata in image search results (May 27, 2010) and What should Google do about media metadata? (June 3, […]


  7. Why is this a problem?

    Google is manufacturing a thumbnail consisting only of pixels; they are not changing your on-line file.

    A thumbmail of a photograph is a derivative work. It is within the rights of a copyright owner to prevent others (for instance, a search engine service) to create and publish derivatives i.e., thumbnails. If you care about yuor copyright even on a thumbnail, serve notice to the search engine service (and anybody else that publishes the derivative of your work). If, on the other hand, you like your images to be indexed (and promoted) by the search engine, stop whining.

    Rodrigo



Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: