nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Attempt to copy DCR

System

I am still very new to TeamSite and do not claim to know what a DCR is. We are running 6.5.1 SP3 on Windows. I have inherited a perl script that is supposed to be copying a DCR. Something is wrong with the resulting copy. When you click on it within TS, it wants to download, rather than open up the window that shows the extended attributes. Also, showing the properties on the new file indicates that the extended attributes are not set.

The script gets the extended attributes that are defined, and then sets them on the copied file using the external "iwextattr" command. The file is copied using "copy()" in perl.

I guess what I am most confused about is what makes a DCR a DCR to TeamSite? What should I be looking for that would be missing?

I am willing to post the code, etc. if you want to see what I am doing.

Any insight, as well as pointers to documentation, examples, etc. are greatly appreciated.

Find more posts tagged with

Comments

nipper

You are on the right track.

The DCR is an XML file that has an extended attribute on it. That EA define how TS handles the files. Since you are getting the download option, it is highly likely that the EA is incorrect.

If you click on the properties of the file in the TS GUI there should be an EA called TeamSite/Templating/DCR/Type with a value of category/type where the values of category/type are the folders where the file lives between templatedata and data i.e. templatedata/category/type/data/somedcr.xml

HTH

Andy

Migrateduser

You are on the right track.

The DCR is an XML file that has an extended attribute on it. That EA define how TS handles the files. Since you are getting the download option, it is highly likely that the EA is incorrect.

If you click on the properties of the file in the TS GUI there should be an EA called TeamSite/Templating/DCR/Type with a value of category/type where the values of category/type are the folders where the file lives between templatedata and data i.e. templatedata/category/type/data/somedcr.xml

HTH

Andy

Thanks. There is an EA indicating the DCR Type which I am setting:

Command:[E:\iw-home/bin/iwextattr -s TeamSite/Templating/DCR/Type=pgi/doc_data "Y:\default\main\PGI\Marketing\Communications\WORKAREA\Web_Infrastructure\templatedata\pgi\doc_data\data\research\marketinsights\2006q4-copy-CAT"]
Result of eadcrType: OK

So, if I followed you, this should be correct, right?

nipper

Yea that looks correct.

Can you do a file-> new form on this DCR type ?

What happens is you run this command from a DOS shell ?

Migrateduser

Thanks. There is an EA indicating the DCR Type which I am setting:

Command:[E:\iw-home/bin/iwextattr -s TeamSite/Templating/DCR/Type=pgi/doc_data "Y:\default\main\PGI\Marketing\Communications\WORKAREA\Web_Infrastructure\templatedata\pgi\doc_data\data\research\marketinsights\2006q4-copy-CAT"]
Result of eadcrType: OK

So, if I followed you, this should be correct, right?

Funny thing, when I try the command on the command line, it just hangs. So, perhaps the OK result is not really OK? All it does is check for a response of "".

Migrateduser

Yea that looks correct.

Can you do a file-> new form on this DCR type ?

The interface comes up just fine. I didn't actually create a new file, though. Do you want me to?

nipper

just for grins try iwextattr.exe

I have seen cases when people have tried a Unix style redirection and created a null file in iwhome/bin

Once you can get iwextattr to work, you should be good to go.

nipper

The interface comes up just fine. I didn't actually create a new file, though. Do you want me to?

Probably not necessary, it sounds like there is an issue with your command to set the EA.

You are executing this perl script on the TS server and not your own desktop, correct ?

Migrateduser

just for grins try iwextattr.exe

I have seen cases when people have tried a Unix style redirection and created a null file in iwhome/bin

Once you can get iwextattr to work, you should be good to go.

I have seen this, too. However, in this case, the command will run and give you the help screen if it has no parameters.

Migrateduser

Probably not necessary, it sounds like there is an issue with your command to set the EA.

You are executing this perl script on the TS server and not your own desktop, correct ?

Yes, this is all running on the server. It seems clear that running the command is either the only thing wrong, or at least preventing progress.

I will spend some more time with the command and see what I can figure out. I know getting values with -g and listing the attributes with -e both work, so I have some issue with setting values.

nipper

FYI, in all of my automated scripts I transpose the backslash to forward slash.


$file=~tr|\\|/|;

That will work in DOS as well as Unix (in the TS filesystem).

Migrateduser

Yes, this is all running on the server. It seems clear that running the command is either the only thing wrong, or at least preventing progress.

I will spend some more time with the command and see what I can figure out. I know getting values with -g and listing the attributes with -e both work, so I have some issue with setting values.

Holy Cow, this is weird. If I execute it like this instead, then I get the attribute set, but with an extra equals sign.

C:\Documents and Settings\teamsite>echo "pgi/doc_data" | iwextattr -s "TeamSite/Templating/DCR/Type" -f //pfgdsmtmsite391/default/main/PGI/Marketing/Communications/WORKAREA/Web_Infrastructure/templatedata/pgi/doc_dat
a/data/research/marketinsights/2007q1-copy-CAT

C:\Documents and Settings\teamsite>iwextattr -l "//pfgdsmtmsite391/default/main/PGI/Marketing/Communications
/WORKAREA/Web_Infrastructure/templatedata/pgi/doc_data/data/research/marketinsights/2007q1-copy-CAT"
TeamSite/Templating/DCR/Type="pgi/doc_data"

TeamSite/Templating/DCR/Type=pgi/doc_data=

C:\Documents and Settings\teamsite>

nipper

OK, so obviously it is thinking it should be getting the EA value via STDIN, that is why it is hanging.

Did you have any extra quotes on the command ?

It appears it made an EA named TeamSite/Templating/DCR/Type=pgi/doc_data with no value and another named TeamSite/Templating/DCR/Type with a value of "pgi/doc_data"

Try running this script (which will go through your folder and properly set all EAs for TST.


#!d:\interwoven\iw-home\iw-perl\bin\iwperl.exe

use TeamSite::Config;
(my $iwhome = TeamSite::Config::iwgethome()) =~ tr|\\|/|;
use File::Find;
$start = "Y:/default/main/PGI/Marketing/Communications/WORKAREA/Web_Infrastructure/templatedata/pgi/doc_data/data/";

find(\&wanted, $start);
foreach $DCR (@list) {
 ($EA = $DCR) =~ s|.*templatedata/||;
 $EA =~ s|/data/.*||;
 $command = "$iwhome/bin/iwextattr -s TeamSite/Templating/DCR/Type=$EA \"$DCR\"";
 system ($command);
 }


sub wanted {-f && push(@list, $File::Find::name);}

Migrateduser

OK, so obviously it is thinking it should be getting the EA value via STDIN, that is why it is hanging.

Did you have any extra quotes on the command ?

It appears it made an EA named TeamSite/Templating/DCR/Type=pgi/doc_data with no value and another named TeamSite/Templating/DCR/Type with a value of "pgi/doc_data"

Try running this script (which will go through your folder and properly set all EAs for TST.
#!d:\interwoven\iw-home\iw-perl\bin\iwperl.exe

use TeamSite::Config;
(my $iwhome = TeamSite::Config::iwgethome()) =~ tr|\\|/|;
use File::Find;
$start = "Y:/default/main/PGI/Marketing/Communications/WORKAREA/Web_Infrastructure/templatedata/pgi/doc_data/data/";

find(\&wanted, $start);
foreach $DCR (@list) {
 ($EA = $DCR) =~ s|.*templatedata/||;
 $EA =~ s|/data/.*||;
 $command = "$iwhome/bin/iwextattr -s TeamSite/Templating/DCR/Type=$EA \"$DCR\"";
 system ($command);
 }


sub wanted {-f && push(@list, $File::Find::name);}

Thanks for the help Nipper. I need to leave for the day, so I will try this tomorrow. I've also opened a case with Interwoven to see what they say about it.

Migrateduser

Ok, I've had some success by altering the script to use the echo/pipe version of the command. Is it necessary to set all the EA's?

The script is only trying to copy these:

TeamSite/Templating/DCR/Type
TeamSite/Templating/Encoding
TeamSite/Templating/PrimaryDCR
TeamSite/Templating/PrimaryDocumentType
TeamSite/Templating/PrimaryPT

but the file also has these set:

TeamSite/Metadata/ContentAuthor
TeamSite/Metadata/ContentOwner
TeamSite/Metadata/EmailContact
TeamSite/Metadata/ExpirationDate
TeamSite/Metadata/MetaDescription
TeamSite/Metadata/Metakeywords
TeamSite/Metadata/RetentionCategory
TeamSite/Metadata/ReviewDate
TeamSite/Metadata/ReviewFrequency

nipper

Ok, I've had some success by altering the script to use the echo/pipe version of the command. Is it necessary to set all the EA's?

The script is only trying to copy these:

TeamSite/Templating/DCR/Type
TeamSite/Templating/Encoding
TeamSite/Templating/PrimaryDCR
TeamSite/Templating/PrimaryDocumentType
TeamSite/Templating/PrimaryPT

but the file also has these set:

TeamSite/Metadata/ContentAuthor
TeamSite/Metadata/ContentOwner
TeamSite/Metadata/EmailContact
TeamSite/Metadata/ExpirationDate
TeamSite/Metadata/MetaDescription
TeamSite/Metadata/Metakeywords
TeamSite/Metadata/RetentionCategory
TeamSite/Metadata/ReviewDate
TeamSite/Metadata/ReviewFrequency

A DCR has DCRType, that is all it needs. I assume if you are doing encoding other than UTF-8, then Encoding would be required as well. A file generated from a template will need PrimaryPT, PrimaryDCR and PrimaryDocumentType.

The others are specific to your site, we have no idea if they are needed or not. They are not set by TST, but with the set metadata screen.

Migrateduser

A DCR has DCRType, that is all it needs. I assume if you are doing encoding other than UTF-8, then Encoding would be required as well. A file generated from a template will need PrimaryPT, PrimaryDCR and PrimaryDocumentType.

The others are specific to your site, we have no idea if they are needed or not. They are not set by TST, but with the set metadata screen.

Thanks for your help. BTW, what does "TST" stand for?

nipper

Thanks for your help. BTW, what does "TST" stand for?

TeamSite Templating - what they used to call Forms Publishing

I got smacked around at GearUp by Sunil for referring to it as Templating, Marketeering has changed its name.

Adam Stoller

TeamSite Templating - what they used to call Forms Publishing

I got smacked around at GearUp by Sunil for referring to it as Templating, Marketeering has changed its name.

You should ask Sunil to explain "tt_data" :-)

Migrateduser

OK, so obviously it is thinking it should be getting the EA value via STDIN, that is why it is hanging.

Did you have any extra quotes on the command ?

It appears it made an EA named TeamSite/Templating/DCR/Type=pgi/doc_data with no value and another named TeamSite/Templating/DCR/Type with a value of "pgi/doc_data"

Try running this script (which will go through your folder and properly set all EAs for TST.
#!d:\interwoven\iw-home\iw-perl\bin\iwperl.exe

use TeamSite::Config;
(my $iwhome = TeamSite::Config::iwgethome()) =~ tr|\\|/|;
use File::Find;
$start = "Y:/default/main/PGI/Marketing/Communications/WORKAREA/Web_Infrastructure/templatedata/pgi/doc_data/data/";

find(\&wanted, $start);
foreach $DCR (@list) {
 ($EA = $DCR) =~ s|.*templatedata/||;
 $EA =~ s|/data/.*||;
 $command = "$iwhome/bin/iwextattr -s TeamSite/Templating/DCR/Type=$EA \"$DCR\"";
 system ($command);
 }


sub wanted {-f && push(@list, $File::Find::name);}

Thanks Nipper. I ran this, but seem to get the same results as before.

Migrateduser

I've just become aware of the iwupdate command. Should I just call that rather than trying to get attributes and attempt to set them on a copied file?

nipper

Are you copying from one workarea on a branch to another on the SAME branch ? Yes, use iwupdate and do not do what you are trying. If you are going to another branch then update will not work.

Adam Stoller

Are you copying from one workarea on a branch to another on the SAME branch ? Yes, use iwupdate and do not do what you are trying. If you are going to another branch then update will not work.

Were you sure it won't work across branches? or were you just assuming so?
It will work across branches too - e.g.:

iwupdate /default/main/foo/WORKAREA/wa1/templatedata/cat/dtype/data/foo.xml /default/main/bar/WORKAREA/wa2

will copy

templatedata/cat/dtype/data/foo.xml

from the foo branch's wa1 workarea to the bar branch's wa2 workarea and preserve EAs (at least in 671SP1+Patch1 on Windows -- I just tested it)

nipper

Were you sure it won't work across branches? or were you just assuming so?
It will work across branches too - e.g.:

My bad, it used not to (5.X timeframe).

gzevin

You should ask Sunil to explain "tt_data" :-)

and templating.cfg and http://server/iw/help/tst/pt