pergamonmu:bison:items_marc
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_marc [2018/07/06 17:34] admin |
pergamonmu:bison:items_marc [2018/07/07 11:42] (current) admin |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| ===== Item MARC Import Process ===== | ===== Item MARC Import Process ===== | ||
| - | MARC is a bibliographic format for transfering information about catalogue items between computer systems. It should be noted that MARC is now a very old concept, and while the 'current' format is now MARC21, the very nature of the format was designed for use with sequentially read records from <i>tape</i> drives. It is still used however, simply because so many software applications understand it and it has a comprehensive definitions of fields. | + | MARC is a bibliographic format for transfering information about catalogue items between computer systems. It should be noted that MARC is now a very old concept, and while the 'current' format is now MARC21, the very nature of the format was designed for use with sequentially read records from //tape// drives. It is still used however, simply because so many software applications understand it and it has a comprehensive definitions of fields. |
| The downside of MARC's age, is that different proprietary users (e.g. book suppliers, LMS suppliers etc.) have gradualy introduced their own minor variations on how a MARC file is written, which were never designed to be or a part of the MARC standards. Many different minor variants of files may therefore be sent to you by different suppliers. | The downside of MARC's age, is that different proprietary users (e.g. book suppliers, LMS suppliers etc.) have gradualy introduced their own minor variations on how a MARC file is written, which were never designed to be or a part of the MARC standards. Many different minor variants of files may therefore be sent to you by different suppliers. | ||
| Line 19: | Line 19: | ||
| ==== Process the MARC file ==== | ==== Process the MARC file ==== | ||
| - | This is the easy bit! | + | {{ :pergamonmu:bison:items_12.png?direct&200|}}This is the easy bit! |
| BISON already knows where the file is at this point, so all you need to do is make sure that you are on the **[Load MARC]** tab and select **[Process]**. | BISON already knows where the file is at this point, so all you need to do is make sure that you are on the **[Load MARC]** tab and select **[Process]**. | ||
| Line 25: | Line 25: | ||
| BISON will open and load the MARC data and after a short while you should see a long list of **RCN** (Record Control Numbers) appear in the window - these are the unique ID's of the records in the file. | BISON will open and load the MARC data and after a short while you should see a long list of **RCN** (Record Control Numbers) appear in the window - these are the unique ID's of the records in the file. | ||
| - | If the RCN's appear 'odd', such as different types of information on each line or otherwise not consistent, do not try to process the file any further. Select **[Cancel]** and contact your Support so that they can take a look at the file for you. A good set of RCNs will look like a long list of ISBN13 numbers, or at the very least be obviously **consistent on every line**. | + | {{:pergamonmu:bison:items_13.png?direct&200 |}}If the RCN's appear 'odd', such as different types of information on each line or otherwise not consistent, do not try to process the file any further. Select **[Cancel]** and contact your Support so that they can take a look at the file for you. A good set of RCNs will look like a long list of ISBN13 numbers, or at the very least be obviously **consistent on every line**. |
| + | |||
| + | **Note:** In computing terms, updating the screen is one of the slowest jobs that can be done. As a result, individual computers may not update the screen with each RCN as it is processed, so you will not see a streaming list building in front of you. Instead, there may be a short period of inactivity, followed by all fo the RCN's bursting onto the screen in one go. This is completely normal and dependant upon the individual workstation, and does not indicate a problem with import. | ||
| ==== Mapping the Fields ==== | ==== Mapping the Fields ==== | ||
| - | Select the **[Map Fields]** tab. At the top of this tab you will be able to select an existing Preset, modify, create and delete new presets. | + | {{ :pergamonmu:bison:items_14.png?direct&200|}}Select the **[Map Fields]** tab. At the top of this tab you will be able to select an existing Preset, modify, create and delete new presets. |
| The bulk of the tab contains a list of all of the unique MARC Tags that were found in your file along with the list of fields that they match in Pergamon (note that this is a composite of the entire file - any individual tag may not appear in **every** record to be imported). At the start they will all be unmapped, so begin by selecting **[Default Mapping]** from the list of available presets. | The bulk of the tab contains a list of all of the unique MARC Tags that were found in your file along with the list of fields that they match in Pergamon (note that this is a composite of the entire file - any individual tag may not appear in **every** record to be imported). At the start they will all be unmapped, so begin by selecting **[Default Mapping]** from the list of available presets. | ||
| - | Any line which has a gap in the **Pergamon** column, or where you believe that the mapping is wrong for this file, can be altered by **right-clicking** with the mouse in that field. Select the most appropriate mapping from the menu presented (an explanation of the various fields can be found at the bottom of this page). | + | {{:pergamonmu:bison:items_15.png?direct&200 |}}Any line which has a gap in the **Pergamon** column, or where you believe that the mapping is wrong for this file, can be altered by **right-clicking** with the mouse in that field. Select the most appropriate mapping from the menu presented (an explanation of the various fields can be found at the bottom of this page). |
| Once you believe that your mappings are correct, use the **[Save As]** button to save those choices as a new preset for future use. | Once you believe that your mappings are correct, use the **[Save As]** button to save those choices as a new preset for future use. | ||
| - | Do not worry if none of your fields seem to contain a usable HID (Accession Number) - few book suppliers provide them, as they really need to be matched to your own printed barcodes. If no HID can be found in the MARC file, Pergamon will generate one for you. | + | Do not worry if none of your fields seem to contain a usable HID (Accession Number) - few book suppliers provide them (unless they have also barcoded them for you at source), as they really need to be matched to your own printed barcodes. If no HID can be found in the MARC file, Pergamon will generate one for you. |
| **Note:** If you have pre-printed barcodes that do not fit a specific order and need to **manually** match books to barcodes, it is best to select the **batch HID** option rather than the **generate next item** system - this will allow you to edit unique book barcodes without creating books that are out-of-sequence in your wider catalogue stock. | **Note:** If you have pre-printed barcodes that do not fit a specific order and need to **manually** match books to barcodes, it is best to select the **batch HID** option rather than the **generate next item** system - this will allow you to edit unique book barcodes without creating books that are out-of-sequence in your wider catalogue stock. | ||
| Line 50: | Line 52: | ||
| Items imported into a package, new or existing, are automatically **received** and made active within the catalogue for the purposes of circulation. | Items imported into a package, new or existing, are automatically **received** and made active within the catalogue for the purposes of circulation. | ||
| + | |||
| + | ---- | ||
| ==== Understanding the MARC / Pergamon field mappings ==== | ==== Understanding the MARC / Pergamon field mappings ==== | ||
| Line 107: | Line 111: | ||
| * Vendor | * Vendor | ||
| - | Many of these fields mean effectively the same thing - in the files provided to you from your book suppliers for example, Author, Personal Name, Title Statement 1 and Title Statement 2 <i>almost</i> translate to being the same thing and might as well be regarded as such(do not take this as gospel - in practice for example, 1 and 2 usually refer to an author and an illustrator). | + | Many of these fields mean effectively the same thing - in the files provided to you from your book suppliers for example, Author, Personal Name, Title Statement 1 and Title Statement 2 //almost// translate to being the same thing and might as well be regarded as such(do not take this as gospel - in practice for example, 1 and 2 usually refer to an author and an illustrator). |
| You may never have heard of many of these, but do not worry about it - BISON has, and knows how to intelligently combine them, take one as preference over another and even disregard some of them as redundant. All you need to do it tell BISON where to get the data from. | You may never have heard of many of these, but do not worry about it - BISON has, and knows how to intelligently combine them, take one as preference over another and even disregard some of them as redundant. All you need to do it tell BISON where to get the data from. | ||
| Line 153: | Line 157: | ||
| * 971.a - Vendor | * 971.a - Vendor | ||
| - | **Note** that not all tags supported are contained within this list - this is mainly because many tags are used in different ways by different suppliers in a varied fashion, which makes their inclusion in the default mappings redundant. If you encounter tags in your MARC files that have a specific meaning, select the correct mapping and save the new mappings as a local preset. | + | **Note** that not all tags supported are contained within this list - this is mainly because many tags are used in different ways by different suppliers in a varied fashion, which makes their inclusion in the default mappings redundant. Your book supplier for example, or an SLS providing a resource box, might have used a tag in the 900.x range, which is quite flexible, to store their HID (Accession number, or barcode). If you encounter tags in your MARC files that have a specific meaning, select the correct mapping and save the new mappings as a local preset. |
pergamonmu/bison/items_marc.1530898477.txt.gz · Last modified: 2018/07/06 17:34 by admin
Page Tools
