MetaTagger from WorkFlow?

Hi,
We are using W2K, TeamSite 5.5.2 sp3, MetaTagger 3.5.

We are trying to find the best way to integrate using MetaTagger into a workflow. What are some options on this? One thing we thought of was:

a) user uploads a new image via TeamSite GUI.
b) they checkmark the file and then start a new workflow.
c) the workflow will launch MetaTagger and the person tags it with metadata.
d) after hitting "close" on the MetaTagger GUI, the workflow takes over automatically and does an external task on the file.

We'd rather not have the person kick off MetaTagger themselves, but instead have it part of the workflow. Item "d" would be really nice to have, but I'm not sure how it would work.

Are there any ideas for doing this? Thanks,

David

Find more posts tagged with

Comments

Migrateduser

I just have a cgitask call mtmetaproxy.cgi directly. Seems to work just fine.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

OMR.jpg

Migrateduser

Thanks. I'm not yet able to make workflows and see for myself, but what happens after a person hits "close" or "save" on MetaTagger? Will it transition to the next task?

POC.dcpackage

ApplyingSheetLayout.jpg

Migrateduser

Hi,
Basically you would have a cgitask in the workflow that calls mtmetaproxy.cgi. Lets say, you have something like
usertask1 -> cgitask -> usertask2 -> submittask -> End.

Then, when you invoke the workflow, the task first goes into user1's todo list who would launch the metatagger gui by saying something like 'Approve' or 'launch metadata' or 'done' or something. Once the metatagger is launch, have the user make his changes and click 'save'/'close' on the metatagger gui. This would close the metatagger gui and the task AUTOMATICALLY transitions to user2's todo list.

In short, YES, the tasks automatically transistion when you hit close on the mt gui.

Hope this helps.

Migrateduser

Have you checked out the configurable workflows? You can optionally include a CGITask that invokes iwmetadata.cgi or mtmetaproxy.cgi simply by changing a property in a configuration file (metadata_capture=yes).

Michelle Neuringer
Interwoven Engineer

Migrateduser

Yes, thanks. I had hoped it would be automatic -- person clicks close and then is somehow presented the option of doing the next (in our case, triggering an update of Verity). We can train them to go the To Do area and it's not a huge deal, but it was an extra step I had hoped to avoid.

Migrateduser

Thanks - I will check this. One question, though. You know how in a regular CGI task, it needs to finish with a callback. When clicking on "Close" in MetaTagger, is that callback sent? After a person hits close, I would like an OpenDeploy job to be triggered.

Adam Stoller

I believe, but cannot verify at this time, that when you close MetaTagger as a cgitask script in a workflow, that it sends a CallBack of 0 - i.e. assume only one transition from that cgitask.

--fish
(Interwoven Senior Technical Consultant)