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:19] 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 20: | Line 20: | ||
| ===== Step 1 - Selecting a Preset ===== | ===== Step 1 - Selecting a Preset ===== | ||
| - | If you know that the data file being imported is a standard file that follows one of the presets (or indeed, you have done this already, and have saved a preset from your earlier work), simply select this from the list and proceed to **[Step 3]**, below. | + | {{ :pergamonmu:bison:items_09.png?direct&200|}}If you know that the data file being imported is a standard file that follows one of the presets (or indeed, you have done this already, and have saved a preset from your earlier work), simply select this from the list and proceed to **[Step 3]**, below. |
| Even if you know the preset for this file, it may be prudent to view the file prior to importing, just to ensure that all of the records are importing as expected. | Even if you know the preset for this file, it may be prudent to view the file prior to importing, just to ensure that all of the records are importing as expected. | ||
| Line 37: | Line 37: | ||
| === Select to Ignore Prefixes === | === Select to Ignore Prefixes === | ||
| - | Especially in Fixed-Width files that were intended for printing, there will be lines that are totally unimportant and just contain decoration and general layout. We can tell BISON to ignore these lines by entering a few **unique** characters representing those lines. If we need to 'ignore' multiple lines, enter each ignore prefix separated by a semi-colon. | + | {{:pergamonmu:bison:items_10.png?direct&200 |}}Especially in Fixed-Width files that were intended for printing, there will be lines that are totally unimportant and just contain decoration and general layout. We can tell BISON to ignore these lines by entering a few **unique** characters representing those lines. If we need to 'ignore' multiple lines, enter each ignore prefix separated by a semi-colon. |
| For example, a report intended for a dot-matrix printer may use a line like **+----------+** to break up sections. To ignore this line, we could probably just enter **+;** as most other lines would not begin with this character, or **+-;** to make it more unique as a normal data line would probably have a space after the plus-symbol before the start of a field. | For example, a report intended for a dot-matrix printer may use a line like **+----------+** to break up sections. To ignore this line, we could probably just enter **+;** as most other lines would not begin with this character, or **+-;** to make it more unique as a normal data line would probably have a space after the plus-symbol before the start of a field. | ||
| 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.1530962369.txt.gz · Last modified: 2018/07/07 11:19 by admin
Page Tools
