11 comments on “New Features in digiKam 2.0: XMP Sidecar

  1. This breaks multi-user environments. Take an example: Pupils are given photos as read-only files and the directories obviously have to be read-only too. So this totally fails right from the beginning, along with the writing of metadata to image files, by the way (which is a horrible thing for managing backups). And even in writable places this means chaos, because which users sidecar file will get precedence will be purely random (ignoring missing permissions to access it any way).

    Darktable went the same way and it took them some time to understand it’s a really bad idea. Put the sidecars in a user-definable place somewhere in ~ or keep them in an sql and give an explicit option to export them, so they can easily be sent to another user for sharing the editing stack (which I consider a good idea).

    • Hi nn,

      I think there are as many people complaining about the files being in the same directory as there are people who complain about the metadata being stored only in the database or the files in some other directories, because in this case managing the files with simple tools like Dolphin will break, as the references to the files have to be updated.

      Anyway, sidecar files are an optional feature, so if it does not fit your way of working, you can at least turn it off.

      Michael

      • i enable XMP side car for read only files…which are basically all the raw files that are in collection…however i also have the issue of them being in the same directory as the pictures….an option to keep them somewhere else or making them hidden would be a great choice…may be that is something that could be implemented in the future development!!

  2. Finally Digikam gets the sidecar XMP. :)

    To my mind it’s a great feature. I want to tag my pics but I want to store the tags outside my pictures (because of privacy issues, e.g. on upload or sharing). Also I want to stay flexible for using my tags with different tools / plattforms, that is why I want to store the tags outside of a specific db. So XMP sidecar is the logical solution.

    Thank you for your work guys. Now I can finally migrate my pics to Digikam ;)

  3. Maybe not the place but I will ask anyway: I shoot raw and usually convert to dng and tag the dngs. Raws go off to a backup untagged (not great). Dngs I want to publish go to jpeg, which brings the tags from the dngs along (don’t have to re-tag). Upload to flickr-like sites brings along tags too for those kinds of sites. Curious how work path could change with sidecars- if tagging raw, then converting to dng (necessary for some software I use at this point), will that bring along the tags, and also to subsequent jpgs? Uploading a jpeg to a site like flickr? Or do the sidecars at some point have to get written to the image? many thanks.. I could ask this on the digikam listserv but what the hey.. have to resubscribe to do that.

  4. Hi

    I’m using Digikam and Darktable. Will Digikam destroy XMP files from Darktable?

    Thank you

  5. Thank you a lot Dmitri!!! I had exactly the same doubt. But I’m in trouble with Digikam. After editing in ShowPhoto a raw file and export it, the original raw file doesn’t not appear in Digikam!!! (but it is there fortunately). Is this a bug?????

    Thank you

    • I had the same problem, and it took me hours to figure out what was going on. The fix turned out to be very simple. Go to Settings -> Configure digiKam -> Editing Images and make sure that the Always show original images option in the In main view section is enabled.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s