<p dir="ltr">There is a reason why database and image metadata shouldn't be out of sync...</p>
<p dir="ltr">If I'm not mistaken, image collection scan read metadata from images and update database. Image scan can be triggered by your changes on local filesystem and you will have all your data from database overwritten. </p>
<p dir="ltr">My first idea was to operate all changes on database only. After you're finished, use sync options for either undo all changes by reading from image or save all changes to image by triggering write to image metadata and delete obsolete tags.</p>
<p dir="ltr">Still need to read all suggestions, maybe I missed something. Until then, I'm working on user interface.</p>
<div class="gmail_quote">On Jun 25, 2013 9:20 PM, "Andrew Goodbody" <<a href="mailto:elfringham@gmail.com">elfringham@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Veaceslav,<br>
<br>
Bug 268688 <a href="https://bugs.kde.org/show_bug.cgi?id=268688" target="_blank">https://bugs.kde.org/show_bug.<u></u>cgi?id=268688</a> that is mentioned in the thread that Elle linked to contains a number of conflicting wishes. The part of your proposal that seems to address any of those wishes is where you offer to 'Write tags from database to image' and remove obsolete tags. I see this as a heavy handed maintenance operation that will not really fix the underlying issue.<br>
The way I would like the bug I would like to see resolved (that got merged into 268688) is when a change is made to the tags hierarchy (ie move or delete a tag) that will render images with applied metadata out of sync, to be offered 3 options or to have one of them selected in preferences:<br>
1) apply change only to database<br>
2) add change to a queue to be actioned later when it will update affected images<br>
3) apply change immediately to database and all affected images.<br>
Also please note that I am talking about applying a 'change' - this is not the same as syncing the database to the image metadata.<br>
<br>
Also I would like to see <a href="https://bugs.kde.org/show_bug.cgi?id=309598" target="_blank">https://bugs.kde.org/show_bug.<u></u>cgi?id=309598</a> resolved. And there should be a bug or wishlist somewhere about copying tags from one image to others.<br>
<br>
Good luck and all the best,<br>
Andrew<br>
<br>
On 25/06/13 11:18, Veaceslav Munteanu wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello,<br>
<br>
my name is Veaceslav and I will work on implementing a Tag Manager for<br>
digiKam as part of Google Summer of Code program.<br>
<br>
Here is my proposal:<br>
<br>
<a href="http://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/slavuttici/35001" target="_blank">http://www.google-melange.com/<u></u>gsoc/proposal/review/google/<u></u>gsoc2013/slavuttici/35001</a><br>
<br>
if you use tags a lot and find an important option that should be added,<br>
please let me know.<br>
<br>
Also, all your suggestions are really appreciated. It will help me to<br>
build a useful tool.<br>
<br>
Don't leave you suggestions until it's too late and lots of things must<br>
be rewritten.<br>
<br>
<br>
Cheers,<br>
<br>
Veaceslav<br>
<br>
<br>
______________________________<u></u>_________________<br>
Digikam-users mailing list<br>
<a href="mailto:Digikam-users@kde.org" target="_blank">Digikam-users@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/digikam-users" target="_blank">https://mail.kde.org/mailman/<u></u>listinfo/digikam-users</a><br>
<br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
Digikam-users mailing list<br>
<a href="mailto:Digikam-users@kde.org" target="_blank">Digikam-users@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/digikam-users" target="_blank">https://mail.kde.org/mailman/<u></u>listinfo/digikam-users</a><br>
</blockquote></div>