| 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 sp_IDs.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 | OCCURRENCE ARB_MERGE/Check IDs/Synchronize |
|---|
| 15 | |
|---|
| 16 | DESCRIPTION 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 | |
|---|
| 35 | NOTES 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 | |
|---|
| 42 | WARNINGS 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 | |
|---|
| 57 | BUGS No bugs known |
|---|
