Adobe 65007312 Programming Guide - Page 72

The user-visible custom fields from plug-ins are shown after all of

Page 72 highlights

CHAPTER 4: Working with Metadata Adding custom metadata 72 title = LOC "$$$/Sample/Fields/ModelRelease/NotSure=Not Sure", }, { value = 'yes', title = LOC "$$$/Sample/Fields/ModelRelease/Yes=Yes", }, { value = 'no', title = LOC "$$$/Sample/Fields/ModelRelease/No=No", }, -- optional: allowPluginToSetOtherValues = true, }, }, }, schemaVersion = 1, -- must be a number, preferably a positive integer updateFromEarlierSchemaVersion = function( catalog, previousSchemaVersion, progressScope ) -- When the plug-in is first installed, previousSchemaVersion is nil. -- As of Lightroom version 3.0, a progress-scope variable is available; you can -- use it to signal progress for your upgrader function. -- Note: This function is called from within a catalog:withPrivateWriteAccessDo -- block. You should not call any of the with___Do functions yourself. catalog:assertHasPrivateWriteAccess( "SampleMetadataDefinition.updateFromEarlierSchemaVersion" ) local myPluginId = 'com.adobe.lightroom.metadata.sample' if previousSchemaVersion == 1 then local photosToMigrate = catalog:findPhotosWithProperty( myPluginId,'siteId') -- optional: can add property version number here for i, photo in ipairs( photosToMigrate ) do local oldSiteId = photo:getPropertyForPlugin( myPluginId, 'siteId' ) -- add property version here if used above local newSiteId = "new:" .. oldSiteId -- replace this with whatever data transformation you need to do photo:setPropertyForPlugin( _PLUGIN, 'siteId', newSiteId ) end elseif previousSchemaVersion == 2 then -- and so on... end end, } This is how these fields appear in the Metadata panel, when the user has chosen a metadata tagset that contains them, or one of the default metadata tagsets "All" or "All Plug-in Metadata" (see "Adding custom metadata tagsets" on page 73). The user-visible custom fields from plug-ins are shown after all of the built-in metadata fields.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204

C
HAPTER
4: Working with Metadata
Adding custom metadata
72
title = LOC "$$$/Sample/Fields/ModelRelease/NotSure=Not Sure",
},
{
value = 'yes',
title = LOC "$$$/Sample/Fields/ModelRelease/Yes=Yes",
},
{
value = 'no',
title = LOC "$$$/Sample/Fields/ModelRelease/No=No",
},
-- optional: allowPluginToSetOtherValues = true,
},
},
},
schemaVersion = 1,
-- must be a number, preferably a positive integer
updateFromEarlierSchemaVersion = function( catalog, previousSchemaVersion,
progressScope )
-- When the plug-in is first installed, previousSchemaVersion is nil.
-- As of Lightroom version 3.0, a progress-scope variable is available; you can
-- use it to signal progress for your upgrader function.
-- Note: This function is called from within a
catalog:withPrivateWriteAccessDo
-- block. You should not call any of the with___Do functions yourself.
catalog:assertHasPrivateWriteAccess(
"SampleMetadataDefinition.updateFromEarlierSchemaVersion" )
local myPluginId = 'com.adobe.lightroom.metadata.sample'
if previousSchemaVersion == 1 then
local photosToMigrate = catalog:findPhotosWithProperty( myPluginId,'siteId')
-- optional: can add property version number here
for i, photo in ipairs( photosToMigrate ) do
local oldSiteId = photo:getPropertyForPlugin( myPluginId, 'siteId' )
-- add property version here if used above
local newSiteId = "new:" .. oldSiteId
-- replace this with whatever data transformation you need to do
photo:setPropertyForPlugin( _PLUGIN, 'siteId', newSiteId )
end
elseif previousSchemaVersion == 2 then
-- and so on...
end
end,
}
This is how these fields appear in the Metadata panel, when the user has chosen a metadata tagset that
contains them, or one of the default metadata tagsets “All” or “All Plug-in Metadata” (see
“Adding custom
metadata tagsets” on page 73
). The user-visible custom fields from plug-ins are shown after all of the
built-in metadata fields.