source: branches/sina/HELP_SOURCE/source/mg_species.hlp

Last change on this file was 19731, checked in by westram, 3 months ago
  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
File size: 7.6 KB
Line 
1#       main topics:
2UP      arb.hlp
3UP      glossary.hlp
4UP      arb_merge_workflow.hlp
5
6#       sub topics:
7SUB     del_list.hlp
8SUB     write_field_list.hlp
9SUB     mod_field_list.hlp
10SUB     mg_xfer_field_of_listed.hlp
11SUB     mg_xfer_field_of_sel.hlp
12
13# format described in ../help.readme
14
15
16TITLE           Compare and Transfer Species Entries
17
18OCCURRENCE      ARB_MERGE/Transfer species
19
20DESCRIPTION     Allows
21                        * database searching,
22                        * comparison of the two databases,
23                        * transferring data from left to right
24                        * realigning sequences to new alignment
25
26        Database Searching:
27
28                To perform database searching within the individual databases
29                use the left or right part of the 'TRANSFER SPECIES' window for
30                source and target database (DB), respectively.
31
32                The database is scanned for 'species' (see LINK{glossary.hlp})
33                which contain (or do not contain) the search string within the
34                specified 'field' (see LINK{glossary.hlp}). The corresponding
35                'species' and the respective 'field' entries are listed in the
36                'HIT LIST' subwindow. The number of hits is displayed after the
37                'Hits:' prompt.
38
39                Define whether matching or non matching species should be
40                listed by pressing the appropriate combination of left
41                and right buttons in the 'QUERY TYPE' area. Performing
42                multiple searches, define whether the list of 'species'
43                should be replaced by the new results, whether newly
44                found 'species' should be removed from or appended
45                to the existing list.
46
47                Select a 'field' from the 'Fields' subwindow.
48
49                Type the search string to the 'Search string' subwindow.
50
51                Press the 'RUN QUERY' button of the results area.
52
53                See also LINK{searching.hlp} and LINK{search_equal_fields.hlp}.
54
55        Marking species:
56
57                The 'TRANSFER SPECIES' window also provides some functionality
58                to interact with species marks (see LINK{mark.hlp}):
59
60                * to mark or unmark all listed species use the corresponding database menu and
61                  select to mark or unmark listed species.
62                  When the hitlist is empty, these entries will mark or unmark all species.
63                * to list all marked species, search for species 'that are marked'.
64                * the number of currently marked species is displayed below the two hitlists,
65                  on the button behind the number of hits.
66                  This button is similar to the one in the ARB main window,
67                  and allows to operate with LINK{species_configs.hlp}.
68
69                Species selections may be transferred between both databases
70                using LINK{mg_species_configs.hlp}.
71
72        Data Transfer:
73
74                Transfer will always happen from source to target species
75                (i.e. from left to right side).
76
77                Select the transfer mode:
78                 * "whole species" will copy all fields,
79                 * "single field" will copy one single field (selectable, allows to append data) and
80                 * "using FTS" will use the "field transfer set" selected below (see LINK{xferset.hlp}).
81
82                   The "using FTS" mode has two flavors (with and w/o sequence data; see section below).
83                   The second mode can be used to update/synchronize metadata between two databases
84                   containing different alignments (e.g. update metadata of common species from
85                   a new SILVA release into your local databases).
86
87                Select the transfer scope:
88                 * "selected species" will copy (from) the selected species into
89                   a new species or to the species selected in the right-side
90                   hitlist.
91                 * "listed species" will copy all species listed in the left-side hitlist.
92
93                Click the 'Transfer species' button in the window center to transfer
94                according to selected transfer-type and -scope.
95
96                See LINK{save.hlp} for howto save the modified database(s).
97
98SECTION         Overwritten data
99
100                This section describes when and what data will be overwritten
101                and when data gets mixed into existing data.
102
103                In "whole species" transfer mode
104                 * any existing species (with the same ID, i.e. 'name') will be deleted and
105                 * a full copy of each source species will be created.
106
107                The "single field" and "using FTS" transfer modes
108                 * will copy from the selected source species to the selected target species
109                   when "selected species" scope is used (regardless whether their IDs match or not) or
110                 * will copy from each listed species to (a new or already existing) target species
111                   with the same ID.
112
113                Some fields are handled special:
114                 * the 'name' entry will always be transferred when missing at target.
115                 * the 'acc' entry will be transferred when missing at target (and when "using FTS" mode).
116                 * whether 'ali_*/data' entries (i.e. the sequence data) will be transferred,
117                   depends on the transfer mode:
118                   * "whole species" and "using FTS (with seq)" will transfer all existing sequence data
119                   * "single field" and "using FTS (w/o seq)" will not transfer any sequence data
120                 * all transferred sequence entries will be targeted by alignment adaption (see below).
121
122SECTION         Adapt Alignment
123
124                ARB Merge tries to keep the alignment correct. Normally people
125                have inserted new gaps in either the left or right database.
126                By entering the ID(s) of some reference species in the input
127                box in the upper center of the TRANSFER SPECIES window, the
128                program will try to find those species in both databases,
129                create a column reference list, and realign all transferred
130                sequences.
131
132                To enable this feature, enable the 'Adapt alignment' toggle.
133
134NOTES           You may mix data from source fields with data of existing target fields
135                using FTS as follows:
136
137                For example if you have a source field 's1' and an existing destination field 'd1'
138                you may merge the contents of these fields (into 'd1') using a simple rule
139                transferring 's1' to 'd1' and add one of the following LINK{aci.hlp} expressions:
140
141                    ACI                   does
142
143                    dd;readdb(d1)         prefix content of 's1' in front of 'd1'
144                    dd;" ";readdb(d1)     dito, but insert one space
145                    readdb(d1);dd         append content of 's1' behind 'd1'
146                    readdb(d1);" ";dd     dito, but insert one space
147
148
149EXAMPLES        For general examples of database searching see LINK{sp_search.hlp}.
150
151WARNINGS        The data will always be transferred from the source DB to
152                the target DB.
153
154                If you want to align sequences during transfer, it is recommended
155                that the left database has fewer gaps than the right one.
156
157                Entries in the target database will be overwritten w/o further consent
158                (applies to single transferred fields and complete transferred species).
159
160BUGS            No bugs known
Note: See TracBrowser for help on using the repository browser.