{"id":11278,"date":"2019-07-09T07:31:37","date_gmt":"2019-07-09T05:31:37","guid":{"rendered":"http:\/\/flaven.fr\/?p=11278"},"modified":"2019-07-09T07:32:29","modified_gmt":"2019-07-09T05:32:29","slug":"image-metadata-dam-getting-metada-from-pictures","status":"publish","type":"post","link":"https:\/\/flaven.fr\/2019\/07\/image-metadata-dam-getting-metada-from-pictures\/","title":{"rendered":"Image, metadata, DAM – Getting metada from pictures"},"content":{"rendered":"

Since 6 months I am working on a new project: launching a new back office that should replace the previous one based on Drupal.
\nThe project was almost a wreck as we try to reproduce, a on a Symfony based application, what was previously existing even even features endorsing the worst habits!<\/p>\n

The main and unacknowledged objective was to copy the existing and previous tool and to focus on features that can be new and interesting. <\/p>\n

Like I usually say with a shrug: “Anyway…” to encourage my mind to move on and not to get stuck on what should have been done!
\nSo anyway, as somebody say “regret is a second mistake”.<\/p>\n

It was the occasion like always to discover again some elements both technical and editorial. As you may know, using a picture without credits is illegal when you are using a picture to illustrate a post, you need at minimum to declare the copyright and to ensure that you have the right to usage this image.<\/b><\/p>\n

Long time ago, I did a post about this subject. The concern is still the same, how can you leverage on EXIF metadata from pictures and populate the data inside a CMS for credits, description and title.<\/p>\n

At the time, I was using Photoshop and use WordPress to grab the data. This time I have been looking for open source tools to make.<\/p>\n

Here is 2 of the tools that have bee using :<\/p>\n

    \n
  1. exiftool is a command line tool that allows you to change and manipulate the EXIF metadata of images.<\/li>\n
  2. detox is a utility designed to clean up filenames. It replaces difficult to work with characters, such as spaces, with standard equivalents. It will also clean up filenames with UTF-8 or Latin-1 (or CP-1252) characters in them (i.e: foo bar – quz.avi -> foo_bar-quz.avi).<\/li>\n<\/ol>\n
    \r\n#install tools with homebrew\r\nbrew install exiftool\r\nbrew install detox\r\n\r\n#renaming files inside a directory named photos\r\ndetox -r -v photos\/\r\n<\/pre>\n
    \r\n #go to path\r\ncd \/your-path-to-the-images\/_values_images\/\r\n\r\n#check infos\r\nexiftool -a -u -g1 000_1G87QJ_v1.jpg\r\n<\/pre>\n
    The metadata output in the console<\/b>
    \n\"Image,<\/p>\n
    \r\n#check infos\r\nexiftool -T -createdate -aperture -shutterspeed -iso DIR > out.txt\r\n\r\n#check infos and output in a text file named out.txt\r\nexiftool -a -u -g1 000_1G87QJ_v1.jpg > out.txt\r\n<\/pre>\n
    Source: https:\/\/arslan.io\/2018\/04\/18\/tips-tricks-to-batch-edit-exif-metadata-of-photos\/<\/a><\/i><\/p>\n
    Conclusion: Indeed, it is a very good habit to grab EXIF from pictures. All these EXIF stuff is part of a true DAM (Digital Assets Management).  It is worth working around that question, especially if you are using images from Reuters, AFP, Getty or any photographic fund or archive. If done well, leveraging on EXIF will save much more time later when it is time to look for content inside your CMS. This is critical for a useful DAM.<\/b><\/p>\n
    Read more<\/h2>\n