Loadcoll.asp process description
Executed from the staging database web page, the script 'loadcoll.asp' distributes sample collecting event information into the appropriate tables of the samples database (see Database design). The action is executed by the button "Load database" at the bottom of the page. At this time, it is restricted to the Sample Coordinator and several members of the Information Applications group.
Information common to all the samples is typed into the form fields at the top of the page (eg., Chief Scientist, Collector, ShipName, ROVName, DiveNumber). Some of this data is used to populate a new record that is created in the database's CollectionGroup table (StartDTG, Chief Scientist, ShipName, and ROVName); some is used in the subsequently created records in the CollectionEvent and Sample tables (ChiefScientist, Collector, DiveName).
Information specific to individual samples is loaded into new records in the CollectionEvent and Sample tables, but only for the samples that are checked on the staging database web page, recognizing that not all samples that were annotated successfully made it to the surface and therefore won't be tracked further. Most of the information for a particular sample is inserted as a record in the CollectionEvent table (eg., Date/Time, FrameGrabImageURL, Equipment, CollectionVIMSConcept, CollectionRefName, DiveName). A record is also created in the Sample table (populated with CollectionEventID, SampleRefName, Collector). Database fields that are not populated from this process are left blank or given default values.

The first thing main() does is check if the IP address of the machine running the script is allowed to run it; if it's not then it redirects the user to the deny.html file. The top part of the staging database form is used to create a CollectionGroup record. CheckIfInExpd() first checks that there isn't already an existing record with the same keys.
![]()
»Next: Samples database
Last updated: 12 May, 2000 by
Jenny Paduan
Copyright © 1998 MBARI