maxwellfire

@[email protected]

This profile is from a federated server and may be incomplete. View on remote instance

maxwellfire ,

I think upstate is forecast to be one of the clearer places

kde , (edited ) to KDE
@kde@floss.social avatar

digiKam, KDE's powerful photo management application, releases version 8.2.0.

This version brings better support for more languages (up to 61 in the works), and an improved version on Windows.

Look forward to automatic tagging based on content analysis and deep-learning. This feature is currently in pre-production.

https://www.digikam.org/news/2023-12-03-8.2.0_release_announcement/

@kde

maxwellfire ,

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.

maxwellfire ,

That make sense. I would use tags like that:

`Flickr PublishedYear roundup/2022type/Landscapestype/PortraitsEvents/Trips/Zion 2022content/foodcontent/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

maxwellfire ,

I think you want something like s*(((?!versd).)*)s*

See regexr.com/7jbvk

Basically this consumes all characters between parentheticals with whitespace unless the next character set in the parentheticals is ver followed by a number. Now this uses a negative lookahead which might not be supported by the engine that krename is using. You can also explicitly construct the group to not match, but that’s rather painful, see here

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • All magazines