Hi,

at first, thank you for this module that will gain me a lot of time: I'm photographer.

My question is about to know if it's necessary to assign (or not) a vocabulary in the setting page admin/config/media/exif/settings.
I mean, if we do not assign a vocabulary in this page, is it possible to assign several vocabularies in the settings of the several iptc fields ? (what seems to work bad)
Or it's necessary to have only one vocabulary for all iptc fields ?

PS: note that the read documentation link in the module page is broken

Thanks
Stephane //$vocabulary = $vocabularies[$chosen_vocabulary];

Comments

Stephane Bouillet’s picture

Stephane Bouillet CreditAttribution: Stephane Bouillet commented
Title: Choose or not a vocabulary » Existing term choosen instead of creating new one in the new vocabulary
Component: Documentation » Miscellaneous
Category: support » bug
Priority: Minor » Normal

Hi,

As for my problem, I've finally choosen only one vocabulary.

But there is another problem:
I have 2 vocabularies: one for my blog "stories", and another for the content type "image".
But if the image has a keyword (or country...) that is already in the blog vocabulary, it will use this one instead of creating a new one in the image metadata vocabulary.

Do you have already experimented this issue ?

Note that I use path auto and token, but without using these modules, it seems to be the same...

Thank you for your help

jphautin’s picture

jphautin CreditAttribution: jphautin commented

The actual design of the module is to work with only one vocabulary that must be set in the admin page.
If it is not set, It should not link any tags to any images.

I could perharps add an option to choose a vocabulary per node type or per even per node but is it really your need ?

For your 2nd issue, I think this is a bug and you should open an new issue with the description.

regards,

jphautin’s picture

jphautin CreditAttribution: jphautin commented
Assigned: Unassigned » jphautin
jphautin’s picture

jphautin CreditAttribution: jphautin as a volunteer commented
Version: 7.x-1.2 » 7.x-1.3
Component: Miscellaneous » Code
Issue summary: View changes
jphautin’s picture

jphautin CreditAttribution: jphautin as a volunteer commented
Version: 7.x-1.3 » 7.x-1.x-dev
Issue summary: View changes
Status: Active » Fixed

There was an issue in the "section" term lookup. The first lookup was not limited to the chosen vocabulary.
I change the behavior to be compliant with the description I give it to you in my previous post.

  • jphautin committed ec5ca33 on 7.x-1.x 
    Issue #1445744: Existing term choosen instead of creating new one in the...

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.