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; } } }

Teamsite folder structure replication on portal

jkm

Hi All,

We have a requirement where we want to display the complete document structure in the Teamsite to portal so that portal can read this at run time and build the document hierarchy at run time.

We thought through two approaches for this

1) Deploy the files on web server and then portal can read the information at run time from WS and display the document hierarchy. As the number of documents grow, this can be an awful design from performance stand point for sure.

2) Second thought process to pump each record in the portal database where we will enter the document path and its parent path. In this the problem will be, we can not set EAs on the folders, so we need to create dummy file per folder basis. Further we need to customize all the new, move, rename, delete events so that any operation in the CMS is reflected in the portal database. This sounds like quite a lot of work.

Would like to know your thoughts how this can be done in easy ways. For me this seems to be a simple requirement where we want to publish the TS file structure to portal env and there should be something OOTB feature for such things.

Can we use DAS for this..thoughts?

Find more posts tagged with

Comments

jkm

Any thoughts folks...let me know if you need more information to provide your inputs?

Migrateduser

Hi JKM,

When you say document structure iam assuming it to be the Teamsite Branching structure.

Here are some of my ideas on how can achieve this.

1. Deploy complete teamsite directory structure to a remote server using Opendeploy and manage the remote folder structure using deployment mechanism such as remote diff etc. But you are right as the documents grows it impacts the performance.

2. If you are using Portal then you might try using Interwoven Teamportal to display the teamsite branching structure ( iam not sure why you want to display the teamsite branching structure) but here is one way

3. DAS can used to sync the content of the form to the database. iam not sure if you can use DAS to store the hirarchy of the content as well.

jkm

Thanks Santvs for your reply..

Hi JKM,

When you say document structure iam assuming it to be the Teamsite Branching structure.

This is folder structure inside the branch not the complete branching structure

Here are some of my ideas on how can achieve this.

1. Deploy complete teamsite directory structure to a remote server using Opendeploy and manage the remote folder structure using deployment mechanism such as remote diff etc. But you are right as the documents grows it impacts the performance.

yes this kind of design will not be accepted by any stage.

2. If you are using Portal then you might try using Interwoven Teamportal to display the teamsite branching structure ( iam not sure why you want to display the teamsite branching structure) but here is one way

We are not using Teamportal product and this is a big change on the production platform, so can not go with this option by any means.

3. DAS can used to sync the content of the form to the database. iam not sure if you can use DAS to store the hirarchy of the content as well.

I think need to scratch my head more on DAS which can be a solution...

This should be standard OOTB product feature for such work supported by IWOV. This is unnecessary coding to do this kind of standard functionality Smiley Sad

Husna

Were you able to achieve this?
We have a similar requirement.
It would be helpful to know how did you finally implement this.

Reghunath

Hi,
Assuming you need to know just the folder structure and files information(just file names) and you are not going to use them for links in webpage.

In your deployment workflow you can add an external task to look for Workarea directory pattern and if any file attached to the workflow matches portal directory structure, read the Portal directories/file listing using perl FILE modules/java APIs and build an xml with the directory/file information and attach to the workflow. This program gets triggered whenever user deploys any file/directory and reflects the latest directory/file listing as light weight XML or HTML or whatever format your Portal application needs.

Your portal application can consume this to build the directory structure.

Hope this works for you...