Context Sensitive Content (CSC)
Sections:
Database Table
Set up
Managed DB derived Html Page Content
Managed subcomponent HTML Page Content
Multilingual Strings
Suggestive Selling Content
Suggestive Selling Buybuttons
Category Descriptions
Brands Descriptions
Search Engine Content
E-mail Broadcasts
Knowledge-base or Message Board
Blog Tools
SEO Records
Context Sensitive Content (CSC) is a powerful system which renders embedded content on-the-fly for visitors which contain messages and information keyed to the exact activity or source of the visitor. CSC is also used to create e-mailable content which is sent out via the e-mail broadcast system and knowledge-bases.
CSC can be used in these ways and more:
Website customization is required for all functions other than "SUGGESTIVE SELLING CONTENT" (manual version).
Content types 1 - 8 are reserved for key records. Content types 9 - 12 are reserved for SEO. Content types 13 is resevered for HTMLP content. Content types 1000 - 2000 are reserved for KBs. Content types 3000 - 10000 are reserved for blogs.
Using the CSC admin page is user friendly way of managing content. This DB derived content is displayed in the center of the page using the CLDRCSC.ASP templpate files. This content is used for 100% managed content the same way Subcomponent HTML Pages are used. The same techniques and JavaScript tools used for subcomponent HTML Pages are used for CSC Managed pages.
The CSC record for this content is ContentType = 13.
Key1 = record selection field i.e. CLDRCSC.ASP?RS=key1
Key3 = Page Title
Content = the HTML content for the page
ContentLocation = Country/Language code (en,es,de,etc.), used only in multilingual mode. One code per CSC record.
notes:
see Subcomponent HTML file management for details on using static html subcomponent files as another means of content management.
This record is used to hold multilingual strings which are used on the SendSafe cart and account pages.
The CSC record for this content is ContentType = 15.
Key1 = the full file name of the cart page OR the reserve word CUSTOMERMMI for MIMarketingInfo
Content = a set of strings which are delimited by "~"
ContentLocation = Country/Language code (en,es,de,etc.), used only in multilingual mode. One code per CSC record.
notes:
This content is displayed in the product showcase page merged onto the page after the buy buttons. This content is often used in combination with Suggestive Selling Buy Buttons (CSC ContentType = 8). One CSC record will be displayed per showcase page.
The CSC record for this content is ContentType = 1.
The CSC Key fields are used:
key1 = keyword is the record selection or linkage field (this value must be present in the items.keyword field for all items which are to display this CSC Record).
OR
key1 = "#DEFAULT" this record will be selected if cscShowCaseRANDSuggestiveSell = true AND no keyword occured.
notes:
This CSC is used to implement "item pairings" for suggestive selling such as: "These items are best purchased together."
This is a set of buy buttons which are displayed on the product showcase page after any Suggestive Selling Content (Contenttype=1) is displayed. There can be N number of matching CSC records of this type for a given Items record. CSC linked Items with FFPs will not have their FFP dialogs rendered, instead a CUSTOMIZE or other buttons will replaced the BuyButton for this item.
The CSC record for this content is ContentType = 8.
A CSC Suggestive Selling Content Record (ContentType = 1) must also be assigned for the product OR no buybuttons will be rendered. The only exception occurs when "cscShowCaseRANDSuggestiveSell" is enabled and a display of randomly selected CSC BuyButtons are displayed; in this case the #DEFAULT CSC Content is automatically dislayed. If the #DEFAULT CSC content record is not present, RANDOM BuyButton suggestions will not be displayed.
The CSC Key fields are used:
key1 = keyword is the record selection or linkage field (this value must be present in the items.keyword field for all items which are to display this BuyButton).
key2 = The sku for the suggestive selling BuyButton item to be included
notes:
One select query per showcase page is performed to retrieve suggestive sell items for display. The query can match an unlimited number of suggestive selling items records.
Select * from items, itemsExt
where sku in (Select rtrim(key2)
from ContextSensitiveContent, items
where ContentType = 8
and keywords like '%contents of key1%'
and sku = the first SKU retrieved for the showcase product
and enabled = 1)
and items.itemcodeId = itemsExt.itemcodeid
order by fullname
This content is displayed on any website page as merged or replaced content. This CSC function requires custom ASP webpage development on the site. The key purpose of this Search Engine CSC is to dynamically display different webpage content based on the search engine terms which were entered into the such engine (such as Google or Yahoo).
The CSC record for this content is ContentType = 2.
The CSC system will first attempt to match all four keys (key1,2,3,4), then three keys (key1,2,3), then two keys (key1,2), with one key matches discarded.
The CSC Key fields are used in an SQL select clause to
match incoming HTTP Referral information as follows:
key1 = Search Phrase 1
key2 = Search Phrase 2
key3 = Search Phrase 3
key4 = Search Phrase 4
notes:
The CSC ContentLocation field must match root the webpage being loaded.
This content is used for creating content for e-mail broadcasts or for I-CRM e-mails. The CSC subsystem can be used to create standard set of reusable e-mails or a one time e-mail. Using CSC is the typical way e-blast are authored and sent.
There are two different kinds of CSC E-Mails:
In the case of I-CRM e-mails the CSC content can contain I-CRM mail-merge variables which are replaced with values taken from DB records.
The CSC record for this content is ContentType = 3.
These entries for e-mail broadcasts are:
Make sure all records (CSC and Advertisements) are enabled.
The format of the e-mail:
From: sales@mybiz.com To: mycustomer@theirbiz.com Subject: You have left un-purchased items in your shopping cart
|
VERY IMPORTANT Do not change the record being sent until the e-mail blast has completed. Do not run more than one broadcast job at time. Changing the record before the e-mail blast has begun or running multiple jobs at the same time can result in unexpected results such as mixed subject lines or duplicate emails beging sent out. To check status on an I-CRM job load either the CSC Admin page or Job Queue. When an I-CRM job completes, an email will be sent to the return address set for the message AND to the CC Mail list configured for the storefront.
CATEGORY DRILLDOWN DESCRIPTIONS
This content is used solely as a means of adding a description for category icons when in Matrix product browsing mode. The content of each CSC will be displayed next to the category icon in a similar format as seen in the product display level of drilldown browsing.
The CSC record is related to a category by key1.
E-Business framework the configuration keyword catDrilldownLabeling = true OR listingCatDrilldownLabeling = true
The CSC record for this content is ContentType = 5 for products and 6 for listings.
These entries for category labels are:
Note: Categories flagged with an "@" in the category name must use the full category name including the "@" in the category name field of the CSC record.
This content is used solely as a means of adding a description for brand icons when in Matrix browsing mode. The content of each CSC will be displayed next to the brand logo (icon) in a similar format as seen in the product display level of drilldown browsing.
The CSC record is related to a brand by key1.
E-Business framework the configuration keyword brandDrilldownLabeling = true
The CSC record for this content is ContentType = 7.
These entries for brands labels are:
Enhanced SEO System CSC records are used to setup and tune enhanced automated SEO.
For categories:
For subcategories:
For showcases:
For brands:
For static content pages:
KNOWLEDGE-BASE OR MESSAGE BOARD
CSC can be used to create newsletters, mini-blogs, message boards, bulletin boards, announcement, or other collections of articles and factoids.
This content can be used for e-mail broadcasts.
The CSC record for this content is ContentType = 1000 - 2000; where each numeric value is a separate knowledge-base
These entries for are:
The system is linked into the e-mail broadcasting system, so with the push of button you can send an article in an e-mail blast to all customers who have signed up (think e-mailed newsletter). In an e-mailed newsletter, up to three type 10 ads will be included at the end of all broadcasts.
SendSafe comes with a Knowledge-base reader. This webpage is designed to index and display a set of articles. To use the Knowledge-base reader, open the webpage: Store.kbreader.asp?Ctype=1000 (where Ctype = the set of records defined by ContentType).
The reader displays a dated list of articles chronologically at the top of the webpage. Clicking on any article will open the article in the "viewer pane" located directly below the list. In the example below, someone has clicked on the "Electric cars of the Future" link.
Set of articles are managed with a very easy to use Admin page. Articles can have any kind of HTML, pictures and text. There is a built in HTML editor on the admin page OR you can use some other editor and then copy & paste.
CSC can be used to create full featured blogs. This content can be used for e-mail broadcasts. The CSC record for this content is ContentType = 3000 - 10000; where each numeric value is a separate blog.
Information on using blogs can be found on this page.
There are three visitor pages:
The Basics:
Editing and setup notes:
These CSC entries are used for blogs:
Review and approval for Publication (blog moderation) is required before a blog entry is displayed on the site. An entry will be displayed when the following fields are set:
Records with a CSCPublicationProcessingStep=>1 are canidates for publication. Records with a CSCPublicationProcessingStep=0 are being edited by the visitor. You can find all records in CSCPublicationProcessingStep1 or 2 by performing a FIND operation then going through each record in the list selecting or rejecting publication.
Rejecting publication can be done manually or by using the [Reject for Publication] button. It is recommend that the [Reject for Publication] button be used. This button will set Enabled=0 and CSCPublicationProcessingStep=3 (i.e. moderation tasks are complete for this record). Automated notication of blog entry status changes are not provided to the author in any way.
Formatting of headlines is controlled by each record by the CSCheadlineFormatCode. Each headline is display in a separate content box arranged one after the other vertically on a page. Beyond the verticial orientation, all other fortmat is controlled by the code.
Headlines:
Format Code CSS tag Description 1 BlogFmt1* Standard vertical layout with picture CSCpicturefileB, title, and summary one below the other. The read more link is at the end of the summary. Horizontal lines seperate each headline. 2 BlogFmt2* Abbreviated horizontal layout with picture CSCpicturefileB on the left and a text block on the right consiting of: date,author, & title (no summary). The read more link is at the end of the the content block. 3 BlogFmt3* Press Release layout with date on the left and the title (no summary) on the right. The read more link is at the end of the the title block. 4 BlogFmt4* Same as #1, Standard vertical layout with picture CSCpicturefileB, title, and summary one below the other. The only difference from #1 is the author's name does not appear on the headline summary page. The read more link is at the end of the summary. Horizontal lines seperate each headline.
Articles:
Format Code CSS tag Description 1 BlogArticleFmt1* Standard vertical layout with the only picture (CSCpicturefileA) displayed (all other pictures are not displayed), title, and article one below the other. The go back link is at the end of the article. 2 BlogArticleFmt2* This is 100% Free-form content except for the return (goback) link. All content other than the link it derrived from the ContextSensitiveContent.Content DB field. 3 BlogArticleFmt3* Press Release layout title, date and release one below the other. CSCpicturefileA will be displayed if present. The go back link is at the end of the release. 4 BlogArticleFmt1* Same as #1, standard vertical layout with ALL seven pictures displayed (in order a-b), title, and article one below the other. The go back link is at the end of the article. The author's name is at the bottom of the article. 10 BlogArticleFmt1* Same as #1, Standard vertical layout with the only picture (CSCpicturefileB) displayed (all other pictures are not displayed), title, and article one below the other. The difference is that CSCpicturefileB is used instead of CSCpicturefileA. The go back link is at the end of the article.
Each headline box is not placed in a table row. Each line is a paragraph break or some other height controlled break. Entire groups of headlines can therefore be easily placed within a table cell (column) as part of top level page layout.
Formatting headlines and articles using CSS is accomplished with the following selectors. Each selection is the same name for each format code (except the number is different i.e. BlogFmt1, BlogFmt2, etc.). There are two sets of CSS selectors; one for headlines and one for articles.
The system is linked into the e-mail broadcasting system, so with the push of button you can send a blog article in an e-mail blast to all customers who have signed up (think e-mailed newsletter). In an e-mailed blog article, up to three type 10 ads will be included at the end of all broadcasts.
Basic Article navigation is accomplished with bart codes. The same ASP page which displays the headlines MUST ALSO display the full articles. This dual purpose is accomplished with URL parameters to select an operating mode for the ASP page.
To display a full article a URL parameter is added to the URL the current page. This parameter is called bart code. The bart code is it indexkey for the article to display. These URL links and parameters are automatically generated by the headling listing functions.
Public Posting is enabled by setting "allowBlogPosts = true" and "blogEditPage = "file.asp" must equal the page which performs editing; both these params are set in the pageconfig.inc.asp E-Business framework config file. You must also set up a "post label" in the CSCReadMoreLink db column if you want a label other than "post new blog." If the CSCReadMoreLink contains two strings delimited by an "=" then the first string will be the read more of this article link and the second string will be the post a new blog string.
If this functionality is enabled an "Post New Thread" link will be displayed next to each "Read More" link on the headline page. Clicking this link will open a new article in the editor.
Editing blogs after posting is easy. If this functionality is enabled an "Edit" link will be displayed below the article if you are logged in as the author. Clicking this link will open the article in the editor.
To enable editing, make sure the editAllowed parameter is set TRUE in the advancedBlogArticle() function.
SendSafe comes with tools to display blogs:
BlogToolKit Object setup:
blogDisplayPage = "store.blog.asp" Set to the page which displays blogs blogEditPage = "store.blogedit.asp" Set to the page which allows editing OR null blogDetailedAuditingEnabled = true Set true/false for detailed auditing blogPicHeight = 200 Set default pic height blogPicWidth = 300 Set default pic width headlinesPerPage = 10 Default number headlines per pages blogSummarySize = 1 Sets detault summary size in paragraphs BlogEditMsg = "" Additional message displayed by submit button blogContentTypeCode = 0 The ContextType code (blogId) OnlySuperCanPost = false Only a super user can post ModeratorEMail = "" Email Address to send posting and other alerts CSCheadlineFormatCode = 1 Format code for headlines. CSCArticleFormatCode = 4 Format code for articles.
DATABASE BLOG REPAIR TOOL
This job periodically scans blogs and corrects the errors. The repairs performed are:
| Parameter | value |
| param1 | This should be the same parameter used for param1 in a Replication job stripped of the user specified upload directory i.e. \en\uploads would be entered (from a replication job with \en\uploads\157117208). |
| param2 | This should be the same parameter used for param2 in a Replication job. |
| param3 | starting index key (optional) |