1 .. include:: images.rst
3 Using third party software with Koha
4 ====================================
9 -------------------------
11 Many libraries like to use MarcEdit for modifications or data cleanup.
12 If you'd like to do this you will need to download it at:
13 http://marcedit.reeset.net/
17 Many of the actions described in this chapter can be done in Koha
18 using :ref:`Marc Modification Templates <marc-modification-templates-label>`, but this
19 section is here for those who are used to MarcEdit.
21 .. _adding-a-prefix-to-call-numbers-label:
23 Adding a prefix to call numbers
24 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
26 When bringing data into Koha, you may want to first clean it up. One
27 common action among Koha users is to add a prefix to the call number.
35 - Go to Tools > Edit Subfield Data
39 - To prepend data the special character is: ^b To simply prepend data
40 to the beginning of a subfield, add ^b to the Field Data: textbox and
41 the data to be appended in the Replace
45 - To prepend data to the beginning of the subfield while replacing a
46 text string, add ^b[string to replace] to the Field Data textbox
47 and the data to be appended in the Replace With textbox.
49 .. _importing-excel-data-into-koha-label:
51 Importing Excel data into Koha
52 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
54 Suppose you have records of your library in excel data sheet format and
55 want them to import into Koha. But how will you do this? Koha will not
56 let you import excel records directly. Well here is a very simple
57 solution for you which will let you import your excel records in Koha
58 easily. First, we will convert excel file into Marc file and then will
61 Follow the given steps to import your excel records into Koha
63 .. _converting-from-excel-format-into-.mrk-format-label:
65 Converting from Excel format into .mrk format
66 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
68 First, we will convert excel format into .mrk format. For this we will
69 use MarcEdit. You can download it from http://marcedit.reeset.net/
71 Now open it and select Add-ins-->Delimited Text Translator.
75 Click Next when the following window appears.
79 Browse for your excel file.
83 Locate your excel file by choosing the format Excel File(\*.xls).
87 Similarly, fill all the other entries such as Output File, Excel Sheet
88 Name and check UTF-8 Encoded (if required) and Click Next.
92 Now you will be prompted for mapping the fields to recognise the fields
93 by standard marc format.
95 Suppose for Field 0 that is first column I entered Map to: 022$a( Valid
96 ISSN for the continuing resource) and then click on Apply.
102 You can customize Indicators and all other things, for more
103 information on marc21 format visit the `official library of congress
104 site <http://www.loc.gov/marc/bibliographic/>`__.
106 Similarly map all other fields and then Click on Finish.
110 And then a window will appear indicating that your Marc Text
111 File(\*.mrk) has been created.
115 Click Close and we have created a .mrk file from .xls file in this step.
116 You can view the file by double clicking on it.
118 .. _convert-.mrk-file-to-.mrc-label:
120 Convert .mrk file to .mrc
121 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
123 We will convert .mrk file that we have created in the above step into
124 raw Marc format that can be directly imported into Koha.
126 For this again open MarcEdit and Select MARC Tools.
130 Next Select MarcMaker to convert .mrk file into .mrc format.
134 Locate your input file and name your output file. Then Click Execute.
138 And it will show you the Result.
142 Click Close and now we have raw Marc records with us (.mrc file).
144 .. _import-.mrc-into-koha-label:
146 Import .mrc into Koha
147 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
149 More information on importing records into Koha can be found in the
150 ':ref:`Stage MARC Records for Import`' section of this manual.
152 Finally we will import above created .mrc file into Koha.
154 Click on Tools in your Koha staff client.
158 Next Click on Stage MARC Records for Import.
162 After this, choose your previously created .mrc file and click on
167 You can also add comment about file and finally click on Stage For
172 When the import is done, you will get a result something like this
176 Next, click on Manage staged records.
178 Here you can even change matching rules.
182 Click on Import this batch into catalog when you are done.
184 Thats it. After all the records get imported, check Status and it should
189 You can even undo the Import operation.
191 And within few minutes, we have imported around 10,000 records in Koha
195 OCLC Connexion Gateway
196 --------------------------------------------
198 Koha can be set to work with the OCLC Connextion Gateway. This allows
199 libraries to use OCLC Connexion as their cataloging tool and simply send
200 those records to Koha with a single click. The following instructions
201 will help you set up the OCLC Connexion Gateway, if you have a system
202 administrator you will want to consult with them on this process.
204 .. _setting-up-oclc-service-on-koha-label:
206 Setting up OCLC service on Koha
207 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
209 First, you'll need to create a file somewhere on your system with
210 configuration information. You could put this anywhere that is visible
211 to the account that will be running the service.
213 The file contains 11 lines. The first 6 will be about your Koha system:
217 host: The IP address of your Koha server
218 port: The port you want to use for the Connexion service. This port must be different from your SIP port, or any other service
219 koha: The full URL of your staff client
220 log: The location (full file specification) of your log for the service
221 user: The default Koha username to use for importing
222 password: The password that goes with that username
224 The remaining lines describe how to do the staging:
228 match: The name of the matching rule from your system to use
229 overlay_action: "replace", "create_new", or "ignore"-- what to do if there is a match
230 nomatch_action: "create_new" or "ignore"-- what to do if there is no match
231 item_action: "always_add","add_only_for_matches","add_only_for_new", or "ignore" -- what to do with embedded 952 item data
232 import_mode: "direct" or "stage"
234 A sample file would look like this:
240 log: /home/koha/koha-dev/var/log/connexion.log
241 koha: http://kohastaff.myuniversity.edu
242 user: koha_generic_staff
245 overlay_action: replace
246 nomatch_action: create_new
250 When choosing an 'import\_mode' if you use "direct" then the staged
251 record will be immediately imported into Koha, and should be searchable
252 after your indexes catch up. If you choose "stage", then the record
253 will be placed in a staged batch for you to later go the :ref:`Manage Staged
254 MARC Records <staged-marc-record-management-label>` tool to finish the import.
256 If you import multiple records, they'll be in the same batch, until that
257 batch is imported, then a new batch will be created.
259 In "direct" mode, each record will be in its' own batch.
261 To start the service, run the script:
265 /location/of/connexion/import/daemon/connexion_import_daemon.pl -d -c /location/of/config/file.cnf
267 .. _setting-up-your-oclc-desktop-client-label:
269 Setting up your OCLC desktop client
270 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
274 Screenshots are OCLC Connexion Client v.2.50, Koha v.3.12
276 To set up the OCLC Connexion desktop client to connect to Koha, go to
277 Tools > Options, then choose the Export tab.
281 - Click the "Create..." button to set up a new destination, then choose
282 "OCLC Gateway Export" and click OK.
284 - Enter the following information:
286 - "Host Name:" Your catalog’s appropriate IP address (from your
287 :ref:`config file above <setting-up-oclc-service-on-koha-label>`)
289 - "Port:" Your catalog's appropriate port number (from your
290 :ref:`config file above <setting-up-oclc-service-on-koha-label>`)
292 - "Login ID:" The cataloger's Koha login
294 - "Password:" The cataloger's Koha password
296 - "Notify Host Before Disconnect" = checked,
298 - "Timeout" = 100, "Retries" = 3, "Delay" = 0 (zero),
300 - "Send Local System Logon ID Password" = checked.
304 - Select "OK" when finished, and you should see your new "Gateway
305 Export" option listed (The catalog's IP address and port are blacked
306 out in the following screenshot)
310 - Click on "Record Characteristics" and make sure that the
311 bibliographic records are using MARC21, UTF-8 Unicode, and click OK
314 Record Characteristics
316 You should be ready to go! To export a record from OCLC Connexion
317 Client to Koha, just press F5 while the record is on-screen. The export
318 dialog will pop up, and you'll see Connexion attempting to talk to Koha.
319 You should get a message that the record was added or overlaid,
320 including its biblio number, and a URL that you can copy into your web
321 browser to jump straight to the record.
323 .. _using-the-oclc-connexion-gateway-label:
325 Using the OCLC Connexion Gateway
326 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
328 Records can be exported from Connexion either in a batch or one by one.
330 .. _exporting-records-one-by-one-label:
332 Exporting records one by one
333 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
335 To export bibliographic records one by one, be sure your "Batch" options
336 are correct: from the "Tools" menu, select "Options", and select the
337 "Batch" tab. In the "Perform local actions in batch" area,
338 "Bibliographic Record Export" should be unchecked
342 When ready to export, from the "Action" menu, select "Export" or use the
343 F5 key. You will see a screen similar to the following if the import is
344 successful and if the record is new to the Catalog; you may copy & paste
345 the resulting URL into your Koha catalog to see the new record.
349 If the record was overlaid, you will see a message to that effect in the
350 "OCLC Gateway Export Status" window
354 .. _exporting-records-in-a-batch-label:
356 Exporting records in a batch
357 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
359 To export bibliographic records in a batch, be sure your "Batch" options
360 are correct: from the "Tools" menu, select "Options", and select the
361 "Batch" tab. In the "Perform local actions in batch" area,
362 "Bibliographic Record Export" should be checkedOCLC
366 When a record is ready to export, from the "Action" menu, select
367 "Export" or use the F5 key, and it’s export status will be "ready."
369 When ready to export the batch, from the "Batch" menu, select "Process
370 batch" and check the appropriate "Path" and "Export" boxes
374 The export will begin, and the bib records will be exported & imported
375 into Koha one by one; you will see "OCLC Gateway Export Status" windows,
376 as above, showing you the results of each export. That window will stay
377 there until you select "Close," and then the next record’s export/import
378 will begin. The process will continue until all records in the batch are
379 completed. Then you may or may not see the Connexion Client export
380 report (depending on your Client options for that).
382 .. _items-in-oclc-label:
385 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
387 If you'd like to create your item records in OCLC you can do so by
388 addding a 952 for each item to the bib record you're cataloging. The
389 :ref:`Item/Holdings Cataloging Guide <item/holdings-record-cataloging-guide-label>` will break down what
390 subfields you can use in the 952, but at the minimum you want to have
391 subfield 2, a, b, and y on your items.
394 \\\\$2CLASSIFICATION$aHOMEBRANCHCODE$bHOLDINGBRANCHCODE$yITEMTYPECODE
396 - The subfield 2 holds the classification code. This can be ddc for
397 Dewey or lcc for Library of Congress or z for Custom. Other
398 classification sources can be found in the :ref:`Classification
399 Sources <classification-sources-label>` area in administration
401 - Subfield a is your home library and needs to be the code for your
402 home library, not the library name. You can find these codes in the
403 :ref:`Libraries <libraries-label>` administration area.
405 - Subfield b is your holding library and needs to be the code for your
406 holding library, not the library name. You can find these codes in
407 the :ref:`Libraries <libraries-label>` administration area.
409 - Subfield y is your item type code. It needs to be the code, not the
410 item type name. You can find these codes in the :ref:`Item
411 Types <item-types-label>` administration area.
413 952 \\\\$2ddc$aMAIN$bMAIN$yBOOK
415 In addition to these required fields you can enter any other subfield
416 you'd like. Most libraries will enter a call number in subfield o and a
417 barcode in subfield p as well. Review the :ref:`Item/Holdings Cataloging
418 Guide <item/holdings-record-cataloging-guide-label>` for a full list of subfields and values.
420 .. _talking-tech-label:
423 -------------------------------------------------
425 Talking Tech I-tiva is a third party, proprietary, product that
426 libraries can subscribe to. Learn more here:
427 http://www.talkingtech.com/solutions/library.
429 .. _installation-and-setup-instructions-label:
431 Installation and Setup Instructions
432 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
435 installer/data/mysql/atomicupdate/Bug-4246-Talking-Tech-itiva-phone-notifications.pl
436 to install the required data pack (new syspref, notice placeholders and
437 messaging transport preferences)
440 :ref:`TalkingTechItivaPhoneNotification`
441 syspref must be turned on.
443 If you wish to process PREOVERDUE or RESERVES messages, you'll need the
444 :ref:`EnhancedMessagingPreferences` system
445 preference turned on, and patrons to have filled in a preference for
446 receiving these notices by phone.
448 For OVERDUE messages, overdue notice triggers must be configured under
449 Koha -> Tools -> :ref:`Overdue Notice Triggers <overdue-notice/status-triggers-label>`. Either
450 branch-specific triggers or the default level triggers may be used
451 (script will select whichever is appropriate).
453 .. _sending-notices-file-label:
456 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
458 1. Add the :ref:`TalkingTech\_itiva\_outbound.pl <sending-notices-file-label>`
459 script to your crontab
461 2. Add an FTP/SFTP or other transport method to send the output file to
464 3. If you wish, archive the sent notices file in another directory after
467 Run TalkingTech\_itiva\_outbound.pl --help for more information
469 .. _receiving-results-file-label:
471 Receiving Results File
472 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
474 1. Add an FTP/SFTP or other transport method to send the Results file to
475 a known directory on your Koha server
477 2. Add the :ref:`TalkingTech\_itiva\_inbound.pl <receiving-notices-file-label>`
478 script to your crontab, aimed at that directory
480 3. If you wish, archive the results file in another directory after
483 Run TalkingTech\_itiva\_inbound.pl --help for more information