| 1 | #Please insert up references in the next lines (line starts with keyword UP) |
|---|
| 2 | UP arb.hlp |
|---|
| 3 | UP glossary.hlp |
|---|
| 4 | |
|---|
| 5 | #Please insert subtopic references (line starts with keyword SUB) |
|---|
| 6 | SUB mg_names.hlp |
|---|
| 7 | |
|---|
| 8 | # Hypertext links in helptext can be added like this: LINK{ref.hlp|http://add|bla@domain} |
|---|
| 9 | |
|---|
| 10 | #************* Title of helpfile !! and start of real helpfile ******** |
|---|
| 11 | TITLE Nameserver admin |
|---|
| 12 | |
|---|
| 13 | OCCURRENCE ARB_NT/Tools/Nameserver admin |
|---|
| 14 | |
|---|
| 15 | SECTION General warning |
|---|
| 16 | |
|---|
| 17 | Most of the functions here will destroy or at least affect the consistency |
|---|
| 18 | of the species IDs (shortnames) for all users of the affected names.dat. |
|---|
| 19 | |
|---|
| 20 | Please only use these functions if you really know what you are doing. |
|---|
| 21 | Otherwise ask your local ARB guru. |
|---|
| 22 | |
|---|
| 23 | DESCRIPTION Delete old names file |
|---|
| 24 | |
|---|
| 25 | After using the NAMESERVER for a while, the names database |
|---|
| 26 | may contain several entries which are used nowhere. |
|---|
| 27 | |
|---|
| 28 | This happens e.g. if you've changed accession numbers during |
|---|
| 29 | your data curation or if you had species in one of your database |
|---|
| 30 | which you don't store anymore. |
|---|
| 31 | |
|---|
| 32 | To get rid of these unused IDs click 'Delete old names file'. |
|---|
| 33 | Your names database will be deleted and all IDs will be regenerated. |
|---|
| 34 | |
|---|
| 35 | Edit names file |
|---|
| 36 | |
|---|
| 37 | The names database is a simple text file, which may be modified |
|---|
| 38 | with a texteditor. |
|---|
| 39 | |
|---|
| 40 | Use this feature with care! |
|---|
| 41 | |
|---|
| 42 | Remove ARB_XXXX entries |
|---|
| 43 | |
|---|
| 44 | ARB automatically generates accession numbers if they are missing. |
|---|
| 45 | e.g if you import plain sequence data. |
|---|
| 46 | |
|---|
| 47 | Use this to get rid of all NAMESERVER entries using ARB_xxx accession |
|---|
| 48 | numbers. |
|---|
| 49 | |
|---|
| 50 | After using any of the above functions |
|---|
| 51 | |
|---|
| 52 | you should consider to synchronize IDs (see LINK{rename.hlp}) in |
|---|
| 53 | all your arb-databases. |
|---|
| 54 | |
|---|
| 55 | Additional species ID field |
|---|
| 56 | |
|---|
| 57 | If you have good reasons, why you have to keep several species |
|---|
| 58 | with identical accession numbers in your databases, you'll normally |
|---|
| 59 | get problems with the ARB NAMESERVER, because it handles these species |
|---|
| 60 | as "identical" and gives them IDs like 'HalHalob.2', 'HalHalob.3' etc. |
|---|
| 61 | to mark them as duplicates. |
|---|
| 62 | |
|---|
| 63 | Here you can specify an additional DB-species-field, which will be used |
|---|
| 64 | for species identification in addition to 'acc' (accession number). |
|---|
| 65 | |
|---|
| 66 | This setting is database-specific - so you have to set it for each database |
|---|
| 67 | where it's needed. |
|---|
| 68 | |
|---|
| 69 | For each field you use, a separate NAMESERVER will be generated. |
|---|
| 70 | That means: |
|---|
| 71 | |
|---|
| 72 | - You have to add a new entry into arb_tcp.dat (except for field 'start' |
|---|
| 73 | where a predefined entry exists) |
|---|
| 74 | |
|---|
| 75 | - Names between database using different additional fields (or no add. |
|---|
| 76 | field) are NOT compatible. To merge such databases, change this setting |
|---|
| 77 | such that both databases use equal additional fields and synchronize species IDs. |
|---|
| 78 | Otherwise you'll most likely merge the data of non-equal species, which will |
|---|
| 79 | corrupt your data! |
|---|
| 80 | |
|---|
| 81 | Please also read help for LINK{sp_IDs.hlp}. |
|---|
| 82 | |
|---|
| 83 | NOTES If you comment out the default ARB_NAME_SERVER entry in arb_tcp.dat, renaming |
|---|
| 84 | with empty 'Additional species ID field' will lead to an error. Use this to |
|---|
| 85 | avoid creating databases that use the standard NAMESERVER with no additional field. |
|---|
| 86 | |
|---|
| 87 | EXAMPLES None |
|---|
| 88 | |
|---|
| 89 | WARNINGS None |
|---|
| 90 | |
|---|
| 91 | BUGS No bugs known |
|---|