Sf assemblage - Revision history

Andydufton: /* Additional Fields */

2008-11-14T10:49:51Z

‎Additional Fields

Andydufton at 10:49, 14 November 2008

2008-11-14T10:49:39Z

Andydufton at 10:49, 14 November 2008

2008-11-14T10:49:21Z

Andydufton: /* the sf_conf */

2008-11-14T10:46:50Z

‎the sf_conf

192.168.0.1 at 09:09, 31 August 2007

2007-08-31T09:09:49Z

81.134.11.8: /* the fields */

2007-08-24T09:49:17Z

‎the fields

81.134.11.8 at 09:48, 24 August 2007

2007-08-24T09:48:58Z

81.134.11.8: /* Set-Up */

2007-08-24T09:48:28Z

‎Set-Up

81.134.11.8 at 09:39, 24 August 2007

2007-08-24T09:39:21Z

81.134.11.8 at 09:37, 24 August 2007

2007-08-24T09:37:49Z

New page

These are some notes describing the sf_assemblage.

===Description===

sf_assemblage can be used for displaying and editing attributes that have numbers chained to them. As an example, this could be used for recording the numbers of a certain type of seed in a sample, or for attaching total numbers of findtypes.

===Usage===

This form should normally be used in conjunction with [[sf_attr_bytype]]. The attribute gets added to the item and then sf_assemblage will offer you the chance to add one or more numbers to that attribute.

===Set-Up===

@@ Line 8: / Line 8: @@
 *'''op_assemblage_type''' - this is the type of attribute (in cor_lut_attribute) that the fields will be chained to.
 *'''op_chart''' - sets whether the assemblage information will be displayed in pie-chart form on micro view, set as TRUE/FALSE
 ===Example Configuration===

@@ Line 10: / Line 10: @@
-====Example Configuration====
+===Example Configuration===
 <pre>
 $conf_mcd_botanic =

@@ Line 1: / Line 1: @@
 ===Description===
-sf_assemblage can be used for displaying and editing attributes that have numbers chained to them. As an example, this could be used for recording the numbers of a certain type of seed in a sample, or for attaching total numbers of findtypes.
+sf_assemblage can be used for displaying and editing attributes that have numbers chained to them. As an example, this could be used for recording the numbers of a certain type of seed in a sample, or for attaching total numbers of findtypes.  This form should normally be used in conjunction with [[sf_attr_bytype]]. The attribute gets added to the item and then sf_assemblage will offer you the chance to add one or more numbers to that attribute.
-sf_assemblage needs a number of different 'op' variables set in the sf_conf and also it will need some custom validation set up (to allow for the chains).
+===Additional Fields===
-===Examples===
+The sf_assemblage needs a number of different 'op' variables set in the sf_conf:
 ====Example Configuration====
@@ Line 37: / Line 30: @@
 </pre>
 [[category: Administrator]]

@@ Line 17: / Line 17: @@
 In this example, sf_assemblage is being used to chain coordinates to a projection system that is attached to the item.
-====the sf_conf====
+====Example Configuration====
+<pre>
-  $conf_mcd_coords =
+$conf_mcd_botanic =
      array(
          'view_state' => 'max',
          'edit_state' => 'view',
          'sf_nav_type' => 'full',
          'script' => 'php/subforms/sf_assemblage.php',
-        'op_assemblage_type' => 'projection',
+         'op_label' => 'space',
          'op_input' => 'save',
          'fields' => array(
-            $conf_field_easting,
+             $conf_field_total
+         )
-  );
+);
+</pre>
 *'op_assemblage_type' - this is the type of attribute (in cor_lut_attribute) that the fields will be chained to.

← Older revision		Revision as of 09:09, 31 August 2007
Line 91:		Line 91:
	$conf_field_northing['add_validation'][] = $vd_chainkey;		$conf_field_northing['add_validation'][] = $vd_chainkey;
	$conf_field_northing['add_validation'][] = $vd_chainval;		$conf_field_northing['add_validation'][] = $vd_chainval;
		+
		+	[[category: Administrator]]

@@ Line 45: / Line 45: @@
    //set up some custom validation for the coordinate chains
   $vd_chainkey =
      array(
@@ Line 61: / Line 60: @@
        'var_locn' => 'request',
   );
   $conf_field_easting =
      array(

@@ Line 12: / Line 12: @@
 sf_assemblage needs a number of different 'op' variables set in the sf_conf and also it will need some custom validation set up (to allow for the chains).
    $conf_mcd_coords =
@@ Line 19: / Line 25: @@
          'sf_nav_type' => 'full',
          'sf_title' => 'coordinates', //appears in the titlebar of the subform (mk nname)
-        'sf_html_id' => 'fst_cd_coordinates', //the form id tag (must be unique)
+         'sf_html_id' => 'fst_cd_coordinates', //the form id tag (must be unique)
          'script' => 'php/subforms/sf_assemblage.php',
          'op_assemblage_type' => 'projection',
@@ Line 29: / Line 35: @@
+         )
    );

← Older revision		Revision as of 09:39, 24 August 2007
Line 10:		Line 10:

	===Set-Up===		===Set-Up===
		+
		+	sf_assemblage needs a number of different 'op' variables set in the sf_conf and also it will need some custom validation set up (to allow for the chains).
		+
		+	$conf_mcd_coords =
		+	array(
		+	'view_state' => 'max',
		+	'edit_state' => 'view',
		+	'sf_nav_type' => 'full',
		+	'sf_title' => 'coordinates', //appears in the titlebar of the subform (mk nname)
		+	'sf_html_id' => 'fst_cd_coordinates', //the form id tag (must be unique)
		+	'script' => 'php/subforms/sf_assemblage.php',
		+	'op_assemblage_type' => 'projection',
		+	'op_label' => 'save',
		+	'op_input' => 'save',
		+	'fields' => array(
		+	$conf_field_easting,
		+	$conf_field_northing
		+	)
		+	);