The Web Content resource collection

 

+

Search Tips   |   Advanced Search

 

The Web Content resource collection is installed and configured out of the box. This pre-defined collection allows us to write rules which select lists of content from IWWCM . Rules specify which web content to show in a Portal Personalization component in Web Content Management. The Personalization component is similar to a menu component in that its content is decided by a rule. The Personalization component specifies how the content returned from the rule is presented and points to a rule to decide what content to display. That rule may make use of the Web Content resource collection to select a list of web content.

The Web Content resource collection allows rules based on the following attributes:

Attribute Description
Author Author of the content as set in Web Content Management. This attribute value is stored as a 'distinguished name,' for instance, uid=wpsadmin,o=Default Organization.
Authoring template The authoring template used to create the web content. The value may be selected using an authoring template picker.
Category The categories to which the piece of web content belongs. If you are matching this attribute to a value from another resource collection or application object, the format for the value should be /parentcategory/childcategory.
Creation date Date the piece of web content was created.
Creator Person who first created this piece of web content. This attribute value is stored as a 'distinguished name,' for instance, uid=wpsadmin,o=Default Organization.
Description Description provided for the piece of web content.
Expiration date Date the content is set to expire in Web Content Management.
Full text Use this attribute to search the full text of a piece of web content. It should be used sparingly. This attribute may not perform as as other attributes when used in rules, especially when used in conjunction with other attributes.
Keywords The keywords stored on the piece of web content.
Last modified date Date a modification last occurred on the piece of content.
Last modifier The last person to modify the piece of content. This attribute value is stored as a 'distinguished name,' for instance, uid=wpsadmin,o=Default Organization.
Name The name of the piece of web content as specified in Web Content Management.

This property uses case-insensitive matching. For example, a piece of content with a name of "SampleContent" matches "SampleContent," "samplecontent," "SAMPLECONTENT," and other variations.

Publish date Publish date as specified in Web Content Management.
Site area The site area from which to select content. The value may be selected using a site area picker. If you are matching this attribute to a value from another resource collection or application object, the format for the value should be a /-delimited string starting with the site and followed by the hierarchy to the desired site area, as in...

/site/sitearea/sitearea

The "starts with" operator operates on path segments. For example, /Portal/Personalization starts with Portal is true, but /Portal/Personalization starts with /Portal/Pers is false, because there is no site area called 'Pers'.

The site area property is optional. It must be used as a single condition, be the first condition in the rule, and use an AND operation with all other conditions. A rule may or may not include a condition using site area, and may only include a site area condition and no other conditions.

Rules from previous versions that made use of the site area property will need to be manually updated.

Title Display title as specified in Web Content Management.

When a text, numeric, or date component is added to an authoring template in Web Content Management, that component will appear as an attribute on the resource collection. For example, if an authoring template is created for "Benefit Announcement" which includes an "enrollment begin" date component, you will have an "Enrollment begin" attribute on the Web Content resource collection. This new attribute would appear under a submenu for "Benefit Announcement". This will allow us to write rules based on custom metadata you attach to web content. The performance of the standard metadata will do better compared to the performance of rules using attributes added to authoring templates. The use of keywords and categories should be considered since these are part of the standard metadata of web content.

All attributes which store a reference to a person are stored as distinguished names. This format will match against the value of the Distinguish Name attribute on the Portal User resource collection. For instance, to select all documents authored by the user viewing the portlet, you would write, "Author is current Portal Users.Distinguished Name."

 

Related information

Presenting personalized content