1 .. include:: images.rst
9 -------------------------
11 .. _custom-item-type/authorized-value-icons-label:
13 Custom item type/Authorized value icons
14 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
16 **Question:** Can I have my own set of item type images (or authorized
19 **Answer:**\ Absolutely. To add additional icons to your system you
20 simply add a new directory to
21 koha-tmpl/intranet-tmpl/prog/img/itemtypeimg/ and to
22 koha-tmpl/opac-tmpl/prog/itemtypeimg and put your icons in the new
23 directory. Your icons will show up in a new tab as soon as they are in
28 Remember to put the icons in both places (on the OPAC and the
31 .. _customizing-koha-images-label:
33 Customizing Koha images
34 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
36 **Question**: Can I customize the images in the OPAC?
38 **Answer**: Absolutely. Koha comes with a series of original images that
39 you can alter to meet your needs. The originals can be found in the
40 misc/interface\_customization/ directory.
42 .. _opac-display-fields-label:
45 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
47 **Question**: What MARC fields print to the different OPAC screens in
50 **Answer**: The XSLT preference must be set as follows for the following
53 - :ref:`OPACXSLTResultsDisplay` = using XSLT
56 - :ref:`OPACXSLTDetailsDisplay` = using XSLT
59 - :ref:`DisplayOPACiconsXSLT` = show
61 The OPAC Results page shows:
77 The OPAC Details page shows:
119 - plus all of the 5xx fields in the Notes tab at the bottom
121 .. _subtitle-display-on-bib-records-label:
123 Subtitle display on bibliographic records
124 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
126 **Question**: How do I get the subtitle to display on the detail pages
129 **Answer**: Subtitle display now depends on there being a :ref:`keyword
130 mapping <keywords-to-marc-mapping-label>` for the MARC field in question. Adding a
131 mapping for "subtitle" -> "245b" for an item's framework results in
132 display of the subtitle in OPAC and staff client search and detail pages
133 (although not in all instances where subtitles might be displayed, e.g.
136 .. _show-patrons-the-barcodes-of-items-they-have-checked-out-label:
138 Show patrons the barcodes of items they have checked out
139 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
141 **Question**: Can patrons see the barcodes for the items they have
144 **Answer**: Not by default, but with a few edits to the patron record
145 you can make a barcode column appear on the patron's check out summary
146 in the OPAC. You can set up a :ref:`patron
147 attribute <patron-attribute-types-label>` with the value of SHOW\_BCODE and
148 :ref:`authorized value <authorized-values-label>` of YES\_NO to make this happen.
152 Then on the :ref:`patron's record set the value <editing-patrons-label>` for
157 This will add a column to the check out summary in the OPAC that shows
158 the patrons the barcodes of the items they have checked out.
162 Clicking on the 'Overdue' tab will show only the items that are overdue.
164 .. _circulation/notices-label:
167 ----------------------------------
169 .. _book-drop-date-label:
172 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
174 **Question**: How is the book drop date is determined? Is it the last
175 open date for the checkout branch? Is it today's date minus one? Can the
176 book drop checkin date be set?
178 **Answer**: If the library is closed for four days for renovations, for
179 example, there would be more than one day needed for the book drop date.
180 You will only have one book drop date and that will be the last day that
181 the library open (determined by the holiday calendar) because there is
182 no real way to know what day the books were dropped into the box during
183 the 4 closed days. The only way to change the effective checkin date in
184 book drop mode is to modify the calendar.
186 .. _holds-to-pull-and-holds-queue-label:
188 Holds to pull and holds queue
189 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
191 **Question**: What is the difference between the :ref:`Holds
192 Queue <holds-queue-label>` and :ref:`Holds to Pull <holds-to-pull-label>`?
194 **Answer**: The holds to pull report gives a simple list of what holds
195 need to be filled with available items. It should only be used in Koha
196 installations where there is only one library.
198 The holds queue tries to do the same thing, but in a 'smarter' way. This
199 allows it to split up the list by library, consult the :ref:`transport cost
200 matrix <transport-cost-matrix-label>` and refresh regularly to provide
201 different pull lists to each library.
203 .. _duplicate-overdue-notices-label:
205 Duplicate overdue notices
206 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
208 **Question**: Why are patrons getting two overdue notices?
210 **Answer**: This tool takes all branches in the overdue rules and sent
211 notifications to them. So, if you have a default rule & a branch rule,
212 the notification will be generated twice. A quick fix is to discard
213 "default rule" for instance.
215 .. _printing-overdue-notices-label:
217 Printing overdue notices
218 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
220 **Question**: Can I print overdue notices for patrons without email
223 **Answer**: Yes. The :ref:`overdue notice cron job <overdue-notice-label>`
224 has a setting to generate the overdue notices as HTML for printing. An
225 example of this usage would be:
229 overdue_notices.pl -t -html /tmp/noticedir -itemscontent issuedate,date_due,title,barcode,author
231 In this example, we wanted to use only certain item fields in our
232 notices, so we specified itemscontent fields in the cron entry; that's
233 not a requirement for the feature.
235 The command line needs to specify a web-accessible directory where the
236 print notices will go -- they get a filename like
237 notices-2009-11-24.html (or holdnotices-2009-11-24.html). The overdue
238 notice itself can be formatted to fit a Z-mailer. Within the notice
239 file, the text is spaced down or over to where it will print properly on
240 the form. The script has code that wraps around the notice file to tell
241 the HTML to obey the formatting, and to do a page break between notices.
242 That's so that when staff print it out, they get one per page. We had to
243 add an extra syspref (:ref:`PrintNoticesMaxLines`)
244 to specify page length because our client allows a \_lot\_ of checkouts
245 which meant some notices were running onto multiple pages. That syspref
246 says to truncate the print notice at that page length and put in a
247 message about go check your OPAC account for the full list.
249 The cron entry is :ref:`gather\_print\_notices.pl <print-hold-notices>` /tmp/noticedir
251 .. _unable-to-renew-items-label:
253 Unable to renew items
254 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
256 **Question**: We're trying to renew some items for our patron. One of
257 the items is on hold and ineligible for renewal, but the other two items
258 refuse to renew even though they should be eligible. When I try to use
259 the override renewal limit, it just returns a little message that says
260 "renewal failed". Any idea what's going on here?
262 **Answer**: At the very least you will need to set an absolute :ref:`default
263 circulation rule <circulation-and-fine-rules-label>`. This rule should be set for the
264 default itemtype, default branchcode and default patron category. That
265 will catch anyone who doesn't match a specific rule. Patrons who do not
266 match a specific rule will get blocked from placing holds or renewing
267 items, since there was no baseline number of holds or renewals to
270 .. _unable-to-place-holds-label:
272 Unable to place holds
273 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
275 **Question**: Why can't I place holds when I have all of the preferences
278 **Answer**: You probably need to set a default circulation rule. At the
279 very least you will need to set an default circulation rule. This rule
280 should be set for all item types, all branches and all patron
281 categories. That will catch all instances that do not match a specific
282 rule. When checking out if you do not have a rule for the default
283 branch, default item and default patron category then you may see
284 patrons getting blocked from placing holds.
286 .. _keyboard-shortcuts-label:
289 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
291 **Question**: Do I have to use my mouse to access the checkout, checkin
292 and cataloging tabs at the top of the circulation pages?
294 **Answer**: You can jump between the tabs on the quick search box at the
295 top of the screen by using the following hot keys (if the tab is
298 - jump to the catalog search with Alt+Q
300 - jump to the checkout with Alt+U
302 - this will not work for Mac user
304 - jump to the checkin with Alt+R
308 Mac users use the OPTION button in place of ALT
310 .. _sms-notices/messages-label:
313 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
315 **Question**: I want Koha to send notices via SMS, what do I need to do?
317 **Answer**: First you need to choose a SMS service to use with Koha.
318 There is a list available here:
319 http://search.cpan.org/search?query=sms%3A%3Asend&mode=all Not all SMS
320 services available to libraries have Perl drivers, so be sure to check
321 this list to see if the provider you're considering is listed. If not
322 you want to ask your provider if they have a Perl module, if not you
323 should consider another service. Some common options in the US (that
324 have Perl drivers) are:
326 - AQL (`www.aql.com <http://www.aql.com>`__)
328 - Wadja (`wadja.com <http://wadja.com>`__)
330 - Ipipi (`ipipi.com <http://ipipi.com>`__)
334 - SMSDiscount (`smsdiscount.com <http://smsdiscount.com>`__)
338 **Question**: What about in India?
340 **Answer**: India does not yet have too many options here. This is
341 partly due to the Telecom regulatory authority's (TRAI) stipulations
342 about transactional SMSes and limits on the number of SMSes that may be
343 sent / received per users per day. India specific drivers include:
345 - Unicel Technologies Pvt Ltd (`unicel.in <http://unicel.in>`__)
347 .. _cataloging-label:
350 ------------------------
352 .. _authority-fields-label:
355 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
357 **Question:**\ Why can't I edit 1xx, 6xx, or 7xx fields in my catalog
360 **Answer:** These fields are authority controlled and you probably have
361 the :ref:`BiblioAddsAuthorities` set to "Don't
362 allow". When it is set to "Don't allow" these fields will be locked and
363 require you to search for an existing authority record to populate the
364 field with. To allow typing in these authority fields set
365 :ref:`BiblioAddsAuthorities` to 'Allow'.
369 Fields affected by this preference will show a lock symbol in them
373 .. _faq-koha-to-marc-mapping-label:
376 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
378 **Question**: What's the relationship between 'Koha to MARC Mapping' and
379 'MARC Bibliographic Frameworks'?
381 **Answer**: Mapping can be defined through 'MARC Bibliographic
382 Frameworks' OR 'Koha to MARC Mapping'. 'Koha to MARC Mapping' is just a
383 shortcut to speed up linkage. If you change a mapping in one of these
384 modules, the mapping will change in the other as well. (In other words,
385 the two modules 'overwrite' each other in order to prevent conflicts
386 from existing in Koha).
388 .. _number-of-items-per-bib-record-label:
390 Number of items per bibliographic record
391 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
393 **Question**: Is there a limit on the number of items I can attach to a
396 **Answer**: There is no explicit limit to the number of items you can
397 attach to a bibliographic record, but if you attach enough of them, your
398 MARC record will exceed the maximum file size limit for the ISO 2709
399 standard, which breaks indexing for that record. I've found this occurs
400 somewhere between 600 and 1000 items on a 'normal' bibliographic record.
405 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
407 **Question**: I am using the
408 :ref:`EasyAnalyticalRecords` feature, but my links
409 in the OPAC and Staff Client to 'Show Analytics' are not working.
411 **Answer**: If you plan on using
412 :ref:`EasyAnalyticalRecords` you will want to make
413 sure to set your :ref:`UseControlNumber` preference to
414 "Don't use," this will prevent broken links.
416 .. _acquisitions-label:
419 --------------------------
421 .. _planning-categories-label:
424 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
426 **Question**: What is a planning category?
428 **Answer**: When you plan in advance for the way your budget is going to
429 be spent, you initially plan for how it's going to be spent over time,
430 that's the most natural thing to do.
432 So you plan for $1000 in Jan. $1000 in Feb., $3000 in March, etc. You
433 can basically do the same thing with a list of values in lieu of the
436 Say you have a list like this one:
450 The list is meant to represent when the books acquired where published.
451 Then you plan for it, saying: we went to spend at list 40% of our
452 budgets on books published less than a year ago, 10% on books more than
455 Upon acquiring new material, you'll be able to select, for a given item,
456 a value from this list in a drop down. Then, after the material has been
457 acquired, at the end of the year, you'll be able to compare the goals
458 set, with what's been achieved.
463 -------------------------
465 .. _advanced-patterns-label:
468 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
470 **Question**: What is the 'inner counter' on the advanced serials
473 **Answer**: I think it is better to give an example to understand this :
475 Example for a monthly subscription :
477 - First issue publication date : April 2010
479 - Numbering : No {X}, year {Y}
481 - First issue : No 4, year 2010
483 For the year Y : you will want the year change on January 2011
485 So, the advanced pattern for Y will be :
491 - When more than 9999999
499 Year is going to change after 12 received issues from April 2010, that
500 is in April 2011 if you don't set inner counter. Set inner counter to 3
501 will say to Koha : change year after 12-3 = 9 received issues.
503 Inner counter says to Koha to take into account the first issues of the
504 year, even if they are not received with Koha. If you begin with first
505 issue of the year write nothing or 0.
507 .. _faq-reports-label:
510 -------------------------
512 .. _define-codes-stored-in-db-label:
514 Define codes stored in database
515 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
517 .. _fines-table-label:
520 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
522 **Question:** What do the codes in the accounttype field in the
523 accountlines table stand for?
527 - A = Account management fee
535 - FU = Overdue, still acccruing
539 - LR = Lost item returned/refunded
549 .. _statistics-table-label:
552 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
554 **Question:**\ What are the possible codes for the type field in the
561 - Registers if an item that had been checked out to a statistics
562 patron (category type = 'X') is returned
576 - The XXX stores different types of fee credits, so a query to catch
577 them all would include a clause like "type LIKE 'Credit%'"
579 .. _reserves-table-label:
582 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
584 **Question**: What are the possible codes for the found field in the
585 reserves and old\_reserves tables?
589 - NULL: means the patron requested the 1st available, and we haven't
592 - T = Transit: the reserve is linked to an item but is in transit to
595 - W = Waiting: the reserve is linked to an item, is at the pickup
596 branch, and is waiting on the hold shelf
598 - F = Finished: the reserve has been completed, and is done
600 .. _reports-dictionary-table-label:
602 Reports dictionary table
603 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
605 **Question**: What are the possible codes for the area field in the
606 reports\_dictionary table?
620 .. _messages-table-label:
623 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
625 **Question**: What are the possible codes for the message\_type field in
632 - B = For Patrons/Borrowers
634 .. _serial-table-label:
637 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
639 **Question**: What are the possible codes for the status field in the
660 - 41 = Missing (not received)
662 - 42 = Missing (sold out)
664 - 43 = Missing (damaged)
666 - 44 = Missing (lost)
668 .. _borrowers-table-label:
671 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
673 **Question**: What are the possible codes for the privacy field in the
684 .. _patron-categories-table-label:
686 Patron categories table
687 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
689 **Question**: What are the possible codes for the category types?
705 .. _messaging-preferences-label:
707 Messaging preferences
708 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
710 **Question**: What are the possible codes in the message\_attribute\_id
711 field in the borrower\_message\_preferences table?
715 - 2 = advanced notice
725 .. _runtime-parameters-label:
728 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
730 **Question**: Is there a way to filter my custom SQL reports before they
733 **Answer**: If you feel that your report might be too resource intensive
734 you might want to consider using runtime parameters to your query.
735 Runtime parameters basically make a filter appear before the report is
736 run to save your system resources.
738 There is a specific syntax that Koha will understand as 'ask for values
739 when running the report'. The syntax is <<Question to
740 ask\|authorized\_value>>.
742 - The << and >> are just delimiters. You must put << at the beginning
743 and >> at the end of your parameter
745 - The 'Question to ask' will be displayed on the left of the string to
748 - The authorized\_value can be omitted if not applicable. If it
749 contains an authorized value category, or branches or itemtype or
750 categorycode or biblio\_framework, a list with the Koha authorized
751 values will be displayed instead of a free field Note that you can
752 have more than one parameter in a given SQL Note that entering
753 nothing at run time won't probably work as you expect. It will be
754 considered as "value empty" not as "ignore this parameter". For
755 example entering nothing for : "title=<<Enter title>>" will display
756 results with title='' (no title). If you want to have to have
757 something not mandatory, use "title like <<Enter title>>" and enter a
758 % at run time instead of nothing
762 - SELECT surname,firstname FROM borrowers WHERE branchcode=<<Enter
763 patrons library\|branches>> AND surname like <<Enter filter for
764 patron surname (% if none)>>
766 - SELECT \* FROM items WHERE homebranch = <<Pick your
767 branch\|branches>> and barcode like <<Partial barcode value here>>
769 - SELECT title , author FROM biblio WHERE frameworkcode=<<Enter the
770 frameworkcode\|biblio\_framework>>
774 To generate a date picker calendar to the right of the field when
775 running a report you can use the 'date' keyword like this: <<Enter
782 You have to put "%" in a text box to 'leave it blank'. Otherwise, it
783 literally looks for "" (empty string) as the value for the field.
787 In addition to using any authorized value code to generate a
788 dropdown, you can use the following values as well: Framework codes
789 (biblio\_framework), Branches (branches), Item Types (itemtypes) and
790 Patron Categories (categorycode). For example a branch pull down
791 would be generated like this <<Branch\|branches>>
795 .. _results-limited-label:
798 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
800 **Question**: When I download my report it's limited to 10,000 results,
801 how do I get all of the results to download?
803 **Answer**: There is a limit of 10,000 records put on SQL statements
804 entered in Koha. To get around this you want to add 'LIMIT 100000' to
805 the end of your SQL statement (or any other number above 10,000.
810 --------------------------
812 .. _advanced-search-label:
815 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
817 .. _scan-indexes-label:
820 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
822 **Question**: What does 'scan indexes' on the advanced search page mean?
824 **Answer**: When you choose an index, enter a term, click 'scan indexes'
825 and do the search, Koha displays the searched term and the following
826 terms found in this index with the number of corresponding records That
827 is search is not made directly in the catalog, but first in the indexes
828 It works only for one index at once, and only with no limit in Location
829 (All libraries needed)
831 .. _searching-for-terms-that-start-with-a-character-label:
833 Searching for terms that start with a character
834 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
836 **Question**: How do I search for all titles that start with the letter
839 **Answer**: You can choose to search for things that start with a
840 character or series of characters by using the CCL 'first-in-subfield'
842 - example: ti,first-in-subfield=C
844 .. _wildcard-searching-label:
847 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
849 **Question**:What is the difference between a keyword search using the
850 '\*' (asterisk) versus a keyword search using the '%' (percent)? Both
851 work in the catalog, but return different sets. Why?
853 **Answer**: A wildcard is a character (\*,?,%,.) that can be used to
854 represent one or more characters in a word. Two of the wildcard
855 characters that can be used in Koha searches are the asterisk ('\*') and
856 the percent sign ('%'). However, these two characters act differently
857 when used in searching.
859 The '\*' is going to force a more exact search of the first few
860 characters you enter prior to the '\*'. The asterisk will allow for an
861 infinite number of characters in the search as long as the first few
862 characters designated by your search remain the same. For example,
863 searching for authors using the term, Smi\*, will return a list that may
864 include Smith, Smithers, Smithfield, Smiley, etc depending on the
865 authors in your database.
867 The '%' will treat the words you enter in the terms of "is like". So a
868 search of Smi% will search for words like Smi. This results in a much
869 more varied results list. For example, a search on Smi% will return a
870 list containing Smothers, Smith, Smelley, Smithfield and many others
871 depending on what is your database.
873 The bottom line in searching with wildcards: '\*' is more exact while
874 '%' searches for like terms.
876 .. _title-searching-label:
879 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
881 **Question**: Why does my Zebra title search for 'Help' not turn up 'The
882 help' in the first pages of results?
884 **Answer**: When doing a title search, you actually want to search for
885 the title (i.e., 'the help' rather than just 'help'), and it will bubble
886 right up to the top. If you're just searching for 'help' then the
887 relevance ranking is going to affect the results you see.
889 When it comes to relevance in Zebra, here's what's happening. First, the
890 search is done. If you search for the title "help", then any title that
891 has "help" in it comes back. Then from those records, separately, it
892 does relevance on the \*whole\* record. The more your word appears, the
893 more relevant, and some MARC tags are worth more points than others. So
894 a self-help book with 505 notes where "help" appears a \*lot\* will be
895 at the top, regardless of keyword or title.
897 But when you add a \*second word\*, that helps it figure things out, as
898 it's weighing the relevance of both words and the phrase. Because of the
899 way relevance works, if you search "the help", then "the help" or "the
900 help I need" are more relevant than "the way to help", because they
901 appear together in order. Likewise, "help the girl" would be lower
902 relevance, because it's out of order, and "help for the homeless" would
903 be lower still, as they're out of order, and apart.
905 The moral of the story is that single word searches, particularly on
906 common words, will always struggle a bit; it can't evaluate relevance
907 well, because you've not given it enough input.
909 .. _reset-the-zebra-index-label:
911 Reset the Zebra index
912 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
914 Run the following commands to reset the authorities and biblios Zebra
919 $ zebraidx -c /etc/koha/zebradb/zebra-authorities-dom.cfg -g iso2709 -d authorities init
920 $ zebraidx -c /etc/koha/zebradb/zebra-biblios.cfg -g iso2709 -d biblios init
922 If you are running a package install then you'll want to run the
923 following commands to reset the authorities and biblios Zebra indices
928 $ sudo zebraidx -c /etc/koha/sites/YOURLIBRARY/zebra-authorities-dom.cfg -g iso2709 -d authorities init
929 $ sudo zebraidx -c /etc/koha/sites/YOURLIBRARY/zebra-biblios.cfg -g iso2709 -d biblios init
931 Replacing YOURLIBRARY with your Koha installation name.
933 .. _enhanced-content-label:
936 ------------------------------------------
938 .. _frbrizing-content-label:
941 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
943 **Question:**\ At our public library we are running a Koha installation
944 and we've tried to turn on all the nice functionalities in Koha such as
945 the frbrising tool, but do not get the same result as Nelsonville public
948 **Answer:**\ In fact, this feature is quite tricky to make that right.
949 First it looks at XISBN service. And then search in your database for
950 that ISBN. So both XISBN and your internal ISBN (in biblio table) have
951 to be normalized. You could therefore use the script
952 misc/batchupdateISBNs.pl (it removes all the - in your local ISBNs)
954 .. _faq-amazon-label:
959 .. _all-amazon-content-label:
962 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
964 **Question**: I have all of the Amazon preferences turned on and have
965 entered both of my keys, but none of the content appears in my system,
968 **Answer**: Amazon's API checks your server time on all requests and if
969 your server time is not set properly requests will be denied. To resolve
970 this issue be sure to set your system time appropriately. Once that
971 change in made Amazon content should appear immediately.
973 On Debian the the command is *date -s "2010-06-30 17:21"* (with the
974 proper date and time for your timezone).
976 .. _system-administration-label:
978 System administration
979 --------------------------------------
981 .. _errors-in-zebra-cron-label:
984 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
986 **Question**: I am noticing some errors in the
987 koha-zebradaemon-output.log file. When new records are added it takes a
988 bit longer to index than we think they should. Running rebuild zebra is
989 often faster. Zebra ends up indexing and search works, but I am
990 concerned about the errors. Any ideas?
992 **Answer**: Rebuild\_zebra.pl -r deletes all of the files in the Zebra
993 db directories (such as reci-0.mf) and then recreates them. Thus,
994 permissions will be lost, and the files will be owned by the user who
995 ran rebuild\_zebra.pl. If one rebuilds the zebra indexes as root, the
996 daemons, which typically run under the user Koha, will not be able to
997 update the indexes. Thus, it's important then that the zebra rebuilds
998 are put in the cronjob file of the user Koha, and not root. Also
999 important is that other users, such as root, don't manually execute
1002 If one desires that another user be able to execute rebuild\_zebra.pl,
1003 he should be given the permission to execute 'sudo -u Koha
1004 .../rebuild\_zebra.pl,' (if you want to do this, you also have to edit
1005 the sudoers file to pass the PERL5LIB variable with the env\_keep option
1006 as by default sudo strips away almost all environment variables). Or, as
1007 root user, one can use a simple 'su koha' and then the rebuild\_zebra.pl
1010 I've also tried to set the sticky bit on rebuild\_zebra.pl, but for
1011 whatever reason it didn't seem to work due to some problem with the
1012 PERL5LIB variable that I wasn't able to figure. That seems to me the
1013 easiest thing to do, if anybody has any idea how to make it work. If it
1014 worked and were the default, I think it would help folks to avoid a
1015 great deal of the problems that come up with zebra.
1017 .. _making-z39.50-target-public-label:
1019 Making Z39.50 target public
1020 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1022 **Question**: Could someone tell me the exact steps I need to take to
1023 configure Zebra to expose my Koha 3 db as a public Z39.50 service?
1025 **Answer**: Edit the KOHA\_CONF file that your Koha is using. Uncomment
1026 the publicserver line like:
1028 <!-- <listen id="publicserver" >tcp:@:9999</listen> -->
1032 <listen id="publicserver" >tcp:@:9999</listen>
1034 Then restart zebasrv and connect on the port specified (9999).
1036 .. _shelving-location-authorized-values-label:
1038 Shelving location authorized values
1039 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1041 **Question**: When editing an item, the new shelving location I created
1042 is not showing up by default in the items where I assigned it to.
1044 **Answer**: This is because you created the new shelving location with a
1045 code value of 0 (zero) Just FYI the system interprets authorized values
1046 of 0 as equaling a null so when you edit a record in cataloging where
1047 the authorized value in a field was assigned where the code was 0, the
1048 value displays as null in the item editor (or MARC editor) instead of
1049 the value the library meant it to be.
1051 .. _why-do-i-need-authorized-values?-label:
1053 Why do I need authorized values?
1054 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1056 **Question**: Why would I want to define authorized values for MARC
1059 **Answer**: Authorized values create a 'controlled vocabulary' for your
1060 staff. As an example, let us assume that your Koha installation is used
1061 by several libraries, and you use MARC 21. You might want to restrict
1062 the 850a MARC subfield to the institution codes for just those
1063 libraries. In that case, you could define an authorized values category
1064 (perhaps called "INST") and enter the institution codes as the
1065 authorized values for that category.
1069 Koha automatically sets up authorized value categories for your item
1070 types and branch codes, and you can link these authorized values to
1071 MARC subfields when you set up your MARC tag structure.
1073 .. _how-do-i-clean-up-the-sessions-table?-label:
1075 How do I clean up the sessions table?
1076 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1078 **Question**: Is there a periodic job that can be run to cull old
1079 sessions from the table? We don't want to backup all the useless session
1082 **Answer**: You can run :ref:`cleanup database cron job <clean-up-database-label>`.
1084 Or just before doing a backup command (mysqldump), you can truncate
1089 mysql -u<kohauser -p<password <koha-db-name -e 'TRUNCATE TABLE sessions'
1094 ---------------------------
1096 .. _barcode-scanners-label:
1099 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1101 **Question**: What barcode scanners have been known to work with Koha?
1103 **Answer**: The simple rule of thumb is, does it act like a keyboard
1104 device?, if so, it will work. (i.e. can you take the scanner, scan a
1105 barcode and have it show up in a text editor, if so, it will work.)
1107 The main points to check are that it connects to your PC conveniently
1108 (can be USB or "keyboard wedge" which means it connects in line with the
1109 keyboard, which is useful with older computers), and that it scans the
1110 barcode type that you are using.
1112 It is a good idea to test some 'used' barcodes if you have any, to see
1113 whether the scanner can read scuffed or slightly wrinkled ones
1114 successfully. Most scanners are capable of reading several barcode types
1115 - there are many, and the specification should list the ones it can
1116 read. You may need to adjust settings slightly, such as prefix and
1117 suffix characters, or whether you want to send an 'enter' character or
1120 One more tip - some can be set 'always on' and may come with a stand,
1121 some have triggers under the handle, some have buttons on top, some are
1122 held like a pen. Think about the staff working with the hardware before
1123 choosing, as a button in the wrong place can be very awkward to use.
1128 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
1130 .. _printers-used-by-koha-libraries-label:
1132 Printers used by Koha libraries
1133 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1135 - POS-X receipt printer
1137 - Star Micronics printer (exact model unknown) with a generic/plain
1140 - Star SP2000 (Nelsonville)
1142 - Star TSP-100 futurePRINT (Geauga)
1144 - "I know there have been a lot of questions on receipt printers so
1145 I thought I'd pass on my findings. We have been testing the Star
1146 TSP-100 futurePRINT. I found this print to be VERY easy to
1147 configure for Koha. I was even able to customize the print job by
1148 adding our system logo (a .gif) to the top of every receipt. Also
1149 with a bitmap created in Paint was able to add a message at the
1150 bottom of each receipt with the contact information, hours and
1151 website for the library that the materials were checked out at."
1153 - Epson TM 88 IIIP thermal receipt printers
1157 - 1x1 labels using a Dymolabelwriter printer
1159 .. _braille-support-label:
1162 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1164 **Question**: Are there any braille embosser or printer which has
1165 inbuilt braille converter and it is accessible with UNIX environment?
1167 **Answer**: You may want to look into BRLTTY
1168 (http://www.emptech.info/product_details.php?ID=1232).
1170 .. _additional-support-label:
1173 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1175 - http://www.nexpresslibrary.org/go-live/configure-your-receipt-printers/