Branding XMP Sidecar Files with J

• jacks

  3 40 6.9 HTML

  Consolidated J language code referenced in my blog Analyze the Data not the Drivel

  For details on how to use titbrandxmp refer to the J script brandxmp.ijs and the associated document brandxmp.pdf. Both of these files are available on GitHub. Enjoy!

• darktable

  389 8,751 10.0 C

  darktable is an open source photography workflow application and raw developer

  

  Darktable, my current favorite RAW developer, creates and maintains XMPs when you add images to its library or apply non-destructive edits. Darktable's edits are stored in sidecar XMPs leaving the originals unmolested. When you export a developed image Darktable creates a copy of the original, applies all the edits stored in the sidecar file, and then inserts Dublin Core metadata elements in the copy's IPTC metadata. Most image processors leave Dublin Core elements alone so they make a nice home for hash hacks.

• WorkOS

  workos.com

  sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• exiftool

  249 2,827 6.8 Perl

  ExifTool meta information reader/writer

  

  Once you recognize the need for proper hashes the question becomes, "Where do you store them?" You might think a file's EXIF or ITPC metadata would be the ideal location. I tried this approach. Using the superb exiftool, I inserted hashes in images only to watch various editors strip or mangle them later on. The XMP (e*Xtensible **Metadata **P*latform) sidecar3 file was created to address this and other irritants. The XMP sidecar file provides a safe home for image metadata with the added bonus that you never need to touch or alter the original image file. If you don't treat your original RAWs like sacred bytes there's something wrong with you.

Suggest a related project