Do not create a label v This label is private

[peterpix]

Can anyone please help me with the difference in practice in the Metadata settings for a label between "Do not create a label" and "This label is private - Catalogue only"? In what situations might one use one or the other?

Peter

[Hert]

Do not create keyword for this label; The catalog label will not be written as a keyword in the metadata of the images that it is assigned to
This label is private; The label will never be written to the metadata, not even in the IDimage Core Schema.

I think I don't have to explain the first one.

You could use a private label for info that you don't want to have shared with anyone. For example catalog labels for customers that have purchased a certain picture.

[stevehughes]

Is there a way to make this selection inheritable to sub-labels?

Use case:
In my catalog I am using 'Places' for geo-tagging. I set a geo location on the catalog label and then assign the label to the images that were taken at that location. However I don't want the label name written as a keyword - I just want the GPS co-ords to be written to the image.

It appears that I can achieve this by setting the top-level 'Places' to be Private, and then everything under it also becomes private. This seems to do what I want, but if my database crashes I'll lose the label info. What I really want is to set the top level 'Places' to 'Do not create a keyword' and have that propagate down to everything under it.

Perhaps there is a better way to achieve my objective.

Thanks,
Steve

[Hert]

Setting the category to private is indeed what you're looking for. There's no option to set "do not create keyword" on a category level, but that would be the same as setting it to private.

This seems to do what I want, but if my database crashes I'll lose the label info

A private category isn't written to the image, neither are catalog labels that are set to not write keywords (which also means "private"). So I don't see how that differs.
Backups are to protect against loss

[G8DHE]

Hert, is the private data written to the ICS scheme data, I would assume not but never needed so far to use it?

[Hert]

If it would be written to ICS then it wouldn't be private, so the answer is "private labels are not written to ICS".

[stevehughes]

Thanks Hert. I had some fuzzy thinking going on there. You are right of course. Setting it to Private is the obvious and correct way to go.

I am noticing, with Places set to Private, that PSU is not writing the GPS info to the files unless I manually perform 'Write Metadata to File'. At least that's what I'm seeing with the latest build. I could be wrong but I don't think it behaved this way with whatever build I was previously running. Has something changed that would cause this?

Also, I am seeing that some of my 'Places' labels appear in italics, but I can't figure out why. What does this mean?

[Hert]

Changes are listed at https://whatsnew.idimager.com No sync changes.

Italic catalog label name means that it is a private label.

[stevehughes]

OK. It's just that not all the labels are in italics. The top-level 'Places' is, and some of the sub-labels, but not all.

[Hert]

I guess you've defined those as private catalog labels before making the top level category private.

[stevehughes]

Right you are sir.

I set the category to public, then reset those labels, then set the category back to private. Now the entire 'Places' tree is italicised.

However, I then added another label under Places and it appeared as non-italicised, even though it is obviously private. Setting 'Places' to public and back to private fixed that so that the entire tree is again italicised.

It's only a cosmetic thing but I mention it anyway.