source: trunk/doc/src/docbook/userdoc/file_system.xml @ 3563

Last change on this file since 3563 was 3563, checked in by Nicklas Nordborg, 15 years ago

Fixes #470

  • Property svn:eol-style set to native
  • Property svn:keywords set to Id
File size: 27.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: file_system.xml 3563 2007-07-16 12:46:59Z nicklas $
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="file_system">
30  <?dbhtml dir="filesystem"?>
31  <title>File management</title>
32  <sect1 id="file_system.system">
33    <title>File system</title>
34    <para>
35      Files in BASE 2 are managed from the page at
36      <menuchoice>
37        <guimenu>View</guimenu>
38        <guimenuitem>Files</guimenuitem>
39      </menuchoice>. The basic layout on the page is the same as for all the other list pages
40      in BASE 2 but
41      there are some differences e.g. there is a navigation tree to the left, used to browse
42      the directory structure, and there are some buttons in the toolbar, that are special for
43      files and directories. The figure below is a representation of the files and
44      directories-page and is followed with a short description to some of the special
45      functions.
46    </para>
47    <figure id="file.system.figures.filepage">
48      <title>The file page</title>
49      <screenshot>
50        <mediaobject>
51          <imageobject>
52            <imagedata fileref="figures/filepage.png" format="PNG" 
53            scalefit="1" width="100%" />
54          </imageobject>
55        </mediaobject>
56      </screenshot>
57    </figure>
58    <variablelist>
59      <varlistentry>
60        <term>
61          <interface>1. Home directory for current user</interface>
62        </term>
63        <listitem>
64          <para>
65            This is the logged in user's home directory with sub directories. It is
66            visible if the current user has a home directory and is then always located at
67            the top of the navigation tree. More about this can be read in
68            <xref linkend="file_system.system.browse.tree.home" />.
69            Click on a directory to display it's contents to the right
70            or click on the plus sign to expand the directory and view the
71            sub directories (no plus sign = no sub directories).
72          </para>
73        </listitem>
74      </varlistentry>
75
76      <varlistentry>
77        <term>
78          <interface>2. Other users</interface>
79        </term>
80        <listitem>
81          <para>
82            The other users' home directories that the current user has permission
83            to read are listed here, including his/her own.
84          </para>
85        </listitem>
86      </varlistentry>
87
88      <varlistentry>
89        <term>
90          <interface>3. Refresh button</interface>
91        </term>
92        <listitem>
93          <para>
94            This button, which is located at the bottom of the navigation tree,
95            refreshes/updates the directory tree. It can for example be used to get a
96            recently created directory to appear in the tree.
97          </para>
98        </listitem>
99      </varlistentry>
100
101      <varlistentry>
102        <term>
103          <interface>4. Current directory</interface>
104        </term>
105        <listitem>
106          <para>Shows the full BASE 2 path to current directory.</para>
107        </listitem>
108      </varlistentry>
109
110      <varlistentry>
111        <term>
112          <interface>5. View a file's contents</interface>
113        </term>
114        <listitem>
115          <para>
116            A click on this icon will open the file's contents in a new window. If the
117            browser does not has support to view the file there will be a dialog window
118            to download the file instead.
119          </para>
120        </listitem>
121      </varlistentry>
122
123      <varlistentry>
124        <term>
125          <interface>6. Download file</interface>
126        </term>
127        <listitem>
128          <para>
129            Download the file to a local computer with this icon. The download will
130            start in a new dialog window.
131          </para>
132        </listitem>
133      </varlistentry>
134
135      <varlistentry>
136        <term>
137          <interface>7. Re-upload a file</interface>
138        </term>
139        <listitem>
140          <para>
141            This icon is only visible for those files that have been moved offline and
142            it can be used to re-upload the file to the BASE. Start to
143            upload the file to the same position by clicking on the icon.
144          </para>
145         
146          <note>
147            <title>Replace an existing file</title>
148            <para>
149              It is possible to re-upload file that are online, but this
150              has to be done from the single-item view.
151            </para>
152          </note>
153        </listitem>
154      </varlistentry>
155    </variablelist>
156
157    <sect2 id="file_system.system.browse">
158      <title>Browse the file system</title>
159      <para>
160        Browsing thr BASE 2 file system is done from the navigation bar by clicking on a
161        directory in the tree to view it's contents. Both sub directories and files in the
162        selected directory are showed. A directory with sub directories can be expand with a
163        click on the plus-sign.
164      </para>
165      <note>
166        <title>Browse a directory</title>
167        <para>
168          A directory can only be open from the navigation tree and never from the list. A
169          click on a directory's name in the list will open the directory's edit window.
170        </para>
171      </note>
172      <sect3 id="file_system.system.browse.tree">
173        <title>Navigation tree</title>
174        <para>
175          The navigation tree contains of folders/directories that the logged in user has
176          permission to read. At the top is the current user's home directory and under it
177          is a folder with all accessible home directories.
178        </para>
179        <para>
180          The tree can be updated with the refresh-button at the bottom of the panel (the
181          tree is not self-refreshing).
182        </para>
183        <sect4 id="file_system.system.browse.tree.home">
184          <title>Home directory - 'My home'</title>
185          <para>
186            To make it easier for the logged in user to find his/her directory without
187            having to scroll through the whole list of home directories, his or hers
188            home directory is located at the top of the navigation tree under the
189            <interface>My home</interface>
190            folder.
191          </para>
192          <note>
193            <title>No home directory</title>
194            <para>
195              Not all users have a home directory connected to their accounts. If
196              <interface>My home</interface>
197              is missing, it most certainly depends on that the current user account
198              have not got a home directory. Home directories are managed by the
199              administrator of the BASE server.
200            </para>
201          </note>
202        </sect4>
203      </sect3>
204    </sect2>
205    <sect2 id="file_system.system.quota">
206      <title>Disk space quota</title>
207      <para>
208        Normally, a user is assigned limited disk spacefor files.
209        More information about how much quota the current account has and how much of it
210        that is occupied can be found at the account's home page, described in
211        <xref linkend="webclient.intro.homepage" />.
212      </para>
213     
214      <para>
215        See <xref linkend="user_administration.quota" /> for more information about
216        the quota system.
217      </para>
218    </sect2>
219  </sect1>
220
221  <sect1 id="file_system.handling">
222    <title>Handling files</title>
223   
224    <sect2 id="file_system.handling.upload">
225      <title>Upload a new file</title>
226      <para>
227        Uploading a file is started by clicking on
228        <guibutton>Upload file&hellip;</guibutton>
229        in the toolbar. The uploaded file will be placed in current directory.
230      </para>
231     
232      <figure id="file_system.figures.upload">
233        <title>Upload new file</title>
234        <screenshot>
235          <mediaobject>
236            <imageobject><imagedata 
237              fileref="figures/upload_file.png" format="PNG"
238              /></imageobject>
239          </mediaobject>
240        </screenshot>
241      </figure>
242     
243      <helptext external_id="file.upload" title="Upload a file">
244        <para>
245          <variablelist>
246            <varlistentry>
247              <term>
248                <guilabel>Directory</guilabel>
249              </term>
250              <listitem>
251                <para>
252                  Shows the current directory, where the file will be uploaded.
253                  This property cannot be changed and is only for information.
254                </para>
255              </listitem>
256            </varlistentry>
257            <varlistentry>
258              <term>
259                <guilabel>File</guilabel>
260              </term>
261              <listitem>
262                <para>
263                  This field is required and needs to have a valid file path for
264                  the local computer before the upload is started. Use
265                  <guibutton>Browse&hellip;</guibutton>
266                  to choose which file to upload.
267                </para>
268              </listitem>
269            </varlistentry>
270            <varlistentry>
271              <term>
272                <guilabel>Write protected</guilabel>
273              </term>
274              <listitem>
275                <para>
276                  Mark this checkbox if you want the file to be write
277                  protected. A write protected file cannot be deleted,
278                  moved offline or replaced with another file. It is
279                  still possible to change other metadata, such as
280                  the name, description, file type, MIME type, etc.
281                </para>
282              </listitem>
283            </varlistentry>
284            <varlistentry>
285              <term>
286                <guilabel>Type</guilabel>
287              </term>
288              <listitem>
289                <para>
290                  This is the file-type that the uploaded file should get.
291                  <nohelp>The
292                  file-types to choose between from the drop-down list are
293                  described in
294                  <xref linkend="file_system.filetypes" />.</nohelp>
295                  Select
296                  <userinput>- none -</userinput>
297                  if the file should not be associated with any file type.
298                </para>
299              </listitem>
300            </varlistentry>
301            <varlistentry>
302              <term>
303                <guilabel>Description</guilabel>
304              </term>
305              <listitem>
306                <para>
307                  A description about the uploaded file can be put into this text
308                  area. Use the magnifying glass to edit the text in a pop-up
309                  window with a larger text area.
310                </para>
311              </listitem>
312            </varlistentry>
313            <varlistentry>
314              <term>
315                <guilabel>Max transfer rate</guilabel>
316              </term>
317              <listitem>
318                <para>
319                  This shows the maximum transfer rate that the upload will
320                  approximately reach. The transfer rate is set by the
321                  server admin and cannot be changed.
322                </para>
323              </listitem>
324            </varlistentry>
325            <varlistentry>
326              <term>
327                <guilabel>Compressed file</guilabel>
328              </term>
329              <listitem>
330                <para>
331                  These settings are only active if you select
332                  a compressed file format that BASE knows how to
333                  unpack. BASE ships with support for some of the most common
334                  compressed file formats, such as zip and tar,
335                  but this can be extended by the use of plug-ins.
336                  <nohelp>See <xref linkend="plugin_developer.other.unpacker" 
337                    /> for more information.</nohelp>
338                   
339                  <itemizedlist>
340                    <listitem>
341                      <para>
342                        <guilabel>Unpack file</guilabel>:
343                        Mark this checkbox if the compressed file should
344                        be unpacked after it had been uploaded. The
345                        files will be unpacked with the same subdirectory
346                        structure as in the compressed file.
347                      </para>
348                    </listitem>
349                   
350                    <listitem>
351                      <para>
352                        <guilabel>Overwrite existing files</guilabel>:
353                        Mark this checkbox if the unpacking is allowed
354                        to overwrite existing files.
355                      </para>
356                    </listitem>
357                    <listitem>
358                      <para>
359                        <guilabel>Keep the compressed file</guilabel>:
360                        Mark this checkbox if you want to keep the
361                        compressed file after upload. Otherwise, only
362                        the unpacked files are kept.
363                      </para>
364                    </listitem>
365                  </itemizedlist>
366                </para>
367              </listitem>
368            </varlistentry>
369          </variablelist>
370        </para>
371        <para>
372          Finish the configuration by clicking on either
373          <guibutton>Upload</guibutton>, which will start uploading the selected file, or
374          &gbCancel; to abort the upload procedure.
375        </para>
376      </helptext>
377     
378      <sect3 id="file_system.handling.actions.reupload">
379        <title>Replace an existing file</title>
380        <para>
381          It is possible to replace an existing file. This is done by clicking
382          on the <guilabel>replace</guilabel> link on the single-item view
383          for the file you want to replace. If the file has been moved offline,
384          you can also use the icon
385          in the actions-column, see number 7 in
386          <xref linkend="file.system.figures.filepage" />.
387          The procedure to upload the file is the same as when uploading a new file,
388          except that compressed files cannot be unpacked. There is also an
389          extra option, <guilabel>Validate MD5</guilabel>, that tells BASE to
390          check that the file is the same as the one it is replacing. This option
391          is useful when you are re-uploading a file that has been moved offline
392          and want to be certain that it is the same file as the original.
393        </para>
394       
395        <para>
396          You cannot replace a file which has been marked as
397          <emphasis>write protected</emphasis>.
398        </para>
399      </sect3>
400     
401    </sect2>
402    <sect2 id="file_system.handling.edit">
403      <title>Edit a file</title>
404      <para>
405        The edit window to set a file's property in can either be open with
406        &gbEdit;
407        that is located in the toolbar at the file's view page or by holding down
408        <keycap>CTRL</keycap>, <keycap>ALT</keycap>
409        or <keycap>SHIFT</keycap>
410        when clicking on the file's name in the list. It requires that the current user has
411        write permission on the file to be able to edit and set the properties.
412      </para>
413
414      <helptext external_id="file.edit" title="Edit file properties">
415        <variablelist>
416          <varlistentry>
417            <term>
418              <guilabel>Path</guilabel>
419            </term>
420            <listitem>
421              <para>
422                This is the path where the file is located. This can only be changed
423                by moving the file.
424                <nohelp>Read more about how this is done in
425                <xref linkend="file_system.handling.move" /></nohelp>.
426              </para>
427            </listitem>
428          </varlistentry>
429          <varlistentry>
430            <term>
431              <guilabel>Name</guilabel>
432            </term>
433            <listitem>
434              <para>
435                The file's name, which cannot be left empty and must be unique in
436                current directory. The maximum length of the file name is 255
437                characters and it can contain blank spaces but not any of
438                <keycap>~</keycap>,
439                <keycap>\</keycap>,
440                <keycap>/</keycap>,
441                <keycap>:</keycap>,
442                <keycap>;</keycap>,
443                <keycap>*</keycap>,
444                <keycap>&#63;</keycap>,
445                <keycap>&lt;</keycap>,
446                <keycap>&gt;</keycap>
447                or
448                <keycap>|</keycap>.
449              </para>
450            </listitem>
451          </varlistentry>
452          <varlistentry>
453            <term>
454              <guilabel>Write protected</guilabel>
455            </term>
456            <listitem>
457              <para>
458                Mark this checkbox if you want the file to be write
459                protected. A write protected file cannot be deleted,
460                moved offline or replaced with another file. It is
461                still possible to change other metadata, such as
462                the name, description, file type, MIME type, etc.
463              </para>
464            </listitem>
465          </varlistentry>
466          <varlistentry>
467            <term>
468              <guilabel>Type</guilabel>
469            </term>
470            <listitem>
471              <para>
472                Sets which kind of type the file is. Select the file type to use
473                from the drop down list with available types. The option
474                <guilabel>-none-</guilabel>
475                should be used if the file should not be associated with any kind of
476                file type.
477              </para>
478            </listitem>
479          </varlistentry>
480          <varlistentry>
481            <term>
482              <guilabel>MIME type</guilabel>
483            </term>
484            <listitem>
485              <para>
486                The file's content/media type. This is normally set automatically
487                when uploading the file into BASE but it can be changed by an user,
488                that has write permissions, at any time.
489              </para>
490            </listitem>
491          </varlistentry>
492          <varlistentry>
493            <term>
494              <guilabel>Description</guilabel>
495            </term>
496            <listitem>
497              <para>
498                This text area can be used to store relevant information about file
499                and it's contents. Use the magnifying glass, located to the right
500                under the text area, to edit the text in a larger window.
501              </para>
502            </listitem>
503          </varlistentry>
504        </variablelist>
505        <para>
506          Finish the editing process by pressing either
507          &gbSave;
508          to save the properties to the database or
509          &gbCancel;
510          to abort and discard the changes.
511        </para>
512      </helptext>
513
514    </sect2>
515    <sect2 id="file_system.handling.move">
516      <title>Move files</title>
517     
518      <para>
519        These functions are used to manage the location of the files on the
520        server. They are all accessed from the <guibutton>Move</guibutton>
521        button on the list view of from the single-item view. On the list view,
522        you must first select one or more files / directories.
523      </para>
524     
525      <tip>
526        <title>Write protect your files!</title>
527        <para>
528        If you mark a file as <emphasis>write protected</emphasis> it will
529        not be possible to delete, move or replace the file. Use this options
530        for important data files that you do not want to loose by accident.
531        </para>
532      </tip>
533     
534      <sect3 id="file_system.handling.move.directory">
535        <title>To another directory</title>
536        <para>
537          Files and directories can be moved to other directories for re-organization. The
538          user need write permission on the target directory to be able to move the
539          files/directories to it.
540        </para>
541        <para>
542          First, select all files and directories in the current path that should be moved
543          and then click on
544          <menuchoice>
545            <guibutton>Move&hellip;</guibutton>
546            <guisubmenu>To another directory</guisubmenu>
547          </menuchoice>
548          in the toolbar to open a window with the directory tree where the target directory
549          can be picked.
550        </para>
551        <para>
552          Choose a directory which the selected items should be moved to. It
553          is possible to create new subdirectories with the
554          &gbNew; button.
555        </para>
556        <para>
557          Click on
558          &gbOk;
559          to carry out the move or
560          &gbCancel;
561          to abort.
562        </para>
563      </sect3>
564     
565      <sect3 id="file_system.handling.move.offline">
566        <title>Offline</title>
567        <para>
568          Moving a file offline means that the actual file contents is deleted from the
569          server's disk space but information about the file will still exist as an item
570          in the database. This makes it possible to save disk space but still be
571          able to associated the file with other items in BASE.
572        </para>
573        <para>
574          First, select all files in current path that should be moved offline
575          and then click on
576          <menuchoice>
577            <guibutton>Move&hellip;</guibutton>
578            <guisubmenu>Offline</guisubmenu>
579          </menuchoice>
580          in the toolbar.
581        </para> 
582        <warning>
583          <para>
584          Be careful! The selected files will be removed from the server.
585          The only way to recover the contents again is to re-upload the files.
586          </para>
587        </warning>
588      </sect3>
589
590      <sect3 id="file_system.handling.move.secondary">
591        <title>To the secondary storage</title>
592
593        <para>
594          This option is only available if the server administrator
595          has enabled it.
596        </para>
597
598        <para>
599          The secondary storage is a kind of storage were it is appropriate
600          to store files that have been used and no longer requires immediate
601          access. Moving a file to and from the secondary storage is the job
602          of a plug-in, which is usually executed once or twice a day.
603        </para>
604       
605        <para>
606          First, select all files in the current path that should be moved
607          and then click on
608          <menuchoice>
609            <guibutton>Move&hellip;</guibutton>
610            <guisubmenu>To secondary location</guisubmenu>
611          </menuchoice>
612          in the toolbar. The only thing that will happen is that BASE sets a flag
613          on each file. The next time the secondary storage plug-in
614          is executed, the files will be moved to the secondary storage. The
615          actual file contents is deleted from the server's disk.
616        </para>
617       
618        <para>
619          While the file is in the secondary storage BASE behaves in the same way as
620          if the file is offline. Th file cannot be used to import data from, or
621          other things. To use the file again, the file must be moved back to
622          the primary storage.
623        </para>
624       
625        <para>
626          To bring files back from the secondary storage, select the files
627          and then click on
628          <menuchoice>
629            <guibutton>Move&hellip;</guibutton>
630            <guisubmenu>To primary location</guisubmenu>
631          </menuchoice> in the toolbar. The files will be moved back the next
632          time the secondary storage plug-in is executed.
633        </para>
634       
635        <note>
636          <title>Do not forget to set quota for the secondary storage</title>
637          <para>
638            The default installation does not assign quota for the
639            secondary storage. Unless the administrator assigns quota
640            the move will silently fail.
641          </para>
642        </note>
643      </sect3>
644
645    </sect2>
646
647    <sect2 id="file_system.handling.actions">
648      <title>Viewing and downloading files</title>
649      <para>
650        In <guilabel>Actions</guilabel> column in the list view there
651        are icons you can click on to perform different kinds of actions on a
652        file, like downloading the file and viewing the file. The same icons appear
653        on the single-item view and in most other places where files are used.
654        You cannot view or download files that have been moved offline or to the
655        secondary storage.
656      </para>
657      <sect3 id="file_system.handling.actions.download">
658        <title>Download a file</title>
659        <para>
660          This will let the user to download the contents of a file to a path on a local
661          computer. The window that opens contains the selected file's name, size e.t.c.
662          and it will also open a download dialog window where the user can choose what to
663          do with the file locally.
664          <tip>
665            <title>Download does not start</title>
666            <para>
667              Click on the file's path name in the pop-up window if the download
668              dialog window does not appears.
669            </para>
670          </tip>
671        </para>
672        <para>
673          Close the pop-up window and return to file page with
674          &gbClose;.
675        </para>
676      </sect3>
677      <sect3 id="file_system.handling.actions.view">
678        <title>View the contents of file</title>
679        <para>
680          A file's contents can be displayed directly in the web browser if the
681          browser supports displaying that kind of files. Typically all HTML, text
682          files and images are supported. Click on the icon to view the contents
683          in a new window. If the type is not supported by the browser there will be
684          a dialog-window to download the file instead.
685        </para>
686      </sect3>
687    </sect2>
688    <sect2 id="file_system.handling.directories">
689      <title>Directories</title>
690      <para>
691        Directories in BASE are folders where files can be organized into. Click on
692        <guibutton>New directory&hellip;</guibutton>
693        in the toolbar to create a directory in current path and edit the properties as
694        described below.
695      </para>
696      <sect3 id="file_system.handling.directories.edit">
697        <title>Edit a directory</title>
698        <para>
699          The window to edit a directory's properties is opened either by clicking on the
700          directory's name in the list or when creating a new directory.
701        </para>
702        <helptext external_id="directory.edit" title="Edit directory">
703          <para>
704            <variablelist>
705              <title>Properties</title>
706              <varlistentry>
707                <term>
708                  <guilabel>Path</guilabel>
709                </term>
710                <listitem>
711                  <para>
712                    This property is read-only in the edit window but can be
713                    changed by moving the directory<nohelp>, described in
714                    <xref linkend="file_system.handling.move" /></nohelp>.
715                  </para>
716                </listitem>
717              </varlistentry>
718              <varlistentry>
719                <term>
720                  <guilabel>Name</guilabel>
721                </term>
722                <listitem>
723                  <para>
724                    The directory's name to identify it with in the list. This
725                    field must have a value and it has to be an unique name for
726                    the current directory.
727                  </para>
728                </listitem>
729              </varlistentry>
730              <varlistentry>
731                <term>
732                  <guilabel>Description</guilabel>
733                </term>
734                <listitem>
735                  <para>
736                    Any relevant information about the directory can be written
737                    in this text area. The magnifying glass down to the right
738                    can be used to edit the description text in a larger text
739                    area, just click on the icon to open it in a separate pop-up
740                    window.
741                  </para>
742                </listitem>
743              </varlistentry>
744            </variablelist>
745          </para>
746          <para>
747            The editing process is completed with either
748            &gbSave;, to save the properties into the database, or with
749            &gbCancel;
750            to discard the changes. Both of the buttons will close the edit window and
751            if the directory is updated the list will be reloaded with the directory's
752            new properties.
753          </para>
754         
755          <note>
756            The new directory does not appear in the navigation tree
757            to the left automatically. You must click on the
758            <guibutton>Refresh</guibutton> button.
759          </note>
760         
761        </helptext>
762      </sect3>
763    </sect2>
764
765  </sect1>
766
767  <sect1 id="file_system.filetypes">
768    <title>File types</title>
769    <para>
770      A file can be associated with one of the file types that exists in BASE 2. File types
771      make it possible to filter the files depending of what kind of file it is. Here
772      is a list of file types that are defined in BASE.
773      <menuchoice>
774        <guimenu>Administrate</guimenu>
775        <guisubmenu>Types</guisubmenu>
776        <guimenuitem>File types</guimenuitem>
777      </menuchoice>
778    </para>
779    <variablelist>
780      <title>File types</title>
781      <varlistentry>
782        <term>Image</term>
783        <listitem>
784          <para>Indicates that the file is an image file.</para>
785        </listitem>
786      </varlistentry>
787      <varlistentry>
788        <term>Plate</term>
789        <listitem>
790          <para>The associated file is a file with information about plate/plates.</para>
791        </listitem>
792      </varlistentry>
793      <varlistentry>
794        <term>Plate mapping</term>
795        <listitem>
796          <para>Files with information about plate mapping.</para>
797        </listitem>
798      </varlistentry>
799      <varlistentry>
800        <term>Print map</term>
801        <listitem>
802          <para>Print map files</para>
803        </listitem>
804      </varlistentry>
805      <varlistentry>
806        <term>Protocol</term>
807        <listitem>
808          <para>Files with protocol information</para>
809        </listitem>
810      </varlistentry>
811      <varlistentry>
812        <term>Raw data</term>
813        <listitem>
814          <para>Raw data files</para>
815        </listitem>
816      </varlistentry>
817      <varlistentry>
818        <term>Reporter</term>
819        <listitem>
820          <para>Files with information about reporters</para>
821        </listitem>
822      </varlistentry>
823      <varlistentry>
824        <term>Reporter map</term>
825        <listitem>
826          <para>
827            Files of this type contain information about how the reporters are mapped.
828          </para>
829        </listitem>
830      </varlistentry>
831      <varlistentry>
832        <term>Spot images</term>
833        <listitem>
834          <para>A zip-file containing generated spot images in JPEG format.</para>
835        </listitem>
836      </varlistentry>
837    </variablelist>
838  </sect1>
839</chapter>
Note: See TracBrowser for help on using the repository browser.