source: trunk/doc/src/docbook/userdoc/array_lims.xml @ 3414

Last change on this file since 3414 was 3414, checked in by Martin Svensson, 16 years ago

References #565. Major organizations, will read it one more time before this ticket is closed.

  • Property svn:eol-style set to native
  • Property svn:keywords set to Id
File size: 17.2 KB
Line 
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 3414 2007-05-30 21:46:05Z 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 the next section.
172        </para>
173      </sect3>
174
175      <sect3 id="array_lims.arraydesign.properties.annotations">
176        <title>Annotations and inherited annotations</title>
177        <para>
178          This allow you to input values associated to annotation types devised to refine
179          array design description. Read more about annotations in
180          <xref linkend="annotations" />
181          .
182        </para>
183      </sect3>
184
185
186      <sect3 id="array_lims.arraydesign.properties.importfeature">
187        <title>Importing features to an array design</title>
188
189        <para>
190          For non-affymetrix arraydesigns, importing features is an important step in
191          order to fully define an array design. It should be noted that BASE2 does not
192          enforce the immediate feature import upon creation of array design. However, It
193          is STRONGLY advised to do so when creating an array design. Doing so enables to
194          use the array design for downstream analysis with no further trouble. It also
195          matters when importing raw bioassay data and matching those to the corresponding
196          array design.
197        </para>
198
199        <para>
200          This section applies only to non-affymetrix array design since affymetrix
201          designs are handled differently. For affymetrix platform, features are
202          considered imported when the affymetrix CDF file is actually uploaded.
203        </para>
204        <para>
205          From the array design item view, click on the &gbImport; button and use the
206          reporter map importer and an appropriate plugin configuration when following the
207          instructions in
208          <xref linkend="import_export_data.import" />
209          .
210        </para>
211        <note>
212          <para>
213            The button only shows up if the logged in user has enough permissions.
214          </para>
215        </note>
216        <para>
217          If the import run is successful, go to the array design list view. The
218          <guilabel>Has features</guilabel>
219          column will show
220          <guilabel>Yes (n)</guilabel>
221          where n is the number of features actually present on the microarray and now
222          associated to the newly created ArrayDesign.
223        </para>
224      </sect3>
225    </sect2>
226  </sect1>
227
228
229  <sect1 id="array_lims.arraybatch">
230    <title>Array batches</title>
231
232    <sect2 id="array_lims.arraybatch.create">
233      <title>Creating array batches</title>
234      <para>
235        Beside the common way of creating items in BASE, an array batch can also be created
236        directly from an array design, both in list view and single item view.
237      </para>
238      <variablelist>
239        <varlistentry>
240          <term>In list view of array design</term>
241          <listitem>
242            <para>
243              Click on the
244              <inlinemediaobject>
245                <imageobject>
246                  <imagedata fileref="figures/add.png" format="PNG" />
247                </imageobject>
248              </inlinemediaobject>
249              icon available from the
250              <guilabel>Batches</guilabel>
251              column of the array design you want to use.
252              <tip>
253                <para>
254                  As default in BASE the
255                  <guilabel>Batches</guilabel>
256                  column is hidden and need therefore be made visible first, see
257                  <xref linkend="webclient.itemlist.columns" />
258                </para>
259              </tip>
260            </para>
261          </listitem>
262        </varlistentry>
263      </variablelist>
264      <para>
265        <guibutton>New batch&hellip;</guibutton>
266        is the corresponding button in single item view. The current array design will
267        automatically be filled in the array design property for the new batch.
268      </para>
269    </sect2>
270    <sect2 id="array_lims.arraybatch.properties">
271      <title>Properties</title>
272      <variablelist>
273        <varlistentry>
274          <term>
275            <guilabel>Name</guilabel>
276          </term>
277          <listitem>
278            <para>The name of the array batch (required).</para>
279          </listitem>
280        </varlistentry>
281        <varlistentry>
282          <term>
283            <guilabel>Array design</guilabel>
284          </term>
285          <listitem>
286            <para>Array design that is used for the batch.</para>
287          </listitem>
288        </varlistentry>
289        <varlistentry>
290          <term>
291            <guilabel>Print robot</guilabel>
292          </term>
293          <listitem>
294            <para>The print robot that is used.</para>
295          </listitem>
296        </varlistentry>
297        <varlistentry>
298          <term>
299            <guilabel>Protocol</guilabel>
300          </term>
301          <listitem>
302            <para>
303              The printing protocol that was followed when producing the array batch
304            </para>
305          </listitem>
306        </varlistentry>
307      </variablelist>
308      <para>
309        Click on the &gbSave; button to store the information in BASE2 or on the &gbCancel;
310        button to abort.
311      </para>
312      <para>
313        See
314        <xref linkend="annotations" />
315        for information about annotating items and inherit annotations.
316      </para>
317      <para>
318        Number of slides that belongs to each array batch can be found in the
319        <guilabel>Slides</guilabel>
320        column, list view page.
321      </para>
322    </sect2>
323  </sect1>
324
325  <sect1 id="array_lims.arrayslide">
326    <title>Array slides</title>
327    <para>
328      Use
329      <menuchoice>
330        <guimenu>Array LIMS</guimenu>
331        <guimenuitem>Array slides</guimenuitem>
332      </menuchoice>
333      to get to the list page of array slides.
334    </para>
335    <sect2 id="array_lims.arrayslide.create">
336      <title>Creating array slides</title>
337      <para>In BASE2, array slides can be created, except the common way, by 2 routes:</para>
338      <variablelist>
339        <varlistentry>
340          <term>from the array batch list page</term>
341          <listitem>
342            <para>
343              Clicking on the
344              <inlinemediaobject>
345                <imageobject>
346                  <imagedata fileref="figures/add.png" format="PNG" />
347                </imageobject>
348              </inlinemediaobject>
349              icon in the
350              <guilabel>Slides</guilabel>
351              column for the batch to add a slide to. Corresponding button in the view
352              page of a batch is
353              <guibutton>New slide&hellip;</guibutton>
354              .
355            </para>
356          </listitem>
357        </varlistentry>
358        <varlistentry>
359          <term>using a wizard to create multiple slides simultaneously</term>
360          <listitem>
361            <para>
362              This can be started from three different places:
363              <itemizedlist>
364                <listitem>
365                  <para>
366                    array batch list view by clicking on
367                    <inlinemediaobject>
368                      <imageobject>
369                        <imagedata fileref="figures/new_wizard.gif"
370                          format="GIF" />
371                      </imageobject>
372                    </inlinemediaobject>
373                    in the
374                    <guilabel>Slides</guilabel>
375                    column of the batch that should be used.
376                  </para>
377                </listitem>
378                <listitem>
379                  <para>
380                    Using the
381                    <guibutton>Create slides</guibutton>
382                    in a single item view of an array batch.
383                  </para>
384                </listitem>
385                <listitem>
386                  <para>
387                    In the list page of array slides, using the
388                    <guibutton>Create multiple&hellip;</guibutton>
389                    button
390                  </para>
391                </listitem>
392              </itemizedlist>
393              The wizard is described further down in this chapter,
394              <xref linkend="array_lims.arrayslide.properties.wizard" />
395              .
396            </para>
397          </listitem>
398        </varlistentry>
399      </variablelist>
400    </sect2>
401    <sect2 id="array_lims.arrayslide.properties">
402      <title>Properties</title>
403
404      <figure id="write_docbook_doc.figures.arrayslide-single-create">
405        <title>Create New Array Slide from the ArrayBatch List View</title>
406        <screenshot>
407          <mediaobject>
408            <imageobject>
409              <imagedata contentwidth="10cm" width="10cm"
410                fileref="figures/arrayslide-single-create.png" format="PNG" />
411            </imageobject>
412          </mediaobject>
413        </screenshot>
414      </figure>
415      <variablelist>
416        <varlistentry>
417          <term>
418            <guilabel>Name</guilabel>
419          </term>
420          <listitem>
421            <para>The name of the array slide (required).</para>
422          </listitem>
423        </varlistentry>
424        <varlistentry>
425          <term>
426            <guilabel>Barcode</guilabel>
427          </term>
428          <listitem>
429            <para>Does the array slide have a barcode, it can be put here.</para>
430          </listitem>
431        </varlistentry>
432        <varlistentry>
433          <term>
434            <guilabel>Destroyed</guilabel>
435          </term>
436          <listitem>
437            <para>
438              This check-box can be ticked to mark the slide as destroyed, lost or
439              damaged.
440            </para>
441          </listitem>
442        </varlistentry>
443        <varlistentry>
444          <term>
445            <guilabel>Array batch</guilabel>
446          </term>
447          <listitem>
448            <para>Array batch that the slide belongs to (required).</para>
449          </listitem>
450        </varlistentry>
451        <varlistentry>
452          <term>
453            <guilabel>Index</guilabel>
454          </term>
455          <listitem>
456            <para>Index to mark up the name of the array slide.</para>
457          </listitem>
458        </varlistentry>
459        <varlistentry>
460          <term>
461            <guilabel>Description</guilabel>
462          </term>
463          <listitem>
464            <para>
465              Any information useful information about the slide can be in this field.
466            </para>
467          </listitem>
468        </varlistentry>
469      </variablelist>
470      <para>
471        Click on the &gbSave; button to store the information in BASE2 or on the &gbCancel;
472        button to abort.
473      </para>
474      <sect3 id="array_lims.arrayslide.properties.wizard">
475        <title>Multiple slides wizard</title>
476        <para>
477          As mentioned above there is an alternative to create one slide at a time if you
478          have many to add. The wizard is in two steps, both showed in the picture
479          <xref linkend="write_docbook_doc.figures.arrayslide-multiple-create" />
480          .
481          <orderedlist>
482            <listitem>
483              <para>
484                The first step reminds alot of the normal edit window of an array
485                slide, but there are some differences:
486                <variablelist>
487                  <varlistentry>
488                    <term>Quantity</term>
489                    <listitem>
490                      <para>
491                        Number of slides to create with this wizard
492                        (required and must be between 1 and 999)
493                      </para>
494                    </listitem>
495                  </varlistentry>
496                  <varlistentry>
497                    <term>Start at</term>
498                    <listitem>
499                      <para>
500                        The index number to start from when indexing the
501                        name of the slides.
502                      </para>
503                    </listitem>
504                  </varlistentry>
505                  <varlistentry>
506                    <term>Pad size</term>
507                    <listitem>
508                      <para>
509                        The index will be filled out with zeros in front to
510                        always have this length.
511                      </para>
512                    </listitem>
513                  </varlistentry>
514                </variablelist>
515                Press
516                <guibutton>Next</guibutton>
517                to continue to next step of the wizard.
518                <important>
519                  <para>
520                    Be sure to get everything right before proceeding, be cause
521                    it is not possible to go back from step 2.
522                  </para>
523                </important>
524              </para>
525            </listitem>
526            <listitem>
527              <para>
528                In step 2 should the barcodes for the array slides be entered, for
529                those which have one. The autogenerated names of the slides can also
530                be changed if that is wanted, as long as not any name-field is
531                empty.
532              </para>
533            </listitem>
534          </orderedlist>
535        </para>
536        <figure id="write_docbook_doc.figures.arrayslide-multiple-create">
537          <title>Create multiple array slide</title>
538          <screenshot>
539            <mediaobject>
540              <imageobject>
541                <imagedata contentwidth="10cm" width="10cm"
542                  fileref="figures/arrayslide-multiple-create.png" format="PNG" />
543              </imageobject>
544            </mediaobject>
545          </screenshot>
546        </figure>
547        <para>Fill in the necessary information as exhaustively as possible.</para>
548        <para>
549          Click on the &gbSave; button to store the information in BASE2 or on the
550          &gbCancel; button to abort.
551        </para>
552      </sect3>
553    </sect2>
554  </sect1>
555</chapter>
Note: See TracBrowser for help on using the repository browser.