| 1 | #Please insert up references in the next lines (line starts with keyword UP) |
|---|
| 2 | UP arb.hlp |
|---|
| 3 | UP glossary.hlp |
|---|
| 4 | UP arb_merge_workflow.hlp |
|---|
| 5 | |
|---|
| 6 | #Please insert subtopic references (line starts with keyword SUB) |
|---|
| 7 | SUB rename.hlp |
|---|
| 8 | |
|---|
| 9 | # Hypertext links in helptext can be added like this: LINK{ref.hlp|http://add|bla@domain} |
|---|
| 10 | |
|---|
| 11 | #************* Title of helpfile !! and start of real helpfile ******** |
|---|
| 12 | TITLE Synchronize species IDs before merging |
|---|
| 13 | |
|---|
| 14 | DESCRIPTION When merging two databases it is VERY IMPORTANT to use identical |
|---|
| 15 | IDs ('name') for identical species and different IDs for different species. |
|---|
| 16 | If not, data of different species will be merged or overwritten. |
|---|
| 17 | |
|---|
| 18 | Species are identified using the accession number and (optionally) one |
|---|
| 19 | additional field. If you use an additional field, a different nameserver |
|---|
| 20 | is used to synchronize species IDs. |
|---|
| 21 | |
|---|
| 22 | Because of different name servers, merging two databases is only possible |
|---|
| 23 | if both databases use no additional field or if they use the same field. |
|---|
| 24 | |
|---|
| 25 | To synchronize IDs of all species in both databases, press the 'Check IDs ...' button |
|---|
| 26 | to open the 'Synchronize IDs' window. |
|---|
| 27 | |
|---|
| 28 | Make sure both databases use the same additional id. |
|---|
| 29 | |
|---|
| 30 | Press the 'Synchronize' button to synchronize species IDs in both databases. |
|---|
| 31 | |
|---|
| 32 | |
|---|
| 33 | NOTES Automatically creates unique IDs (=shortname) for all |
|---|
| 34 | species entries in the database. The entries are identified by |
|---|
| 35 | their accession numbers (public databases). The IDs are created |
|---|
| 36 | using the 'full_name' information. Usually, the first three |
|---|
| 37 | letters are taken from the genus designation, the remaining |
|---|
| 38 | letters from the species name. |
|---|
| 39 | |
|---|
| 40 | In some cases where you are absolutely sure that both databases use |
|---|
| 41 | identical IDs for identical species, but renaming creates |
|---|
| 42 | different IDs (e.g. because one DB lacks accession numbers) |
|---|
| 43 | you can override ID synchronization by checking the 'Override' toggle. |
|---|
| 44 | |
|---|
| 45 | WARNINGS If there are duplicated entries (same accession number - |
|---|
| 46 | different 'full_name'; no accession number - same 'full_name') |
|---|
| 47 | the different versions are indicated by appending running |
|---|
| 48 | numbers separated from the 'name' by a dot. |
|---|
| 49 | |
|---|
| 50 | Normally merging is not allowed when there are duplicated species. |
|---|
| 51 | |
|---|
| 52 | You may override that behavior by checking 'Allow merging duplicates', |
|---|
| 53 | but be warned: |
|---|
| 54 | |
|---|
| 55 | It is VERY DANGEROUS to merge when duplicated species are in your |
|---|
| 56 | databases, cause there is no guarantee, that duplicates with the |
|---|
| 57 | same .NUM suffix refer to the same species. |
|---|
| 58 | You may easily overwrite or duplicate your data! |
|---|
| 59 | |
|---|
| 60 | Similar applies to the 'Override' toggle. Be careful! |
|---|
| 61 | |
|---|
| 62 | BUGS No bugs known |
|---|
