Changeset 4401 for trunk/doc/src/docbook/userdoc/array_lims.xml
- Timestamp:
- Aug 20, 2008, 3:58:58 PM (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/src/docbook/userdoc/array_lims.xml
r4131 r4401 7 7 8 8 Copyright (C) 2007 Nicklas Nordborg, Philippe Rocca-Serra, Martin Svensson 9 Copyright (C) 2007 Jari Hakkinen, Nicklas Nordborg 9 10 10 11 This file is part of BASE - BioArray Software Environment. … … 27 28 --> 28 29 29 <chapter id="array_lims" >30 <chapter id="array_lims" chunked="0"> 30 31 <?dbhtml dir="array_lims"?> 31 32 <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 </para> 58 59 </sect1> 33 34 <para> 35 Arrays are at the core of the BASE business and are essential 36 elements to describe in order to 37 be <ulink url='http://www.mged.org/Workgroups/MIAME/miame.html'>MIAME</ulink> 38 compliant. It is also critical to track and manage information 39 about microarray design as accurately as possible since mistakes 40 could prove extremely costly in downstream analysis. 41 </para> 42 <para> 43 As a good practice, all array related information should be 44 entered into BASE prior to work on describing the sample 45 processing and hybridizations events making up a microarray 46 experiment is begun. 47 </para> 48 <para> 49 BASE is engineered to support microarray printing facilities. The 50 system therefore offers objects to describe plates, their 51 geometries, and the events (<emphasis>e.g.</emphasis>, merging and 52 printing) affecting them. The first section of this chapter deals 53 with this functionality as well as plate management. Users buying 54 arrays from commercial sources can ignore the plate management 55 component and immediately jump to 56 <xref linkend="array_lims.arraydesign" />. 57 </para> 60 58 61 59 <sect1 id="array_lims.platemanagement"> … … 72 70 may run out leading to the interruption of this process. All slides created during this 73 71 printing process belong to the same printing batch. It is the array slide that will 74 eventually be used in a hybridization event. BASE 2allows user to track those 3 entities72 eventually be used in a hybridization event. BASE allows user to track those 3 entities 75 73 with great details. This is an important functionality for users producing their own 76 74 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 BASE 2to help in these75 printing facility. The following sections detail how to use BASE to help in these 78 76 tasks. 79 77 </para> … … 148 146 </variablelist> 149 147 <para> 150 Click on the &gbSave; button to store the information in BASE 2or on the148 Click on the &gbSave; button to store the information in BASE or on the 151 149 &gbCancel; button to abort. 152 150 </para> … … 175 173 176 174 <para> 177 Importing features is an important step in 178 order to fully define an array design. It should be noted that BASE2 does not 179 enforce the immediate feature import upon creation of array design. However, it 180 is STRONGLY advised to do so when creating an array design. Doing so enables to 181 use the array design for downstream analysis with no further trouble. It also 182 matters when importing raw bioassay data and matching those to the corresponding 183 array design. 175 Importing features is an important step in order to fully 176 define an array design. It should be noted that BASE does not 177 enforce the immediate feature import upon creation of array 178 design. However, it is STRONGLY advised to do so when creating 179 an array design. Performing the import enables use of the 180 array design in downstream analysis with no further 181 trouble. It also matters when importing raw bioassay data and 182 matching those to the corresponding array design. 184 183 </para> 185 184 … … 313 312 </variablelist> 314 313 <para> 315 Click on the &gbSave; button to store the information in BASE 2or on the &gbCancel;314 Click on the &gbSave; button to store the information in BASE or on the &gbCancel; 316 315 button to abort. 317 316 </para> … … 341 340 <sect2 id="array_lims.arrayslide.create"> 342 341 <title>Creating array slides</title> 343 <para>In BASE 2, array slides can be created, except the common way, by 2 routes:</para>342 <para>In BASE, array slides can be created, except the common way, by 2 routes:</para> 344 343 <variablelist> 345 344 <varlistentry> … … 479 478 </variablelist> 480 479 <para> 481 Click on the &gbSave; button to store the information in BASE 2or on the &gbCancel;480 Click on the &gbSave; button to store the information in BASE or on the &gbCancel; 482 481 button to abort. 483 482 </para> … … 565 564 </para> 566 565 <para> 567 Click on the &gbSave; button to store the information in BASE 2or on the566 Click on the &gbSave; button to store the information in BASE or on the 568 567 &gbCancel; button to abort. 569 568 </para>
Note: See TracChangeset
for help on using the changeset viewer.