pergamonmu:bison:items_fixed
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
pergamonmu:bison:items_fixed [2018/07/07 11:23] admin |
pergamonmu:bison:items_fixed [2018/07/07 11:26] (current) admin |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Importing MARC Files and Variants ====== | + | ====== Importing Fixed Width Item Text Files ====== |
| On selection of the **[Load All]** toolbar button, BISON will load the first file in the list and display the **Data Process Window** (see below). | On selection of the **[Load All]** toolbar button, BISON will load the first file in the list and display the **Data Process Window** (see below). | ||
| Line 58: | Line 58: | ||
| ===== Step 2 - Defining Columns ===== | ===== Step 2 - Defining Columns ===== | ||
| - | Once we have broken down the file into lines correctly, and told BISON how to ignore lines that we do not want, we need to split each individual line into the separate fields. Unfortunately, unlike a delimited file, these field widths may all be different and it will need to some human intervention to configure them. | + | {{ :pergamonmu:bison:items_11.png?direct&200|}}Once we have broken down the file into lines correctly, and told BISON how to ignore lines that we do not want, we need to split each individual line into the separate fields. Unfortunately, unlike a delimited file, these field widths may all be different and it will need to some human intervention to configure them. |
| At the start, only a single column start-point is defined - as a result, each line is regarded as one long column (another name for 'field' of data). In order to split this single column up, we need to perform the following recursive procedure until we have all of the columns defined. | At the start, only a single column start-point is defined - as a result, each line is regarded as one long column (another name for 'field' of data). In order to split this single column up, we need to perform the following recursive procedure until we have all of the columns defined. | ||
| Line 82: | Line 82: | ||
| === 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 (e.g. **Accession** and **Barcode** are represented by **HID** in Pergamon). As a result, and only after we know how the fields are laid out, 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 (e.g. **Accession** and **Barcode** are represented by **HID** in Pergamon). As a result, and only after we know how the fields are laid out, 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>**. | ||
pergamonmu/bison/items_fixed.1530962595.txt.gz · Last modified: 2018/07/07 11:23 by admin
Page Tools
