Source Metadata
The metadata (javadoc/XSD) are complementary information to the content that allows control over its publication. Below are the tags that must be available in the douidefinition.xml
file, assuming all publication properties have been selected.
The supported metadata for source content is listed below.
<publishToServiceInstances/>
-
Publication of content to instances of the same service.
<publishToSocialNetwork/>
-
Publication to social networks.
<publishToPrincipals/>
-
Publication to groups.
<publishStartDate/>
-
Publication date/time.
<publishEndDate/>
-
Expiration date/time.
<highlight/>
-
Highlight.
<highlightEndDate/>
-
Highlight expiration date/time.
<comments/>
-
Comment.
<versioning/>
-
Content version control.
<multiLanguage/>
-
Publication of content in more than one language.
<workflow/>
<association/>
-
Allows the service to be associated with another.
<lock/>
-
Indicates that the current source uses the content locking and unlocking tool.
<categorization/>
-
Enables the categorization metadata for filters and display in lists.
<tag/>
-
Enables the use of tags in the content. For effective use, a tag repository must be associated with the service instance. For more information, refer to the Tag page.
<seo/>
-
Provides the content publisher with access to a specific registry for data used in SEO and sharing for social networks. For more information, refer to the SEO & Sharing page.
<slug/>
-
Gives the content publisher a registry for a slug for the content. This slug can be used to obtain details about the content through a REST API.
<primaryContent/>
-
Defines the content as primary content. For more information, refer to the Primary Content page.
Content Version Control Metadata (versioning)
LumisPortal has a mechanism for cleaning old versions of content to avoid pollution from very old versions. The cleaning is done in a way that retains the newer versions of content and removes the older ones. This cleaning is enabled at development time, on the source to which the content to be cleaned belongs.
To do this, simply add the maxVersions attribute to the versioning node. If such an attribute does not exist, cleaning will not occur. This attribute indicates the limit of versions to be retained (the most recently created will be kept). The expected value for this attribute is an integer greater than one. It is important to emphasize that version cleaning never removes the active version or the published version.