Manually import versions

[Tom Vincent]

I'm currently in the process of migrating from Picasa. I'd like to
import the original image *and* any edits as a "version" in Digikam.

I've saved all edits to file (using this [search for jpg][1]
approach), which backs up the originals into a hidden
".picasaoriginals" directory.

Can I retain the linkage between the original and edited version
during import to Digikam? I've tried a naive approach of simply
appending "_v1" to the edited version's filename, but Digikam treats
the two files independently.

 [1]: http://www.google.com/support/forum/p/Picasa/thread?tid=187b49a46dacacaf&hl=en
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[hajo]

Tom Vincent wrote

[...]
I'd like to import the original image *and* any edits as a "version" in Digikam.
[...]
Can I retain the linkage between the original and edited version
during import to Digikam? I've tried a naive approach of simply
appending "_v1" to the edited version's filename, but Digikam treats
the two files independently.
[...]

That question never got an answer apparently. Anyone out there who knows how to do this? For me, I'd like to process RAWs with an external RAW editor since it provides more flexibility than DigiKam's. Naturally, I'd like to have the processed file a revision of the RAW. Yes, I could group them instead, but wouldn't it make more sense to have it a revision instead?

[Gilles Caulier-4]

digiKam has version implemented. This include RAW process workflow.

version create new file with filename postfix, as _v1, _v2, ex...

But all versioning stuff is registered in XMP digiKam namespace, including all operation done in editor to patch image... This is not a simple file renaming (:=)))...

http://www.exiv2.org/tags-xmp-digiKam.html

Gilles Caulier

2013/5/2 hajo <[hidden email]>

Tom Vincent wrote
> [...]

> I'd like to import the original image *and* any edits as a "version" in
> Digikam.

> [...]

> Can I retain the linkage between the original and edited version
> during import to Digikam? I've tried a naive approach of simply
> appending "_v1" to the edited version's filename, but Digikam treats
> the two files independently.

> [...]

That question never got an answer, apparently. Anyone out there who knows
how to do this? For me, I'd like to process RAWs with an external RAW editor
since it provides more flexibility than DigiKam's. Naturally, I'd like to
have the processed file a revision of the RAW. Yes, I could group them
instead, but wouldn't it make more sense to have it a revision instead?



--
View this message in context: http://digikam.1695700.n4.nabble.com/Manually-import-versions-tp3714496p4663467.html
Sent from the digikam-users mailing list archive at Nabble.com.

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Remco Viëtor]

On Friday 03 May 2013 11:44:23 Gilles Caulier wrote:
> digiKam has version implemented. This include RAW process workflow.
>
> version create new file with filename postfix, as _v1, _v2, ex...
>
> But all versioning stuff is registered in XMP digiKam namespace,
including
> all operation done in editor to patch image... This is not a simple file
> renaming (:=)))...
>
> http://www.exiv2.org/tags-xmp-digiKam.html

Not quite on subject, but is there a way to 're-use' that processing
information on the same or another image? That would allow easy identical
processing (batch?) of a group of images.

Remco
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-4]

2013/5/3 Remco Viëtor <[hidden email]>

On Friday 03 May 2013 11:44:23 Gilles Caulier wrote:
> digiKam has version implemented. This include RAW process workflow.
>
> version create new file with filename postfix, as _v1, _v2, ex...
>
> But all versioning stuff is registered in XMP digiKam namespace,
including
> all operation done in editor to patch image... This is not a simple file
> renaming (:=)))...
>
> http://www.exiv2.org/tags-xmp-digiKam.html

Not quite on subject, but is there a way to 're-use' that processing
information on the same or another image? That would allow easy identical
processing (batch?) of a group of images.

Not yet, but it's planed. This is the goal for the future...

Gilles Caulier

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Marcel Wiesweg]

>
> Not quite on subject, but is there a way to 're-use' that processing
> information on the same or another image? That would allow easy identical
> processing (batch?) of a group of images.

backend is there, UI is not
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Marcel Wiesweg]

>
> That question never got an answer, apparently. Anyone out there who knows
> how to do this? For me, I'd like to process RAWs with an external RAW editor
> since it provides more flexibility than DigiKam's. Naturally, I'd like to
> have the processed file a revision of the RAW. Yes, I could group them
> instead, but wouldn't it make more sense to have it a revision instead?

As Gilles already pointed out, it's not trivial as history is stored as XML in
the metadata.
What I want to have at some point it
1) Manual creation of these relations (e.g., for single files edited in Gimp
2) An automated tool to group RAW+JPEG or, more general, create relations by
heuristics typically based on filename

Marcel
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[hajo]

Marcel Wiesweg wrote

What I want to have at some point it
1) Manual creation of these relations (e.g., for single files edited in Gimp
2) An automated tool to group RAW+JPEG or, more general, create relations by
heuristics typically based on filename

Tnx for your replies, guys! Understand the issues. I meanwhile figured that I can at least group variants automatically "by time" and that brought me to another thought -- since nowadays about all editors preserve EXIF/IPTC/.. data, could it make sense that DigiKam sets a custom EXIF field when the user chooses "edit with...". If then a new file appears in the directory, it could be identified as a new version since it'd contain the same (unique) EXIF field. I'm mainly thinking about RAW conversion (darktable) for my case.
But yes, an intelligent algorithm based on filenames plus a manual intervention are certainly desireable,..