1 .. include:: images.rst
3 .. _administration-label:
8 .. _basic-parameters-label:
11 -----------------------------------
13 *Get there:* More > Administration
17 Configure all 'parameters' in the order they appear.
22 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
24 When setting up your Koha system you will want to add information for
25 every library that will be sharing your system. This data is used in
26 several areas of Koha.
28 - *Get there:* More > Administration > Basic Parameters > Libraries
30 When visiting this page you are presented with a list of the libraries that have already been added to the system.
35 .. _adding-a-library-label:
38 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
44 - The top of the form asks for some basics about the library
48 - The library code should not contain any spaces and be 10 or fewer
49 characters. This code will be used as a unique identifier in the
52 - The name will be displayed on the OPAC wherever the library name
53 displays to the public and should be a name that makes sense to
56 - Next you can enter basic contact info about the branch
59 .. screenshot is missing the OPAC info box
61 - The address and contact fields can be used to make notices custom
64 - The email address field is not required, but it should be filled
65 for every library in your system
69 Be sure to enter a library email address to make sure that
70 notices are sent to and from the right address
72 - If you'd like you can enter a different 'Reply-To' email address.
73 This is the email address that all replies will go to.
77 If you do not fill in this value Koha will use the address
78 in the :ref:`ReplytoDefault` preference
80 - If you'd like you can also enter a different 'Return-Path' email
81 address. This is the email address that all bounced messages will
86 If you do not fill in this value Koha will use the address
87 in the :ref:`ReturnpathDefault`
90 - If the URL field is populated then the library name will be linked
91 in the holdings table on the OPAC
95 - The OPAC Info box is for you to put information about the library
96 that will appear in the OPAC when the branch name is moused over
101 - IP Address does not have be filled in unless you plan on limiting
102 access to your staff client to a specific IP Address
106 An IP address is required if you have enabled
109 - If this library has a specific `MARC organization code <http://www.loc.gov/marc/organizations/orgshome.html>`_, you can enter it here. If left blank, the code entered in the :ref:`MARCOrgCode` preference will be used for this library.
111 - Finally, if you have any notes you can put them here. These will
116 Of the fields listed, only 'Library code' and 'Name' are required
118 .. _editing/deleting-a-library-label:
120 Editing/deleting a library
121 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
123 You will be unable to delete any library that has patrons or items
128 Each library will have an 'Edit' link to the right of it. Click this
129 link to edit/alter details associated with the library in question.
133 You will be unable to edit the 'Library code'
135 .. _library-groups-label:
138 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
140 Library groups are used in searches to limit the search to a group of
141 libraries (for example in a neigbourhood).
143 - *Get there:* More > Administration > Basic Parameters > Library groups
145 When visiting this page you are presented with a list of the groups
146 that have already been added to the system.
150 .. _adding-a-group-label:
153 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
155 Click the 'Add Group' button at the top of the screen
159 - Give the group a title and a description. Only the title is mandatory
160 as it will show up in the staff client and in the OPAC. The description
161 is only used in this page to give an idea of what the group is used for.
163 - You can limit staff from seeing other groups' patrons by checking the
164 box next to the 'Limit patron data access by group' option.
168 This can be overriden with the :ref:`user permission view_borrower_infos_
169 from_any_libraries <patron-permissions-defined-label>`.
171 - If you would like the group to show up in the library pulldown menu at the
172 top of the OPAC (with :ref:`OpacAddMastheadLibraryPulldown` set to 'Add')
173 and on the advanced search page you can check the 'Use for OPAC search
176 - If you want the group to appear in the library pulldown in the staff
177 client advanced search, check the 'Use for staff search groups' box.
181 .. _adding-a-library-to-a-group-label:
183 Adding a library to a group
184 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
186 Click on the 'Add library' button next to the group to add a library to
187 this group. You will be presented with a list of the libraries that are
188 not already in the group.
192 .. _adding-a-sub-group-label:
195 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
197 If your system is very large, you can create sub-groups. Click on the
198 'Actions' button next to the group and select the 'Add a sub-group'
199 option. Fill in the title and the description (optional) of the sub-group.
200 The features will be inherited from the parent group.
204 .. _deleting-a-group-label:
207 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
209 To delete a group, click on the 'Actions' button next to the group and select
216 .. _item-types-label:
219 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
221 Koha allows you to organize your collection by item types and collection
224 - *Get there:* More > Administration > Basic parameters > Item types
226 Item types typically refer to the material type (book, cd, dvd, etc),
227 but can be used in any way that works for your library.
231 .. _adding-item-types-label:
234 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
236 To add a new item type, simply click the 'New item type' button at the
237 top of the Item types page.
241 - In the 'Item type' field, enter a short code for your item type (maximum
244 - The description is the plain text definition of the item type (for
245 those with multiple languages installed you can translate the item
246 type description in to all of those languages using the 'Translate in
247 to other languages' link)
249 - Item types and can grouped together for searching at the same time.
250 For example you can put DVDs and Bluray in to a group called Movie
251 and then they can be searched together. These groups are defined in
252 the ITEMTYPECAT authorized value.
254 - You can choose to have an image associated with your item type
256 - You can choose from a series of image collections
258 - You can link to a remote image
260 - Or you can just have no image associated with the item type
264 To have your item type images appear in the OPAC you need to
265 set :ref:`noItemTypeImages` to 'Show'
267 - *Get there:*\ More > Administration > Global system preferences
268 > :ref:`Administration <administration-label>`
270 - For items that you are suppressing from the OPAC you can hide their
271 item type from being searched in the OPAC
273 - For items that do not circulate, check the 'Not for loan' options
275 - Items marked 'Not for loan' will appear in the catalog, but cannot
276 be checked out to patrons
278 - For items that you charge a rental fee for, enter the total fee you
279 charge in the 'Rental charge' field. This will charge the patron on checkout.
283 Do not enter symbols in this field, only numbers and decimal
284 points (ex. $5.00 should be entered as 5 or 5.00)
286 - You can add a default replacement cost for this type of item. If left
287 blank, the replacement price of the item itself will be charged to the
288 user when the item is lost.
291 Do not enter symbols in this field, only numbers and decimal
292 points (ex. $5.00 should be entered as 5 or 5.00)
295 - You can also add a processing fee that will be added to the replacement cost.
299 Do not enter symbols in this field, only numbers and decimal
300 points (ex. $5.00 should be entered as 5 or 5.00)
303 - If you would like a message or alert to appear when items of this
304 type are checked in you can enter that in the 'Checkin message' box
308 - The Checkin message type can be a Message or an Alert. The only
309 difference between these two is the styling. By default a Message
314 and an Alert is yellow.
318 - Some SIP devices need you to use a SIP-specific media type instead of
319 Koha's item type (usually lockers and sorters need this media type),
320 if you use a device like this you'll want to enter the SIP media
323 - When finished, click 'Save changes'
327 All fields, with the exception of the 'Item type' will be
328 editable from the Item types list
330 - Your new item type will now appear on the list
334 .. _editing-item-types-label:
337 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
339 Each item type has an Edit button beside it. To edit an item simply
340 click the 'Edit' link.
344 You will not be able to edit the code you assigned as the 'Item
345 type' but you will be able to edit the description for the item.
347 .. _deleting-item-types-label:
350 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
352 Each item has a Delete button beside it. To delete an item type, simply click
357 You will not be able to delete item types that are being used by
358 items within your system.
362 .. _authorized-values-label:
365 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
367 Authorized values can be used in several areas of Koha. One reason you
368 would add an authorized value category would be to control the values
369 that can be entered into MARC fields by catalogers.
371 - *Get there:* More > Administration > Basic parameters > Authorized
374 .. _existing-values-label:
377 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
379 Koha installs with pre-defined values that your library is likely to
380 use, for instance 'Lost'.
384 - Used for acquisitions statistical purposes
388 - Used for acquisitions statistical purposes
392 - Values for custom patron messages that appear on the circulation
393 screen and the OPAC. The value in the Description field should be
394 the message text and is limited to 200 characters.
400 - Values that can be entered to fill in the patron's sort 1 field
404 - Values that can be entered to fill in the patron's sort 2 field
408 - Collection codes (appears when cataloging and working with items)
410 - CONTROL\_NUM\_SEQUENCE
412 - Used to generate control numbers in the advanced cataloguing editor.
413 Enter a string ending with a number as the authorized value and use
414 the description to describe the type of number. For example: 'sprLib0001'
415 'Springfield library'. In the advanced editor this will activate a
416 new widget that will allow you to choose the type of number and
417 generate the next number in the sequence.
421 - Used in UNIMARC 102 $a
425 - Descriptions for items marked as damaged (appears when cataloging
426 and working with items)
430 - Departments are required by and will be used in the `Course
431 Reserves <#coursereserves>`__ module
435 - Used in French UNIMARC installations in field 995 $o to identify item status.
440 - General holdings: acquisition status designator :: This data
441 element specifies acquisition status for the unit at the time of
446 - General holdings: completeness designator
450 - Physical form designators
454 - General holdings: retention designator :: This data element
455 specifies the retention policy for the unit at the time of the
460 - General holdings: type of unit designator
464 - Frequencies used by the housebound module. They are displayed on
465 the housebound tab in the patron account in staff.
469 - Allows multiple Item types to be searched in a category. Categories can be
470 entered into the Authorized value ITEMTYPECAT. To combine Item types to this
471 category, enter this Search category to any Item types.
473 For example, an ITEMTYPECAT could be NEW, then in the Item type
474 for NEW BOOKS NEW DVDS, etc the search category could be added NEW.
475 This is helpful when a patron chooses the Search category of NEW, they could
476 get Koha to search multiple Item types with a single search.
480 - ISO 639-2 standard language codes
484 Shelving location (usually appears when adding or editing an item). LOC maps to
485 items.location in the Koha database.
489 Is the shelving cart location, used by
490 :ref:`InProcessingToShelvingCart` and
491 :ref:`ReturnToShelvingCart`
495 The location to be used for
496 :ref:`NewItemsDefaultLocation` (change
497 description as desired), also the location expected by
498 :ref:`InProcessingToShelvingCart`.
502 - Descriptions for the items marked as lost (appears when adding or
507 Values given to lost statuses should be numeric and not
508 alphabetical in order for statuses to appear properly
512 - Values for manual invoicing types
516 The value set as the Authorized value for the MANUAL\_INV
517 authorized value category will appear as the Description and
518 the Authorized value description will be used as the amount.
519 Enter monetary amounts in the description without currency
524 - A list of reasons displayed in the suggestion form on the OPAC.
528 - Reasons why a title is not for loan
532 Values given to lost statuses should be numeric and not
533 alphabetical in order for statuses to appear properly
537 Negative number values will still allow holds (use for on
538 order statuses for example) where as positive numbers will not
539 allow holds or checkouts. A value of 0 means 'for loan'.
541 - ORDER\_CANCELLATION\_REASON
543 - Reasons why an order might have been cancelled
547 - Populates a dropdown list of custom payment types when paying fines
551 - Function codes (author, editor, collaborator, etc.) used in UNIMARC 7XX $4
556 - French terms of relations
560 - A way to sort and filter your reports, the default values in this
561 category include the Koha modules (Accounts, Acquitisions,
562 Catalog, Circulation, Patrons)
568 - Can be used to further sort and filter your reports. This category
569 is empty by default. Values here need to include the authorized
570 value code from REPORT\_GROUP in the Description (OPAC) field to
571 link the subgroup to the appropriate group.
577 - Restricted status of an item
581 - Road types to be used in patron addresses
585 - Used when :ref:`creating <adding-item-types-label>` or
586 :ref:`editing <editing-item-types-label>` an item type to assign a SIP specific
587 media type for devices like lockers and sorters.
591 - List of patron suggestion reject or accept reasons (appears when
592 managing suggestions)
596 - List of Item types to display in a drop down menu on the Purchase suggestion
597 form on the OPAC. When creating the authorized values for SUGGEST_FORMAT,
598 enter a description into this form so it is visible on the OPAC to patrons.
602 - A list of additional custom status values for suggestions that can
603 be used in addition to the default values.
607 - Shelving control number
611 - Terms to be used in `Course Reserves <#coursereserves>`__ module.
612 Enter Terms that will show in the drop down menu when setting up a Course
613 reserve. (For example: Spring, Summer, Winter, Fall).
617 - Description of a withdrawn item (appears when adding or editing an
622 - A generic authorized value field that can be used anywhere you
623 need a simple yes/no pull down menu.
625 .. _add-new-authorized-value-category-label:
627 Add new authorized value category
628 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
630 In addition to the existing categories that come by default with Koha,
631 librarians can add their own authorized value categories to control data
632 that is entered into the system. To add a new category:
634 - Click 'New category'
638 - Limit your Category to 10 characters (something short to make it
639 clear what the category is for)
643 Category cannot have spaces or special characters other than
644 underscores and hyphens in it.
646 - When adding a new category you're asked to create at least one
649 - Enter a code for your Authorized value into the 'Authorized value'
654 Authorized value is limited to 80 characters and cannot
655 have spaces or special characters other than underscores
658 - Use the Description field for the actual value that will be
659 displayed. If you want something different to show in the OPAC,
660 enter a 'Description (OPAC)'
662 - If you would like to limit this authorized value category to only
663 specific libraries you can choose them from the 'Branches
664 limitation' menu. To have it show for all libraries just choose
665 'All branches' at the top of the list.
668 `StaffAuthorisedValueImages <#StaffAuthorisedValueImages>`__
669 and/or :ref:`AuthorisedValueImages` set to
670 show images for authorized values you can choose the image under
675 - Your new category and value will appear on the list of Authorized
680 .. _add-new-authorized-value-label:
682 Add new authorized value
683 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
685 New authorized values can be added to any existing or new category. To
688 - Click 'New authorized value for ...'
692 - Enter a code for your authorized value into the 'Authorized value'
697 Authorized value is limited to 80 characters and cannot have
698 spaces or special characters other than underscores and
701 - Use the Description field for the actual value that will be
702 displayed. If you want something different to show in the OPAC, enter
703 a 'Description (OPAC)'
705 - If you would like to limit this authorized value category to only
706 specific libraries you can choose them from the 'Branches limitation'
707 menu. To have it show for all libraries just choose 'All branches' at
711 `StaffAuthorisedValueImages <#StaffAuthorisedValueImages>`__ and/or
712 :ref:`AuthorisedValueImages` set to show images
713 for authorized values you can choose the image under 'Choose an icon'
717 - The new value will appear in the list along with existing values
721 .. _patrons-&-circulation-label:
723 Patrons and circulation
724 -------------------------------------
726 Settings for controlling circulation and patron information.
728 .. _patron-categories-label:
731 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
733 Patron categories allow you to organize your patrons into different
734 roles, age groups, and patron types.
736 - *Get there:* More > Administration > Patrons and circulation > Patron
741 Patrons are assigned to one of six main categories:
745 - Most common patron type, usually used for a general 'Patron'
750 - Children patrons can have a guardian to be attached to them.
754 - Librarians (and library workers) should be assigned the staff
755 category so that you can :ref:`set their
756 permissions <patron-permissions-label>` and give them access to the
761 - Organizational patrons are organizations. Organizations can be
762 used as guarantors for Professional patrons.
766 - Professional patrons can be linked to Organizational patrons
770 - This patron type is used strictly for statistical purposes, such
771 as in house use of items.
773 .. _adding-a-patron-category-label:
775 Adding a patron category
776 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
778 To add a new patron category click 'New category' at the top of the page
782 - The 'Category code' is an identifier for your new code.
786 The category code is limited to 10 characters (numbers and
791 This field is required in order to save your patron category.
792 If left blank you will be presented with an error.
796 - Enter a plain text version of the category in the 'Description'
801 This field is required in order to save your patron category.
802 If left blank you will be presented with an error.
806 - Enrollment period (in months) should be filled in if you have a
807 limited enrollment period for your patrons (eg. Student cards expire
808 after 9 months or until a specific date)
812 You cannot enter both a month limit and a date until. Choose
813 to enter either one or the other.
817 This field is required in order to save your patron category.
818 If left blank you will be presented with an error.
822 - Some patron categories can have a minimum age (in years) requirement
823 associated with them, enter this age in the 'Age required'
827 This value will only be checked if
828 :ref:`BorrowerMandatoryField` defines
829 the dateofbirth as a required field on the patron record
831 - Patron categories can also have a maximum age (in years) associated
832 with them (such as children), enter this age in the 'Upperage limit'
836 This value will only be checked if
837 :ref:`BorrowerMandatoryField` defines
838 the dateofbirth as a required field on the patron record
840 - If you charge a membership fee for your patrons (such as those who
841 live in another region) you can enter that in the 'Enrollment fee'
846 Only enter numbers and decimals in this field
850 Depending on your value for the
851 :ref:`FeeOnChangePatronCategory`
852 preference this fee will be charged on patron renewal as well
853 as when they are first enrolled.
855 - If you want your patron to receive overdue notices, set the 'Overdue
856 notice required' to 'Yes'
858 - You can decide on a patron category basis if lost items are shown in
859 the staff client by making a choice from the 'Lost items in staff
866 Note that this is only applicable in the staff client, so
867 changing this value on patron categories who do not have
868 access to the staff client won't make any difference
870 - If you charge patrons for placing holds on items, enter the fee
871 amount in the 'Hold fee' field.
875 Only enter numbers and decimals in this field
877 - In the 'Category type' field choose one of the six main parent
884 This field is required in order to save your patron category.
885 If left blank you will be presented with an error.
889 - The Branch limitations let you limit this patron category to only
890 some branches in your library system. Select 'All branches' if you
891 would like any library to be able to use this category.
893 - You can decide if this patron category is blocked from performing
894 actions in the OPAC if their card is expired using the next option.
895 By default it will follow the rule set in the
896 :ref:`BlockExpiredPatronOpacActions`
901 - Next you can choose the default privacy settings for this patron
902 category. This setting can be edited by the patron via the OPAC if
903 you allow it with the :ref:`OPACPrivacy` system
908 - You can set the preference for checking the patron's circulation history
909 when checking out an item. The default value for this is set in the
910 :ref:`CheckPrevCheckout` system preference. This setting can be
911 overridden on a per-patron basis in their :ref:`individual file <add-a-new-patron>`.
913 - Finally you can assign advanced messaging preferences by default to a
918 Requires that you have
919 :ref:`EnhancedMessagingPreferences`
922 - These defaults will be applied to new patrons that are added to
923 the system. They will not edit the preferences of the existing
924 patrons. Also, these can be changed for individual patrons, this
925 setting is just a default to make it easier to set up messages for
930 After setting the default for the patron category you can
931 force those changes to all existing patrons by running the
932 *borrowers-force-messaging-defaults* script found in the
933 *misc/maintenance* folder. Ask your system administrator
934 for assistance with this script.
936 .. _circulation-and-fine-rules-label:
938 Circulation and fines rules
939 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
941 These rules define how your items are circulated, how/when fines are
942 calculated and how holds are handled.
944 - *Get there:* More > Administration > Patrons and circulation >
945 Circulation and fines rules
947 The rules are applied from most specific to less specific, using the
948 first found in this order:
950 - same library, same patron category, same item type
952 - same library, same patron category, all item types
954 - same library, all patron categories, same item type
956 - same library, all patron categories, all item types
958 - default (all libraries), same patron category, same item type
960 - default (all libraries), same patron category, all item types
962 - default (all libraries), all patron categories, same item type
964 - default (all libraries), all patron categories, all item types
966 The :ref:`CircControl` and
967 :ref:`HomeOrHoldingBranch` also come in to play when
968 figuring out which circulation rule to follow.
970 - If CircControl is set to "the library you are logged in at" circulation
971 rules will be selected based on the library you are logged in at
973 - If CircControl is set to "the library the patron is from" circulation rules
974 will be selected based on the patron's library
976 - If CircControl is set to "the library the item is from" circulation rules
977 will be selected based on the item's library where
978 HomeOrHoldingBranch chooses if item's home library is used or holding
981 - If :ref:`IndependentBranches` is set to 'Prevent'
982 then the value of HomeOrHoldingBranch is used in figuring out if the
983 item can be checked out. If the item's home library does not match
984 the logged in library, the item cannot be checked out unless you are
985 a :ref:`superlibrarian <patron-permissions-defined-label>`.
989 At the very least you will need to set a default circulation rule.
990 This rule should be set for all item types, all libraries and all
991 patron categories. That will catch all instances that do not match a
992 specific rule. When checking out if you do not have a rule for all
993 libraries, all item types and all patron categories then you may see
994 patrons getting blocked from placing holds.
996 .. _defining-circulation-rules-label:
998 Defining circulation rules
999 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1001 Using the issuing rules matrix you can define rules that depend on
1002 patron category/item type combos. To set your rules, choose a library from the
1003 pull down (or 'Standard rules for all libraries' if you want to apply these rules to all
1008 From the matrix you can choose any combination of patron categories and
1009 item types to apply the rules to
1013 - First choose which patron category you'd like the rule to be applied
1014 to. If you leave this to 'All' it will apply to all patron categories
1016 - Choose the item type you would like this rule to apply to. If you
1017 leave this to 'All' it will apply to all item types
1019 - Add notes about your circulation rule into the notes field. This can
1020 be helpful to remember why and when something was last changed.
1022 - Limit the number of items a patron can have checked out at the same
1023 time by entering a number in the 'Current checkouts allowed' field.
1025 - If you're allowing :ref:`OnSiteCheckouts` then you
1026 may also want to set a limit on the number of items patron's can have
1031 This setting also depends on the
1032 :ref:`ConsiderOnSiteCheckoutsAsNormalCheckouts`
1035 - Define the period of time an item can be checked out to a patron by
1036 entering the number of units (days or hours) in the 'Loan period'
1039 - Choose which unit of time, days or hours, that the loan period and
1040 fines will be calculated in in the 'Unit' column
1042 - You can also define a hard due date for a specific patron category
1043 and item type. The hard due date offers three options:
1045 - Exactly on: The due date of any item checked out with this rule
1046 will be set to the hard due date.
1048 - Before: Koha will calculate the normal loan period. If the calculated
1049 due date would be after or on the hard due date, the hard due date
1050 will be used instead.
1052 - After: Koha will calculate the normal loan period. If the calculated
1053 due date would be before the hard due date, the hard due date will
1056 - 'Fine amount' should have the amount you would like to charge for
1061 Enter only numbers and decimal points (no currency symbols).
1063 - Enter the 'Fine charging interval' in the unit you set (ex. charge
1064 fines every 1 day, or every 2 hours). The :ref:`finesCalendar`system
1065 preference controls wether the days the library is closed will be taken
1066 into account or not.
1068 - 'When to charge' is most handy in libraries that have a fine charging
1069 interval of more than 1 day.
1071 - End of interval: Given a grace period of 2 days and a fine interval of 7 days,
1072 the first fine will appear 7 days after the due date, it will
1073 always take one fine interval (7 days), before the first fine
1076 - Start of interval: Given a grace period of 2 days and a fine interval of 7 days,
1077 the first fine will appear 2 days after the due date and the
1078 second fine 7 days after the due date.
1080 - The 'Fine grace period' is the period of time an item can be overdue
1081 before you start charging fines. The :ref:`FinesIncludeGracePeriod`
1082 system preference controls if the grace period will be included when
1083 calculating the fine or not.
1087 This can only be set for the Day unit, not in Hours
1089 - The 'Overdue fines cap' is the maximum fine per item for this patron
1090 and item type combination.
1094 If this field is left blank then Koha will not put a limit on
1095 the fines this item will accrue. A maximum fine amount can be
1096 set using the :ref:`MaxFine` system preference.
1098 - If you would like to prevent overcharging patrons for a lost items,
1099 you can check the box under 'Cap fine at replacement price.' This
1100 will prevent the patron's fines from going above the replacement
1105 If the 'Overdue fines cap' is also set, the fine will be the
1106 lesser of the two, if both apply to the given overdue
1109 - If your library 'fines' patrons by suspending their account you can
1110 enter the number of days their fine should be suspended in the
1111 'Suspension in days' field.
1115 This can only be set for the Day unit, not in Hours-
1117 - You can also define the maximum number of days a patron will be
1118 suspended in the 'Max suspension duration' setting-
1120 - Next decide if the patron can renew this item type and if so, enter
1121 how many times they can renew it in the 'Renewals allowed' box.
1123 - If you're allowing renewals you can control how long the renewal loan
1124 period will be (in the units you have chosen) in the 'Renewal period'
1127 - If you're allowing renewals you can control how soon before the due
1128 date patrons can renew their materials with the 'No renewals before'
1131 - Items can be renewed at any time if this value is left blank.
1132 Otherwise items can only be renewed if the item is due after the
1133 number in units (days/hours) entered in this box.
1135 - To control this value on a more granular level please set the
1136 :ref:`NoRenewalBeforePrecision`
1139 - You can enable automatic renewals for certain items/patrons if you'd
1140 like. This will renew automatically following your circulation rules
1141 unless there is a hold on the item.
1145 You will need to enable the :ref:`automatic renewal cron
1146 job <automatic-renewal-label>` for this to work.
1150 This feature needs to have the "no renewal before" column
1151 filled in or it will auto renew everyday after the due date.
1153 - If you are using automatic renewals, you can use the 'No automatic
1154 renewals after' to limit the time a patron can have the item independent:
1155 Exampple: Don't allow automatic renewals after a checkout period of 80 days.
1157 - Similar to the hard due date setting, you can also stop automatic renwals
1158 after a specific date using the 'No automatic renwal after (hard limit)'
1161 - If the patron can place holds on this item type, enter the total
1162 numbers of items (of this type) that can be put on hold in the 'Holds
1165 - You can also set a daily limit on the number of holds a patron can place.
1167 - While the two settings before limit the holds that can be placed across
1168 various records, the next setting is used to limit the number of holds
1169 that can be placed on one record at the same time.
1170 Example: For fiction books you might want to allow only one item to be placed
1171 on hold at the same time by the same user. But for serials where items
1172 represent different issues more than one hold at the same time is fine.
1174 - Next you can decide how the availability of items influences the ability
1175 to place a hold. The 'On shelf holds allowed' option has three settings:
1177 - Yes: This will allow to place holds on items at all times. It doesn't
1178 matter if they are available or checked out.
1180 - If any unavailable: This will allow to place a hold as soon as one
1181 or more items of the record are checked out. It doesn't matter if
1182 there are still one or more items available on the shelf.
1184 - If all unavailable: This will allow to place a hold as soon as all
1185 items on the record are checked out that could fill the hold. This is
1186 especially useful for libraries that don't offer the service of getting items
1187 placed on hold off the shelf for patrons.
1189 - You can also decide if patrons are allowed to place item specific
1190 holds on the item type in question. The options are:
1192 - Allow: Will allow patrons the option to choose next available or
1195 - Don't allow: Will only allow patrons to choose next available item.
1197 - Force: Will only allow patrons to choose a specific item.
1199 - If you want to allow patrons to be able to place article requests, you
1203 If you want to use the article request functionality
1204 you need to enable it using the :ref:`ArticleRequests` system
1205 preference and configure the form using the other related preferences.
1207 - Finally, if you charge a `rental fee <#rentalcharge>`__ for the item
1208 type and want to give a specific patron type a discount on that fee,
1209 enter the percentage discount (without the % symbol) in the 'Rental
1212 When finished, click 'Save' to save your changes. To modify a rule,
1213 simply click the 'Edit' link at the beginning or at the end of the row
1214 and edit the values that appear filled in at the bottom of the form.
1218 If you would like to delete your rule, click the 'Delete' link at the beginning
1219 or at the end of the rule row.
1221 To save time you can clone rules from one library to another by choosing
1222 the clone option above the rules matrix. Please note that this will overwrite
1223 all rules already configured for that library.
1227 After choosing to clone you will be presented with a confirmation
1232 .. _default-checkouts-and-hold-policy-label:
1234 Default checkout, hold, and return policy
1235 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1237 You can set a default maximum number of checkouts, a default maximum number
1238 of holds and a hold policy that
1239 will be used if none is defined below for a particular item type or
1240 category. This is the fall back rule for defaults.
1244 From this menu you can set a default to apply to all item types and
1245 patrons in the library if no other option is set in the forms below.
1247 - In 'Total current checkouts allowed' enter the total number of items
1248 patrons can have checked out at one time
1250 - In 'Total current on-site checkouts allowed' enter the total number
1251 of items patrons can have checked out on site at a time
1252 (:ref:`OnSiteCheckouts` needs to be set to 'Enable')
1254 - In 'Maximum total holds allowed (count)' enter the total number
1255 of pending holds patrons can have at the same time.
1257 - Control where patrons can place holds from using the 'Hold Policy'
1260 - From Any Library: Patrons from any library may put this item on
1261 hold. (default if none is defined)
1263 - From Home Library: Only patrons from the item's home library may
1264 put this book on hold.
1266 - No Holds Allowed: No patron may put this book on hold.
1268 - Control if there is a limit to filling a hold based on the item's
1273 - item's home library
1275 - item's holding library
1279 The patron's home library should not affect whether a patron
1280 can place the hold, instead the hold will only be fillable
1281 when an item matching the pickup location becomes available.
1283 - Control where the item returns to once it is checked in
1287 - Item returns to issuing branch
1291 - When an item floats it stays where it was checked in and does
1292 not ever return 'home'
1294 - Once your policy is set, you can unset it by clicking the 'Unset'
1295 link to the right of the rule
1297 .. _default-checkouts-and-hold-by-category-label:
1299 Default checkout and hold policy by patron cateogry
1300 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1302 For this library, you can specify the maximum number of checkouts,
1303 on-site checkouts and holds that a patron of a given category can have,
1304 regardless of the item type.
1310 If the total amount of checkouts, on-site checkout and holds
1311 for a given patron category is left blank, no limit applies,
1312 except possibly for a limit you define in the circulation rules above.
1314 For example, if you have a rule in the matrix that says Board patrons
1315 are allowed 10 books and 5 DVDs but you want to make it so that Board
1316 patrons only have a total of 12 things checked out at once. If you enter
1317 12 here and the patron has 10 books out already they will only be
1318 allowed 2 DVDs to equal the 12 total they're allowed.
1320 .. _item-fee-refund-on-return-label:
1322 Default lost item fee refund on return policy
1323 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1325 Here, you can specify the default policy for lost item fees on return.
1326 This policy will apply to this library. This rule is to be used with the
1327 :ref:`RefundLostOnReturnControl <refundlostonreturncontrol-label>`
1330 .. _item-hold-policies-label:
1332 Default holds policy by item type
1333 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1335 For this library, you can edit hold and return policies for a given item
1336 type, regardless of the patron's category.
1340 The various hold policies have the following effects:
1342 - From any library: Patrons from any library may put this item on hold.
1343 (default if none is defined)
1345 - From home library: Only patrons from the item's home library may put
1348 - No holds allowed: No patron may put this book on hold.
1352 Note that if the system preference
1353 :ref:`AllowHoldPolicyOverride` set to
1354 'allow', these policies can be overridden by your circulation staff.
1358 These policies are based on the patron's home branch, not the branch
1359 that the reserving staff member is from.
1361 Control if there is a limit to filling a hold based on the item's
1366 - item's home library
1368 - item's holding library
1372 The patron's home library should not affect whether a patron can
1373 place the hold, instead the hold will only be fillable when an
1374 item matching the pickup location becomes available.
1376 The various return policies have the following effects:
1378 - Item returns home: The item will prompt the librarian to transfer the
1379 item to its home library
1383 If the :ref:`AutomaticItemReturn`
1384 preference is set to automatically transfer the items home,
1385 then a prompt will not appear
1387 - Item returns to issuing branch: The item will prompt the librarian to
1388 transfer the item back to the library where it was checked out
1392 If the :ref:`AutomaticItemReturn`
1393 preference is set to automatically transfer the items home,
1394 then a prompt will not appear
1396 - Item floats: The item will not be transferred from the branch it was
1397 checked in at, instead it will remain there until transferred
1398 manually or checked in at another branch
1400 For example you might allow holds at your libraries but not what New
1401 items or DVDs to be placed on hold by other branches so you can set the
1402 'Hold policy' to 'From home library' so that those items can only be
1403 placed on hold if the items' owning library and the patron's home
1404 library are the same. You can also block holds completely on specific
1405 item types from this form. This is also how you can set up floating item
1406 types and types that remain with their home library.
1408 .. _patron-attribute-types-label:
1410 Patron attribute types
1411 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1413 Patron attributes can be used to define custom fields to associate with
1414 your patron records. In order to enable the use of custom fields you
1415 need to set the :ref:`ExtendedPatronAttributes`
1418 - *Get there:* More > Administration > Patrons and circulation > Patron
1421 A common use for this field would be for a student ID number or a
1422 Driver's license number.
1426 .. _adding-patron-attributes-label:
1428 Adding patron attributes
1429 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1431 To add a new patron attribute type, click the 'New patron attribute
1432 type' button at the top of the page
1436 - In the 'Patron attribute type code', enter a short code to identify
1441 This field is limited to 10 characters (numbers and letters
1446 This setting cannot be changed after an attribute is defined
1448 - In the 'Description' field, enter a longer (plain text) explanation
1449 of what this field will contain
1451 - Check the box next to 'Repeatable' to let a patron record have
1452 multiple values of this attribute.
1456 This setting cannot be changed after an attribute is defined
1458 - If 'Unique identifier' is checked, the attribute will be a unique
1459 identifier which means, if a value is given to a patron record, the
1460 same value cannot be given to a different record.
1462 - Unique attributes can be used as match points on the :ref:`patron
1463 import tool <patron-import-label>`
1467 This setting cannot be changed after an attribute is defined
1469 - Check 'Allow password' to make it possible to associate a password
1470 with this attribute.
1472 - Check 'Display in OPAC' to display this attribute on a patron's
1473 details page in the OPAC.
1475 - Check 'Searchable' to make this attribute searchable in the staff
1478 - Check 'Display in check-out' to make this attribute visible in the
1479 patron's short detail display on the left of the checkout screen and
1484 - Authorized value category; if one is selected, the patron record
1485 input page will only allow values to be chosen from the authorized
1488 - You will first need to add an authorized value list for it to
1491 - *Get there:*\ More > Administration > Basic parameters >
1492 :ref:`Authorized values <authorized-values-label>`
1496 an authorized value list is not enforced during batch patron
1499 - If you would like this attribute to only be used by specific branches
1500 you can choose those branches from the 'Branches limitation' list.
1501 Choose 'All branches' to show it for all libraries.
1505 Note that items with locations already set on them will not be
1506 altered. The branch limitation only limits the choosing of an
1507 authorized value based on the home branch of the current staff
1508 login. All authorized values for item records (LOC, LOST,
1509 CCODE, etc) will show in the OPAC for all patrons.
1511 - If you'd like to only show this attribute on patrons of one type
1512 choose that patron type from the 'Category' pull down
1514 - If you have a lot of attributes it might be handy to group them so
1515 that you can easily find them for editing. If you create an
1516 :ref:`Authorized value <authorized-values-label>` for PA\_CLASS it will show
1517 in the 'Class' pull down and you can then change your attributes page
1518 to have sections of attributes
1522 - Click Save to save your new attribute
1524 Once added your attribute will appear on the list of attributes and also
1525 on the patron record add/edit form
1529 If you have set up classes for organizing attributes they will appear
1530 that way on the add/edit patron form
1534 .. _editing/deleting-patron-attributes-label:
1536 Editing/deleting patron attributes
1537 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1539 Each patron attribute has an edit and a delete link beside it on the
1542 Some fields in the attribute will not be editable once created:
1544 - Patron attribute type code
1550 You will be unable to delete an attribute if it's in use.
1554 .. _library-transfer-limits-label:
1556 Library transfer limits
1557 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1559 Limit the ability to transfer items between libraries based on the
1560 library sending, the library receiving, and the collection code
1563 - *Get there:* More > Administration > Patrons and circulation > Library
1566 These rules only go into effect if the preference
1567 :ref:`UseBranchTransferLimits <usebranchtransferlimits-&-branchtransferlimitstype-label>` is set to
1570 Before you begin you will want to choose which library you are setting
1575 Transfer limits are set based on the collections codes you have applied
1576 via the :ref:`Authorized value <authorized-values-label>` administration area.
1580 Collection codes will appear as tabs above the checkboxes:
1584 Check the boxes for the libraries that you accept checkins from for the
1585 item type you have selected at the top (in the example below - FIC)
1589 In the above example, Centerville library will allow patrons to return
1590 items from all libraries except Liberty and Franklin to their branch.
1592 .. _transport-cost-matrix-label:
1594 Transport cost matrix
1595 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1597 The transport cost matrix lets a library system define relative costs to
1598 transport books to one another. In order for the system to use this
1599 matrix you must first set the
1600 :ref:`UseTransportCostMatrix` preference to
1605 The transport cost matrix takes precedence in controlling where
1606 holds are filled from, if the matrix is not used then Koha checks
1607 the :ref:`StaticHoldsQueueWeight <staticholdsqueueweight,-holdsqueueskipclosed-&-randomizeholdsqueueweight-label>`.
1609 Costs are decimal values between some arbitrary maximum value (e.g. 1 or
1610 100) and 0 which is the minimum (no) cost. For example, you could just
1611 use the distance between each library in miles as your 'cost', if that
1612 would accurately reflect the cost of transferring them. Perhaps post
1613 offices would be a better measure. Libraries sharing a post office would
1614 have a cost of 1, adjacent post offices would have a cost of 2, etc.
1616 To enter transport costs simply click in the cell you would like to
1617 alter, uncheck the 'Disable' box and enter your 'cost'
1621 After entering in your cost, hit 'Enter' on your keyboard or click the
1622 'Save' button at the bottom of the matrix to save your changes.
1626 A NULL value will make no difference where the From and To libraries
1627 are the same library. However, as a best practice, you should put a
1628 0 in there. For all other To/From combinations, a NULL value will
1629 cause that relationship to act as if it has been disabled. So, in
1630 summary, don't leave any of the values empty. It's best to always
1631 put a number in there ( even if you choose to disable that given
1634 .. _item-circulation-alerts-label:
1636 Item circulation alerts
1637 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1639 Libraries can decide if they want to have patrons automatically notified
1640 of circulation events (check ins and check outs).
1642 - *Get there:* More > Administration > Patrons and circulation > Item
1645 These preferences are set based on patron types and item types.
1649 These preference can be overridden by changes in the individual
1650 patron's messaging preferences.
1652 To set up circulation alerts:
1654 - Choose your library from the pull down at the top of the screen
1658 - To set preferences for all libraries, keep the menu set to
1661 - By default all item types and all patrons are notified of check ins
1662 and check outs. To change this, click on the item/patron type combo
1663 that you would like to stop notices for.
1667 - In the above example, Juveniles and Kids will not receive check
1670 .. _cities-and-towns-label:
1673 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1675 To standardize patron input you can define cities or towns within your
1676 region so that when new patrons are added librarians simply have to
1677 select the town from a list instead of having to type the town and zip
1678 (or postal) code information.
1680 - *Get there:* More > Administration > Patrons and circulation > Cities
1683 .. _adding-a-city-label:
1686 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1688 To add a new city, click the 'New city' button at the top of the page
1689 and enter the city name, state, zip/postal code and country.
1693 One you click Submit, your city will be saved and will be listed on the
1694 Cities and towns page
1698 Cities can be edited or deleted at any time.
1700 .. _viewing-cities-on-patron-add-form-label:
1702 Viewing cities on patron add form
1703 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1705 If you have defined local cities using the 'New city' form, then when
1706 adding or editing a patron record you will see those cities in a pull
1707 down menu to make city selection easy.
1711 This will allow for easy entry of local cities into the patron record
1712 without risking the potential for typos or mistaken zip/postal codes.
1714 .. _catalog-administration-label:
1716 Catalog administration
1717 --------------------------------------
1719 Set these controls before you start cataloging on your Koha system.
1721 - *Get there:* More > Administration > Catalog
1723 .. _marc-bibliographic-frameworks-label:
1725 MARC bibliographic frameworks
1726 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1728 Think of frameworks as templates for creating new bibliographic records.
1729 Koha comes with some predefined frameworks that can be edited or
1730 deleted, and librarians can create their own frameworks for content
1731 specific to their libraries.
1733 - *Get there:* More > Administration > Catalog > MARC bibliographic
1740 Do not delete or edit the Default framework since this will cause
1741 problems with your cataloging records - always create a new template
1742 based on the Default framework, or alter the other frameworks.
1744 After clicking the 'MARC structure' link to the right of each framework
1745 you can decide how many fields you want to see on one screen by using
1746 the pagination options at the top of the table.
1750 .. _add-new-framework-label:
1753 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1755 To add a new framework
1757 - Click 'New framework'
1761 - Enter a code of 4 or fewer characters
1763 - Use the Description field to enter a more detailed definition of
1768 - Once your framework is added click 'MARC structure' to the right of
1769 it on the list of frameworks
1773 - You will be asked to choose a framework to base your new framework
1774 off of, this will make it easier than starting from scratch
1776 - Once your framework appears on the screen you can edit or delete each
1777 field by following the instructions for :ref:`editing
1778 subfields <edit-framework-subfields-label>`
1780 .. _edit-existing-frameworks-label:
1782 Edit existing frameworks
1783 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1785 Clicking 'Edit' to the right of a framework will only allow you to edit
1786 the description for the framework:
1790 To make edits to the fields associated with the framework you must first
1791 click 'MARC Structure' and then follow the instructions for :ref:`editing
1792 subfields <edit-framework-subfields-label>`
1794 .. _add-subfields-to-frameworks-label:
1796 Add subfields to frameworks
1797 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1799 To add a field to a framework click the 'New tag' button at the top of
1800 the framework definition
1804 This will open up a blank form for entering MARC field data
1808 Enter the information about your new tag:
1810 - The 'Tag' is the MARC field number
1812 - The 'Label for lib' is the text that will appear in the staff client
1813 when in the cataloging module
1815 - The 'Label for OPAC' is the text that will appear in the OPAC when
1816 viewing the MARC version of the record
1818 - If this field can be repeated, check the 'Repeatable' box
1820 - If this field is mandatory, check the 'Mandatory' box
1822 - If you want this field to be a pull down with limited possible
1823 answers, choose which 'Authorized value' list you want to use
1825 When you're finished, click 'Save changes' and you will be presented
1830 To the right of the new field is a link to 'Subfields,' you will need to
1831 add subfields before this tag will appear in your MARC editor. The
1832 process of entering the settings for the new subfield is the same as
1833 those found in the :ref:`editing subfields in frameworks <edit-framework-subfields-label>`
1834 section of this manual.
1836 .. _edit-framework-subfields-label:
1838 Edit framework subfields
1839 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1841 Frameworks are made up of MARC fields and subfields. To make edits to
1842 most frameworks you must edit the fields and subfields. Clicking 'Edit'
1843 to the right of each subfield will allow you to make changes to the text
1844 associated with the field
1848 - Each field has a tag (which is the MARC tag) that is uneditable
1850 - The 'Label for lib' is what will show in the staff client if you
1851 have :ref:`advancedMARCeditor` set to display
1854 - The 'Label for OPAC' is what will show on the MARC view in the
1857 - If you check 'Repeatable' then the field will have a plus sign
1858 next to it allowing you to add multiples of that tag
1860 - If you check 'Mandatory' the record will not be allowed to save
1861 unless you have a value assigned to this tag
1863 - 'Authorized value' is where you define an :ref:`authorized
1864 value <authorized-values-label>` that your catalogers can choose from
1865 a pull down to fill this field in
1867 To edit the subfields associated with the tag, click 'Subfields' to the
1868 right of the tag on the 'MARC Structure' listing
1870 - From the list of subfields you can click 'Delete' to the right of
1871 each to delete the subfields
1873 - To edit the subfields click 'Edit subfields'
1875 - For each subfield you can set the following basic constraint values
1879 - Text for librarian
1881 - what appears before the subfield in the librarian interface
1885 - what appears before the field in the OPAC.
1887 - If left empty, the text for librarian is used instead
1891 - the field will have a plus sign next to it allowing you to add
1892 multiples of that tag
1896 - the record will not be allowed to save unless you have a value
1897 assigned to this tag
1901 - defines the tab where the subfield is shown. All subfields of a
1902 given field must be in the same tab or ignored. Ignore means
1903 that the subfield is not managed.
1905 - For each subfield you can set the following advanced constraint
1912 - defines what you want to appear in the field by default, this
1913 will be editable, but it saves time if you use the same note
1914 over and over or the same value in a field often.
1918 If you would like a field to fill in with today's date you
1919 can use the YYYY MM DD syntax in the 'Default value'. For
1920 example: a default of "Year:YYYY Month:MM Day:DD" (without
1921 quotes) will print as "Year:2015 Month:11 Day:30"
1925 - allows you to select from where this subfield is
1926 visible/hidden, simply check the boxes where you would like the
1927 field to show and uncheck the boxes where you would like it
1934 - if checked, it means that the subfield is a URL and can be
1939 - If you enter a field/subfield here (200b), a link appears after
1940 the subfield in the MARC Detail view. This view is present only
1941 in the staff client, not the OPAC. If the librarian clicks on
1942 the link, a search is done on the database for the
1943 field/subfield with the same value. This can be used for 2 main
1946 - on a field like author (200f in UNIMARC), put 200f here, you
1947 will be able to see all bib records with the same author.
1949 - on a field that is a link (4xx) to reach another bib record.
1950 For example, put 011a in 464$x, will find the serials that
1955 This value should not change after data has been added to
1956 your catalog. If you need to change this value you must ask
1957 your system administrator to run
1958 misc/batchRebuildBiblioTables.pl.
1962 - Koha is multi-MARC compliant. So, it does not know what the
1963 245$a means, neither what 200$f (those 2 fields being both the
1964 title in MARC21 and UNIMARC). So, in this list you can "map" a
1965 MARC subfield to its meaning. Koha constantly maintains
1966 consistency between a subfield and its meaning. When the user
1967 want to search on "title", this link is used to find what is
1968 searched (245 if you're MARC21, 200 if you're UNIMARC).
1970 - For each subfield you can set the following Other option values
1976 - means the value cannot by typed by the librarian, but must be
1977 chosen from a pull down generated by the :ref:`authorized
1978 value <authorized-values-label>` list
1980 - In the example above, the 504a field will show the MARC504
1981 authorized values when cataloging
1987 - means that the value is not free text, but must be searched in
1988 the authority/thesaurus of the selected category
1992 - means the value is calculated or managed by a plugin. Plugins
1993 can do almost anything.
1997 - For call numbers there is an option to add a call number
1998 browser next to the the call number subfield so that you can
1999 identify which call numbers are in use and which are not.
2000 Simply choose the cn\_browser.pl plugin. Learn more in the
2001 :ref:`cataloging section <adding-items-label>` of this manual.
2003 - If you'd like to let file uploads via cataloging you can
2004 choose the upload.pl plugin and this will allow you to
2005 :ref:`upload files to Koha to link to your
2006 records <attaching-files-to-records-label>`.
2008 - In UNIMARC there are plugins for every 1xx fields that are
2009 coded fields. The plugin is a huge help for cataloger! There
2010 are also two plugins (unimarc\_plugin\_210c and
2011 unimarc\_plugin\_225a that can "magically" find the editor
2012 from an ISBN, and the collection list for the editor)
2014 - To save your changes simply click the 'Save changes' button at the
2017 .. _import/export-frameworks-label:
2019 Import/export frameworks
2020 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2022 Next to each framework is a link to either import or export the
2025 .. _export-framework-label:
2028 ''''''''''''''''''''''''''''''''''''''''
2030 To export a framework simply click the 'Export' link to the right of
2035 When you click 'Export' you will be prompted to choose what format to
2040 A framework exported this way can be imported into any other Koha
2041 installation using the import framework option.
2043 .. _import-framework-label:
2046 ''''''''''''''''''''''''''''''''''''''''
2048 An easy way to create a new framework is to import one created for your
2049 or another Koha installation. This framework would need to be exported
2050 from the other system :ref:`using the instructions
2051 above <export-framework-label>` to be available for import here.
2053 To import a framework you first need to create :ref:`a new
2054 framework <add-new-framework-label>`. Once you have that framework, click
2055 'Import' to the right of the new framework.
2059 You will be prompted to find a file on your computer to import into the
2064 You will be asked to confirm your actions before the file is imported.
2068 As your file is uploaded you will see an image that will confirm that
2069 the system is working.
2073 Once your import is complete you will be brought to the framework edit
2074 tool where you can make any changes you need to the framework you
2077 .. _koha-to-marc-mapping-label:
2079 Koha to MARC mapping
2080 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2082 While Koha stores the entire MARC record, it also stores common fields
2083 for easy access in various tables in the database. Koha to MARC mapping
2084 is used to tell Koha where to find these values in the MARC record. In
2085 many cases you will not have to change the default values set by in this
2086 tool on installation, but it is important to know that the tool is here
2087 and can be used at any time.
2089 - *Get there:* More > Administration > Catalog > Koha to MARC mapping
2091 The table shows all the database fields that can be mapped to MARC fields.
2095 To add a new mapping, click on the 'Add' button to the right of the
2100 Write in the MARC field and subfield you would like to map, separated
2101 by a comma, to this Koha field and click the 'OK' button.
2105 It is possible to link more than one MARC field to a database field.
2106 For example, you could link both 260$a and 264$a to the biblioitems.place
2109 If you would like to clear the mapping for a database field, click
2110 the 'Remove' button.
2114 All changes are immediate.
2116 .. _keywords-to-marc-mapping-label:
2118 Keywords to MARC mapping
2119 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2121 This tool will allow you to map MARC fields to a set of predefined
2124 - *Get there:* More > Administration > Catalog > Keywords to MARC
2129 This tool only affects sites that are not using the XSLT
2132 At this time the only keyword in use is 'subtitle.'
2134 Using this tool you can define what MARC field prints to the detail
2135 screen of the bibliographic record using keywords. The following example
2136 will use the subtitle field.
2138 Using the framework pull down menu, choose the
2139 :ref:`Framework <marc-bibliographic-frameworks-label>` you would like to apply this rule to.
2140 For example, the subtitle for books can be found in the 245$b field.
2144 However the subtitle for DVDs appears in 245$p
2148 Using this tool you can tell Koha to print the right field as the
2149 subtitle when viewing the bibliographic record in the OPAC.
2153 This tool can be used to chain together pieces of the record as well. If
2154 you want the series number to show in the title on your search results
2155 you simply have to map 490 $v to 'subtitle' along with the 245 $b.
2159 Chain together the fields you want to show after the item title in
2160 the order in which you want them to appear.
2162 Future developments will include additional keyword assigned fields.
2164 .. _marc-bibliographic-framework-test-label:
2166 MARC bibliographic framework test
2167 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2169 Checks the MARC structure.
2171 - *Get there:* More > Administration > Catalog > MARC bibliographic
2174 If you change your MARC bibliographic framework it's recommended that
2175 you run this tool to test for errors in your definition.
2179 .. _authority-types-label:
2182 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2184 Authority types are basically MARC frameworks for authority records and
2185 because of that they follow the same editing rules found in the :ref:`MARC
2186 bibliographic frameworks <marc-bibliographic-frameworks-label>` section of this manual.
2187 Koha comes with many of the necessary authority frameworks already
2188 installed. To learn how to add and edit authority types, simply review
2189 the :ref:`MARC bibliographic frameworks` section of this manual.
2191 - *Get there:* More > Administration > Catalog > Authority types
2193 .. _classification-sources-label:
2195 Classification sources
2196 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2198 Source of classification or shelving scheme is an :ref:`Authorized
2199 values <authorized-values-label>` category that is mapped to field 952$2 and
2200 942$2 in Koha's MARC bibliographic frameworks and stored in the
2201 items.cn\_source field in the database.
2203 - *Get there:* More > Administration > Catalog > Classification sources
2207 Commonly used values of this field are:
2209 - ddc - Dewey Decimal Classification
2211 - lcc - Library of Congress Classification
2213 If you chose to install classification sources during Koha's
2214 installation, you would see other values too:
2216 - ANSCR (sound recordings)
2218 - SuDOC classification
2220 - Universal Decimal Classification
2222 - Other/Generic Classification
2224 .. _adding/editing-classification-sources-label:
2226 Adding/editing classification sources
2227 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2229 You can add your own source of classification by using the 'New
2230 classification source' button. To edit use the 'Edit' button.
2234 When creating or editing:
2236 - You will need to enter a code and a description.
2238 - Check the 'Source in use?' checkbox if you want the value to appear
2239 in the drop down list for this category.
2241 - Select the appropriate :ref:`filing rule <classification-filing-rules-label>` from the
2244 .. _classification-filing-rules-label:
2246 Classification filing rules
2247 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2249 Filing rules determine the order in which items are placed on shelves.
2251 Values that are pre-configured in Koha are:
2259 Filing rules are mapped to :ref:`Classification
2260 sources <adding/editing-classification-sources-label>`. You can setup new
2261 filing rules by using the 'New filing rule' button. To edit use the 'Edit'
2264 When creating or editing:
2266 - Enter a code and a description
2268 - Choose an appropriate filing routine - dewey, generic or lcc
2270 .. _record-matching-rules-label:
2272 Record matching rules
2273 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2275 Record matching rules are used when importing MARC records into Koha.
2277 - *Get there:* More > Administration > Catalog > Record matching rules
2279 The rules that you set up here will be referenced with you :ref:`Stage MARC
2280 records for import <stage-marc-records-for-import-label>`.
2282 It is important to understand the difference between 'Match points' and
2283 'Match checks' before adding new matching rules to Koha.
2285 Match points are the criteria that you enter that must be met in order
2286 for an incoming record to match an existing MARC record in your catalog.
2287 You can have multiple match points on an import rule each with its own
2288 score. An incoming record will be compared against your existing records
2289 ('one record at a time') and given a score for each match point. When
2290 the total score of the match points matches or exceeds the threshold
2291 given for the matching rule, Koha assumes a good match and
2292 imports/overlays according your specifications in the import process. An
2293 area to watch out for here is the sum of the match points. Double check
2294 that the matches you want will add up to a successful match.
2300 Match point on 020$a 1000
2302 Match point on 022$a 1000
2304 Match point on 245$a 500
2306 Match point on 100$a 100
2308 In the example above, a match on either the 020$a or the 022$a will
2309 result in a successful match. A match on 245$a title and 100$a author
2310 (and not on 020$a or 022$a) will only add up to 600 and not be a match.
2311 And a match on 020$a and 245$a will result in 1500 and while this is a
2312 successful match, the extra 500 point for the 245$a title match are
2313 superfluous. The incoming record successfully matched on the 020$a
2314 without the need for the 245$a match. However, if you assigned a score
2315 of 500 to the 100$a Match Point, a match on 245$a title and 100$a author
2316 will be considered a successful match (total of 1000) even if the 020$a
2319 Match checks are not commonly used in import rules. However, they can
2320 serve a couple of purposes in matching records. First, match checks can
2321 be used as the matching criteria instead of the match points if your
2322 indexes are stale and out of date. The match checks go right for the
2323 data instead of relying on the data in the indexes. (If you fear your
2324 indexes are out of date, a rebuild of your indexes would be a great idea
2325 and solve that situation!) The other use for a match check is as a
2326 'double check' or 'veto' of your matching rule. For example, if you have
2327 a matching rule as below:
2331 Match point on 020$a 1000
2333 Match check on 245$a
2335 Koha will first look at the 020$a tag/subfield to see if the incoming
2336 record matches an existing record. If it does, it will then move on to
2337 the Match Check and look directly at the 245$a value in the incoming
2338 data and compare it to the 245$a in the existing 'matched' record in
2339 your catalog. If the 245$a matches, Koha continues on as if a match was
2340 successful. If the 245$a does not match, then Koha concludes that the
2341 two records are not a match after all. The Match Checks can be a really
2342 useful tool in confirming true matches.
2344 When looking to create matching rules for your authority records the
2345 following indexes will be of use:
2347 +--------------------------+--------------------+
2348 | Index name | Matches MARC tag |
2349 +==========================+====================+
2350 | LC-cardnumber | 010$a |
2351 +--------------------------+--------------------+
2352 | Personal-name | 100$a |
2353 +--------------------------+--------------------+
2354 | Corporate-name-heading | 110$a |
2355 +--------------------------+--------------------+
2356 | Meeting-name | 111$a |
2357 +--------------------------+--------------------+
2358 | Title-uniform | 130$a |
2359 +--------------------------+--------------------+
2360 | Chronological-term | 148$a |
2361 +--------------------------+--------------------+
2362 | Subject-topical | 150$a |
2363 +--------------------------+--------------------+
2364 | Name-geographic | 151$a |
2365 +--------------------------+--------------------+
2366 | Term-genre-form | 155$a |
2367 +--------------------------+--------------------+
2369 Table: Authority indexes
2371 .. _adding-matching-rules-label:
2373 Adding matching rules
2374 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2376 To create a new matching rule :
2378 - Click 'New record matching rule'
2382 - Choose a unique name and enter it in the 'Matching rule code'
2385 - 'Description' can be anything you want to make it clear to you
2386 what rule you're picking
2388 - 'Match threshold' is the total number of 'points' a biblio must
2389 earn to be considered a 'match'
2391 - 'Record type' is the type of import this rule will be used for -
2392 either authority or bibliographic
2394 - Match points are set up to determine what fields to match on
2396 - 'Search index' can be found by looking at the ccl.properties file
2397 on your system which tells the zebra indexing what data to search
2398 for in the MARC data". Or you can review the index for standard
2399 index names used. :ref:`Koha Search Indexes`
2401 - 'Score' - The number of 'points' a match on this field is worth.
2402 If the sum of each score is greater than the match threshold, the
2403 incoming record is a match to the existing record
2405 - Enter the MARC tag you want to match on in the 'Tag' field
2407 - Enter the MARC tag subfield you want to match on in the
2410 - 'Offset' - For use with control fields, 001-009
2412 - 'Length' - For use with control fields, 001-009
2414 - Koha only has one 'Normalization rule' that removes extra
2415 characters such as commas and semicolons. The value you enter in
2416 this field is irrelevant to the normalization process.
2418 - 'Required match checks' - ??
2420 .. _sample-bibliographic-record-matching-rule-control-number-label:
2422 Sample bibliographic record matching rule: Control number
2423 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2427 - Match threshold: 100
2429 - Record type: Bibliographic
2433 If you'd like a rule to match on the 001 in authority records
2434 you will need the repeat all of these values and change just
2435 the record type to 'Authority record'
2437 - Matchpoints (just the one):
2439 - Search index: Control-number
2447 this field is for the control number assigned by the
2448 organization creating, using, or distributing the record
2456 - Normalization rule: Control-number
2458 - Required match checks: none (remove the blank one)
2462 .. _oai-sets-configuration-label:
2464 OAI sets configuration
2465 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2467 On this page you can create, modify and delete OAI-PMH sets
2469 .. _create-a-set-label:
2472 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2476 - Click on the link 'Add a new set'
2478 - Fill the mandatory fields 'setSpec' and 'setName'
2480 - Then you can add descriptions for this set. To do this click on 'Add
2481 description' and fill the newly created text box. You can add as many
2482 descriptions as you want.
2484 - Click on 'Save' button'
2486 .. _modify/delete-a-set-label:
2489 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2491 To modify a set, just click on the link 'Modify' on the same line of the
2492 set you want to modify. A form similar to set creation form will appear
2493 and allow you to modify the setSpec, setName and descriptions.
2495 To delete a set, just click on the link 'Delete' on the same line of the
2496 set you want to delete.
2498 .. _define-mappings-label:
2501 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2503 Here you can define how a set will be build (what records will belong to
2504 this set) by defining mappings. Mappings are a list of conditions on
2505 record content. A record only need to match one condition to belong to
2508 - Fill the fields 'Field', 'Subfield' and 'Value'. For example if you
2509 want to include in this set all records that have a 999$9 equal to
2510 'XXX'. Fill 'Field' with 999, 'Subfield' with 9 and 'Value' with XXX.
2512 - If you want to add another condition, click on 'OR' button and repeat
2517 To delete a condition, just leave at least one of 'Field', 'Subfield' or
2518 'Value' empty and click on 'Save'.
2522 Actually, a condition is true if value in the corresponding subfield
2523 is strictly equal to what is defined if 'Value'. A record having
2524 999$9 = 'XXX YYY' will not belong to a set where condition is 999$9
2527 And it is case sensitive : a record having 999$9 = 'xxx' will not belong
2528 to a set where condition is 999$9 = 'XXX'.
2530 .. _build-sets-label:
2533 ^^^^^^^^^^^^^^^^^^^^^^^^^^
2535 Once you have configured all your sets, you have to build the sets. This
2536 is done by calling the script misc/migration\_tools/build\_oai\_sets.pl.
2538 .. _item-search-fields-label:
2541 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2543 From here you can add custom search fields to the :ref:`item
2544 search <item-searching-label>` option in the staff client.
2548 To add a new search term simply click the 'New search field' button
2552 - Name is a field for you to identify the search term
2554 - Label is what will appear on the item search page
2556 - MARC field allows you to pick which field you'd like to search in
2558 - MARC subfield is the subfield you'd like to search in
2560 - Authorised values category can be used to turn this search field in
2561 to a pull down instead of a free text field
2563 Once your new field is added it will be visible at the top of this page
2564 and on the item search page
2568 .. _acquisitions-module-label:
2571 ----------------------------
2573 The Koha Acquisitions module provides a way for the library to record
2574 orders placed with vendors and manage purchase budgets.
2576 Before using the `Acquisitions Module <#acqmodule>`__, you will want to
2577 make sure that you have completed all of the set up.
2579 - *Get there:* More > Administration > Acquisitions
2581 .. _currencies-and-exchange-rates-label:
2583 Currencies and exchange rates
2584 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2586 If you place orders from more than one country you will want to input
2587 currency exchange rates so that your acquisitions module will properly
2590 - *Get there:* More > Administration > Acquisitions > Currencies and
2597 This data is not automatically updated, so be sure to keep it up to
2598 date so that your accounting is kept correct.
2600 The ISO code you enter will be used when importing MARC files via the
2601 staging tools, the tool will attempt to find and use the price of the
2602 currently active currency.
2604 The active currency is the main currency you use in your library. Your
2605 active currency will have a check mark in the 'Active' column. If you
2606 don't have an active currency you will see an error message telling you
2607 to choose an active currency.
2614 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2616 Budgets are used for tracking accounting values related to acquisitions.
2617 For example you could create a budget for the current year (ex. 2015)
2618 and then break that into :ref:`Funds` for different areas of the
2619 library (ex. Books, Audio, etc).
2621 - *Get there:* More > Administration > Acquisitions > Budgets
2623 When visiting the main budget administration you will see two tabs, one
2624 for active and one for inactive budgets.
2628 .. _adding-budgets-label:
2631 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2633 Budgets can either be created :ref:`from scratch <add-a-new-budget-label>`, by
2634 :ref:`duplicating the previous year's budget <duplicate-a-budget-label>` or by
2635 :ref:`closing a previous year's budget <close-a-budget-label>`.
2637 .. _add-a-new-budget-label:
2640 ''''''''''''''''''''''''''''''''''''
2642 If you haven't used Koha before for acquisitions then you'll need to
2643 start fresh with a new budget. To add a new budget click the 'New
2648 - Choose the time period this budget is for, whether it's an academic
2649 year, a fiscal year, a quarter, etc.
2651 - The description should be something that will help you identify the
2652 budget when ordering
2654 - In the amount box do not use any symbols, simply enter the amount of
2655 the budget with numbers and decimals.
2657 - Marking a budget active makes it usable when placing orders in the
2658 acquisitions module, even if the order is placed after the budget end
2659 date. This will allow you to record orders that were places in a
2660 previous budget period.
2662 - Locking a budget means that funds will not be able to be modified by
2665 Once you have made your edits, click the 'Save changes' button. You will
2666 be brought to a list of your existing budgets.
2670 .. _duplicate-a-budget-label:
2673 '''''''''''''''''''''''''''''''''''''''''
2675 To duplicate a budget from a previous year, click on the link for the
2676 budget name from the list of budgets
2680 On the screen listing the budget breakdown click the 'Edit' button at the
2681 top and choose to 'Duplicate budget'
2685 You can also click the 'Actions' button to the right of the budget and
2690 In both cases you will be presented with a form where you simply need to
2691 enter the new start and end date and save the budget.
2695 Check the box for 'Mark the original budget as inactive' if the original
2696 budget should no longer be used.
2698 Check the box for 'Set all funds to zero' if you wish the new budget to
2699 contain all the same fund structures as the previous budget but no
2700 allocations until you manually enter an amount in the fund.
2702 This will not only duplicate your budget, but all of the funds
2703 associated with that budget so that you can reuse budgets and funds from
2704 year to year and so that you can move unreceived orders and if desired
2705 unspent funds from a previous budget to the new budget.
2707 .. _close-a-budget-label:
2710 '''''''''''''''''''''''''''''''''
2712 Close a budget to move or roll over unreceived orders and if desired
2713 unspent funds from a previous budget to a new budget. Before closing
2714 your budget you might want to :ref:`duplicate the previous year's
2715 budget <duplicate-a-budget-label>` so that you have somewhere for the
2716 unreceived orders to roll to.
2718 Find the previous budget with unreceived orders on the Active budgets or
2719 the Inactive budgets tab and select 'Close' under 'Actions'.
2725 In order for the unreceived orders to be automatically moved to the
2726 new budget, the fund structures in the previous budget must exist in
2727 the new budget. Budgets without unreceived orders cannot be closed.
2729 When you select 'Close' you will be presented with a form.
2733 Use the 'Select a budget' drop down to choose the new budget for the
2736 Check the box for 'Move remaining unspent funds' to move the unspent
2737 amounts from the funds of the budget being closed to the selected
2740 Once you have made your choices, click the 'Move unreceived orders'
2741 button. You will be presented with a dialog box that says 'You have
2742 chosen to move all unreceived orders from 'Budget X' to 'Budget Y'. This
2743 action cannot be reversed. Do you wish to continue?' Budget X is the
2744 budget to be closed and Budget Y is the selected budget.
2748 If everything seems correct click 'OK' and the unreceived orders and, if
2749 selected, unspent funds will be moved.
2751 Wait until the 'Report after moving unreceived orders from budget X to
2752 Y' displays. This will list the order numbers which have been impacted
2753 (grouped by fund) and detail if the unreceived order was moved or if
2754 there was a problem. For example, if the new budget does not contain a
2755 fund with the same name as the previous budget, the order will not be
2765 - *Get there:* More > Administration > Acquisitions > Funds
2767 .. _add-a-fund-label:
2770 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2772 A fund is added to a budget.
2776 A :ref:`budget <adding-budgets-label>` must be defined before a fund can be
2779 To add a new fund click the 'New' button and then choose which budget you
2780 would like to add the fund to.
2784 In the form that appears you want to enter the basics about your fund.
2788 The three first fields are required, the rest are optional
2790 - Fund code is a unique identifier for your fund
2792 - The fund name should be something that librarians will understand
2794 - Amount should be entered with only numbers and decimals, no other
2797 - Warning at (%) or Warning at (amount) can be filled in to make Koha
2798 warn you before you spend a certain percentage or amount of your
2799 budget. This will prevent you from overspending.
2801 - You can choose to assign this fund to a librarian. Doing so will make
2802 it so that only that librarian can make changes to the fund
2804 - Choose which library will be using this fund
2806 - You can restrict who can order from this fund by choosing either the
2807 'owner', 'owner and users' or 'owner, users and library' from the
2808 'Restrict access to' menu
2814 Without an owner, the access restriction will be ignored, be
2815 sure to enter an owner as well as choose a restriction
2817 - Notes are simply for any descriptive notes you might want to add so
2818 that librarians know when to use this fund
2820 - Planning categories are used for statistical purposes. If you will be
2821 using the Asort1 and/or Asort2 authorised values lists to track your orders
2822 you need to select them when setting up the fund. Select the Asort1/Asort2
2823 option from the dropdown lists for the Statiscal 1 done on: and
2824 Statistical 2 done on: fields.
2826 - To learn more about planning categories, check out the :ref:`Planning category
2827 FAQ <planning-categories-label>`.
2829 When complete, click 'Submit' and you will be brought to a list of all
2830 of the funds for the budget.
2834 The monetary columns in the fund table break down as follows:
2836 1. Base-level allocated is the 'Amount' value you defined when creating
2839 2. Base-level ordered is the ordered amount for this fund (without child
2842 3. Total ordered is the base-level ordered for this fund and all its
2845 4. Base-level spent is the spent amount for this fund (without child
2848 5. Total spent is the base-level spent for this fund and all its child
2851 6. Base-level available is 1 - 2
2853 7. Total available is 1 - 3
2855 To the right of each fund you will find the 'Actions' button under which
2856 you will find the 'Edit,' 'Delete,' and 'Add child fund' options.
2860 A child fund simply a sub-fund of the fund listed. An example would be
2861 to have a fund for 'Fiction' and under that have a fund for 'New
2862 releases' and a fund for 'Science Fiction.' It is an optional way to
2863 further organize your finances.
2865 Funds with children will show with a small arrow to the left. Clicking
2866 that will show you the children funds.
2870 .. _budget-planning-label:
2873 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2875 When viewing the list of funds click the 'Planning' button and choose
2876 how you would like to plan to spend your budget.
2880 If you choose 'Plan by MONTHS' you will see the budgeted amount broken
2885 To hide some of the columns you can click the 'hide' link to the right
2886 (or below as in the screenshot above) the dates. To add more columns you
2887 can click the 'Show a column' link found below the 'Fund remaining'
2892 From here you can plan your budget spending by manually entering values
2893 or by clicking the 'Auto-fill row' button. If you choose to auto-fill
2894 the form the system will try to divide the amount accordingly, you may
2895 have to make some edits to split things more accurately.
2899 Once your changes are made, click the 'Save' button. If you would like
2900 to export your data as a CSV file you can do so by entering a file name
2901 in the 'Output to a file named' field and clicking the 'Output' button.
2905 .. _edi-accounts-label:
2908 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2910 From here you can set up the information needed to connect to your
2911 acquisitions vendors.
2915 Before you begin you will need at least one :ref:`Vendor set up in
2916 Acquisitions <add-a-vendor-label>`.
2918 To add account information click the 'New account' button.
2922 In the form that appears you will want to enter your vendor information.
2924 New account information
2926 Each vendor will have one account.
2928 .. _library-eans-label:
2931 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2933 A library EAN is the identifier the vendor gives the library to send
2934 back to them so they know which account to use when billing. One EDI
2935 account can have multiple EANs.
2937 To add an EAN click the 'New EAN' button.
2941 In the form that appears enter the information provided by your vendor.
2945 .. _additional-parameters-label:
2947 Additional parameters
2948 --------------------------------------------
2950 - *Get there:* More > Administration > Additional parameters
2952 .. _z39.50/sru-servers-label:
2955 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2957 Z39.50 is a client/server protocol for searching and retrieving
2958 information from remote computer databases, in short it's a tool used
2959 for copy cataloging.
2961 SRU- Search/Retrieve via URL - is a standard XML-based protocol for
2962 search queries, utilizing CQL - Contextual Query Language - a standard
2963 syntax for representing queries.
2965 Using Koha you can connect to any Z39.50 or SRU target that is publicly
2966 available or that you have the log in information to and copy both
2967 bibliographic and/or authority records from that source.
2969 - *Get there:* More > Administration > Additional parameters >
2972 Koha comes with a default list of Z39.50/SRU targets set up that you can
2973 add to, edit or delete
2977 To find additional Z39.50 targets you use IndexData's IRSpy:
2978 `http://irspy.indexdata.com <http://irspy.indexdata.com/>`__ or the
2979 Library of Congress's list of targets http://www.loc.gov/z3950/
2981 .. _add-a-z39.50-target-label:
2984 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2986 - From the main Z39.50 page, click 'New Z39.50 server'
2990 - 'Z39.50 server' should be populated with a name that will help you
2991 identify the source (such as the library name).
2993 - 'Hostname' will be the address to the Z39.50 target.
2995 - 'Port' tells Koha what port to listen on to get results from this
2998 - 'Userid' and 'Password' are only required for servers that are
3001 - Check the 'Preselected' box if you want this target to always be
3002 selected by default.
3004 - 'Rank' lets you enter where in the list you'd like this target to
3007 - If this is left blank the targets will be in alphabetical
3010 - 'Syntax' is the MARC flavor you use.
3012 - 'Encoding' tells the system how to read special characters.
3014 - 'Timeout' is helpful for targets that take a long while. You can
3015 set the timeout so that it doesn't keep trying the target if
3016 results aren't found in a reasonable amount of time.
3018 - 'Record type' lets you define if this is a bibliographic or an
3021 - 'XSLT file(s)' lets enter one or more (comma-separated) XSLT file
3022 names that you want to apply on the search results.
3024 - When retrieving records from external targets you may wish to
3025 automate some changes to those records. XSLT's allow you to do
3026 this. Koha ships with some sample XSLT files in the
3027 /koha-tmpl/intranet-tmpl/prog/en/xslt/ directory ready for use:
3029 - Del952.xsl: Remove items (MARC21/NORMARC)
3031 - Del995.xsl: Remove items (UNIMARC)
3033 - Del9LinksExcept952.xsl: Remove $9 links. Skip item fields
3036 - Del9LinksExcept995.xsl: Remove $9 links. Skip item fields
3039 .. _suggested-bibliographic-z39.50-targets-label:
3041 Suggested bibliographic Z39.50 targets
3042 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
3044 Koha libraries with open Z39.50 targets can share and find connection
3045 information on the Koha wiki:
3046 http://wiki.koha-community.org/wiki/Koha_Open_Z39.50_Sources. You can
3047 also find open Z39.50 targets by visiting IRSpy:
3048 http://irspy.indexdata.com.
3050 The following targets have been used successfully by other Koha
3051 libraries (in the Americas):
3053 - ACCESS PENNSYLVANIA 205.247.101.11:210 INNOPAC
3055 - CUYAHOGA COUNTY PUBLIC webcat.cuyahoga.lib.oh.us:210 INNOPAC
3057 - GREATER SUDBURY PUBLIC 216.223.90.51:210 INNOPAC
3059 - HALIFAX PUBLIC catalogue.halifaxpubliclibraries.ca:210 horizon
3061 - HALTON HILLS PUBLIC cat.hhpl.on.ca:210 halton\_hills
3063 - LIBRARY OF CONGRESS lx2.loc.gov: 210 LCDB
3065 - LONDON PUBLIC LIBRARY catalogue.londonpubliclibrary.ca:210 INNOPAC
3067 - MANITOBA PUBLIC library.gov.mb.ca:210 horizon
3069 - MILTON PL cat.mpl.on.ca:210 horizon
3071 - NATIONAL LIBRARY OF WALES cat.llgc.org.uk:210 default
3073 - NHUPAC 199.192.6.130:211 nh\_nhupac
3075 - OCEAN STATE LIBRARIES (RI) catalog.oslri.net:210 INNOPAC
3077 - OHIOLINK olc1.ohiolink.edu:210 INNOPAC
3079 - PUBCAT prod890.dol.state.vt.us:2300 unicorn
3081 - SAN JOAQUIN VALLEY PUBLIC LIBRARY SYSTEM (CA) hip1.sjvls.org:210
3084 - SEATTLE PUBLIC LIBRARY ZSERVER.SPL.ORG:210 HORIZON
3086 - TORONTO PUBLIC symphony.torontopubliclibrary.ca:2200 unicorn
3088 - TRI-UNI 129.97.129.194:7090 voyager
3090 - VANCOUVER PUBLIC LIBRARY z3950.vpl.ca:210 Horizon
3092 .. _suggested-authority-z39.50-targets-label:
3094 Suggested Authority Z39.50 Targets
3095 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
3097 The following targets have been used successfully by other Koha
3098 libraries (in the Americas):
3100 - LIBRARIESAUSTRALIA AUTHORITIES
3101 z3950-test.librariesaustralia.nla.gov.au:210 AuthTraining Userid:
3102 ANLEZ / Password: z39.50
3104 - LIBRARY OF CONGRESS NAME AUTHORITIES lx2.loc.gov:210 NAF
3106 - LIBRARY OF CONGRESS SUBJECT AUTHORITIES lx2.loc.gov:210 SAF
3108 .. _add-a-sru-target-label:
3111 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
3113 - From the main Z39.50/SRU page, click 'New SRU server'
3117 - 'Server name' should be populated with a name that will help you
3118 identify the source (such as the library name).
3120 - 'Hostname' will be the address to the Z39.50 target.
3122 - 'Port' tells Koha what port to listen on to get results from this
3125 - 'Userid' and 'Password' are only required for servers that are
3128 - Check the 'Preselected' box if you want this target to always be
3129 selected by default.
3131 - 'Rank' lets you enter where in the list you'd like this target to
3134 - If this is left blank the targets will be in alphabetical
3137 - 'Syntax' is the MARC flavor you use.
3139 - 'Encoding' tells the system how to read special characters.
3141 - 'Timeout' is helpful for targets that take a long while. You can
3142 set the timeout so that it doesn't keep trying the target if
3143 results aren't found in a reasonable amount of time.
3145 - 'Additional SRU options' is where you can enter additional options
3146 of the external server here, like sru\_version=1.1 or
3147 schema=marc21, etc. Note that these options are server dependent.
3149 - 'SRU Search field mapping' lets you add or update the mapping from
3150 the available fields on the Koha search form to the specific
3151 server dependent index names.
3153 - To further refine your searches, you could add the following
3154 index names to the SRU search field mappings. To do this, edit
3155 the server and click the Modify button next to this field.
3157 +---------------+---------------------------+
3158 | Title | dc.title |
3159 +---------------+---------------------------+
3160 | ISBN | bath.isbn |
3161 +---------------+---------------------------+
3162 | Any | cql.anywhere |
3163 +---------------+---------------------------+
3164 | Author | dc.author |
3165 +---------------+---------------------------+
3166 | ISSN | bath.issn |
3167 +---------------+---------------------------+
3168 | Subject | dc.subject |
3169 +---------------+---------------------------+
3170 | Standard ID | bath.standardIdentifier |
3171 +---------------+---------------------------+
3175 - 'XSLT file(s)' lets enter one or more (comma-separated) XSLT file
3176 names that you want to apply on the search results.
3178 - When retrieving records from external targets you may wish to
3179 automate some changes to those records. XSLT's allow you to do
3180 this. Koha ships with some sample XSLT files in the
3181 /koha-tmpl/intranet-tmpl/prog/en/xslt/ directory ready for use:
3183 - Del952.xsl: Remove items (MARC21/NORMARC)
3185 - Del995.xsl: Remove items (UNIMARC)
3187 - Del9LinksExcept952.xsl: Remove $9 links. Skip item fields
3190 - Del9LinksExcept995.xsl: Remove $9 links. Skip item fields
3193 .. _did-you-mean?-label:
3196 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3198 *Get there:* More > Administration > Additional parameters > Did you
3201 Koha can offer 'Did you mean?' options on searches based on values in
3202 your :ref:`authorities <authorities-label>`.
3206 Did you mean? only works in the OPAC at this time. The intranet
3207 options are here for future development.
3209 Using this page you can control which options Koha gives patrons on
3210 their search results.
3214 To turn on the 'Did you mean?' bar on your search results you need to
3215 check the box next to each plugin you would like to use. The two plugins
3216 you have to choose from are:
3218 - The ExplodedTerms plugin suggests that the user try searching for
3219 broader/narrower/related terms for a given search (e.g. a user
3220 searching for "New York (State)" would click the link for narrower
3221 terms if they're also interested in "New York (City)"). This is only
3222 relevant for libraries with highly hierarchical authority data.
3224 - The AuthorityFile plugin searches the authority file and suggests the
3225 user might be interested in bibs linked to the top 5 authorities
3227 If you want one plugin to take priority over another you simply drag it
3232 If you choose both plugins you will see several options at the top of
3237 If you choose just the AuthorityFile you'll see just authorities.
3241 .. _column-settings-label:
3244 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3246 This administration area will help you hide or display columns on fixed
3247 tables throughout the staff client.
3249 - *Get there:* Administration > Additional parameters > Column settings
3253 Clicking on the module you'd like to edit tables for will show you the
3254 options available to you.
3256 This area lets you control the columns that show in the table in
3257 question. If nothing is hidden you will see no check marks in the 'is
3258 hidden by default' column.
3262 And will see all of the columns when viewing the table on its regular
3267 If columns are hidden they will have checks in the 'is hidden by
3272 And hidden when you view the table.
3276 You can also toggle columns using the 'Show/hide columns' button in the
3277 top right of the page
3283 Any tables with columns listed here have the option to export to Excel, export to CSV,
3284 copy, or print within the table header
3286 .. _audio-alerts-label:
3289 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3291 If you have your :ref:`AudioAlerts` preference set to
3292 'Enable' you will be able to control the various alert sounds that Koha
3293 uses from this area.
3295 - *Get there:* More > Administration > Additional parameters > Audio
3298 Each dialog box in Koha has a CSS class assigned to it that can be used
3299 as a selector for a sound.
3303 You can edit the defaults by clicking the 'Edit' button to the right of
3308 You can assign alerts to other CSS classes in Koha by entering that
3309 information in the selector box. For example if you enter
3313 body:contains('Check in message')
3315 Then when you visit the checkin page you will hear an alert.
3317 Every page in Koha has a unique ID in the body tag which can be used to
3318 limit a sound to a specific page
3320 Any ID selector (where HTML contains id="name\_of\_id" ) and can also be
3321 a trigger as: #name\_of\_selector
3323 .. _sms-cellular-providers-label:
3325 SMS cellular providers
3326 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3330 This option will only appear if the
3331 :ref:`SMSSendDriver <smssenddriver,-smssendusername,-and-smssendpassword-label>` preference is set to 'Email'
3333 From here you can enter as many cellular providers as you need to send
3334 SMS notices to your patrons using the email protocol.
3338 Some examples in the US are:
3340 +---------------------+-----------------------------+
3341 | Mobile Carrier | SMS Gateway Domain |
3342 +=====================+=============================+
3343 | Alltel | sms.alltelwireless.com |
3344 +---------------------+-----------------------------+
3345 | AT&T | txt.att.net |
3346 +---------------------+-----------------------------+
3347 | Boost Mobile | sms.myboostmobile.com |
3348 +---------------------+-----------------------------+
3349 | Project Fi | msg.fi.google.com |
3350 +---------------------+-----------------------------+
3351 | Republic Wireless | text.republicwireless.com |
3352 +---------------------+-----------------------------+
3353 | Sprint | messaging.sprintpcs.com |
3354 +---------------------+-----------------------------+
3355 | T-Mobile | tmomail.net |
3356 +---------------------+-----------------------------+
3357 | U.S. Cellular | email.uscc.net |
3358 +---------------------+-----------------------------+
3359 | Verizon Wireless | vtext.com |
3360 +---------------------+-----------------------------+
3361 | Virgin Mobile | vmobl.com |
3362 +---------------------+-----------------------------+
3364 Table: SMS provider examples
3366 To add new providers enter the details in the form and click 'Add new'
3371 These options will appear in the OPAC for patrons to choose from on the
3372 :ref:`messaging tab <your-messaging-label>` if you have
3373 :ref:`EnhancedMessagingPreferences`
projects / kohadocs.git / blob