Variables with Metadatacapture

TS 6.7.1/Win

I have an inline that I'd like to use with my MDC form to show the person who last modified the current file. Given the lack of options with passing variables back and forth compared to a DCT, is there a way to do this without a hack?

Thanks.

Find more posts tagged with

Comments

nipper

I am not totally clear on your requirement. But you can run IPL via MDC (via a an inline)> That needs to generate the appropriate XML for MDC. It *should* be able to define an EA with the default being the iwuser.

HTH

Andy

Migrateduser

What I'm looking for is: how does my ipl know the file to which I'm attaching metadata? I have 4 environment variables, one of them being my current workarea, which is remotely useful but not good enough. So, in my script, it seems that I have no way to determine what file I'm working with and thus, no way to retrieve the last modifier of the file.

Dave

nipper

OK now I get it

How about a different approach.

Write a trigger that will, when an object (or certain type of file) is modified, attach create/change the last modified by EA on your file.

ISCBorisB

What I'm looking for is: how does my ipl know the file to which I'm attaching metadata? I have 4 environment variables, one of them being my current workarea, which is remotely useful but not good enough. So, in my script, it seems that I have no way to determine what file I'm working with and thus, no way to retrieve the last modifier of the file.

Dave

In addition to Environment variables you have posted MDCT CGI Form as well. As far as I recall you have a full Path of the File in the Form's variable 'path_0'

Migrateduser

In addition to Environment variables you have posted MDCT CGI Form as well. As far as I recall you have a full Path of the File in the Form's variable 'path_0'

No, I don't think so. At least, when I dumped all POST, GET and ENV variables to the screen, all I got was 4 environment variables and IW_ROLE was even blank. Helpful, that.

ISCBorisB

No, I don't think so. At least, when I dumped all POST, GET and ENV variables to the screen, all I got was 4 environment variables and IW_ROLE was even blank. Helpful, that.

I've double-checked that in my (6.5) environment. It works and it is 'path_0'.
Perhaps 6.7 differs in that respect? Try to add the following temporarily to your MDCT, what does it show?
(providing that TS kept 'show_env' in 6.7)[html]
Fake

[/html]

Migrateduser

Good suggestion but this is an inline instead of a callout, which leads me to believe that I'm relegated to the command line syntax if I want to provide anything. This inline would basically give some File::stat-type info on the file being tagged.

ISCBorisB

Good suggestion but this is an inline instead of a callout

Ah... I've missed that, my mistake. TST Engine runs Inline to build full blown DCT before applying it to any particular asset.
There is nothing Posted, inline is actually not run through CGI Framework. I do not beleive there is anything you can do within inline itself.

nipper

Good suggestion but this is an inline instead of a callout, which leads me to believe that I'm relegated to the command line syntax if I want to provide anything. This inline would basically give some File::stat-type info on the file being tagged.

which brings you back to my original suggestion, set up a trigger that will attach EAs with the information you desire whenever a file is modified in TS.