rename directory/workflow

I am curious if/how people are handing workflow around directory rename when the directory has already been submitted/deployed, specifically what do you do about files that contain links into the renamed directory, or files generated from DCRs in directories within templatedata/category/type/data that correlate to the renamed directory.

Thanks,

-John

Find more posts tagged with

Comments

Migrateduser

I am not sure if I am missing something or if it is really not as complicated as it seems. Here are some of the issues I can see:

Corresponding directories within data for each category/type within templatedata should be renamed (for instance, if /olddir were being renamed /newdir, and /olddir/index.xml had been generated from /templatedata/category/type/data/olddir/index, then /templatedata/category/type/data/olddir would need to be renamed /templatedata/category/type/data/newdir - this would have to happen for each category/type that generates output files to the folder being renamed).

Extended attributes on all templated output files under the renamed directory would be modified to point to the DCRs in the renamed directory.

All links in all files that link to files in the renamed directory would have to be updated.

Templated content affected by the change would need to be regenerated.

The new directory would need to be deployed.

The deletion of the old directory would need to be deployed.

This should all be coordinated by a single workflow (does workflow still have performance issues when you attach hundreds of files?).

Something would need to ensure there were no conflicts with other workflows.

Users would have to be taught how to manage all of this.

Other workareas would be updated with the changes when the workflow completed.

Proxy remapping could be affected.

Migrateduser

Interwoven, can you respond to this?

Johnny

It all sounds about right.

How would you capture this though?....
Your users would have to specifically select this workflow.

It seems like it would be very messy workflow.

Do these events actually occur regularly?...

Most places I have worked for, the directory structure (or Information Architecture) is maintained by the TeamSite administrators, based on business requests.

Simply because of issues like setting ACLs on the new directories.

Sounds like it would be very useful, but only if it’s a regular occurrence.

Is there are workflow for creating new directories??... EG setting ACLs, replicating the structure to the related data directories, etc?
If you don’t need one of those, maybe a rename workflow wouldn’t be needed as well, and could be taken care of by IT.
I simply just don’t like regular users fiddling with things like this.
But most of our end users aren’t technically inclined and this could be different for you.

John Cuiuli
Consultant
Sydney, Australia

Migrateduser

Users can change directories in their pre-CMS environment using FrontPage or whatever. Some of these tools find all the references to the directory and update the links. There are no extended attributes and other issues to deal with, and no administrator needs to be involved. It is critical that they be able to do this for policical reasons. They think it is an incredible step backward if the same functionality is not available in the CMS. I have to build a custom menu item to allow them to create a directory (set permissions, specify which templatedata/category/type/data directories the corresponding directory should be created under, etc.).

Thanks,

-John