Hey,

I noticed this issue a while back #598558: iptc multiple keywords not loaded into field where someone asked to merge the keywords so that all of them would get shown. Now I'm wondering if you'd be interested in doing the opposite ;) namely splitting these up again so that they could be added as taxonomy tags.. For example I've created a CCK field using the content_taxonomy module, but that module does preprocessing of the inputted data before the insert (eg. if you type 'drupal, cms', it will split the two tags up, insert them both into the taxonomy and return the tids so that they could be saved as field_name[0]['value'] = N, field_name[1]['value'] = M).

As you can see there are several steps missing from the current module.. the preprocessing and inserting of terms, and the ability to store several values inside a field (right now it's always field_name[0]...). It's a shame though as having keywords as taxonomy terms would be sooo useful.

The question is - are you interested in this at all, would you be willing to write a patch or should I go for that myself and maybe post it here?

Thanks,
Martin

CommentFileSizeAuthor
#3 exif_kw.patch2.74 KBarski

Comments

arski’s picture

bump :( please?

rapsli’s picture

how about you write a patch. Right now I don't have time to look into this. I'm though usually very open accepting patches. Incase you write a patch, make sure both methods are possible.

arski’s picture

Title: Separating IPTC keywords » Separating IPTC keywords when saving to a content_taxonomy field
Assigned: Unassigned » arski
Status: Active » Needs review
StatusFileSize
new2.74 KB

Hey,

Okido, here's a patch. What it does is check if the iptc_keywords data should be saved to a "content_taxonomy" field, and if so, does the processing according to the selected widget (I only implemented it for the autocomplete widget now, as select/checkbox make no sense here due to limited set of keywords in my opinion. Anyway, if anyone feels the will to extend this further, the patch offers an easy way to do so..). Obviously, if the field is not from content_taxonomy, things go as usual.

Let me know if anything is wrong with it and I'll try to improve this.

Cheers,
Martin

momper’s picture

subscribe

arski’s picture

hmm, good point - any news on reviewing this one? :(

rapsli’s picture

oky. Just go kinda busy reviewing this. Gotta get deeper into this, so it's probably gonna take some more time.

arski’s picture

np, as long as something is happening and you don't forget it :)

arski’s picture

umm, bump again :)

arski’s picture

sachbearbeiter’s picture

subscribe

galooph’s picture

Thanks arski - tried the patch and it works for me \m/ :-)

metabits’s picture

I have my page in a shared hosting. Can I use this patch? If yes, how.? I am a photogrpaher and this is very important for me (it would save me hours of tedious work!)

Thanks!

psc

metabits’s picture

I found out myself reading http://drupal.org/node/534548 I apply the patch manually to the dev version (2010-Oct-13) and now I get my keywords imported.

You made my day with this patch!

Thousand thanks

psc

korayal’s picture

I am using imagefield_import

I can see that new taxonomy terms are generated. But those terms look like they aren't assigned to that node. (I check this from the term page)

Not until I edit that node and save it again.

I think it's only saving to the cck_taxonomy table.

jarodms’s picture

I applied this patch to 1.4 and it seems to work for the most part. The only issues I see so far are:

  1. Any tags I add manually are overwritten during the next save of the node
  2. If the keyword is duplicated within the exif data, the keyword is added multiple times to the vocabulary. I can delete the duplicate tag, but then when I save the node again issue #1 takes over and the duplicate tag appears again.
clintthayer’s picture

I'm finding the same issue as issue 1 from #15.

Anyone find a solution?

clintthayer’s picture

Anyone have any thoughts on what jarodms and I are finding? This is a helpful tool, but if I can't edit the info after the fact, it makes it less useful.

jphautin’s picture

Issue summary: View changes
Status: Needs review » Closed (outdated)
jphautin’s picture

Drupal 6 EOL