Feature request: Custom XMP namespaces

Bug #549496 reported by Yann Hamon
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pyexiv2
Fix Released
Wishlist
Olivier Tilloy

Bug Description

Hello, I would need to create my own XMP namespace to add custom tags to my photos. I didn't manage to figure out how to do it with pyexiv2, I keep getting invalid key exceptions, so I guess it is not possible to do it yet, or am I just missing something?
I manage to read custom tags though.

Is this a feature that could be implemented?

Revision history for this message
Yann Hamon (yannh) wrote :
Revision history for this message
Olivier Tilloy (osomon) wrote :

Indeed, this feature is not supported yet and would be nice to have.

Changed in pyexiv2:
importance: Undecided → Wishlist
status: New → Triaged
Revision history for this message
Thomas Hirsch (fwd-launchpad-20-ravn) wrote :

As far as I could see, this is already supported in exiv2 - it mainly requires the wrapping of the namespace registration methods, after which the current methods should be able to read/write tags in a custom XMP namespace:

    static void registerNs (const std::string &ns, const std::string &prefix)

Is there any news about that in the current versions? I would like to add my voice to the wishlist motion. :)

Revision history for this message
Olivier Tilloy (osomon) wrote :

This is not planned for the next release (which should contain mostly bug fixes), but it's probably not too hard to implement.
Once a clean way to integrate that functionality in pyexiv2's API has been decided, implementation should be pretty straightforward.

Revision history for this message
reco (reco.nex9) wrote :

yep we also need to write into our own namespace.
+1

is there a way to fund this?

Revision history for this message
Olivier Tilloy (osomon) wrote :
Revision history for this message
Olivier Tilloy (osomon) wrote :

I’m experimenting with this feature and so far I have a working prototype that allows registering custom namespaces and unregistering them.

There is however a limitation to the type of values that can be written to custom tags, they’re simple text values only. As far as I can see, overcoming this limitation would require substantial work so I need to understand if the limitation is acceptable in a first step.

@all: please comment on your use-cases and whether this limitation would be a problem.

Changed in pyexiv2:
assignee: nobody → Olivier Tilloy (osomon)
status: Triaged → In Progress
Olivier Tilloy (osomon)
Changed in pyexiv2:
milestone: none → 0.3
Revision history for this message
aschmid00 (a-schmid00) wrote :

the text values would me ok for me. in my case i would only need to store a uuid and a sha value. i could always transform the values to whatever type in python anyway.

Revision history for this message
reco (reco.nex9) wrote : Re: [Bug 549496] Re: Feature request: Custom XMP namespaces

Cool man

best,
christof

Christof Haemmerle
Nex9, LLC

401 Broadway, suite 900
New York, NY 10014

FON 212 937 7766
FAX 212 937 7767

This e-mail and any attachments are intended solely for the individual
or entity to whom it is addressed. Its contents and that of the
attachments are confidential, contain proprietary information, some or
all of which may be legally privileged. If you are not the intended
recipient, please notify the author immediately by telephone or by
replying to this e-mail, and then delete all copies of the e-mail on
your system. If you are not the intended recipient, you must not use,
disclose, distribute, copy, print or rely on this e-mail. Finally, the
recipient should check this email and any attachments for the presence
of viruses. Nex9 accepts no liability for any damage caused by any
virus transmitted by this email.

On Nov 30, 2010, at 7:26 AM, aschmid00 <email address hidden> wrote:

> the text values would me ok for me. in my case i would only need to
> store a uuid and a sha value. i could always transform the values to
> whatever type in python anyway.
>
> --
> Feature request: Custom XMP namespaces
> https://bugs.launchpad.net/bugs/549496
> You received this bug notification because you are subscribed to
> pyexiv2.
>
> Status in pyexiv2, a python binding to exiv2: In Progress
>
> Bug description:
> Hello, I would need to create my own XMP namespace to add custom tags to my photos. I didn't manage to figure out how to do it with pyexiv2, I keep getting invalid key exceptions, so I guess it is not possible to do it yet, or am I just missing something?
> I manage to read custom tags though.
>
> Is this a feature that could be implemented?
>
>

Revision history for this message
Olivier Tilloy (osomon) wrote :

That’s correct, additional parsing/serializing of the value in the client code is always possible to store/retrieve complex types. Not the most convenient (as in, it would be easier if pyexiv2 handled it itself), but a possible solution if needed.

Revision history for this message
Olivier Tilloy (osomon) wrote :

Implemented with revision 344 of the trunk.

@all: please test and report your feedback here, I’m curious to see if this implementation provides what you need (hopefully it does!).

Changed in pyexiv2:
status: In Progress → Fix Committed
Olivier Tilloy (osomon)
Changed in pyexiv2:
status: Fix Committed → Fix Released
Revision history for this message
reco (reco.nex9) wrote : Nex9 nominated for redesign of Munro Studio

→ web version http://campaign.nex9.com/t/r-e-ntlxjd-tyiylyudo-i/ → forward http://nex9llc.forwardtomyfriend.com/r-tyiylyudo-79E3914B-ntlxjd-l-d

We are nominated for Best Website for our work on the newly launched Tom Munro Website.

See our nomination at AWWWARDS [http://www.awwwards.com/best-websites/munro-studio] and vote for us if you like it.

you subscribed with the address <email address hidden>, unsubscribe http://campaign.nex9.com/t/r-u-ntlxjd-tyiylyudo-h/, update subscription http://nex9llc.updatemyprofile.com/r-ntlxjd-79E3914B-tyiylyudo-k

Nex9 LLC

102 Franklin Street, 2nd Floor

New York, NY 10013

212 937 7766

Revision history for this message
reco (reco.nex9) wrote : Nex9 nominated for JillJillStuart.com

→ web version http://campaign.nex9.com/t/r-e-xthkidt-tyiylyudo-i/ → forward http://nex9llc.forwardtomyfriend.com/r-tyiylyudo-79E3914B-xthkidt-l-d

We are nominated for Best Website for our work on the newly launched Jill Jill Stuart Website.

See our nomination at AWWWARDS [http://www.awwwards.com/best-websites/jill-jill-stuart] and vote for us if you like it.

you subscribed with the address <email address hidden>

unsubscribe http://campaign.nex9.com/t/r-u-xthkidt-tyiylyudo-h/, update subscription http://nex9llc.updatemyprofile.com/r-xthkidt-79E3914B-tyiylyudo-k

Nex9 LLC

102 Franklin Street, 2nd Floor

New York, NY 10013

212 937 7766 [https://www.google.com/maps/preview#!q=NEX9+LLC]

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.