Write XML triggers too early

[peterk]

Hi,

I have set up a watcher with two responses:
Copy
WriteXML

It downloads a file from a folder, puts it to the Library and I need to export XML AT THE END of the process. I need to have an Asset ID in the .xml file.
The problem is that WriteXML reponse is fired just after copy is finished and before FCS sets all the metadata fields.
My xml file that is created in this Watcher doesn't contain metadata I need and is different than xml. file created from the same asset when it is in FCS already (and finished).

My task:
I am watching remote ftp folder with incoming .mpg files. Each mpg file on ftp has a counterpart - .xml file with the same name as the .mpg file.
I need to download .mpg to FCS, then .xml and set my custom meta data fields in a new asset to values from remote xml file.
I have written a ruby script that downloads the xml from remote site and creates a new xml (in FCS 'Read XML' format). I am calling my ruby script in my watcher (actually in place where is WriteXML - this is just for testing for now) with parameters "[Title]""[Asset ID]". I need to know Asset ID for xml I need to read in FCS. The problem is that Asset ID in this case is not the same Asset ID as when FCS finishes all processes with the asset being created.
I have couple of ideas how to fix it, but I would like to keep it as simple as possible, and this seems to be the simplest way ...
Any ideas ?

Thank you.


Peter

[MattG]

You need to trigger the Write XML not from the Watcher, but from a Subscription. Simply subscribe to the "Created" event of an Asset. This way, as soon as the Watcher has completed its copy and made an asset for the new file, it will fire the "Created" subscription and provide a Write XML with the Asset ID inside of it.

[peterk]

Hi Matt, yes that was one solution I considered, but it will be triggred for every Create event. I used a WriteXML just to test what is in metadata of asset when it is calling. I need to call external script instead of WriteXML to which I need to pass [Title] and [AssetID], the script then downloads and transform some xml to xml for FCS (not every asset have this xml attached). So I need to trigger script after my copy response, but not before metadata are set.
I have a workaround: I created an auxiliray metadata field that I set to TRUE in the resposne that is copying file. I subscribed to this MD and it calls my ruby srcript that does the rest. Workaround, but no so elegant as I wanted .. Anyway, I would appreciate any other idea.
Thank you.

[peterk]

Hi,

I just want to add my solution:
I created a subscription that checks for: "myMetadatSet" Im setting when uploading asset from ftp and for my auxiliary MD field "MDisSet" I also set when uploading from ftp.
When these conditions are true I run my ruby script with prameters [FileName] [Asset ID].
- script is triggered only when asset is uploaded, it also sets MDisSet to FALSE
- script is not triggered when asset is modificated or uploaded to FCS client with "myMetadatSet".