• Max@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    11 months ago

    One of the things I really like about digikam is the matching of the disk layout with the album structure. This makes it really easy to have other programs also interact with my photo library in a way that’s near impossible if you instead have an internal photo database.

    Tags work great for me for multi-categorization. What feels clunky about them in your workflow? You’re even allowed to have a tag hierarchy.

    • tcgoetz@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      11 months ago

      In my workflow tags == keywords which are orthogonal to albums. Keywords describe a photo and get published with the photo. One photo can be in multiple albums like Flickr Photosteam (published to Flickr), “Zion Vacation” (event album, published to Piwigo for friends and family consumption), “2022 Year in Photos” (yearly highlight album), “Favorite Landscapes”. Photos are in a date hierchary on disk.

      • Max@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        11 months ago

        That make sense. I would use tags like that:

        • Flickr Published

        • year roundup/2022

        • type/Landscapes

        • type/Portraits

        • events/trips/Zion 2022

        • content/food

        • content/animals

        I actually do event level as my on-disk sorting. And then tag for stuff that’s not that. But I think it would work pretty well to do the event sorting under tags as well.

        Then I rate my favorite photos, usually using the green approved, not stars. But stars would work too. Then if you want to find say, favorite landscapes, the digikam interface makes it really easy to do so.

        I’m not sure if you can select what tags get written into the image, but if you can, you might be able to exclude certain parts of the hierarchy, and only include content/ or type/ subhierarchies