Featured Content

C H A P T E R 17

17.1 Enabling Featured Content

This feature is initially disabled for both the PC-based Subscriber Portal and the device-based Subscriber Portal. To support the ability to feature specific content items, follow these steps:

1. Enable the feature in the portal of your choice.

Set the following properties in the $CDS_HOME/deployment/deployment-name/conf/SubscriberPortal.properties file:

featured_content.desktop.show - Set to true to show content marked as featured at the top of each page when browsing content in the PC-based Subscriber Portal. Set to false to not show an area for featured content.

featured_content.device.show - Set to true to show content marked as featured at the top of each page when browsing content in the device-based Subscriber Portal. Set to false to not show an area for featured content.

2. Set the number of featured items shown.

Set the following properties in the $CDS_HOME/deployment/deployment-name/conf/SubscriberPortal.properties file:

featured_content.desktop.display.number - Number of items to include in the list of featured content when shown on the PC-based Subscriber Portal. The default is 2. This property is ignored if the featured_content.desktop.show property is set to false.

featured_content.device.display.number - Number of items to include in the list of featured content when shown on the device-based Subscriber Portal. The default is 1. Keep in mind the limited display size of most devices when setting this property. This property is ignored if the featured_content.device.show property is set to false.

If more content items than the default number are marked as featured, the items are shown in ascending order based on the value set for the feature order until the default number to display is reached.

3. Define the custom fields that are needed.

The custom fields used by this feature are included in the $CDS_HOME/deployment/deployment-name/conf/CustomField.properties file as comments. Uncomment the properties shown in the following code sample by removing the pound sign (#) at the beginning of each line:

emf.all.isfeatured.scope=item
emf.all.isfeatured.required=false
emf.all.isfeatured.datatype=boolean
emf.all.isfeatured.editable=vm
emf.all.isfeatured.viewable=vm
emf.all.isfeatured.reserved=true 
 
emf.all.featuredorder.scope=item
emf.all.featuredorder.required=false
emf.all.featuredorder.datatype=number
emf.all.featuredorder.editable=vm
emf.all.featuredorder.viewable=vm
emf.all.featuredorder.reserved=true

Note - The label properties for these fields are defined in the $CDS_HOME/deployment/deployment-name/localization/VendingManagerMessages.properties file. The properties are not initially commented out so no action is needed.

4. Include the custom fields in the search schema.

The statements needed are included in the $CDS_HOME/deployment/deployment_name/conf/vss/solr/conf/schema.xml file as comments. Uncomment the following statements by removing the pound sign (#) from the beginning of the line:

<field name="emf.isfeatured" type="boolean" indexed="true" stored="true"/>
<field name="emf.featuredorder" type="sfloat" indexed="true" stored="true"/>

5. Restart the Vending Manager.

17.2 Configuring Featured Content

The Vending Manager administrator configures featured content using the Vending Manager administration console. The administrator identifies the content to feature and assigns the order in which the content appears. See the Vending Manager administration console online help for information on setting the custom fields associted with featured content.