\|{ 088a }\|
+
+Configuring Receipt Printers
+============================
+
+The following instructions are for specific receipt printers, but can
+probably be used to help with setup of other brands as well.
+
+`For Epson TM-T88III (3) & TM-T88IV (4) Printers <#epsonprinters>`__
+--------------------------------------------------------------------
+
+`In the Print Driver <#epsonprintdriver>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+For these instructions, we are using version 5,0,3,0 of the Epson
+TM-T88III print driver; the EPSON TM-T88IV version is ReceiptE4.
+Register at the `EpsonExpert Technical Resource Center
+website `__ to gain access to the
+drivers; go to Technical Resources, then choose the printer model from
+the Printers drop-down list.
+
+Click Start > Printers and Faxes > Right click the receipt printer >
+Properties:
+
+- Advanced Tab, click Printing Defaults button
+
+- Layout Tab: Paper size: Roll Paper 80 x 297mm
+
+- TM-T88III: Layout Tab: Check Reduce Printing and Fit to Printable
+ Width
+
+- TM-T88IV: Check Reduced Size Print; Click OK on the popup window that
+ appears. Fit to Printable Width should be automatically selected.
+
+- OK your way out of there.
+
+`In Firefox <#epsonfirefox>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Under File > Page Setup:
+
+- Shrink to fit page on Format & Options tab
+
+- 0,0,0,0 for Margins on Margins & Header/Footer Tab. This makes the
+ receipts use all available space on the paper roll.
+
+- Set all Headers/Footers to -blank-. This removes all of the gunk you
+ might normally find on a print from Firefox, such as the URL, number
+ of pages, etc.
+
+- Click OK
+
+Set the default printer settings in Firefox so you don't see a "Print"
+dialog:
+
+- Go to File > Print
+
+- Set the Printer to the receipt printer.
+
+- Click the Advanced (or Properties) button
+
+- Layout Tab: Paper size: Roll Paper 80 x 297mm
+
+- TM-T88III: Layout Tab: Check Reduce Printing and Fit to Printable
+ Width
+
+- TM-T88IV: Check Reduced Size Print; click OK on the popup window that
+ appears. Fit to Printable Width should be automatically selected.
+
+- OK your way out, go ahead and print whatever page you are on.
+
+- Type about:config, in the address bar. Click "I'll be careful, I
+ promise!" on the warning message.
+
+- Type, print.always in Filter.
+
+- Look for print.always\_print\_silent.
+
+ - If the preference is there then set the value to true.
+
+- If the preference is not there (and it shouldn't be in most browsers)
+ you have to add the preference.
+
+ - Right click the preference area and select New > Boolean
+
+ - Type print.always\_print\_silent in the dialog box and set the
+ value to True. This sets the print settings in Firefox to always
+ use the same settings and print without showing a dialog box.
+
+ **Warning**
+
+ Setting the print.always\_print\_silent setting in about:config
+ DISABLES the ability to choose a printer in Firefox.
+
+`For Epson TM-T88II (2) Printers <#epson2>`__
+---------------------------------------------
+
+Register at the `EpsonExpert Technical Resource Center
+website `__ to gain access to the
+drivers; go to Technical Resources, then choose the printer model from
+the Printers drop-down list.
+
+`In Firefox <#epson2firefox>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Under File > Page Setup:
+
+- Shrink to fit page on Format & Options tab
+
+- 0,0,0,0 for Margins on Margins & Header/Footer Tab. This makes the
+ receipts use all available space on the paper roll.
+
+- Set all Headers/Footers to -blank-. This removes all of the gunk you
+ might normally find on a print from Firefox, such as the URL, number
+ of pages, etc.
+
+- Click OK
+
+Set the default printer settings in Firefox so you don't see a "Print"
+dialog:
+
+- Go to File > Print
+
+- Set the Printer to the receipt printer.
+
+- Print whatever page you are on.
+
+- Type about:config, in the address bar. Click "I'll be careful, I
+ promise!" on the warning message.
+
+- Type, print.always in Filter.
+
+- Look for, print.always\_print\_silent.
+
+ - If the preference is there then set the value to true.
+
+- If the preference is not there (and it shouldn't be in most browsers)
+ you have to add the preference.
+
+ - Right click the preference area and select New > Boolean
+
+ - Type, print.always\_print\_silent in the dialog box and set the
+ value to True. This sets the print settings in Firefox to always
+ use the same settings and print without showing a dialog box.
+
+ **Warning**
+
+ Setting the print.always\_print\_silent setting in about:config
+ DISABLES the ability to choose a printer in Firefox.
+
+`For Star SP542 Printers <#starprinter>`__
+------------------------------------------
+
+`Installing the Printer <#installstarprinter>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+While the following comments are based on the Star SP542 receipt
+printer, they probably apply to all printers in the SP5xx series.
+
+The Star SP542 receipt printer works well with Koha and **Firefox on
+Windows XP SP3**. This printer, with either the parallel or USB
+interface, is fairly easy to install and configure. You will need the
+following executable file which is available from numerous places on the
+Internet:
+
+linemode\_2k-xp\_20030205.exe
+
+This executable actually does all of the installation; you will not need
+to use the Microsoft Windows "Add Printer" program. We recommend that
+when installing, the option for the software monitor not be selected; we
+have experienced significant pauses and delays in printing with it.
+Instead, simply choose to install the receipt printer without the
+monitor.
+
+Additionally, the install program may not put the printer on the correct
+port, especially if using the USB interface. This is easily corrected by
+going to "Start -> Printers and Faxes -> Properties for the SP542
+printer -> Ports", then check the appropriate port.
+
+A reboot may be required, even if not indicated by the installation
+software or the operating system.
+
+**Windows 7** users should refer to this page:
+http://www.starmicronics.com/supports/win7.aspx.
+
+`Configuring Firefox to Print to Receipt Printer <#firefoxreceipt>`__
+---------------------------------------------------------------------
+
+- Open File > Page Setup
+
+- Make all the headers and footers blank
+
+- Set the margins to 0 (zero)
+
+- In the address bar of Firefox, type about:config
+
+- Search for print.always\_print\_silent and double click it
+
+- Change it from false to true
+
+ - This lets you skip the Print pop up box that comes up, as well as
+ skipping the step where you have to click OK, automatically
+ printing the right sized slip.
+
+- If print.always\_print\_silent does not come up
+
+ - Right click on a blank area of the preference window
+
+ - Select new > Boolean
+
+ - Enter "print.always\_print\_silent" as the name (without quotes)
+
+ - Click OK
+
+ - Select true for the value
+
+- You may also want to check what is listed for print.print\_printer
+
+ - You may have to choose Generic/Text Only (or whatever your receipt
+ printer might be named)
+
+Notice & Slips Guides
+=====================
+
+`Field Guide for Notices & Slips <#noticesfieldguide>`__
+--------------------------------------------------------
+
+This guide will break down the notices and slips information in 3 ways.
+First it will tell you what file generates the notice, then how you will
+present the item info in that notice and finally if the notice can be
+branch specific or not.
+
++---------------------+----------------------------+---------------------------------------+--------------------------+
+| Letter Code | Used In | Detail tag | Can be branch specific |
++=====================+============================+=======================================+==========================+
+| DUE | advance\_notices.pl | <> | No |
++---------------------+----------------------------+---------------------------------------+--------------------------+
+| DUEDGST | advance\_notices.pl | <> | No |
++---------------------+----------------------------+---------------------------------------+--------------------------+
+| PREDUE | advance\_notices.pl | <> | No |
++---------------------+----------------------------+---------------------------------------+--------------------------+
+| PREDUEDGST | advance\_notices.pl | <> | No |
++---------------------+----------------------------+---------------------------------------+--------------------------+
+| ODUE\* | overdue\_notices.pl | <> or | Yes |
++---------------------+----------------------------+---------------------------------------+--------------------------+
+| CHECKOUT | C4/Circulation.pm | N/A | Yes |
++---------------------+----------------------------+---------------------------------------+--------------------------+
+| RENEWAL | C4/Circulation.pm | N/A | Yes |
++---------------------+----------------------------+---------------------------------------+--------------------------+
+| TRANSFERSLIP | C4/Circulation.pm | N/A | Yes |
++---------------------+----------------------------+---------------------------------------+--------------------------+
+| ISSUESLIP | C4/Members.pm | | Yes |
+| | | | |
+| | | | |
+| | | | |
+| | | | |
++---------------------+----------------------------+---------------------------------------+--------------------------+
+| ISSUEQSLIP | C4/Members.pm | | Yes |
++---------------------+----------------------------+---------------------------------------+--------------------------+
+| HOLDPLACED | C4/Reserves.pm | N/A | Yes |
++---------------------+----------------------------+---------------------------------------+--------------------------+
+| RESERVESLIP | C4/Reserves.pm | N/A | Yes |
++---------------------+----------------------------+---------------------------------------+--------------------------+
+| ASKED | C4/Suggestions.pm | N/A | Yes |
++---------------------+----------------------------+---------------------------------------+--------------------------+
+| CHECKED | C4/Suggestions.pm | N/A | Yes |
++---------------------+----------------------------+---------------------------------------+--------------------------+
+| ACCEPTED | C4/Suggestions.pm | N/A | Yes |
++---------------------+----------------------------+---------------------------------------+--------------------------+
+| REJECTED | C4/Suggestions.pm | N/A | Yes |
++---------------------+----------------------------+---------------------------------------+--------------------------+
+| OPAC\_REG\_VERIFY | opac/opac-memberentry.pl | N/A | No |
++---------------------+----------------------------+---------------------------------------+--------------------------+
+
+Example Notice
+==============
+
+Nicole Engard
+
+410 Library Rd.
+
+Philadelphia, PA 19107
+
+Dear Nicole Engard (23529000035726),
+
+According to our records, at the time of this notice, you have items
+that are overdue. Please return or renew them as soon as possible to
+avoid increasing late fines.
+
+If you have registered a password with the library, you may use it with
+your library card number to renew online.
+
+If you believe you have returned the items below please call at and
+library staff will be happy to help resolve the issue.
+
+The following item(s) are currently overdue:
+
+07/08/2008 Creating drug-free schools and communities : 502326000054
+Fox, C. Lynn.
+
+06/27/2008 Eating fractions / 502326000022 McMillan, Bruce.
+
+Sincerely, Library Staff
+
+Sample Serials
+==============
+
+`Reader's Digest (0034-0375) <#readersdigestsample>`__
+------------------------------------------------------
+
+- Published 12 times a year (monthly)
+
+- The Volume number changes every 6 months and the numbers continues on
+ (requires an advanced pattern).
+
+ Sample Reader's Digest Subscription
+ |image1069|
+
+`People Weekly (1076-0091) <#peoplesample>`__
+---------------------------------------------
+
+- Published weekly
+
+ - The website says "on Saturday except the first week of August,
+ Thanksgiving week, the first and last weeks of the year" but this
+ does not match the pattern for 2007 or 2008
+
+- In the Jul-Dec there are 26 issues
+
+- In the Jan-Jun there are 25 issues (no issue for the first week of
+ January)
+
+Since the irregularity on the first # 26 does not skip a week, this
+would be set up as to roll over on issue 25. The 26th issue in the
+second half of the year would have to be received as a supplemental.
+
+The irregularity check will complain that 52 issues were expected, but
+25 entered. The current irregularity check can only check that the first
+position of the numbering pattern matches the expected issue count of
+the periodicity. But we do need to trigger the rollover on the volume,
+so we need to define the last two weeks of the year as irregularities.
+So we receive 50 issues the first 50 weeks, then one supplemental issue
+in week 51, which we have to define the enumeration for, then the next
+predicted issue will be the following year's first week.
+
+`Et-Mol <#hebrewserialsample>`__
+--------------------------------
+
+This journal is published with the following rules:
+
+- 6 issues a year (every 2 months)
+
+- year changes every 6 issues
+
+- we start in 2011
+
+- the issue number goes up indefinitely
+
+- starting from issue 215
+
+The planning would look like this:
+
+Sample for this Hebrew Journal
+|image1070|
+
+`Backpacker (0277-867X) <#backpackerserial>`__
+----------------------------------------------
+
+Published 9 times a year irregularly. The issues continues while the
+volume and number rolls over every 9 issues. If you're holding Volume
+41, Number 3, Issue 302 in your hand the prediction would look like
+this:
+
+Backpacker numbering pattern
+|image1071|
+
+And the received issues would number like this:
+
+v. 41, no. 3, iss. 302 Â
+
+v. 41, no. 4, iss. 303
+
+v. 41, no. 5, iss. 304
+
+v. 41, no. 6, iss. 305
+
+v. 41, no. 7, iss. 306
+
+v. 41, no. 8, iss. 307
+
+v. 41, no. 9, iss. 308
+
+v. 42, no. 1, iss. 309
+
+v. 42, no. 2, iss. 310
+
+v. 42, no. 3, iss. 311
+
+v. 42, no. 4, iss. 312
+
+`Keats-Shelley Journal (0453-4387) <#keatsserial>`__
+----------------------------------------------------
+
+This journal is published once per year in July. The numbering follows
+this pattern: Â
+
+- Vol. 61 2013
+
+- Vol. 62 2014
+
+- Vol. 63 2015
+
+Setup should look like this (if you're starting in July 2014):
+
+Serial planning
+|image1072|
+
+`Computers in Libraries (1041-7915) <#cilserial>`__
+---------------------------------------------------
+
+Computers in Libraries is published ten times per year (monthly with
+January/February and July/August combined issues).
+
+Subscription details
+|image1073|
+
+Serial Planning
+|image1074|
+
+Received details
+|image1075|
+
+Sample List & Cart Emails
+=========================
+
+`Example Email from List <#examplelistemail>`__
+-----------------------------------------------
+
+Below is an example of an email from a list in Koha.
+
+::
+
+ Hi,
+
+ Here is your list called If You Like Jodi Picoult, sent from our online catalog.
+
+ Please note that the attached file is a MARC bibliographic records file
+ which can be imported into a Personal Bibliographic Software like EndNote,
+ Reference Manager or ProCite.
+ ---------------------------------------------
+
+ Home safe : a novel /
+
+ by Berg, Elizabeth.
+
+ Published by: Random House,, 260 p. ;, 25 cm.
+ Copyright year: 2009
+ LCCN: 2008049247
+ In the online catalog:
+ http://MYCATALOG/cgi-bin/koha/opac-detail.pl?biblionumber=12113
+ Items :
+ North Branch FIC (FIC Ber) TVSN500088894O
+ Main Library FIC (FIC Boh) TVSN5000921548
+ South Branch FIC (FIC Boh) TVSN500092156A
+ West Branch FIC (FIC Boh) TVSN5000921559
+
+ ---------------------------------------------
+
+ Half a heart /
+
+ by Brown, Rosellen.
+
+ Published by: Farrar, Straus, and Giroux,, 402 p. ;, 24 cm.
+ Copyright year: 2000
+ LCCN: 00022926
+ In the online catalog:
+ http://MYCATALOG/cgi-bin/koha/opac-detail.pl?biblionumber=12501
+ Items :
+ East Branch (813/.54)
+ South Branch FIC (FIC Bro) TVSN5000451333
+
+`Example Email from Cart <#examplecartemail>`__
+-----------------------------------------------
+
+Below is a sample of what an email from the Cart in Koha will look like:
+
+::
+
+ Hi,
+
+ Joaquin D'Planque sent you a cart from our online catalog.
+
+ Please note that the attached file is a MARC bibliographic records
+ file which can be imported into personal bibliographic software like
+ EndNote, Reference Manager or ProCite.
+
+ ---------------------------------------------------------------------
+
+
+ 1. Book /
+ Author(s): Brookfield, Karen. ;
+ Published by: Knopf : | Distributed by Random House, , 63 p. : ,
+ 29 cm.
+ Copyright year: 1993
+ Notes : Includes index.
+ LCCN: 93018833 /AC
+
+ In online catalog:
+ http://MYCATALOG/cgi-bin/koha/opac-detail.pl?biblionumber=31644
+
+ Items:
+
+ * East Branch (JNF 002 Bro) TVSN500017618A
+
+ -----------------------------------------------------------------
+
+ 2. The 1965 World book year book :
+
+ Published by: Field Enterprises Educational Corp., , 628 p. : , 26
+ cm.
+ Copyright year: 1965
+ Notes : Includes index. | Spine title: Year book, 1965. | Cover
+ title: The World book year book, 1965.
+ URL:
+ http://www.archive.org/details/1965worldbookyea00chic%20%7C%20http://www.openlibrary.org/books/OL24199089M
+
+ In online catalog:
+ http://MYCATALOG/cgi-bin/koha/opac-detail.pl?biblionumber=88666
+
+ -----------------------------------------------------------------
+
+Using Koha as a Content Management System (CMS)
+===============================================
+
+`Setup <#kohacmssetup>`__
+-------------------------
+
+These are instructions for taking a default install of Koha and allowing
+it to function as a little content management system. This will allow a
+library to publish an arbitrary number of pages based on a template.
+This example uses the template for the main opac page, but you could
+just as well use any template you wish with a bit more editing. This may
+be appropriate if you have a small library, want to allow librarians to
+easily add pages, and do not want to support a complete CMS.
+
+- Copy /usr/share/koha/opac/cgi-bin/opac/opac-main.pl to
+ /usr/share/koha/opac/cgi-bin/opac/pages.pl (in the same directory)
+
+- Edit pages.pl in an editor
+
+- At approximately line 33 change this code:
+
+ ::
+
+ template_name => "opac-main.tmpl",
+
+- To this code:
+
+ ::
+
+ template_name => "pages.tmpl",
+
+- At approximately line 62 after this code:
+
+ ::
+
+ $template->param(
+ koha_news => $all_koha_news,
+ koha_news_count => $koha_news_count,
+ display_daily_quote => C4::Context->preference('QuoteOfTheDay'),
+ daily_quote => $quote,
+ );
+
+- Add these lines:
+
+ ::
+
+ my $page = "page_" . $input->param('p'); # go for "p" value in URL and do the concatenation
+ my $preference = C4::Context->preference($page); # Go for preference
+ $template->{VARS}->{'page_test'} = $preference; # pass variable to template pages.tt
+
+- Note pages.pl file must have Webserver user execution permissions,
+ you can use `chmod `__ command if
+ you are actually logged in as such user:
+
+ ::
+
+ $chmod 755 pages.pl
+
+- In the browser go to Home > Administration > System Preferences >
+ Local Use and add a New Preference called "page\_test"
+
+- Fill it out as so
+
+ - Explanation: test page for pages tiny cms
+
+ - Variable: page\_test
+
+ - Value: Lorem ipsum
+
+ - Click the TextArea link (or enter "TextArea" into the input field
+ below it)
+
+ - variable options (last field): 80\|50
+
+- In a browser go to http://youraddress/cgi-bin/koha/pages.pl?p=test
+ The page should come up with the words "Lorem ipsum" in the main
+ content area of the page. (replace "youraddress" with localhost,
+ 127.0.0.1, or your domain name depending on how you have Apache set
+ up.)
+
+- To add more pages simply create a system preference where the title
+ begins with "page\_" followed by any arbitrary letters. You can add
+ any markup you want as the value of the field. Reference the new page
+ by changing the value of the "p" parameter in the URL.
+
+To learn more visit the Koha wiki page on this topic:
+http://wiki.koha-community.org/wiki/Koha_as_a_CMS
+
+`Editing the pages template <#kohacmstmpl>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The file to create / edit for the pages template will depend on your
+`opacthemes <#opacthemes>`__ system preference setting
+
+`Editing 'bootstrap' theme template (current) <#kohacmstmplboot>`__
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+- Copy
+ /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/en/modules/opac-main.tt
+ to
+ /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/en/modules/pages.tt
+
+- Edit
+ /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/en/modules/pages.tt
+
+- At approximately line 61, change this:
+
+ ::
+
+ [% IF ( OpacMainUserBlock ) %]
[% OpacMainUserBlock %]
[% END %]
+
+- To this:
+
+ ::
+
+ [% IF ( page_test ) %]
[% page_test %]
[% END %]
+
+Remark: You may wish to disable your News block of these CMS style pages
+e.g. when you do not want it displayed on the CMS style pages or where
+the News block is long enough that it actually makes the 'page\_test'
+include scroll outside the default viewport dimensions. In that case,
+remove the following code from your pages.tt template.
+
+::
+
+ [% IF ( koha_news_count ) %]
+
+
+ [% FOREACH koha_new IN koha_news %]
+
[% koha_new.title %]
+
[% koha_new.new %]
+
(published on [% koha_new.newdate %])
+ [% END %]
+
+
+ [% END %]
+
+
+`Troubleshooting <#kohacmstrouble>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+If you have problems check file permissions on pages.pl and pages.tmpl.
+They should have the same user and group as other Koha files like
+opac-main.pl.
+
+`Bonus Points <#kohacmsbonus>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Instead of using the address
+http://youraddress/cgi-bin/koha/pages.pl?p=test you can shorten it to
+http://youraddress/pages.pl?p=test Just open up
+/etc/koha/koha-httpd.conf and add the follow at about line 13:
+
+::
+
+ ScriptAlias /pages.pl "/usr/share/koha/opac/cgi-bin/opac/pages.pl"
+
+Then restart Apache.
+
+`Usage <#kohacmsusage>`__
+-------------------------
+
+After setting up Koha as a CMS you can create new pages following these
+instructions:
+
+`Adding Pages <#kohacmspages>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+To add a new page you need to add a system preference under Local Use.
+
+- Get there: More > Administration > Global System Preferences > Local
+ Use
+
+- Click 'New Preference'
+
+- Enter in a description in the Explanation field
+
+- Enter a value that starts with 'page\_' in the Variable field
+
+- Enter starting HTML in the Value field
+
+ Add a new preference
+ |image1076|
+
+- Set the Variable Type to Textarea
+
+- Set the Variable options to something like 20\|20 for 20 rows and 20
+ columns
+
+ Settings for the new preference
+ |image1077|
+
+`Viewing your page <#kohacmsview>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+You can view your new page at
+http://YOUR-OPAC/cgi-bin/koha/pages.pl?p=PAGENAME where PAGENAME is the
+part you entered after 'page\_' in the Variable field.
+
+`Example <#kohacmsexpage>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+This process can be used to create recommended reading lists within
+Koha. So once the code changes have been made per the instructions on
+'Koha as a CMS' you go through the 'Adding a New Page' instructions
+above to great a page for 'Recommended Reading Lists'
+
+Create page by modifying a system preference
+|image1078|
+
+Next we need to create pages for our various classes (or categories). To
+do this, return to the 'Adding a New Page' section and create a
+preference for the first class.
+
+Add a new sys pref for another page
+|image1079|
+
+Next you'll want to link your first page to your new second page, go to
+the page\_recommend preference and click 'Edit.' Now you want to edit
+the HTML to include a link to your newest page:
+
+Edit original preference to add new page
+|image1080|
+
+`Live Examples <#examplecms>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+- The Crawford Library at Dallas Christian College is using this method
+ for their recommended reading lists: http://opac.dallas.edu/
+
+Resetting the Koha Database
+===========================
+
+These notes on how to reset the database for Koha were derived from the
+following email thread:
+http://lists.koha-community.org/pipermail/koha-devel/2009-January/008939.html
+and http://lists.katipo.co.nz/public/koha/2014-June/039701.html
+
+Resetting the database may be useful if you install Koha with the sample
+data, and then wish to use real data without reinstalling the software.
+
+`Delete sample data from Tables <#deletetables>`__
+--------------------------------------------------
+
+Use your preferred MySQL client to
+`delete `__ the
+following tables:
+
+- bibio
+
+- biblioitems
+
+- items
+
+- auth\_header
+
+- sessions
+
+- zebraqueue
+
+You may need to disable foreign key checks to delete data from same
+tables. For instructions follow this thread:
+https://lists.katipo.co.nz/pipermail/koha/2013-July/036853.html.
+
+`Reset the Zebra Index <#resetzebra>`__
+---------------------------------------
+
+Run the following commands to reset the authorities and biblios Zebra
+indices.
+
+::
+
+ $ zebraidx -c /etc/koha/zebradb/zebra-authorities-dom.cfg -g iso2709 -d authorities init
+ $ zebraidx -c /etc/koha/zebradb/zebra-biblios.cfg -g iso2709 -d biblios init
+
+If you are running a package install then you'll want to run the
+following commands to reset the authorities and biblios Zebra indices
+instead:
+
+::
+
+ $ sudo zebraidx -c /etc/koha/sites/YOURLIBRARY/zebra-authorities-dom.cfg  -g iso2709 -d authorities init
+ $ sudo zebraidx -c /etc/koha/sites/YOURLIBRARY/zebra-biblios.cfg  -g iso2709 -d biblios init
+
+Replacing YOURLIBRARY with your Koha installation name.
+
+Important Links
+===============
+
+`Koha Related <#koharelatedlinks>`__
+------------------------------------
+
+- Report Koha Bugs - http://bugs.koha-community.org
+
+- Koha Versioning Control - http://git.koha-community.org/
+
+- Database Structure - http://schema.koha-community.org
+
+- Koha Community Statistics - http://hea.koha-community.org
+
+- Koha as a CMS - http://wiki.koha-community.org/wiki/Koha_as_a_CMS
+
+- Kyles's Koha Tools - http://kylehall.info/index.php/projects/koha/
+
+- Koha Bibliography - http://www.zotero.org/groups/koha
+
+- Koha Shared Links - http://groups.diigo.com/group/everything-koha
+
+`Circulation Related <#circrelatedlinks>`__
+-------------------------------------------
+
+- Koha Desktop Offline Circulation:
+ https://github.com/bywatersolutions/koha-offline-circulation/releases
+
+- Koha Firefox Offline Circulation:
+ https://addons.mozilla.org/en-US/firefox/addon/koct/
+
+`Cataloging Related <#catalogrelatedlinks>`__
+---------------------------------------------
+
+- Koha MARC Tutorials - http://www.pakban.net/brooke/
+
+- IRSpy Open Z39.50 Server Search - http://irspy.indexdata.com/
+
+- Z39.50 Server List -
+ http://staff.library.mun.ca/staff/toolbox/z3950hosts.htm
+
+- Open Koha Z39.50 Targets -
+ http://wiki.koha-community.org/wiki/Koha_Open_Z39.50_Sources
+
+- Library of Congress Authorities - http://authorities.loc.gov/
+
+- MARC Country Codes - http://www.loc.gov/marc/countries/
+
+- Search the MARC Code List for Organizations -
+ http://www.loc.gov/marc/organizations/org-search.php
+
+- Search for Canadian MARC Codes -
+ http://www.collectionscanada.gc.ca/illcandir-bin/illsear/l=0/c=1
+
+- Z39.50 Bib-1 Attribute -
+ http://www.loc.gov/z3950/agency/defns/bib1.html
+
+`Enhanced Content Related <#enhancedcontentlinks>`__
+----------------------------------------------------
+
+- Amazon Associates -
+ `https://affiliate-program.amazon.com `__
+
+- Amazon Web Services - http://aws.amazon.com
+
+- WorldCat Affiliate Tools -
+ http://www.worldcat.org/wcpa/do/AffiliateUserServices?method=initSelfRegister
+
+- XISBN - http://www.worldcat.org/affiliate/webservices/xisbn/app.jsp
+
+- LibraryThing for Libraries - http://www.librarything.com/forlibraries
+
+`Design Related <#opaclinks>`__
+-------------------------------
+
+- JQuery Library - http://wiki.koha-community.org/wiki/JQuery_Library
+
+- HTML & CSS Library -
+ http://wiki.koha-community.org/wiki/HTML_%26_CSS_Library
+
+- Owen Leonard's Koha Blog - http://www.myacpl.org/koha
+
+`Reports Related <#reportlinks>`__
+----------------------------------
+
+- SQL Reports Library -
+ http://wiki.koha-community.org/wiki/SQL_Reports_Library
+
+- Database Schema - http://schema.koha-community.org
+
+- Sample reports from NEKLS -
+ http://www.nexpresslibrary.org/training/reports-training/
+
+`Installation Guides <#installlinks>`__
+---------------------------------------
+
+- Installing Koha 3 on Ubuntu -
+ http://www.blazingmoon.org/guides/k3-on-u810-1.html
+
+- Koha on Debian installation documentation -
+ http://openlib.org/home/krichel/courses/lis508/doc/koha_installation_overview.html
+
+- Koha 3.2 on Debian Squeeze -
+ http://wiki.koha-community.org/wiki/Koha_3.2_on_Debian_Squeeze
+
+`Misc <#misclinks>`__
+---------------------
+
+- Zotero - http://zotero.org
+
+- SOPAC - `http://thesocialopac.net `__
+
+Koha XSLT Item Types
+====================
+
+When you have any of the XSLT system preferences
+(`OPACXSLTDetailsDisplay <#OPACXSLTDetailsDisplay>`__,
+`OPACXSLTResultsDisplay <#OPACXSLTResultsDisplay>`__,
+`XSLTDetailsDisplay <#XSLTDetailsDisplay>`__, and/or
+`XSLTResultsDisplay <#XSLTResultsDisplay>`__) along with the
+`DisplayOPACiconsXSLT <#DisplayOPACiconsXSLT>`__ and
+`DisplayIconsXSLT <#DisplayIconsXSLT>`__ preferences turned on you will
+see item type icons on the related screen.
+
+ **Important**
+
+ These images are coming from values found in your leader, if your
+ leader is not cataloged properly it might be best to turn off the
+ `DisplayOPACiconsXSLT <#DisplayOPACiconsXSLT>`__ preference (which
+ can be done while leaving the other XSLT preferences turned on).
+
+Book image
+|image1081|
+
+- Book [BK]
+
+ - leader6 = a (and one of the leader7 values below)
+
+ - leader7 = a
+
+ - leader7 = c
+
+ - leader7 = d
+
+ - leader7 = m
+
+ - leader6 = t
+
+Computer Image
+|image1082|
+
+- Computer File [CF]
+
+ - leader6 = m
+
+Continuing Resource Image
+|image1083|
+
+- Continuing Resource [CR]
+
+ - leader7 = b
+
+ - leader7 = i
+
+ - leader7 = s
+
+Map Image
+|image1084|
+
+- Map [MP]
+
+ - leader6 = e
+
+ - leader6 = f
+
+Mixed Materials Image
+|image1085|
+
+- Mixed [MX]
+
+ - leader6 = p
+
+Sound Image
+|image1086|
+
+- Sound [MU]
+
+ - leader6 = c
+
+ - leader6 = d
+
+ - leader6 = i
+
+ - leader6 = j
+
+Visual Material Image
+|image1087|
+
+- Visual Material [VM]
+
+ - leader6 = g
+
+ - leader6 = k
+
+ - leader6 = r
+
+Kit Image
+|image1088|
+
+- Kit
+
+ - leader6 = o
+
+MarcEdit
+========
+
+Many libraries like to use MarcEdit for modifications or data cleanup.
+If you'd like to do this you will need to download it at:
+http://marcedit.reeset.net/
+
+ **Important**
+
+ Many of the actions described in this chapter can be done in Koha
+ using `Marc Modification Templates <#marcmodtemplates>`__, but this
+ section is here for those who are used to MarcEdit.
+
+`Adding a prefix to call numbers <#marceditprefix>`__
+-----------------------------------------------------
+
+When bringing data into Koha, you may want to first clean it up. One
+common action among Koha users is to add a prefix to the call number.
+
+- Open MarcEdit
+
+ MarcEdit
+ |image1089|
+
+- Click 'MarcEditor'
+
+- Go to Tools > Edit Subfield Data
+
+ Edit subfield data
+ |image1090|
+
+- To prepend data the special character is: ^b To simply prepend data
+ to the beginning of a subfield, add ^b to the Field Data: textbox and
+ the data to be appended in the Replace
+
+ Prepend data to a field
+ |image1091|
+
+ - To prepend data to the beginning of the subfield while replacing a
+ text string, add ^b[string to replace] to the Field Data textbox
+ and the data to be appended in the Replace With textbox.
+
+`Importing Excel data into Koha <#marceditexcel>`__
+---------------------------------------------------
+
+Suppose you have records of your library in excel data sheet format and
+want them to import into Koha. But how will you do this? Koha will not
+let you import excel records directly. Well here is a very simple
+solution for you which will let you import your excel records in Koha
+easily. First, we will convert excel file into Marc file and then will
+import it into Koha.
+
+Follow the given steps to import your excel records into Koha
+
+`Converting from Excel format into .mrk format <#convertexcel>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+First, we will convert excel format into .mrk format. For this we will
+use MarcEdit. You can download it from http://marcedit.reeset.net/
+
+Now open it and select Add-ins-->Delimited Text Translator.
+
+Delimited Text Translator
+|image1092|
+
+Click Next when the following window appears.
+
+Delimited Text Translator
+|image1093|
+
+Browse for your excel file.
+
+Delimited Text Translator
+|image1094|
+
+Locate your excel file by choosing the format Excel File(\*.xls).
+
+Delimited Text Translator
+|image1095|
+
+Similarly, fill all the other entries such as Output File, Excel Sheet
+Name and check UTF-8 Encoded (if required) and Click Next.
+
+Delimited Text Translator
+|image1096|
+
+Now you will be prompted for mapping the fields to recognise the fields
+by standard marc format.
+
+Suppose for Field 0 that is first column I entered Map to: 022$a( Valid
+ISSN for the continuing resource) and then click on Apply.
+
+Delimited Text Translator
+|image1097|
+
+ **Note**
+
+ You can customize Indicators and all other things, for more
+ information on marc21 format visit the `official library of congress
+ site `__.
+
+Similarly map all other fields and then Click on Finish.
+
+Delimited Text Translator
+|image1098|
+
+And then a window will appear indicating that your Marc Text
+File(\*.mrk) has been created.
+
+Delimited Text Translator
+|image1099|
+
+Click Close and we have created a .mrk file from .xls file in this step.
+You can view the file by double clicking on it.
+
+`Convert .mrk file to .mrc <#convertmrk>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+We will convert .mrk file that we have created in the above step into
+raw Marc format that can be directly imported into Koha.
+
+For this again open MarcEdit and Select MARC Tools.
+
+MARC Tools
+|image1100|
+
+Next Select MarcMaker to convert .mrk file into .mrc format.
+
+MarcMaker
+|image1101|
+
+Locate your input file and name your output file. Then Click Execute.
+
+MarcMaker
+|image1102|
+
+And it will show you the Result.
+
+MarcMaker
+|image1103|
+
+Click Close and now we have raw Marc records with us (.mrc file).
+
+`Import .mrc into Koha <#importmrc>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+More information on importing records into Koha can be found in the
+'`Stage MARC Records for Import <#stagemarc>`__' section of this manual.
+
+Finally we will import above created .mrc file into Koha.
+
+Click on Tools in your Koha staff client.
+
+Koha Staff Client
+|image1104|
+
+Next Click on Stage MARC Records for Import.
+
+Stage MARC Records for Import
+|image1105|
+
+After this, choose your previously created .mrc file and click on
+Upload.
+
+Stage File
+|image1106|
+
+You can also add comment about file and finally click on Stage For
+Import.
+
+Stage for Import
+|image1107|
+
+When the import is done, you will get a result something like this
+
+Staged Records Summary
+|image1108|
+
+Next, click on Manage staged records.
+
+Here you can even change matching rules.
+
+Manage Staged Records
+|image1109|
+
+Click on Import this batch into catalog when you are done.
+
+Thats it. After all the records get imported, check Status and it should
+read "imported"
+
+Finalize Import
+|image1110|
+
+You can even undo the Import operation.
+
+And within few minutes, we have imported around 10,000 records in Koha
+
+Talking Tech
+============
+
+Talking Tech I-tiva is a third party, proprietary, product that
+libraries can subscribe to. Learn more here:
+http://www.talkingtech.com/solutions/library.
+
+`Installation and Setup Instructions <#talkingtechinstall>`__
+-------------------------------------------------------------
+
+Be sure you've run
+installer/data/mysql/atomicupdate/Bug-4246-Talking-Tech-itiva-phone-notifications.pl
+to install the required data pack (new syspref, notice placeholders and
+messaging transport preferences)
+
+To use,
+`TalkingTechItivaPhoneNotification <#TalkingTechItivaPhoneNotification>`__
+syspref must be turned on.
+
+If you wish to process PREOVERDUE or RESERVES messages, you'll need the
+`EnhancedMessagingPreferences <#EnhancedMessagingPreferences>`__ system
+preference turned on, and patrons to have filled in a preference for
+receiving these notices by phone.
+
+For OVERDUE messages, overdue notice triggers must be configured under
+Koha -> Tools -> `Overdue Notice Triggers <#noticetriggers>`__. Either
+branch-specific triggers or the default level triggers may be used
+(script will select whichever is appropriate).
+
+`Sending Notices File <#talkingtechsend>`__
+-------------------------------------------
+
+1. Add the `TalkingTech\_itiva\_outbound.pl <#talkingtechsendcron>`__
+ script to your crontab
+
+2. Add an FTP/SFTP or other transport method to send the output file to
+ the I-tiva server
+
+3. If you wish, archive the sent notices file in another directory after
+ sending
+
+Run TalkingTech\_itiva\_outbound.pl --help for more information
+
+`Receiving Results File <#talkingtechreceive>`__
+------------------------------------------------
+
+1. Add an FTP/SFTP or other transport method to send the Results file to
+ a known directory on your Koha server
+
+2. Add the `TalkingTech\_itiva\_inbound.pl <#talkingtechreceivecron>`__
+ script to your crontab, aimed at that directory
+
+3. If you wish, archive the results file in another directory after
+ processing
+
+Run TalkingTech\_itiva\_inbound.pl --help for more information
+
+OCLC Connexion Gateway
+======================
+
+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.
+
+`Setting up OCLC service on Koha <#oclckohasetup>`__
+----------------------------------------------------
+
+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 `Manage Staged
+MARC Records <#managestaged>`__ 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
+
+`Setting up your OCLC desktop client <#oclcdesktopsetup>`__
+-----------------------------------------------------------
+
+ **Note**
+
+ Screenshots are OCLC Connexion Client v.2.50, Koha v.3.12
+
+To set up the OCLC Connexion desktop client to connect to Koha, go to
+Tools > Options, then choose the Export tab. Connexion Export Tab
+
+- Click the "Create..." button to set up a new destination, then choose
+ "OCLC Gateway Export" and click OK.
+
+ - Enter the following information:
+
+ - "Host Name:" Your catalogâs appropriate IP address (from your
+ `config file above <#oclckohasetup>`__)
+
+ - "Port:" Your catalog's appropriate port number (from your
+ `config file above <#oclckohasetup>`__)
+
+ - "Login ID:" The cataloger's Koha login
+
+ - "Password:" The cataloger's Koha password
+
+ - "Notify Host Before Disconnect" = checked,
+
+ - "Timeout" = 100, "Retries" = 3, "Delay" = 0 (zero),
+
+ - "Send Local System Logon ID Password" = checked.
+
+ OCLC Gateway Export Settings
+ |image1111|
+
+- Select "OK" when finished, and you should see your new "Gateway
+ Export" option listed (The catalog's IP address and port are blacked
+ out in the following screenshot)
+
+ Gateway Export Added
+
+- Click on "Record Characteristics" and make sure that the
+ bibliographic records are using MARC21, UTF-8 Unicode, and click OK
+ to save.
+
+ Record Characteristics
+
+You should be ready to go! Â To export a record from OCLC Connexion
+Client to Koha, just press F5 while the record is on-screen. Â The export
+dialog will pop up, and you'll see Connexion attempting to talk to Koha.
+Â You should get a message that the record was added or overlaid,
+including its biblio number, and a URL that you can copy into your web
+browser to jump straight to the record.
+
+`Using the OCLC Connexion Gateway <#oclcgateway>`__
+---------------------------------------------------
+
+Records can be exported from Connexion either in a batch or one by one.
+
+`Exporting records one by one <#oclconeexport>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+To export bibliographic records one by one, be sure your "Batch" options
+are correct: from the "Tools" menu, select "Options", and select the
+"Batch" tab. In the "Perform local actions in batch" area,
+"Bibliographic Record Export" should be uncheckedConnexion batch options
+
+When ready to export, from the "Action" menu, select "Export" or use the
+F5 key. You will see a screen similar to the following if the import is
+successful and if the record is new to the Catalog; you may copy & paste
+the resulting URL into your Koha catalog to see the new record.Connexion
+Export
+
+If the record was overlaid, you will see a message to that effect in the
+"OCLC Gateway Export Status" windowOverlay confirmation
+
+`Exporting records in a batch <#oclcbatchexport>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+To export bibliographic records in a batch, be sure your "Batch" options
+are correct: from the "Tools" menu, select "Options", and select the
+"Batch" tab. In the "Perform local actions in batch" area,
+"Bibliographic Record Export" should be checkedOCLC Batch Export Options
+
+When a record is ready to export, from the "Action" menu, select
+"Export" or use the F5 key, and itâs export status will be "ready."
+
+When ready to export the batch, from the "Batch" menu, select "Process
+batch" and check the appropriate "Path" and "Export" boxesBatch import
+process
+
+The export will begin, and the bib records will be exported & imported
+into Koha one by one; you will see "OCLC Gateway Export Status" windows,
+as above, showing you the results of each export. That window will stay
+there until you select "Close," and then the next recordâs export/import
+will begin. The process will continue until all records in the batch are
+completed. Then you may or may not see the Connexion Client export
+report (depending on your Client options for that).
+
+`Items in OCLC <#oclcitems>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+If you'd like to create your item records in OCLC you can do so by
+addding a 952 for each item to the bib record you're cataloging. The
+`Item/Holdings Cataloging Guide <#itemcatguide>`__ will break down what
+subfields you can use in the 952, but at the minimum you want to have
+subfield 2, a, b, and y on your items.
+
+952
+\\\\$2CLASSIFICATION$aHOMEBRANCHCODE$bHOLDINGBRANCHCODE$yITEMTYPECODE
+
+- The subfield 2 holds the classification code. This can be ddc for
+ Dewey or lcc for Library of Congress or z for Custom. Other
+ classification sources can be found in the `Classification
+ Sources <#classificationsources>`__ area in administration
+
+- Subfield a is your home library and needs to be the code for your
+ home library, not the library name. You can find these codes in the
+ `Libraries & Groups <#libsgroups>`__ administration area.
+
+- Subfield b is your holding library and needs to be the code for your
+ holding library, not the library name. You can find these codes in
+ the `Libraries & Groups <#libsgroups>`__ administration area.
+
+- Subfield y is your item type code. It needs to be the code, not the
+ item type name. You can find these codes in the `Item
+ Types <#itemtypeadmin>`__ administration area.
+
+952 \\\\$2ddc$aMAIN$bMAIN$yBOOK
+
+In addition to these required fields you can enter any other subfield
+you'd like. Most libraries will enter a call number in subfield o and a
+barcode in subfield p as well. Review the `Item/Holdings Cataloging
+Guide <#itemcatguide>`__ for a full list of subfields and values.
+
+FAQs
+====
+
+`Display <#displayfaq>`__
+-------------------------
+
+`Custom Item Type/Authorized Value Icons <#customicons>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+**Question:** Can I have my own set of item type images (or authorized
+value icons)?
+
+**Answer:**\ Absolutely. To add additional icons to your system you
+simply add a new directory to
+koha-tmpl/intranet-tmpl/prog/img/itemtypeimg/ and to
+koha-tmpl/opac-tmpl/prog/itemtypeimg and put your icons in the new
+directory. Your icons will show up in a new tab as soon as they are in
+the folders.
+
+- **Note**
+
+ Remember to put the icons in both places (on the OPAC and the
+ intranet).
+
+`Customizing Koha Images <#customkohaimages>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+**Question**: Can I customize the images in the OPAC?
+
+**Answer**: Absolutely. Koha comes with a series of original images that
+you can alter to meet your needs. The originals can be found in the
+misc/interface\_customization/ directory.
+
+`OPAC Display Fields <#opacdisplayfaq>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+**Question**: What MARC fields print to the different OPAC screens in
+Koha?
+
+**Answer**: The XSLT preference must be set as follows for the following
+fields to show
+
+- `OPACXSLTResultsDisplay <#OPACXSLTResultsDisplay>`__ = using XSLT
+ stylesheets
+
+- `OPACXSLTDetailsDisplay <#OPACXSLTDetailsDisplay>`__ = using XSLT
+ stylesheets
+
+- `DisplayOPACiconsXSLT <#DisplayOPACiconsXSLT>`__ = show
+
+The OPAC Results page shows:
+
+- 245
+
+- 100, 110, 111
+
+- 700, 710, 711
+
+- 250
+
+- 260
+
+- 246
+
+- 856
+
+The OPAC Details page shows:
+
+- 245
+
+- 100, 110, 111
+
+- 700, 710, 711
+
+- 440, 490
+
+- 260
+
+- 250
+
+- 300
+
+- 020
+
+- 022
+
+- 246
+
+- 130, 240
+
+- 6xx
+
+- 856
+
+- 505
+
+- 773
+
+- 520
+
+- 866
+
+- 775
+
+- 780
+
+- 785
+
+- plus all of the 5xx fields in the Notes tab at the bottom
+
+`Subtitle Display on Bib Records <#displaysubtitle>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+**Question**: How do I get the subtitle to display on the detail pages
+for my bib records?
+
+**Answer**: Subtitle display now depends on there being a `keyword
+mapping <#keywordmapping>`__ for the MARC field in question. Adding a
+mapping for "subtitle" -> "245b" for an item's framework results in
+display of the subtitle in OPAC and staff client search and detail pages
+(although not in all instances where subtitles might be displayed, e.g.
+the Cart).
+
+`Show patrons the barcodes of items they have checked out <#opacbarcodesfaq>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+**Question**: Can patrons see the barcodes for the items they have
+checked out.
+
+**Answer**: Not by default, but with a few edits to the patron record
+you can make a barcode column appear on the patron's check out summary
+in the OPAC. You can set up a `patron
+attribute <#patronattributetypes>`__ with the value of SHOW\_BCODE and
+`authorized value <#authorizedvalues>`__ of YES\_NO to make this happen.
+
+Add SHOW\_BCODE patron attribute
+|image1112|
+
+Then on the `patron's record set the value <#editpatrons>`__ for
+SHOW\_BCODE to yes.
+
+Setting value for SHOW\_BCODE on patron record
+|image1113|
+
+This will add a column to the check out summary in the OPAC that shows
+the patrons the barcodes of the items they have checked out.
+
+Barcode number on checkout list in OPAC
+|image1114|
+
+Clicking on the 'Overdue' tab will show only the items that are overdue.
+
+`Circulation/Notices <#circfaq>`__
+----------------------------------
+
+`Book drop Date <#dropboxfaq>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+**Question**: How is the book drop date is determined? Is it the last
+open date for the checkout branch? Is it today's date minus one? Can the
+book drop checkin date be set?
+
+**Answer**: If the library is closed for four days for renovations, for
+example, there would be more than one day needed for the book drop date.
+You will only have one book drop date and that will be the last day that
+the library open (determined by the holiday calendar) because there is
+no real way to know what day the books were dropped into the box during
+the 4 closed days. The only way to change the effective checkin date in
+book drop mode is to modify the calendar.
+
+`Holds to Pull and Holds Queue <#holdsreportsfaq>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+**Question**: What is the difference between the `Holds
+Queue <#holdsqueue>`__ and `Holds to Pull <#holdspull>`__?
+
+**Answer**: The holds to pull report gives a simple list of what holds
+need to be filled with available items. It should only be used in Koha
+installations where there is only one library.
+
+The holds queue tries to do the same thing, but in a 'smarter' way. This
+allows it to split up the list by library, consult the `transport cost
+matrix <#transportcostmatrix>`__ and refresh regularly to provide
+different pull lists to each library.
+
+`Duplicate Overdue Notices <#dupoverduefaq>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+**Question**: Why are patrons getting two overdue notices?
+
+**Answer**: This tool takes all branches in the overdue rules and sent
+notifications to them. So, if you have a default rule & a branch rule,
+the notification will be generated twice. A quick fix is to discard
+"default rule" for instance.
+
+`Printing Overdue Notices <#printoverduefaq>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+**Question**: Can I print overdue notices for patrons without email
+addresses on file?
+
+**Answer**: Yes. The `overdue notice cron job <#overduenoticecron>`__
+has a setting to generate the overdue notices as HTML for printing. An
+example of this usage would be:
+
+::
+
+ overdue_notices.pl -t -html /tmp/noticedir -itemscontent issuedate,date_due,title,barcode,author
+
+In this example, we wanted to use only certain item fields in our
+notices, so we specified itemscontent fields in the cron entry; that's
+not a requirement for the feature.
+
+The command line needs to specify a web-accessible directory where the
+print notices will go -- they get a filename like
+notices-2009-11-24.html (or holdnotices-2009-11-24.html). The overdue
+notice itself can be formatted to fit a Z-mailer. Within the notice
+file, the text is spaced down or over to where it will print properly on
+the form. The script has code that wraps around the notice file to tell
+the HTML to obey the formatting, and to do a page break between notices.
+That's so that when staff print it out, they get one per page. We had to
+add an extra syspref (`PrintNoticesMaxLines <#PrintNoticesMaxLines>`__)
+to specify page length because our client allows a \_lot\_ of checkouts
+which meant some notices were running onto multiple pages. That syspref
+says to truncate the print notice at that page length and put in a
+message about go check your OPAC account for the full list.
+
+The print and email overdues use the same notice file. The print notices
+for holds are different -- there's a separate HOLD\_PRINT notice file
+and the system uses it if there's no email address. Then a nightly cron
+job runs to gather those up from the message queue and put them in an
+HTML file in the notice directory, as above.
+
+The cron entry is gather\_print\_notices.pl /tmp/noticedir
+
+`Unable to Renew Items <#renewfaq>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+**Question**: We're trying to renew some items for our patron. One of
+the items is on hold and ineligible for renewal, but the other two items
+refuse to renew even though they should be eligible. When I try to use
+the override renewal limit, it just returns a little message that says
+"renewal failed". Any idea what's going on here?
+
+**Answer**: At the very least you will need to set an absolute `default
+circulation rule <#circfinerules>`__. This rule should be set for the
+default itemtype, default branchcode and default patron category. That
+will catch anyone who doesn't match a specific rule. Patrons who do not
+match a specific rule will get blocked from placing holds or renewing
+items, since there was no baseline number of holds or renewals to
+utilize.
+
+`Unable to Place Holds <#holdsfaq>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+**Question**: Why can't I place holds when I have all of the preferences
+turned on.
+
+**Answer**: You probably need to set a default circulation rule. At the
+very least you will need to set an default circulation rule. This rule
+should be set for all item types, all branches and all patron
+categories. That will catch all instances that do not match a specific
+rule. When checking out if you do not have a rule for the default
+branch, default item and default patron category then you may see
+patrons getting blocked from placing holds.
+
+`Keyboard Shortcuts <#keyboardshort>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+**Question**: Do I have to use my mouse to access the checkout, checkin
+and cataloging tabs at the top of the circulation pages?
+
+**Answer**: You can jump between the tabs on the quick search box at the
+top of the screen by using the following hot keys (if the tab is
+available):
+
+- jump to the catalog search with Alt+Q
+
+- jump to the checkout with Alt+U
+
+ - this will not work for Mac user
+
+- jump to the checkin with Alt+R
+
+ **Note**
+
+ Mac users use the OPTION button in place of ALT
+
+`SMS Notices/Messages <#smsnoticefaq>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+**Question**: I want Koha to send notices via SMS, what do I need to do?
+
+**Answer**: First you need to choose a SMS service to use with Koha.
+There is a list available here:
+http://search.cpan.org/search?query=sms%3A%3Asend&mode=all Not all SMS
+services available to libraries have Perl drivers, so be sure to check
+this list to see if the provider you're considering is listed. If not
+you want to ask your provider if they have a Perl module, if not you
+should consider another service. Some common options in the US (that
+have Perl drivers) are:
+
+- AQL (`www.aql.com `__)
+
+- Wadja (`wadja.com `__)
+
+- Ipipi (`ipipi.com `__)
+
+- T-mobile
+
+- SMSDiscount (`smsdiscount.com `__)
+
+- Clickatell
+
+**Question**: What about in India?
+
+**Answer**: India does not yet have too many options here. This is
+partly due to the Telecom regulatory authority's (TRAI) stipulations
+about transactional SMSes and limits on the number of SMSes that may be
+sent / received per users per day. India specific drivers include:
+
+- Unicel Technologies Pvt Ltd (`unicel.in `__)
+
+`Cataloging <#catfaq>`__
+------------------------
+
+`Authority Fields <#authorityfaq>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+**Question:**\ Why can't I edit 1xx, 6xx, or 7xx fields in my catalog
+record?
+
+**Answer:** These fields are authority controlled and you probably have
+the `BiblioAddsAuthorities <#BiblioAddsAuthorities>`__ set to "Don't
+allow". When it is set to "Don't allow" these fields will be locked and
+require you to search for an existing authority record to populate the
+field with. To allow typing in these authority fields set
+`BiblioAddsAuthorities <#BiblioAddsAuthorities>`__ to 'Allow'.
+
+ **Note**
+
+ Fields affected by this preference will show a lock symbol in them
+
+Fields affected by this preference show a lock in the field
+|image1115|
+
+`Koha to MARC Mapping <#kohamarcfaq>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+**Question**: What's the relationship between 'Koha to MARC Mapping' and
+'MARC Bibliographic Frameworks'?
+
+**Answer**: Mapping can be defined through 'MARC Bibliographic
+Frameworks' OR 'Koha to MARC Mapping'. 'Koha to MARC Mapping' is just a
+shortcut to speed up linkage. If you change a mapping in one of these
+modules, the mapping will change in the other as well. (In other words,
+the two modules 'overwrite' each other in order to prevent conflicts
+from existing in Koha).
+
+`Number of Items Per Bib Record <#itemsperbibfaq>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+**Question**: Is there a limit on the number of items I can attach to a
+bib record?
+
+**Answer**: There is no explicit limit to the number of items you can
+attach to a bibliographic record, but if you attach enough of them, your
+MARC record will exceed the maximum file size limit for the ISO 2709
+standard, which breaks indexing for that record. I've found this occurs
+somewhere between 600 and 1000 items on a 'normal' bibliographic record.
+
+`Analytics <#analyticsfaq>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+**Question**: I am using the
+`EasyAnalyticalRecords <#EasyAnalyticalRecords>`__ feature, but my links
+in the OPAC and Staff Client to 'Show Analytics' are not working.
+
+**Answer**: If you plan on using
+`EasyAnalyticalRecords <#EasyAnalyticalRecords>`__ you will want to make
+sure to set your `UseControlNumber <#UseControlNumber>`__ preference to
+"Don't use," this will prevent broken links.
+
+`Acquisitions <#acqfaq>`__
+--------------------------
+
+`Planning Categories <#planningcatfaq>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+**Question**: What is a planning category?
+
+**Answer**: When you plan in advance for the way your budget is going to
+be spent, you initially plan for how it's going to be spent over time,
+that's the most natural thing to do.
+
+So you plan for $1000 in Jan. $1000 in Feb., $3000 in March, etc. You
+can basically do the same thing with a list of values in lieu of the
+months.
+
+Say you have a list like this one:
+
+- < 1 month
+
+- < 6 months
+
+- < 1 year
+
+- < 3 years
+
+- < 10 years
+
+- > 10 years
+
+The list is meant to represent when the books acquired where published.
+Then you plan for it, saying: we went to spend at list 40% of our
+budgets on books published less than a year ago, 10% on books more than
+10 years old, etc.
+
+Upon acquiring new material, you'll be able to select, for a given item,
+a value from this list in a drop down. Then, after the material has been
+acquired, at the end of the year, you'll be able to compare the goals
+set, with what's been achieved.
+
+`Serials <#serialsfaq>`__
+-------------------------
+
+`Advanced Patterns <#advancedpatternfaq>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+**Question**: What is the 'inner counter' on the advanced serials
+pattern interface?
+
+**Answer**: I think it is better to give an example to understand this :
+
+Example for a monthly subscription :
+
+- First issue publication date : April 2010
+
+- Numbering : No {X}, year {Y}
+
+- First issue : No 4, year 2010
+
+For the year Y : you will want the year change on January 2011
+
+So, the advanced pattern for Y will be :
+
+- Add : 1
+
+- once every : 12
+
+- When more than 9999999
+
+- inner counter : 3
+
+- Set back to 0
+
+- Begins with 2010
+
+Year is going to change after 12 received issues from April 2010, that
+is in April 2011 if you don't set inner counter. Set inner counter to 3
+will say to Koha : change year after 12-3 = 9 received issues.
+
+Inner counter says to Koha to take into account the first issues of the
+year, even if they are not received with Koha. If you begin with first
+issue of the year write nothing or 0.
+
+`Reports <#reportsfaq>`__
+-------------------------
+
+`Define Codes Stored in DB <#accounttypefaq>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+`Fines Table <#finescodefaq>`__
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+**Question:** What do the codes in the accounttype field in the
+accountlines table stand for?
+
+**Answer:**
+
+- A = Account management fee
+
+- C = Credit
+
+- F = Overdue fine
+
+- FOR = Forgiven
+
+- FU = Overdue, still acccruing
+
+- L = Lost item
+
+- LR = Lost item returned/refunded
+
+- M = Sundry
+
+- N = New card
+
+- PAY = Payment
+
+- W = Writeoff
+
+`Statistics Table <#statscodefaq>`__
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+**Question:**\ What are the possible codes for the type field in the
+statistics table?
+
+**Answer:**
+
+- localuse
+
+ - Registers if an item that had been checked out to a statistics
+ patron (category type = 'X') is returned
+
+- issue
+
+- return
+
+- renew
+
+- writeoff
+
+- payment
+
+- CreditXXX
+
+ - The XXX stores different types of fee credits, so a query to catch
+ them all would include a clause like "type LIKE 'Credit%'"
+
+`Reserves Table <#rescodefaq>`__
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+**Question**: What are the possible codes for the found field in the
+reserves and old\_reserves tables?
+
+**Answer**:
+
+- NULL: means the patron requested the 1st available, and we haven't
+ chosen the item
+
+- T = Transit: the reserve is linked to an item but is in transit to
+ the pickup branch
+
+- W = Waiting: the reserve is linked to an item, is at the pickup
+ branch, and is waiting on the hold shelf
+
+- F = Finished: the reserve has been completed, and is done
+
+`Reports Dictionary Table <#reportdicfaq>`__
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+**Question**: What are the possible codes for the area field in the
+reports\_dictionary table?
+
+**Answer**:
+
+- 1 = Circulation
+
+- 2 = Catalog
+
+- 3 = Patrons
+
+- 4 = Acquisitions
+
+- 5 = Accounts
+
+`Messages Table <#msgtablefaq>`__
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+**Question**: What are the possible codes for the message\_type field in
+the messages table?
+
+**Answer**:
+
+- L = For Librarians
+
+- B = For Patrons/Borrowers
+
+`Serial Table <#serialtablefaq>`__
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+**Question**: What are the possible codes for the status field in the
+serial table?
+
+**Answer**:
+
+- 1 = Expected
+
+- 2 = Arrived
+
+- 3 = Late
+
+- 4 = Missing
+
+- 5 = Not available
+
+- 6 = Delete
+
+- 7 = Claimed
+
+- 8 = Stopped
+
+- 41 = Missing (not received)
+
+- 42 = Missing (sold out)
+
+- 43 = Missing (damaged)
+
+- 44 = Missing (lost)
+
+`Borrowers Table <#borrowerprivacyvalues>`__
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+**Question**: What are the possible codes for the privacy field in the
+borrowers table?
+
+**Answer**:
+
+- 0 = Forever
+
+- 1 = Default
+
+- 2 = Never
+
+`Messaging Preferences <#messpreffaq>`__
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+**Question**: What are the possible codes in the message\_attribute\_id
+field in the borrower\_message\_preferences table?
+
+**Answer**:
+
+- 2 = advanced notice
+
+- 6 = item checkout
+
+- 4 = hold filled
+
+- 1 = item due
+
+- 5 = item check in
+
+`Runtime Parameters <#runtimefaq>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+**Question**: Is there a way to filter my custom SQL reports before they
+run?
+
+**Answer**: If you feel that your report might be too resource intensive
+you might want to consider using runtime parameters to your query.
+Runtime parameters basically make a filter appear before the report is
+run to save your system resources.
+
+There is a specific syntax that Koha will understand as 'ask for values
+when running the report'. The syntax is <>.
+
+- The << and >> are just delimiters. You must put << at the beginning
+ and >> at the end of your parameter
+
+- The 'Question to ask' will be displayed on the left of the string to
+ enter.
+
+- The authorized\_value can be omitted if not applicable. If it
+ contains an authorized value category, or branches or itemtype or
+ categorycode or biblio\_framework, a list with the Koha authorized
+ values will be displayed instead of a free field Note that you can
+ have more than one parameter in a given SQL Note that entering
+ nothing at run time won't probably work as you expect. It will be
+ considered as "value empty" not as "ignore this parameter". For
+ example entering nothing for : "title=<>" will display
+ results with title='' (no title). If you want to have to have
+ something not mandatory, use "title like <>" and enter a
+ % at run time instead of nothing
+
+Examples:
+
+- SELECT surname,firstname FROM borrowers WHERE branchcode=<> AND surname like <>
+
+- SELECT \* FROM items WHERE homebranch = <> and barcode like <>
+
+- SELECT title , author FROM biblio WHERE frameworkcode=<>
+
+ **Note**
+
+ To generate a date picker calendar to the right of the field when
+ running a report you can use the 'date' keyword like this: <>
+
+ Date Picker
+ |image1116|
+
+ **Note**
+
+ You have to put "%" in a text box to 'leave it blank'. Otherwise, it
+ literally looks for "" (empty string) as the value for the field.
+
+ **Important**
+
+ In addition to using any authorized value code to generate a
+ dropdown, you can use the following values as well: Framework codes
+ (biblio\_framework), Branches (branches), Item Types (itemtypes) and
+ Patron Categories (categorycode). For example a branch pull down
+ would be generated like this <>
+
+ Branch pull down
+ |image1117|
+
+`Results Limited <#reportlimitfaq>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+**Question**: When I download my report it's limited to 10,000 results,
+how do I get all of the results to download?
+
+**Answer**: There is a limit of 10,000 records put on SQL statements
+entered in Koha. To get around this you want to add 'LIMIT 100000' to
+the end of your SQL statement (or any other number above 10,000.
+
+`Searching <#searchfaq>`__
+--------------------------
+
+`Advanced Search <#advancedsearchfaq>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+`Scan Indexes <#scanindexfaq>`__
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+**Question**: What does 'scan indexes' on the advanced search page mean?
+
+**Answer**: When you choose an index, enter a term, click 'scan indexes'
+and do the search, Koha displays the searched term and the following
+terms found in this index with the number of corresponding records That
+is search is not made directly in the catalog, but first in the indexes
+It works only for one index at once, and only with no limit in Location
+(All libraries needed)
+
+`Searching for Terms that Start With a Character <#searchstartswith>`__
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+**Question**: How do I search for all titles that start with the letter
+'C'?
+
+**Answer**: You can choose to search for things that start with a
+character or series of characters by using the CCL 'first-in-subfield'
+
+- example: ti,first-in-subfield=C
+
+`Wildcard Searching <#wildcardsearchfaq>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+**Question**:What is the difference between a keyword search using the
+'\*' (asterisk) versus a keyword search using the '%' (percent)? Both
+work in the catalog, but return different sets. Why?
+
+**Answer**: A wildcard is a character (\*,?,%,.) that can be used to
+represent one or more characters in a word. Two of the wildcard
+characters that can be used in Koha searches are the asterisk ('\*') and
+the percent sign ('%'). However, these two characters act differently
+when used in searching.
+
+The '\*' is going to force a more exact search of the first few
+characters you enter prior to the '\*'. The asterisk will allow for an
+infinite number of characters in the search as long as the first few
+characters designated by your search remain the same. For example,
+searching for authors using the term, Smi\*, will return a list that may
+include Smith, Smithers, Smithfield, Smiley, etc depending on the
+authors in your database.
+
+The '%' will treat the words you enter in the terms of "is like". So a
+search of Smi% will search for words like Smi. This results in a much
+more varied results list. For example, a search on Smi% will return a
+list containing Smothers, Smith, Smelley, Smithfield and many others
+depending on what is your database.
+
+The bottom line in searching with wildcards: '\*' is more exact while
+'%' searches for like terms.
+
+`Title Searching <#titlesearchingfaq>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+**Question**: Why does my Zebra title search for 'Help' not turn up 'The
+help' in the first pages of results?
+
+**Answer**: When doing a title search, you actually want to search for
+the title (i.e., 'the help' rather than just 'help'), and it will bubble
+right up to the top. If you're just searching for 'help' then the
+relevance ranking is going to affect the results you see.
+
+When it comes to relevance in Zebra, here's what's happening. First, the
+search is done. If you search for the title "help", then any title that
+has "help" in it comes back. Then from those records, separately, it
+does relevance on the \*whole\* record. The more your word appears, the
+more relevant, and some MARC tags are worth more points than others. So
+a self-help book with 505 notes where "help" appears a \*lot\* will be
+at the top, regardless of keyword or title.
+
+But when you add a \*second word\*, that helps it figure things out, as
+it's weighing the relevance of both words and the phrase. Because of the
+way relevance works, if you search "the help", then "the help" or "the
+help I need" are more relevant than "the way to help", because they
+appear together in order. Likewise, "help the girl" would be lower
+relevance, because it's out of order, and "help for the homeless" would
+be lower still, as they're out of order, and apart.
+
+The moral of the story is that single word searches, particularly on
+common words, will always struggle a bit; it can't evaluate relevance
+well, because you've not given it enough input.
+
+`Enhanced Content <#enhancedcontentfaq>`__
+------------------------------------------
+
+`FRBRizing Content <#frbrfaq>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+**Question:**\ At our public library we are running a Koha installation
+and we've tried to turn on all the nice functionalities in Koha such as
+the frbrising tool, but do not get the same result as Nelsonville public
+library.
+
+**Answer:**\ In fact, this feature is quite tricky to make that right.
+First it looks at XISBN service. And then search in your database for
+that ISBN. So both XISBN and your internal ISBN (in biblio table) have
+to be normalized. You could therefore use the script
+misc/batchupdateISBNs.pl (it removes all the - in your local ISBNs)
+
+`Amazon <#amzfaq>`__
+~~~~~~~~~~~~~~~~~~~~
+
+`All Amazon Content <#amazonfaq>`__
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+**Question**: I have all of the Amazon preferences turned on and have
+entered both of my keys, but none of the content appears in my system,
+why is that?
+
+**Answer**: Amazon's API checks your server time on all requests and if
+your server time is not set properly requests will be denied. To resolve
+this issue be sure to set your system time appropriately. Once that
+change in made Amazon content should appear immediately.
+
+On Debian the the command is *date -s "2010-06-30 17:21"* (with the
+proper date and time for your timezone).
+
+`System Administration <#systemfaq>`__
+--------------------------------------
+
+`Errors in Zebra Cron <#zebracronfaq>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+**Question**: I am noticing some errors in the
+koha-zebradaemon-output.log file. When new records are added it takes a
+bit longer to index than we think they should. Running rebuild zebra is
+often faster. Zebra ends up indexing and search works, but I am
+concerned about the errors. Any ideas?
+
+**Answer**: Rebuild\_zebra.pl -r deletes all of the files in the Zebra
+db directories (such as reci-0.mf) and then recreates them. Thus,
+permissions will be lost, and the files will be owned by the user who
+ran rebuild\_zebra.pl. If one rebuilds the zebra indexes as root, the
+daemons, which typically run under the user Koha, will not be able to
+update the indexes. Thus, it's important then that the zebra rebuilds
+are put in the cronjob file of the user Koha, and not root. Also
+important is that other users, such as root, don't manually execute
+rebuilds.
+
+If one desires that another user be able to execute rebuild\_zebra.pl,
+he should be given the permission to execute 'sudo -u Koha
+.../rebuild\_zebra.pl,' (if you want to do this, you also have to edit
+the sudoers file to pass the PERL5LIB variable with the env\_keep option
+as by default sudo strips away almost all environment variables). Or, as
+root user, one can use a simple 'su koha' and then the rebuild\_zebra.pl
+command.
+
+I've also tried to set the sticky bit on rebuild\_zebra.pl, but for
+whatever reason it didn't seem to work due to some problem with the
+PERL5LIB variable that I wasn't able to figure. That seems to me the
+easiest thing to do, if anybody has any idea how to make it work. If it
+worked and were the default, I think it would help folks to avoid a
+great deal of the problems that come up with zebra.
+
+`Making Z39.50 Target Public <#publicztarget>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+**Question**: Could someone tell me the exact steps I need to take to
+configure Zebra to expose my Koha 3 db as a public Z39.50 service?
+
+**Answer**: Edit the KOHA\_CONF file that your Koha is using. Uncomment
+the publicserver line like:
+
+
+
+to be:
+
+tcp:@:9999
+
+Then restart zebasrv and connect on the port specified (9999).
+
+`Shelving Location Authorized Values <#authvalfaq>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+**Question**: When editing an item, the new shelving location I created
+is not showing up by default in the items where I assigned it to.
+
+**Answer**: This is because you created the new shelving location with a
+code value of 0 (zero) Just FYI the system interprets authorized values
+of 0 as equaling a null so when you edit a record in cataloging where
+the authorized value in a field was assigned where the code was 0, the
+value displays as null in the item editor (or MARC editor) instead of
+the value the library meant it to be.
+
+`Why do I need Authorized Values? <#whyauthvals>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+**Question**: Why would I want to define authorized values for MARC
+tags?
+
+**Answer**: Authorized Values create a 'controlled vocabulary' for your
+staff. As an example, let us assume that your Koha installation is used
+by several libraries, and you use MARC 21. You might want to restrict
+the 850a MARC subfield to the institution codes for just those
+libraries. In that case, you could define an authorized values category
+(perhaps called "INST") and enter the institution codes as the
+authorized values for that category.
+
+ **Note**
+
+ Koha automatically sets up authorized value categories for your item
+ types and branch codes, and you can link these authorized values to
+ MARC subfields when you set up your MARC tag structure.
+
+`How do I clean up the sessions table? <#sessionstblfaq>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+**Question**: Is there a periodic job that can be run to cull old
+sessions from the table? We don't want to backup all the useless session
+data every night.
+
+**Answer**: You can run `cleanup database cron job <#cleandbcron>`__.
+
+Or just before doing a backup command (mysqldump), you can truncate
+session table: Â
+
+::
+
+ mysql -u`__
+---------------------------
+
+`Barcode Scanners <#barcodefaq>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+**Question**: What barcode scanners have been known to work with Koha?
+
+**Answer**: The simple rule of thumb is, does it act like a keyboard
+device?, if so, it will work. (i.e. can you take the scanner, scan a
+barcode and have it show up in a text editor, if so, it will work.)
+
+The main points to check are that it connects to your PC conveniently
+(can be USB or "keyboard wedge" which means it connects in line with the
+keyboard, which is useful with older computers), and that it scans the
+barcode type that you are using.
+
+It is a good idea to test some 'used' barcodes if you have any, to see
+whether the scanner can read scuffed or slightly wrinkled ones
+successfully. Most scanners are capable of reading several barcode types
+- there are many, and the specification should list the ones it can
+read. You may need to adjust settings slightly, such as prefix and
+suffix characters, or whether you want to send an 'enter' character or
+not.
+
+One more tip - some can be set 'always on' and may come with a stand,
+some have triggers under the handle, some have buttons on top, some are
+held like a pen. Think about the staff working with the hardware before
+choosing, as a button in the wrong place can be very awkward to use.
+
+`Printers <#printersfaq>`__
+~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+`Printers used by Koha libraries <#kohaprinters>`__
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+- POS-X receipt printer
+
+- Star Micronics printer (exact model unknown) with a generic/plain
+ text driver.
+
+- Star SP2000 (Nelsonville)
+
+- Star TSP-100 futurePRINT (Geauga)
+
+ - "I know there have been a lot of questions on receipt printers so
+ I thought I'd pass on my findings. We have been testing the Star
+ TSP-100 futurePRINT. I found this print to be VERY easy to
+ configure for Koha. I was even able to customize the print job by
+ adding our system logo (a .gif) to the top of every receipt. Also
+ with a bitmap created in Paint was able to add a message at the
+ bottom of each receipt with the contact information, hours and
+ website for the library that the materials were checked out at."
+
+- Epson TM 88 IIIP thermal receipt printers
+
+- Epson TM-T88IV
+
+- 1x1 labels using a Dymolabelwriter printer
+
+`Braille Support <#braillefaq>`__
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+**Question**: Are there any braille embosser or printer which has
+inbuilt braille converter and it is accessible with UNIX environment?
+
+**Answer**: You may want to look into BRLTTY
+(http://www.emptech.info/product_details.php?ID=1232).
+
+`Additional Support <#hardwaresupport>`__
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+- http://www.nexpresslibrary.org/go-live/configure-your-receipt-printers/
+
+Extending Koha
+==============
+
+`Amazon lookup script for Koha libraries <#amzlookup>`__
+--------------------------------------------------------
+
+We order most of our materials from Amazon, so I've been looking for a
+convenient way to tell if a book under consideration is in our catalog
+already.
+
+Greasemonkey & a custom user script fit the bill nicely:
+
+- https://addons.mozilla.org/en-US/firefox/addon/748
+
+- http://userscripts.org/scripts/show/56847
+
+A few caveats:
+
+- Like most scripts, this one was designed to work with Firefox; I
+ haven't explored getting it to work with other browsers.
+
+- I'm not a JavaScript programmer -- this was adapted from others'
+ work. Just a few lines would have to be changed to get the script to
+ work with your catalog.
+
+- It depends on the existence of ISBN for the item in question, so
+ movies, older books, etc. would not work.
+
+Others have added all sorts of bells & whistles: XISBN lookups to search
+for related titles, custom messages based on the status of items (on
+order, on hold, etc.), ... just search the UserScripts site for Amazon +
+library. For a later date!
+
+`Keyword Clouds <#extendkeywordclouds>`__
+-----------------------------------------
+
+In addition to the traditional tag cloud available in Koha, there is a
+way to generate clouds for popular subjects within Koha.
+
+The `Author/Subject Cloud cron job <#keywordclouds>`__ is used to help
+with this process. This cron job sends its output to files.
+
+- /home/koha/mylibrary/koharoot/koha-tmpl/cloud-author.html
+
+- /home/koha/yourlibrary/koharoot/koha-tmpl/cloud-subject.html
+
+This means that you can produce clouds for authors, collective author,
+all kind of subjects, classifications, etc. And since it works on zebra
+indexes, it is quick, even on large DBs. Tags clouds are sent to files.
+It's up to library webmaster to deal with those files in order to
+include them in `OPACMainUserBlock <#OpacMainUserBlock>`__, or include
+them into their library CMS.
+
+Some libraries even send the file into a Samba shared folder where
+webmaster take them, eventually clean them a little bit before
+integrating them into navigation widgets or pages.
+
+`Newest Titles Pulldown <#newtitlesoption>`__
+---------------------------------------------
+
+Often we want to add a way for our patrons to do searches for the newest
+items. In this example I'll show you how to create a pull down menu of
+the newest items by item type. These tips will work (with a couple
+changes) for collection codes or shelving locations as well.
+
+First, it's important to note that every link in Koha is a permanent
+link. This means if I do a search for everything of a specific item type
+sorted by the acquisitions date and bookmark that URL, whenever I click
+it I'll see the newest items of that type on the first few pages of the
+results.
+
+I took this knowledge and wrote a form takes this functionality in to
+consideration. It basically just does a search of your Koha catalog for
+a specific item type and sorts the results by acquisitions date.
+
+The first thing I did was write a MySQL statement to generate a list of
+item types for me - why copy and paste when you can use the power of
+MySQL?
+
+::
+
+ select concat('') from itemtypes
+
+The above looks at the itemtypes table and slaps the necessary HTML
+around each item type for me. I then exported that to CSV and opened it
+in my text editor and added the other parts of the form.
+
+::
+
+
New Items
+
+
+
+Now, what does all of that mean? The important bits are these:
+
+First the starting of the form.
+
+::
+
+