Jeffrey’s “Data Explorer” Lightroom Plugin

One example of the plugin's 251 ways to group your images

This plugin for Adobe Lightroom allows you group photos and videos in your Lightroom catalog by more than 200 data criteria. For example, grouping a large folder tree by Crop Amount might result in the screenshot seen above.

By clicking isolate on each row, the relevant images are shown. The plugin also creates a row-specific collection, such as:

Data Explorer > Crop Amount > Slight Crop

and populates it with the pertinent photos so that you can refer to them later.

The basic purpose is essentially the same as Lightroom's own Library Grid Filter, but Adobe's built-in functionality, though fast, has extremely limited scope. If it were able to handle more than the scant few fields it currently supports, there would be no need for this plugin, but it doesn't, so here we are.

As it is, this plugin lets you inspect and group photos via a bewildering number of criteria, from the mundane (group by copyright name) to the esoteric (group by geoencoded hemispheres) to the particular (group by amount of Clarity applied in Develop) to the advanced (group by camera-calibration profile). The entire list of 251 criteria is shown below.

Table of Contents

Download

This plugin works in Lightroom Classic, and older versions as far back as Lightroom 4.1, though some features depend on the version of Lightroom.

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.

Search. Filter. Group. Explore.

This plugin can be used to search or to browse. A search helps you locate photos that match specific criteria, such as "Where are my panoramas with a really wide aspect ratio?", while browsing lets you see the range of values represented by some particular criteria in your library, answering questions like What range of aspect ratios do I have in my library? (The answer for my catalog at the moment: as tall as 1 : 2.58151 and as wide as 6.4 : 1”).

Browsing can be both fun and useful, especially for catalog cleanup, such as after grouping by Copyright, you may see various versions of the same person's name that you'd want to make identical.

Sometimes the results are surprising. While making the screenshot shown at the top of this page, the first thing I noticed was that four photos had an essentially-100% crop! I wondered what they were, and found the answer with one click of the isolate button: the four photos were presented and I recognized them as the extrem crops that appeared on this blog post 18 months ago, and an extreme crop of the first photo on this post that I used to use as my online avatar.

Anyway, I started writing this plugin the first time I tried to use the results of an X-Rite ColorChecker Passport in Lightroom, which allows you to make situation-specific camera-calibration profiles for Lightroom's render engine. After trying it with some photos in my library, I quickly lost track of which photos got which profile; it was very frustrating because the only way to know was to inspect each photo's develop settings, one by tedious one, and manually keep a running tally.

Now, I can invoke this plugin on a folder and quickly see:

It didn't take long to solve my immediate need (a crude plugin that merely listed the camera-calibration profiles and their photos), but it's taken three weeks of never-ending just one more enhancement... development to whip it into good enough shape to put my name on and release.

Even while writing up this web page after I thought the plugin was ready to release, I realized that Lightroom does not normally subject images hidden within collapsed stacks to catalog operations (such as the grouping operation done by this plugin), so writing this page got put on hold while I addressed that issue in the plugin:

It wasn't straightforward at all, especially to handle it as efficiently as possible, so I burned the better part of a day on just that. Such is the nature of Lightroom plugin development driven by a passion to make things useful.

When first released the plugin supported 109 explore criteria; now it supports 251 criteria.

For times when you want only to search, this Data-Explorer plugin may well fill your needs, but you may also want to keep the following plugins in mind as well:

I've not used John's plugin, but it looks to be quite impressive.

Invocation

The plugin is invoked via File > Plugin Extras > Explore..., but it's much faster and convenient to invoke via a Lightroom keyboard shortcut.

On Windows, the keyboard shortcut is ALT-F S E.

On a Mac, you can set the shortcut as you like. For my own workflow, I've chosen Option Shift Command F.

This pops up a dialog that allows you to select the criterion to explore by:

You can pick something from the dropdown box (currently showing Aspect Ratio... in the screenshot above), or just start typing search terms, and the dialog immediately transforms into an effective way to find the item you want among the 251 criteria the plugin supports:

Clicking on any criterion returns you to the initial dialog with that item selected, but if the search results in just one criterion, you can press ENTER to immediately launch Data Explorer with that criterion as the basis for grouping.

The Include items hidden within collapsed stacks? option is off by default because with large sets of photos it can cause quite a delay because when enabled, the plugin must fetch stack-related data from the catalog, then walk the list inspecting each stack for new photos not already included.

This doesn't take long for small sets of photos... on my laptop it takes about a second to do 1,000 photos, but even this is highly dependent on what else Lightroom is doing in the background. (When I select All Photographs, Lightroom turns my CPU into a space heater as it renders thumbnails in the background.)

But that time adds up, and it's a one-minute delay for 60,000 photos. Because the process must finish before the grouping process can be launched, I made the entire option default to unselected.

By the way, here's an interesting general little Lightroom workflow tidbit: Lightroom ignores stacks if you select both Folders and Collections, bringing anything that had been hidden within collapsed stacks into the target set. So, if you select All Photographs in the upper left of Library and see X of Y photos in the filmstrip instead of just Y photos, and if this can't be explained by you Library Filter, you have photos hidden within collapsed stacks.

If you then option-click (ALT-click) on any folder, you're not really adding anything new to the target set because any folder's photos are already included with All Photographs, but because you've now got a collection and a folder selected, Lightroom ignores stacking and voilà, you're at a straight-up Y photos that really is everything in your catalog.

You can apply the same idea while viewing a specific folder if you create an empty collection (perhaps named Empty) that you can add to the selection.

Criteria List

The following table lists the 251 criteria available as of version 20181015.160.

Due to the nature of Lightroom's plugin infrastructure, items marked with a * take longer to process.
Items marked with a *** take even longer, requiring a full inspection of each master image file.

Don't see the field you want in the list below? Check out User-Specified Field toward the end of the list; it lets you inspect any metadata field in a master image file.

In Lightroom Library
File Currently Available?*File is available, or offline (e.g. on an external disk not currently connect)?

Example responses include:

  • Offline (master file not available)
  • Offline (but Smart Preview does exist)
  • Available (though without a Smart Preview)
  • Available, but file on disk is empty(!!!)
  • Available, but file on disk is smaller than Lightroom expects
  • Available, but file on disk is larger than Lightroom expects
Smart-Preview Status*Does a smart preview exist for the image? (Lightroom 5.0 and later)

Example responses include:

  • Yes
  • Yes (but master image has fewer bytes)
  • No (but could be built)
  • No (can't be built; photo is unavailable)

Also reports the amount of disk space actually taken by Smart Previews, and the space savings afforded by those Smart Previews (that is, for images with Smart Previews, their disk space relative to the disk space required for their master images).

File TypeFile type (DNG, JPEG, Raw, Video, ...)
Image Representations*List of image forms (master files, JPEG sidecars, and virtual copies) for each selected photo.

Unlike other items that this plugin can report, this item's report can reference unselected items (e.g. unselected virtual copies of a selected master, or vice-versa), and even items not in the catalog (e.g. unread JPEG sidecar files).

If a raw file has a JPEG sidecar, this plugin reports the JPEG as missing from the catalog, because Lightroom doesn't offer a way for a plugin to know about sidecars. Also, this item works only on images whose master-image folder is present.

Photo Merge Type***HDR, Panorama, ...
File Write-Permission StatusWhether the file can be changed (written) and/or deleted
Folder NameName of the folder (without path) the file is in. Useful for isolating images in a parent folder when there are also images in a subfolder.
Folder HierarchyThe hierarchy of the folder that each image is in, as it appears in the Library “Folders” panel.

For a “Folder Hierarchy” search only, the “isolate” button on the result page creates not just a simple collection with the photos, but replicates the folder hierarchy as a hierarchy of collection sets and collections.

Note that there is special handling for when a folder contains both photos and other folders: Lightroom doesn't allow photos to appear in a collection set, nor collections to appear in other collections, so when there is an overlap, the plugin makes both a collection and a collection set with what appears to be the same name, though in reality one name has a space appended to it.

Path NameFull path of the folder the file is in. Useful for isolating images in a parent folder when there are also images in a subfolder.
File ExtensionFilename extension (JPG, NEF, AVI, MTS, CR2, ...) in a case-insensitive manner.
File Extension
(case sensitive)
Filename extension (jpg, NEF, AVI, mts, CR2, ...) in a case-sensitive manner
Copy NameVirtual-copy name for the photo/video.
Virtual-Copy CountNumber of virtual copies a master image or video has.
Snapshot Count*The number of snapshots for the related master photo.
Snapshot Names*The names of any snapshots (for the related master photos; virtual copies share snapshots with their master).
Stacking StatusStatus with respect to stacking (within its parent folder).

Example responses include:

  • Not stacked
  • Part of a visible stack
  • Top of a collapsed stack
  • Hidden within a collapsed stack
Stack-Membership SizeNumber of photos/videos in its stack (within its parent folder).
Position in StackPlace in stack (within its parent folder).

Example responses include:

  • Not stacked
  • Top
  • Bottom
  • Inside
Number of UpdatesRough count of changes (both metadata updates and develop edits). It's not an absolute counter, though, as Lightroom lumps multiple changes within a short time as a single update.
Most-Recent Update DateDate of the most recent database change (metadata update or develop edit) to the image
RatingStar rating (a number from 1 to 5).
Flag StatusPick, Rejected, or Neither
Color LabelColor label name.
Plugin Custom Metadata?Shows the number of plugins that have added custom metadata for the image. The list of plugin ids is included in TSV spreadsheet file.
Keywords and Faces
Specific KeywordDescribe images with respect to a specific keyword (does include it, does not, etc.)

Example responses include:

  • Keyworded with “wedding”
  • Keyworded with “wedding” and something unrelated
  • Keyworded with a synonym of “wedding”
  • Keyworded with something unrelated
  • Not keyworded
Keyword List
(all)
List of keywords, both exportable and non-exportable, associated with an image. This may include synonyms and parents. [Warning: can be long!]
Keyword List
(exportable only)
List of keywords associated with an image that would be exported (perhaps including synonyms and parents). [Warning: can be long!]
Keyword Count (all)Count of keywords associated with an image (those directly assigned, and possibly their synonyms and parents)
Keyword Count (exportable)Count of keywords that would actually be exported (those directly assigned, and possibly their synonyms and parents)
Directly-Assigned Keywords
(individually, all)
Each keyword directly assigned, as individual items. This does not include synonyms or parents.
Directly-Assigned Keywords
(individually, exportable only)
Each keyword directly assigned that's marked “Include on Export”, as individual items. This does not include synonyms or parents.
Directly-Assigned Keywords
(individually, non-exportable only)
Each keyword directly assigned that's not marked “Include on Export”, as individual items. This does not include synonyms or parents.
Count of Directly-Assigned Keywords (all)Count of directly-assigned keywords. This does not include synonyms and parents.

Also reports the total number of distinct keywords seen across all selected images.

Count of Directly-Assigned Keywords (exportable)Count of directly-assigned keywords marked “Include on Export”. This does not include synonyms or parents.

Also reports the total number of distinct keywords seen across all selected images.

Count of Directly-Assigned Keywords (non-exportable)Count of directly-assigned keywords not marked “Include on Export”. This does not include synonyms or parents.

Also reports the total number of distinct keywords seen across all selected images.

Count of People Tagged in a PhotoCount of people tagged in a photo (confirmed faces only).
Count of People Tagged in a Photo
via keyword that is marked “Include on Export”.
Count of people tagged in a photo (confirmed faces only) where the keyword is marked “Include on Export”.
Count of People Tagged in a Photo
via keyword that is not marked “Include on Export”.
Count of people tagged in a photo (confirmed faces only) where the keyword is not marked “Include on Export”.
Cropped-out-but-Exportable People***List faces that have been completely cropped out of an image, but whose name keywords are marked for export. If people keywords are included in the export, the names of those cropped out are included as well, which could be a privacy issue. This item is very slow to process because the plugin actually exports each photo in the background.
Collection Membership
Collection Membership*
(All)
Lists the collections (standard or publish) that selected photos are part of.

This item could entail a performance hit for some catalogs. In order to calculate the results for this item, the plugin has to do a manual walkthrough of every photo in every publish collection and in every non-publish smart collection of the entire catalog, regardless of how many or few photos are selected for inspection. This could take some time.

Normally the search ignores collections that this plugin itself creates (when you isolate results after a search), but as an option you can have them included as well.

For convenience, publish collections that have items waiting to be published include a “Publish Now” button; the lack of a button means that the collection is all up to date.

Note: any Workflow Delete Options collections are always ignored.

Collection Membership*
(non-Publish only)
Lists the standard (non-publish) collections that selected photos are part of.

This item could entail a performance hit for some catalogs. In order to calculate the results for this item, the plugin has to do a manual walkthrough of every photo in every non-publish smart collection of the entire catalog, regardless of how many or few photos are selected for inspection. This could take some time.

Normally the search ignores collections that this plugin itself creates (when you isolate results after a search), but as an option you can have them included as well.

Note: any Workflow Delete Options collections are always ignored.

Collection Membership*
(Publish only)
Lists the publish collections that selected photos are part of.

This item could entail a performance hit for some catalogs. In order to calculate the results for this item, the plugin has to do a manual walkthrough of every photo in every publish collection of the entire catalog, regardless of how many or few photos are selected for inspection. This could take some time.

Normally the search ignores collections that this plugin itself creates (when you isolate results after a search), but as an option you can have them included as well.

For convenience, publish collections that have items waiting to be published include a “Publish Now” button; the lack of a button means that the collection is all up to date.

Note: any Workflow Delete Options collections are always ignored.

Equipment
Camera Make and ModelCamera make and model in a normal human-readable way (e.g. “Nikon D4”, “Apple iPhone 5s”, etc.)
Camera Make, Model,
and Serial Number
Camera name with its serial number.
LensThe lens used to take the photo (e.g. “50 mm f/1.4”).
Lens Description***
(built from master-file data)
A description of the lens cobbled together from the raw master-file metadata. This can be useful to identify certain kinds of manual lenses, or perhaps lens + teleconverter combinations.
Focal LengthFocal length of lens as shot (e.g. “85 mm”).
Focal Length 35mm EquivFocal length of the lens as shot, in full-frame 35mm terms (e.g. “135 mm”).
Post-Crop Focal Length 35mm EquivEffective focal length, in full-frame 35mm terms, of the post-crop image. (e.g. “135 mm”).
Focal Length Needed For Sensor SizeComputes the focal length, given a target sensor size, of the lens needed to match the post-crop field of view.
SoftwareSoftware used to process/create the photo prior to import into Lightroom.
Exposure
Exposure*Exposure summary (e.g. “1/60 sec at f/2.8”).
Total Exposure
(camera Ev)
Total camera exposure (Ev), derived from the shutter speed, aperture, and the ISO speed rating (but without any adjustment for Exposure added or removed in Lightroom). Gives a sense for how much light was available. Lower numbers mean less light.
Total Effective Exposure*
(effective camera Ev)
Total effective camera exposure (effective Ev), derived from the shutter speed, aperture, and the ISO speed rating, then adjusted to reflect any Exposure added or removed in Lightroom. Gives a sense for how much light was available. Lower numbers mean less light.
Shutter Speed*Shutter speed used to take the photo (e.g. “1/60 sec”).
Aperture*Aperture used to take the photo (e.g, “f/2.8”).
In-Camera Exposure Compensation*In-camera exposure bias/compensation (e.g. “-2/3 EV”).
FlashWhether the flash fired (“Did fire” or “Did not fire”).
Exposure ProgramExposure program (“Manual”, “Aperture priority”, “Landscape”, ...).
Metering ModeMetering mode (“Center-weighted average”, “Spot”, ...).
ISOISO Sensor-sensitivity speed rating (e.g. “100”).
Subject DistanceSubject distance (e.g. “1.92 m”); often wildly incorrect.
Size
Cropped?Has a crop been applied in Develop? (“Cropped” or “Not cropped”)
Crop Rotation*Amount of crop rotation applied in Develop, rounded to the nearest degree (e.g. “2° CCW”).
Crop Amount*Relative area of the image cropped away from the original, in percent. Larger numbers indicate images left with increasingly smaller areas compared to their original.
Megapixels (post-crop)Image size, after any Develop crop/rotation adjustments, in megapixels.
Megapixels (original)Original image size, prior to any Develop crop/rotation adjustments, in megapixels.
Megapixels (max available)Image size originally available, prior to any downsizing that might have happened prior to import into Lightroom, and prior to any cropping within Lightroom. This uses the IPTC “maxAvailWidth” and “maxAvailHeigh” fields if available (which is rare). If not available, this is the same as “Megapixels (original)”.
Width x Height (post-crop)Dimensions, after any Develop crop/rotation adjustments, in pixels and megapixels (e.g. “3208 x 4928 (16.0 MP)”)
Width x Height (original)Original dimensions, prior to any Develop crop/rotation adjustments, in pixels and megapixels (e.g. “3208 x 4928 (16.0 MP)”). Note: “Original” does take into account any “Rotate Left (CCW)” or “Rotate Right (CW)” applied to the photo; just not subtle rotation applied in the Develop Module
Long Edge (post-crop)Length of the long edge of the image, after any Develop crop/rotation adjustments, in pixels.
Long Edge (original)Length of the long edge of the original image, prior to any Develop crop/rotation adjustments, in pixels.
Short Edge (post-crop)Length of the short edge of the image, after any Develop crop/rotation adjustments, in pixels.
Short Edge (original)Length of the short edge of the original image, prior to any Develop crop/rotation adjustments, in pixels.
Width (post-crop)Width of the image, after any Develop crop/rotation adjustments, in pixels.
Width (original)Width of the original image, prior to any Develop crop/rotation adjustments, in pixels. Note: “Original” does take into account any “Rotate Left (CCW)” or “Rotate Right (CW)” applied to the photo; just not subtle rotation applied in the Develop Module
Height (post-crop)Height of the image, after any Develop crop/rotation adjustments, in pixels.
Height (original)Height of the original image, prior to any Develop crop/rotation adjustments, in pixels. Note: “Original” does take into account any “Rotate Left (CCW)” or “Rotate Right (CW)” applied to the photo; just not subtle rotation applied in the Develop Module
Aspect Ratio
(short:long, post-crop)
Aspect ratio of the image, after any Develop crop/rotation adjustments, without regard to image orientation (e.g. “2 : 3”)
Aspect Ratio
(short:long, original)
Aspect ratio of the original image, prior to any Develop crop/rotation adjustments, without regard to image orientation (e.g. “2 : 3”). Note: “Original” does take into account any “Rotate Left (CCW)” or “Rotate Right (CW)” applied to the photo; just not subtle rotation applied in the Develop Module
Aspect Ratio
(width:height, post-crop)
Aspect ratio of the image, after any Develop crop/rotation adjustments (e.g. “5 : 4”).
Aspect Ratio
(width:height, original)
Aspect ratio of the original image, prior to any Develop crop/rotation adjustments (e.g. “5 : 4”). Note: “Original” does take into account any “Rotate Left (CCW)” or “Rotate Right (CW)” applied to the photo; just not subtle rotation applied in the Develop Module
Aspect Ratio compared to...Post-crop aspect ratio compared to an aspect ratio you specify: “Same”, “Wider”, “Taller”. This can be useful if you need to do different processing/cropping/exporting based on how an image's aspect ratio best fits a specific display aspect ratio.
Orientation*
With Respect to Image Sensor
The image orientation with respect to a straight-from-the-sensor presentation, e.g. “rotated 90° clockwise” and “flipped vertically”. For many modern cameras with orientation sensors, Lightroom applies an orientation update automatically upon import; these automatic updates are not distinguishable from subsequent user-directed updates.
File size (bytes)File size of the master image or video, in bytes. Also reports total disk usage for selected items. Note that due to a Lightroom bug, the size for offline items is not shown correctly.
Cached-Preview Size (bytes)Size on disk of all the cached normal previews for the image. (Smart Previews are not included.)
Audio sidecar file*The kind, if any, of the audio sidecar file associated with the image
XMP sidecar file*Does the image have an associated XMP sidecar file?
JPEG sidecar file*Does the image have an associated JPEG sidecar file?
Video
Video Size and RateVideo frame dimension and rate (e.g. “1080 x 1920 (30)”)
Video Trim*Whether the video has had its start and/or end trimmed (“Trimmed at start and end”, “Trimmed at end only”, “Untrimmed”, ...).

Example responses include:

  • Not trimmed
  • Trimmed at start and end
  • Trimmed at start only
  • Trimmed at end only
  • Untrimmed
Video Length (Trimmed)Length of the video, after any trimming in Lightroom (e.g. “17 min”).
Video Length (original)Length of the original video, without regard to trimming in Lightroom (e.g. “22 min”).
Video Frame RateFrame rate for the video (“15.000 fps”, “29.989 fps”, ...)
Audio Sample Rate
(of a video)
Sample rate for the audio track of a video (e.g. “48000 Hz”).
Audio Channels
(of a video)
Number of audio tracks (“Mono”, “Stereo”, “5.1”, ...)
Video Pixel Aspect RatioAspect ratio of pixels encoded in a video (e.g. “1”, “1.3333”, ...)
Develop (except crop)
Develop Sections Disabled*List of disabled Develop-module sections (e.g. “Paint-Based Corrections and Lens Correction”).
Red-Eye Corrections*Count of red-eye corrections applied in Develop (e.g. “3 Pet Eyes”).
Clone/Heal Corrections*Count of clone/healing-healing corrections (spots and strokes) applied in Develop, e.g. “27 corrections (7 clone spots and 20 heal strokes)”.

Also reports the total number of corrections across all inspected images, and the median number of corrections among images with at least one correction.

Local Adjustment-*
Brush Corrections
Count of local adjust-brush spots and strokes applied in Develop.
Radial Filter*Count of radial-filter corrections applied in Develop.
Graduated Filter*Count of graduated-filter corrections applied in Develop.
White Balance*White-balance setting applied in Develop (“Daylight”, “Custom”, etc.). Also, notes which images have the same white-balance temperature and tint as the most-selected image.
Exposure Adjustment*
(in Lightroom, to the closest ⅓ stop)
Amount of overall exposure compensation applied in Develop, to the closest ⅓ stop.
Contrast*Amount of overall “Contrast” applied in Develop, rounded to the nearest +/- 5.
Highlights*Amount of overall “Highlights” applied in Develop, rounded to the nearest +/- 5.
Shadows*Amount of overall “Shadows” applied in Develop, rounded to the nearest +/- 5.
Whites*Amount of overall “Whites” applied in Develop, rounded to the nearest +/- 5.
Blacks*Amount of overall “Blacks” applied in Develop, rounded to the nearest +/- 5.
Clarity*Amount of overall “Clarity” applied in Develop, rounded to the nearest +/- 5.
Vibrance*Amount of overall “Vibrance” applied in Develop, rounded to the nearest +/- 5.
Saturation*Amount of overall “Saturation” applied in Develop, rounded to the nearest +/- 5.
Dehaze*Amount of overall “Dehaze” applied in Develop, rounded to the nearest +/- 5.
Color Treatment*Black & White vs. Color vs. Desaturated Color

Example responses include:

  • Black & White
  • Color (but fully desaturated)
  • Color (but extremely desaturated)
  • Color (but highly desaturated)
  • Color (but somewhat desaturated)
  • Color (but slightly desaturated)
  • Color
  • Color (super-saturated)
  • Color (hyper-saturated)
Tone Curve Name*Name of the tone curve applied in Develop (“Linear”, “Custom”, “Strong Contrast”, ...)
Split Toning*What split-toning edits have been applied (“Highlights and Shadows”, “Shadows Only”, ...)
Sharpening Amount*Amount of overall “Sharpening Amount” applied in Develop, rounded to the nearest 5.
Sharpening Detail*Amount of overall “Sharpening Detail” applied in Develop, rounded to the nearest 5.
Sharpening Masking*Amount of overall “Sharpening Masking” applied in Develop, rounded to the nearest 5.
Luminance Noise Reduction*Amount of overall “Luminance Noise Reduction” applied in Develop, rounded to the nearest 5.
Luminance Noise-Reduction Detail*Amount of overall “Luminance Noise-Reduction Detail” applied in Develop, rounded to the nearest 5.
Luminance Noise-Reduction Contrast*Amount of overall “Luminance Noise-Reduction Contrast” applied in Develop, rounded to the nearest 5.
Color Noise Reduction*Amount of overall “Color Noise Reduction” applied in Develop, rounded to the nearest 5.
Color Noise-Reduction Detail*Amount of overall “Color Noise-Reduction Detail” applied in Develop, rounded to the nearest 5.
Color Noise-Reduction Smoothness*Amount of overall “Color Noise-Reduction Smoothness” applied in Develop, rounded to the nearest 5.
Lens Corrections*List of Lens Corrections enabled in Develop (e.g. “Color defringe + Manual”).
Lens-Correction Profile Name*The name of the lens-correction profile applied
Chromatic-Aberration Removal*Indicates whether “Remove Chromatic Aberration” is enabled
Defringe Enabled*Indicates whether “Defringe” is enabled
Unconstrained Crop*Identifies photos with lens corrections that might expose canvas, but without “Constrain Crop” enabled.
Upright Lens Corrections*Status of the “Upright” Lens Correction in Develop (e.g. “Auto”, “Full”, “Off”, etc.)
Vignette*Amount of post-crop Vignette effect applied in Develop (e.g. “Slight white vignette”, “15 black vignette”, ...)'
Grain Amount*Amount of overall “Grain Amount” applied in Develop, rounded to the nearest 5.
Basic Tone/Presence Edits?*Reports whether an images has basic Tone changes (exposure, etc), Presence changes (saturation, etc.), both, or neither.
Process Version*Name of the Lightroom render engine applied in Develop (e.g. “Version 4 (2017), default from Lightroom 7)”).
Camera-Calibration Profile*Name of the camera-calibration profile applied in Develop (e.g. “Adobe Standard”).
Process Version + Camera-Calibration Profile*The combination of the process version and the camera-calibration profile.
Camera-Calibration Profile + Process Version*The combination of the camera-calibration profile and the process version.
Comparison with Most-Selected Image
Develop differs*
from most-selected image?
Experimental comparison of develop settings the “most-selected” image to each other selected image.

This is a very-experimental feature, and it may not be completely accurate; it may incorrectly cite a photo as having different develop settings when in fact those settings that differ play no part in the final rendition (for example, if the redeye data for the two photos differ, but redeye correction is also disabled for both photos, they may flag as “different”).

If no more than 50 images are found to be different, you can pop up a dialog that displays the raw differences. (More than about 50 taxes Lightroom's display infrastructure too much.) This entire feature is subject to radical change in future versions of the plugin.

Copyright StateCopyright state.
Artist / CreatorArtist's name.
Rights Usage TermsInstructions on how image can legally be used.
Copyright Info UrlCopyright info URL.
ProviderName of person who should be credited when image is published.
SourceOriginal owner of the copyright.
Creator Job TitleJob title of the person that created the image.
Creator AddressAddress for the person that created the image.
Creator CityCity for the person that created the image.
Creator State/ProvinceState or province for the person the created this image.
Creator Postal CodePostal code for the person that created the image.
Creator CountryCountry for the person that created the image.
Creator PhonePhone number for the person that created the image.
Creator EmailEmail address for the person that created the image.
Creator UrlWeb URL for the person that created the image.
PLUS Copyright Owner: NameEach “Name” associated with the PLUS Copyright Owner, as individual items.
PLUS Copyright Owner: IdentifierEach “Identifier” associated with the PLUS Copyright Owner, as individual items.
PLUS Image Creator: NameEach “Name” associated with the PLUS Image Creator, as individual items.
PLUS Image Creator: IdentifierEach “Identifier” associated with the PLUS Image Creator, as individual items.
PLUS Image Supplier: NameEach “Name” associated with the PLUS Image Supplier, as individual items.
PLUS Image Supplier: Identifierthis id within each “Image Supplier” record is not necessarily related to the flat “Supplier Image ID” text field
Supplier Image IDthis is a “flat” text field, not necessarily related each “Identifier” within the various “Image Supplier” records.
Misc PLUS (http://useplus.org/) and IPTC-Extension Items
PLUS Licensor: NameEach “Name” associated with the PLUS Licensor, as individual items.
PLUS Licensor: IdentifierEach “Identifier” associated with the PLUS Licensor, as individual items.
PLUS Licensor: URLEach “URL” associated with the PLUS Licensor, as individual items.
Image Registry Entry: Organization IDEach “Organization ID” associated with the Image Registry Entry, as individual items.
Image Registry Entry: Item IDEach “Item ID” associated with the Image Registry Entry, as individual items.
Artwork Shown: TitleEach “Title” associated with the Artwork Shown, as individual items.
Artwork Shown: CreatorEach “Creator” associated with the Artwork Shown, as individual items.
Artwork Shown: Inventory NumberEach “Inventory Number” associated with the Artwork Shown, as individual items.
Artwork Shown: Copyright NoticeEach “Copyright Notice” associated with the Artwork Shown, as individual items.
Artwork Shown: SourceEach “Source” associated with the Artwork Shown, as individual items.
Artwork Shown: Date CreatedEach “Date Created” associated with the Artwork Shown, as individual items.
Location
CityName of the city where image was taken.
StateName of the state where image was taken.
CountryName of the country where image was taken.
Country Code2 or 3 letter ISO 3166 Country Code of the country.
LocationDetails about a location where image was taken.
Geoencoded HemisphereGeoencoded hemispheres (e.g. “North/East”). This can also be used to answer simple “Geoencoded?” queries, and to find mis-encoded “0°N 0°E” entries.
Geoencoded Location*
Marked Private?
Is the geoencoded location marked a private? (“Private”, “Not Private”, or “Not Geoencoded”)
Geoencoded AltitudeGeoencoded altitude (e.g. “65 m”).
Image Direction (degrees)The compass angle in degrees that the camera faced when the photo was taken. (Lightroom CC/6 and later)
Image Direction (North, South, etc...)The direction (North, South, etc..) the camera faced when the photo was taken. (Lightroom CC/6 and later)
Location Shown: SublocationEach “Sublocation” associated with the Location Shown, as individual items.
Location Shown: CityEach “City” associated with the Location Shown, as individual items.
Location Shown: State / ProvinceEach “State / Province” associated with the Location Shown, as individual items.
Location Shown: CountryEach “Country” associated with the Location Shown, as individual items.
Location Shown: Country CodeEach “Country Code” associated with the Location Shown, as individual items.
Location Shown: World RegionEach “World Region” associated with the Location Shown, as individual items.
Location Created: SublocationEach “Sublocation” associated with the Location Created, as individual items.
Location Created: CityEach “City” associated with the Location Created, as individual items.
Location Created: State / ProvinceEach “State / Province” associated with the Location Created, as individual items.
Location Created: CountryEach “Country” associated with the Location Created, as individual items.
Location Created: Country CodeEach “Country Code” associated with the Location Created, as individual items.
Location Created: World RegionEach “World Region” associated with the Location Created, as individual items.
Other Text Fields
Title LengthReports whether “Title” is blank, starts or ends with spaces or had doubled spaces; otherwise reports the length.
Title Line CountReports the number of lines in “Title”.
Headline LengthReports whether “Headline” is blank, starts or ends with spaces or had doubled spaces; otherwise reports the length.
Headline Line CountReports the number of lines in “Headline”.
Caption LengthReports whether “Caption” is blank, starts or ends with spaces or had doubled spaces; otherwise reports the length.
Caption Line CountReports the number of lines in “Caption”.
SceneIPTC Scene.
EventNames or describes the specific event at which the photo was taken.
IPTC Subject CodeIPTC Subject.
IPTC Category
(deprecated field)
deprecated IPTC Category.
IPTC Other Categories
(deprecated field)
deprecated IPTC Other Categories.
Description WriterName of the person who wrote the description.
Intellectual GenreIntellectual genre.
Job IdentifierA number or identifier needed for workflow control or tracking.
InstructionsInformation about embargoes, or other restrictions not covered by the Rights Usage field.
Name of Org ShownName of the organization or company featured in this image.
Code of Org ShownCode from a controlled vocabulary for identifying the organization or company featured in this image.
Leading/Trailing Spaces
in a Text Field
Lists which text fields contain a leading and/or trailing space
Multiple Embedded Spaces
in a Text Field
Lists which text fields contain more than one embedded space in a row, “Like    This”
Modeling
Plus VersionThe version number of the PLUS standards in place at the time of the transaction.
Model AgeAge of human model(s) at the time this image was taken in a model released image.
Minor Model AgeAge of the youngest model pictured in the image, at the time that the image was made.
Model Release StatusSummarizes the availability and scope of model releases authorizing usage of the likenesses of persons appearing in the photo.
Model Release IDA PLUS-ID identifying each Model Release.
Additional Model InfoInformation about the ethnicity and other facets of model(s) in a model-released image.
Source TypeThe type of the source of this digital image, selected from a controlled vocabulary.
Property Release StatusInfo on the availability of property releases.
Property Release IDPLUS-ID identifying each Property Release.
Person Shown in ImageIPTC person-shown field.
Dates
Has “dateTimeOriginal” FieldA simple yes/no on whether the “dateTimeOriginal” field is present.
Has “dateTimeDigitized” FieldA simple yes/no on whether the “dateTimeDigitized” field is present.
Has “dateTime” FieldA simple yes/no on whether the “dateTime” field is present.
Has “dateCreated” FieldA simple yes/no on whether the “dateDreated” field is present.
Date fields agree?Reports on whether the “dateTimeOriginal”, “dateTimeDigitized”, and “dateTime” fields are the same

Example responses include:

  • All are empty
  • All are the same
  • They differ
By HourGroups images by the hour of the day in which they were taken.
By DateGroups photos by date they were taken on.
By Day of WeekGroups images by the day of the week that they were taken on.
By MonthGroups photos by the month they were taken in.
By Month and DateGroups photos by the month/date they were taken in.
Date/Time RangeIsolate photos taken within a specific range of dates, times, and/or week days. Useful for finding all photos taken during a particular season, for example.
Height of the SunHeight of the sun above (or below) the horizon when the photo was taken.

Requires photos to be geoencoded and have timestamps. Furthermore, all photos must either have a timezone marked via my Geoencoding-Support plugin, or be in the same timezone with other photos processed together (and have that timezone specified manually during the search).

The distance reported is the amount of space between the horizon and the closest edge of the sun (that is, if above the horizon, the distance from the horizon to the lower edge of the sun's disk). The result takes into account the atmospheric refraction of fair weather at 20°C.

The result is quite accurate if the photo time, timezone, and location are accurate, and you're at the same altitude as your horizon (such as when at a beach looking out over the ocean). If an altitude is registered for the photo, and it's over 4000m, the plugin assumes you're in a plane and that your horizon is at sea level.

Significant errors can appear if you're not at the same altitude as your horizon (such as on a high cliff over a beach looking out over the ocean). At about 300m above, your sun will just be touching the horizon while it will just be disappearing for someone on the beach.

Of course, all bets are off if there are things like mountains or buildings at your horizon.

Example responses include:

  • 70° above the horizon
  • 15° above the horizon
  • 6° above the horizon
  • touching the horizon
  • 4° below the horizon
Kind of Sunlight
(Twilight, Golden Hour, etc.)
Based on the angle of the sun above/below the horizon

Requires photos to be geoencoded and have timestamps. Furthermore, all photos must either have a timezone marked via my Geoencoding-Support plugin, or be in the same timezone with other photos processed together (and have that timezone specified manually during the search).

“Golden Hour” is when the sun is within 10° above the horizon.

Example responses include:

  • setting sun golden hour (sun 1°〜10° above horizon)
  • morning astronomical twilight (sun 18°〜12° below horizon)
  • at sunrise
Master Image File
Bit Depth / Color Mode***
of the master image file
The bit depth (per channel) and color mode (e.g. RGB vs. CMYK) of the master image.
Color Space***
of the master imgage file
Color space (e.g. sRGB, AdobeRGB) of the master image. Note that the color space for a raw file is specific to the camera make and model; raw files appear here as "unknown".
Special Access...
Speical: List Data Fields***Lists raw metadata field labels and values found in the most-selected master image file. This is useful to find appropriate field names for the “User-Specified Master-File Data Field” search item described immediately below.

With this special item, only one photo/video is processed, regardless of how many are selected. This is sort of a “raw” version of my Metadata Viewer plugin; this item is useful to find the exact master-file field label for use in the “User-Specified Master-File Data Field” search item described immediately below, while the Metadata-Viewer plugin is far superior for general “what metadata is in this master file?” browsing.

User-Specified Field***
of the master image file
Explore the specific master-file metadata field entered by the user.

You can enter any metadata field known to ExifTool; you can see the list of raw fields for a specific master file by selecting it and applying this plugin's “Special: List Master-File Data Fields” search item, described immediately above..

Token Template*Any text, including the template tokens that my plugins understand.
Other
Part of a high-speed burst sequence*Isolates photos taken as part of a high-speed burst. You can specify how many photos are required in any particular sequence to count (the default is 3), as well as the maximum time separating each shot of the sequence (the default is 0.5 seconds).
Random Distribution Into BucketsPhotos are divvied up randomly into buckets, which you can then save into collections. If you want, for example, to randomly isolate 5% of your photos, choose a bucket count of 20. Each resulting bucket should have about 5% of the selection; you can then save a bucket to its own collection.
EXPERIMENTAL DATABASE DIGGING
Count of History Steps (experimental)
Count of Image-Adjustment History Steps (experimental)
Count of Exports in History (experimental)
Count of Publishes in History (experimental)
Count of Print Operations in History (experimental)

Results Dialog

After the plugin does its work, it brings up a dialog to display the results, for example:

I've spent considerable energy on tailoring the presentation and default sort for each of the 251 criteria the plugin supports. In the Lens example seen here (which Adobe's Library Grid Filter does support, though not as well), I take care to sort the lenses by focal length, and to pretty up the presentation (e.g. 50 mm instead of 50.0 mm).

Some features of the results dialog:

  • Click on an isolate button to create a collection named for the criteria and result, populate it with the appropriate photos, and switch to it.

    Shift-Clicking on an isolate button creates a collection with the opposite set of photos, all photos except those that match the criteria.

  • Click on the Isolate All... button to create all the individual collections and dismiss the dialog.

  • Click on two or more checkboxes to enable an Isolate Combined Checked Items button that creates one special collection with all the photos of the checked rows.

  • Click on a column header to toggle the display sort.

  • Click on a photo- or video- count number to display some percentage information. In the example above, clicking on the 8,306 of the Voigtländer 125mm f/2.5 row reveals that 31.9% of the target photos were taken with that lens (because it's such an oh-so-sweet lens whose results I adore).

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 Lr6 to Lr7 (or the equivalent under the hood for the Lightroom Classic subscription) 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 )

20181030.161

In the items that report collection membership, add "publish now" buttons to collections that have unpublished changes.

In items that reference publish collections, be a bit smarter about whether to bother showing the name of the publish service; do so only when it's needed to differentiate among publish services.

Removed the "Number of Duplicate People in a Photo" item, since it didn't work reliabily.

20181015.160

Updates for Lr8 (Lightroom Classic CC Version 8).

Added the special PP() function to the {LUA} token.

Added hierarchical options to the Keywords token.

Try to work around a Lightroom bug related to photo timezones and how Lightroom handles accessing plugin data.

20181004.159

Upgraded to the embedded copy of ExifTool to version 11.01.

Added the 'nicknames' modifier to the {People} token.

Added the SST1, SST2, and SS3 tokens to the template tokens that the plugin understands.

20180906.158

Added some experimental items:

  • Count of History Steps (experimental)
  • Count of Exports in History (experimental)
  • Count of Publishes in History (experimental)
  • Count of Image-Adjustment History Steps (experimental)
  • Count of Print Operations in History (experimental)

These work by accessing the catalog database directly, and not through Lightroom, so they won't necessarily have access to recent (since Lightroom started) editing work, as Lightroom doesn't update the database file in realtime. It does update the database file at irregular intervals, so you might get the data, but for trustworthy results, restart Lightroom before running the query.

20180821.156

Worked around a Lightroom bug that had HEIC photos showed an empty "File Type".

Added the token.

Clicking on the version number in the Plugin Manager now copies version info to the clipboard

Updated the PublishCollectionName token to allow numeric arguments along the lines of the CollectionName token.

Added the folowing template tokens: {home}, {desktop}, {temp}, {pictures}, {documents}

Added the 'PCH' variable to the {LUA} tag.

Upgraded to the embedded copy of ExifTool to version 11.00.

20180420.155

Upgraded to the embedded copy of ExifTool to version 10.82.

Fixed a bug when 'Token Examples' invoked in certain situations.

Added a bunch of token filters: F2D F2S F2X B2D B2S B2X S2X A2D A2S A2X

20180121.154

Updated some Phase One data.

Updated the "35mm-equiv focal length" calculation to handle orientation changes more reasonably.

Added the "Focal Length Needed For Sensor Size" option.

20180117.153

Ampersands weren't displaying on Windows.

20180111.152

Added process-version + calibration profile combos.

20180108.151

Fixed a boo-boo in the prior updated.

20180107.150

Redid the keyword-related items to make clear the difference between directly-assigned keywords and the whole set of keywords that might be associated with an image (the latter including synonyms and parents).

Added some cameras to the crop-factor database.

20180102.149

Fixed the crop-factor data for the Canon 5D Mark IV.

20171229.148

Updates to the data templates that my plugins understand: updated the Keywords token, added CollectionNames and CollectionFullNames tokens, and added a bunch of stuff (KWf, CN, CFN, CNf, CFNf) to the {LUA} token.

20171019.147

Oops, more Lr7 stuff.

20171019.146

Updates for Lr7

Better handle some character-encoding issues related to template tokens.

Allow the "If Exists" feature of Templat Tokens to work with the PluginProperty token.

Update registration support to handle a stupid bug at PayPal that PayPal refuses to fix )-:

20170817.145

Added a bunch of cameras to the crop-factor database.

20170710.144

Fixed a bug introuded the other day in template tokens, related to Windows filenames.

20170621.143

Added some cameras to the crop-factor database

Added the "only if it has a value" feature to template tokens.

Updated the {FolderName} token to allow {FolderName=1} (rather than requiring the plus as in {FolderName=+1})

Added the "only if it has a value" feature to template tokens.

20170610.142

Added a bunch of search items related to PLUS and IPTC extensions: “Copyright Owner: Name”, “Copyright Owner: Identifier”, “Image Creator: Name”, “Image Creator: Identifier”, “Supplier Image ID”, “Image Supplier: Name”, “Image Supplier: Identifier”, “Licensor: Name”, “Licensor: Identifier”, “Licensor: URL”, “Image Registry Entry: Organization ID”, “Image Registry Entry: Item ID”, “Location Shown: Sublocation”, “Location Shown: City”, “Location Shown: State / Province”, “Location Shown: Country”, “Location Shown: Country Code”, “Location Shown: World Region”, “Location Created: Sublocation”, “Location Created: City”, “Location Created: State / Province”, “Location Created: Country”, “Location Created: Country Code”, “Location Created: World Region

Upgraded to the embedded copy of ExifTool to version 10.55.

Added the Newline template token, and enhanced the FolderName token

20170520.141 Added some Phase One cameras to the crop-factor database
20170509.140

Added the "Number of Duplicate People in a Photo" item.

Added operating-system items about a file (e.g. MacOS's color label) to the "User-Specified Master-File Data Field" item. Use the "Special: List Master-File Data Fields" item to see the list of fields for any one particular photo, then click on the field name there, to explore that field overall the selected photos. MacOS's color label is, for example, "File:MDItemUserTags".

20170424.139

Upgraded to the embedded copy of ExifTool to version 10.50.

20170330.138

A shift-click on the [isolate] button used to isolate photos not represented by the row, but it wasn't very discoverable, and didn't always work. Added a new [all but] button that addresses both issues.

20170315.137

A recent change caused items with blank/missing values not to be listed in the results.

Present blank/missing values (e.g. "no Title") more nicely.

20170309.136

Upgraded to the embedded copy of ExifTool to version 10.40.

Added the following tokens to the template tokens that my plugins understand: Artworks, ArtworkTitle, ArtworkCopyright, ArtworkSource, ArtworkCreator, ArtworkDateCreated, ArtworkInventoryNum

20170212.135

Added the "Image Representations" item, to list the kind of ways an image appears in the catalog (or is present but missing from the catalog. Master image files, JPEG sidecars, and virtual copies are considered.

For the "File Currently Available" item, distinguise between a master image file that's missing because the entire folder is missing (which may be because its disk is not attached), and a file that's missing in a folder that's not (e.g. the file has clearly been deleted).

Added "ISO8601Date" to the template tokens that my plugins understand.

20170123.134

Added the "Dehaze" item.

20170115.133

Added some Canon cameras to the crop-factor database.

20170104.132

Added the "Cropped-out-but-Exportable People" item. If a face has been cropped out from an image, that face keyword can still be included in exported copies.

20170102.131

Added the "Part of a high-speed burst sequence" item. Complimentary with the Bag-o-Goodies plugin's "Find Next Photo Group" feature.

20161128.130

Added support for Guided upright to the "Lens Corrections" and "Upright" items.

Added Weekday, Wday, weekday, and wday to the list of template tokens that my plugins understand.

Upgraded to the embedded copy of ExifTool to version 10.36.

20161023.129

Added the "Post-Crop Focal Length 35mm Equiv" item. How did I not have this before?

Fixed a bug with the keyword tables in the LUA token.

20160929.128 Added a "check all" box to the results page.
20160926.127 Ah, the law of unintended consequences..... fixed a bug that reduced the photos inspected during "another search" subsequent searches.
20160919.126

Added the "Token Template" item, whereby you can query via the template tokens that my plugins understand.

Upgraded to the embedded copy of ExifTool to version 10.26.

20160912.125

Added "By Month/Date" item.

"By Month" and "By Date of Week" items now take into account the timezone of the photo, if known (via my Geoencoding-support plugin).

Better support for network shares on Windows.

20160825.124

Added "Radial-Filter Corrections" and "Graduated-Filter Corrections", and updated "Red-Eye Corrections" to differentiate between people- and pet-eye corrections.

20160823.123

Text-length items like "Title Length" now report down to the exact character length, as opposed to being grouped into ranges.

20160706.122

Added the ability to choose the name for the base collection set the plugin uses.

Added the ability to revert the selection to the what you started with after having isolated some results to a collection.

20160628.121

Added various IPTC "Artwork Shown" items.

Upgraded to the embedded copy of ExifTool to version 10.20.

20160605.120

Added a bunch more Fujifilm cameras to the crop-factor database.

20160525.119

The "Cached-Preview Size (bytes)" item wasn't reporting preview totals.

20160506.118

Added the "Snapshot Names" item.

20160505.117

The "Creator Job Title" item didn't work; does now.

20160503.116

Added the ability to save summary data to a spreadsheet file.

20160309.115

Fixed a Date-Range bug.

Added some Sony/Casio cameras to the crop-factor database.

20160130.114

Try to avoid yet another place where Lightroom gets hung because it can't handle certain kinds of dialogs at the same time.

Upgraded to the embedded copy of ExifTool to version 10.10.

Added a bunch more Canon cameras to the crop-factor database

20160112.113

For collection-membership items, added the ability to limit the search to smart collection or non-smart collections only.

Added data to the crop-factor database on the original iPhone, and the HP PhotoSmart 618.

20160103.112

Added "Image Direction (North, South, .." criteria. Fixed a bug in the original "Image Direction" (added yesterday) so that 359.9° properly rounds to 0° instead of 360°.

20160102.111

Added the "Image Direction" criteria.

20151225.110

A shift-click on the "isolate" button now isolates all photo NOT having that row's value.

Added the 200th criteria, "Folder Hierarchy". Click on the "isolate" button in its result repliates the folder hierarchy as a hierarchy of collection sets and collections.

20151222.109

Enabled the ExifTool stuff to extract "Unknown" tags.

For the collection-membership items, show the "not in any collection" result row even if there are no photos in that row, to make it apparent that indeed all photos are in at least one of the other listed collections.

20151219.108

Added new search item, "Photo Merge Type", for quickly finding images created via Lightroom's "Photo > Photo Merge" tools.

20151218.107

Sigh, Canon continues to boggle the mind with their image metadata. It turns out that they released two cameras with the exact same Make/Model identifier, a decade apart. This update now differentiates them so that the 35mm-equivalent focal length can be calculated.

20151114.106

Added new search item "Specific Keyword", for finding photos that do/don't include a given keywords.

20151109.105

Added new search item "Random Distribution Into Buckets", for grabbing a random selection of photos.

20151024.104

Photos isolated to a collection are now sorted by the search term, when viewed with the "Custom Order" sort.

20151009.103

Upgraded to the embedded copy of ExifTool to version 10.00.

20150921.102 Added an old Kodak camera to the crop-factor database
20150728.101 Had the wrong data in the crop-factor database for the Fuji X100s. Fixed that, and added some other recent Fuji cameras.
20150705.100

The results column on Windows was sometimes too narrow. Had to make the result text unselectable to get around it.

20150626.99

Changed how develop-setting numbers are reported, now explicitly presenting the range of each slot.

Added new items: "Split Toning", "Sharpening Amount", "Sharpening Detail", "Sharpening Masking", "Color Noise Reduction", "Color Noise-Reduction Detail", "Color Noise-Reduction Smoothness".

Added an "Another Search" button to the results page.

20150622.98 Added a couple of Olympus cameras to the crop-factor database
20150618.97 Added Leica M type 240 to the crop-factor database
20150607.96

Added support for People (LrCC/6)

20150301.95

Make collection-names sort properly ("Hour of the Day", "Day of Week", and "Month" items).

Even if all photos have the same result, show the full-results dialog if data was collected for a spreadsheet report, so that the "save to file" button is available.

20150206.94

In the POODLE-vulnerability dialog, display a raw URL of a page on my site that discusses the issue, so that folks can be independently sure that the dialog is indeed from me and not malware.

20150131.93 Build update.
20150115.92

Updated the camera-name code to try to guess the actual camera model of Hasselblad H5D files, since in their infinite wisdom Hasselblad decided to encode three distinct models with the same internal code, making it impossible to know for sure what camera produced a given image file.

Same sleuthing for Hasselblad crop-factor calculations.

Added the "Megapixels (max available)" search item.

20141225.91

Added the Canon EOS 7D Mark II to the camera crop-factor database.

20141127.90

When applied to a collection, photos not in the collection could have been included in the search via the "items hidden within collapsed stacks" option.

The "Camera Name" items were missing a row for photos that had no camera make/model data.

Added new items to search by: "Cached-Preview Size (bytes)", "Local Adjustment-Brush Corrections", "Height of the Sun", and "Kind of Sunlight (Twilight, Golden Hour, etc.)"

For data that are simple numeric values (such as "length of short edge, in pixels"), when isolating photos to a collection, the collection may be created with a name that has some extra spaces at the beginning, in an attempt to get Lightroom to sort the list of collections reasonably.

Upgraded to the embedded copy of ExifTool to version 9.76.

20141104.89 For the "keyword count" items, added a summary note about the total number of distinct keywords seen for the inspected items.
20141104.88

Added a bunch of Canon cameras to the crop-factor database.

20141019.87 Windows Only: Add a one-time check for the POODLE security vulnerability, and alert the user if it exists.
20140928.86

Added various "collection membership" items.

Updated the various "Keywords (individually)" items to include a row for photos that have no keywords of the given type, if any.

20140913.85 Added Olympus E-M1 to the camera crop-factor database. (Why Olympus can't include the crop factor in the metadata like most everyone else is beyond me...)
20140902.84 New build system
20140820.83 Added new items for lens-correction profile name, chromatic aberration, and defringe.
20140805.82

Updated the "White Balance" item to note which images have the same white-balance temperature and tint as the most-selected photo.

The "Develop differs from most-selected image?" item had actually referred to the first image selected, not the "most-selected image". It now refers to the most-selected image, unless there isn't one, in which case it reverts to the first image.

20140801.81 Added new "Keywords, individually" items.
20140731.80 Registration fix for Lr5.6
20140730.79 Added "Video Size and Rate"
20140720.78

The “has ...” items for dates (for dateTimeOriginal, dateTimeDigitized, and dateTime) now actually work.

More Creative-Cloud support.

20140715.77

Fixed an issue with Creative-Cloud revalidation.

20140712.76

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

20140710.75 Sigh, had a bug in the Creative-Cloud support.
20140708.74

Now supports Lr5.5+ Creative-Cloud Installs.

20140706.73 Added some more keyword-related search items.
20140704.72 For some reason (bug in Lightroom?), Lightroom is not following the plugin's direction on how large to make the result dialog, so in an attempt to work around it, I've added a "debug options" link in the upper-right corner of the item-selection dialog.
20140701.71 Added some debug logging to track down a display-size issue.
20140630.70 Build-system update
20140629.69

Added "By Month" data item.

20140629.68

Added "By Date Taken" data item. The Library Grid Filter is probably better for browsing by date, but this might be useful if you want to automatically create collections based on the date.

Updated some of the other date-related items to try harder to find a date associated with the photo.

20140605.67

Upgraded to the embedded copy of ExifTool to version 9.60.

20140506.66 Added a new search criteria: file writeability (e.g. readonly or not)
20140422.65

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

20140418.64

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

20140330.63

Worked around a Lightroom bug that stopped the new "list master-file data fields" from displaying properly on Windows.

20140327.62

Added the “User-Specified Master-File Data Field” item, giving the plugin the ability to explore arbitrary master-file metadata.

Added the “Special: List Master-File Data Fields” item to allow you to quickly see the raw metadata field labels need for the “User-Specified Master-File Data Field” item.

Upgraded to the embedded copy of ExifTool to version 9.53.

20140311.60 Wow, I'd really screwed up the calculations for the “Total Exposure (camera Ev)” and “Total Effective Exposure (effective camera Ev)” items. In both cases I had the sense of adjustment for ISO speed backwards, and in the latter case I had the sense of adjustment for the Lightroom develop setting backwards, and in some cases could use the wrong number to begin with. Doh!
20140302.59 added the following items to the list of explorable items: amount of Contrast applied in Develop, amount of Highlights applied in Develop, amount of Whites applied in Develop, amount of Blacks applied in Develop, amount of Vibrance applied in Develop, amount of Saturation applied in Develop, and the IPTC “Person Shown in Image” field.
20140212.58 Updated the file-size counting done for “File size (bytes)” and “Smart-Preview Status” to better indicate the file-size status for offline files.
20140207.57

Added “Most-Recent Update Date” and “Number of Updates” items.

20140206.56

(Lr5.2+) Update the “Clone/Heal Corrections“ item to report the total number of corrections for the inspected photos, and to report the median number of corrections among photos with at least one correction.

20140124.55

Added more detail to the disk-usage summary presented for the “File size” and “Smart-Preview Status” items. Fixed a bug in how previews for videos are reported.

Cite in the result-dialog title the number of items inspected.

20140120.54

Result dialog for the “File Size” item could end up too big for the screen.

Upgraded to the embedded copy of ExifTool to version 9.46.

20140104.53 Updated a bug with “Cropped Amount”, and renamed its "100%" result with "Almost Completely Cropped Away".
20131230.52 Updated the “File Currently Available” item to report whether a Smart Preview exists.
20131128.51 Updated how megapixels, video duration, and focal length are displayed, to avoid apparent duplicates (such dual "20.0" and "20" results).
20131125.50 Made the “Exposure Adjustment” results look nicer, and made it clear that results are displayed to the nearest ⅓ stop.
20131124.49 Added “Flag Status” item
20131122.48 Fixed error with “Exposure Adjustment” item.
20131115.47

Fixed a bug in the "File Size" stuff added yesterday.

20131114.46

Discovered that at some point Lightroom developed a bug that makes reporting the byte size of offline images impossible. The plugin report now notices when this happens and points out that the data is not to be trusted.

Added an extra report to the "File Size" item to show the disk space used by all the selected items (the masters, smart previews, and normal previews). However, it currently doesn't work correctly for offline images due to the Lightroom bug cited above.

20131102.45

Update for OS X Mavricks.

Updated the Image::ExifTool library to version 9.39.

20131014.44 Found that with certain settings some math errors would pop up.
20131010.43

Update how the aspect-ratio criterion are computed. Should give more reasonable results.

Updated the Image::ExifTool library to version 9.38.

20131003.42

Added new criteria: "Leading/Trailing Spaces in Text Field" and "Multiple Embedded Spaces in Text Field".

You can now tell which results you've isolated... the "isolate" button becomes "view" once the associated collection has been created.

20130930.41

Added "Unconstrained Crop" criteria.

Fixed a bug with the "Lens Corrections" item, which always indicated that "Chromatic Aberration" and "Constrain Crop" were set for an image regardless of whether they were.

More attention to the default display order of some results.

20130926.40

Added new criteria: "By Weekday", "By Hour", and "Date/Time Range".

An update to track a change in Lightroom 5.2 in how develop clone/heal spots and strokes are encoded.

Made it much easier to see relative percentages in the results... just click on any total and all totals are replaced with percentages.

20130925.39 Updated the camera crop factor database.
20130911.38 The "Total Effective Exposure (effective camera Ev)" criteria couldn't be selected.
20130910.37 Added a bunch of cameras to the crop-factor database.
20130910.36

Added a new criteria, “Aspect Ratio: compared to...”.

Renamed “File Extension” and “File Extension (case-insensitive)” to “File Extension (case-sensitive)” and “File Extension” respectfully, and swapped their order in the list, because Lightroom generally runs on case-insensitive file systems, so case insensitive is the norm, and case sensitive the oddball.

Gave the spell-checker a much needed run.

20130908.35 The “File Currently Available?” item relied on a component of Lightroom's internals that seems to be buggy, so I rewrote it to check the disk directly for the presence of the master image file.
20130830.34 Added a few more cameras to the crop-factor database.
20130828.33

Added new exploring criteria “Has plugin custom metadata?”. If you generate the spreadsheet-data file, it'll include the list of IDs for the plugins involved.

Changed the label “Spot-Healing Corrections” to “Clone/Heal Corrections” and updated it to include clone/heal strokes as well as spots, producing results along the lines of "“11 corrections (2 clone spots, 2 heal spots, 3 clone strokes, and 4 heal strokes)”.

Updated the list of develop changes (as generated by th “Develop differs from most-selected image?” criteria) to include more detail about clone/healing strokes and spots. Also, removed “Orientation” from consideration as a develop change, to match that develop-settings copy/paste doesn't include the orientation. You can deal with orientation via the newly-added the “Orientation With Respect to Image Sensor” criteria.

20130828.32

Added the ability to compare develop settings against the most-selected image. It's a work in progress. See documentation for “Develop differs from most-selected image?” above.

20130826.31 Some fixes to the previous changes for Windows.
20130826.30

Added several new search criteria: “File Extension (case insensitive)”, “Lens Description (built from master-file data)”, “Bit Depth and Color Mode”, “Color Space”,

Made searching large numbers of images a bit more efficient, and allow the searches to be canceled midway.

In the criteria-picker dialog, added a direct link to the full criteria list.

20130723.29

Added the ability to save the raw data to a TSV (tab-separated values) file.

20130721.28 Added Canon 650D to the camera sensor-crop database
20130629.27 In some rare cases photos with a Process Version of 2003 would show up as "Unknown".
20130626.26 Added a bunch of data to the crop-factor database
20130620.25 Updated the "Color Treatment" item to partition color photos based on their amount of saturation/desaturation.
20130613.24 Better support for plugin revalidation.
20130611.23 Yet another Lr5 update
20130610.22

Updated the "Lens Corrections" item for Lr5, and added a new "Lens Corrections (Upright only)" item.

Added an item related to whether smart previews exist.

Added a bunch of new crop-factor data, and corrected the crop-factor data for the Canon Powershot G1 X.

(Note: Lr5 painted heal/clone brush strokes are not yet taken into account.)

20130501.20 Update for Lr5
20130420.19

Added "Folder Name" and "Path Name" to the list of search items.

20130415.18

Added the “Has Basic Tone/Presence Edits” search item.

Fixed the “dateCreated” search.

20130412.17 Build system update.
20130330.16 Added some Ricoh cameras to the crop-factor database.
20130328.15 Fix for the registration system.
20130311.14

Added "Total Exposure (Ev) and Total Effective Exposure (effective Ev).

Filled in some areas where the docs were not yet written.

20130219.13 Added some notes to the aspect-ratio results to denote common aspect ratios (e.g. 16:10 is a wide-screen monitor)
20130218.12 Added some extra text fields (title, caption, etc.)
20130214.11

Added the ability to identify images with sidecar files.

In the criteria-selection dialog, warning messages would sometimes get truncated.

20130212.10 Added some date fields
20130209.9 More build-system maintenance
20130206.8 Tweak for my registration system
20130124.6 Added a bunch of Canon cameras to the crop-factor database.
20130119.5

Computation for the megapixel notation for "Width x Height (post-crop)" was wrong.

Many of the pixel-size items crashed when used on videos.

20130111.4

Focal-Length 35mm crashed if a photo didn't have focal-length data.

Added a bit of buffer to the dialog-height calculations to help ensure that the dialog doesn't grow taller than the screen.

20121113.3 Made "Dimensions" available for video.
20121020.2 Added "Lens Corrections"
20121019.1 Initial public release.

The 30 most-recent comments (out of 112; see all), most recent last...

I would like to complement my previous message, since I can’t edit it. It would be great to have a feature of negating the criteria, like the NOT part of collection Wedding example, NOT a specific keyword, etc..

Thanks

It used to be (until the version I just pushed out) that you could shift-click on the [isolate] button to isolate items NOT represented by the row. It wasn’t very discoverable, as evidenced by me having forgotten about it until I’d almost finished implementing something similar. I made it into its own button in the new version, so this should address your needs. —Jeffrey

— comment by Carlos Viana on March 29th, 2017 at 6:21pm JST (1 year, 9 months ago) comment permalink

Thank you! That’s precisely what I needed

— comment by Carlos Viana on March 30th, 2017 at 9:31pm JST (1 year, 9 months ago) comment permalink

Hi Jeffrey
I just started using the “Image Supplier” compound metadata field. While the documentation is a little unclear, I *think* one role for this field is to record where you found the image. (E.g. Image Supplier: “Flickr”, Image Supplier Image ID: “www.flickr.com/…”). The only problem is that it is impossible to search these fields, which will be important as I catalog more images from the web.

Any possibility of adding these fields to Data Explorer?

Thanks
Alan in Oakland, CA

Oops, I added these back in June but neglected to update this comment until now (Oct 2017), sorry. —Jeffrey

— comment by Alan Harper on April 18th, 2017 at 1:18am JST (1 year, 8 months ago) comment permalink

Is there any possiblity that you could include macOS Finder tags as a criteria? I have been recompressing thousands of images using JPEGmini and keeping track of the progress by changing the Finder tags from “Source” to “Mini”, but there is no way for me to see that info inside Lightroom. I’d love to use Data Explorer to create a collection for me and then I could just add a Processed keyword to that set. Thanks for considering my request and all the exceptional work you’ve done. Im writing from Wake Forest, NC, USA, BTW.

Check out this update that I just released. —Jeffrey

— comment by Shannon Settles on May 6th, 2017 at 6:01am JST (1 year, 7 months ago) comment permalink

Hey Jeffrey! This plugin is priceless! I am still using the trial and would be sure to make a purchase. It’s already saved me but now looking for another report which is to report by filenames. i.e. custom name, original file name etc. Unless it’s already there?

I don’t think it’s possible… the plugin has access only to the current filename; there’s no history of what names the file might have had in the past. Sorry. —Jeffrey

— comment by Jerry Syder on May 11th, 2017 at 12:15am JST (1 year, 7 months ago) comment permalink

Hi, and first of all thanks for a great plugin, along with all the other great plugins you have made!

I have made a Pivot table in Excel to combine data extracted via your Data Explorer into statistics for my photos, e.g. for comparisons such as “how many >2 star rated photos have been taken with which lens and which camera at f/2.0 the last year”… However, to do so, I have to (as far as I know) extract one metadata search at a time, click Save to tab-separated-values file per-image data and repeat for all metadata fields I want to extract.

Is it possible, or would it be possible to implement, extraction of multiple metadata columns at one time? The selection of which metadata to extract could for instance be done by a check list, and the export columns then look something like:

Full Path UUID Filename Copy Name Camera Make Lens Aperture By Date Rating

Thanks

That’s more than what my plugin is designed for, but perhaps the Lr/Transporter plugin does exactly what you want. —Jeffrey

— comment by Morten Lien on May 12th, 2017 at 3:08am JST (1 year, 7 months ago) comment permalink

To further expound on my last comment, I have since discovered that JPEGmini flags files it has already processed using the File Comment tag, which I can see using your Online EXIF Viewer, but cannot seem to use as a search criteria here in Data Explorer. Am I missing how to use it, or is this a feature request? Thanks in advance.

I’d expect the JPEG file comment to be newly available via the same update that gave access to the Finder color label. Are you sure it’s not? —Jeffrey

— comment by Shannon Settles on May 13th, 2017 at 2:37am JST (1 year, 7 months ago) comment permalink

It is! Thank you. I didn’t understand the usage of the “List Data Fields” two-step process.

— comment by Shannon Settles on May 13th, 2017 at 9:24pm JST (1 year, 7 months ago) comment permalink

Jeffrey – Hi from the UK.

If I use LR Mobile and make a collection “public” then anyone I share the link with can add comments or likes to the images which sync back to the desktop and appear in the Comments panel of the library module.

Are those Comments and Likes fields accessible to plugins? If so, could I request you add them to the Data Explorer plugin please? If would be really helpful for me to have “Has Comments” and “Has Likes” isolated into collections.

Thanks for a great plugin.

Unfortunately, Lightroom gives plugins no access to this data at all. The data doesn’t seem to be even kept in the catalog. )-: —Jeffrey

— comment by Roger on June 5th, 2017 at 3:57am JST (1 year, 6 months ago) comment permalink

Jeffrey wrote, “Unfortunately, Lightroom gives plugins no access to this data at all. The data doesn’t seem to be even kept in the catalog.”

Synced LR Mobile comments and likes are kept in a separate database in AppData/Local/Adobe/Lightroom/Caches/Sync Data/Sync.lrdata (Windows) or Library/Caches/Adobe/Lightroom/Sync Data/Sync.lrdata (Mac) in the user’s home directory. I don’t have a good understanding of why they would be kept here rather than in the catalog (as compared to publish-service comments, which are in the catalog).

My Any Comment plugin goes to some lengths to extract both LR Mobile and publish-service comments/likes and make them accessible via custom metadata fields.

— comment by John R. Ellis on July 11th, 2017 at 11:44pm JST (1 year, 5 months ago) comment permalink

The isolate button is not working when I have a large number of values. I am trying to isolate on the field “Creator url” and when I have a small number of photos, it works great. But when I do it for a large number (2,000+) the isolate button doesn’t show up for any rows. The “isolate each” button does show up, and it solves my problem.

I suspect that this is a bug in Lightroom that you can’t control. But if you want more information, drop me a line.

I think you’re right about it being a Lightroom bug. It degrades ungracefully when a dialog has “too many” (whatever that means) elements. )-: —Jeffrey

— comment by Alan Harper on July 27th, 2017 at 6:06am JST (1 year, 5 months ago) comment permalink

Hi , I’m Fabrizia from Italy

Jeffrey, thank’s so much !

Ciao !

— comment by Fabrizia on October 2nd, 2017 at 2:36am JST (1 year, 3 months ago) comment permalink

Hi Jeffrey,

I’ve read all the criteria, but I still can’t find what I’m looking for – I hope I didn’t just overlook it! I was hoping to search for images that have been exported, e.g. all images I exported yesterday. Is that possible with this plugin (or any of the others)?
Thanks, Kat

No, sorry, not possible… that data is not made available to plugins. It’s possible that one could create a plugin that provides a section of the Export/Publish dialog and remembers, itself, the most recent export date. If it’s really really important to you to have this functionality, you could perhaps make (or have made) such a plugin. —Jeffrey

— comment by Kat on October 26th, 2017 at 10:03pm JST (1 year, 2 months ago) comment permalink

Hi Jeffrey,
My issue may be related to Alan’s, above, but manifesting differently. I’m using “length of long edge (original),” photos only. When I try to run it on the entire catalog of approx 60,000 images, the entire bottom of the window is blank, where usually it’s showing options and the dismiss dialog button. Unlike Alan, I maintain the isolate and all but buttons at each row.
I haven’t yet found the upper limit. It does still work with 12,538 images.
*Edited to add: That was on the last version of LR. I’ve now updated to the Lightroom Classic, and trying to do the entire library hangs the application. Smaller chunks appear to work fine.

These kind or problems sound like they’re related to the display mechanics of Lightroom and the operating system…. Lightroom or the OS just can’t handle such large dialog data, and at some point unknown to the plugin it runs into trouble. It’s not related to the number of images directly, but instead the number of rows in the final dialog (that is, the number of unique results of whatever is being searched for). The plugin can’t detect when this flakiness will start; I don’t think there’s anything I can do about it )-: —Jeffrey

— comment by Angela on January 3rd, 2018 at 8:00am JST (11 months, 16 days ago) comment permalink

“It’s not related to the number of images directly, but instead the number of rows in the final dialog”

This is caused by Adobe cutting corners on the Windows implementation of the LR user-interface controls. It’s the same reason that the Keyword List panel fails ungracefully with more than about 1500 keywords (ditto for other panels, such as the Folders panel). See here for more details: https://feedback.photoshop.com/photoshop_family/topics/bug-that-causes-collections-and-publish-services-to-disappear?topic-reply-list%5Bsettings%5D%5Bfilter_by%5D=all&topic-reply-list%5Bsettings%5D%5Breply_id%5D=19142555#reply_19142555

— comment by John R. Ellis on January 4th, 2018 at 3:53am JST (11 months, 15 days ago) comment permalink

Just downloaded, data Explorer plug-in to try. So far it looks excellent. One minor issue in the results panel. I had a few cases where the State was shown as “Tyne and Wear” and some where it was shown as “Tyne & Wear”.

The plug-in correctly identified them as different values, but showed the latter case in the results panel as “Tyne Wear”.

On checking I found that all cases where a “&” was used in Lightroom was displayed as a blank space.

I use UK English as the one and only language on my PC

Oops, thanks, it turns out to be an issue only on Windows, which is why I hadn’t noticed. I’ve just pushed a fix. Thanks for the report. —Jeffrey

— comment by Colin McDonald on January 13th, 2018 at 10:09pm JST (11 months, 5 days ago) comment permalink

Is there a method to extract the Collection Name somehow? I would then back-load it as other metadata.
I see that the Data-Explored can find the photo´s Collection, so this already is a good step. But can these Collection names then somehow be extracted?

Unfortunately, I don’t see an easy way. It’s a bit kludgy, but you can export the data as a CVS file, then use the Lr/Transporter plugin to bring the data back into a metadata field. —Jeffrey

— comment by Joachim Strobel on January 15th, 2018 at 4:15am JST (11 months, 4 days ago) comment permalink

London, UK

I have just installed this and have been trying to count the number of keywords in specific images. If I select, say, 2 images, I get the results for the 2 images, as one would expect. If, however, I select only 1 image, the results given are for the entirety of the images in the folder, which does not give the information I am looking for.

Is it possible to count keywords from a single selected image only? Maybe I am missing something, but I have not found a way to do this yet. Lightroom’s tool tip count in the Enter Keywords field is useless if you want to know the number of keywords which will export, allowing both for synonyms, parents and for some keywords possibly being non-exporting. Essentially I am hoping to find a way achieve a more useful per image keyword count for specific single images.

Thank you.

Your use case makes perfect sense, but it’s not the common way people invoke Data Explorer. If I allowed the plugin to work with just one photo, then folks who wanted to run it on the entire set would have to first deselect everything (losing their place in the set of photos). This change would hurt more people than it helps, I think, sorry. For your needs, you can just select two photos and run it, or perhaps use the Quick Collection…. there are keyboard shortcuts to put the current photo into the quick collection, and to toggle to/from the quick collection; using these, you can throw the photo there, invoke Data Explorer on it (and only it, assuming the quick collection had been empty), toggle back to your set of photos and remove it from the quick collection. Once you know the keyboard shortcuts, you can do this very quickly… much more quickly than it takes to read about it. —Jeffrey

— comment by Graham on January 18th, 2018 at 9:17am JST (11 months ago) comment permalink

Hi Jeffrey,

I’m writing from the Wood County in Austria. I’m using your plugins a lot, namely jf Metadata Presets and jf Metadata Wrangler and also jf Data Explorer. I’m glad to have them. Thank you for your work!

Would it be possible to get this criteria list of Data Explorer as nice PDF to print it?

Kind regards
Subhash

I’m not sure how to automate that, sorry. On MacOS, you can print this web page to a PDF…. —Jeffrey

— comment by Subhash on February 22nd, 2018 at 12:47am JST (9 months, 25 days ago) comment permalink

I’m trying to find a way to search for photos that were published (for instance to zenfolio using our other plugin). I can see the metadata on each the photo with the information. Is there a way to use metadata as search criteria? cheers

For that, you can create Smart Collections that identify such photos, or use the Library Grid Filter. You can also use Data Explorer, using the pawel on February 25th, 2018 at 6:02pm JST (9 months, 21 days ago) comment permalink

Just registered today, and used one of the keyword options to create individual collections. I have one Keyword “B&”W”. This is output as B&&W in the collection created for it.

I’m on PC

That’s unexpected… could you send a plugin log after the collection is created? Thanks. —Jeffrey

— comment by Colin McDonald on March 7th, 2018 at 6:32pm JST (9 months, 11 days ago) comment permalink

A minor problem with the plug-in.

When I do a back-up (every time I exit), I get a dialog box headed “Jeffrey’s Data Explorer” which says “attempt to call a nil value”.

I am obviously concerned as to whether this affects the back-up in any way as this would be a potential disaster.

This won’t have any effect on the backup, but I’d like to know what’s causing it. Since the error pops up during shutdown, you can’t use the normal method to send the plugin log; could you zip up the log and email it? Thanks. —Jeffrey

— comment by Colin McDonald on March 8th, 2018 at 5:22am JST (9 months, 11 days ago) comment permalink

Hi there, not sure if im doing something wrong, but when i do a dataexplore on focal length, i get a result set longer than a page. Although you can scroll within the result set, the page itself is bigger than the screen, so you cannot click (or see) any of the dialog button choices at the bottom like “isolate all”. You can only hit enter which triggers the default ‘dismiss’; dialog.

You cant drag the window with a mouse (the top of the window muct always be visible on screen!). You can move the window with the keyboard so you can see the lower dialog buttons, but as soon as you move your mouse to click on them the window reverts to the top!

am i doing something wrong?!

thanks

It’s not your fault. Lightroom gives a plugin woefully little control over a dialog’s size; the best a plugin can do is try to guess how big a dialog will become, reducing the amount shown to hopefully keep it small enough to fit on the screen. But with all kinds of “retina” displays these days, it’s more and more difficult to make an intelligent guess. In your case, the guess fails. Perhaps send a plugin log and I’ll try to tweak the heuristics. —Jeffrey

— comment by Stewart on March 21st, 2018 at 6:12am JST (8 months, 29 days ago) comment permalink

Re the too-large window, the root cause of this is a bug in Windows LrSystemInfo.displayInfo(). LrView uses units of scaled pixels, while LrSystemInfo incorreclty returns physical pixels. (On Mac, both LrView and LrSystemInfo use scaled pixels.)

See here for details:
https://feedback.photoshop.com/photoshop_family/topics/lightroom-lrsysteminfo-displayinfo-returns-wrong-units-of-pixels-on-windows
Please add your constructive opinion and your me-too vote to that bug report.

— comment by John R. Ellis on March 28th, 2018 at 2:50pm JST (8 months, 22 days ago) comment permalink

hi! i’m looking for a filter that can monitor my search activities like popular searches. What keyword searches were typed and how many times the keyword was inputted. I’m managing more than 100k photos and 2 catalogs. The photo database is being accessed by more than 10 staffs, and I want to have a report on the keyword searches. Thank you.

Sorry, but I don’t think Lightroom logs that at all. It just performs the search and that’s that. —Jeffrey

— comment by Carlo Dacumos on July 24th, 2018 at 5:33pm JST (4 months, 26 days ago) comment permalink

Hi

Love your plugins – shame about the Facebook issue – that was one of my most used.

This plugin would be of significant use to me if there was a way of not only grouping by some attribute (eg folder, lens), but also giving some data fields (eg count of blue labels, average rating). In theory it should be possible to give several different values, so long as they are all aggregate values (cont, max, min, ave, etc), altho “First” can also be very useful.

Is this possible? Or could it be done?
or can you suggest some alternative (I have done it with MS Access connecting and pivoting against my catalogue, but built in would be so much nicer)

I’m not quite sure what you’re asking for, in a concrete sense, but it sounds like it’s beyond the scope of what this plugin is intended for. —Jeffrey

— comment by Anonymous on August 13th, 2018 at 7:20am JST (4 months, 6 days ago) comment permalink

Writing from Silicon Valley, CA. Your Data Explorer plugin (latest version 20180420.155) lists the newly-supported file type “HEIC” as “(blank)”.

Oops, indeed it does. Turns out to be a bug in Lightroom. I’ve reported it, and put out a new version of the plugin that works around it. —Jeffrey

— comment by Marc Sinykin on August 19th, 2018 at 7:38am JST (4 months ago) comment permalink

Hello Jeffrey
England

I’m trying to find images that do or do not have more than one entry in the develop history.
I have tried number of edits, but it is so erratic as to be useless, essentially identical images (ie exact same develop history) have different results.
All I want is to find images that have exactly one develop history (that will be the import + any develop preset) or more than one (though a count would be nice to have). Clearly LR ‘knows’, because it can list the develop history in order.

Is this a current search criteria that I can’t find for looking, or is a possible enhancement?

TIA

Your query prompted me to work on something that had been in the back of my mind, a way to access some of the database stuff “out from under” Lightroom. I’ve given it a first shot with these experimental develop-history items in my Data Explorer plugin. I’ve not been able to test on Windows yet, but I think they’ll work. If not, please send a plugin log. —Jeffrey

— comment by Jon on September 6th, 2018 at 6:22am JST (3 months, 13 days ago) comment permalink

I just updated 5 plugins for LR8. FYI, the minimum Paypal donation is $1.00. I am not complaining – I use your plugins all of the time. I thought you might want to update to registration instructions to reflect this.

It’s already mentioned there, just above to two big red buttons. I’ve no idea why PayPal forces a higher minimum onto some folks, but judging from the flood of 1-cent registrations I see after the Lr8 upgrade, they’re not doing it for most people. Instructions show how to get around it if you’re hit by it…. —Jeffrey

— comment by Marc Sontag on October 15th, 2018 at 11:28pm JST (2 months, 3 days ago) comment permalink

After “developing” a potentially large number of images (typically in a folder structure) and which are in any number of different collections which are in turn referenced by Collection Published, I’ve been looking for a way to identify which collections (or collection sets) within the publish service have images which need to be (re)published. At least Data Explorer allows me to see all the publish collections that MAY contain images which need to be (re)published, but it still take quite a bit of time to look at them all. (re)Publishing all services is not an option due to the time it takes. Can you see any way to help me with this? I was thinking that an extra column in the Data Explorer .txt file showing the number of images to be (re)published, or even just an indicator if one or more images need to be (re)published would do the job, but happy for any solution. Many thanks.

I just pushed out a new version that includes a “publish now” button for collections that are in need of being published. —Jeffrey

— comment by Howard on October 28th, 2018 at 8:13am JST (1 month, 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.


You can use basic HTML; be sure to close tags properly.

Subscribe without commenting