This question is answered. Helpful answers available: 2. Correct answers available: 1.


Permlink Replies: 39 - Pages: 3 [ Previous | 1 2 3 ] - Last Post: 15 Aug 24, 13:42 Last Post By: phil44
JeffTucker

Posts: 8,431
Registered: 31-Jan-2006
Re: Please keep comments when an image is overwritten
Posted: 14 Aug 24, 20:05   in response to: phil44 in response to: phil44
 
  Click to reply to this thread Reply
The difference is that when you add the keywords in the Description field on the right, the keywords are stored in the image's xmp metadata, but not in the image's .info file. Then when you reopen the project, if you haven't chosen xmp as a source under Advanced > Metadata > Sources, the keywords are "missing."

Finally, image metadata are wiped out when the image file is replaced, so if the xmp field is the only place the keywords are stored, they're well and truly gone.

I'll leave that one to David to sort out. The keywords should, I think, always be stored in the .info file, as well as the xmp field. The title is stored in both places.
phil44

Posts: 103
Registered: 18-Jun-2010
Re: Please keep comments when an image is overwritten
Posted: 15 Aug 24, 09:41   in response to: JeffTucker in response to: JeffTucker
 
  Click to reply to this thread Reply
JeffTucker wrote:
The difference is that when you add the keywords in the Description field on the right, the keywords are stored in the image's xmp metadata, but not in the image's .info file. Then when you reopen the project, if you haven't chosen xmp as a source under Advanced > Metadata > Sources, the keywords are "missing."

Finally, image metadata are wiped out when the image file is replaced, so if the xmp field is the only place the keywords are stored, they're well and truly gone.

I'll leave that one to David to sort out. The keywords should, I think, always be stored in the .info file, as well as the xmp field. The title is stored in both places.


Thanks for the clarification, Jeff, I didn't know about this difference.

In my opinion, in the UI world, it's a good thing to have multiple different paths for the same action (e.g. File/Open using the menu bar or a right mouse click). However, having two similar but different actions (here, entering keywords), without a visual distinction in the UI, can only confuse the user and be a source of problems and/or errors.

The ideal would be either to have the same behavior for both ways of entering the keywords (and probably as you said to modify the .info file and the xmp field), or to have two different actions, but it should be clearly visible in the UI.
RobM

Posts: 3,963
Registered: 4-Aug-2006
Re: Please keep comments when an image is overwritten
Posted: 15 Aug 24, 11:28   in response to: phil44 in response to: phil44
 
  Click to reply to this thread Reply
There is a preference setting that controls writing xmp data to images too. See Edit>Description which has a link to the preference setting - the default is set to checked.
davidekholm

Posts: 3,605
Registered: 18-Oct-2002
Re: Please keep comments when an image is overwritten
Posted: 15 Aug 24, 12:02   in response to: RobM in response to: RobM
 
  Click to reply to this thread Reply
I see, yes, there's a slight difference there. In Edit view, the "Description" section considers xmp fields only. I don't know whether I'm motivated to aligning that behaviour as well...
phil44

Posts: 103
Registered: 18-Jun-2010
Re: Please keep comments when an image is overwritten
Posted: 15 Aug 24, 12:05   in response to: RobM in response to: RobM
 
  Click to reply to this thread Reply
I don't know what to think about this...

I did a test with Write xmp metadata to files unchecked: the keywords entered in the Description field are always written in the image metadata, and nothing is stored in the .info file :-(

Where are the keywords theoretically stored when "Write xmp metadata to files" is unchecked?
phil44

Posts: 103
Registered: 18-Jun-2010
Re: Please keep comments when an image is overwritten
Posted: 15 Aug 24, 12:08   in response to: davidekholm in response to: davidekholm
 
  Click to reply to this thread Reply
davidekholm wrote:
I see, yes, there's a slight difference there. In Edit view, the "Description" section considers xmp fields only. I don't know whether I'm motivated to aligning that behaviour as well...

It might be good if the section title specified that it only concerns Xmp fields :-)
davidekholm

Posts: 3,605
Registered: 18-Oct-2002
Re: Please keep comments when an image is overwritten
Posted: 15 Aug 24, 12:13   in response to: phil44 in response to: phil44
 
  Click to reply to this thread Reply
phil44 wrote:

It might be good if the section title panel specified that it only concerns Xmp fields :-)

True.
RobM

Posts: 3,963
Registered: 4-Aug-2006
Re: Please keep comments when an image is overwritten
Posted: 15 Aug 24, 12:27   in response to: davidekholm in response to: davidekholm
 
  Click to reply to this thread Reply
davidekholm wrote:
phil44 wrote:

It might be good if the section title panel specified that it only concerns Xmp fields :-)

True.

Instead of ‘Description’ maybe ‘XMP data’ and if the preference setting is unchecked then the fields in that panel should be disabled.
JeffTucker

Posts: 8,431
Registered: 31-Jan-2006
Re: Please keep comments when an image is overwritten
Posted: 15 Aug 24, 13:39   in response to: RobM in response to: RobM
 
  Click to reply to this thread Reply
RobM wrote:
Instead of ‘Description’ maybe ‘XMP data’ and if the preference setting is unchecked then the fields in that panel should be disabled.

Yes, this. "Description" also conflicts with the name of a well-known metadata field for folders. Confusing.
phil44

Posts: 103
Registered: 18-Jun-2010
Re: Please keep comments when an image is overwritten
Posted: 15 Aug 24, 13:42   in response to: RobM in response to: RobM
 
  Click to reply to this thread Reply
Instead of ‘Description’ maybe ‘XMP data’ and if the preference setting is unchecked then the fields in that panel should be disabled.

+ 1
Legend
Forum admins
Helpful Answer
Correct Answer

Point your RSS reader here for a feed of the latest messages in all forums