Skip to Main Content
Improve Capture One

Request a new feature, or support for a camera/lens that you would like to use in Capture One.

Status Awaiting review
Workspace Feature requests
Categories Capture One Pro
Created by Guest
Created on Jan 18, 2024

Faster rename of keywords

What problem do you see this solving?

Renaming keywords in a larger catalog, especially top-level keywords in a hierarchy, takes unbearably long.

When was the last time you were affected by this lack of functionality, or specific tool?

Everytime I try to rename a toplevel keyword in a larger catalog.

Current workaround

Are you using any workarounds or other solutions to achieve your goals in Capture One?

This could greatly be improved using SQLite's replace function on the corresponding database table (ZVARIANTMETADATA) and field (ZCONTENT_KEYWORDS).

Tests proved that this way I could reduce renaming a toplevel keyword in a 10000 images catalog from over 1 hour! to 0.5 milliseconds!!!!

  • Guest
    Reply
    |
    Jan 18, 2024

    Actually, I haven't contacted support yet, since it occured to me this was a common problem... Maybe will do that right away.

  • Thomas Kyhn
    Reply
    |
    Jan 18, 2024

    It sounds like it. Have you contacted support?

  • Guest
    Reply
    |
    Jan 18, 2024

    I'm on a windows 11 machine, 16GB RAM, hence the progressbar. I sync XMP only manually as well, so there must be another obstacle. 

  • Thomas Kyhn
    Reply
    |
    Jan 18, 2024

    I definitely agree that this needs improvement. Renaming a keyword, any keyword, shouldn't cause Capture One to become unresponsive.

    I don't see a progress bar when renaming keywords, only the spinning beachball (macOS) while Capture One is unresponsive. Perhaps the differences have to do with metadata settings? I only sync XMP sidecar files manually.

     

  • Guest
    Reply
    |
    Jan 18, 2024

    Well, since Capture One is showing a modal progressbar while performing this task, yes, it is unresponsive so to say. A quick check tells me that the keyword renamed was used only in 55% of the images, but since all images must be traversed it travels the whole catalog no matter what.

    Hearing that renaming a top-level keyword in a catalog twice as big within only 18 seconds concerns me though. But even this would benefit from using a simple SQL function at hand, don't you agree?

  • Thomas Kyhn
    Reply
    |
    Jan 18, 2024

    It takes over 1 hour for Capture One to rename a top-level keyword in a catalogue containing 10k images? I assume that during this time Capture One is unresponsive?

    I've had and still have plenty of trouble with Capture One becoming unresponsive regularly, but here it only takes about 18 seconds to rename a top-level keyword in a catalogue containing 22k images (and this is a catalogue with lots of hierarchical keywords).

  • +1