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

Content reuse

tsrookie

Gidday All,

We are trying to facilitate content re-use across our implementation.

For each content record we create we are writing a pages metadata out to a database as part of the metadata we will also record the location of the dcr for that record.

If a page is reused across multiple branches a table will be used to record in which branches a piece of content is being reused.

For example I wil use the privacy statement, each of our institutes will have their own look and feel we would like to author the privacy statement in the admin branch. The presentation template for the privacy statement would then do a lookup in the database to find the location of the privacy master dcr and draw the content from their thus applying the look and feel for each institute when the page is generated.

If in the future the privacy dcr is edited the page generation proces will then do a lookup in the database to see where a piece of content has been reused and regenrate the pages in the affected branches as well.

Thats the theory anyway, has anyone had experience with this sort of thing am I on the right track.

Regards
Colin

Find more posts tagged with

Comments

Dwayne

Sounds like you've got most of the bases covered pretty well.

Some things you'll need to think about:

How will users choose this content for re-use? You'll propbably have to write a CGI callout to browse the database
How do you decide which pieces of content are available for reuse? All; only admin branch; by user selection; etc
What happens after the referencing page(s) are regenerated? Should they be left as "modified" in the workarea, or should they be automatically be submitted to staging? Or a combination - submit if it was unmodified, leave modified if it already WAS modified
How will you handle multiple workareas for the same branch? In which workarea will you do the regen?
What do you do when a referenced piece of content is deleted?

There are probably others as well, but that's enough for starters.

--

Current project: TS 5.5.2/6.1 W2K

Adam Stoller

What happens after the referencing page(s) are regenerated? Should they be left as "modified" in the workarea, or should they be automatically be submitted to staging? Or a combination - submit if it was unmodified, leave modified if it already WAS modified

Hmm - an interesting alternate possibility is you do the adjustment in a temporary workarea based off the latest edition + current submissions in staging, re-generate and re-submit, and then if the file was modified in any other workarea it remains modified *and* in conflict - requiring a merge... Unfortunately I don't think conflict/merge works very will in DCRs (haven't tried it in 6.1 yet - perhaps they've finally addressed this issue?)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

gzevin

if one does not want to use a DB, we could think of different techniques as well.

say, your policy is generates as an SSI component - then all you need to do is to have a list of separate presentation templates that are invoked from ONE PT for this component. This PT will automatically generate new policies pages - of course, some scripting will need to be involved in order to sumbit and propagate all the changes everywhere,,....But this needs to be done in any case

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

tsrookie

Thank you all for your replies,

The database is in, the project is stage one of a bigger project, the metadata is being written to the database to make it searchable and re-usable.
We are using our Internet site rebuild as a pilot for content reuse.

Via the workflow as each page is deployed the metadata will be attached as TS ea's and written to the database. Later in the Year we will also use metatagger to pre-populate some of the metadata fields.

Its my job to figure out how to facilitate the reuse of the content.

Cheers
Colin

gzevin

well, in doing so with metadata your are going against the stream - in TeamSite 6.5 the search will be done using OEM'd Verity engine, so no need to worry now about this.

however, your implementation could have some specifics that I am not aware of...

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

tsrookie

Hi Greg,

the use of the database was scoped before the announcement of the verity search, we have to deliver by november and can't wait for TS 6.5, you should've seen our draws drop when Interwoven presented to us only a few weeks ago about TS 6.5 and the inclusion of the verity search.

Colin

gzevin

oh, don't worry then - you cannot go live till at least 6.5.1..... which will be next yesr I suppose

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