ACDSee Pro 3

Captions on photo import in IPTC dont appear in DBase

• 

  grahcom
  Member

  What I can't fathom is that when downloading photos from the camera into Pro 3 using the ACDSee Device Detector, details that I put in the IPTC caption field during the import, don't show up in the database Caption field after import.    I would have thought that the details would import across into the DBase Caption field, (or a DBase Caption field entry area should be on the Device Detector import menu) so that one doesn't have to redo the same details again, as I would have thought most users would want the inforamtion to appear and be stored in the datase caption field not just the IPTC caprion field.   Appears to me one has to either redo/copy paste the information or run Batch Set Information to get the info copied across from the IPTC Caption filed into the DBase Caption field.  or am I just not doing something correctly?

  cya Graham

  Posted On September 29, 2009 - 10:20 AM (1 month ago) (Permalink to this post)
• 

  Marc Sabatella
  Moderator

  Database Caption and IPTC Caption are two completely unrelated fields.  You can choose to set *both*, if you like, during import.  But I never normally mess with doing that sort of thing on import - I enter info into the db fields after import, then run Batch Set Information to copy it all to IPTC when I'm done.  I have a template (set to come up by default) to do this, so it takes only three keystrokes to do the job - one to bring up the Batch Set Information, then Enter to start the operation, then Enter when it's done to close the dialog.

  Posted On September 29, 2009 - 07:34 PM (1 month ago) (Permalink to this post)
• 

  grahcom
  Member

  Thanks for the prompt reply Marc.   Yes I would like to be able to set *both*, the IPTC & DB Caption fields on import BUT (unless I'm missing something here) there is no DB Caption field availabe on the import menu.  So at the moment I just copy data, ie select relevant files and Ctrl D, paste the info into the DB field.    Just thought I'd give the new import menu/fields a try, but will revert back to my previous method.

  Previously as you do, I also imported the photo's then entered info into the db fields after import, then run Batch Set Information to copy relevant info to IPTC/EXIF and will go back to that method, not just because of the above, but I like to rename the files date/time_sequence number once they are into the relvant folder/sub folder they are to be kept so that sequence numbers follow on from those already in the folder.

  cya

  Graham  

  Posted On September 30, 2009 - 01:35 AM (1 month ago) (Permalink to this post)
• 

  grahcom
  Member

  Have notice that if I leave the IPTC caption field blank on photo import, it gets filled by data from the EXIF Image Description field during the import.    ie the EXIF Image Description field contains the words  "OLYMPUS DIGITAL CAMERA"   these words get duplicated into the IPTC Caption field on photo import.   This did not happen with Pro 1, the words would just stay in the EXIF field.         No great drama really as I later Batch Set Information from the DB Captions into both these fields.  

  Anyone else find this happening??    

  cya

  Graham

  Posted On September 30, 2009 - 07:36 AM (1 month ago) (Permalink to this post)
• 

  Marc Sabatella
  Moderator

  I believe Pro 1 didn't support XMP; it's with XMP support at Pro 2 that EXIF Image Description was defined to to be the same as IPTC Caption.

  Anyhow, you're right - doesn't seem to be a way to set db caption on import, so I guess it's a job for Batch Set Information.  FWIW, I normally use Caption for info specific to each photo, and Notes for info common to a whole shoot.  I notice that "Notes" is on the list but Caption is not, so I'm guessing the program designers were imagining people doing things more like I described.

  Posted On October 1, 2009 - 11:35 PM (1 month ago) (Permalink to this post)
• 

  grahcom
  Member

  Thanks again for the info Marc, I've never really used the Notes field, I've usually have just used captions but sometimes the info can get a bit long winded.   So will do a bit of testing and experimenting and see what use it can be for me,  keeping in mind both your system for Batch Set Information DBase to IPTC of  Author->Photographer, Notes->Headline, Caption->Caption, Keywords->Keywords, and Rating->Urgency  and the following...url   http://blog.davidburren.com/2008/05/sensible-metadata-captions.html

  cya Graham

  Posted On October 2, 2009 - 03:38 AM (1 month ago) (Permalink to this post)
• 

  Marc Sabatella
  Moderator

  Thanks for the pointer to David Burren's article.  I think I had seen it before, but good to see again.  I realize this is all pretty subjective, but I do think his read of the IPTC specs matches mine - the Headline field is really intended to the be sort of brief/ general thing that I think you are probably using Caption for (I assume this since you are using one Caption for a whole batch of images), but Caption is intended to be more image-specific.  I think it was starting from that realization that I worked backwards and decided to put that general stuff into Notes and have Notes map to headline.  Although i don't actually set Notes on Import; I find it easier to do a select all *after* import then type into the larger Notes box than to deal with customizing this field on import.  I basically don't mess with the default values I placed in the various fields of the import (photographer and contact info), except for location, which I do alter on the fly when traveling.  And even then, I only mess with the IPTC location fields directly on import because there is nothing else in the db I can use to store that info after import.  If there were db fields for location, I'd set location there after import (for images not shot in my default lcoation) and then write that to IPTC along with everything else when done processing the images.

  Posted On October 2, 2009 - 06:46 PM (1 month ago) (Permalink to this post)

Subscribe to this topic via RSS

Reply

You must log in to post.