2) A hash with the pool id as the key and the pool description as the value
2) A hash with the pool_set id as the key and the description as the value
overgos can be formatted as either contig/position or plate/row/col
cutoff is optional (default = 30bp, can also specify a cutoff of 'none' to return everything)
or
my %input = (dbh => $dbh, overgos => ['1jp1234567']);
or
my %input = (dbh => $dbh, overgos => [@overgos]);
my @valid_overgos = overgo_filter(%input);
2) CGI handle.
3) If to use HTML tables. 0 = no, 1 = yes, 2 = yes & leave table open (often because the calling program wishes to add other information to the table; a two column table is created)
4..8) Five variables on which sections to display. 0 = no display, 1 = display normal, 2 = display with wildcard. It is up to the calling program to handle the wildcard.
The sections are: 4) Contig-position ... a unified field for the user to put this information 5) Contig, position ... two fields for data entry 6) Plate, row, column ... three fields for data entry 7) Pool 8) Pool set
The routine should be enclosed within a form otherwise the user will not be able to choose the drop down menus properly.
The user's selection can be obtained via a cgi_handle->query('xxx') where 'xxx' is:
conpos
contig position
plate row column
pool
poolset
For the 5 sections respectively. It is up to the calling program to handle the wildcards if there are any.
overgo_query_html($dbh,$q,2,0,2,0,1,1);
(B) Not using tables, displaying only the 3rd section without wildcards
overgo_query_html($dbh,$q,0,0,0,1,0,0);