TagUI & G11N/Locale

We've started the localization process in Teamsite 7.3.1 and would like to use the g11n_locales.cfg datacapture with TagUI so we can tag the following items:

G11N/Locale
G11N/Localizable
G11N/TranslationStatus

However when we try to tag files with these extended attributes, the path is added as this:

TeamSite/Metadata/G11N/Locale
TeamSite/Metadata/G11N/Localizable
TeamSite/Metadata/G11N/TranslationStatus

How can we remove the first part of the path? (TeamSite/Metadata/) Thanks.

Find more posts tagged with

Comments

Rick Poulin

AFAIK, you can't. The TagUI is intentionally restricted to a specific namespace so it can't interfere with system attributes. You'd have to either use FormAPI+callServer, or build a custom screen in workflow.

Adam Stoller

To follow on Rick's answer ...

iwextattr (or CSSDK equivalent) can created EAs with any string (e.g.: G11N/Locale) - so you could either handle the processing up-front (with FormAPI + callServer or home-grown metadata capture form, as Rick indicated) or post-process it (within your workflow) by extracting and re-creating the EAs with the paths you want - and either removing or leaving the other EAs there.

If you need the EAs for in-context Preview - then one of the two suggestions Rick provided (and I reiterated) is what you need. If you only need the EAs to be processed and stored (e.g.: DD, LSCS, etc.) - then inserting a custom task within your workflow to post-process the file prior to any deployment, would probably be a reasonable way to go.

WeekData.zip

JoeS

OK - thanks Rick and Fish for suggesting the various options.

JoeS

OK - so I added this js to the FormAPI:

[PHP] var server=window.location.hostname;

var params = new Object();

// set server parameters
params.fileUrl = IWDCRInfo.getDCRName();
var locale = IWDatacapture.getItem("/G11N/Globalization/G11N/Locale");
params.localeVal = locale.getValue();
IWDatacapture.callServer("http://"+server+"/iw-bin/mfs/setEAs.ipl",params, false);
return true; [/PHP]

And created the following ipl:

[PHP]use TeamSite::Config;
use CGI;
my $in = new CGI;
my $dcrname= $in->param('fileUrl');
my $locale= $in->param('localeVal');
my $iwhome = TeamSite::Config::iwgethome();

system(qq($iw_home/bin/iwextattr -s "G11N/Locale=$locale" $dcrname)); [/PHP]

However the iwextattr command isn't copying the extended attributes. I see this errror in the error.log:
sh: /bin/iwextattr: not found

Thanks for any advice.

neeraj_kumar

Try and check by hardcoding for $iw_home.

Ex: $iw_home -> c:\Interwoven\Teamsite\bin\iwextattr

Check if this works for you?

JoeS

Yes - hardcoding it worked. Thanks.

system(qq(/iw-home/Interwoven/TeamSite/bin/iwextattr -s "G11N/Locale=$locale" $dcrpath));

Adam Stoller

[...]

And created the following ipl:

[PHP]use TeamSite::Config;
use CGI;
my $in = new CGI;
my $dcrname= $in->param('fileUrl');
my $locale= $in->param('localeVal');
my $iwhome = TeamSite::Config::iwgethome();

system(qq($iw_home/bin/iwextattr -s "G11N/Locale=$locale" $dcrname)); [/PHP]

However the iwextattr command isn't copying the extended attributes. I see this errror in the error.log:
sh: /bin/iwextattr: not found

You may have figured it out - but in case you didn't - the problem was that you defined $iwhome but then attempted to use i$w[color=red]_home[/color] - something that you would have caught if you had included the pragmas:

use strict;
use warnings;

and/or checked the script with

iwperl -w -c script-name

JoeS

Good catch - thanks.