The input of the meta attributes takes place, just like the text inputs, through forms; each object has certain attributes characteristic for this object. The templates have access to the attribute values and so construct for example the navigation. The standard set for the document attributes is as follows:

screenshot_fh_Metaatribute_ZMS_ger.gif

Screenshot: input interface for the meta attributes of a document. Alternatively to the manual input there is a button [acquire] that permits inheritance of the attribute values of the parent object to the actual object.

Attribute configuration for optimal search engine responses

Search engines analyse attribute contents and the text body by different criterions: especially the document title is highly valued in the relevance but also keywords or the document description (in dependence on the type of the search engine) are relatively high valued. Finally the occurrence frequency of particular terms is valued in the text body.
Indexing persons already know "tricks" such as repetitions or white text on white background and in the worst case exclude such websites from the indexing process (so-called "burning"). Therefore the best strategy is to realise a correct and as precise as possible attribution of the documents!
As not all indexing persons master the DC conventions, a double output of the values for "DC.subject" or "keywords" and "DC.description" or "description"i s recommended. In the template model the template "headMeta_Spec" is planned for this special output. Here any attribute values can be capsulated in any HTML constructs at will whereas in "headMeta_DC" the attribute values are published systematically conform to the key.

Example for "headMeta_Spec":

<!--BO medvalue/headMeta_Spec //-->
<META NAME="keywords" content="<dtml-var
"getObjProperty('attr_dc_subject',REQUEST)">">
<META NAME="description" content="<dtml-var
"getObjProperty('attr_dc_description',REQUEST)">">
<!--EO medvalue/headMeta_Spec //-->


As the element of the title is very high valued it is advisable to place keywords also here next to the value of the object title or to insert the content of the DC.subject. This can be realised through a modified headMetas_DC-Template where the attribute call can look as follows:

...
<title>
<dtml-var "getTitle(REQUEST)">: <dtml-var "getObjProperty('attr_dc_subject',REQUEST)">
</title>
...


Alternatively a template headTitle can be introduced with a corresponding code and called for example in the standard_html_header before headMetas_DC.

Optimisation of special documents

To receive significant attributes also in special documents, either corresponding elements are introduced additionally and designated with the same ID values just like the meta attributes or those ID names are used for certain elements. For example an element "attr_dc_subject" of the type "string" can be introduced. When assembling template navigated pages these elements are written into the HTML code for meta attributes just like in standard objects.
IMPORTANT: By default the first two elements of a special document are addressed as short titles (title.alt) or titles (title) and are used correspondingly in the page navigation or in the title assembling.

Erstellt von: Dr. Frank Hoffmann , HOFFMANN+LIEBENBERG , erstellt am:  2008/06/27 , zuletzt geändert: 2008/07/22