Adding extra fields

[Jeroen]

Is it possible to add extra fields to images?

Background info:
I manage an archive, like we all do, and want to keep track of a picture has been used in a publication. Especially if a photo's hits the front page or a leading article I need to be sure that picture isn't used the same period again (length of period depending on the circulation/importance of the magazine). So I want to be able to store Things like; publication name, page number, photo size (small, medium, large), publication date, medium (print, web) and circulation (number of prints or estimated views on a webpage). To make things more complicated; it is possible the same picture is used on more than one magazine/website...

(For now I scan the magazine and store that image next to my original photo and add an extra keyword "printed". All parameters above I store in the title of the scan.)

Thanks in Advance

Jeroen / Amersfoort / The Netherlands

 

[johnbeardy]

You can use the SDK to create extra fields. However, this requires some programming skill, and while two of us plug-in authors have created user-definable custom field plug-ins, we've chosen not to release them because of a range of weaknesses in the implementation. In my view releasing a plug-in more widely would expose users to the risk of losing valuable metadata. If you have your own programming skills and experience of data preservation (DAM awareness) then you're OK.

Most people pollute their keywords with such information. It's a shame we're still in this situation when almost any existing DAM application (and Aperture) allows users to set up extra fields.

John

 

[Jeroen]

Thanks for your (quick) reply; I will dive into the SDK. I understand your concern (and highly appreciate it).

When adding this, or other, extra information via the SDK; will there be a change it will survive an upgrade to 2.6 or even 3.x?

Thanks in advance

--
Jeroen / Amersfoort / The Netherlands

 

[johnbeardy]

Well, there's no absolute guarantee but I expect it to be OK. However, LR custom fields are not yet as standard as XMP metadata so there's got to be some risk.

John