For example: A tag's properties (let's say TagA) would include a field for "Implied Tags". Any tags entered there would be "implied" by TagA. So, if TagA is set to imply TagP and TagZ, any file tagged with TagA would automatically also be tagged with TagP and TagZ. Similar functionality is possible with tag hierarchy by using the Toggle Auto feature, but this approach has its limits. Auto-tagging all parent tags usually works, but will result in files being tagged with superfluous meta-tags. Additionally, if a tag implies two other tags which do not imply each other, automating this relationship becomes impossible with simple hierarchy rules. Not a huge deal, as you just have to remember to manually tag, but a problem solved is a problem solved. If anyone is convinced this would be a useful addition to Digikam and decides to spend their free time figuring out how to add it, you have my endless gratitude. If not, that's cool.
(In reply to fewopex195 from comment #0) > For example: > A tag's properties (let's say TagA) would include a field for "Implied > Tags". Any tags entered there would be "implied" by TagA. So, if TagA is set > to imply TagP and TagZ, any file tagged with TagA would automatically also > be tagged with TagP and TagZ. > > Similar functionality is possible with tag hierarchy by using the Toggle > Auto feature, but this approach has its limits. Auto-tagging all parent tags > usually works, but will result in files being tagged with superfluous > meta-tags. Additionally, if a tag implies two other tags which do not imply > each other, automating this relationship becomes impossible with simple > hierarchy rules. Not a huge deal, as you just have to remember to manually > tag, but a problem solved is a problem solved. > > If anyone is convinced this would be a useful addition to Digikam and > decides to spend their free time figuring out how to add it, you have my > endless gratitude. If not, that's cool. Hi fewopex195, I also had this idea. I'm calling it "relational tagging". Like you said, TagA automatically adds TagP and TagZ. Here's the question, if TagP also has related tags, should those tags be added? Let's say TagP is related to TagQ. Do we also apply TagQ since it's related to TagP which is related to TagA? I'm thinking of making this configurable in the UI through "Tag recursion". Thoughts? Cheers, Mike