Converting XML files into dcrs

We are converting an old Spectra application into TeamSite. We are planning on converting the Spectra objects into xml files whose tags map directly to the tags I have created in the dcr's within TeamSite. What would be the best method to import these xml files into teamsite and set the attributes correctly so that we can use these as dcrs?

Thanks for any help or pointers!

Craig

Find more posts tagged with

Comments

nipper

Yea that is pretty it. The good thing is that you get plenty of time to debug to get it correct. Times I have done this, I have had the incorrect case of one of the areas so I had to redo it (or change the DCT, which ever is easier). I have done this a couple times, typically from data in a DB or in an Excel spreadsheet.

Try to create a new DCR check, line by line how ti compares with the XML you have.

Also, think how you want these named (the files). That can often be an issue.

Finally, since you are importing what seems to be a significant amount of data, (several hundred to many thousands), then you need to decide if you want to add sub directories to your DCRs. Instead of tossing them all in the data dir, you may want to split them up, that begs the question how ? And then how to put your XML in the correct spot and then how to write the formapi for development down the road so that the DCRs will show up in the correct directory.

kaalraa

We are converting an old Spectra application into TeamSite. We are planning on converting the Spectra objects into xml files whose tags map directly to the tags I have created in the dcr's within TeamSite. What would be the best method to import these xml files into teamsite and set the attributes correctly so that we can use these as dcrs?

Thanks for any help or pointers!

Craig

The XML structure should be similar to what could be generated from your newly created DCT and all files should have External Attribute attached (TeamSite/Templating/DCR/Type).

frbcraig

Thank you so much for the replies. Is using iwextattr.exe within a perl script that will loop over each new dcr the only way (and best way) to set the external attributes after the xml files are imported? or is there a way to copy the attributes from an existing dcr and apply those attributes to all the new dcrs?

Craig

nipper

Thank you so much for the replies. Is using iwextattr.exe within a perl script that will loop over each new dcr the only way (and best way) to set the external attributes after the xml files are imported? or is there a way to copy the attributes from an existing dcr and apply those attributes to all the new dcrs?

Craig

Use XML mode. Check out this thread or this one for details.

It will set the EAs in 1 call instead of 3, that is where you will spend a great deal of time, so this is a big savings.

frbcraig

Another question regarding this - is there a command line tool or other such thing that could be called to import an XML file into TeamSite? - I know how to import a file through the CCPro interface, but I was hoping i could automate this process and set the EA's in the same perl module....

Any ideas on this??

Thanks,

Craig

nipper

The physical import is easy, copy, xcopy, something like that. Deciding where what name etc, is something you may need to do

If you have the XML files accessible to th server already and they do not need renaming or new directories, then just copy the structure to the data dir

I was also brain dead on my previous post, you do not need 3 EAs on a DCR, you only need one. You need 3 on the generated output.

I use a script like this to set all EAs in a structure:


#!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/branch/WORKAREA/Content/templatedata/";

find(\&wanted, $start);
foreach $DCR (@list) {
 if (!($DCR =~ m|\.xml$|) ) { next;}

 ($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);}