Template to capture Sitemap or hierarchy of website

Hi,
I have to create DCT to capture hierarchy or Sitemap kind of thing. We have TS6.7.2(Solaris) but we are not using Sitepublisher as Some other portal is being used.
1. Can someone guide, how to achieve this w/o SP?
2. Relationships will be maintained in the DB (Oracle using DD) from where portal will pick it up. Is it possible just to use Sitemap tab to get this done?
Pointers would be very helpful.

Thanks.

Find more posts tagged with

Comments

nipper

It is quite easy to do this without SP. However to do it correctly you need to change all DCRs as well.

The way I implement this is a Navigation DCR, with containers for the 1st level, then containers of children and then containers of children of them.

When I make a DCR, I read the Navigation DCR and the user chooses the page being created (or the parent of the page being created)

Then you can do top/side navigation, breadcrumbs and sitemap easily.

Without integrating this into all your DCRs you then duplication information and some data will be out of date (i.e. change the title of a 2nd level page then the breadcrumb of children will be out of date unless you change the Navigation DCR as well).

vpatel

In addition to what Andy just said, in some cases a single "Navigation DCR" tend to get extremely large for larger sites. In that case, instead of having 100s of nested replicants in a single DCR, you may have to break them out into multiple DCRs -- probably one for your primary level navigation item. Other than that Andy has you going on the right track.

CRB

It is quite easy to do this without SP. However to do it correctly you need to change all DCRs as well.

I actually implemented the exact same thing, however i didn't have to worry about the DCRs since the DCR path was part of the info the user enters in navigation DCR. what did you mean by "change all DCRs"? like what would the change be?

and as vpatel said, loading large DCR is very slow and sometimes impossible in IE. i broke the site into 8 sections (DCRs) since i didnt have to worry about relationship between the sections. even with that i still have performance issue. so i am thinking about a better way to manage the sitemap till we move to SP.

nipper

I add a select list to all DCRs. The user chooses the parent (or page location) so it can calulate the breadcrumbs and menu

If you change the DCR then you can regenerate the pages and get the correct data. This is if the breadcrumbs and navigation are static

BTW, the IE load large DCR bug has been fixed, there is a patch for 6.7.1 SP1 and it is fixed in 6.7.2

merry

The way I implement this is a Navigation DCR, with containers for the 1st level, then containers of children and then containers of children of them.

When I make a DCR, I read the Navigation DCR and the user chooses the page being created (or the parent of the page being created)

Hi, Thanx for ur reply.
Creating a navigation dcr with containers is fine. But i am not clear how to associate other DCRs with navigation DCR while creating them.

nipper

Use an inline call that reads the Navigation DCR and produces a select list of pages

merry

Thanx for d reply.
I will certainly try that out. But is there is possible to get the Tree structure?

nipper

Sure the DCR is the tree structure. The select list in the child DCR decides where the specific page falls into the tree

merry

That is very helpful for me. Thanks a tonne.

CRB

Your job is actually easy since you already have folder structure with pages (your arent moving pages from existing to new folder struction):

1) use perl or something to go throu your website structure, save that structure in a text file or as an excel sheet (file 1). at the same time, map each html file you hit to its DCR and save that data in another text file (file2).

2) then using perl again or any other scripting or programming lang to create the DCRs ( xml files ) based on your folder structure (by reading file1). each container (node) would represent a folder (or page) and each item in the container (element) would represent a peice of info about the page (name, url, dcr ... ).

3) then set data-type attribute to turn the xml files into DCRs

but before all that, you have to know how the DCR is gonna look like in terms of all the fields needed... so each DCR would like this:
[HTML]

...

...

...

...
...

[/HTML]

those are just some general steps of what needs to be done, so use your creativity to come up with the details.

merry

That's very useful information. The website is under construction, so currently there isn't any structure to migrate from.