About channel specific content

The standard schema defaults to

•The basic article elements, that are not channel specific. Therefore, the head, body, jumpHead, subHead, kicker, intro, pullquote, photoCaption, urlCaption will by default go in all channels, except in cases that a specific channel element exists.

•The channel specific elements: webHead, webbody, smsbody, blogPost, twitterMsg, facebookMsg, galleryCaption, videoCaption, audioCaption. Such elements don't go in the print channel.

The list of default article elements

In version 2.1:

<xs:element ref="head" minOccurs="0" maxOccurs="1"/>

<xs:element ref="webHead" minOccurs="0" maxOccurs="1"/>

<xs:element ref="blogPost" minOccurs="0" maxOccurs="1"/>

<xs:element ref="jumpHead" minOccurs="0" maxOccurs="1"/>

<xs:element ref="subhead" minOccurs="0" maxOccurs="1"/>

<xs:element ref="kicker" minOccurs="0" maxOccurs="1"/>

<xs:element ref="intro" minOccurs="0" maxOccurs="1"/>

<xs:element ref="body" minOccurs="0" maxOccurs="1"/>

<xs:element ref="webBody" minOccurs="0" maxOccurs="unbounded"/>

<xs:element ref="smsBody" minOccurs="0" maxOccurs="unbounded"/>

<xs:element ref="twitterMsg" minOccurs="0" maxOccurs="unbounded"/>

<xs:element ref="facebookMsg" minOccurs="0" maxOccurs="unbounded"/>

<xs:element ref="pullquote" minOccurs="0" maxOccurs="unbounded"/>

<xs:element ref="photoCaption" minOccurs="0" maxOccurs="unbounded"/>

<xs:element ref="urlCaption" minOccurs="0" maxOccurs="unbounded"/>

<xs:element ref="audioCaption" minOccurs="0" maxOccurs="unbounded"/>

<xs:element ref="videoCaption" minOccurs="0" maxOccurs="unbounded"/>

<xs:element ref="galleryCaption" minOccurs="0" maxOccurs="unbounded"/>

In older versions:

<xs:element ref="objGroup" minOccurs="0" maxOccurs="unbounded"/>

<xs:element ref="head" minOccurs="0" maxOccurs="unbounded"/>

<xs:element ref="webHead" minOccurs="0" maxOccurs="unbounded"/>

<xs:element ref="blogPost" minOccurs="0" maxOccurs="unbounded"/>

<xs:element ref="jumpHead" minOccurs="0" maxOccurs="unbounded"/>

<xs:element ref="subhead" minOccurs="0" maxOccurs="unbounded"/>

<xs:element ref="kicker" minOccurs="0" maxOccurs="unbounded"/>

<xs:element ref="intro" minOccurs="0" maxOccurs="unbounded"/>

<xs:element ref="body" minOccurs="0" maxOccurs="unbounded"/>

<xs:element ref="twitterMsg" minOccurs="0" maxOccurs="unbounded"/>

<xs:element ref="facebookMsg" minOccurs="0" maxOccurs="unbounded"/>

<xs:element ref="photo" minOccurs="0" maxOccurs="unbounded"/>

<xs:element ref="pullquote" minOccurs="0" maxOccurs="unbounded"/>

<xs:element ref="photoCaption" minOccurs="0" maxOccurs="unbounded"/>

<xs:element ref="urlCaption" minOccurs="0" maxOccurs="unbounded"/>

<xs:element ref="audioCaption" minOccurs="0" maxOccurs="unbounded"/>

<xs:element ref="videoCaption" minOccurs="0" maxOccurs="unbounded"/>

<xs:element ref="Tables" minOccurs="0" maxOccurs="unbounded"/>

<xs:element ref="videoLink" minOccurs="0" maxOccurs="unbounded"/>

<xs:element ref="mediaGalleryCaption" minOccurs="0" maxOccurs="unbounded"/>

The list of elements in your GN4 system may be different.

Adding the channel-specific elements to the schema

You can add any number of channel-specific elements, e.g. webBody, webPhoto, digBody (digital edition) etc.

Such elements will be exported only to the specific channel.

The channel-specific elements are independent. If you change anything in the content of the body element, the change is not replicated in webBody, or in any other element. The common container (article), ties the elements together, but their content is independent.

Many users can edit many article elements at once, as long two users do not attempt to edit the same element. Example: a user can edit body, and another user can edit webBody at the same time.

Copy flow of channel-specific elements

You can send a channel-specific element in another folder independently of the article, so they can follow different workflows. For example, paper body can reside in the folder W with the workstate X, while the web body element can reside in the folder Y with the workstate Z.

This provides for the multi-channel copy flow.

You can mark certain parts of text just for specific channel (region). Such parts of text are exported only to that channel.

See Routing parts of text only to Web channel and Routing parts of text only to print edition for automated procedures. See Routing parts of text to a specific channel for a general procedure.

The text, marked for specific region may appear in the source pane painted by user-specific attributes, defined in user preferences, and depending on the current region.