Collecting Information
This page deals with both the embedded subform (part of the main CO form) and the full table. Entering data into the CI subform ties it automatically to the CO you are working with. Entering data into the independent table does not. Using the data table is handy for 'priming the pump' and populating complex info into the database. This way, complex locality, Geography and Collecting Event info can be distilled into a Field Number and given to a database trainee as part of a general data entry task.
The Collecting Information line on the Collection Object form takes information from many different tables and strings it together into a single line. Collecting information, Locality, Geography and the plug-in Geolocate all contribute to the information shown in the field.
Review the primer on relational databases to see how all these sub-forms relate to other tables and 'tie in' to the Collection Object form.
Subform View:
Form View:
Whichever way you get here, the form is the same and has the same rules. This form has 3 sub-forms nested inside it.
When accessed through the CO form it's a subform with 3 subforms nested into it. Xzibit would be so proud.
The top part of the locality form is a combination of the Locality subform, and some generalized information. These are separated because there are cases where a locality name will be the same, the other information will be different. Instead of creating a new locality each time a collector heads out to that site, or uses a different collecting method, we just tie the unchanging Locality to the more flexible Collecting Information form. We'll dissect the form the order they appear in the above version of the form.