Setting Default Value of Custom Metadata for Virtual Copy
currently there no way set default value of custom metadata virtual copy... current behavior custom metadata copy values of mastercopy. not desirable since custom metadata place plug-in developers implement logic control of plugin workflow. jerry friedl flickr plugin suffer same problem. when photo been published there no way republished copy different develop setting because flickr id transfer custom metadata master copy.. recommend implement like
{
id = 'stock_photoid',
title = loc "$$$/stock/custommetadata/stockphotoid=stock photoid",
datatype = 'string',
readonly = true,
searchable = true,
browsable = true,
defaultvalue = "0" -- initial value new virtual copy
version = 2,
},
{
id = 'project',
title = loc "$$$/stock/custommetadata/stockphotoid=stock photoid",
datatype = 'string',
readonly = true,
searchable = true,
browsable = true,
defaultvalue = master.dafaultvalue -- same project same value
version = 2,
},
{
id = 'published',
title = loc "$$$/stock/custommetadata/published=published",
datatype = 'enum',
readonly = true,
searchable = true,
browsable = true,
defaultvalue = false -- control publish plugin.. if false publish else don't publish
version = 2,
},
i have not dig plugin development far can see bad design consideration...
i feeling virtual copies came along after basic design had been settled - seems add-on.
i think better if there no distinction between virtual copies , other copies.
in other words, photos in catalog should bunch of database settings , stuff, , "pointer"(reference) raw file upon based.
that way quit worrying kind of copy photo is.
rob
More discussions in Lightroom Feature Requests
adobe
Comments
Post a Comment