Supported IPTC Fields in Aperture 3.3

Does anyone know what the current state of IPTC support in Aperture is as of 3.3.
Is there a document anywhere that specifies which fields are / are not supported ?
Thx

I've never seen this information documented (fwiw ).
You can get a list of IPTC fields in Aperture in a few ways.  Probably the easiest is via "Aperture➞Presets➞Metadata".  That dialog shows five sections of IPTC metadata fields.

Similar Messages

  • Missing IPTC Fields In Aperture 2

    Okay, I am switching from Lightroom to Aperture 2 after using Lightroom for roughly one year. Let me back up... I am trying to switch. Right off the bat, I am running into a problem that really has me perplexed... why on earth did Apple leave out certain IPTC fields, but leave in fields that are completely (at least in my humble opinion) useless to photography. Which fields? These are left out:
    - CCI City *
    - CCI Country *
    - CCI Address *
    - CCI Postal Code *
    - CCI State/Province *
    - CCI Email *
    - CCI Phone *
    - CCI URL *
    - ISO Country Code *
    - Intellectual Genre
    - Location *
    - Rights Usage Terms *
    - IPTC Subject Code
    - IPTC Scene
    Most of these, marked with an asterisk, are crucial to me, and are necessary when sending images to certain clients of mine. In the meantime, Apple, for some bizarre reason, chose to include the following, useless fields:
    - Action Advised
    - Audio Duration
    - Audio Outcue
    - Audio Sampling Rate
    - Audio Sampling Re... (can't read this one because Aperture refuses to show me the whole field name no matter how wide I make the metadata panel)
    - Audio Type
    This makes absolutely no sense to me, and I see no convenient way to get around this. This is compounded by the fact that IPTC seems to be transitioning to Core (XMP) standards, which means the field names are changed. Aperture is on version 2, and yet the IPTC support is this behind the times?
    I hope someone has some good news to help rectify this.

    ifarlow wrote:
    I just fired up Aperture 2 after reading your Post, and I see this for one of my images:
    Lens Model: EF24-70mm f/2.8L USM
    It is under EXIF - Expanded under the Metadata tab. Do you not see this?
    No, I didn't at first. First off - it does not show up at all in images I imported under 1.x and have not migrated to 2.0 version of RAW processing. Then - I see additional data under EXIF with new imports under Aperture 2.0 and images with updated RAW processors - but still not lens model. However, I then edited EXIF and found lens model. I simply added that field to my EXIF metadata, and now I can see (and search on) lens model for all of my images!
    Thanks for pointing that out - no telling how long it would have been before I found it. Its a shame this isn't a question I posted, or I would give the "solved" points.
    Now, if we can just find your metadata fields...
    Scott

  • What IPTC fields are supported by LR 1.1 (or 1.2)?

    I have previously discovered that Lightroom does not support IPTC properly. Does anyone have a list of supported IPTC fields, so I can know whether my current IPTC data will be safe or not? An answer from Adobe on this issue would have been great.
    Thanks
    H

    So it only supports a subset of the full ITPC-NAA IIM? Theoretically that's quite ok, but removing IPTC fields that are not supported is NOT quite ok.
    Is Lightroom's IPTC support documented somewhere? I haven't seen anything about it somewhere. At least, when a program is removing data from files that it does not like, it should have been a big warning sign somewhere.
    H

  • Missing IPTC fields

    Does anybody found the IPTC fields: categories, scenes and subject codes?
    They are quite important for journalism, but aren’t included yet? (like most of the creator infos)
    It would be nice, if I also can make sets/buttons from other IPTC information like from the keywords.
    Any press photographer here, who got the same IPTC problems?
    Greets.

    kgelner wrote:
    "Category" is there, as is "Subject Reference" (could be used as subject codes?). I'm not sure if there is something there Scene would map to.
    The ones that are there, you can add to any metadata set you are viewing by opening up the IPTC tab at the bottom of the screen, and pressing the checkmark next to the IPTC field you desire to add to the current metadata view (any metadata element from any category can be added to any view, they are just grouped as they are to start for convienience).
    Any that are not there - why not add them? For "Scene", open the "Other" tab at the bottom, then type "Scene" into the "New Custom Metadata" at the top of the field list, then enter some value for that field and press return. Now it will appear in the list with a checkbox, which you can add to the current view - and it should export with the image when you ask Aperture to export metadata.
    With all due respect, it absolutely amazes me that so many people don't understand how IPTC works. You can't just "map" fields any way you want, and if you want to follow the schema properly, you can't just put whatever data you want to in each of these fields. The ability to add custom metadata fields in Aperture is pointless, as they don't actually have any IPTC relevance.
    Therefore, adding fields to compensate for the lacking IPTC support doesn't work as these custom fields don't map to existing IPTC fields when the image is exported, so the data is lost. Pointless waste of time.
    Check out http://www.iptc.org for all the details. You should quickly realize after just a little reading that Aperture, even version 2, is lacking proper IPTC support. Frustrating, as Adobe Photoshop, Adobe Photoshop Lightroom, iView MediaPro, Microsoft Expression Media, and so many others properly support IPTC.
    However, to be fair, you are correct that Category is there. Subject Reference in Aperture is Subject Code in IPTC, however, in testing I have found that Aperture has serious export issues with metadata, and this is one of the fields that does not export at all. The four fields that do not export are:
    Object Attribute Reference -> IPTC Field: Intellectual Genre
    Sub-Location -> IPTC Field: Location
    Country Code -> IPTC Field: Country Code
    Subject Reference -> IPTC Field: Subject Code
    There is no Scene support in Aperture 2 (this is one of many missing fields in Aperture 2).
    I have a compiled list of IPTC fields, the properly mapped fields in Aperture 2, and the missing/broken fields in Aperture 2 if anyone wants it.
    Message was edited by: ifarlow

  • Can't find IPTC metadata after Aperture export into Lightroom

    Hi all, 
    I'm sure you've already worked through this pain, so maybe you'll have some insight for me:
    I am exporting approximately 25,000 images from Aperture 2.1.4 and importing them into Lightroom 4.  I started working with my small projects of about 300 images to test.  From Aperture, I exported the Master files with the Sidecar (IPTC4.XMP) files.  [My masters are a mix of .jpgs and .NEF, and I read that the jpgs don't always carry the meta data through].  I successfully imported the master files into Lightroom and ran the "Read Metadata from File" command.  I also exported the keywords file from Aperture and imported those into Lightroom as well. 
    Prior to exporting, I edited one file in Aperture by entering "test caption", "test location", "test keyword", "test copyright" etc. into several of the IPTC fields.  These fields are NOT appearing in the equivalent Lightroom fields.  I checked the .XMP file (using text edit) and it does contain the correct "test values".  I am getting all of the EXIF metadata, but none of my custom values.
    Is it as simple as not looking in the right place in Lightroom for my values?

    John, and Brent -
    Yes, thank you, you were both right.  Here is an updated screenshot showing the image in both applications, with the metadata where I expected it.  The trick, in my case, was to follow "Method 1" in the link above, to write the IPTC data into the .jpgs.  I'll use the sidecar method for the .NEFs, probably.  Also, expanding the fields proved that the keyword was present.  I'm sure I can mess around with the Display Metadata options from Default to other things.  All well; heroes to the rescue!
    Regards,
    Grace

  • Creating support message field reported by doesn't fill

    Hi colleagues,
    When I create a support message field reported by doesn't fill automatically.
    I think that I've completed all required steps in order these fields were filled automatically. Fields sold-to party and support team are filled automatically, they work ok.
    The steps that I've checked:
    - The support message is created successfully from satellite message(SID=DES_01). The user which creates this message is zprueba5 exists with profiles: SAP_ALL, SAP_NEW at the satellite system.
    -In the solution manager system(SID=SMG), transaction ib52 for the satellite system is filled with partners: employee responsible, sold-to party and system administrator.
    - In the solution manager system(SID=SMG), zprueba5 exists with profiles: SAP_ALL, SAP_NEW.
    - Transaction bp, zprueba5 user contains BP roles: Business Partner, Employee, Bill-To Party, Financial Services and at the tab "Identification":
    External BP Number: SMG 010 ZPRUEBA5
    ID Type     Description                         Identification number
    CRM001    External System Identifier   DES_01 0020281686 100 ZPRUEBA5
    CRM001    External System Identifier   SMG 0020276689 010 ZPRUEBA5
    So, In the solution manager system(SID=SMG), crm_dno_monitor transaction when I open the support message just created from satellite system, I have an error because reported by field isn't filled.
    Please could you help me?
    Thanks and Regards
    Raul Aguilar

    Hi Nikhil,
    At this message I'm going to reply your last two replies.
    1.- You typed me "In ib52 select both the system simultaneously and then go to->parner and assign proper bp no for the respective partner function. You need to do it for every system may be users are same.
    I hope you have maintained proper access sequence i.e. via ibase."
    For each SAP System that I've defined at SAP Solution Manager, at ib52 transaction I've defined the three roles that IMG activity documentation types:
            Assign business partners with the following functions to the new iBase component systems:
                Administrator
                Key User
                Sold-to Party
    SAP Solution Manager Implementation Guide->SAP Solution Manager(SP 17)->Configuration->Basic Settings->Standard Configuration of Basic Settings->Solution Manager->iBase->Assign Business Partners to iBase Components ->transaction Change iBase (IB52), enter in field Installed Base '1' and I select the SAP System->Goto -> Partner
          Function                                        Partner      
        00000014  Employee Responsible     298
        00000001  Sold-To Party                  295
        SLFN0001 System Administrator      295
    2.- You typed me  "Select you partner determination procedure and double click on "User interface setting" here select appropriate partner functions and assign all of them in ibase as I said in above reply.
    You must not be getting reported by partner function. Take out System administrator. Motivate by assigning points."
    My Partner Determ. Proc. is SLFN0001, so I double click on User interface setting like you explained me, adn now appears:
    Header Screen:
    Sequence and Functions for (main) Partner Displayed
    Partner Function1 00000001  Sold-To Party (CRM)
    Partner Function2 SLFN0002 Reported by (CRM)
    Partner Function3 SLFN0003 Support Team (CRM)
    Partner Function4 SLFN0004 Message Processor (CRM)
    But now I don't understand if at ib52 transaction I've to add any role or if from "User interface setting" I've to delete any Partner Function. Could you detail me when you type "You must not be getting reported by partner function. Take out System administrator", please?
    Regards,
    Raul .

  • Places: problem with the State field in Aperture 3.03

    hi,
    I live in Europe and I have some problems in handling the State field in Aperture 3.03, because this field isn't always relevant in non North-American Countries.
    The Google suggestions in Places don't always include the 4 fields (Location/City/State/Country). I have a lot of pictures taken in the Azores islands (Portugal) which don't show up in my Aperture map because the marker somehow doesn't write Azores in the State field.
    Question #1: is there a way to eliminate the State field from Aperture, or at least to render it optional?
    Question #2: if I manually create a New Location, what is the proper syntax to separate Location/City/State/Country in a way that will be understood by the Aperture database? I tried putting commas as a separator, but it doesn't seem to be working.
    Thanks for your help.

    Yes, same here. I cannot complete my registration process due to the same error. My state is correct, which is RS (two letters only). I don't know what else to do. Refer to the image below. Thanks!

  • LR and IPTC fields

    I have been running a photoblog at Digital-Photo for over 3 years now. I have noticed that ever since I have started to use Lightroom it gave me an added value of populating IPTC fields in Gallery 2 (web gallery I use). The IPTC seems to be very broad and I would like to understand how to use properly most if not all the fields within Lightroom.
    My question/request for Lightroom developers: can we get some build in selectors for many of standard IPTC fields with descriptions, please? This way I would not have to spend hours each time I get a new "genre code" etc.
    Here is a neutral and work safe example of what details show up for me: abstract photograph or an air vent
    Is anyone else in the community use those codes beyond Caption, Keywords and Copyright, and if so what gally applicatation are you using?
    Ted

    I have been running a photoblog at Digital-Photo for over 3 years now. I have noticed that ever since I have started to use Lightroom it gave me an added value of populating IPTC fields in Gallery 2 (web gallery I use). The IPTC seems to be very broad and I would like to understand how to use properly most if not all the fields within Lightroom.
    My question/request for Lightroom developers: can we get some build in selectors for many of standard IPTC fields with descriptions, please? This way I would not have to spend hours each time I get a new "genre code" etc.
    Here is a neutral and work safe example of what details show up for me: abstract photograph or an air vent
    Is anyone else in the community use those codes beyond Caption, Keywords and Copyright, and if so what gally applicatation are you using?
    Ted

  • I have got two photos by mail from iPhoto. My friend has put descriptions in the description field. The I got the mail I saw the description below each photo. If I check the photos with Preview they have Exif and JFIF fields but no IPTC field.

    I have got two photos by mail from iPhoto. My friend has put descriptions in the description field. The I got the mail I saw the description below each photo. If I check the photos with Preview they have Exif and JFIF fields but no IPTC field.

    Does you friend use any accented letters in the descriptions?  That might cause it but I don't know for sure.
    Has he run any repair operations on his library, i.e. repairing the database file? Another possible fixe that's easy to apply is the following:
    1 - delete the iPhoto preference file, com.apple.iPhoto.plist, that resides in your
        Home/Library/ Preferences folder.
    2 - delete iPhoto's cache folder(s):
    Home/Library/Containers/com.apple.iPhoto
    and, if there is one, the
    Home/Library/Caches/com.apple.iPhoto folder
    3 - reboot, launch iPhoto and try again.
    NOTE: In Lion and Mountain Lion the Home/Library folder is now invisible. To make it permanently visible enter the following in the Terminal application window: chflags nohidden ~/Library and press the Return key - 10.7: Un-hide the User Library folder.
    For  Mavericks, 10.9,  go to your Home folder and use the View ➙ Show View Options menu to bring the this window:
    The demo version of GraphicConverter can be used to view/check/edit the ITPC fields in an image file after exporting.

  • Reset or Edit IPTC Fields Stored Values

    Previous values used in IPTC fields are stored so that values can be auto-filled as a field is entered. I would like to remove some of the "stored values" for a field. How can I do this?
    Thanks,

    You can batch change. Select the photos you want to edit, batch change, leave the field empty, and check the "replace" checkbox.

  • IPTC-fields too small

    We are encouraged to use metadata with our pictures.
    Why - in the Organizer - are the IPTC fields so small. Description just one scrolling line  Keywords - normally not many, have been granted 3 lines! The editor "file information" is OK.

    In PSE11 you can select a thumbnail and click on the three small dots to the right of IPTC. You have many fields to add data (see image) and you can also select multiple thumbnails, to add, append or overwrite metadata and save it to files.

  • IPTC fields

    Does anyone know where I can find scripts for filling in IPTC fields on photos via an Automator workflow?
    I have previously used Automator workflows to fill in the IPTC fields of my digital photos. I've recently reinstalled my computer and now the workflows don't work - I seem to remember downloading some scripts and included one for IPTC date in the workflows. I guess they got wiped when I reinstalled - any idea were I could dig them up? The most important element for me was the bit that writes the file name into one of the IPTC fields.

    Hi Bebbs,
    Does this help...
    http://cva.stanford.edu/people/davidbbs/photos/IPTCkeywords_tofilename/
    Or this...
    http://discussions.apple.com/thread.jspa?threadID=1499998

  • IPTC field codes -- Bridge IPTC Core metadata

    Is there a reference somewhere as to which IPTC codes match up with the IPTC Core fields in Bridge metadata?
    A list of the codes is here, so you know what I'm talking about. For example, the Description field in Bridge metadata corresponds to the Caption / #120 code in this list:
    http://www.fotoware.com/binaries/fsp50/userguide/28.htm
    I'm using a plug-in that writes image info from a database into the corresponding file's IPTC fields based on the IPTC code, but the names of the fields on the list of codes don't match up with what they're called in Bridge, so it's taking a lot of trial and error to figure out where things go.

    Never mind, found one. It doesn't mention Bridge specifically, but it has Photoshop and Lightroom (along with several other image-browsing apps) and both seem similar to Bridge:
    http://www.controlledvocabulary.com/imagedatabases/iptc_core_mapped.pdf

  • Adding EXIF Fields to Aperture - possible?

    Hello all,
    I would like to add to the EXIF fields that aperture displays.  I know that you edit the Metadata views, and check the various Metadate Fields on and off, but I would like to add Metadata that my camera records in EXIF that aren't listed.  Is that possible? 
    As an example, one of the EXIF fields that I see when looking at the RAW picture using exiftool is "Drive Mode" (with a value of "Continuous Shooting" in this particular image).  However, I don't see a selectable "Drive Mode" field in the Metadata Fields list, so is it possible to edit the EXIF fields that Aperture displays somewhere?
    Thanks,
    Brian

    To see, which of the EXIF fields of your images Aperture recognizes, try a simple Apple Script:
    Launch AppleScript Editor and paste this in:
    tell application "Aperture"
              set imageSel to (get selection)
              repeat with i from 1 to count of imageSel
                        tell item i of imageSel
                                  get name of every EXIF tag
                        end tell
              end repeat
    end tell
    Then select an image in Aperture and press the "Run" button in AppleScript's toolbar.
    This script will simply list all names of the EXIF tags, that are available to be used in AppleScript messages to Aperture.
    For example for my Canon Photos I see this list:
    {"ApertureValue", "CameraSerialNumber", "CaptureDayOfWeek", "CaptureHourOfDay", "CaptureMinuteOfHour", "CaptureMonthOfYear", "CaptureSecondOfMinute", "CaptureYear", "ColorModel", "ColorSpace", "Copyright", "Depth", "ExifVersion", "ExposureBiasValue", "ExposureMode", "ExposureProgram", "Firmware", "Flash", "FlashExposureComp", "FlashPixVersion", "FocalLength", "FocusMode", "ISOSpeedRating", "ImageDate", "LensMaxMM", "LensMinMM", "LensModel", "Make", "MaxApertureValue", "MeteringMode", "Model", "PixelHeight", "PixelWidth", "ProfileName", "SceneCaptureType", "ShutterSpeed", "WhiteBalance", "WhiteBalanceIndex"}
    To use all tags that exiftool sees, you can embed calls to exiftool into an AppleScript and write them to a Custom Metadata field.
    Regards
    Léonie

  • CS3 Extended - IPTC field limit of 32 characters?

    When I open an image, then save it - Photoshop will shorten the information in the Credit field to about 32 characters - BUT not all the times!!?? PS has saved this shorter version to the side in the 'pull down' area. I'm not positive if PS is shortening or using the 'saved' wrong version. 
    I have two questions -
    Is there a character limit? 
    Is there a way to remove typos in the 'saved' area of Credit or other IPTC fields within PS?
    Thank you
    Lloyd

    If you store a 33-character text in the IPTC Sublocation field in LR, do Metadata > Save To File, and then check the metadata with Exiftool, you'll see that the IPTC:Sub-location field contains a truncated 32-character value, while XMP:Location contains the full 33-character value.  This conforms to the industry standards.
    The terminology is horribly confusing.  In the JPEG file format, there are several sections of metadata, including EXIF, IPTC, and XMP.  EXIF and IPTC are defined by older standards (cameras create EXIF metadata, and applications create and add to both EXIF and IPTC metdata).  The XMP section is defined by a newer industry standard, and it was designed to incorporate all of the fields that can be stored in EXIF and IPTC; a subset of the XMP fields (a "namespace") is called the "IPTC Core" and defines fields similar to the legacy IPTC fields but without the restrictions.
    A recent standard, the Metadata Working Group's Guidelines for Handling Image Metadata 2.0, defines the rules for how the three sections of metadata (EXIF, IPTC, and XMP) should be "synchronized".  LR appears to mostly conform to that standard.

Maybe you are looking for

  • How to change a field of type CHAR of a database table to DATS

    Dear ABAP experts, I have a database table: ZLT_aztnew with fields M1, M2, K1, K2, A1, A2, P1, P2, S2, D1, D2,  STD, BES. All these fields are of type 'Character'.  except D2 which is of type DATS. The field D1 is date and is in format DD.MM.YYYY. I

  • Anyone have a step-by step guide to downloading new itunes version?

    I've downloaded a new version before but i lost all my music. Does anyone have a way so that I won't? I'm trying to fix an authorization problem (-208). Thanks   Windows 2000  

  • How to execute Show Desktop.scf in Labview?

    Dear all,,  Can anyone tell me how to excute Show Desktop.scf in labview? Regards, Santhosh Solved! Go to Solution.

  • BAPI output column names are not meaningful. How to change it?

    Hi Experts The custom BAPI's output has the the table field names as its column headings. So it is difficult to understand. How can I replace them with meaningful headings for each column? For that, is there any way without creating another output st

  • CK-7W Bluetooth Echo problems

    Hi I have two cars each with Nokia CK-7W car kits installed. They work fine with Nokia phones, but when I use any non-Nokia phones over bluetooth the caller hears a loud echo of themselves when speaking although my side sounds fine. This is a major p