Příloha M. OCLC Connexion Gateway

Obsah

M.1. Setting up OCLC service on Koha
M.2. Setting up your OCLC desktop client
M.3. Using the OCLC Connexion Gateway
M.3.1. Exporting records one by one
M.3.2. Exporting records in a batch

Koha can be set to work with the OCLC Connextion Gateway. This allows libraries to use OCLC Connexion as their cataloging tool and simply send those records to Koha with a single click. The following instructions will help you set up the OCLC Connexion Gateway, if you have a system administrator you will want to consult with them on this process.

M.1. Setting up OCLC service on Koha

D. Ruth Bavousett

ByWater Solutions

Sestavil

Nicole C. Engard

2012

First, you'll need to create a file somewhere on your system with configuration information.  You could put this anywhere that is visible to the account that will be running the service.

The file contains 11 lines. The first 6 will be about your Koha system:

host:  The IP address of your Koha server 
port:  The port you want to use for the Connexion service. This port must be different from your SIP port, or any other service 
koha:  The full URL of your staff client 
log:  The location (full file specification) of your log for the service 
user:  The default Koha username to use for importing 
password:  The password that goes with that username

The remaining lines describe how to do the staging:

match: The name of the matching rule from your system to use 
overlay_action: "replace", "create_new", or "ignore"-- what to do if there is a match 
nomatch_action: "create_new" or "ignore"-- what to do if there is no match 
item_action: "always_add","add_only_for_matches","add_only_for_new", or "ignore" -- what to do with embedded 952 item data 
import_mode: "direct" or "stage"

A sample file would look like this:

host: 1.2.3.4
port: 8000
log: /home/koha/koha-dev/var/log/connexion.log
koha: http://kohastaff.myuniversity.edu
user: koha_generic_staff
password: password
match: 001
overlay_action: replace
nomatch_action: create_new
item_action: ignore
import_mode: direct

When choosing an 'import_mode' if you use "direct" then the staged record will be immediately imported into Koha, and should be searchable after your indexes catch up.  If you choose "stage", then the record will be placed in a staged batch for you to later go the Managed Staged MARC Records tool to finish the import.

If you import multiple records, they'll be in the same batch, until that batch is imported, then a new batch will be created.

In "direct" mode, each record will be in its' own batch.

To start the service, run the script:

/location/of/connexion/import/daemon/connexion_import_daemon.pl -d -c /location/of/config/file.cnf