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'
136 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
138 Library groups are used in searches to limit the search to a group of
139 libraries (for example in a neigbourhood).
141 - *Get there:* More > Administration > Basic Parameters > Library groups
143 When visiting this page you are presented with a list of the groups
144 that have already been added to the system.
148 .. _adding-a-group-label:
151 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
153 Click the 'Add Group' button at the top of the screen
157 - Give the group a title and a description. Only the title is mandatory
158 as it will show up in the staff client and in the OPAC. The description
159 is only used in this page to give an idea of what the group is used for.
161 - You can limit staff from seeing other groups' patrons by checking the
162 box next to the 'Limit patron data access by group' option.
166 This can be overriden with the :ref:`user permission view_borrower_infos_
167 from_any_libraries <patron-permissions-defined-label>`.
169 - If you would like the group to show up in the library pulldown menu at the
170 top of the OPAC (with :ref:`OpacAddMastheadLibraryPulldown` set to 'Add')
171 and on the advanced search page you can check the 'Use for OPAC search
174 - If you want the group to appear in the library pulldown in the staff
175 client advanced search, check the 'Use for staff search groups' box.
179 .. _adding-a-library-to-a-group-label:
181 Adding a library to a group
182 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
184 Click on the 'Add library' button next to the group to add a library to
185 this group. You will be presented with a list of the libraries that are
186 not already in the group.
190 .. _adding-a-sub-group-label:
193 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
195 If your system is very large, you can create sub-groups. Click on the
196 'Actions' button next to the group and select the 'Add a sub-group'
197 option. Fill in the title and the description (optional) of the sub-group.
198 The features will be inherited from the parent group.
202 .. _deleting-a-group-label:
205 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
207 To delete a group, click on the 'Actions' button next to the group and select
214 .. _item-types-label:
217 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
219 Koha allows you to organize your collection by item types and collection
222 - *Get there:* More > Administration > Basic parameters > Item types
224 Item types typically refer to the material type (book, cd, dvd, etc),
225 but can be used in any way that works for your library.
229 .. _adding-item-types-label:
232 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
234 To add a new item type, simply click the 'New item type' button at the
235 top of the Item types page.
239 - In the 'Item type' field, enter a short code for your item type (maximum
242 - The description is the plain text definition of the item type (for
243 those with multiple languages installed you can translate the item
244 type description in to all of those languages using the 'Translate in
245 to other languages' link)
247 - Item types and can grouped together for searching at the same time.
248 For example you can put DVDs and Bluray in to a group called Movie
249 and then they can be searched together. These groups are defined in
250 the ITEMTYPECAT authorized value.
252 - You can choose to have an image associated with your item type
254 - You can choose from a series of image collections
256 - You can link to a remote image
258 - Or you can just have no image associated with the item type
262 To have your item type images appear in the OPAC you need to
263 set :ref:`noItemTypeImages` to 'Show'
265 - *Get there:*\ More > Administration > Global system preferences
266 > :ref:`Administration <administration-label>`
268 - For items that you are suppressing from the OPAC you can hide their
269 item type from being searched in the OPAC
271 - For items that do not circulate, check the 'Not for loan' options
273 - Items marked 'Not for loan' will appear in the catalog, but cannot
274 be checked out to patrons
276 - For items that you charge a rental fee for, enter the total fee you
277 charge in the 'Rental charge' field. This will charge the patron on checkout.
281 Do not enter symbols in this field, only numbers and decimal
282 points (ex. $5.00 should be entered as 5 or 5.00)
284 - You can add a default replacement cost for this type of item. If left
285 blank, the replacement price of the item itself will be charged to the
286 user when the item is lost.
289 Do not enter symbols in this field, only numbers and decimal
290 points (ex. $5.00 should be entered as 5 or 5.00)
293 - You can also add a processing fee that will be added to the replacement cost.
297 Do not enter symbols in this field, only numbers and decimal
298 points (ex. $5.00 should be entered as 5 or 5.00)
301 - If you would like a message or alert to appear when items of this
302 type are checked in you can enter that in the 'Checkin message' box
306 - The Checkin message type can be a Message or an Alert. The only
307 difference between these two is the styling. By default a Message
312 and an Alert is yellow.
316 - Some SIP devices need you to use a SIP-specific media type instead of
317 Koha's item type (usually lockers and sorters need this media type),
318 if you use a device like this you'll want to enter the SIP media
321 - When finished, click 'Save changes'
325 All fields, with the exception of the 'Item type' will be
326 editable from the Item types list
328 - Your new item type will now appear on the list
332 .. _editing-item-types-label:
335 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
337 Each item type has an Edit button beside it. To edit an item simply
338 click the 'Edit' link.
342 You will not be able to edit the code you assigned as the 'Item
343 type' but you will be able to edit the description for the item.
345 .. _deleting-item-types-label:
348 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
350 Each item has a Delete button beside it. To delete an item type, simply click
355 You will not be able to delete item types that are being used by
356 items within your system.
360 .. _authorized-values-label:
363 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
365 Authorized values can be used in several areas of Koha. One reason you
366 would add an authorized value category would be to control the values
367 that can be entered into MARC fields by catalogers.
369 - *Get there:* More > Administration > Basic parameters > Authorized
372 .. _existing-values-label:
375 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
377 Koha installs with pre-defined values that your library is likely to
378 use, for instance 'Lost'.
382 - Used for acquisitions statistical purposes
386 - Used for acquisitions statistical purposes
390 - Values for custom patron messages that appear on the circulation
391 screen and the OPAC. The value in the Description field should be
392 the message text and is limited to 200 characters.
398 - Values that can be entered to fill in the patron's sort 1 field
402 - Values that can be entered to fill in the patron's sort 2 field
406 - Collection codes (appears when cataloging and working with items)
410 - Used in UNIMARC 102 $a
414 - Descriptions for items marked as damaged (appears when cataloging
415 and working with items)
419 - Departments are required by and will be used in the `Course
420 Reserves <#coursereserves>`__ module
424 - Used in French UNIMARC installations in field 995 $o to identify item status.
429 - General holdings: acquisition status designator :: This data
430 element specifies acquisition status for the unit at the time of
435 - General holdings: completeness designator
439 - Physical form designators
443 - General holdings: retention designator :: This data element
444 specifies the retention policy for the unit at the time of the
449 - General holdings: type of unit designator
453 - Frequencies used by the housebound module. They are displayed on
454 the housebound tab in the patron account in staff.
458 - Allows multiple Item types to be searched in a category. Categories can be
459 entered into the Authorized value ITEMTYPECAT. To combine Item types to this
460 category, enter this Search category to any Item types.
462 For example, an ITEMTYPECAT could be NEW, then in the Item type
463 for NEW BOOKS NEW DVDS, etc the search category could be added NEW.
464 This is helpful when a patron chooses the Search category of NEW, they could
465 get Koha to search multiple Item types with a single search.
469 - ISO 639-2 standard language codes
473 Shelving location (usually appears when adding or editing an item). LOC maps to
474 items.location in the Koha database.
478 Is the shelving cart location, used by
479 :ref:`InProcessingToShelvingCart` and
480 :ref:`ReturnToShelvingCart`
484 The location to be used for
485 :ref:`NewItemsDefaultLocation` (change
486 description as desired), also the location expected by
487 :ref:`InProcessingToShelvingCart`.
491 - Descriptions for the items marked as lost (appears when adding or
496 Values given to lost statuses should be numeric and not
497 alphabetical in order for statuses to appear properly
501 - Values for manual invoicing types
505 The value set as the Authorized value for the MANUAL\_INV
506 authorized value category will appear as the Description and
507 the Authorized value description will be used as the amount.
508 Enter monetary amounts in the description without currency
513 - A list of reasons displayed in the suggestion form on the OPAC.
517 - Reasons why a title is not for loan
521 Values given to lost statuses should be numeric and not
522 alphabetical in order for statuses to appear properly
526 Negative number values will still allow holds (use for on
527 order statuses for example) where as positive numbers will not
528 allow holds or checkouts. A value of 0 means 'for loan'.
530 - ORDER\_CANCELLATION\_REASON
532 - Reasons why an order might have been cancelled
536 - Populates a dropdown list of custom payment types when paying fines
540 - Function codes (author, editor, collaborator, etc.) used in UNIMARC 7XX $4
545 - French terms of relations
549 - A way to sort and filter your reports, the default values in this
550 category include the Koha modules (Accounts, Acquitisions,
551 Catalog, Circulation, Patrons)
557 - Can be used to further sort and filter your reports. This category
558 is empty by default. Values here need to include the authorized
559 value code from REPORT\_GROUP in the Description (OPAC) field to
560 link the subgroup to the appropriate group.
566 - Restricted status of an item
570 - Road types to be used in patron addresses
574 - Used when :ref:`creating <adding-item-types-label>` or
575 :ref:`editing <editing-item-types-label>` an item type to assign a SIP specific
576 media type for devices like lockers and sorters.
580 - List of patron suggestion reject or accept reasons (appears when
581 managing suggestions)
585 - List of Item types to display in a drop down menu on the Purchase suggestion
586 form on the OPAC. When creating the authorized values for SUGGEST_FORMAT,
587 enter a description into this form so it is visible on the OPAC to patrons.
591 - A list of additional custom status values for suggestions that can
592 be used in addition to the default values.
596 - Shelving control number
600 - Terms to be used in `Course Reserves <#coursereserves>`__ module.
601 Enter Terms that will show in the drop down menu when setting up a Course
602 reserve. (For example: Spring, Summer, Winter, Fall).
606 - Description of a withdrawn item (appears when adding or editing an
611 - A generic authorized value field that can be used anywhere you
612 need a simple yes/no pull down menu.
614 .. _add-new-authorized-value-category-label:
616 Add new authorized value category
617 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
619 In addition to the existing categories that come by default with Koha,
620 librarians can add their own authorized value categories to control data
621 that is entered into the system. To add a new category:
623 - Click 'New category'
627 - Limit your Category to 10 characters (something short to make it
628 clear what the category is for)
632 Category cannot have spaces or special characters other than
633 underscores and hyphens in it.
635 - When adding a new category you're asked to create at least one
638 - Enter a code for your Authorized value into the 'Authorized value'
643 Authorized value is limited to 80 characters and cannot
644 have spaces or special characters other than underscores
647 - Use the Description field for the actual value that will be
648 displayed. If you want something different to show in the OPAC,
649 enter a 'Description (OPAC)'
651 - If you would like to limit this authorized value category to only
652 specific libraries you can choose them from the 'Branches
653 limitation' menu. To have it show for all libraries just choose
654 'All branches' at the top of the list.
657 `StaffAuthorisedValueImages <#StaffAuthorisedValueImages>`__
658 and/or :ref:`AuthorisedValueImages` set to
659 show images for authorized values you can choose the image under
664 - Your new category and value will appear on the list of Authorized
669 .. _add-new-authorized-value-label:
671 Add new authorized value
672 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
674 New authorized values can be added to any existing or new category. To
677 - Click 'New authorized value for ...'
681 - Enter a code for your authorized value into the 'Authorized value'
686 Authorized value is limited to 80 characters and cannot have
687 spaces or special characters other than underscores and
690 - Use the Description field for the actual value that will be
691 displayed. If you want something different to show in the OPAC, enter
692 a 'Description (OPAC)'
694 - If you would like to limit this authorized value category to only
695 specific libraries you can choose them from the 'Branches limitation'
696 menu. To have it show for all libraries just choose 'All branches' at
700 `StaffAuthorisedValueImages <#StaffAuthorisedValueImages>`__ and/or
701 :ref:`AuthorisedValueImages` set to show images
702 for authorized values you can choose the image under 'Choose an icon'
706 - The new value will appear in the list along with existing values
710 .. _patrons-&-circulation-label:
712 Patrons and circulation
713 -------------------------------------
715 Settings for controlling circulation and patron information.
717 .. _patron-categories-label:
720 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
722 Patron categories allow you to organize your patrons into different
723 roles, age groups, and patron types.
725 - *Get there:* More > Administration > Patrons and circulation > Patron
730 Patrons are assigned to one of six main categories:
734 - Most common patron type, usually used for a general 'Patron'
739 - Children patrons can have a guardian to be attached to them.
743 - Librarians (and library workers) should be assigned the staff
744 category so that you can :ref:`set their
745 permissions <patron-permissions-label>` and give them access to the
750 - Organizational patrons are organizations. Organizations can be
751 used as guarantors for Professional patrons.
755 - Professional patrons can be linked to Organizational patrons
759 - This patron type is used strictly for statistical purposes, such
760 as in house use of items.
762 .. _adding-a-patron-category-label:
764 Adding a patron category
765 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
767 To add a new patron category click 'New category' at the top of the page
771 - The 'Category code' is an identifier for your new code.
775 The category code is limited to 10 characters (numbers and
780 This field is required in order to save your patron category.
781 If left blank you will be presented with an error.
785 - Enter a plain text version of the category in the 'Description'
790 This field is required in order to save your patron category.
791 If left blank you will be presented with an error.
795 - Enrollment period (in months) should be filled in if you have a
796 limited enrollment period for your patrons (eg. Student cards expire
797 after 9 months or until a specific date)
801 You cannot enter both a month limit and a date until. Choose
802 to enter either one or the other.
806 This field is required in order to save your patron category.
807 If left blank you will be presented with an error.
811 - Some patron categories can have a minimum age (in years) requirement
812 associated with them, enter this age in the 'Age required'
816 This value will only be checked if
817 :ref:`BorrowerMandatoryField` defines
818 the dateofbirth as a required field on the patron record
820 - Patron categories can also have a maximum age (in years) associated
821 with them (such as children), enter this age in the 'Upperage limit'
825 This value will only be checked if
826 :ref:`BorrowerMandatoryField` defines
827 the dateofbirth as a required field on the patron record
829 - If you charge a membership fee for your patrons (such as those who
830 live in another region) you can enter that in the 'Enrollment fee'
835 Only enter numbers and decimals in this field
839 Depending on your value for the
840 :ref:`FeeOnChangePatronCategory`
841 preference this fee will be charged on patron renewal as well
842 as when they are first enrolled.
844 - If you want your patron to receive overdue notices, set the 'Overdue
845 notice required' to 'Yes'
847 - You can decide on a patron category basis if lost items are shown in
848 the staff client by making a choice from the 'Lost items in staff
855 Note that this is only applicable in the staff client, so
856 changing this value on patron categories who do not have
857 access to the staff client won't make any difference
859 - If you charge patrons for placing holds on items, enter the fee
860 amount in the 'Hold fee' field.
864 Only enter numbers and decimals in this field
866 - In the 'Category type' field choose one of the six main parent
873 This field is required in order to save your patron category.
874 If left blank you will be presented with an error.
878 - The Branch limitations let you limit this patron category to only
879 some branches in your library system. Select 'All branches' if you
880 would like any library to be able to use this category.
882 - You can decide if this patron category is blocked from performing
883 actions in the OPAC if their card is expired using the next option.
884 By default it will follow the rule set in the
885 :ref:`BlockExpiredPatronOpacActions`
890 - Next you can choose the default privacy settings for this patron
891 category. This setting can be edited by the patron via the OPAC if
892 you allow it with the :ref:`OPACPrivacy` system
897 - You can set the preference for checking the patron's circulation history
898 when checking out an item. The default value for this is set in the
899 :ref:`CheckPrevCheckout` system preference. This setting can be
900 overridden on a per-patron basis in their :ref:`individual file <add-a-new-patron>`.
902 - Finally you can assign advanced messaging preferences by default to a
907 Requires that you have
908 :ref:`EnhancedMessagingPreferences`
911 - These defaults will be applied to new patrons that are added to
912 the system. They will not edit the preferences of the existing
913 patrons. Also, these can be changed for individual patrons, this
914 setting is just a default to make it easier to set up messages for
919 After setting the default for the patron category you can
920 force those changes to all existing patrons by running the
921 *borrowers-force-messaging-defaults* script found in the
922 *misc/maintenance* folder. Ask your system administrator
923 for assistance with this script.
925 .. _circulation-and-fine-rules-label:
927 Circulation and fines rules
928 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
930 These rules define how your items are circulated, how/when fines are
931 calculated and how holds are handled.
933 - *Get there:* More > Administration > Patrons and circulation >
934 Circulation and fines rules
936 The rules are applied from most specific to less specific, using the
937 first found in this order:
939 - same library, same patron type, same item type
941 - same library, same patron type, all item type
943 - same library, all patron types, same item type
945 - same library, all patron types, all item types
947 - default (all libraries), same patron type, same item type
949 - default (all libraries), same patron type, all item types
951 - default (all libraries), all patron types, same item type
953 - default (all libraries), all patron types, all item types
955 The :ref:`CircControl` and
956 :ref:`HomeOrHoldingBranch` also come in to play when
957 figuring out which circulation rule to follow.
959 - If CircControl is set to "the library you are logged in at" circulation
960 rules will be selected based on the library you are logged in at
962 - If CircControl is set to "the library the patron is from" circulation rules
963 will be selected based on the patron's library
965 - If CircControl is set to "the library the item is from" circulation rules
966 will be selected based on the item's library where
967 HomeOrHoldingBranch chooses if item's home library is used or holding
970 - If :ref:`IndependentBranches` is set to 'Prevent'
971 then the value of HomeOrHoldingBranch is used in figuring out if the
972 item can be checked out. If the item's home library does not match
973 the logged in library, the item cannot be checked out unless you are
974 a :ref:`superlibrarian <patron-permissions-defined-label>`.
978 If you are a single library system choose your branch name before
979 creating rules (sometimes having only rules for the 'all libraries'
980 option can cause issues with holds)
984 At the very least you will need to set a default circulation rule.
985 This rule should be set for all item types, all libraries and all
986 patron categories. That will catch all instances that do not match a
987 specific rule. When checking out if you do not have a rule for all
988 libraries, all item types and all patron types then you may see
989 patrons getting blocked from placing holds. You will also want a
990 rule for your specific library set for all item types and all patron
991 types to avoid this holds issue. Koha needs to know what rule to
994 .. _default-circulation-rules-label:
996 Default circulation rules
997 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
999 Using the issuing rules matrix you can define rules that depend on
1000 patron/item type combos. To set your rules, choose a library from the
1001 pull down (or 'all libraries' if you want to apply these rules to all
1006 From the matrix you can choose any combination of patron categories and
1007 item types to apply the rules to
1011 - First choose which patron category you'd like the rule to be applied
1012 to. If you leave this to 'All' it will apply to all patron categories
1014 - Choose the 'Item type' you would like this rule to apply to. If you
1015 leave this to 'All' it will apply to all item types
1017 - Limit the number of items a patron can have checked out at the same
1018 time by entering a number in the 'Current checkouts allowed' field
1020 - If you're allowing :ref:`OnSiteCheckouts` then you
1021 may also want to set a limit on the number of items patron's can have
1026 This setting also depends on the
1027 :ref:`ConsiderOnSiteCheckoutsAsNormalCheckouts`
1030 - Define the period of time an item can be checked out to a patron by
1031 entering the number of units (days or hours) in the 'Loan period'
1034 - Choose which unit of time, Days or Hours, that the loan period and
1035 fines will be calculated in in the 'Unit' column
1037 - You can also define a hard due date for a specific patron category
1038 and item type. A hard due date ignores your usual circulation rules
1039 and makes it so that all items of the type defined are due on, before
1040 or after the date you specify.
1042 - 'Fine amount' should have the amount you would like to charge for
1047 Enter only numbers and decimal points (no currency symbols).
1049 - Enter the 'Fine charging interval' in the unit you set (ex. charge
1050 fines every 1 day, or every 2 hours)
1052 - 'When to charge' is most handy in libraries that have a fine charging
1053 interval of more than 1 day.
1057 - Given a grace period of 2 days and a fine interval of 7 days,
1058 the first fine will appear 7 days after the due date, it will
1059 always take one fine interval (7 days), before the first fine
1064 - Given a grace period of 2 days and a fine interval of 7 days,
1065 the first fine will appear 2 days after the due date and the
1066 second fine 7 days after the due date.
1068 - The 'Fine grace period' is the period of time an item can be overdue
1069 before you start charging fines.
1073 This can only be set for the Day unit, not in Hours
1075 - The 'Overdue fines cap' is the maximum fine for this patron and item
1080 If this field is left blank then Koha will not put a limit on
1081 the fines this item will accrue. A maximum fine amount can be
1082 set using the :ref:`MaxFine` system preference.
1084 - If you would like to prevent overcharging patrons for a lost items,
1085 you can check the box under 'Cap fine at replacement price.' This
1086 will prevent the patron's fines from going above the replacement
1091 If the 'Overdue fines cap' is also set, the fine will be the
1092 lesser of the two, if both apply to the given overdue
1095 - If your library 'fines' patrons by suspending their account you can
1096 enter the number of days their fine should be suspended in the
1097 'Suspension in days' field
1101 This can only be set for the Day unit, not in Hours
1103 - You can also define the maximum number of days a patron will be
1104 suspended in the 'Max suspension duration' setting
1106 - Next decide if the patron can renew this item type and if so, enter
1107 how many times they can renew it in the 'Renewals allowed' box
1109 - If you're allowing renewals you can control how long the renewal loan
1110 period will be (in the units you have chosen) in the 'Renewal period'
1113 - If you're allowing renewals you can control how soon before the due
1114 date patrons can renew their materials with the 'No renewals before'
1117 - Items can be renewed at any time if this value is left blank.
1118 Otherwise items can only be renewed if the item is due after the
1119 number in units (days/hours) entered in this box.
1121 - To control this value on a more granular level please set the
1122 :ref:`NoRenewalBeforePrecision`
1125 - You can enable automatic renewals for certain items/patrons if you'd
1126 like. This will renew automatically following your circulation rules
1127 unless there is a hold on the item
1131 You will need to enable the :ref:`automatic renewal cron
1132 job <automatic-renewal-label>` for this to work.
1136 This feature needs to have the "no renewal before" column
1137 filled in or it will auto renew everyday after the due date
1139 - If the patron can place holds on this item type, enter the total
1140 numbers of items (of this type) that can be put on hold in the 'Holds
1143 - Next you can decide if this patron/item combo are allowed to place
1144 holds on items that are on the shelf (or available in the library) or
1145 not. If you choose 'no' then items can only be placed on hold if
1148 - You can also decide if patrons are allowed to place item specific
1149 holds on the item type in question. The options are:
1151 - Allow: Will allow patrons the option to choose next available or
1154 - Don't allow: Will only allow patrons to choose next available
1156 - Force: Will only allow patrons to choose an specific item
1158 - Finally, if you charge a `rental fee <#rentalcharge>`__ for the item
1159 type and want to give a specific patron type a discount on that fee,
1160 enter the percentage discount (without the % symbol) in the 'Rental
1163 When finished, click 'Add' to save your changes. To modify a rule,
1164 simply click the 'Edit' link to the right of the fule and edit the
1165 values that appear filled in at the bottom of the form.
1169 If you would like to delete your rule, click the 'Delete' link to the
1172 To save time you can clone rules from one library to another by choosing
1173 the clone option above the rules matrix.
1177 After choosing to clone you will be presented with a confirmation
1182 .. _default-checkouts-and-hold-policy-label:
1184 Default checkout, hold and return policy
1185 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1187 You can set a default maximum number of checkouts and hold policy that
1188 will be used if none is defined below for a particular item type or
1189 category. This is the fall back rule for defaults.
1193 From this menu you can set a default to apply to all item types and
1194 patrons in the library if no other option is set in the forms below.
1196 - In 'Total current checkouts allowed' enter the total number of items
1197 patrons can have checked out at one time
1199 - In 'Total current on-site checkouts allowed' enter the total number
1200 of items patrons can have checked out on site at a time
1201 (:ref:`OnSiteCheckouts` needs to be set to 'Enable')
1203 - Control where patrons can place holds from using the 'Hold Policy'
1206 - From Any Library: Patrons from any library may put this item on
1207 hold. (default if none is defined)
1209 - From Home Library: Only patrons from the item's home library may
1210 put this book on hold.
1212 - No Holds Allowed: No patron may put this book on hold.
1214 - Control if there is a limit to filling a hold based on the item's
1219 - item's home library
1221 - item's holding library
1225 The patron's home library should not affect whether a patron
1226 can place the hold, instead the hold will only be fillable
1227 when an item matching the pickup location becomes available.
1229 - Control where the item returns to once it is checked in
1233 - Item returns to issuing branch
1237 - When an item floats it stays where it was checked in and does
1238 not ever return 'home'
1240 - Once your policy is set, you can unset it by clicking the 'Unset'
1241 link to the right of the rule
1243 .. _checkouts-per-patron-label:
1245 Default checkout limit by patron cateogry
1246 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1248 For this library, you can specify the maximum number of loans that a
1249 patron of a given category can make, regardless of the item type.
1255 If the total amount loanable for a given patron category is left
1256 blank, no limit applies, except possibly for a limit you define for
1257 a specific item type.
1259 For example, if you have a rule in the matrix that says Board patrons
1260 are allowed 10 books and 5 DVDs but you want to make it so that Board
1261 patrons only have a total of 12 things checked out at once. If you enter
1262 12 here and the patron has 10 books out already they will only be
1263 allowed 2 DVDs to equal the 12 total they're allowed.
1265 .. _item-fee-refund-on-return-label:
1267 Default lost item fee refund on return policy
1268 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1270 Here, you can specify the default policy for lost item fees on return.
1271 This policy will apply to this library. This rule is to be used with the
1272 :ref:`RefundLostOnReturnControl <refundlostonreturncontrol-label>`
1275 .. _item-hold-policies-label:
1277 Default holds policy by item type
1278 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1280 For this library, you can edit hold and return policies for a given item
1281 type, regardless of the patron's category.
1285 The various hold policies have the following effects:
1287 - From any library: Patrons from any library may put this item on hold.
1288 (default if none is defined)
1290 - From home library: Only patrons from the item's home library may put
1293 - No holds allowed: No patron may put this book on hold.
1297 Note that if the system preference
1298 :ref:`AllowHoldPolicyOverride` set to
1299 'allow', these policies can be overridden by your circulation staff.
1303 These policies are based on the patron's home branch, not the branch
1304 that the reserving staff member is from.
1306 Control if there is a limit to filling a hold based on the item's
1311 - item's home library
1313 - item's holding library
1317 The patron's home library should not affect whether a patron can
1318 place the hold, instead the hold will only be fillable when an
1319 item matching the pickup location becomes available.
1321 The various return policies have the following effects:
1323 - Item returns home: The item will prompt the librarian to transfer the
1324 item to its home library
1328 If the :ref:`AutomaticItemReturn`
1329 preference is set to automatically transfer the items home,
1330 then a prompt will not appear
1332 - Item returns to issuing branch: The item will prompt the librarian to
1333 transfer the item back to the library where it was checked out
1337 If the :ref:`AutomaticItemReturn`
1338 preference is set to automatically transfer the items home,
1339 then a prompt will not appear
1341 - Item floats: The item will not be transferred from the branch it was
1342 checked in at, instead it will remain there until transferred
1343 manually or checked in at another branch
1345 For example you might allow holds at your libraries but not what New
1346 items or DVDs to be placed on hold by other branches so you can set the
1347 'Hold policy' to 'From home library' so that those items can only be
1348 placed on hold if the items' owning library and the patron's home
1349 library are the same. You can also block holds completely on specific
1350 item types from this form. This is also how you can set up floating item
1351 types and types that remain with their home library.
1353 .. _patron-attribute-types-label:
1355 Patron attribute types
1356 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1358 Patron attributes can be used to define custom fields to associate with
1359 your patron records. In order to enable the use of custom fields you
1360 need to set the :ref:`ExtendedPatronAttributes`
1363 - *Get there:* More > Administration > Patrons and circulation > Patron
1366 A common use for this field would be for a student ID number or a
1367 Driver's license number.
1371 .. _adding-patron-attributes-label:
1373 Adding patron attributes
1374 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1376 To add a new patron attribute type, click the 'New patron attribute
1377 type' button at the top of the page
1381 - In the 'Patron attribute type code', enter a short code to identify
1386 This field is limited to 10 characters (numbers and letters
1391 This setting cannot be changed after an attribute is defined
1393 - In the 'Description' field, enter a longer (plain text) explanation
1394 of what this field will contain
1396 - Check the box next to 'Repeatable' to let a patron record have
1397 multiple values of this attribute.
1401 This setting cannot be changed after an attribute is defined
1403 - If 'Unique identifier' is checked, the attribute will be a unique
1404 identifier which means, if a value is given to a patron record, the
1405 same value cannot be given to a different record.
1407 - Unique attributes can be used as match points on the :ref:`patron
1408 import tool <patron-import-label>`
1412 This setting cannot be changed after an attribute is defined
1414 - Check 'Allow password' to make it possible to associate a password
1415 with this attribute.
1417 - Check 'Display in OPAC' to display this attribute on a patron's
1418 details page in the OPAC.
1420 - Check 'Searchable' to make this attribute searchable in the staff
1423 - Check 'Display in check-out' to make this attribute visible in the
1424 patron's short detail display on the left of the checkout screen and
1429 - Authorized value category; if one is selected, the patron record
1430 input page will only allow values to be chosen from the authorized
1433 - You will first need to add an authorized value list for it to
1436 - *Get there:*\ More > Administration > Basic parameters >
1437 :ref:`Authorized values <authorized-values-label>`
1441 an authorized value list is not enforced during batch patron
1444 - If you would like this attribute to only be used by specific branches
1445 you can choose those branches from the 'Branches limitation' list.
1446 Choose 'All branches' to show it for all libraries.
1450 Note that items with locations already set on them will not be
1451 altered. The branch limitation only limits the choosing of an
1452 authorized value based on the home branch of the current staff
1453 login. All authorized values for item records (LOC, LOST,
1454 CCODE, etc) will show in the OPAC for all patrons.
1456 - If you'd like to only show this attribute on patrons of one type
1457 choose that patron type from the 'Category' pull down
1459 - If you have a lot of attributes it might be handy to group them so
1460 that you can easily find them for editing. If you create an
1461 :ref:`Authorized value <authorized-values-label>` for PA\_CLASS it will show
1462 in the 'Class' pull down and you can then change your attributes page
1463 to have sections of attributes
1467 - Click Save to save your new attribute
1469 Once added your attribute will appear on the list of attributes and also
1470 on the patron record add/edit form
1474 If you have set up classes for organizing attributes they will appear
1475 that way on the add/edit patron form
1479 .. _editing/deleting-patron-attributes-label:
1481 Editing/deleting patron attributes
1482 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1484 Each patron attribute has an edit and a delete link beside it on the
1487 Some fields in the attribute will not be editable once created:
1489 - Patron attribute type code
1495 You will be unable to delete an attribute if it's in use.
1499 .. _library-transfer-limits-label:
1501 Library transfer limits
1502 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1504 Limit the ability to transfer items between libraries based on the
1505 library sending, the library receiving, and the collection code
1508 - *Get there:* More > Administration > Patrons and circulation > Library
1511 These rules only go into effect if the preference
1512 :ref:`UseBranchTransferLimits <usebranchtransferlimits-&-branchtransferlimitstype-label>` is set to
1515 Before you begin you will want to choose which library you are setting
1520 Transfer limits are set based on the collections codes you have applied
1521 via the :ref:`Authorized value <authorized-values-label>` administration area.
1525 Collection codes will appear as tabs above the checkboxes:
1529 Check the boxes for the libraries that you accept checkins from for the
1530 item type you have selected at the top (in the example below - FIC)
1534 In the above example, Centerville library will allow patrons to return
1535 items from all libraries except Liberty and Franklin to their branch.
1537 .. _transport-cost-matrix-label:
1539 Transport cost matrix
1540 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1542 The transport cost matrix lets a library system define relative costs to
1543 transport books to one another. In order for the system to use this
1544 matrix you must first set the
1545 :ref:`UseTransportCostMatrix` preference to
1550 The transport cost matrix takes precedence in controlling where
1551 holds are filled from, if the matrix is not used then Koha checks
1552 the :ref:`StaticHoldsQueueWeight <staticholdsqueueweight,-holdsqueueskipclosed-&-randomizeholdsqueueweight-label>`.
1554 Costs are decimal values between some arbitrary maximum value (e.g. 1 or
1555 100) and 0 which is the minimum (no) cost. For example, you could just
1556 use the distance between each library in miles as your 'cost', if that
1557 would accurately reflect the cost of transferring them. Perhaps post
1558 offices would be a better measure. Libraries sharing a post office would
1559 have a cost of 1, adjacent post offices would have a cost of 2, etc.
1561 To enter transport costs simply click in the cell you would like to
1562 alter, uncheck the 'Disable' box and enter your 'cost'
1566 After entering in your cost, hit 'Enter' on your keyboard or click the
1567 'Save' button at the bottom of the matrix to save your changes.
1571 A NULL value will make no difference where the From and To libraries
1572 are the same library. However, as a best practice, you should put a
1573 0 in there. For all other To/From combinations, a NULL value will
1574 cause that relationship to act as if it has been disabled. So, in
1575 summary, don't leave any of the values empty. It's best to always
1576 put a number in there ( even if you choose to disable that given
1579 .. _item-circulation-alerts-label:
1581 Item circulation alerts
1582 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1584 Libraries can decide if they want to have patrons automatically notified
1585 of circulation events (check ins and check outs).
1587 - *Get there:* More > Administration > Patrons and circulation > Item
1590 These preferences are set based on patron types and item types.
1594 These preference can be overridden by changes in the individual
1595 patron's messaging preferences.
1597 To set up circulation alerts:
1599 - Choose your library from the pull down at the top of the screen
1603 - To set preferences for all libraries, keep the menu set to
1606 - By default all item types and all patrons are notified of check ins
1607 and check outs. To change this, click on the item/patron type combo
1608 that you would like to stop notices for.
1612 - In the above example, Juveniles and Kids will not receive check
1615 .. _cities-and-towns-label:
1618 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1620 To standardize patron input you can define cities or towns within your
1621 region so that when new patrons are added librarians simply have to
1622 select the town from a list instead of having to type the town and zip
1623 (or postal) code information.
1625 - *Get there:* More > Administration > Patrons and circulation > Cities
1628 .. _adding-a-city-label:
1631 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1633 To add a new city, click the 'New city' button at the top of the page
1634 and enter the city name, state, zip/postal code and country.
1638 One you click Submit, your city will be saved and will be listed on the
1639 Cities and towns page
1643 Cities can be edited or deleted at any time.
1645 .. _viewing-cities-on-patron-add-form-label:
1647 Viewing cities on patron add form
1648 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1650 If you have defined local cities using the 'New city' form, then when
1651 adding or editing a patron record you will see those cities in a pull
1652 down menu to make city selection easy.
1656 This will allow for easy entry of local cities into the patron record
1657 without risking the potential for typos or mistaken zip/postal codes.
1659 .. _catalog-administration-label:
1661 Catalog administration
1662 --------------------------------------
1664 Set these controls before you start cataloging on your Koha system.
1666 - *Get there:* More > Administration > Catalog
1668 .. _marc-bibliographic-frameworks-label:
1670 MARC bibliographic frameworks
1671 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1673 Think of frameworks as templates for creating new bibliographic records.
1674 Koha comes with some predefined frameworks that can be edited or
1675 deleted, and librarians can create their own frameworks for content
1676 specific to their libraries.
1678 - *Get there:* More > Administration > Catalog > MARC bibliographic
1685 Do not delete or edit the Default framework since this will cause
1686 problems with your cataloging records - always create a new template
1687 based on the Default framework, or alter the other frameworks.
1689 After clicking the 'MARC structure' link to the right of each framework
1690 you can decide how many fields you want to see on one screen by using
1691 the pagination options at the top of the table.
1695 .. _add-new-framework-label:
1698 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1700 To add a new framework
1702 - Click 'New framework'
1706 - Enter a code of 4 or fewer characters
1708 - Use the Description field to enter a more detailed definition of
1713 - Once your framework is added click 'MARC structure' to the right of
1714 it on the list of frameworks
1718 - You will be asked to choose a framework to base your new framework
1719 off of, this will make it easier than starting from scratch
1721 - Once your framework appears on the screen you can edit or delete each
1722 field by following the instructions for :ref:`editing
1723 subfields <edit-framework-subfields-label>`
1725 .. _edit-existing-frameworks-label:
1727 Edit existing frameworks
1728 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1730 Clicking 'Edit' to the right of a framework will only allow you to edit
1731 the description for the framework:
1735 To make edits to the fields associated with the framework you must first
1736 click 'MARC Structure' and then follow the instructions for :ref:`editing
1737 subfields <edit-framework-subfields-label>`
1739 .. _add-subfields-to-frameworks-label:
1741 Add subfields to frameworks
1742 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1744 To add a field to a framework click the 'New tag' button at the top of
1745 the framework definition
1749 This will open up a blank form for entering MARC field data
1753 Enter the information about your new tag:
1755 - The 'Tag' is the MARC field number
1757 - The 'Label for lib' is the text that will appear in the staff client
1758 when in the cataloging module
1760 - The 'Label for OPAC' is the text that will appear in the OPAC when
1761 viewing the MARC version of the record
1763 - If this field can be repeated, check the 'Repeatable' box
1765 - If this field is mandatory, check the 'Mandatory' box
1767 - If you want this field to be a pull down with limited possible
1768 answers, choose which 'Authorized value' list you want to use
1770 When you're finished, click 'Save changes' and you will be presented
1775 To the right of the new field is a link to 'Subfields,' you will need to
1776 add subfields before this tag will appear in your MARC editor. The
1777 process of entering the settings for the new subfield is the same as
1778 those found in the :ref:`editing subfields in frameworks <edit-framework-subfields-label>`
1779 section of this manual.
1781 .. _edit-framework-subfields-label:
1783 Edit framework subfields
1784 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1786 Frameworks are made up of MARC fields and subfields. To make edits to
1787 most frameworks you must edit the fields and subfields. Clicking 'Edit'
1788 to the right of each subfield will allow you to make changes to the text
1789 associated with the field
1793 - Each field has a tag (which is the MARC tag) that is uneditable
1795 - The 'Label for lib' is what will show in the staff client if you
1796 have :ref:`advancedMARCeditor` set to display
1799 - The 'Label for OPAC' is what will show on the MARC view in the
1802 - If you check 'Repeatable' then the field will have a plus sign
1803 next to it allowing you to add multiples of that tag
1805 - If you check 'Mandatory' the record will not be allowed to save
1806 unless you have a value assigned to this tag
1808 - 'Authorized value' is where you define an :ref:`authorized
1809 value <authorized-values-label>` that your catalogers can choose from
1810 a pull down to fill this field in
1812 To edit the subfields associated with the tag, click 'Subfields' to the
1813 right of the tag on the 'MARC Structure' listing
1815 - From the list of subfields you can click 'Delete' to the right of
1816 each to delete the subfields
1818 - To edit the subfields click 'Edit subfields'
1820 - For each subfield you can set the following basic constraint values
1824 - Text for librarian
1826 - what appears before the subfield in the librarian interface
1830 - what appears before the field in the OPAC.
1832 - If left empty, the text for librarian is used instead
1836 - the field will have a plus sign next to it allowing you to add
1837 multiples of that tag
1841 - the record will not be allowed to save unless you have a value
1842 assigned to this tag
1846 - defines the tab where the subfield is shown. All subfields of a
1847 given field must be in the same tab or ignored. Ignore means
1848 that the subfield is not managed.
1850 - For each subfield you can set the following advanced constraint
1857 - defines what you want to appear in the field by default, this
1858 will be editable, but it saves time if you use the same note
1859 over and over or the same value in a field often.
1863 If you would like a field to fill in with today's date you
1864 can use the YYYY MM DD syntax in the 'Default value'. For
1865 example: a default of "Year:YYYY Month:MM Day:DD" (without
1866 quotes) will print as "Year:2015 Month:11 Day:30"
1870 - allows you to select from where this subfield is
1871 visible/hidden, simply check the boxes where you would like the
1872 field to show and uncheck the boxes where you would like it
1879 - if checked, it means that the subfield is a URL and can be
1884 - If you enter a field/subfield here (200b), a link appears after
1885 the subfield in the MARC Detail view. This view is present only
1886 in the staff client, not the OPAC. If the librarian clicks on
1887 the link, a search is done on the database for the
1888 field/subfield with the same value. This can be used for 2 main
1891 - on a field like author (200f in UNIMARC), put 200f here, you
1892 will be able to see all bib records with the same author.
1894 - on a field that is a link (4xx) to reach another bib record.
1895 For example, put 011a in 464$x, will find the serials that
1900 This value should not change after data has been added to
1901 your catalog. If you need to change this value you must ask
1902 your system administrator to run
1903 misc/batchRebuildBiblioTables.pl.
1907 - Koha is multi-MARC compliant. So, it does not know what the
1908 245$a means, neither what 200$f (those 2 fields being both the
1909 title in MARC21 and UNIMARC). So, in this list you can "map" a
1910 MARC subfield to its meaning. Koha constantly maintains
1911 consistency between a subfield and its meaning. When the user
1912 want to search on "title", this link is used to find what is
1913 searched (245 if you're MARC21, 200 if you're UNIMARC).
1915 - For each subfield you can set the following Other option values
1921 - means the value cannot by typed by the librarian, but must be
1922 chosen from a pull down generated by the :ref:`authorized
1923 value <authorized-values-label>` list
1925 - In the example above, the 504a field will show the MARC504
1926 authorized values when cataloging
1932 - means that the value is not free text, but must be searched in
1933 the authority/thesaurus of the selected category
1937 - means the value is calculated or managed by a plugin. Plugins
1938 can do almost anything.
1942 - For call numbers there is an option to add a call number
1943 browser next to the the call number subfield so that you can
1944 identify which call numbers are in use and which are not.
1945 Simply choose the cn\_browser.pl plugin. Learn more in the
1946 :ref:`cataloging section <adding-items-label>` of this manual.
1948 - If you'd like to let file uploads via cataloging you can
1949 choose the upload.pl plugin and this will allow you to
1950 :ref:`upload files to Koha to link to your
1951 records <attaching-files-to-records-label>`.
1953 - In UNIMARC there are plugins for every 1xx fields that are
1954 coded fields. The plugin is a huge help for cataloger! There
1955 are also two plugins (unimarc\_plugin\_210c and
1956 unimarc\_plugin\_225a that can "magically" find the editor
1957 from an ISBN, and the collection list for the editor)
1959 - To save your changes simply click the 'Save changes' button at the
1962 .. _import/export-frameworks-label:
1964 Import/export frameworks
1965 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1967 Next to each framework is a link to either import or export the
1970 .. _export-framework-label:
1973 ''''''''''''''''''''''''''''''''''''''''
1975 To export a framework simply click the 'Export' link to the right of
1980 When you click 'Export' you will be prompted to choose what format to
1985 A framework exported this way can be imported into any other Koha
1986 installation using the import framework option.
1988 .. _import-framework-label:
1991 ''''''''''''''''''''''''''''''''''''''''
1993 An easy way to create a new framework is to import one created for your
1994 or another Koha installation. This framework would need to be exported
1995 from the other system :ref:`using the instructions
1996 above <export-framework-label>` to be available for import here.
1998 To import a framework you first need to create :ref:`a new
1999 framework <add-new-framework-label>`. Once you have that framework, click
2000 'Import' to the right of the new framework.
2004 You will be prompted to find a file on your computer to import into the
2009 You will be asked to confirm your actions before the file is imported.
2013 As your file is uploaded you will see an image that will confirm that
2014 the system is working.
2018 Once your import is complete you will be brought to the framework edit
2019 tool where you can make any changes you need to the framework you
2022 .. _koha-to-marc-mapping-label:
2024 Koha to MARC mapping
2025 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2027 While Koha stores the entire MARC record, it also stores common fields
2028 for easy access in various tables in the database. Koha to MARC mapping
2029 is used to tell Koha where to find these values in the MARC record. In
2030 many cases you will not have to change the default values set by in this
2031 tool on installation, but it is important to know that the tool is here
2032 and can be used at any time.
2034 - *Get there:* More > Administration > Catalog > Koha to MARC mapping
2036 The table shows all the database fields that can be mapped to MARC fields.
2040 To add a new mapping, click on the 'Add' button to the right of the
2045 Write in the MARC field and subfield you would like to map, separated
2046 by a comma, to this Koha field and click the 'OK' button.
2050 It is possible to link more than one MARC field to a database field.
2051 For example, you could link both 260$a and 264$a to the biblioitems.place
2054 If you would like to clear the mapping for a database field, click
2055 the 'Remove' button.
2059 All changes are immediate.
2061 .. _keywords-to-marc-mapping-label:
2063 Keywords to MARC mapping
2064 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2066 This tool will allow you to map MARC fields to a set of predefined
2069 - *Get there:* More > Administration > Catalog > Keywords to MARC
2074 This tool only affects sites that are not using the XSLT
2077 At this time the only keyword in use is 'subtitle.'
2079 Using this tool you can define what MARC field prints to the detail
2080 screen of the bibliographic record using keywords. The following example
2081 will use the subtitle field.
2083 Using the framework pull down menu, choose the
2084 :ref:`Framework <marc-bibliographic-frameworks-label>` you would like to apply this rule to.
2085 For example, the subtitle for books can be found in the 245$b field.
2089 However the subtitle for DVDs appears in 245$p
2093 Using this tool you can tell Koha to print the right field as the
2094 subtitle when viewing the bibliographic record in the OPAC.
2098 This tool can be used to chain together pieces of the record as well. If
2099 you want the series number to show in the title on your search results
2100 you simply have to map 490 $v to 'subtitle' along with the 245 $b.
2104 Chain together the fields you want to show after the item title in
2105 the order in which you want them to appear.
2107 Future developments will include additional keyword assigned fields.
2109 .. _marc-bibliographic-framework-test-label:
2111 MARC bibliographic framework test
2112 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2114 Checks the MARC structure.
2116 - *Get there:* More > Administration > Catalog > MARC bibliographic
2119 If you change your MARC bibliographic framework it's recommended that
2120 you run this tool to test for errors in your definition.
2124 .. _authority-types-label:
2127 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2129 Authority types are basically MARC frameworks for authority records and
2130 because of that they follow the same editing rules found in the :ref:`MARC
2131 bibliographic frameworks <marc-bibliographic-frameworks-label>` section of this manual.
2132 Koha comes with many of the necessary authority frameworks already
2133 installed. To learn how to add and edit authority types, simply review
2134 the :ref:`MARC bibliographic frameworks` section of this manual.
2136 - *Get there:* More > Administration > Catalog > Authority types
2138 .. _classification-sources-label:
2140 Classification sources
2141 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2143 Source of classification or shelving scheme is an :ref:`Authorized
2144 values <authorized-values-label>` category that is mapped to field 952$2 and
2145 942$2 in Koha's MARC bibliographic frameworks and stored in the
2146 items.cn\_source field in the database.
2148 - *Get there:* More > Administration > Catalog > Classification sources
2152 Commonly used values of this field are:
2154 - ddc - Dewey Decimal Classification
2156 - lcc - Library of Congress Classification
2158 If you chose to install classification sources during Koha's
2159 installation, you would see other values too:
2161 - ANSCR (sound recordings)
2163 - SuDOC classification
2165 - Universal Decimal Classification
2167 - Other/Generic Classification
2169 .. _adding/editing-classification-sources-label:
2171 Adding/editing classification sources
2172 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2174 You can add your own source of classification by using the 'New
2175 classification source' button. To edit use the 'Edit' button.
2179 When creating or editing:
2181 - You will need to enter a code and a description.
2183 - Check the 'Source in use?' checkbox if you want the value to appear
2184 in the drop down list for this category.
2186 - Select the appropriate :ref:`filing rule <classification-filing-rules-label>` from the
2189 .. _classification-filing-rules-label:
2191 Classification filing rules
2192 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2194 Filing rules determine the order in which items are placed on shelves.
2196 Values that are pre-configured in Koha are:
2204 Filing rules are mapped to :ref:`Classification
2205 sources <adding/editing-classification-sources-label>`. You can setup new
2206 filing rules by using the 'New filing rule' button. To edit use the 'Edit'
2209 When creating or editing:
2211 - Enter a code and a description
2213 - Choose an appropriate filing routine - dewey, generic or lcc
2215 .. _record-matching-rules-label:
2217 Record matching rules
2218 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2220 Record matching rules are used when importing MARC records into Koha.
2222 - *Get there:* More > Administration > Catalog > Record matching rules
2224 The rules that you set up here will be referenced with you :ref:`Stage MARC
2225 records for import <stage-marc-records-for-import-label>`.
2227 It is important to understand the difference between 'Match points' and
2228 'Match checks' before adding new matching rules to Koha.
2230 Match points are the criteria that you enter that must be met in order
2231 for an incoming record to match an existing MARC record in your catalog.
2232 You can have multiple match points on an import rule each with its own
2233 score. An incoming record will be compared against your existing records
2234 ('one record at a time') and given a score for each match point. When
2235 the total score of the match points matches or exceeds the threshold
2236 given for the matching rule, Koha assumes a good match and
2237 imports/overlays according your specifications in the import process. An
2238 area to watch out for here is the sum of the match points. Double check
2239 that the matches you want will add up to a successful match.
2245 Match point on 020$a 1000
2247 Match point on 022$a 1000
2249 Match point on 245$a 500
2251 Match point on 100$a 100
2253 In the example above, a match on either the 020$a or the 022$a will
2254 result in a successful match. A match on 245$a title and 100$a author
2255 (and not on 020$a or 022$a) will only add up to 600 and not be a match.
2256 And a match on 020$a and 245$a will result in 1500 and while this is a
2257 successful match, the extra 500 point for the 245$a title match are
2258 superfluous. The incoming record successfully matched on the 020$a
2259 without the need for the 245$a match. However, if you assigned a score
2260 of 500 to the 100$a Match Point, a match on 245$a title and 100$a author
2261 will be considered a successful match (total of 1000) even if the 020$a
2264 Match checks are not commonly used in import rules. However, they can
2265 serve a couple of purposes in matching records. First, match checks can
2266 be used as the matching criteria instead of the match points if your
2267 indexes are stale and out of date. The match checks go right for the
2268 data instead of relying on the data in the indexes. (If you fear your
2269 indexes are out of date, a rebuild of your indexes would be a great idea
2270 and solve that situation!) The other use for a match check is as a
2271 'double check' or 'veto' of your matching rule. For example, if you have
2272 a matching rule as below:
2276 Match point on 020$a 1000
2278 Match check on 245$a
2280 Koha will first look at the 020$a tag/subfield to see if the incoming
2281 record matches an existing record. If it does, it will then move on to
2282 the Match Check and look directly at the 245$a value in the incoming
2283 data and compare it to the 245$a in the existing 'matched' record in
2284 your catalog. If the 245$a matches, Koha continues on as if a match was
2285 successful. If the 245$a does not match, then Koha concludes that the
2286 two records are not a match after all. The Match Checks can be a really
2287 useful tool in confirming true matches.
2289 When looking to create matching rules for your authority records the
2290 following indexes will be of use:
2292 +--------------------------+--------------------+
2293 | Index name | Matches MARC tag |
2294 +==========================+====================+
2295 | LC-cardnumber | 010$a |
2296 +--------------------------+--------------------+
2297 | Personal-name | 100$a |
2298 +--------------------------+--------------------+
2299 | Corporate-name-heading | 110$a |
2300 +--------------------------+--------------------+
2301 | Meeting-name | 111$a |
2302 +--------------------------+--------------------+
2303 | Title-uniform | 130$a |
2304 +--------------------------+--------------------+
2305 | Chronological-term | 148$a |
2306 +--------------------------+--------------------+
2307 | Subject-topical | 150$a |
2308 +--------------------------+--------------------+
2309 | Name-geographic | 151$a |
2310 +--------------------------+--------------------+
2311 | Term-genre-form | 155$a |
2312 +--------------------------+--------------------+
2314 Table: Authority indexes
2316 .. _adding-matching-rules-label:
2318 Adding matching rules
2319 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2321 To create a new matching rule :
2323 - Click 'New record matching rule'
2327 - Choose a unique name and enter it in the 'Matching rule code'
2330 - 'Description' can be anything you want to make it clear to you
2331 what rule you're picking
2333 - 'Match threshold' is the total number of 'points' a biblio must
2334 earn to be considered a 'match'
2336 - 'Record type' is the type of import this rule will be used for -
2337 either authority or bibliographic
2339 - Match points are set up to determine what fields to match on
2341 - 'Search index' can be found by looking at the ccl.properties file
2342 on your system which tells the zebra indexing what data to search
2343 for in the MARC data". Or you can review the index for standard
2344 index names used. :ref:`Koha Search Indexes`
2346 - 'Score' - The number of 'points' a match on this field is worth.
2347 If the sum of each score is greater than the match threshold, the
2348 incoming record is a match to the existing record
2350 - Enter the MARC tag you want to match on in the 'Tag' field
2352 - Enter the MARC tag subfield you want to match on in the
2355 - 'Offset' - For use with control fields, 001-009
2357 - 'Length' - For use with control fields, 001-009
2359 - Koha only has one 'Normalization rule' that removes extra
2360 characters such as commas and semicolons. The value you enter in
2361 this field is irrelevant to the normalization process.
2363 - 'Required match checks' - ??
2365 .. _sample-bibliographic-record-matching-rule-control-number-label:
2367 Sample bibliographic record matching rule: Control number
2368 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2372 - Match threshold: 100
2374 - Record type: Bibliographic
2378 If you'd like a rule to match on the 001 in authority records
2379 you will need the repeat all of these values and change just
2380 the record type to 'Authority record'
2382 - Matchpoints (just the one):
2384 - Search index: Control-number
2392 this field is for the control number assigned by the
2393 organization creating, using, or distributing the record
2401 - Normalization rule: Control-number
2403 - Required match checks: none (remove the blank one)
2407 .. _oai-sets-configuration-label:
2409 OAI sets configuration
2410 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2412 On this page you can create, modify and delete OAI-PMH sets
2414 .. _create-a-set-label:
2417 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2421 - Click on the link 'Add a new set'
2423 - Fill the mandatory fields 'setSpec' and 'setName'
2425 - Then you can add descriptions for this set. To do this click on 'Add
2426 description' and fill the newly created text box. You can add as many
2427 descriptions as you want.
2429 - Click on 'Save' button'
2431 .. _modify/delete-a-set-label:
2434 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2436 To modify a set, just click on the link 'Modify' on the same line of the
2437 set you want to modify. A form similar to set creation form will appear
2438 and allow you to modify the setSpec, setName and descriptions.
2440 To delete a set, just click on the link 'Delete' on the same line of the
2441 set you want to delete.
2443 .. _define-mappings-label:
2446 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2448 Here you can define how a set will be build (what records will belong to
2449 this set) by defining mappings. Mappings are a list of conditions on
2450 record content. A record only need to match one condition to belong to
2453 - Fill the fields 'Field', 'Subfield' and 'Value'. For example if you
2454 want to include in this set all records that have a 999$9 equal to
2455 'XXX'. Fill 'Field' with 999, 'Subfield' with 9 and 'Value' with XXX.
2457 - If you want to add another condition, click on 'OR' button and repeat
2462 To delete a condition, just leave at least one of 'Field', 'Subfield' or
2463 'Value' empty and click on 'Save'.
2467 Actually, a condition is true if value in the corresponding subfield
2468 is strictly equal to what is defined if 'Value'. A record having
2469 999$9 = 'XXX YYY' will not belong to a set where condition is 999$9
2472 And it is case sensitive : a record having 999$9 = 'xxx' will not belong
2473 to a set where condition is 999$9 = 'XXX'.
2475 .. _build-sets-label:
2478 ^^^^^^^^^^^^^^^^^^^^^^^^^^
2480 Once you have configured all your sets, you have to build the sets. This
2481 is done by calling the script misc/migration\_tools/build\_oai\_sets.pl.
2483 .. _item-search-fields-label:
2486 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2488 From here you can add custom search fields to the :ref:`item
2489 search <item-searching-label>` option in the staff client.
2493 To add a new search term simply click the 'New search field' button
2497 - Name is a field for you to identify the search term
2499 - Label is what will appear on the item search page
2501 - MARC field allows you to pick which field you'd like to search in
2503 - MARC subfield is the subfield you'd like to search in
2505 - Authorised values category can be used to turn this search field in
2506 to a pull down instead of a free text field
2508 Once your new field is added it will be visible at the top of this page
2509 and on the item search page
2513 .. _acquisitions-module-label:
2516 ----------------------------
2518 The Koha Acquisitions module provides a way for the library to record
2519 orders placed with vendors and manage purchase budgets.
2521 Before using the `Acquisitions Module <#acqmodule>`__, you will want to
2522 make sure that you have completed all of the set up.
2524 - *Get there:* More > Administration > Acquisitions
2526 .. _currencies-and-exchange-rates-label:
2528 Currencies and exchange rates
2529 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2531 If you place orders from more than one country you will want to input
2532 currency exchange rates so that your acquisitions module will properly
2535 - *Get there:* More > Administration > Acquisitions > Currencies and
2542 This data is not automatically updated, so be sure to keep it up to
2543 date so that your accounting is kept correct.
2545 The ISO code you enter will be used when importing MARC files via the
2546 staging tools, the tool will attempt to find and use the price of the
2547 currently active currency.
2549 The active currency is the main currency you use in your library. Your
2550 active currency will have a check mark in the 'Active' column. If you
2551 don't have an active currency you will see an error message telling you
2552 to choose an active currency.
2559 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2561 Budgets are used for tracking accounting values related to acquisitions.
2562 For example you could create a budget for the current year (ex. 2015)
2563 and then break that into :ref:`Funds` for different areas of the
2564 library (ex. Books, Audio, etc).
2566 - *Get there:* More > Administration > Acquisitions > Budgets
2568 When visiting the main budget administration you will see two tabs, one
2569 for active and one for inactive budgets.
2573 .. _adding-budgets-label:
2576 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2578 Budgets can either be created :ref:`from scratch <add-a-new-budget-label>`, by
2579 :ref:`duplicating the previous year's budget <duplicate-a-budget-label>` or by
2580 :ref:`closing a previous year's budget <close-a-budget-label>`.
2582 .. _add-a-new-budget-label:
2585 ''''''''''''''''''''''''''''''''''''
2587 If you haven't used Koha before for acquisitions then you'll need to
2588 start fresh with a new budget. To add a new budget click the 'New
2593 - Choose the time period this budget is for, whether it's an academic
2594 year, a fiscal year, a quarter, etc.
2596 - The description should be something that will help you identify the
2597 budget when ordering
2599 - In the amount box do not use any symbols, simply enter the amount of
2600 the budget with numbers and decimals.
2602 - Marking a budget active makes it usable when placing orders in the
2603 acquisitions module, even if the order is placed after the budget end
2604 date. This will allow you to record orders that were places in a
2605 previous budget period.
2607 - Locking a budget means that funds will not be able to be modified by
2610 Once you have made your edits, click the 'Save changes' button. You will
2611 be brought to a list of your existing budgets.
2615 .. _duplicate-a-budget-label:
2618 '''''''''''''''''''''''''''''''''''''''''
2620 To duplicate a budget from a previous year, click on the link for the
2621 budget name from the list of budgets
2625 On the screen listing the budget breakdown click the 'Edit' button at the
2626 top and choose to 'Duplicate budget'
2630 You can also click the 'Actions' button to the right of the budget and
2635 In both cases you will be presented with a form where you simply need to
2636 enter the new start and end date and save the budget.
2640 Check the box for 'Mark the original budget as inactive' if the original
2641 budget should no longer be used.
2643 Check the box for 'Set all funds to zero' if you wish the new budget to
2644 contain all the same fund structures as the previous budget but no
2645 allocations until you manually enter an amount in the fund.
2647 This will not only duplicate your budget, but all of the funds
2648 associated with that budget so that you can reuse budgets and funds from
2649 year to year and so that you can move unreceived orders and if desired
2650 unspent funds from a previous budget to the new budget.
2652 .. _close-a-budget-label:
2655 '''''''''''''''''''''''''''''''''
2657 Close a budget to move or roll over unreceived orders and if desired
2658 unspent funds from a previous budget to a new budget. Before closing
2659 your budget you might want to :ref:`duplicate the previous year's
2660 budget <duplicate-a-budget-label>` so that you have somewhere for the
2661 unreceived orders to roll to.
2663 Find the previous budget with unreceived orders on the Active budgets or
2664 the Inactive budgets tab and select 'Close' under 'Actions'.
2670 In order for the unreceived orders to be automatically moved to the
2671 new budget, the fund structures in the previous budget must exist in
2672 the new budget. Budgets without unreceived orders cannot be closed.
2674 When you select 'Close' you will be presented with a form.
2678 Use the 'Select a budget' drop down to choose the new budget for the
2681 Check the box for 'Move remaining unspent funds' to move the unspent
2682 amounts from the funds of the budget being closed to the selected
2685 Once you have made your choices, click the 'Move unreceived orders'
2686 button. You will be presented with a dialog box that says 'You have
2687 chosen to move all unreceived orders from 'Budget X' to 'Budget Y'. This
2688 action cannot be reversed. Do you wish to continue?' Budget X is the
2689 budget to be closed and Budget Y is the selected budget.
2693 If everything seems correct click 'OK' and the unreceived orders and, if
2694 selected, unspent funds will be moved.
2696 Wait until the 'Report after moving unreceived orders from budget X to
2697 Y' displays. This will list the order numbers which have been impacted
2698 (grouped by fund) and detail if the unreceived order was moved or if
2699 there was a problem. For example, if the new budget does not contain a
2700 fund with the same name as the previous budget, the order will not be
2710 - *Get there:* More > Administration > Acquisitions > Funds
2712 .. _add-a-fund-label:
2715 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2717 A fund is added to a budget.
2721 A :ref:`budget <adding-budgets-label>` must be defined before a fund can be
2724 To add a new fund click the 'New' button and then choose which budget you
2725 would like to add the fund to.
2729 In the form that appears you want to enter the basics about your fund.
2733 The three first fields are required, the rest are optional
2735 - Fund code is a unique identifier for your fund
2737 - The fund name should be something that librarians will understand
2739 - Amount should be entered with only numbers and decimals, no other
2742 - Warning at (%) or Warning at (amount) can be filled in to make Koha
2743 warn you before you spend a certain percentage or amount of your
2744 budget. This will prevent you from overspending.
2746 - You can choose to assign this fund to a librarian. Doing so will make
2747 it so that only that librarian can make changes to the fund
2749 - Choose which library will be using this fund
2751 - You can restrict who can order from this fund by choosing either the
2752 'owner', 'owner and users' or 'owner, users and library' from the
2753 'Restrict access to' menu
2759 Without an owner, the access restriction will be ignored, be
2760 sure to enter an owner as well as choose a restriction
2762 - Notes are simply for any descriptive notes you might want to add so
2763 that librarians know when to use this fund
2765 - Planning categories are used for statistical purposes. If you will be
2766 using the Asort1 and/or Asort2 authorised values lists to track your orders
2767 you need to select them when setting up the fund. Select the Asort1/Asort2
2768 option from the dropdown lists for the Statiscal 1 done on: and
2769 Statistical 2 done on: fields.
2771 - To learn more about planning categories, check out the :ref:`Planning category
2772 FAQ <planning-categories-label>`.
2774 When complete, click 'Submit' and you will be brought to a list of all
2775 of the funds for the budget.
2779 The monetary columns in the fund table break down as follows:
2781 1. Base-level allocated is the 'Amount' value you defined when creating
2784 2. Base-level ordered is the ordered amount for this fund (without child
2787 3. Total ordered is the base-level ordered for this fund and all its
2790 4. Base-level spent is the spent amount for this fund (without child
2793 5. Total spent is the base-level spent for this fund and all its child
2796 6. Base-level available is 1 - 2
2798 7. Total available is 1 - 3
2800 To the right of each fund you will find the 'Actions' button under which
2801 you will find the 'Edit,' 'Delete,' and 'Add child fund' options.
2805 A child fund simply a sub-fund of the fund listed. An example would be
2806 to have a fund for 'Fiction' and under that have a fund for 'New
2807 releases' and a fund for 'Science Fiction.' It is an optional way to
2808 further organize your finances.
2810 Funds with children will show with a small arrow to the left. Clicking
2811 that will show you the children funds.
2815 .. _budget-planning-label:
2818 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2820 When viewing the list of funds click the 'Planning' button and choose
2821 how you would like to plan to spend your budget.
2825 If you choose 'Plan by MONTHS' you will see the budgeted amount broken
2830 To hide some of the columns you can click the 'hide' link to the right
2831 (or below as in the screenshot above) the dates. To add more columns you
2832 can click the 'Show a column' link found below the 'Fund remaining'
2837 From here you can plan your budget spending by manually entering values
2838 or by clicking the 'Auto-fill row' button. If you choose to auto-fill
2839 the form the system will try to divide the amount accordingly, you may
2840 have to make some edits to split things more accurately.
2844 Once your changes are made, click the 'Save' button. If you would like
2845 to export your data as a CSV file you can do so by entering a file name
2846 in the 'Output to a file named' field and clicking the 'Output' button.
2850 .. _edi-accounts-label:
2853 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2855 From here you can set up the information needed to connect to your
2856 acquisitions vendors.
2860 Before you begin you will need at least one :ref:`Vendor set up in
2861 Acquisitions <add-a-vendor-label>`.
2863 To add account information click the 'New account' button.
2867 In the form that appears you will want to enter your vendor information.
2869 New account information
2871 Each vendor will have one account.
2873 .. _library-eans-label:
2876 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2878 A library EAN is the identifier the vendor gives the library to send
2879 back to them so they know which account to use when billing. One EDI
2880 account can have multiple EANs.
2882 To add an EAN click the 'New EAN' button.
2886 In the form that appears enter the information provided by your vendor.
2890 .. _additional-parameters-label:
2892 Additional parameters
2893 --------------------------------------------
2895 - *Get there:* More > Administration > Additional parameters
2897 .. _z39.50/sru-servers-label:
2900 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2902 Z39.50 is a client/server protocol for searching and retrieving
2903 information from remote computer databases, in short it's a tool used
2904 for copy cataloging.
2906 SRU- Search/Retrieve via URL - is a standard XML-based protocol for
2907 search queries, utilizing CQL - Contextual Query Language - a standard
2908 syntax for representing queries.
2910 Using Koha you can connect to any Z39.50 or SRU target that is publicly
2911 available or that you have the log in information to and copy both
2912 bibliographic and/or authority records from that source.
2914 - *Get there:* More > Administration > Additional parameters >
2917 Koha comes with a default list of Z39.50/SRU targets set up that you can
2918 add to, edit or delete
2922 To find additional Z39.50 targets you use IndexData's IRSpy:
2923 `http://irspy.indexdata.com <http://irspy.indexdata.com/>`__ or the
2924 Library of Congress's list of targets http://www.loc.gov/z3950/
2926 .. _add-a-z39.50-target-label:
2929 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2931 - From the main Z39.50 page, click 'New Z39.50 server'
2935 - 'Z39.50 server' should be populated with a name that will help you
2936 identify the source (such as the library name).
2938 - 'Hostname' will be the address to the Z39.50 target.
2940 - 'Port' tells Koha what port to listen on to get results from this
2943 - 'Userid' and 'Password' are only required for servers that are
2946 - Check the 'Preselected' box if you want this target to always be
2947 selected by default.
2949 - 'Rank' lets you enter where in the list you'd like this target to
2952 - If this is left blank the targets will be in alphabetical
2955 - 'Syntax' is the MARC flavor you use.
2957 - 'Encoding' tells the system how to read special characters.
2959 - 'Timeout' is helpful for targets that take a long while. You can
2960 set the timeout so that it doesn't keep trying the target if
2961 results aren't found in a reasonable amount of time.
2963 - 'Record type' lets you define if this is a bibliographic or an
2966 - 'XSLT file(s)' lets enter one or more (comma-separated) XSLT file
2967 names that you want to apply on the search results.
2969 - When retrieving records from external targets you may wish to
2970 automate some changes to those records. XSLT's allow you to do
2971 this. Koha ships with some sample XSLT files in the
2972 /koha-tmpl/intranet-tmpl/prog/en/xslt/ directory ready for use:
2974 - Del952.xsl: Remove items (MARC21/NORMARC)
2976 - Del995.xsl: Remove items (UNIMARC)
2978 - Del9LinksExcept952.xsl: Remove $9 links. Skip item fields
2981 - Del9LinksExcept995.xsl: Remove $9 links. Skip item fields
2984 .. _suggested-bibliographic-z39.50-targets-label:
2986 Suggested bibliographic Z39.50 targets
2987 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2989 Koha libraries with open Z39.50 targets can share and find connection
2990 information on the Koha wiki:
2991 http://wiki.koha-community.org/wiki/Koha_Open_Z39.50_Sources. You can
2992 also find open Z39.50 targets by visiting IRSpy:
2993 http://irspy.indexdata.com.
2995 The following targets have been used successfully by other Koha
2996 libraries (in the Americas):
2998 - ACCESS PENNSYLVANIA 205.247.101.11:210 INNOPAC
3000 - CUYAHOGA COUNTY PUBLIC webcat.cuyahoga.lib.oh.us:210 INNOPAC
3002 - GREATER SUDBURY PUBLIC 216.223.90.51:210 INNOPAC
3004 - HALIFAX PUBLIC catalogue.halifaxpubliclibraries.ca:210 horizon
3006 - HALTON HILLS PUBLIC cat.hhpl.on.ca:210 halton\_hills
3008 - LIBRARY OF CONGRESS lx2.loc.gov: 210 LCDB
3010 - LONDON PUBLIC LIBRARY catalogue.londonpubliclibrary.ca:210 INNOPAC
3012 - MANITOBA PUBLIC library.gov.mb.ca:210 horizon
3014 - MILTON PL cat.mpl.on.ca:210 horizon
3016 - NATIONAL LIBRARY OF WALES cat.llgc.org.uk:210 default
3018 - NHUPAC 199.192.6.130:211 nh\_nhupac
3020 - OCEAN STATE LIBRARIES (RI) catalog.oslri.net:210 INNOPAC
3022 - OHIOLINK olc1.ohiolink.edu:210 INNOPAC
3024 - PUBCAT prod890.dol.state.vt.us:2300 unicorn
3026 - SAN JOAQUIN VALLEY PUBLIC LIBRARY SYSTEM (CA) hip1.sjvls.org:210
3029 - SEATTLE PUBLIC LIBRARY ZSERVER.SPL.ORG:210 HORIZON
3031 - TORONTO PUBLIC symphony.torontopubliclibrary.ca:2200 unicorn
3033 - TRI-UNI 129.97.129.194:7090 voyager
3035 - VANCOUVER PUBLIC LIBRARY z3950.vpl.ca:210 Horizon
3037 .. _suggested-authority-z39.50-targets-label:
3039 Suggested Authority Z39.50 Targets
3040 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
3042 The following targets have been used successfully by other Koha
3043 libraries (in the Americas):
3045 - LIBRARIESAUSTRALIA AUTHORITIES
3046 z3950-test.librariesaustralia.nla.gov.au:210 AuthTraining Userid:
3047 ANLEZ / Password: z39.50
3049 - LIBRARY OF CONGRESS NAME AUTHORITIES lx2.loc.gov:210 NAF
3051 - LIBRARY OF CONGRESS SUBJECT AUTHORITIES lx2.loc.gov:210 SAF
3053 .. _add-a-sru-target-label:
3056 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
3058 - From the main Z39.50/SRU page, click 'New SRU server'
3062 - 'Server name' should be populated with a name that will help you
3063 identify the source (such as the library name).
3065 - 'Hostname' will be the address to the Z39.50 target.
3067 - 'Port' tells Koha what port to listen on to get results from this
3070 - 'Userid' and 'Password' are only required for servers that are
3073 - Check the 'Preselected' box if you want this target to always be
3074 selected by default.
3076 - 'Rank' lets you enter where in the list you'd like this target to
3079 - If this is left blank the targets will be in alphabetical
3082 - 'Syntax' is the MARC flavor you use.
3084 - 'Encoding' tells the system how to read special characters.
3086 - 'Timeout' is helpful for targets that take a long while. You can
3087 set the timeout so that it doesn't keep trying the target if
3088 results aren't found in a reasonable amount of time.
3090 - 'Additional SRU options' is where you can enter additional options
3091 of the external server here, like sru\_version=1.1 or
3092 schema=marc21, etc. Note that these options are server dependent.
3094 - 'SRU Search field mapping' lets you add or update the mapping from
3095 the available fields on the Koha search form to the specific
3096 server dependent index names.
3098 - To further refine your searches, you could add the following
3099 index names to the SRU search field mappings. To do this, edit
3100 the server and click the Modify button next to this field.
3102 +---------------+---------------------------+
3103 | Title | dc.title |
3104 +---------------+---------------------------+
3105 | ISBN | bath.isbn |
3106 +---------------+---------------------------+
3107 | Any | cql.anywhere |
3108 +---------------+---------------------------+
3109 | Author | dc.author |
3110 +---------------+---------------------------+
3111 | ISSN | bath.issn |
3112 +---------------+---------------------------+
3113 | Subject | dc.subject |
3114 +---------------+---------------------------+
3115 | Standard ID | bath.standardIdentifier |
3116 +---------------+---------------------------+
3120 - 'XSLT file(s)' lets enter one or more (comma-separated) XSLT file
3121 names that you want to apply on the search results.
3123 - When retrieving records from external targets you may wish to
3124 automate some changes to those records. XSLT's allow you to do
3125 this. Koha ships with some sample XSLT files in the
3126 /koha-tmpl/intranet-tmpl/prog/en/xslt/ directory ready for use:
3128 - Del952.xsl: Remove items (MARC21/NORMARC)
3130 - Del995.xsl: Remove items (UNIMARC)
3132 - Del9LinksExcept952.xsl: Remove $9 links. Skip item fields
3135 - Del9LinksExcept995.xsl: Remove $9 links. Skip item fields
3138 .. _did-you-mean?-label:
3141 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3143 *Get there:* More > Administration > Additional parameters > Did you
3146 Koha can offer 'Did you mean?' options on searches based on values in
3147 your :ref:`authorities <authorities-label>`.
3151 Did you mean? only works in the OPAC at this time. The intranet
3152 options are here for future development.
3154 Using this page you can control which options Koha gives patrons on
3155 their search results.
3159 To turn on the 'Did you mean?' bar on your search results you need to
3160 check the box next to each plugin you would like to use. The two plugins
3161 you have to choose from are:
3163 - The ExplodedTerms plugin suggests that the user try searching for
3164 broader/narrower/related terms for a given search (e.g. a user
3165 searching for "New York (State)" would click the link for narrower
3166 terms if they're also interested in "New York (City)"). This is only
3167 relevant for libraries with highly hierarchical authority data.
3169 - The AuthorityFile plugin searches the authority file and suggests the
3170 user might be interested in bibs linked to the top 5 authorities
3172 If you want one plugin to take priority over another you simply drag it
3177 If you choose both plugins you will see several options at the top of
3182 If you choose just the AuthorityFile you'll see just authorities.
3186 .. _column-settings-label:
3189 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3191 This administration area will help you hide or display columns on fixed
3192 tables throughout the staff client.
3194 - *Get there:* Administration > Additional parameters > Column settings
3198 Clicking on the module you'd like to edit tables for will show you the
3199 options available to you.
3201 This area lets you control the columns that show in the table in
3202 question. If nothing is hidden you will see no check marks in the 'is
3203 hidden by default' column.
3207 And will see all of the columns when viewing the table on its regular
3212 If columns are hidden they will have checks in the 'is hidden by
3217 And hidden when you view the table.
3221 You can also toggle columns using the 'Show/hide columns' button in the
3222 top right of the page
3228 Any tables with columns listed here have the option to export to Excel, export to CSV,
3229 copy, or print within the table header
3231 .. _audio-alerts-label:
3234 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3236 If you have your :ref:`AudioAlerts` preference set to
3237 'Enable' you will be able to control the various alert sounds that Koha
3238 uses from this area.
3240 - *Get there:* More > Administration > Additional parameters > Audio
3243 Each dialog box in Koha has a CSS class assigned to it that can be used
3244 as a selector for a sound.
3248 You can edit the defaults by clicking the 'Edit' button to the right of
3253 You can assign alerts to other CSS classes in Koha by entering that
3254 information in the selector box. For example if you enter
3258 body:contains('Check in message')
3260 Then when you visit the checkin page you will hear an alert.
3262 Every page in Koha has a unique ID in the body tag which can be used to
3263 limit a sound to a specific page
3265 Any ID selector (where HTML contains id="name\_of\_id" ) and can also be
3266 a trigger as: #name\_of\_selector
3268 .. _sms-cellular-providers-label:
3270 SMS cellular providers
3271 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3275 This option will only appear if the
3276 :ref:`SMSSendDriver <smssenddriver,-smssendusername,-and-smssendpassword-label>` preference is set to 'Email'
3278 From here you can enter as many cellular providers as you need to send
3279 SMS notices to your patrons using the email protocol.
3283 Some examples in the US are:
3285 +---------------------+-----------------------------+
3286 | Mobile Carrier | SMS Gateway Domain |
3287 +=====================+=============================+
3288 | Alltel | sms.alltelwireless.com |
3289 +---------------------+-----------------------------+
3290 | AT&T | txt.att.net |
3291 +---------------------+-----------------------------+
3292 | Boost Mobile | sms.myboostmobile.com |
3293 +---------------------+-----------------------------+
3294 | Project Fi | msg.fi.google.com |
3295 +---------------------+-----------------------------+
3296 | Republic Wireless | text.republicwireless.com |
3297 +---------------------+-----------------------------+
3298 | Sprint | messaging.sprintpcs.com |
3299 +---------------------+-----------------------------+
3300 | T-Mobile | tmomail.net |
3301 +---------------------+-----------------------------+
3302 | U.S. Cellular | email.uscc.net |
3303 +---------------------+-----------------------------+
3304 | Verizon Wireless | vtext.com |
3305 +---------------------+-----------------------------+
3306 | Virgin Mobile | vmobl.com |
3307 +---------------------+-----------------------------+
3309 Table: SMS provider examples
3311 To add new providers enter the details in the form and click 'Add new'
3316 These options will appear in the OPAC for patrons to choose from on the
3317 :ref:`messaging tab <my-messaging-label>` if you have
3318 :ref:`EnhancedMessagingPreferences`
projects / kohadocs.git / blob