Taxonomy terms for iptc_keywords not split

@fuse
can I ask you how do you succeed to populate vocabulary terms? (even with the issue of 1 "big" term).

I think I have all the correct settings:

• field name:"field_iptc_keywords"
• field: "Term reference"
• widget: "metadata from image"
• my jpg images have keywords (used irfanview to populate keywords and keywords are still there if I download my uploaded images from the nodes. So I'm sure that image files contain iptc data)
• in manage display (I'm using Display Suite and all other exif fields show up), my field_iptc_keywords is set to display "link"

However my keywords do not show up in node and the vocabulary is not filled (not even as 1 big term). So I think I'm missing something.
thanks

In the admin page of the exif module, did you activate exif on the content type you are using ?

@jphautin: yes. Content type was activated. Thanks.
I think I found my error. In the "iptc keywords" field settings I missed to select a parent term. Now I have "keywords" as the parent term and the items populate.

@fuse: for "taxonomy terms added as 1 big term". I do not know if this can help you:
I had the same problem but I noticed that I was putting all my terms on an single line in the keywords area of my jpg file. When I wrote each term on a new line of the textarea, then the terms populated as different items.
Hope that can be useful for someone.

Hello,

I'am also using comma separated value in keywords and it works for me. Can you upload image with Lightroom metadata so I can test and found what is the issue.

regards,

keywords are not placed comma seperated in exif ( A,B,C) but like this:

<dc:subject> 
 <rdf:Bag>
   <rdf:li>A</rdf:li> 
   <rdf:li>B</rdf:li> 
   <rdf:li>C</rdf:li> 
 </rdf:Bag> 
</dc:subject>

There is also an hierarchical version in <lr:hierarchicalSubject>

It should not matter what programme is used for the tagging.
I tried with exif from lightroom, Adobe Bridge, geosetter. All working.
I use 7.x-1.x-dev with taxonomy patch: http://drupal.org/node/973328

Can the issue be considered as closed ?