Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Add/Edit XMP Data

NNN634289132254246897
It seems the only way to add/modify XMP data is via MediaItem.Annotations.ImportFromXMP().

* Is there really no easier way?
* If not is there at least some library to generate XMP files?
* How would I modify xmp data as this will require to first read the xmp data so it can be changed and written back?
0

Comments

5 comments

Date Votes
  • Ulf Liljegren
    Maybe this will help?
    http://www.youtube.com/user/PhaseOneDK# ... xmUepqGzCA
    0
  • NNN634289132254246897
    Thanks for the response. I checked the video which explains very well how this works with Capture One. However, I want to do this all in MediaPro. In short, I want to create a script that transfers the information from proprietary tags into standard tags. For instance, MediaPro seems to store the People information in a custom field. This will not be found by other programs including a search in Windows Explorer. I want to create a script that transfers such custom fields into standard fields which quite frequently are xmp fields. In case of people it would allow somebody without MediaPro to search for people simply by typing the name of people in windows explorer. The only way I see this can be done in a script is by writing xmp files and then import them. Is there any other way and if not how can I create these xmp files in the script?
    0
  • NNN634407623648915965
    Arggh.. why is Mediapro using CUSTOM fields to begin with? There are clearly defined IPTC and XMP fields for many of these standard items.. the key is for the companies to just use them to begin with!
    0
  • johnbeardy
    Custom fields are needed because users want to add metadata that doesn't necessarily fit in existing IPTC fields! Also, when People was first added to the catalogue, Person Shown wasn't an IPTC-Extension field. So all these fields are written to XMP and rightly took advantage of the X in XMP - ie by writing to custom XMP tags.

    Today, you can certainly argue that P1 should now update People so it maps to Person Shown and allow users to map custom fields to individual XMP tags (IIRC Peter Krogh, Robert Edwards and I asked MS for this Extensis-style mapping back in '06). But right now things are as they are for good reasons, and P1 have more urgent priorities than dealing with what to most users is gobbledegook.

    Try automating Exiftools with vbs so it modifies existing XMP (sidecars or embedded). You could then point each custom field at whatever XMP tag you want.

    John
    0
  • NNN634407623648915965
    It certainly should take advantage of standard XMP fields... and it should also allow custom schemas to be created instead of user fields which only get stored in the database... Idimager allows you create your own schema and easily map labels directly to XMP fields as well.. 2 great features that MP should add in the future.
    0

Post is closed for comments.