This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
pergamonmu:bison:items_xlsx [2018/07/06 17:26] admin |
pergamonmu:bison:items_xlsx [2018/07/07 10:27] (current) admin |
||
---|---|---|---|
Line 17: | Line 17: | ||
==== Mapping Data to Pergamon Fields ==== | ==== Mapping Data to Pergamon Fields ==== | ||
- | It is extremely rare for the headings of data in your import file to match the actual fields in Pergamon. As a result, we need to 'map' each field to tell BISON where to put the data. | + | {{:pergamonmu:bison:items_07.png?direct&200 |}}It is extremely rare for the headings of data in your import file to match the actual fields in Pergamon. As a result, we need to 'map' each field to tell BISON where to put the data. |
Above the sample data can be found the 'Mapping Strip' containing each of the column names and what the column is mapped to - at the start, these will all read **<none>**. | Above the sample data can be found the 'Mapping Strip' containing each of the column names and what the column is mapped to - at the start, these will all read **<none>**. | ||
Line 25: | Line 25: | ||
==== Selecting an Internal Field Separator ==== | ==== Selecting an Internal Field Separator ==== | ||
- | If you have a field which itself can be broken down into smaller pieces of data (e.g. Keywords), you will need to select an **Internal Field Separator** - for example a cell containing "Middle Earth;Hobbit;Sauron" would need the semi-colon (';') selected as the Internal Field Separator. | + | {{ :pergamonmu:bison:items_06.png?direct&200|}}If you have a field which itself can be broken down into smaller pieces of data (e.g. Keywords), you will need to select an **Internal Field Separator** - for example a cell containing "Middle Earth;Hobbit;Sauron" would need the semi-colon (';') selected as the Internal Field Separator. |
===== Step 2 - Processing Your Data ===== | ===== Step 2 - Processing Your Data ===== |