Zum Hauptinhalt gehen

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Can C1 exclude selected keywords on image output?

Kommentare

8 Kommentare

  • Ian Wilson
    Moderator
    Top Commenter
    I watched that webinar too. I don't think it was particularly clear at that point. I think that the use of the ~ symbol was intended to work with some other system, rather than it being translatable into Capture One. However, this is what I do. I have created several keyword libraries called Where, Who, Living Things (I shoot a lot of bird and other nature photography), etc. So Living Things might have a hierarchy like Birds>Birds of Prey>Marsh Harrier. Keywords in the export include Birds>Birds of Prey>Marsh Harrier but usefully they don't include the library title (Living Things). Also in my process recipes I can specify whether or not keywords are included, and if they are included I can specify which libraries (so I can exclude Who but include Where, for example.

    Ian

    Edited to add: you could make use of the imported library without having to enter all the keywords yourself, on my system too. The libraries are stored as text files, so it would be easy enough to use only the Where section of it for your Where library, for instance. (Though I have chosen not to do that - I just build up entries for new places, birds, etc as I go, so the libraries grow as I visit new places, or spot new species.)
    0
  • Tim Woodcock
    Ian3 wrote:
    I watched that webinar too. I don't think it was particularly clear at that point. I think that the use of the ~ symbol was intended to work with some other system, rather than it being translatable into Capture One. However, this is what I do. I have created several keyword libraries called Where, Who, Living Things (I shoot a lot of bird and other nature photography), etc. So Living Things might have a hierarchy like Birds>Birds of Prey>Marsh Harrier. Keywords in the export include Birds>Birds of Prey>Marsh Harrier but usefully they don't include the library title (Living Things). Also in my process recipes I can specify whether or not keywords are included, and if they are included I can specify which libraries (so I can exclude Who but include Where, for example.

    Ian

    Edited to add: you could make use of the imported library without having to enter all the keywords yourself, on my system too. The libraries are stored as text files, so it would be easy enough to use only the Where section of it for your Where library, for instance. (Though I have chosen not to do that - I just build up entries for new places, birds, etc as I go, so the libraries grow as I visit new places, or spot new species.)


    Thanks for your detailed reply. I'll experiment with your MO and see whether it suits my workflow.

    Ideally I'm still hoping for a way to tag keywords I don't want to export rather than exclude whole libraries.

    Tim
    0
  • SFA
    trailguru wrote:
    Ian3 wrote:
    I watched that webinar too. I don't think it was particularly clear at that point. I think that the use of the ~ symbol was intended to work with some other system, rather than it being translatable into Capture One. However, this is what I do. I have created several keyword libraries called Where, Who, Living Things (I shoot a lot of bird and other nature photography), etc. So Living Things might have a hierarchy like Birds>Birds of Prey>Marsh Harrier. Keywords in the export include Birds>Birds of Prey>Marsh Harrier but usefully they don't include the library title (Living Things). Also in my process recipes I can specify whether or not keywords are included, and if they are included I can specify which libraries (so I can exclude Who but include Where, for example.

    Ian

    Edited to add: you could make use of the imported library without having to enter all the keywords yourself, on my system too. The libraries are stored as text files, so it would be easy enough to use only the Where section of it for your Where library, for instance. (Though I have chosen not to do that - I just build up entries for new places, birds, etc as I go, so the libraries grow as I visit new places, or spot new species.)


    Thanks for your detailed reply. I'll experiment with your MO and see whether it suits my workflow.

    Ideally I'm still hoping for a way to tag keywords I don't want to export rather than exclude whole libraries.

    Tim


    Sounds laborious if image by image depending on volumes.

    If you always want to exclude certain words then simply putting them in their own KW library would be effective in many cases.

    If image by image or output by output you could consider creating a variant of the image which excludes those KWs. Perhaps not elegant but it would be simple and effective and make the output easily repeatable.

    Grant
    0
  • Tim Woodcock
    Grant wrote:


    Sounds laborious if image by image depending on volumes.

    If you always want to exclude certain words then simply putting them in their own KW library would be effective in many cases.

    If image by image or output by output you could consider creating a variant of the image which excludes those KWs. Perhaps not elegant but it would be simple and effective and make the output easily repeatable.

    Grant


    An example of what I'm after should help....

    From the keyword library text file (Tabs are represent in italics):


    [~PHOTOGRAPHY]
    "TAB" [~Angle Of View]
    "TAB TAB" back view


    If I begin to type 'back view' into the the Keywords 'Enter keywords' field the above keywords can be selected from the offered list as follows:

    ~PHOTOGRAPHY, ~Angle Of View, back view

    From my initial post you'll appreciate that I had expected that words prefixed with ~ (tilde) would not be carried over on output. But they are.

    I would like to know if someone has found a character that does work in the way I had hoped the ~ (tilde) would.
    0
  • SFA
    Ah! Hierarchical keywords.

    As far as I am aware the concept of the tilde as an 'omit' indicator is not supported but that may have changed and I would be happy to be corrected.

    The solution would seem to be to call the source Keyword library "Photography" and skip the duplication of the 'Photography' keyword since it looks a little superfluous unless you are also using the same sub-words of other, non-photography, file tagging. Art files for example. In which case in a combined DAM the distinction may be important.

    However in your example both tilde pre-fixed words, although exemplary representation of an hierarchical construction, seem to be superfluous.

    However there are a number of other situations that can arise where the ability to trace the hierarchy back to a particular group and, perhaps, remove the entire hierarchical group even though the same low level KW needs to be retained from a different hierarchical source set of 'words', means that the availability of the entire source chain has potential benefits.

    However I do not think the tilde (or an alternative character) functionality you seek is supported at this time. I may be wrong, as mentioned before.

    HTH.


    Grant
    0
  • Edward Moroch

    Has anybody found a character that can be used to signify "don't export this keyword"?  I hate seeing ~WHAT (as well as ~WHO, ~ATTRIBUTE, ~Event, ~...)  as a keywords in all of my exports. 

    0
  • Ian Wilson
    Moderator
    Top Commenter

    I don't think Capture One supports that convention. 

    Ian

    0
  • Edward Moroch

    Ian, That’s a shame. It’s such an easy thing to implement. I know, I use to write a lot of code before I retired. I wound up taking the keyword list that “trailguru” referenced and flattened it a lot. It still has a hierarchy but not that deep. I eliminated all ~... keywords and where appropriate used real keywords.

    0

Post ist für Kommentare geschlossen.