Thanks for your question and for adding the rule details; very helpful.
You wrote “so I can use the hierarchical structure“. There is nothing in the current mapping logic that will generate hierarchical structures from the content of the “EXIF/Template Value” text box. You can use the “Parent” dropdown to put the mapped terms under one specific parent term. You might be interested in this earlier topic which motivated an MLA example plugin to add the feature:
Help with Custom Taxonomy
Your final rule looks very close. Here’s a rule I think will accomplish your goal:
template:([+exif:Artist+], )([+exif:Keywords+], )Gallery Photo
I have removed the leading [+ before the template: prefix (and trailing +]) and moved the trailing space character into the Keywords substitution parameter.
Regarding your “spurious category of [+exif:Keywords+]“, I have run some tests on my system and I cannot reproduce this issue. It is possible that this is an artifact of the variations you experimented with. Try deleting this term from the Media/Att. Category taxonomy edit screen and rerunning the mapping.
If the problem persists, and you can post a link to one or more of the items that have this issue on your system I can investigate further. Thanks for any additional details you can provide.
David,
Hi thanks for the response I had to adjust your mapping rule as I found that some photos (not destined for the gallery) had keywords but no Artist. In the end I used this rule:
template:([+exif:Artist+], Gallery Photo, )([+exif:Keywords+])
so the Gallery Photo category is only created if I have an entry in exif:Artist which is populated from the Windows PC File Explorer Authors field.
I also discovered that everything is case sensitive!
thanks again for an excellent plug in.
Paul
Thanks for your update with the good news. It occurs to me that if all the terms have unique names and are defined in advance the mapping rule should find them and work as you intend.
I am marking this topic resolved, but please update it if you have any problems or further questions regarding your mapping rules. Thanks for your interest in the plugin.