https://bugs.kde.org/show_bug.cgi?id=308366
Bug ID: 308366 Severity: wishlist Version: 2.8.0 Priority: NOR Assignee: [hidden email] Summary: digiKam as a "picture management program" should extend management-capabilities Classification: Unclassified OS: Linux Reporter: [hidden email] Hardware: Ubuntu Packages Status: UNCONFIRMED Component: Database Product: digikam digiKam offers a serious number of picture relevant capabilities. It offers ways to incorporate pics ("import"), dealing with pictures (panoramas, versioning, white + coulour management etc.) and export options galore. When I work with my pics collection, I came across a topics, digiKam can _not_ deal with at all (as much as I understand): Many times, I need to derive several different versions of _one_ original picture. This can extend to different sizes, colours (white balancing, black-and-white), with or without signature (copyright information) and as many other possibilities, as digiKam offers the user. DigiKam sould be able to take care of _all_ versions, one drives from a specific picture. I addressed this issue to "database" , as I assume this could be the key role for all management activities Reproducible: Always Steps to Reproduce: 1. just run digiKam - missing function 2. 3. Actual Results: Right know, the users forced to take care of all his pictures manually. This is - time consuming (because of manual checking takes enormous time), - defective (as manual work is risky) - causes the risk of double work (when not beeing aware, that a pic can be locatetd on more than one location) - can affect the basics of databases, as this affects nomalize requirement (to avoid doublettes) ... and more Expected Results: digiKam should handle any version of everey pic of a collection consitently and thouroghly. When searchuing (or getting across) one picture, digiKam should show immediatelly _all_ existent versions of this pic. If so, one would be lead not to produce similar or even identicall version or a second time. This issue could connected to versioning and...? From my standpoint, this is a serious wish, to extend professionality of a pic management program. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
https://bugs.kde.org/show_bug.cgi?id=308366
--- Comment #1 from Axel Krebs <[hidden email]> --- excuse me- I never got a proof for arrival... Axel -------- Original-Nachricht -------- Betreff: [Bug 308366] New: digiKam as a "picture management program" should extend management-capabilities Datum: Sun, 14 Oct 2012 11:11:28 +0000 Von: Axel Krebs <[hidden email]> Antwort an: [hidden email] An: [hidden email] https://bugs.kde.org/show_bug.cgi?id=308366 Bug ID: 308366 Severity: wishlist Version: 2.8.0 Priority: NOR Assignee: [hidden email] Summary: digiKam as a "picture management program" should extend management-capabilities Classification: Unclassified OS: Linux Reporter: [hidden email] Hardware: Ubuntu Packages Status: UNCONFIRMED Component: Database Product: digikam digiKam offers a serious number of picture relevant capabilities. It offers ways to incorporate pics ("import"), dealing with pictures (panoramas, versioning, white + coulour management etc.) and export options galore. When I work with my pics collection, I came across a topics, digiKam can _not_ deal with at all (as much as I understand): Many times, I need to derive several different versions of _one_ original picture. This can extend to different sizes, colours (white balancing, black-and-white), with or without signature (copyright information) and as many other possibilities, as digiKam offers the user. DigiKam sould be able to take care of _all_ versions, one drives from a specific picture. I addressed this issue to "database" , as I assume this could be the key role for all management activities Reproducible: Always Steps to Reproduce: 1. just run digiKam - missing function 2. 3. Actual Results: Right know, the users forced to take care of all his pictures manually. This is - time consuming (because of manual checking takes enormous time), - defective (as manual work is risky) - causes the risk of double work (when not beeing aware, that a pic can be located on more than one location) - can affect the basics of databases, as this affects normalize requirement (to avoid doublettes) ... and more Expected Results: digiKam should handle _any_ version of everey pic of a collection consistently and thouroghly. When searching (or getting across) one picture, digiKam should show immediatelly _all_ existent versions of this pic. If so, one would be lead not to produce similar or even identical version or a second time. This issue could related to versioning and...? From my standpoint, this is a serious wish, to extend professionality of a pic management program. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Axel Krebs
https://bugs.kde.org/show_bug.cgi?id=308366
Gilles Caulier <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Database |Versioning CC| |[hidden email] --- Comment #2 from Gilles Caulier <[hidden email]> --- Axel, Requests in this file are confuse... This sound like relevant to versioning support, already implemented since 3.x release... Right ? Gilles Caulier -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Axel Krebs
https://bugs.kde.org/show_bug.cgi?id=308366
Gilles Caulier <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |WAITINGFORINFO --- Comment #3 from Gilles Caulier <[hidden email]> --- We need a better description here as ask in my previous comment... Gilles Caulier -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Axel Krebs
https://bugs.kde.org/show_bug.cgi?id=308366
--- Comment #4 from Gilles Caulier <[hidden email]> --- New digiKam 4.11.0 is available : https://www.digikam.org/node/740 Can you reproduce the problem with this release ? Gilles Caulier -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Axel Krebs
https://bugs.kde.org/show_bug.cgi?id=308366
--- Comment #5 from Gilles Caulier <[hidden email]> --- digiKam 4.12.0 is out : https://www.digikam.org/node/741 We need a fresh feedback using this release please... Thanks in advance. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Axel Krebs
https://bugs.kde.org/show_bug.cgi?id=308366
[hidden email] changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|WAITINGFORINFO |INVALID --- Comment #6 from [hidden email] --- No feedback. Closed -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Free forum by Nabble | Edit this page |