Can a diff. file structure be maintained in TeamSi

Whether a file structure can be maintained in the Teamsite Server with the folder names more meaningful from the point of view of the actual content contributor but different from the actual folder names in the web server. We have a folder called Chapter1 in the web server, can we create a folder called 'Johnfolder' in the Teamsite file structure which will map to Chapter1 folder in the web server when we upload 'Johnfolder' from TeamSite server to presentation server.

Find more posts tagged with

Comments

PaulW

So you want the contents of one folder in TS to be 'mapped' to the contents of a folder with a different folder name on the WWW server?

This would be done by configuring your dpeloyment script. For every folder that you want to be different, you would need a different path and target path section in the OpenDeploy configuration script.

Adam Stoller

Yes - this can be done - but I strongly recommend against it. The more your directory structures are identical - the easier it is to implement solutions. Conversely, the more different they are, the more difficult it is to implement solutions (something that might take 1 day to implement could easily take over a month ! if the structures are not the same)

--fish
(Interwoven Senior Technical Consultant)

gzevin

Adam,

how this could be done? One of my clients have this as a no. 1 requirement. - they have started with certain folder names/structures - and in their information architecture (IA) they have had a direct mapping between directory names and section names (for their web site). Now - section names have changed, but directory structure remains the same. And this is confusing, as the users are really non-technical...

Well, in TS6 I'd reccomend them to simply create favourites and stick to them, but in pre-6 environments there is not much they can do...

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

Adam Stoller

The problem is that if your directory structures don't match - you have to deploy each directory separately as you need to map them on a 1:1 basis - and this becomes really difficult if the structures differ inside nested folders (you'd have to set up deployment definitions that essentially deployed the contents of a folder with exclusions for its sub-folders and then have separate definitions for each of the sub-folders - a nightmare in development, testing, and maintenance).

If the web-site structure changes - make the same changes in TeamSite - rename folders, move folders, etc - so that you can maintain a relationship between them. Your deployments then become [near] trivial to develop, test, and maintain - also as the users learn their new website structure, they can map that knowledge into where files live within TeamSite - and vice-versa.

--fish
(Interwoven Senior Technical Consultant)