Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
importing images and thier XML metadata
Samuelq
Greetings,
We are going to have several images that we need to import into MediaBin for our client. The metadata for each of the assets, will be in a corresponding XML file for each individual asset.
We are reviewing the API for ways to import the assets, and have the metadata from the XML file be imported with it.
We will already have the required metadata fields defined in MediaBin, we will just need to place the metadata into the appropriate fields for each asset.
Can someone please provide us with some direction towards this end?
Thank you,
Jim
Find more posts tagged with
Comments
msrinivas
With some effort you should be able to write a script in your favorite programming language using MediaBin API. I have the script that does this but unfortunately I can not share it here.
lyman
One option would be to use an XSLT transform to convert your xml format to the format needed by the MediaBin XML Metadata Adder and then using that as an insertion task...
That would be a bit more elegant than looping through the metadata fields...
Cheers,
Lyman Hurd
Samuelq
Hi Lyman,
Can you let me know about what the "MediaBin XML Metadata Adder" is?
Thanks!
Jim
Samuelq
I know that the XMP mapping tells you which metadata fields to keep; but the problem is, the images don't have the metadata, the XML files do.
Jim
lyman
Sorry to be confusing. There are two distinct uses of XML in MediaBin. Let me explain a bit:
1) The XMP packet is an XML format proposed by Adobe as a standard and currently adopted also by a committee, XMP Open. Our XMP Mapping file provides a way to flow XML in this format into and out of metadata fields that MediaBin can display, search for, etc.
2) The metadata adder, on the other hand, is one of the primitives provided by MediaBin for constructing tasks. It uses a proprietary format shared only by it and the XML Decoder and XML Encoder primitives. Its main purpose was to facilitate our "Syndication Manager" product but it is publicly accessible as well. To produce examples of what it expects, try outputting a file with a task consisting of an XML Encoder with export parameter set to "metadata only".
Cheers,
Lyman Hurd