.
Jeffrey’s “Creative Commons” Lightroom Plugin

This Lightroom plugin allows you to inject metadata related to your Creative Commons choices into exported copies of images.

If you choose to share your copyrighted image with the world under a creative-commons license, this plugins injects details of the license into the metadata of exported copies, to tightly associate your license choice with the image.

This metadata tagging is much better than a simple text- or icon-based notation near the image, or RDFa markup in HTML, because it keeps your express wishes tied to the image even when it is later downloaded, copied, shared, deep linked, etc.

You can configure the kind and form of metadata to add, but as a quick example, the following metadata display via my online image-metadata viewer, of the metadata in the first photo of my recent post “Cute Little Melodrama in Five Photos”, illustrates the Creative-Commons metadata I chose to add:

For maximum effectiveness in both protecting the rights you chose to reserve, and in sharing the rights you choose to share, use this plugin in addition to other notation methods.

Download

This plugin works in Lightroom 5 and Lightroom 4.

The same download works for both Windows and Mac. See the box to the upper right for the download link (in orange) and installation instructions.

Library Setup

After the plugin is installed, a new metadata tagset is available, as illustrated at right.

It includes standard metadata fields such as Filename, Artist, and Copyright, and one plugin-specific field, “Creative Commons”, marked in purple in the screen snippet at right. (In that example, “BY-NC” is the standard shorthand notation for Creative Commons's "Attribution Required, No Commercial Use license.)

When one or more images are selected, you can set the “Creative Commons” field to any of the six licenses that Creative Commons defines, or three different ways to indicate that the image is not to be creative-commons licensed.

Possible Field Values

UnspecifiedThe default... no creative-commons license.
Not My ImageNo creative-commons license because you don't own copyright.
NoA specific chose not to release with a creative-commons license.
CC BY
CC BY-ND
CC BY-SA
CC BY-NC
CC BY-NC-ND
CC BY-NC-SA
The six Creative Commons licenses described here.
CC ZeroThe Creative Commons “Zero” public-domain waiver described here

The three “not Creative Commons licensed” values (Unspecified, Not My Image, and No) are all treated the same as far as the plugin is concerned... no license information will be added to exported copies... but the different values may be convenient for your own data maintenance.

For better integration with your workflow, you can add the “Creative Commons” field to your main metadata display with my “Metadata-Viewer Preset Editor” plugin.

At right is an example of what the selector looks like when viewed via my personal metadata viewer preset, where I've moved the Creative-Commons field to be near the Copyright/Artist fields, and I've shortened the field label to “C. Commons” to keep the label column narrow, preserving more of the panel width for actual image metadata.

Export Setup

Changing an image's “Creative Commons” metadata field to a license value doesn't actually change the image in your library, but if you then enable the plugin's section in your Export or Publish dialog, the exported copies of images with a creative-commons license get the appropriate metadata added.

The screenshot at right illustrates how to add the plugin's section to an Export or Publish dialog.

(Only the marked “Creative Commons” section is added by this plugin... the other items seen in the screenshot from my personal workflow are added by other plugins that I use.)

Once enabled within the Dialog, a large “Creative Commons” section appears. Here's an example of what it looks like within my own personal workflow:

As you can see, there are a lot of sanity checks (and I've enabled all of them) to help guard against accidentally releasing a mistaken image/license combination.

Warning: No Video Support

The export metadata-injector works only with images; it completely ignores all videos and no settings matter for video. Videos are passed through by Lightroom and the plugin never even sees them.

You can still set the “Creative Commons” metadata field for videos if you like, but doing so has no meaning other than perhaps a notation to yourself.

Warning: Lightroom Bug

I've noticed (and reported to Adobe) a bug in Lightroom that causes the metadata display for multiple images to sometimes be wrong.

Normally, if the selected images have multiple values for a particular field (e.g. the “City” field not all being the same city), Lightroom displays “<mixed>” to indicated that they are indeed not all the same.

However, Lightroom seems to always show “Unspecified” for the Creative-Commons field when multiple values are present among the selected images. This unfortunate bug can lead you to believe that all selected images have no creative-commons license, when in fact some or all my well have them. Take care.

Availability

This plugin is distributed as “donationware”. I have chosen to make it available for free — everyone can use it forever, without cost of any kind — but unless registered, its functionality is somewhat reduced after six weeks.

Registration is done via PayPal, and if you choose to register, it costs the minimum 1-cent PayPal fee; any amount you'd like to add beyond PayPal's sliding fees as a gift to me is completely optional, and completely appreciated.

Note: a Lightroom major upgrade, such as from Lr4 to Lr5, de-registers the plugin in the upgraded version, so if you want to maintain registration, a new ($0.01 if you like) registration code is needed in the upgraded version. It makes for a hassle every couple of years, I know. Sorry. See this note for details.

For details on plugin registration and on how I came into this hobby of Lightroom plugin development, see my Plugin Registration page.

Version History
( Update Log via RSS )

20140715.31

Fixed an issue with Creative-Cloud revalidation.

20140712.30

Lr5.5 and later Creative-Cloud installs can now revalidate themselves if needed.

20140710.29 Sigh, had a bug in the Creative-Cloud support.
20140708.28

Now supports Lr5.5+ Creative-Cloud Installs.

20140704.27 Sigh, introduced an error for some folks with the rebuild the other day.
20140630.26 Build-system update
20140621.25 Added an "Expunge Plugin Data" section to the plugin manager, to allow plugin data to be cleared from the catalog.
20140613.24

Added date_diff() and raw_time_diff() functions to the special {LUA} token understood by the plugin.

20140605.23

Fixed an issue with UNC shares on Windows.

Upgraded to the embedded copy of ExifTool to version 9.60.

20140509.22

Added new tokens to the template language the plugin understands: LrVersion, LrVersionMajor, LrVersionMinor, LrVersionRevision, LrVersionBuild, Location, CatalogName, CatalogPath, OperatingSystem, OS

Added new token filters: NS and LO

20140423.21 Fix a location-related template-token bug introduced in a recent build.
20140422.20

Fixed a bug in the "smoother revalidation" stuff recently added.

20140418.19

Using this plugin in a Publish Service and entering the Publishing Manager with no photos visible would cause the Publishing Manger to not be savable. Fixed.

Upgraded to the embedded copy of ExifTool to version 9.53.

The {Empty} template token wasn't working properly.

Make the revalidation process smoother, especially for folks using Lr5.4 and later.

20140304.18

Allowed sanity checks to be disabled in one fell swoop, and I fixed a potential error that allowed some sanity checks to be ignored.

20140129.17

Upgraded to the embedded copy of ExifTool to version 9.46.

20131214.16 Update for CC 4.0
20131102.15

Update for OS X Mavricks

Updated the Image::ExifTool library to version 9.39.

20130926.14 Oops, fix a bug introduced in the previous update
20130925.13

Added a bunch of tokens to the preset templates supported: ExportFormat, ExportColorSpace, ExportBitDepth, ExportQuality, ExportSharpeningLevel, ExportSharpeningMedia, IpernityUrl, GoogleDriveUrl, and TumblrUrl.

The token-examples dialog had been broken. Also deprecated Folder and Path tokens in preference to FolderName and FolderPath tokens.

Fixed the KW/KWE tables used by the LUA token; they had been broken when using load for the script.

Updated the Image::ExifTool library to version 9.35.

20130613.12 Better support for plugin revalidation.
20130611.11 Yet another Lr5 update
20130610.10 Final update for Lr5
20130501.9 Update for Lr5
20130412.8 Build system update.
20130328.7 Fix for the registration system.
20130220.6

Added support for some new template tokens: FlagStatus (requires Lr4.1 or later), and for Lr3 and later, a bunch of IPTC extended metadata: AdditionalModelInfo, CodeOfOrgShown, DigImageGUID, Event, ImageSupplierImageId, MinorModelAge, ModelAge, ModelReleaseID, ModelReleaseStatus, NameOfOrgShown, PersonShown, PlusVersion, PropertyReleaseID, PropertyReleaseStatus, and SourceType.

20130209.5 More build-system maintenance
20130206.4 Tweak for my registration system
20130201.3

Enhance the {EMPTY} template token so that it interrupts the squelching of superfluous joining characters.

Upgraded to the embedded copy of ExifTool to version 9.15.

20121005.2

Based on feedback from the folks at Creative Commons, updated how the various licenses are presented within Lightroom's UI, now using the official shorhands (e.g. "BY-NC") instead of what I came up with ("Attrib NonComm")

Added support for CC0 (CC Zero, their public-domain license)

Changed he sense of the "must not be marked as public-domain" sanity check to "must be marked as copyrighted".

Added more sanity-check options.

Added the copyright-status field to the metadata-viewer tagset.

20120925.1 Initial public release

Comments so far....

Commenting From Rockport Tx 28.021928,-97.050826
Great idea.
I am delivering images on Thursday under the Creative Commons.
I will try it out with this small project for the local Ronald McDonald House.

— comment by Ed Pouso on September 26th, 2012 at 12:43am JST (1 year, 10 months ago) comment permalink

This is awesome, thank you. I was wondering if you could post up a “demo” jpg that’s been exported with data from this plugin? Thanks!

Here’s one example showing the metadata in one image from my blog the other day. Searching on that page for “creative” will find things both in the basic summary at top, and in details down below. —Jeffrey

— comment by Rubin on September 26th, 2012 at 4:30am JST (1 year, 10 months ago) comment permalink
— comment by Rubin on September 26th, 2012 at 7:31am JST (1 year, 10 months ago) comment permalink

Yes, I am so happy. I have been looking for a way to add CC information in my photos. This will make it so much easier.

//Jens

— comment by Jens on September 26th, 2012 at 6:23pm JST (1 year, 10 months ago) comment permalink

What do you recommend for the “Web Statement?”
Does that field support html markup?

The “Descriptions and Defaults” button in the plugin explains it. It’s intended to hold a URL. —Jeffrey

— comment by Ian Aberle on May 14th, 2013 at 7:37am JST (1 year, 2 months ago) comment permalink

This plugin is exactly what I need except for one small thing: support for the newly released Creative Commons 4.0 is missing. Do you have any plans for adding 4.0 support?

Yes, I’ve added what I think is needed for 4.0 support, but I’m waiting on word from my contact at CC to see whether I’ve done it appropriately. —Jeffrey

— comment by Visa Putkinen on December 8th, 2013 at 8:30pm JST (7 months, 15 days ago) comment permalink

When using this what should I set the “Rights Usage Terms” field to in Lightroom’s default metadata?

If you use the plugin to set the “Usage Terms”, it’ll override anything you might have in that field. I suppose you could set it to some default that takes effect if you ever export without this plugin. I leave it blank and let the plugin fill it in for me. —Jeffrey

— comment by John Vanderbeck on February 5th, 2014 at 12:48am JST (5 months, 19 days ago) comment permalink

I’m using Lightroom 5, your Creative Commons plugin v20140129.17, and your Flickr exported plugin v20140204.327

When I look at my images on Flickr they are NOT tagged with built in Flickr support for creative commons. It just shows up as Copyrighted, all right reserved.

It seems that Flickr doesn’t recognize CC metadata within an uploaded image. But that’s okay, because my Flickr plugin was overriding it anyway with the license setting specified in that plugin. I’ve just pushed a new version of the Flickr plugin that notices when you have the CC plugin as well, and uses that value for the Flickr license. Thanks for the heads up. —Jeffrey

— comment by John Vanderbeck on March 1st, 2014 at 6:31am JST (4 months, 22 days ago) comment permalink
Leave a comment...


All comments are invisible to others until Jeffrey approves them.

Please mention what part of the world you're writing from, if you don't mind. It's always interesting to see where people are visiting from.

More or less plain text — see below for allowed markup

You can use the following tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Subscribe without commenting