MediaBin - Metatagger integration

Hello MediaBin_MTS,

Is there a document which talks about MediaBin Metatagger integratiion and how Metatagger communicates with Medaibin?

Thanks,
Aryan.

Find more posts tagged with

Comments

Aryan

Also, Is it possible to get the metadata generated by Metatagger to get inserted in to the Metadata XML generated by mediabin during the deployment agent deployment?

Thanks,
Aryan.

Migrateduser

Lyman is most familiar with the server-side integration of metatagger that he mentioned in a response to one of your other posts.
I've worked only on a UI piece that used a file created by metatagger, independent of MediaBin, that was then copied to a location where the web client could read it.
It sounds like you want to use metatagger to expand a MediaBin metadata value to a larger set of values... and to have the original value and the values generated by metatagger, copied to your own database (or that of your "delivery" system).
Sorry, I'm not familiar enough with Metatagger to know if it's possible to run it on the fly, possibly from the script that you would create to become a step in Deployment Agent, which copies metadata to your database. That could be one solution.
Another solution would be to have a script monitor the MediaBin AuditLog for metadata updates. If a new metadata value is created, check in a static metatagger xml file to see if it's there already. If not, run metatagger and store the results back into the file. This file would then be used by your DA script to expand a metadata value from DA's metadata.exp file into a larger set, based on what's in the metatagger xml file. This is somewhat similar to how the web client works when expanding a search term into a larger set of terms, except that the metatagger xml file is produced and updated manually.
Lyman may be able to provide more details about a server-side solution.

lyman

The metadata inserted based on MetaTagger is stored, as I mentioned in another thread, in one of three metadata fields. All of these fields are "editable" metadata and will be present in an XML export of the asset (either the whole asset or a "metadata only" deployment). Unfortunately we do not currently offer the granularity to restrict to just these fields, although one could significantly reduce bandwidth by inserting a metadata remover into the deployment task to weed out fields not of interest!

Cheers,

Lyman Hurd

Aryan

Thanks a lot for all this information.

It was very helpful.

Thanks,
Aryan.