5 <div class="modal fade" id="upload_crosses_dialog" name="upload_crosses_dialog" tabindex="-1" role="dialog" aria-labelledby="uploadCrossesDialog">
6 <div class="modal-dialog modal-xl" role="document">
7 <div class="modal-content">
8 <div class="modal-header">
9 <button type="button" class="close" data-dismiss="modal" aria-label="Close"><span aria-hidden="true">×</span></button>
10 <h4 class="modal-title" id="uploadCrossesDialog">Upload Crosses</h4>
12 <div class="modal-body">
13 <div class="container-fluid">
15 <&| /util/workflow.mas, id=> "crosses_upload_workflow" &>
16 <&| /util/workflow.mas:step, title=> "Intro" &>
17 <& /page/page_title.mas, title=>"What are crosses?" &>
19 <li>Crosses represent any pollination that occurs.</li>
20 <li>Crosses can be of different types (biparental, self, open, sib, polycross, bulk, bulk_self, bulk_open, or doubled_haploid)</li>
21 <li>Depending on the cross type, an individual cross can be defined as between two accessions (e.g. accession A is the female and accession B is the male in a biparental cross)</li>
22 <li>For an open pollinated cross, the cross can be defined as between female accession A and male population P1 (populations in the database are only defined as groups of accessions), or between female accession A and unknown male parents</li>
23 <li>An individual cross can be linked to the specific female plot or plant, as well as the specific male plot or plant.</li>
24 <li>A cross can have a number of properties associated to it, such as number of flowers, pollination date, etc.</li>
25 <li>A cross can produce seed, which goes into a seedlot.</li>
26 <li>A cross can ultimately produce progeny, which then become named accessions in the database.</li>
31 <button class="btn btn-primary" onclick="Workflow.complete(this);">Go to Next Step</button>
35 <&| /util/workflow.mas:step, title=> "Crossing experiment" &>
36 <& /page/page_title.mas, title=>"Select a crossing experiment for your crosses" &>
38 <p>Crossing experiments are for grouping crosses together. The grouping is most often done for crosses derived from the same field trial, the same year, or for crosses that have the same breeding objective.</p>
41 <div class="form-group">
42 <label class="col-sm-2 control-label">You can check your crossing experiment here: </label>
43 <div class="col-sm-10">
44 <div id="upload_crosses_select_crossingtrial_1" name="upload_crosses_select_crossingtrial_1" >
51 <button class="btn btn-info" name="create_crossingtrial_link">If you need to create a new crossing experiment, click here</button><br/><br/>
52 <button class="btn btn-primary" onclick="Workflow.complete(this);">If you already have a crossing experiment, go to Next Step</button>
56 <&| /util/workflow.mas:step, title=> "Upload your crosses" &>
57 <& /page/page_title.mas, title=>"Enter basic information about the crosses and upload your file" &>
60 <form class="form-horizontal" role="form" method="post" enctype="multipart/form-data" encoding="multipart/form-data" id="upload_crosses_form" name="upload_crosses_form">
61 <div class="form-group">
62 <label class="col-sm-3 control-label">Select a Crossing Experiment: </label>
63 <div class="col-sm-9">
64 <div id="upload_crosses_select_crossingtrial_2" name="upload_crosses_select_crossingtrial_2" >
69 <div class="form-group">
70 <label class="col-sm-2 control-label">Location of Crosses: </label>
71 <div class="col-sm-10">
72 <select class="form-control" id="cross_upload_location" name="cross_upload_location">
73 <option value="">Select Location</option>
75 # foreach my $location (@locations) {
76 # print "<option value=".'"'.@$location[1].'"'.">".@$location[1]."</option>";
78 foreach my $location_hashref (@$locations) {
79 my $properties = exists($location_hashref->{'properties'}) ? $location_hashref->{properties} : "";
80 my $program = $properties->{'Program'};
81 my $name = $properties->{'Name'};
82 print "<option value=\"$name\" data-program=\"$program\">".$name."</option>";
89 <div class="form-group">
90 <label class="col-sm-3 control-label">Select a File Format: </label>
91 <div class="col-sm-9">
92 <select class="form-control" id="cross_file_format_option">
93 <option value="">Select a file format that you want to upload</option>
94 <option value="xls_cross_accession">Excel (.xls) file with only accession/population names for parents</option>
95 <option value="xls_cross_plot">Excel (.xls) file with accession and plot names for parents</option>
96 <option value="xls_cross_plant">Excel (.xls) file with accession and plant names for parents</option>
100 <div id="xls_cross_accession_section" style="display:none">
101 <h3>You want to upload crosses in an Excel file with accession or population names for parents</h3>
102 <div class="well well-sm">
104 <div class="col-sm-4">
105 <&| /page/explanation.mas, title=>'Template information' &>
107 <b>File format information</b>
109 <a id="cross_accession_info_format">Spreadsheet format</a>
113 <div class="col-sm-8">
115 <div class="panel panel-default">
116 <div class="panel-body">
117 <div class="form-group">
118 <label class="col-sm-6 control-label">Select an XLS File: </label>
119 <div class="col-sm-6">
120 <input type="file" name="xls_crosses_simple_file" id="xls_crosses_simple_file" encoding="multipart/form-data" />
129 <div id="xls_cross_plot_section" style="display:none">
130 <h3>You want to upload crosses in an Excel file with accession and plot names for parents</h3>
131 <div class="well well-sm">
133 <div class="col-sm-4">
134 <&| /page/explanation.mas, title=>'Template information' &>
136 <b>File format information</b>
138 <a id="cross_plot_info_format">Spreadsheet format</a>
142 <div class="col-sm-8">
144 <div class="panel panel-default">
145 <div class="panel-body">
146 <div class="form-group">
147 <label class="col-sm-6 control-label">Select an XLS File: </label>
148 <div class="col-sm-6">
149 <input type="file" name="xls_crosses_plots_file" id="xls_crosses_plots_file" encoding="multipart/form-data" />
158 <div id="xls_cross_plant_section" style="display:none">
159 <h3>You want to upload crosses in an Excel file with accession and plant names for parents</h3>
160 <div class="well well-sm">
162 <div class="col-sm-4">
163 <&| /page/explanation.mas, title=>'Template information' &>
165 <b>File format information</b>
167 <a id="cross_plant_info_format">Spreadsheet format</a>
171 <div class="col-sm-8">
173 <div class="panel panel-default">
174 <div class="panel-body">
175 <div class="form-group">
176 <label class="col-sm-6 control-label">Select an XLS File: </label>
177 <div class="col-sm-6">
178 <input type="file" name="xls_crosses_plants_file" id="xls_crosses_plants_file" encoding="multipart/form-data" />
190 <h3>Additional options:</h3>
192 <p>Progeny naming: <i>If generating progeny, use cross name and:</i></p>
193 <div class="form-group">
194 <label class="col-sm-2 control-label">Prefix: </label>
195 <div class="col-sm-10">
196 <input class="form-control" id="upload_prefix" name="upload_prefix" value="P" />
199 <div class="form-group">
200 <label class="col-sm-2 control-label">Suffix: </label>
201 <div class="col-sm-10">
202 <input class="form-control" id="upload_suffix" name="upload_suffix" />
209 <button type="button" onclick="Workflow.complete(this, false);" class="btn btn-primary" name="upload_crosses_submit" id="upload_crosses_submit">Upload File</button>
213 <&| /util/workflow.mas:complete, title=> "Complete" &>
214 <& /page/page_title.mas, title=>"Finished! Your crosses are now in the database" &>
216 <span class="ui-icon ui-icon-circle-check" style="float: left; margin: 0 7px 50px 0;"></span>
217 The crosses file was uploaded successfully
221 <li>You may want to proceed to the cross detail page(s) for the cross(es) you just created.</li>
222 <li>You can print barcodes for the crosses.</li>
223 <li>You can add crossing information as it becomes available (e.g. number of seeds, progeny, etc).</li>
227 <button class="btn btn-primary" name="upload_crosses_success_complete_button">The crosses were saved to the database with no errors! Congrats Click Here</button><br/><br/>
231 </&><!-- End of workflow -->
235 <div class="modal-footer">
236 <button type="button" class="btn btn-default" data-dismiss="modal">Close</button>
242 <div class="modal fade" id="upload_cross_error_display" name="upload_cross_error_display" tabindex="-1" role="dialog" aria-labelledby="uploadCrossesErrorDialog">
243 <div class="modal-dialog modal-lg" role="document">
244 <div class="modal-content">
245 <div class="modal-header">
246 <button type="button" class="close" data-dismiss="modal" aria-label="Close"><span aria-hidden="true">×</span></button>
247 <h4 class="modal-title" id="uploadCrossesErrorDialog">Upload Crosses File Error</h4>
249 <div class="modal-body">
250 <div class="container-fluid">
256 <div class="modal-footer">
257 <button type="button" class="btn btn-default" data-dismiss="modal">Close</button>
263 % my $cross_properties = $c->config->{cross_properties};
264 % my @column_header = split ',',$cross_properties;
266 <div class="modal fade" id="cross_accession_info_dialog" name="cross_accession_info_dialog" tabindex="-1" role="dialog" aria-labelledby="crossAccessionInfoDialog">
267 <div class="modal-dialog modal-xl" role="document">
268 <div class="modal-content">
269 <div class="modal-header">
270 <button type="button" class="close" data-dismiss="modal" aria-label="Close"><span aria-hidden="true">×</span></button>
271 <h4 class="modal-title" id="crossAccessionInfoDialog">Template Information</h4>
273 <div class="modal-body">
274 <div class="container-fluid">
276 <b>Crosses may be uploaded in an Excel file (.xls)</b>
278 (.xlsx format not supported)
283 To set up crosses in the database, please provide required information. The first row (header) must contain the following:
286 <table class="table table-bordered table-hover">
289 <td>cross_unique_id</td>
290 <td>cross_combination</td>
292 <td>female_parent</td>
295 % foreach my $column_header(@column_header){
296 <td><% $column_header %></td>
306 <b>Required columns:</b>
308 <li><b>cross_unique_id</b> (must NOT exist in the database)</li>
309 <li><b>cross_combination</b> (required in the header, but value for cross combination (e.g. female accession/male accession) may be left blank)</li>
310 <li><b>cross_type</b> (must be one of the following: biparental, self, open, sib, polycross, bulk, bulk_self, bulk_open, or doubled_haploid)
312 <li><b>cross type descriptions:</b></li>
314 <li><b>biparental:</b> An individual plant pollinated by another individual plant.</li>
315 <li><b>self:</b> A self pollinated individual plant.</li>
316 <li><b>open:</b> An individual plant pollinated by a group of plants or open pollinated (pollen may be from a group with known or unknown members).</li>
317 <li><b>sib:</b> Mating between individuals that have at least one parent in common. Generally between two individuals within the same plot.</li>
318 <li><b>polycross:</b> Mating between individual female parent from a population and the corresponding male population.</li>
319 <li><b>bulk:</b> A group of plants (usually a related family) pollinated by an individual plant.</li>
320 <li><b>bulk_self:</b> A group of plants (usually a related family) that are self pollinated (each individual selfed, not combined pollen).</li>
321 <li><b>bulk_open:</b> A group of plants (usually a related family) that are pollinated by another group of plants or open pollinated (pollen may be from a group with known or unknown members).</li>
322 <li><b>doubled_haploid:</b> Plants derived from doubling the chromosome number of haploid tissue.</li>
326 <li><b>female_parent</b> (accession names or population names must exist as <b>uniquenames</b> in the database)</li>
327 <li><b>male_parent</b> (required in the header, but value may be left blank for most cross types. Must be specified for biparental, sib, polycross and bulk cross types. When specified, accession names or population names must exist as <b>uniquenames</b> in the database)</li>
331 <b>Optional columns (dates must be in the format YYYY/MM/DD):</b>
333 % foreach my $column_header(@column_header){
334 <li><% $column_header %></li>
339 <b>Additional cross information:</b>
341 <li>After you establish cross unique ids in the database, you can add additional cross info (e.g. pollination date, total number of flowers pollinated, total number of fruits set) or progenies to the corresponding cross unique ids.</li>
342 <li>Cross info and progenies can be uploaded via links in crossing experiment detail page or can be added directly in each cross detail page.</li>
346 <div class="modal-footer">
347 <button type="button" class="btn btn-default" data-dismiss="modal">Close</button>
352 <div class="modal fade" id="cross_plot_info_dialog" name="cross_plot_info_dialog" tabindex="-1" role="dialog" aria-labelledby="crossPlotInfoDialog">
353 <div class="modal-dialog modal-xl" role="document">
354 <div class="modal-content">
355 <div class="modal-header">
356 <button type="button" class="close" data-dismiss="modal" aria-label="Close"><span aria-hidden="true">×</span></button>
357 <h4 class="modal-title" id="crossPlotInfoDialog">Template Information</h4>
359 <div class="modal-body">
360 <div class="container-fluid">
362 <b>Crosses may be uploaded in an Excel file (.xls)</b>
364 (.xlsx format not supported)
369 To set up crosses in the database, please provide required information. The first row (header) must contain the following:
372 <table class="table table-bordered table-hover">
375 <td>cross_unique_id</td>
376 <td>cross_combination</td>
378 <td>female_parent</td>
383 % foreach my $column_header(@column_header){
384 <td><% $column_header %></td>
394 <b>Required columns:</b>
396 <li><b>cross_unique_id</b> (must NOT exist in the database)</li>
397 <li><b>cross_combination</b> (required in the header, but value for cross combination (e.g. female accession/male accession) may be left blank)</li>
398 <li><b>cross_type</b> (must be one of the following: biparental, self, open, sib, polycross, bulk, bulk_self, bulk_open, or doubled_haploid)
400 <li><b>cross type descriptions:</b></li>
402 <li><b>biparental:</b> An individual plant pollinated by another individual plant.</li>
403 <li><b>self:</b> A self pollinated individual plant.</li>
404 <li><b>open:</b> An individual plant pollinated by a group of plants or open pollinated (pollen may be from a group with known or unknown members).</li>
405 <li><b>sib:</b> Mating between individuals that have at least one parent in common. Generally between two individuals within the same plot.</li>
406 <li><b>polycross:</b> Mating between individual female parent from a population and the corresponding male population.</li>
407 <li><b>bulk:</b> A group of plants (usually a related family) pollinated by an individual plant.</li>
408 <li><b>bulk_self:</b> A group of plants (usually a related family) that are self pollinated (each individual selfed, not combined pollen).</li>
409 <li><b>bulk_open:</b> A group of plants (usually a related family) that are pollinated by another group of plants or open pollinated (pollen may be from a group with known or unknown members).</li>
410 <li><b>doubled_haploid:</b> Plants derived from doubling the chromosome number of haploid tissue.</li>
414 <li><b>female_parent</b> (accession names must exist as <b>uniquenames</b> in the database)</li>
415 <li><b>male_parent</b> (required in the header, but value may be left blank for most cross types. Must be specified for biparental, sib, polycross and bulk cross types. When specified, accession or population names must exist as <b>uniquenames</b> in the database)</li>
416 <li><b>female_plot</b> (Plot names must exist in the database)</li>
417 <li><b>male_plot</b> (Plot names must exist in the database)</li>
420 <b>Optional columns (dates must be in the format YYYY/MM/DD):</b>
422 % foreach my $column_header(@column_header){
423 <li><% $column_header %></li>
427 <b>Additional cross information:</b>
429 <li>After you establish cross unique ids in the database, you can add additional cross info (e.g. pollination date, total number of flowers pollinated, total number of fruits set) or progenies to the corresponding cross unique ids.</li>
430 <li>Cross info and progenies can be uploaded via links in crossing experiment detail page or can be added directly in each cross detail page.</li>
434 <div class="modal-footer">
435 <button type="button" class="btn btn-default" data-dismiss="modal">Close</button>
440 <div class="modal fade" id="cross_plant_info_dialog" name="cross_plant_info_dialog" tabindex="-1" role="dialog" aria-labelledby="crossPlantInfoDialog">
441 <div class="modal-dialog modal-xl" role="document">
442 <div class="modal-content">
443 <div class="modal-header">
444 <button type="button" class="close" data-dismiss="modal" aria-label="Close"><span aria-hidden="true">×</span></button>
445 <h4 class="modal-title" id="crossPlantInfoDialog">Template Information</h4>
447 <div class="modal-body">
448 <div class="container-fluid">
450 <b>Crosses may be uploaded in an Excel file (.xls)</b>
452 (.xlsx format not supported)
457 To set up crosses in the database, please provide required information. The first row (header) must contain the following:
460 <table class="table table-bordered table-hover">
463 <td>cross_unique_id</td>
464 <td>cross_combination</td>
466 <td>female_parent</td>
468 <td>female_plant</td>
471 % foreach my $column_header(@column_header){
472 <td><% $column_header %></td>
482 <b>Required columns:</b>
484 <li><b>cross_unique_id</b> (must NOT exist in the database)</li>
485 <li><b>cross_combination</b> (required in the header, but value for cross combination (e.g. female accession/male accession) may be left blank)</li>
486 <li><b>cross_type</b> (must be one of the following: biparental, self, open, sib, polycross, bulk, bulk_self, bulk_open, or doubled_haploid)
488 <li><b>cross type descriptions:</b></li>
490 <li><b>biparental:</b> An individual plant pollinated by another individual plant.</li>
491 <li><b>self:</b> A self pollinated individual plant.</li>
492 <li><b>open:</b> An individual plant pollinated by a group of plants or open pollinated (pollen may be from a group with known or unknown members).</li>
493 <li><b>sib:</b> Mating between individuals that have at least one parent in common. Generally between two individuals within the same plot.</li>
494 <li><b>polycross:</b> Mating between individual female parent from a population and the corresponding male population.</li>
495 <li><b>bulk:</b> A group of plants (usually a related family) pollinated by an individual plant.</li>
496 <li><b>bulk_self:</b> A group of plants (usually a related family) that are self pollinated (each individual selfed, not combined pollen).</li>
497 <li><b>bulk_open:</b> A group of plants (usually a related family) that are pollinated by another group of plants or open pollinated (pollen may be from a group with known or unknown members).</li>
498 <li><b>doubled_haploid:</b> Plants derived from doubling the chromosome number of haploid tissue.</li>
502 <li><b>female_parent</b> (accession names must exist as <b>uniquenames</b> in the database)</li>
503 <li><b>male_parent</b> (required in the header, but value may be left blank for most cross types. Must be specified for biparental, sib, polycross and bulk cross types. When specified, accession or population names must exist as <b>uniquenames</b> in the database)</li>
504 <li><b>female_plant</b> (Plant names must exist in the database)</li>
505 <li><b>male_plant</b> (Plant names must exist in the database)</li>
508 <b>Optional columns (dates must be in the format YYYY/MM/DD):</b>
510 % foreach my $column_header(@column_header){
511 <li><% $column_header %></li>
515 <b>Additional cross information:</b>
517 <li>After you establish cross unique ids in the database, you can add additional cross info (e.g. pollination date, total number of flowers pollinated, total number of fruits set) or progenies to the corresponding cross unique ids.</li>
518 <li>Cross info and progenies can be uploaded via links in crossing experiment detail page or can be added directly in each cross detail page.</li>
522 <div class="modal-footer">
523 <button type="button" class="btn btn-default" data-dismiss="modal">Close</button>