User Tools

Site Tools


pergamonmu:bison:items_text

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
pergamonmu:bison:items_text [2018/07/06 17:22]
admin
pergamonmu:bison:items_text [2018/07/07 10:25] (current)
admin
Line 3: Line 3:
 On selection of the **[Load All]** toolbar button, BISON will load the first file in the list - if the file is identified as a text type (such as .text, .csv, .tab etc.) it will display the **Data Process Window** (see below). On selection of the **[Load All]** toolbar button, BISON will load the first file in the list - if the file is identified as a text type (such as .text, .csv, .tab etc.) it will display the **Data Process Window** (see below).
  
-This window is designed to allow you to tell BISON how you want the file format interpretted,​ or to simply select one of the presets.</p>+This window is designed to allow you to tell BISON how you want the file format interpretted,​ or to simply select one of the presets.
    
 ===== Data Processor Layout ===== ===== Data Processor Layout =====
  
-The top of the window contains a number of configuration options that are mainly selected by choosing an option from a drop-down menu.+{{:​pergamonmu:​bison:​items_03.png?​direct&​200 |}}The top of the window contains a number of configuration options that are mainly selected by choosing an option from a drop-down menu.
  
 Below this is a display sample of the file being imported, along with a band showing how the fields within this file will be mapped to Pergamon fields within the database. As you change configuration options, the appearance of this sample data area will change dynamically to show how your changes are taking effect. Below this is a display sample of the file being imported, along with a band showing how the fields within this file will be mapped to Pergamon fields within the database. As you change configuration options, the appearance of this sample data area will change dynamically to show how your changes are taking effect.
Line 15: Line 15:
 ===== 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, simply select this from the list and proceed to **[Step 3]**, below.+{{ :​pergamonmu:​bison:​items_04.png?​direct&​200|}}If you know that the data file being imported is a standard file that follows one of the presets, 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 25: Line 25:
 ==== Select a Record Separator ==== ==== Select a Record Separator ====
  
-If your data file is a delimited format (such as CSV or TSV) this should be a simple task of selecting Carriage-Return,​ Newline, or combinations of them from the drop-down menu.+{{:​pergamonmu:​bison:​items_05.png?​direct&​200 |}}If your data file is a delimited format (such as CSV or TSV) this should be a simple task of selecting Carriage-Return,​ Newline, or combinations of them from the drop-down menu.
  
 Delimited files tend to use a single text line in the file to represent each individual record, but different operating systems utilise different line-termination characters (e.g. Windows vs. MacOS). Delimited files tend to use a single text line in the file to represent each individual record, but different operating systems utilise different line-termination characters (e.g. Windows vs. MacOS).
Line 49: Line 49:
 ==== Select an Internal Field Separator ==== ==== Select an Internal Field Separator ====
  
-Select the character that separates each individual component of data **within** a field. This can vary greatly. In the keyword example "​Middle Earth;​Hobbit;​Sauron",​ the internal field separator would be the semi-colon (';'​) to identify each individual keyword.+{{ :​pergamonmu:​bison:​items_06.png?​direct&​200|}}Select the character that separates each individual component of data **within** a field. This can vary greatly. In the keyword example "​Middle Earth;​Hobbit;​Sauron",​ the internal field separator would be the semi-colon (';'​) to identify each individual keyword.
  
 Several other common separator options are also provided, or enter a **[Custom Character]** if required, in the same way as above. Several other common separator options are also provided, or enter a **[Custom Character]** if required, in the same way as above.
Line 67: Line 67:
 ==== 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. **ISBN** from a book catalogue is **Serial No.** in Pergamon, as we use the same field to store ISBN, ISSN or even hardware serial numbers). 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 (e.g. **ISBN** from a book catalogue is **Serial No.** in Pergamon, as we use the same field to store ISBN, ISSN or even hardware serial numbers). 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>​**.
pergamonmu/bison/items_text.1530897763.txt.gz · Last modified: 2018/07/06 17:22 by admin