Skip to main content
Participant
January 9, 2007
Question

cannot edit xmp infor

  • January 9, 2007
  • 2 replies
  • 564 views
Hi,

We found that you cannot edit xmp information of files
if you do not own the file.
We get error "There was an error writing metadata to [filename]."

I tried all of the suggestion of this;
http://www.adobe.com/support/techdocs/331581.html

In our workflow, one person import files, and
other person edit the xmp information. They belong to
same group, and the permission of the files to open for them.

If we change the owner (ie. 'sudo chown' in terminal) you can
edit the info, but we don't want to give all users sudo
permission to change the owner. This is serious problem for us.
Does anybody know the way to edit the files that somebody
else imported?

Thank you,
junko
This topic has been closed for replies.

2 replies

Participant
January 9, 2007
> Have you you tried setting the file so that it has group write
> permission.
> chmod 664 filename.psd

I tried. Actually, I am using the panels which permission
to open everybody as the test (-rw-rw-rw-),
but I still get the error.

I made a command line script using XMP SDK, and it can update
the information. I also can update label and rating.
I am wondering if it is a bug of bridgeIt.

In the worst scenario, I have to make a new interface outside
Bridge to update the xmp data with SDK. I don't have time
to make the interface because of the deadline of the project,
and am really hoping there is any way to update it inside Bridge.

Thank you for the advice, anyways.

junko
Known Participant
January 9, 2007
junko_igarashi@adobeforums.com wrote:
> Hi,
>
> We found that you cannot edit xmp information of files
> if you do not own the file.
> We get error "There was an error writing metadata to [filename]."

Have you you tried setting the file so that it has group write permission.
chmod 664 filename.psd

Whoever imports/owns the file would set the permissions.

This would allow everyone in the group to edit, but no one outside of the group,
which is what I think you're asking for.

Using 'sudo chown' would be a little heavy handed.

-X