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

One DCT, multiple DCRs

StephXIII

Hi,

Is it possible to save data input in one DCT into more than one DCR ?

Our users wants to group the input of different contents (DCR) in one unique datacapture template.

Can we do this kind of stuff with FormAPI ? With something else ?

Thank's
Steph

Stéphane

Find more posts tagged with

Comments

Adam Stoller

As a DCR represents a filled in DCT and a DCT is specific to a category/type - I'm not sure that the idea of splitting a single DCT into multiple DCRs makes any sense.

I can think of ways to post-process the DCR and split it into multiple DCRs programmatically - but that seems like a lot of work to go through for an un-clear gain.

Why would you group content for different DCRs in one DCT?

There have been numerous cases whree one DCR may contain *references* to other DCRs such that the resultant generated page may be a consolidation of multiple sources of content - but that doesn't sound like what you're asking about - or is it?

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

StephXIII

Hi Fish,

It's on a 'virtual' case. We are thinking about a new organisation of our contents mainly to split the contents into very independant pieces to facilitate their reuse in many projects. One of the ideas is to separate the way the users input the contents and the "technical view" of these contents (DCR). It's almost the same separation layer as this between the TPL and the contents.

This organisation could allow the business users to input business contents without any knowledge of its final destination. By example, a product manager could input all the informations about his product from one unique interface (DCT) without knowing which field goes into which DCR, branch or even final site.

I don't know yet if it's realistic nor usefull, but it could add an abstraction layer between the content and the way you contribute it.

Best regards,

Stéphane

gzevin

Stephane,

I dealt with a similar issue, when the same content had to be (potentially) re-used in a number of pages.

What I have siggested was a 'warpper DCT', that would point to component DCRs. Actually, user could choose only 'approved' content, i.e. from Staging (however this could be changed based on your business requirements).

Essentially, the business user would come and 'assemble' their content based on 'include' DCRs.

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

StephXIII

Hi Greg,

It's what I had in mind. It seems to be very interesting.

How did you develop the wrapper DCT and was this development expensive ?
Is it based on a specific content organisation or can it be used with any content ?

Thank you by advance

Stéphane

gzevin

Stephane,

The development of the wrapper as such is not that expensive. What you also have to bear in mind is the menu structure and breadcrumbs - the business logic to control this could differ. One could choose the auto-generate menus on the fly or pre-generate navigation and include it as SSI inclides. In the latter case, one would choose a DCR with an article and appropriate navigation, that in turn relates to a breadcrumb.... Another thing to consider is the presentation template (preview/etc), and also this has to be tied to a workflow that will resolve chicken/egg problem (I mean what comes first - the NAV item or the wrapper itself).

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