Adobe 65007312 Programming Guide - Page 68

Working with Metadata, Adding custom metadata, Declaring a Metadata Provider

Page 68 highlights

4 Working with Metadata X A plug-in can define customized metadata fields for photos by declaring a Metadata Provider in the information file, and defining type and version information for each field. See "Adding custom metadata" on page 68. X A plug-in can specify metadata tagsets that affect the display of custom metadata fields in the Library module's Metadata panel. See "Adding custom metadata tagsets" on page 73. X Plug-ins can define complex searches that find photos according to metadata values. See "Searching for photos by metadata values" on page 75. Adding custom metadata Your plug-in can define custom metadata fields for photos that are imported into Lightroom. These fields can be visible and even editable in Lightroom's Metadata panel, or can be invisible and used to store private data. Declaring a Metadata Provider Like an Export Service or Export Filter Provider, you declare a Metadata Provider in the information file (Info.lua) for your plug-in. See "Writing standard plug-ins for Lightroom" on page 22. To declare a Metadata Provider, include an LrMetadataProvider entry in the Info.lua file; for example: return { LrSdkVersion = 3.0, LrToolkitIdentifier = 'com.adobe.lightroom.metadata.sample', LrPluginName = LOC "$$$/CustomMetadata/PluginName=Metadata Sample", LrMetadataProvider = 'SampleMetadataDefinition.lua', } The information file that declares a Metadata Provider can also declare metadata tagsets (see "Adding custom metadata tagsets" on page 73), export services and/or filters, but need not do so. Limitations of custom metadata in this release In the current implementation, custom metadata defined by a plug-in has these limitations, which will be addressed in future versions of the Lightroom SDK: X Values stored in custom metadata fields are stored only in Lightroom's database. In the current release, a plug-in cannot link custom metadata fields to XMP values or save them with the image file. X A plug-in cannot specify complex data types. You can define simple fields per photo, but you cannot define a whole spreadsheet per photo. 68

  • 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

68
4
Working with Metadata
X
A plug-in can define customized metadata fields for photos by declaring a Metadata Provider in the
information file, and defining type and version information for each field. See
“Adding custom
metadata” on page 68
.
X
A plug-in can specify metadata
tagsets
that affect the display of custom metadata fields in the Library
module’s Metadata panel. See
“Adding custom metadata tagsets” on page 73
.
X
Plug-ins can define complex searches that find photos according to metadata values. See
“Searching
for photos by metadata values” on page 75
.
Adding custom metadata
Your plug-in can define custom metadata fields for photos that are imported into Lightroom. These fields
can be visible and even editable in Lightroom's Metadata panel, or can be invisible and used to store
private data.
Declaring a Metadata Provider
Like an Export Service or Export Filter Provider, you declare a Metadata Provider in the information file
(
Info.lua
) for your plug-in. See
“Writing standard plug-ins for Lightroom” on page 22
.
To declare a Metadata Provider, include an
LrMetadataProvider
entry in the
Info.lua
file; for example:
return {
LrSdkVersion = 3.0,
LrToolkitIdentifier = 'com.adobe.lightroom.metadata.sample',
LrPluginName = LOC "$$$/CustomMetadata/PluginName=Metadata Sample",
LrMetadataProvider = 'SampleMetadataDefinition.lua',
}
The information file that declares a Metadata Provider can also declare metadata tagsets (see
“Adding
custom metadata tagsets” on page 73
), export services and/or filters, but need not do so.
Limitations of custom metadata in this release
In the current implementation, custom metadata defined by a plug-in has these limitations, which will be
addressed in future versions of the Lightroom SDK:
X
Values stored in custom metadata fields are stored only in Lightroom's database. In the current
release, a plug-in cannot link custom metadata fields to XMP values or save them with the image file.
X
A plug-in cannot specify complex data types. You can define simple fields per photo, but you cannot
define a whole spreadsheet per photo.