Skip to main content

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

Help with smart album criteria

Comments

4 comments

  • Timothy Trim
    I think you would need to add a Related or Not Related to me keyword, or colour tag and exclude those from your smart album. Likewise with Wedding exclude those. The important thing is to create the keywords and/or colour tags and/or * ratings to suit how you wish to search. A star or colour can mean whatever you want potentially.
    0
  • SFA
    Ian,

    The joys of keywording and the challenges of trying to future proof you word and phrase sets in order to obtain precision without knowing what may be added to the KW set in the future.

    Some things that might be worth trying - you should be able to test this simply using the search as a first check.

    Apart from finding alternative words - like nuptials rather then wedding for example - you could try "wedd "with a space. (Also bear in mind case sensitivity but that it tricky to ensure consistent usage.)

    In a full Smart Album type of search one could use things like "does not include".

    So Includes "wedd" but does not include "wedding" for example. Awkward is you ever come across someone called wedding.

    As for people with the same family name - include the KW family I would think is the simplest solution that would be useful to any search - for example if included in exported images that others might have in their own libraries and might wish to search through. In such cases KWs are useful where colour tags and star ratings most likely ore not.

    Or, of course, other metadata/IPTC fields could be used - perhaps as an interim solution to allow differentiation whilst still assessing the best possible approach for your specific needs.



    Grant
    0
  • Ian Wilson
    Moderator
    Top Commenter
    Grant

    Thanks. You can’t, it seems, use criteria like includes Wedd but does not include wedding. (No but facility.) Your mention of what might be included in the future makes me think that I might do well not to invest too much time and effort before seeing what enhancements to the cataloguing features come with version 12.

    Ian
    0
  • SFA
    Ian3 wrote:
    Grant

    Thanks. You can’t, it seems, use criteria like includes Wedd but does not include wedding. (No but facility.) Your mention of what might be included in the future makes me think that I might do well not to invest too much time and effort before seeing what enhancements to the cataloguing features come with version 12.

    Ian


    I was thinking more of your KW needs for future subject matter than of possibly future functionality enhancements in C1. In terms of search facilities for this sort of activity the way the search/filters capability is offered (ignoring the complex questions of some aspects of hierarchy perception and synonyms and how things work across different languages) what C1 offers is pretty much what most database search engines offer.

    There is no "but" syntax but you can look at including "does not contain" which offers much the same combination or even a little more flexibility although without the natural language logic. Also you have the case sensitivity to play with. So if you always use capital letters at the start of names (or, indeed, for all of a name) it makes the name easier to segregate from words that might use the same letters.

    That said it would be easier to derive searches by not just relying on KWs, useful as they can appear to be.

    Additional categorisations that are separate from KWs (as offered by the IPTC data fields for example) are extremely useful if one uses searches often enough to justify taking the time to set up the specific data fields available.

    The personal challenge here is to come up with a system that you can be confident will work well into the future with whatever you think you may find yourself throwing at it.

    That said if you find things change in the future a good structure now should make is relatively easy to re-engineer any changed requirements in the future.

    Does this help?

    Grant
    0

Post is closed for comments.