to handle contents in GenB a "data template" must first be defined. The definition of a "data template", to make a parallelism with static design of web sites, would be the equivalent to defining the fields in a web form, for example, for collecting user information. In GenB, the "data template" defines the form to be used to enter the contents in each of the records that the lists are built up with, detail views and forms for collecting and storing information from the web site.

the GenB modules that structure contents based on data templates are:
• News.
• Registries.
• Generics.
• Products.
• Authentication.

each GenB module mentioned above can house an indefinite number of "data templates".

an example of using the "Generics" module:

in the web site inte http://www.inte.es/ the "Generics" module is used to manage page contents:
• company.
• GenB - product.
• GenB - download.
• gallery.
• ...

each of these pages has a different content format, giving rise to use of a different data template each one.

the page "company" (just as "technical sheet") uses a "data template" to handle a single record. This record feeds the "preview template" (the page ..company.php) to "paint" a detail view with the information stored by graphic appearance and arrangement.

the page "download - templates" uses a "data template" to handle a set of records (each record corresponds to a template to be downloaded). These record feed the "preview template " (the page ..descarrega/index.php) to "paint" a detail view with the list of data from those records.

definition of "data templates" is done in the contents management site. To access template management "supervision" privileges are required.



from the center page of the management site, click on the link "Managing ... templates" to access the list of templates

from the list of templates, clicking on the icon next to each data template, drop down the set of fields in the second level that make up each template:

the following operations can be performed from the list of templates:

• add templates: click on the icon located on the first level at the end of the list.
• duplicate templates: to duplicate the definition of a template and the definition of associated fields, click on the icon at the end of the row in the template.
• remove templates: to remove the definition of templates and the definition of associated fields, click on the icon at the end of the row in the template.
• add a field to a template: click on the icon at the end of the list of fields in the data template rolled down.
• duplicate a field of a template: click on the icon at the end of the row of the field.
• remove a field from a template: to remove the definition of a field click on the icon at the end of the row of the field.
  
  NOTE: removing a field or a data template involves the loss of all the data associated with it.
  
  
• modify the parameters of a template: to modify the parameters associated with the template, click on the link of its code identifier (idm):

the parameters associated with the form for editing templates are:

Name: [required] parameter used to give a template a name. The value of this parameter can be previewed as part of the contents of the records associated with the template. When designing "preview templates" (lists or detail views) with the help of GenB Dreamweaver® Extensions, the contents of Name are called up by using the "...Field" object and selecting the option "Template name".
Since the parameter Name can be used as part of contents, the system provides an input for each one of the data languages used.

URL list: [optional] parameter used to indicate the root path (e.g., http://www.inte.es/eng/empresa/listado.php) until you reach the file "preview template" to be used in the lists of records based on this template. The URL list does not have to be filled out if no record lists based on this template are used. The system will provide an input for each of the data languages used.

URL detail: [optional] parameter used to show the root path (e.g., http://www.inte.es/eng/empresa/detalle.php) until you reach the file "preview template" to be used in listing records based on this template. The list URL does not have to be filled out if there are no detail views of records based on this template. The system provides an input for each of the data languages used.

Position parameter for sorting or positioning the template in the lists.

• modify the parameters of the field: to modify the parameters associated with a field, click on the link above the name:

the parameters associated with the field editing form are:

Label: [required] parameter for designating a unique name to a field. The Label value will be the identifier used to reference the contents of fields throughout preview template designing.

Position [required] parameter for sorting or positioning the field in the contents management form.

Field type : [required] parameter used to designate the type of field content. The different types of fields and parameters associated with each of them are shown below.

NOTE: html editor requires Internet Explorer >= 5.5 (Windows only), or Mozilla >= 1.3-Beta on any platform. Any browser based on Gecko will also work, provided that Gecko version is at least the one included in Mozilla-1.3-Beta (for example, Galeon-1.2.8). However, it degrades gracefully to other browsers. They will get a regular textarea field instead of a WYSIWYG editor.

email: [optional] [associated with short_text, open_list fields] parameter for showing the contents of an e-mail field. Data templates that contain fields designated as "email" allow e-mails to be copied into distribution lists from the managment lists.

show in admin lists: [optional] parameter for indicating the presence of the field in the contents management lists.

closed list style: [required] [associated with closed_list fields] parameter that designates the format of the closed list to be used in the contents management forms.

NOTE: when a closed-type field has been inserted, the system provides a "Edit value list" link (next to the drop-down list) for managing the set of closed-list values. It is also possible to access the general list of templates (link next to the name of the closed list-type field).

edit in form [optional] [associated with closed_list fields] parameter for indicating that the closed list can be modified from the contents management forms.

multilingual: [optional] when this option is marked, while editing contents, the system provides an input for each of the languages in which the contents are being managed.

add unpredictable suffix: [optional] [associated with image and document fields] parameter that lets the system automatically assign a 15-characters string at the end of the file name. This option will generate unpredictable file names, being this useful in restricted areas when using private documents ("anti-leech" technique).

template + field to show: [required] [associated with related record fields] parameter that designates the related record template, and the field to show from it.

show in form: date: [optional] [associated with related record fields] parameter for showing, in the drop down menu of related records, the related record date.

show in form: internal reference: [optional] [associated with related record fields] parameter for showing, in the drop down menu of related records, the related internal reference.

show in form: value: [optional] [associated with related record fields] parameter for showing, in the drop down menu of related records, the related record designated value.

Allowed file types: [optional] [associated with image and document fields] all selectd file-types from this list will be allowed during the upload proces.

Max file size: [optional] [associated with image and document fields] max size allowed in Kilobytes.

Max image dimensions: [optional] [associated with image fields] max widh and height in pixel units.

Reduce (Reducir): [optional] [associated with image fields] Option that lets you automate the dimensions and size reduction during upload process, when dimensions or size limits are exceeded.

Output type: [optional] [associated with image fields] file type used when the image is reduced. File types that support this option are: bmp, gif, jpg y png.

Thumbnail copy: [optional] [associated with image fields] parameter to turn on the Thumbnail generator. File types that support this option are: bmp, gif, jpg y png.