[Bug 181708] New: [WISH] "fast" tags, that are not written to the image (only to database)

http://bugs.kde.org/show_bug.cgi?id=181708

           Summary: [WISH] "fast" tags, that are not written to the image
                    (only to database)
           Product: digikam
           Version: unspecified
          Platform: Gentoo Packages
        OS/Version: unspecified
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: general
        AssignedTo: [hidden email]
        ReportedBy: [hidden email]


Version:            (using KDE 4.1.96)
Installed from:    Gentoo Packages

I suggest to add tags that are not written to the meta-data of the image, but
only to the datase.

At the moment it is only possible to write all or no tag to the images.

As tags can be used for a lot of different purposes and a lot of them need tags
only temporarely (e.g. tagging images to create a slideshow), it would be nice
that these tags are not changing the image.

On the other hand, tags like Persons etc. should be stored in the image also to
be able to access the tags from other applications and for digikam-independent
backup.


--
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
------- 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

[Gilles Caulier-4]

http://bugs.kde.org/show_bug.cgi?id=181708


Gilles Caulier caulier gilles gmail com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|general                     |Metadata
            Version|unspecified                 |0.10.0-svn




--- Comment #1 from Gilles Caulier <caulier gilles gmail com>  2009-01-24 09:01:05 ---
the proposal will make complex tag<=>metadata management. This have a lots of
side effect everywhere.

My viewpoint : WONTFIX

Andi, Marcel ?

Gilles Caulier


--
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
------- 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

http://bugs.kde.org/show_bug.cgi?id=181708





--- Comment #2 from Ian Hubbertz <kde_bugs hubbertz de>  2009-01-24 10:33:34 ---
Hmm. Couldn't this be implemented by adding a flag to every tag in the database
whether to write it to the image or not?

The flag could be inherited from parent tag on tag creation, so in daily use it
would be quite simple to use:

Just add a tag(-category) like "marker", set the flag and then all sub-tags
will have the flag set, too.


For READING tags from imported images the flag can be ignored - if the same tag
is already in the image, just write it to database.


--
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
------- 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

[Marcel Wiesweg]

http://bugs.kde.org/show_bug.cgi?id=181708


Marcel Wiesweg marcel wiesweg gmx de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]




--- Comment #3 from Marcel Wiesweg <marcel wiesweg gmx de>  2009-01-24 11:16:01 ---
We can keep this bug for the future, if we should update the tags db schema at
some time we can think about this again. I faintly remember a similar wish
where certain tags were meant for publishing, others for private use.


--
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
------- 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

http://bugs.kde.org/show_bug.cgi?id=181708





--- Comment #4 from Mikolaj Machowski <mikmach wp pl>  2009-01-24 11:27:25 ---
It could be "fixed" by workaround: export plugin which will clear (or edit, or
apply) metadata by choice.

Such feature could also be not special plugin but some widget(?) in many other
plugins where pictures are exported from collection.


--
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
------- 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=181708





--- Comment #5 from Ian Hubbertz <kde_bugs hubbertz de>  2009-03-28 02:44:35 ---
At the moment I'm tagging and sorting photos of my last holiday and I am
remembered how useful this feature would be.

Tags are very useful to mark photos for a short time for further processing.

A concrete example: I'm geotagging all the photos, but have no track for some
time (inside building, battery empty, gps tracker crashed), so I use the
korrelator again, but with huge values for time gap.

To find the fotos, I first do a GPS search for the holiday area, tag all photos
as "Geotagged", then switch back to my album, activate "Geotagged" tag filter,
select all photos, deactivate the Geotagged filter, invert selection, tag all
selection photos with non_geotagged, use the correlator again and then manually
check all photos with "non_geotagged" tag if the location is correct.

Finally, I remove the geotagged and non_geotagged tags from the images.

Tagging and especially untagging the photos takes a lot of time, (for example
untagging all 383 photos took more than 4 minutes for me), because of the write
access to the jpg files.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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

[Sherwood Botsford-3]

https://bugs.kde.org/show_bug.cgi?id=181708


Sherwood Botsford <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]




--- Comment #6 from Sherwood Botsford <sgbotsford gmail com>  2009-04-05 18:11:59 ---
I agree with original poster.  There are lots of ways to use tags that are not
specific to a picture but are useful to collections of pictures.

One way to solve this would be to run two databases:  One is PICTURE meta data.
One is DIGIKAM meta-data.  

Digikam meta-data examples:
Tags can get out of hand if you use lots of them. Tag sets could be define for
the collection level. So the tag-tree would have the option:  Show this branch
only for this album.

Slideshow tags.  
If you work in PR or are a public speaker, you will have BUNCHES of slideshows
for different purposes. And you are adding/subtracting stuff to them all the
time.  If you can tag for "Church group speech" "Kiwanis" "Outdoor Ed"  Sure
you can use regular tags for this, but those tags may not be best in a picture.


Workflow tags.
Several programs I've run into have tag sets that reflect the stage in the
workflow.  E.g.
Pix come in and are assigned a tag unviewed.
The act of viewing it once changes it to viewed.
After going through the entire collection, and chucking the duds, the status
for every pic can be set to "culled"

Set tags.  We all do it.  We take 50 pix of something, chuck 30.  Of the
remaining 20, there are 2 sets of 6 and one set of 8 that are essentially
duplicates, but you don't want to chuck them, because they are all good.

So you mark them as a set.  Pick one as canonical for the set.  In thumbnail
view this shows up as a stack of slides in one corner.  This is code for, "This
slide has a bunch of almost identical siblings.

If possible sets should be nestable.

(This sort of thing is has great power for a commercial user.  A good way to
prove that you are the original owner of a picture is the ability to produce
shots from the same session.  This would be very hard to fake.)

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=181708


Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|0.10.0-svn                  |0.10.0




--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=181708


Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]




--- Comment #7 from Gilles Caulier <caulier gilles gmail com>  2011-12-17 09:58:36 ---
Marcel,

What's the status of this file with 2.x serie ?

Gilles Caulier

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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

[Marcel Wiesweg]

https://bugs.kde.org/show_bug.cgi?id=181708





--- Comment #8 from Marcel Wiesweg <marcel wiesweg gmx de>  2011-12-25 14:35:58 ---
not implemented...
In principle, there is no problem to mark a tag as "dont write to the picture",
it's easy to implement in the database
Another point is "deferred writing of metadata to pictures", discussed in
227814 and 268688

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=181708


Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[WISH] "fast" tags, that    |"fast" tags, that are not
                   |are not written to the      |written to the image (only
                   |image (only to database)    |to database)




--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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

[julien.t43+kde]

https://bugs.kde.org/show_bug.cgi?id=181708

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #9 from [hidden email] ---
My view would be having "internal" tags which you could defined with following
properties:
- never written to file (image meta or xmp)
- never exported (picasa, flickr & co)

As an example for me, I'm using the lock function of my Nikon D90 as a way to
pre-rate pictures on camera and my import script transform the "lock" (just
read-only fat32 attribute) in an exif rate of 1 with a tag d90lock, which I
keep but obviously don't want when exporting albums & co.

The problem with deferred writing is: are you using internal/fast tags only
temporarily or do you want to keep them. if the latter, at some point, you will
enable meta writing and write them wether you wanted it or not.

--
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

[Jürgen Karbach]

https://bugs.kde.org/show_bug.cgi?id=181708

Juergen Karbach <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #10 from Juergen Karbach <[hidden email]> ---
I agree to Mikolay
"It could be "fixed" by workaround: export plugin which will clear (or edit, or
apply) metadata by choice. Such feature could also be not special plugin but
some widget(?) in many other plugins where pictures are exported from
collection."

I won't call it workaround, because It wouldbe the smarter solution.
As a routine, which can be used by every export-plugin with it's own preset
data.
So you can store all the metadata in the database; with the affect of
increasing workflow speed.

If the digiKam-team solves this wish in this way, it would be great to make the
preset data URL / mailaddress depending. So you will provide different presets
for the same gallery provider (e,g, private / public) or receiving adress (e.g.
customer / WordPress-workaround by Dimitri Popov).

--
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

[Hans-Peter huth]

https://bugs.kde.org/show_bug.cgi?id=181708

Hans-Peter <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #11 from Hans-Peter <[hidden email]> ---
Another aspect is that changes in meta data may cause changes in the pictures,
so they will be backed up (is this correct english?) the next time. Having
those fast tags would avoid this.

HP

--
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

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=181708

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|"fast" tags, that are not   |Add fast tagging feature
                   |written to the image (only  |that only write to database
                   |to database)                |

--
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

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=181708

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Add fast tagging feature    |HUB : add fast tagging
                   |that only write to database |feature that only write to
                   |                            |database

--
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

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=181708

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Metadata                    |Metadata-Hub

--
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

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=181708

Veaceslav Munteanu <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
   Version Fixed In|                            |5.0.0
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |veaceslav.munteanu90@gmail.
                   |                            |com

--- Comment #12 from Veaceslav Munteanu <[hidden email]> ---
The feature is present in Digikam 5.0.0 and it is called Lazy Syncronization,
which can be enabled in Metadata Settings.

--
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