Bug 338048

Summary:	Separate Tags in Public and Private for Export
Product:	[Applications] digikam	Reporter:	Plasticbeach
Component:	Tags-Engine	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED INTENTIONAL
Severity:	normal	CC:	caulier.gilles
Priority:	NOR
Version:	4.1.0
Target Milestone:	---
Platform:	Other
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=181708 https://bugs.kde.org/show_bug.cgi?id=196484 https://bugs.kde.org/show_bug.cgi?id=129132 https://bugs.kde.org/show_bug.cgi?id=336164
Latest Commit:		Version Fixed In:	4.3.0
Sentry Crash Report:

Description Plasticbeach 2014-08-05 08:34:50 UTC

Here's my Idea:

1. Make it possible to mark Tags as Public or private (and more categories)
2. Make it possible to write only e.g. "Public" Tags to images.
3. Export plugins would be able to add only public tags on export
(4. When importing tags from new images ask whether they should be assigned a new category)

That way My private and Working-Tags like "Print" "guddle wuddle":] and others have no chance landing on flickr. 

Of course we could have even more categories than "public" and "private". (I've just updated from 2.5 to 3.3 and see there's something like child and adult that seems to be a a similar technology for a different purpose)

And that would make exporting so wunderfull because I could export just the right tags for just the right purpose.
YEAH
And my band would get some photos with the right tags for songs and locations attached while some of the same photos are being uploaded to flickr with erm - other tags. Well - what a "real life" example :]

As 4.) suggets importing tags by importing images from other persons wouldn't mess up my private list of tags anymore because I could just put them in a new category.

Well, Thanks for reading

Comment 1 caulier.gilles 2014-08-05 13:51:50 UTC

In your workflow, using a private tags for printing is a bad idea.

Use Color Labels with a specific color for items to print. 

With digiKam 4.2.0, you can access quickly to Color Labels by a dedicated tree-view.

In digiKam Metadata setup, you can disable Color Labels tags writing in image. Color Labels become private in this way...

Gilles Caulier

Comment 2 caulier.gilles 2014-08-05 13:54:41 UTC

See release announcement for digiKam 4.2.0 :

https://www.digikam.org/node/715

You will see also that Color Labels are now available as virtual album selection view from Export tools.

Gilles Caulier

Comment 3 Plasticbeach 2014-08-06 09:00:03 UTC

Hey, Thanks  that's a nice workaround for the printing case and some other workflow cases.

But I've got quite a lot of other tags that I want to have private and I can't remember all their functions by colors.
There's simply not enough colors, too.

And what's really a hazzle to me is that I have no control about tags that are imported through other persons pictures.

Comment 4 caulier.gilles 2014-08-06 09:04:07 UTC

I will be more clear...

There is no plan to separate tags in 2 sections as public and private. Use Labels properties...

Gilles Caulier

Comment 5 Plasticbeach 2014-08-06 10:32:58 UTC

Well fair enough - this is a wish and i'm not asking you to do it.

I'd just like the idea to be kept open for the future or the next summer of code or whatever.

I now found a very similar idea reported five years ago and the technical suggestion to have it as a flag for every tag in the db sounds like a solid solution for me.

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

Label is actually a pretty good name for a "fast tag" now it would be really favorable that every tag could be a label.

Thanks for digikam and greets