source: branches/lib/HELP_SOURCE/source/mg_names.hlp

Last change on this file was 19532, checked in by westram, 4 months ago
  • reintegrates 'help' into 'trunk'
    • tweak arb documentation:
      • automatically link
        • ticket references to arb bug tracker (only affects html version).
        • found URLs.
      • page titles
        • warn about long titles.
        • introduce SUBTITLEs (automatically triggered by multi-line titles in source files).
        • increase allowed length (limited by subwindow width).
      • cleanup header sections in all helpfiles.
      • fix and/or update several help files.
      • document syntax of help sources.
      • build issues:
        • when xml validation fails, next build no longer uses invalid xml ⇒ keeps failing.
        • remove output files on error (including files below ARBHOME/lib).
        • pipe output through logs to ensure proper wrapping in Entering/Leaving lines.
    • moves Tree admin + NDS menu entries to top of menu
  • adds: log:branches/help@18783:19531
  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
File size: 2.4 KB
Line 
1#       main topics:
2UP      arb.hlp
3UP      glossary.hlp
4UP      arb_merge_workflow.hlp
5
6#       sub topics:
7SUB     sp_IDs.hlp
8
9# format described in ../help.readme
10
11
12TITLE           Synchronize species IDs before merging
13
14OCCURRENCE      ARB_MERGE/Check IDs/Synchronize
15
16DESCRIPTION     When merging two databases it is VERY IMPORTANT to use identical
17                IDs ('name') for identical species and different IDs for different species.
18                If not, data of different species will be merged or overwritten.
19
20                Species are identified using the accession number and (optionally) one
21                additional field. If you use an additional field, a different NAMESERVER
22                is used to synchronize species IDs.
23
24                Because of different NAMESERVERs, merging two databases is only possible
25                if both databases use no additional field or if they use the same field.
26
27                To synchronize IDs of all species in both databases, press the 'Check IDs ...' button
28                to open the 'Synchronize IDs' window.
29
30                Make sure both databases use the same additional field.
31
32                Press the 'Synchronize' button to synchronize species IDs in both databases.
33
34
35NOTES           Please also refer to LINK{sp_IDs.hlp}.
36
37                In some cases where you are absolutely sure that both databases use
38                identical IDs for identical species, but renaming creates
39                different IDs (e.g. because one DB lacks accession numbers)
40                you can override ID synchronization by checking the 'Override' toggle.
41
42WARNINGS        If there are duplicated species entries the different versions are indicated by
43                appending running numbers separated from the 'name' by a dot.
44
45                Normally merging is not allowed when there are duplicated species.
46
47                You may override that behavior by checking 'Allow merging duplicates',
48                but be warned:
49
50                    It is VERY DANGEROUS to merge when duplicated species are in your
51                    databases, cause there is no guarantee, that duplicates with the
52                    same .NUM suffix refer to the same species.
53                    You may easily overwrite or duplicate your data!
54
55                Similar applies to the 'Override' toggle. Be careful!
56
57BUGS            No bugs known
Note: See TracBrowser for help on using the repository browser.