Information collection
The information collection feature makes it possible to gather user input when a node referencing an information collector object is viewed. It is typically useful when it comes to the creation of feedback forms, polls, etc.
An object can collect information if at least one of the class attributes is marked as an information collector. When the object is viewed, each collector attribute will be displayed using the chosen datatype's data collector template. Instead of just outputting the attributes' contents, the collector templates provide interfaces for data input. The generated input interface depends on the datatype that represents the attribute. The following table reveals the datatypes that are capable of collecting information.
Datatype | Input interface | Input validation |
---|---|---|
Check-box. |
No. |
|
Single line of text. |
Yes. |
|
Radio buttons or a drop-down menu. |
No. |
|
Multiple lines of unformatted text. |
No. |
|
Single line of unformatted text. |
No. |
The input interfaces must be encapsulated by an HTML form that posts the data using a submit button named "ActionCollectInformation" to "/content/action" (the "action" view of the "content" module). The submitted data will be stored in a dedicated part of the database, separated from but related to the object itself. In addition, whenever the object collects any data, the information can be sent to a specified E-mail address. The "Collected information" section within the "Setup" part of the administration interface can be used to view and delete information that was collected through content objects.
Balazs Halasy (14/09/2010 10:53 am)
Geir Arne Waaler (03/10/2010 2:18 pm)
Comments
Two more hidden inputs also required.
Tuesday 27 September 2005 1:53:18 am
James Robertson
<input type="hidden" name="ContentObjectID" value="{$node.object.id}" />
<input type="hidden" name="ContentNodeID" value="{$node.node_id}" />
[Why oh why isn't this documented!? It simply does not work without it :-[