Skip to main content
R
remov_b4_flight
Known Participant
July 10, 2010
Open for Voting

P: Please add Plug-in metadata type for number

  • July 10, 2010
  • 2 replies
  • 399 views

Please add Plug-in metadata type for 'number' and

Add smart collection search definition for 'gerater than' , 'less than' to Custon metadata.

 

I 'm Making Image evaluation app externallly by launching for LrTask,

Returning results as Plug-in metadata. but 'string' and 'enum' type not have compare functionality.

(only exists/not exist, empty/isn's empty)

 

2 replies

johnrellis
johnrellis
Legend
May 4, 2024

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]

 

I agree, it's a basic missing feature from the SDK. Developers have asked for this since LR 3:

https://community.adobe.com/t5/lightroom-classic-discussions/feature-request-custom-metadata-type-number/m-p/2765756

 

The Any Filter plugin lets you search individual plugin custom metadata fields and do numeric comparisons on string-valued fields, e.g.

 

areohbee
areohbee
Legend
July 10, 2010

As it stands, custom metadata can be string, enum, or url, which precludes the ability to define numeric metadata that could be used to create a smart collection where the number falls in a particular range, or is greater than...

And while you're at it, how about adding the 'date' type as well, and maybe toss in 'boolean' - then custom metadata would be afforded the same status as regular metadata in collection criteria.

Rob

areohbee
areohbee
Legend
July 12, 2010

This is a biggie for me - please Adobe - SDK3.1?

This is a biggie for me - please Adobe - SDK3.1?

This is a biggie for me - please Adobe - SDK3.1?

(and Im sure not just for me)

The problem is that numeric metadata can't be treated numerically for the purpose of collections - big bummer for plugins like my develop settings metadata plugin, since you can't define a collection like:

ISO > 1600 and Lum. NR < 10... or sharpening > 60...

In fact, when dataType is absent, any field value type is accepted, however it looks like its being handled as a string in the collection edit form, but it will never match anything! So, you pretty much have to have dataType = 'string' (if not enum or url) if searchable, otherwise the user will think its broken since things that appear to match, don't match...

Rob

areohbee
areohbee
Legend
July 26, 2010

Where's Chet Drarvik? - Any comment??...

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices