Moving Content

I tried (innocently enough) to move a templated file in Teamsite. I am on Teamsite 5.5.2 (SP2 uninstalled) on Windows 2000. When I moved that file and sent the user to edit the file in the new location, the user was unable to edit the file because he did not have the appropriate authority. I checked everything.... I thought. The reason why the user did not have appropriate permissions was because the templated file had an extended attribute set (Teamsite/Templating/PrimaryDCR) for the DCR that the user did not have authority to edit. Stupid me for thinking that when I move a file - Teamsite would do something for me and move the DCR also.

Anyway...

I found that I have to move the file using the iwextattr command line tool. Here is where my second problem lies:

When I tried to set the attribute using the syntax of:
iwextattr -s Teamsite/Templating/PrimaryDCR = newLocation templatedFileLocation. The command simply created a new attribute rather than updating the old.

Two questions:
Is there an easier way to move templated content than using Teamsites 'Move' command?

What am I doing wrong with the iwextattr comand-line?

Here is the command and the results (using iwextattr -l)

Y:\default\main\CNF\Intranet\ITWEB\WORKAREA\OnlineControl\templatedata\ITWEB\Gen
eral\data\EnterpriseServices\OnLineControl>iwextattr -s Teamsite/Templating/Prim
aryDCR=y:\default\main\CNF\Intranet\ITWEB\WORKAREA\OnlineControl\templatedata\IT
WEB\General\data\EnterpriseServices\OnLineControl\olc Y:\default\main\CNF\Intran
et\ITWEB\WORKAREA\OnlineControl\EnterpriseServices\OnLineControl\olc.asp

Y:\default\main\CNF\Intranet\ITWEB\WORKAREA\OnlineControl\templatedata\ITWEB\Gen
eral\data\EnterpriseServices\OnLineControl>iwextattr -l Y:\default\main\CNF\Intr
anet\ITWEB\WORKAREA\OnlineControl\EnterpriseServices\OnLineControl\olc.asp
CNF/MetaData/CNFContentCreator=domain/username
CNF/MetaData/CNFContentOwner=
CNF/MetaData/CNFDocumentTitle=User Web
CNF/MetaData/CNFPublishDate=1/15/2003 2:11 PM
CNF/MetaData/CNFRemoveDate=
CNF/MetaData/CNFReviewDate=7/14/2003 2:11 PM
CNF/MetaData/CNFXmlMenuFile=\EnterpriseServices\OnLineControl\siteITIOL.xml
CNF/Templating/PrimaryDCRVersion=2
TeamSite/Templating/PrimaryDCR=EnterpriseServices\Userweb\olc
TeamSite/Templating/PrimaryDocumentType=ITWEB/General
TeamSite/Templating/PrimaryPT=General.tpl
Teamsite/Templating/PrimaryDCR=y:\default\main\CNF\Intranet\ITWEB\WORKAREA\Onlin
eControl\templatedata\ITWEB\General\data\EnterpriseServices\OnLineControl\olc

Thank you very much for your help.

Find more posts tagged with

Comments

Migrateduser

The capitalization is different in the extended attribute that you are setting (TeamSite vs. Teamsite) The EAs are case sensitive, thus your new EA is different rather than the same as the old.

With the correct capitalization, it should overwrite.
If you want to be overly cautious, you could use an iwextattr -d first to delete the old EA before writing the new one.

rpjoseph

Well now I just feel like an idiot. Thank you.

Is there an easier way to move templated content?

Migrateduser

Where are you moving it? If you are just moving the output file to a different directory in the same branch, then the move command should work fine. The same old DCR should still be accessible just as it was before even though the output file is in a different location. (This should also work if you do a filesystem move - however, a filesystem copy will not retain extended attributes, and thus they will have to be reset with iwextattr.)

If you are moving it to a different branch that has the same templates enabled, you can use copy-to-area, though you will have to copy both the DCR and the generated file.

If you envision users moving a large number of files, a simple move menu item could be in the order. I have seen a few variants customized to specific purposes. The most simple allows a user to select a file and then moves it and the connected DCR. More complex versions scrub filesystems for all related files, present nice guis for users, or do other things needed for the site.

Migrateduser

Actually the DCR may need to be moved and therefore the attributes updated. Specifically, if there is a directory structure within /templatedata/category/type/data that matches the directory structure of the output files. Which is the way I have always seen it implemented. For instance, /templatedata/category/type/data/dir1/dir2/file generates /dir1/dir2/file.asp. I think it is important that the source path match the target path so you can have rules in workflow about where to generate output files, and to control permissions on directories. Logically it makes sense to have the DCR match the output file name, but if every DCR is in one directory this won't work because there can only be one dcr named default and there could be dozens of default.asp files.

There are probably exceptions if your system generates multiple output files (in which case the directory structure may be a bigger problem).

Of course if it was a real object store instead of a filesystem you wouldn't have any of these issues.

Migrateduser

You probably don't want the full path to the DCR as the value of the extended attribute - you probably just want the path relative to /templatedata/category/type/data relative to the workarea (I think "EnterpriseServices\OnLineControl\olc" in this case). I am not sure which way the slashes go on NT, but the command might look more like:

iwextattr -s TeamSite/Templating/PrimaryDCR=EnterpriseServices\OnLineControl\olc Y:\default\main\CNF\Intranet\ITWEB\WORKAREA\OnlineControl\EnterpriseServices\OnLineControl\olc.asp

documentumError.JPG

rpjoseph

In a way - It is a relief to read this. You expect this behavior to be built in? As you can probably tell - we are relatively new to this and not very happy because we feel like we have to tell Teamsite how to do everything.

I move files using Teamsite's File-Move operation. The templated file moves but the DCR does not. I submit the file once I have moved it. If I move the DCR by hand the extended attribute does not change.

I do not expect users to move a significant amount of files. I just want to be able to move files like normal. I would expect that a move operation would:
- Create a new templated file in the new location
- Create a new DCR under templatedata and the appropriate directory
- Delete the templated file and the DCR in the old location
- Workflow at least the deleted files in the old location
- Delete and possibly add the files on the associated web server

Is that what I should expect?

Thank you for your help and more importantly a glimmer of hope.