1 | <?xml version="1.0" encoding="UTF-8"?> |
---|
2 | <!DOCTYPE chapter PUBLIC |
---|
3 | "-//Dawid Weiss//DTD DocBook V3.1-Based Extension for XML and graphics inclusion//EN" |
---|
4 | "../../../../lib/docbook/preprocess/dweiss-docbook-extensions.dtd"> |
---|
5 | <!-- |
---|
6 | $Id: array_lims.xml 3420 2007-05-31 09:55:37Z martin $ |
---|
7 | |
---|
8 | Copyright (C) Authors contributing to this file. |
---|
9 | |
---|
10 | This file is part of BASE - BioArray Software Environment. |
---|
11 | Available at http://base.thep.lu.se/ |
---|
12 | |
---|
13 | BASE is free software; you can redistribute it and/or |
---|
14 | modify it under the terms of the GNU General Public License |
---|
15 | as published by the Free Software Foundation; either version 2 |
---|
16 | of the License, or (at your option) any later version. |
---|
17 | |
---|
18 | BASE is distributed in the hope that it will be useful, |
---|
19 | but WITHOUT ANY WARRANTY; without even the implied warranty of |
---|
20 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the |
---|
21 | GNU General Public License for more details. |
---|
22 | |
---|
23 | You should have received a copy of the GNU General Public License |
---|
24 | along with this program; if not, write to the Free Software |
---|
25 | Foundation, Inc., 59 Temple Place - Suite 330, |
---|
26 | Boston, MA 02111-1307, USA. |
---|
27 | --> |
---|
28 | |
---|
29 | <chapter id="array_lims"> |
---|
30 | <?dbhtml dir="array_lims"?> |
---|
31 | <title>Array LIMS</title> |
---|
32 | <sect1 id="array_lims.introduction"> |
---|
33 | <title>Introduction</title> |
---|
34 | <para> |
---|
35 | Arrays are at the core of the BASE2 business and are essential elements to describe in |
---|
36 | order to be MIAME compliant. It is also critical to track and manage information about |
---|
37 | microarray design as accurately as possible since mistakes could prove extremely costly |
---|
38 | in downstream analysis. |
---|
39 | </para> |
---|
40 | <para> |
---|
41 | Finally, as a good practice, all array related information should be entered into BASE2 |
---|
42 | system prior to start describing the sample processing and hybridizations events making |
---|
43 | up a microarray experiment. |
---|
44 | </para> |
---|
45 | |
---|
46 | <para> |
---|
47 | BASE2 has been engineered to support microarray printing facilities. The system |
---|
48 | therefore offers objects to describe plates, their geometries and the events (merging, |
---|
49 | printing) affected them. The first section of the chapter deals with this functionality. |
---|
50 | as well as plate management. |
---|
51 | </para> |
---|
52 | |
---|
53 | <para> |
---|
54 | For users buying their arrays from commercial sources, the plate management component |
---|
55 | can be ignored and they can go immediately to |
---|
56 | <xref linkend="array_lims.arraydesign" /> |
---|
57 | . |
---|
58 | </para> |
---|
59 | |
---|
60 | </sect1> |
---|
61 | |
---|
62 | <sect1 id="array_lims.platemanagement"> |
---|
63 | <title>Plates</title> |
---|
64 | <para>TODO</para> |
---|
65 | </sect1> |
---|
66 | |
---|
67 | <sect1 id="array_lims.arraydesign"> |
---|
68 | <title>Array designs</title> |
---|
69 | <para> |
---|
70 | Array design should be understood as a plan which can be realized during a printing |
---|
71 | process producing microarray slides. During the course of the printing process, reagents |
---|
72 | may run out leading to the interruption of this process. All slides created during this |
---|
73 | printing process belong to the same printing batch. It is the array slide that will |
---|
74 | eventually be used in a hybridization event. BASE2 allows user to track those 3 entities |
---|
75 | with great details. This is an important functionality for users producing their own |
---|
76 | arrays and for those caring for quality control and tracking of microarray slides in a |
---|
77 | printing facility. The following sections detail how to use BASE2 to help in these |
---|
78 | tasks. |
---|
79 | </para> |
---|
80 | <tip> |
---|
81 | <para> |
---|
82 | It's highly recommended to have read |
---|
83 | <xref linkend="webclient.items" /> |
---|
84 | before continuing with this chapter. |
---|
85 | </para> |
---|
86 | </tip> |
---|
87 | <para> |
---|
88 | Use |
---|
89 | <menuchoice> |
---|
90 | <guimenu>Array LIMS</guimenu> |
---|
91 | <guimenuitem>Array designs</guimenuitem> |
---|
92 | </menuchoice> |
---|
93 | to get to the list page with array designs. |
---|
94 | </para> |
---|
95 | <sect2 id="array_lims.arraydesign.properties"> |
---|
96 | <title>Properties</title> |
---|
97 | <sect3 id="array_lims.arraydesign.properties.arraydesign"> |
---|
98 | <title>Array design</title> |
---|
99 | <variablelist> |
---|
100 | <varlistentry> |
---|
101 | <term> |
---|
102 | <guilabel>Name</guilabel> |
---|
103 | </term> |
---|
104 | <listitem> |
---|
105 | <para>Provide an unique sensible name for the design (required).</para> |
---|
106 | </listitem> |
---|
107 | </varlistentry> |
---|
108 | <varlistentry> |
---|
109 | <term> |
---|
110 | <guilabel>Affy chip</guilabel> |
---|
111 | </term> |
---|
112 | <listitem> |
---|
113 | <para> |
---|
114 | This is a checkbox for providing a boolean entry, essentially |
---|
115 | telling the system whether the array design being created is of |
---|
116 | affymetrix technology or not. |
---|
117 | </para> |
---|
118 | <warning> |
---|
119 | <para> |
---|
120 | As indicated on the interface, once saved, this information |
---|
121 | cannot be modified, so if a mistake is made, the entry will have |
---|
122 | to be deleted. |
---|
123 | </para> |
---|
124 | </warning> |
---|
125 | </listitem> |
---|
126 | </varlistentry> |
---|
127 | <varlistentry> |
---|
128 | <term> |
---|
129 | <guilabel>CDF file</guilabel> |
---|
130 | </term> |
---|
131 | <listitem> |
---|
132 | <para> |
---|
133 | This field allows to upload an affymetrix CDF file. A CDF file is a |
---|
134 | binary file describing affymetrix chip layout. This file is |
---|
135 | necessary for performing analysis using some BASE2 plugins (e.g |
---|
136 | RMAExpress plugin). |
---|
137 | </para> |
---|
138 | <note> |
---|
139 | <para> |
---|
140 | Affymetrix users, you can also upload CLF or BPMAP files defined |
---|
141 | for exon and tiling arrays respectively. |
---|
142 | </para> |
---|
143 | </note> |
---|
144 | </listitem> |
---|
145 | </varlistentry> |
---|
146 | <varlistentry> |
---|
147 | <term> |
---|
148 | <guilabel>Description</guilabel> |
---|
149 | </term> |
---|
150 | <listitem> |
---|
151 | <para> |
---|
152 | Provide other useful information about the array design in this text |
---|
153 | area. |
---|
154 | </para> |
---|
155 | </listitem> |
---|
156 | </varlistentry> |
---|
157 | </variablelist> |
---|
158 | <para> |
---|
159 | Click on the &gbSave; button to store the information in BASE2 or on the |
---|
160 | &gbCancel; button to abort. |
---|
161 | </para> |
---|
162 | <para> |
---|
163 | Upon saving, the array design list view page is displayed. Users should pay |
---|
164 | attention to the column |
---|
165 | <guilabel>Has features</guilabel> |
---|
166 | . Unless an affymetrix array design was created, the value will be by default |
---|
167 | set to |
---|
168 | <guilabel>no</guilabel> |
---|
169 | . For all other cases, this value will only be updated following |
---|
170 | <guilabel>Importing the features</guilabel> |
---|
171 | , a process which is detailed in |
---|
172 | <xref linkend="array_lims.arraydesign.properties.importfeature" /> |
---|
173 | . |
---|
174 | </para> |
---|
175 | </sect3> |
---|
176 | |
---|
177 | <sect3 id="array_lims.arraydesign.properties.annotations"> |
---|
178 | <title>Annotations and inherited annotations</title> |
---|
179 | <para> |
---|
180 | This allows you to input values associated to annotation types devised to refine |
---|
181 | array design description. Read more about annotations in |
---|
182 | <xref linkend="annotations" /> |
---|
183 | . |
---|
184 | </para> |
---|
185 | </sect3> |
---|
186 | |
---|
187 | |
---|
188 | <sect3 id="array_lims.arraydesign.properties.importfeature"> |
---|
189 | <title>Importing features to an array design</title> |
---|
190 | |
---|
191 | <para> |
---|
192 | For non-affymetrix arraydesigns, importing features is an important step in |
---|
193 | order to fully define an array design. It should be noted that BASE2 does not |
---|
194 | enforce the immediate feature import upon creation of array design. However, It |
---|
195 | is STRONGLY advised to do so when creating an array design. Doing so enables to |
---|
196 | use the array design for downstream analysis with no further trouble. It also |
---|
197 | matters when importing raw bioassay data and matching those to the corresponding |
---|
198 | array design. |
---|
199 | </para> |
---|
200 | |
---|
201 | <para> |
---|
202 | This section applies only to non-affymetrix array design since affymetrix |
---|
203 | designs are handled differently. For affymetrix platform, features are |
---|
204 | considered imported when the affymetrix CDF file is actually uploaded. |
---|
205 | </para> |
---|
206 | <para> |
---|
207 | From the array design item view, click on the &gbImport; button and use the |
---|
208 | reporter map importer and an appropriate plugin configuration when following the |
---|
209 | instructions in |
---|
210 | <xref linkend="import_export_data.import" /> |
---|
211 | . |
---|
212 | </para> |
---|
213 | <note> |
---|
214 | <para> |
---|
215 | The button only shows up if the logged in user has enough permissions. |
---|
216 | </para> |
---|
217 | </note> |
---|
218 | <para> |
---|
219 | If the import run is successful, go to the array design list view. The |
---|
220 | <guilabel>Has features</guilabel> |
---|
221 | column will show |
---|
222 | <guilabel>Yes (n)</guilabel> |
---|
223 | where n is the number of features actually present on the microarray and now |
---|
224 | associated to the newly created ArrayDesign. |
---|
225 | </para> |
---|
226 | </sect3> |
---|
227 | </sect2> |
---|
228 | </sect1> |
---|
229 | |
---|
230 | |
---|
231 | <sect1 id="array_lims.arraybatch"> |
---|
232 | <title>Array batches</title> |
---|
233 | |
---|
234 | <sect2 id="array_lims.arraybatch.create"> |
---|
235 | <title>Creating array batches</title> |
---|
236 | <para> |
---|
237 | Beside the common way of creating items in BASE, an array batch can also be created |
---|
238 | directly from an array design, both in list view and single item view. |
---|
239 | </para> |
---|
240 | <variablelist> |
---|
241 | <varlistentry> |
---|
242 | <term>In list view of array design</term> |
---|
243 | <listitem> |
---|
244 | <para> |
---|
245 | Click on the |
---|
246 | <inlinemediaobject> |
---|
247 | <imageobject> |
---|
248 | <imagedata fileref="figures/add.png" format="PNG" /> |
---|
249 | </imageobject> |
---|
250 | </inlinemediaobject> |
---|
251 | icon available from the |
---|
252 | <guilabel>Batches</guilabel> |
---|
253 | column of the array design you want to use. |
---|
254 | <tip> |
---|
255 | <para> |
---|
256 | As default in BASE the |
---|
257 | <guilabel>Batches</guilabel> |
---|
258 | column is hidden and need therefore be made visible first, see |
---|
259 | <xref linkend="webclient.itemlist.columns" /> |
---|
260 | </para> |
---|
261 | </tip> |
---|
262 | </para> |
---|
263 | </listitem> |
---|
264 | </varlistentry> |
---|
265 | </variablelist> |
---|
266 | <para> |
---|
267 | <guibutton>New batch…</guibutton> |
---|
268 | is the corresponding button in single item view. The current array design will |
---|
269 | automatically be filled in the array design property for the new batch. |
---|
270 | </para> |
---|
271 | </sect2> |
---|
272 | <sect2 id="array_lims.arraybatch.properties"> |
---|
273 | <title>Properties</title> |
---|
274 | <variablelist> |
---|
275 | <varlistentry> |
---|
276 | <term> |
---|
277 | <guilabel>Name</guilabel> |
---|
278 | </term> |
---|
279 | <listitem> |
---|
280 | <para>The name of the array batch (required).</para> |
---|
281 | </listitem> |
---|
282 | </varlistentry> |
---|
283 | <varlistentry> |
---|
284 | <term> |
---|
285 | <guilabel>Array design</guilabel> |
---|
286 | </term> |
---|
287 | <listitem> |
---|
288 | <para>Array design that is used for the batch.</para> |
---|
289 | </listitem> |
---|
290 | </varlistentry> |
---|
291 | <varlistentry> |
---|
292 | <term> |
---|
293 | <guilabel>Print robot</guilabel> |
---|
294 | </term> |
---|
295 | <listitem> |
---|
296 | <para>The print robot that is used.</para> |
---|
297 | </listitem> |
---|
298 | </varlistentry> |
---|
299 | <varlistentry> |
---|
300 | <term> |
---|
301 | <guilabel>Protocol</guilabel> |
---|
302 | </term> |
---|
303 | <listitem> |
---|
304 | <para> |
---|
305 | The printing protocol that was followed when producing the array batch |
---|
306 | </para> |
---|
307 | </listitem> |
---|
308 | </varlistentry> |
---|
309 | </variablelist> |
---|
310 | <para> |
---|
311 | Click on the &gbSave; button to store the information in BASE2 or on the &gbCancel; |
---|
312 | button to abort. |
---|
313 | </para> |
---|
314 | <para> |
---|
315 | See |
---|
316 | <xref linkend="annotations" /> |
---|
317 | for information about annotating items and inherit annotations. |
---|
318 | </para> |
---|
319 | <para> |
---|
320 | How many slides each batch has can be found in the |
---|
321 | <guilabel>Slides</guilabel> |
---|
322 | column, list view page. |
---|
323 | </para> |
---|
324 | </sect2> |
---|
325 | </sect1> |
---|
326 | |
---|
327 | <sect1 id="array_lims.arrayslide"> |
---|
328 | <title>Array slides</title> |
---|
329 | <para> |
---|
330 | Use |
---|
331 | <menuchoice> |
---|
332 | <guimenu>Array LIMS</guimenu> |
---|
333 | <guimenuitem>Array slides</guimenuitem> |
---|
334 | </menuchoice> |
---|
335 | to get to the list page of array slides. |
---|
336 | </para> |
---|
337 | <sect2 id="array_lims.arrayslide.create"> |
---|
338 | <title>Creating array slides</title> |
---|
339 | <para>In BASE2, array slides can be created, except the common way, by 2 routes:</para> |
---|
340 | <variablelist> |
---|
341 | <varlistentry> |
---|
342 | <term>from the array batch list page</term> |
---|
343 | <listitem> |
---|
344 | <para> |
---|
345 | Clicking on the |
---|
346 | <inlinemediaobject> |
---|
347 | <imageobject> |
---|
348 | <imagedata fileref="figures/add.png" format="PNG" /> |
---|
349 | </imageobject> |
---|
350 | </inlinemediaobject> |
---|
351 | icon in the |
---|
352 | <guilabel>Slides</guilabel> |
---|
353 | column for the batch you want to add a slide to. Corresponding button in |
---|
354 | the view page of a batch is |
---|
355 | <guibutton>New slide…</guibutton> |
---|
356 | . |
---|
357 | </para> |
---|
358 | </listitem> |
---|
359 | </varlistentry> |
---|
360 | <varlistentry> |
---|
361 | <term>using a wizard to create multiple slides simultaneously</term> |
---|
362 | <listitem> |
---|
363 | <para> |
---|
364 | This can be started from three different places: |
---|
365 | <itemizedlist> |
---|
366 | <listitem> |
---|
367 | <para> |
---|
368 | array batch list view by clicking on |
---|
369 | <inlinemediaobject> |
---|
370 | <imageobject> |
---|
371 | <imagedata fileref="figures/new_wizard.gif" |
---|
372 | format="GIF" /> |
---|
373 | </imageobject> |
---|
374 | </inlinemediaobject> |
---|
375 | in the |
---|
376 | <guilabel>Slides</guilabel> |
---|
377 | column of the batch that should be used. |
---|
378 | </para> |
---|
379 | </listitem> |
---|
380 | <listitem> |
---|
381 | <para> |
---|
382 | Using the |
---|
383 | <guibutton>Create slides</guibutton> |
---|
384 | in a single item view of an array batch. |
---|
385 | </para> |
---|
386 | </listitem> |
---|
387 | <listitem> |
---|
388 | <para> |
---|
389 | In the list page of array slides, using the |
---|
390 | <guibutton>Create multiple…</guibutton> |
---|
391 | button |
---|
392 | </para> |
---|
393 | </listitem> |
---|
394 | </itemizedlist> |
---|
395 | The wizard is described further down in |
---|
396 | <xref linkend="array_lims.arrayslide.properties.wizard" /> |
---|
397 | . |
---|
398 | </para> |
---|
399 | </listitem> |
---|
400 | </varlistentry> |
---|
401 | </variablelist> |
---|
402 | </sect2> |
---|
403 | <sect2 id="array_lims.arrayslide.properties"> |
---|
404 | <title>Properties</title> |
---|
405 | |
---|
406 | <figure id="write_docbook_doc.figures.arrayslide-single-create"> |
---|
407 | <title>Create new array slide</title> |
---|
408 | <screenshot> |
---|
409 | <mediaobject> |
---|
410 | <imageobject> |
---|
411 | <imagedata contentwidth="10cm" width="10cm" |
---|
412 | fileref="figures/arrayslide-single-create.png" format="PNG" /> |
---|
413 | </imageobject> |
---|
414 | </mediaobject> |
---|
415 | </screenshot> |
---|
416 | </figure> |
---|
417 | <variablelist> |
---|
418 | <varlistentry> |
---|
419 | <term> |
---|
420 | <guilabel>Name</guilabel> |
---|
421 | </term> |
---|
422 | <listitem> |
---|
423 | <para>The name of the array slide (required).</para> |
---|
424 | </listitem> |
---|
425 | </varlistentry> |
---|
426 | <varlistentry> |
---|
427 | <term> |
---|
428 | <guilabel>Barcode</guilabel> |
---|
429 | </term> |
---|
430 | <listitem> |
---|
431 | <para>Does the array slide have a barcode, it can be put here.</para> |
---|
432 | </listitem> |
---|
433 | </varlistentry> |
---|
434 | <varlistentry> |
---|
435 | <term> |
---|
436 | <guilabel>Destroyed</guilabel> |
---|
437 | </term> |
---|
438 | <listitem> |
---|
439 | <para> |
---|
440 | This check-box can be ticked to mark the slide as destroyed, lost or |
---|
441 | damaged. |
---|
442 | </para> |
---|
443 | </listitem> |
---|
444 | </varlistentry> |
---|
445 | <varlistentry> |
---|
446 | <term> |
---|
447 | <guilabel>Array batch</guilabel> |
---|
448 | </term> |
---|
449 | <listitem> |
---|
450 | <para>Array batch that the slide belongs to (required).</para> |
---|
451 | </listitem> |
---|
452 | </varlistentry> |
---|
453 | <varlistentry> |
---|
454 | <term> |
---|
455 | <guilabel>Index</guilabel> |
---|
456 | </term> |
---|
457 | <listitem> |
---|
458 | <para>The index of the array slide in selected array batch.</para> |
---|
459 | </listitem> |
---|
460 | </varlistentry> |
---|
461 | <varlistentry> |
---|
462 | <term> |
---|
463 | <guilabel>Description</guilabel> |
---|
464 | </term> |
---|
465 | <listitem> |
---|
466 | <para> |
---|
467 | Any information useful information about the slide can be in this field. |
---|
468 | </para> |
---|
469 | </listitem> |
---|
470 | </varlistentry> |
---|
471 | </variablelist> |
---|
472 | <para> |
---|
473 | Click on the &gbSave; button to store the information in BASE2 or on the &gbCancel; |
---|
474 | button to abort. |
---|
475 | </para> |
---|
476 | <sect3 id="array_lims.arrayslide.properties.wizard"> |
---|
477 | <title>Multiple slides wizard</title> |
---|
478 | <para> |
---|
479 | As mentioned above there is an alternative to create one slide at a time if you |
---|
480 | have many to add. There is a wizard that can help you to create at the most 999 |
---|
481 | slides in one go. The wizard is in two steps, both showed in the picture |
---|
482 | <xref linkend="write_docbook_doc.figures.arrayslide-multiple-create" /> |
---|
483 | . |
---|
484 | <orderedlist> |
---|
485 | <listitem> |
---|
486 | <para> |
---|
487 | The first step reminds alot of the normal edit window of an array |
---|
488 | slide, but there are some differences: |
---|
489 | <variablelist> |
---|
490 | <varlistentry> |
---|
491 | <term> |
---|
492 | <guilabel>Quantity</guilabel> |
---|
493 | </term> |
---|
494 | <listitem> |
---|
495 | <para> |
---|
496 | Number of slides to create with this wizard |
---|
497 | (required and must be between 1 and 999) |
---|
498 | </para> |
---|
499 | </listitem> |
---|
500 | </varlistentry> |
---|
501 | <varlistentry> |
---|
502 | <term> |
---|
503 | <guilabel>Start at</guilabel> |
---|
504 | </term> |
---|
505 | <listitem> |
---|
506 | <para> |
---|
507 | The index number to start from when indexing the |
---|
508 | name of the slides. |
---|
509 | </para> |
---|
510 | </listitem> |
---|
511 | </varlistentry> |
---|
512 | <varlistentry> |
---|
513 | <term> |
---|
514 | <guilabel>Pad size</guilabel> |
---|
515 | </term> |
---|
516 | <listitem> |
---|
517 | <para> |
---|
518 | The index will be filled out with zeros in front to |
---|
519 | always have this length. |
---|
520 | </para> |
---|
521 | </listitem> |
---|
522 | </varlistentry> |
---|
523 | </variablelist> |
---|
524 | Press |
---|
525 | <guibutton>Next</guibutton> |
---|
526 | to continue to next step of the wizard. |
---|
527 | <important> |
---|
528 | <para> |
---|
529 | Be sure to get everything right before proceeding, because |
---|
530 | it is not possible to go back from step 2. |
---|
531 | </para> |
---|
532 | </important> |
---|
533 | </para> |
---|
534 | </listitem> |
---|
535 | <listitem> |
---|
536 | <para> |
---|
537 | In step 2 should the barcodes for the array slides be entered, for |
---|
538 | those which have one. The autogenerated names of the slides can also |
---|
539 | be changed if that is wanted, as long as no name-field is left |
---|
540 | empty. |
---|
541 | </para> |
---|
542 | </listitem> |
---|
543 | </orderedlist> |
---|
544 | |
---|
545 | <figure id="write_docbook_doc.figures.arrayslide-multiple-create"> |
---|
546 | <title>Create multiple array slide</title> |
---|
547 | <screenshot> |
---|
548 | <mediaobject> |
---|
549 | <imageobject> |
---|
550 | <imagedata contentwidth="10cm" width="10cm" |
---|
551 | fileref="figures/arrayslide-multiple-create.png" format="PNG" /> |
---|
552 | </imageobject> |
---|
553 | </mediaobject> |
---|
554 | </screenshot> |
---|
555 | </figure> |
---|
556 | Fill in the necessary information as exhaustively as possible. |
---|
557 | </para> |
---|
558 | <para> |
---|
559 | Click on the &gbSave; button to store the information in BASE2 or on the |
---|
560 | &gbCancel; button to abort. |
---|
561 | </para> |
---|
562 | <para> |
---|
563 | See |
---|
564 | <xref linkend="annotations" /> |
---|
565 | for information about annotating items and inherit annotations. |
---|
566 | </para> |
---|
567 | </sect3> |
---|
568 | </sect2> |
---|
569 | </sect1> |
---|
570 | </chapter> |
---|