| 1 | # main topics: |
|---|
| 2 | UP arb.hlp |
|---|
| 3 | UP glossary.hlp |
|---|
| 4 | |
|---|
| 5 | # sub topics: |
|---|
| 6 | #SUB subtopic.hlp |
|---|
| 7 | |
|---|
| 8 | # format described in ../help.readme |
|---|
| 9 | |
|---|
| 10 | |
|---|
| 11 | TITLE Field transfer sets |
|---|
| 12 | |
|---|
| 13 | OCCURRENCE ARB_NT/File/Import/Import from external format/FTS |
|---|
| 14 | ARB_NT/File/Export/Export to external format/FTS |
|---|
| 15 | ARB_MERGE/Transfer species/FTS |
|---|
| 16 | |
|---|
| 17 | DESCRIPTION In the "Select field transfer set" window you may |
|---|
| 18 | |
|---|
| 19 | * select or edit an existing field transfer set (FTS) |
|---|
| 20 | * create new FTS |
|---|
| 21 | * copy or rename a FTS |
|---|
| 22 | * delete FTS |
|---|
| 23 | |
|---|
| 24 | To modify a FTS and define the single transfer rules, select the |
|---|
| 25 | FTS and press the EDIT button. |
|---|
| 26 | Another window named "Define rules for field transfer" will open. |
|---|
| 27 | |
|---|
| 28 | SECTION Define rules for field transfer |
|---|
| 29 | |
|---|
| 30 | The left of the three lists shown in this windows displays |
|---|
| 31 | the rules defined in the currently selected FTS. |
|---|
| 32 | |
|---|
| 33 | Select a rule from the list to |
|---|
| 34 | * modify it (by changing the displayed properties) or to |
|---|
| 35 | * delete it (using the DEL button below the list). |
|---|
| 36 | |
|---|
| 37 | Use the ADD button to insert a new, empty rule. Then select |
|---|
| 38 | input and target fields to specify its function. |
|---|
| 39 | |
|---|
| 40 | Use the COPY and PASTE buttons to copy single or multiple |
|---|
| 41 | rules: |
|---|
| 42 | * each click to COPY copies the currently selected rule |
|---|
| 43 | onto an internal stack. |
|---|
| 44 | * each click to PASTE takes the last rule (copied onto the stack) |
|---|
| 45 | and inserts it before the currently selected rule. |
|---|
| 46 | * COPY&PASTE may be used to reuse rules (even in a different FTS). |
|---|
| 47 | |
|---|
| 48 | SECTION Transfer rule elements |
|---|
| 49 | |
|---|
| 50 | Each transfer rule consists of the following elements: |
|---|
| 51 | |
|---|
| 52 | * one or multiple input fields (shown in the middle list), |
|---|
| 53 | * a separator used when concatenating multiple fields, |
|---|
| 54 | * an optional ACI expression (see LINK{aci.hlp}) to postprocess the (concatenated) input data, |
|---|
| 55 | * the name of the target field where data shall be written to, |
|---|
| 56 | * type information for that target field and |
|---|
| 57 | * whether lossy conversion should be accepted or not. |
|---|
| 58 | |
|---|
| 59 | SECTION Field selection |
|---|
| 60 | |
|---|
| 61 | The selection list on the right side of the window |
|---|
| 62 | shows all detected fieldnames. |
|---|
| 63 | |
|---|
| 64 | Depending on where FTS are used from, it'll be filled with all fields |
|---|
| 65 | * probably imported or exported by the currently selected import or export filter, |
|---|
| 66 | * existing in the target and/or source database or |
|---|
| 67 | * defined by the current FTS. |
|---|
| 68 | |
|---|
| 69 | The selector above that list allows to select which of these fields |
|---|
| 70 | get displayed. The selectors "input", "output" and "ruleset" select the sets |
|---|
| 71 | listed at the bullets above. |
|---|
| 72 | The selectors "unread" and "unwritten" may be used to detect |
|---|
| 73 | untransferred data and contain the same as "input"/"output" when no ruleset |
|---|
| 74 | is selected, otherwise they lack all fields which are already used in a rule. |
|---|
| 75 | |
|---|
| 76 | Click on a fieldname in that list to select it; it will show |
|---|
| 77 | up in the textbox below. Alternatively you may type a name there. |
|---|
| 78 | Once a name is specified there |
|---|
| 79 | |
|---|
| 80 | * click FROM to add the current field to the list of input fields, |
|---|
| 81 | * click TO to use it as target field, |
|---|
| 82 | * hit ENTER to show only fields containing the text or |
|---|
| 83 | * click CLEAR to clear the textbox again. |
|---|
| 84 | |
|---|
| 85 | You may specify a hierarchical fieldname, e.g. "misc/value" to create |
|---|
| 86 | a field "value" inside a container "misc". |
|---|
| 87 | |
|---|
| 88 | Below the list of input fields there are some buttons to edit that list: |
|---|
| 89 | * the DROP button will remove the selected input field and |
|---|
| 90 | * the UP and DOWN buttons will move the position of the selected input field. |
|---|
| 91 | |
|---|
| 92 | SECTION Transfer undefined fields |
|---|
| 93 | |
|---|
| 94 | If the 'Transfer undefined fields?' toggle below the left list |
|---|
| 95 | is checked, all fields |
|---|
| 96 | |
|---|
| 97 | * that were not transferred by the ruleset (i.e. neighter read nor written) and |
|---|
| 98 | * that do not yet exist in target item (e.g. when used in mergetool) |
|---|
| 99 | |
|---|
| 100 | will be transferred automatically. |
|---|
| 101 | |
|---|
| 102 | This includes completely unused sub-containers: |
|---|
| 103 | if no field from inside such a container is used by the ruleset, |
|---|
| 104 | the whole container will be transferred to the target. |
|---|
| 105 | |
|---|
| 106 | NOTES Transfer rules lacking input data do not generate output data. |
|---|
| 107 | That applies to single AND multiple input fields. |
|---|
| 108 | If some input fields are missing and other exist, the concatenation is |
|---|
| 109 | performed using the existing fields only. |
|---|
| 110 | |
|---|
| 111 | In most cases the order of the rules in a FTS does not matter. |
|---|
| 112 | If you like to change the order you may either use COPY, DEL + PASTE |
|---|
| 113 | buttons to move rules or use an external editor on the .fts file. |
|---|
| 114 | |
|---|
| 115 | EXAMPLES See LINK{arb_import.hlp}, LINK{arb_export.hlp} or LINK{mg_species.hlp}. |
|---|
| 116 | |
|---|
| 117 | WARNINGS Changes to FTS are instantly applied to the .fts file. |
|---|
| 118 | Undo functionality is not available here. |
|---|
| 119 | |
|---|
| 120 | Consider to backup your files frequently (always a good idea) or |
|---|
| 121 | create a backup-copy of your .fts file before you edit it. |
|---|
| 122 | |
|---|
| 123 | BUGS No bugs known |
|---|