This page allows you to set the system preferences that control much of the basic behavior of Koha. These preferences should be set before any other parameters.
Note
If the system preferences page (or any other page you have seen so far) is in French, that means the installer(s) have installed both the English and the French "SQL Directories" (or only the French SQL Directory). While you can change the language of much of Koha from this page, the language of the descriptions that appear on this page cannot be changed. If your descriptions are in the wrong language, ask the installers to re-install now (before you start setting parameters) and install only your preferred language SQL Directory.
The layout of this page is pretty simple. Three columns list the name of the preference, its current value, and a brief description of what the preference controls. The preferences grouped into tabs relating them to Koha functions: Administration, Acquisitions, the catalogue, Circulation, Members, the OPAC, and some other preferences that do not fit into the other categories. Some of these you won't need to change at all.
To change a preference, click on the folder icon. Don't click on the trash icon, which deletes the preference, unless you're a Koha developer -- and even then make a backup of the systempreferences table first. There is also a button at the bottom of the page for adding more system preferences. Most libraries will have no reason to either add or delete system preferences; the only time such action would be needed would be if a library was making some major changes to the Koha code. But the Koha philosophy is to give you as many options as possible, so this screen makes it easy to add and delete preferences if necessary.
Tip
The preferences (variables) and their values are stored in the systempreferences table in the Koha database.
When you choose to edit a preference, there is a standardized screen that appears to allow you to make your modifications. This screen requires some explanation.
The upper box in this window contains a very brief description of the system preference you are editing, the preference ("Variable") name, and its current value. This is the box in which you will make your changes and save them by clicking on the "OK" button. But what is that strange lower box labeled "Koha Internal" that tells you that you probably have no reason to change anything there? That box defines the type of values that you will be allowed to enter in the "Value" area of the upper box. In the screenshot that we are using as our example, the variable is the "acquisitions" system preference and the type (as defined in the lower box) is a "choice" variable -- meaning that you will be able to select a value from a pull-down list. The values that will appear in the pull-down list are defined in the "Variable options" area of the lower box. Had the variable been of a type that allowed you to type anything you wanted in the "Value" area (such as an e-mail address or an ISBD formula), then the "Variable type" in the lower box would be "free." If you wanted a bigger area for typing (and you might for defining an ISBD formula), then you could change "free" to "Textarea" and define the size of the text area by putting the number of columns and rows in the "Variable options" area. But in most cases, you will have no need to change anything in the lower box and will simply change the "Value" in the upper box and save it by clicking "OK." Again, Koha gives you the ability to change things you will probably never need to change -- but in case you might, you can.
There is no recommended order for setting the preferences, so we will look at them group by group.
- dateformat
Choose "metric," "us," or "iso" date format:
"us" = mm/dd/yyyy
"metric" = dd/mm/yyyy
"iso" = yyyy/mm/dd
This controls how dates are displayed on the Koha screens, not how they are stored in the database (usually yyyy-mm-dd).
- insecure
If you are planning to be the only user of your Koha installation and find the login annoying, you can set this preference to "yes" to turn security off. But in almost every other case, the best choice is "no." If you choose "yes," users do not have to login and all information is open to anyone. Obviously, if your Koha is going to be used for a regular lending library, you want to have security turned on -- just say "no."
- acquisitions
The choices are either "normal" or "simple." "Normal" sets the system to track orders and update budgeting and vendor information as you add materials to your collection. "Simple" tells Koha that you are going to add materials to the collection without tracking orders. So if you plan to use Koha to monitor your budget and your orders with vendors, leave this preference as "normal." If you already have a system for monitoring your budget and orders (or simply don't plan to do any monitoring), change this to "simple."
- gist
The "gist" is the "GST" (Good and Sales Tax) rate. If your local tax laws require you to pay taxes on purchases from your suppliers, enter the tax rate here, expressed as a decimal number and not a percent. (In other words, if the tax rate is 6.5 percent, enter ".065".). Set to "0" if you are not required to pay tax.
Note
The "gist" preference does not apply to fees and fines you charge borrowers, so if you are required to charge tax on such fees, you will need to include the tax in the fee amounts you set in the "Item types" and "Issuing rules" parameters.
- authoritysep
The description reads, "The separator used in authority/thesaurus. Usually '--'." What does that mean?
Basically, Koha is asking what symbol is used in your language to separate the levels of your subject headings. In English, for example, subject headings and their subdivisions are separated by "--" as in "Women--United States--Bibliography." If a different symbol is used for this purpose in your language, change the value of this variable to that symbol.
A detailed explanation of how Koha handles authorities will follow in the discussion of setting up your MARC parameters.
- ISBD
Koha 2.2 can display records in a format that roughly conforms to the International Standard Bibliographic Description standards. ISBD is a family of standards developed by the Section on Cataloguing of the International Federation of Library Associations and Institutions (IFLA) to standardize, as much as possible, the descriptive portion of bibliographic records produced in different countries. The standards specify the descriptive elements constituting the record, their order, and the punctuation between them. (See http://www.ifla.org/VII/s13/pubs/isbdg2004.pdf)
In order to do this Koha requires that you fill this field with the proper set of instructions, or formula, for organizing your MARC tags into an ISBD-conformant display. The online help (click "Help" in the upper right corner of the System preferences screen) provides some instructions and an example of a French language display using UNIMARC tags.
Libraries using MARC 21 instead of UNIMARC probably have records that already contain punctuation conforming to the Anglo-American Cataloging Rules, second edition (AACR2). A reasonably good "AACR2" display can be constructed for such libraries, too -- just put something like this in the
valuefield for the ISBD variable:#050|<label>Call Number: </label>|{082a}{050a}{ / 050b}|<br/><br/> #100|<label>Main Entry: </label>|{100a}{ 100b}{ 100c}{ 100d}{110a}{ 110b}{130a}|<br/> #245|<label> </label>|{245a}{ 245b}{ 245c}{ 245h}{ 246i}{ 246a}| #260||{ 250a}{ 250b}{-- 260a}{ 260b}{ 260c}| #300|<br/><label> </label>|{300a}{ 300b}{ 300c}|<br/> #020|<br/><label> ISBN</label>|{ 020a}{ 024a}|<br/> #440|<br/><label> </label>|{440a}{ 440v}|<br/> #500||{\n500a}|<br/> #511||{511a, }| #520|<label> </label>|{\n520a}{ 520b}| #600|<br/><label>Subjects: </label>|{ 600a.}| #650|<label> </label>|{\n650a }{-- 650x}{-- 650z}{-- 650y}| #651|<label> </label>|{\n651a }{-- 651x}{-- 651z}{-- 651y}| #852|<br/><br/><label>Held at: </label>|{\n852a}{, 852b}{, 852c}|See the related comments in the User Comments section.
- autoBarcode
The barcode number to be assigned to items is automatically assigned (sequentially) by Koha if this is set to "yes" ("1" = "yes") and you set your MARC preference to "no.". You will not be asked for a starting number or for any preferred type of barcode if you choose "yes" -- you simply get whatever Koha gives you. For most libraries, where preprinted barcodes are attached to items as they are cataloged, this will not work. In these cases, you should choose "no" and plan on adding the barcode to the catalogue record while you are adding other item information (such as price, accession date, etc.).
- hide_marc
This is a feature for libraries that want to use MARC records, but don't want to see "too much" MARC. For librarians unfamiliar with MARC, some of the complexities of tags and subfields can be daunting. This feature hides some of those complexities.
- itemcallnumber
This is one system preference that you may want to set after you set your other MARC parameters. This preference holds the MARC tag/subfield that is used to calculate the itemcallnumber variable that is a new Koha feature starting with version 2.2.2. If you set this preference now, please make a note of it and keep it handy when you set your other MARC parameters. If you decide to set it after setting your other MARC parameters, don't forget to come back to it!
Note
Prior to version 2.2.2, Koha could use several MARC subfields to hold various parts of a single call number that was assigned to a group of items related to a single bibliographic record. Displaying the call number correctly often required the user to modify some of the display templates to suit their individual library's cataloging practice. The itemcallnumber feature greatly simplifies Koha's handling of call numbers in screen displays, but the previous option is still available to Koha users.
Putting an itemcallnumber subfield in a MARC record holdings tag allows you to set a call number on individual items, rather than on an entire group of items related to the same bibliographic record. While MARC holdings tags (either the 852 MARC 21 tag, or a user-defined 9xx tag) often contain subfields for holding particular parts of a call number, they may not have a subfield that is set up to hold the entire call number. If you choose to use item call numbers -- for example, to place a copy of a book in one branch in the reference collection, while in another branch it is placed in the non-fiction collection -- then you must use this preference to tell Koha which subfield in your MARC holdings tag contains the entire call number.
Please note that in the example given above, the issuing rules for the item in the reference collection and for the item in the non-fiction collection will be the same: issuing rules are determined by the item type, not the item call number. To assign different issuing rules to the two items, they would have to be assigned to separate bibliographic records, with differing item types for each record. There will be more discussion of item types when we come to that section of our discussion of parameters.
Tip
If you are migrating MARC records that do not have the entire call number in a subfield of the holdings tag, and you want to use the itemcallnumber feature, a programmer can write a simple script to compile the parts of your call numbers and insert the newly-constructed entire call numbers into your holdings tags.
See the related comment in the User Comments section.
- marc
This preference allows you to turn MARC support on or off. Set it to "no" if you do not intend to use MARC records.
- marcflavour
Koha not only lets you specify whether or not you will be using MARC records, it also gives you a choice of MARC "flavors" -- MARC 21 or UNIMARC. Your choice will tell Koha how to interpret your MARC records.
- ReturnBeforeExpiry
This preference, if set to 1, will not allow a borrower to borrow items past the expiration date of their membership. Instead, Koha will recalculate the due date to be the same as the membership expiration date.
This feature is useful for schools, which may set students' expiration dates to be the same as their graduation dates. The library would want all items to be returned before the students graduate and depart.
- maxoutstanding
This preference sets the maximum amount of outstanding charges a borrower may owe before he/she is barred from making reserve requests. The number represents units of your local currency -- for example, "5" means "$5.00," if the dollar is your local currency. Partial "units" will be rounded to the nearest whole unit. For example, 5.25 will not be stored as "5.25," but as "5" -- so keep it simple!
If you want to have no limits, leave this preference set at 0.
- maxreserves
This preference sets the maximum number of active reserves a borrower can have at any one time.
- noissuescharge
This sets the maximum amount of outstanding charges a borrower may owe before he/she is barred from checking out items. As with maxoutstanding, the number represents units of your local currency.
- printcirculationslips
If your library uses receipt printers to provide borrowers with a list of items they have just checked out, you should turn this option on. If set to 1, circulation "slips" are printed on a receipt printer connected (or networked) to your server. If set to 0, no slips are printed.
- NotifyBorrowerDeparture
This system preference represents a number of days. If a borrower tries to check out items, and their registration is due to expire within this number of days, then the librarian sees a warning message. For example, is a borrower's registration is due to expire on the 15th of the month and NotifyBorrowerDeparture is set to 10, then beginning on the 5th of the month the librarian will see a warning if the borrower checks out items. This is a useful feature for schools, where a student's registration often expires on the date when they are scheduled to leave the school. Compare this system preference to the ReturnBeforeExpiry preference described in the preceding section.
- autoMemberNum
The membership number (patron card number) to be assigned to new library users is automatically assigned by Koha if this is set to "yes" ("1" = "yes"). As with the autoBarcode preference, if you choose "1" you will not be asked for a starting barcode or barcode type. For libraries that use preprinted barcodes on their library cards, this preference should be set to "0" (="no").
Tip
Both autoBarcode and autoMemberNum refer to the visible numbers that will be attached to items and borrower cards. Koha will also assign internal control numbers for items and borrowers, called
itemnumberandborrowernumber, that are both used for cross-referencing data in various Koha tables. These internal control numbers are always automatically assigned by Koha.- checkdigit
This preference determines the type of validity checks that will be done on membership numbers (patron card numbers): none or "Katipo" style checks. In almost all cases, you will choose "none." The checkdigit function was developed for the Horowhenua Library Trust ("HLT"), the library system that commissioned Katipo Communications, Ltd. to write the first version of Koha at the end of 1999. The function checks if patron card numbers that are automatically generated (when the autoMemberNum preference is turned on) are in the correct sequence and match pre-printed barcodes purchased by HLT. Unless you are starting a new library and using the same pre-printed barcodes used by HLT, you will leave this preference set to "none."
- BiblioDefaultView
This preference defines how Koha will display a bibliographic record that has been retrieved from a catalogue search. The choices are "normal," "marc" or "isbd."
"normal" displays the record in the standard Koha format, showing most of the basic bibliographic information.
"marc" displays the entire MARC record from Koha's MARC database.
"isbd" displays an ISBD formatted record. (See the "ISBD" system preference below for more information about ISBD.
All of these display modes can be modified by changing the HTML templates you are using, and you also have the ability to switch between views once the record has been displayed on the screen. This preference simply sets Koha's initial behavior when displaying a record. When first setting up your Koha system, "normal" is generally the best choice.
- LibraryName
The text of this variable will be the library name and/or message that will be shown on the main OPAC page.
If you are not familiar with HTML (Hyper-Text Markup Language), you may want to find someone to help with this. You will be using simple HTML tags to format your name and message. Here, for example, is the default name and message:
<i><b>Koha<br/>Free Software ILS<br/><br/></b>Koha : a gift, a contribution<br/> in Maori</i>
The letters and slashes enclosed by wedges (<>) are the HTML tags. All text between <i> and </i> will appear in italics, all text between <b> and </b> will be in bold face, and the <br/> ("break") tags mark the ends of lines of text.
- OpacPasswordChange
This preference controls whether or not a borrower can change their password through the OPAC. It is particularly useful for applications that use LDAP authentication for borrowers, since Koha would have no control over the LDAP password.
- SubscriptionHistory
This system preference sets the type of details that OPAC users will see when they search for information about your library's periodical subscriptions. The choices are "simplified" or "full."
- simplified
The OPAC user will see the name of the periodical, the date when the library began receiving the periodical, how often the periodical is issued, and the date when the library last renewed the subscription (or the date of the last issue received, if the library no longer subscribes). This information will be followed by a list of received issues and missing issues.
- full
The OPAC user will see the name of the periodical followed by a list of issues, showing the date of each issue, the number of each issue, and the status of each issue -- arrived, awaited, late, or missing.
- hidelostitems
If you do not want items in your catalogue which have been tagged as "lost" to appear in the results of OPAC searches, set this preference to "Yes." If you always want all items displayed, regardless of their "lost" status, leave this value set to "No."
- opaclanguages
This preference sets your language preference.
Despite the name, this choice can control the language used for all Koha screens, not just the OPAC. All of Koha is available in either English ("en") or French ("fr"), portions have been translated into Italian ("it") and Taiwan-Chinese ("zh-TW"), and more languages are being added. The top language in your list will be tried first when Koha displays a screen of information.
- opaclargeimage
This system preference allows you to place your own custom logo on the OPAC main page. Normally, OPAC users will see the default Koha logo:
If you want to use your own logo, this system preference should contain the path to your
.gifimage file. (The size of the default logo is 310x440 pixels.)- opacsmallimage
As with the opaclargeimage, this preference allows you to substitute a custom logo for the default Koha logo that normally appears in the upper left corner of OPAC pages other than the main page. (The size of the default small Koha logo is 35x50 pixels.)
- opacstylesheet
In order to be compliant with the web standards recommended by the World Wide Web Consortium, Koha makes use of cascading style sheet (CSS) files to determine many of the aspects of how a Koha screen appears. The default CSS file for the OPAC is
opac.css, which can be found in the/usr/local/koha/opac/htdocs/opac-tmpl/default/en/includesdirectory in most Koha installations. There is also a second choice of style sheet if you set this system preference to/opac-tmpl/css/opac2.css.If you would like to use your own cascading style sheet for the OPAC, enter the complete "href" path to the file as the value of this preference. For example, the href path (or URL) to the default style sheet would be
/opac-tmpl/default/en/includes/opac.css.- opacthemes
Koha makes use of HTML templates to build the web pages that are displayed on the screen. By modifying these templates, the user can change the way data appears on Koha's screens.
There are several groups of templates that have been developed which are complete enough to qualify as OPAC "themes," providing a consistent and distinctive look and feel across many of the Koha OPAC pages. Two themes in particular -- "css" and "npl" -- provide some interesting designs for OPAC pages:
- css
is the current OPAC theme that is installed by default. (The theme that is actually named "default" is similar, but not currently as web compliant as the css theme.) Developed primarily by Paul Poulain, it uses cascading style sheets -- hence the name "css." Unless otherwise noted, the screen shots in this manual depict the css theme.
- npl
is a completely different theme, though it also uses cascading style sheets. This theme was developed by Owen Leonard at the Nelsonville Public Library -- hence the name "npl."
As with opaclanguages, the first choice on your list will be tried for each page, but if there is no template for that page in your chosen theme, Koha will revert to the default theme.
Tip
In most Koha installations, the templates for each theme are found under the
/usr/local/koha/opac/htdocs/opac-tmpldirectory.- suggestion
If set to 1, the Suggestions feature is activated in the OPAC. This feature allows OPAC users to suggest book purchases. When a suggestion is made in the OPAC, it is assigned the status "ASKED." A librarian then manages the suggestion and can set the status to "REJECTED" or "ORDERED." When a book is ordered and has arrived in the library, the status becomes "AVAILABLE." Suggestions that are not yet "AVAILABLE" are visible to all users of the OPAC.
- virtualshelves
This preference turns the virtual shelves option on or off ("1" or "0"). Users who login to the OPAC can set up and manage their own "virtual bookshelves" of favorite library items if this feature is turned on.
There are three types of virtual shelves:
- Private
These shelves can only be viewed or modified by the logged-in user who created them. For example, a borrower might select titles of books in the library's catalogue that he/she wants to read someday and can add these titles to a private virtual shelf for later reference.
- Public
Any logged-in OPAC user can view these virtual shelves, but only the shelf creator can modify the contents. This type of virtual shelf might be used by a teacher to keep a list of library items for students to read, or a library might create "bestseller" lists for the public using public virtual shelves.
- Free
Any logged-in OPAC user can view or modify these virtual shelves. These shelves thus become a sort of "public forum." Someone might start a free virtual shelf of "best computer books," for example, and other users could then add (or delete!) items from the list.
- delimiter
When exporting statistical data for reports, Koha can produce delimited files for importing into other applications. This preference sets the default delimiter. For instance, if you want Koha to produce comma-separated value (csv) files for importing into a spreadsheet application, you would choose the "," as the default delimiter.
- Disable_Dictionary
The Koha OPAC by default allows users to "pre-search" the catalogue for words in titles, authors names, or subjects. This feature can greatly reduce the number of inappropriate records returned by a catalogue search, but some libraries may want to disable the feature by turning this preference on.
The feature is accessed through the Advanced Search and is triggered by clicking on the three dots [...] after the Title, Author, or Subject search fields.
By choosing from the list of terms returned by the dictionary search, a more accurate search of the general catalogue can be accomplished.
- IndependantBranches
If this preference is turned on, all branches are treated as independent libraries working with one common database. Any staff member (with the necessary authority) can create basic bibliographic records for the database, or issue and return any book in the database. But staff at one branch cannot add items to another branch, or add borrowers to another branch, nor can they modify items or borrowers that "belong" to another branch. The exception to this rule is that any librarians with "superlibrarian" privileges can do any of these things; they are not restricted by this system preference.
Note
This preference does not affect the display of catalogue records in the OPAC -- searches will always display results from all branches.
- KohaAdminEmailAddress
This is the e-mail address that will receive requests from borrowers for modification of their records.
When borrowers login to the OPAC and review their accounts, they may see errors in their personal details. Koha allows them to fill out a form requesting corrections to their details, and this form is then e-mailed to a library administrator for review and action. This system preference tells Koha how to address those e-mails
- MIME
Koha can export statistical reports to spreadsheet files in either Microsoft Excel or OpenOffice format. Use this preference to determine which format Koha will use.
- template
This preference should probably really be called "intranetthemes," because it is the counterpart of the "opacthemes" preference. This preference controls which group of templates will be used for your Intranet screens. Currently the only choices are "default" and "npl." The "css" and "vanilla" themes that are available for the OPAC are not available here, because they do not provide Intranet templates.
- timeout
This is the Inactivity timeout period (in seconds). If a workstation is idle for longer than this period, the user will have to login again.
Now that you have set all of your system preferences, it's time to return to the Parameters page and work your way through the rest of the things listed there.
(Send comments and remarks to <st.hedges AT gmail DOT com>. They will be added to this section.)
- Posted by Joshua Allen Holm
There is a minor problem with the ISBD values. The 082 entry for call number will not display when called on the #050 line.
This block should fix the problem:
#082|<label>Call Number: </label>|{082a}|<br/><br/> #050|<label>Call Number: </label<|{050a}{ / 050b}|<br/><br/> #100|<label>Main Entry: </label>|{100a}{ 100b}{ 100c}{100d}{110a}{ 110b}{130a}|<br/> #245|<label> </label>|{245a}{ 245b}{ 245c}{ 245h}{ 246i}{ 246a}| #260||{ 250a}{ 250b}{-- 260a}{ 260b}{ 260c}| #300|<br/><label> </label>|{300a}{ 300b}{300c}|<br/> #020|<br/><label> ISBN</label>|{ 020a}{ 024a}|<br/> #440|<br/><label> </label>|{440a}{ 440v}|<br/> #500||{\n500a}|<br/> #511||{511a, }| #520|<label> </label>|{\n520a}{ 520b}| #600|<br/><label>Subjects: </label>|{ 600a.}| #650|<label> </label>|{\n650a }{-- 650x}{-- 650z}{-- 650y}| #651|<label> </label>|{\n651a }{-- 651x}{-- 651z}{-- 651y}| #852|<br/><br/><label>Held at: </label>|{\n852a}{, 852b}{, 852c}|Anyone wishing to use these values, please note: When cutting and pasting the block above, it is very important to either remove all line breaks first or change the ISBD variable type to Textarea with the variable options 80|20 first. (Click OK after changing the variable type then click edit again to be able to paste the text into a text area).
- Posted by Thomas Dukleth
I have seen that the postings on the koha and koha-devel lists have had very incomplete and inaccurate ISBD mappings from MARC 21 for use in the Koha ISBD System Preference. Here is a coded mapping for ISBD for MARC 21.
The mapping that I have used follows the IFLA ISBD rules as closely as can reasonably be managed in the current Koha implementation with modest exception for some minor concessions to readability usage in Koha. Main author form is implemented appended before the first ISBD section which can be appropriate for a main author form. Subject headings have been separated by newlines for readability. It would be easy for the user to correct those issues. The initial main author may be removed. The newlines before 6XX $a may be replaced by a blank space. There are some punctuation and other issues remaining but they do not seem consistently resolvable without some major corrections to Koha functionality that would not happen before Koha 3.0. Some ISBD section closing punctuation might be improved with further experimentation. I have not thoroughly proofread my work but it seems to show no intrinsic problems to the extent that I have tested it.
#100||{ 100a }{ 100b }{ 100c }{ 100d }{ 110a }{ 110b }{ 110c }{ 110d }{ 110e }{ 110f }{ 110g }{ 130a }{ 130d }{ 130f }{ 130g }{ 130h }{ 130k }{ 130l }{ 130m }{ 130n }{ 130o }{ 130p }{ 130r }{ 130s }{ 130t }|<br/><br/> #245||{ 245a }{ 245b }{245f }{ 245g }{ 245k }{ 245n }{ 245p }{ 245s }{ 245h }| #246||{ : 246i }{ 246a }{ 246b }{ 246f }{ 246g }{ 246n }{ 246p }{ 246h }| #242||{ = 242a }{ 242b }{ 242n }{ 242p }{ 242h }| #245||{ 245c }| #242||{ = 242c }| #250| - |{ 250a }{ 250b }| #254|, |{ 254a }| #255|, |{ 255a }{ 255b }{ 255c }{ 255d }{ 255e }{ 255f }{ 255g }| #256|, |{ 256a }| #257|, |{ 257a }| #258|, |{ 258a }{ 258b }| #260| - |{ 260a }{ 260b }{ 260c }| #300| - |{ 300a }{ 300b }{ 300c }{ 300d }{ 300e }{ 300f }{ 300g }| #306| - |{ 306a }| #307| - |{ 307a }{ 307b }| #310| - |{ 310a }{ 310b }| #321| - |{ 321a }{ 321b }| #340| - |{ 3403 }{ 340a }{ 340b }{ 340c }{ 340d }{ 340e }{ 340f }{ 340h }{ 340i }| #342| - |{ 342a }{ 342b }{ 342c }{ 342d }{ 342e }{ 342f }{ 342g }{ 342h }{ 342i }{ 342j }{ 342k }{ 342l }{ 342m }{ 342n }{ 342o }{ 342p }{ 342q }{ 342r }{ 342s }{ 342t }{ 342u }{ 342v }{ 342w }| #343| - |{ 343a }{ 343b }{ 343c }{ 343d }{ 343e }{ 343f }{ 343g }{ 343h }{ 343i }| #351| - |{ 3513 }{ 351a }{ 351b }{ 351c }| #352| - |{ 352a }{ 352b }{ 352c }{ 352d }{ 352e }{ 352f }{ 352g }{ 352i }{ 352q }| #362| - |{ 362a }{ 351z }| #440| - |{ 440a }{ 440n }{ 440p }{ 440v }{ 440x }|. #490| - |{ 490a }{ 490v }{ 490x }|. #800| - |{ 800a }{ 800b }{ 800c }{ 800d }{ 800e }{ 800f }{ 800g }{ 800h }{ 800j }{ 800k }{ 800l }{ 800m }{ 800n }{ 800o }{ 800p }{ 800q }{ 800r }{ 800s }{ 800t }{ 800u }{ 800v }|. #810| - |{ 810a }{ 810b }{ 810c }{ 810d }{ 810e }{ 810f }{ 810g }{ 810h }{ 810k }{ 810l }{ 810m }{ 810n }{ 810o }{ 810p }{ 810r }{ 810s }{ 810t }{ 810u }{ 810v }|. #811| - |{ 811a }{ 811c }{ 811d }{ 811e }{ 811f }{ 811g }{ 811h }{ 811k }{ 811l }{ 811n }{ 811p }{ 811q }{ 811s }{ 811t }{ 811u }{ 811v }|. #830| - |{ 830a }{ 830d }{ 830f }{ 830g }{ 830h }{ 830k }{ 830l }{ 830m }{ 830n }{ 830o }{ 830p }{ 830r }{ 830s }{ 830t }{ 830v }|. #500|<br/><br/>|{ 5003 }{ 500a }| #501|<br/><br/>|{ 501a }| #502|<br/><br/>|{ 502a }| #504|<br/><br/>|{ 504a }| #505|<br/><br/>|{ 505a }{ 505t }{ 505r }{ 505g }{ 505u }| #506|<br/><br/>|{ 5063 }{ 506a }{ 506b }{ 506c }{ 506d }{ 506u }| #507|<br/><br/>|{ 507a }{ 507b }| #508|<br/><br/>|{ 508a }{ 508a }| #510|<br/><br/>|{ 5103 }{ 510a }{ 510x }{ 510c }{ 510b }| #511|<br/><br/>|{ 511a }| #513|<br/><br/>|{ 513a }{513b }| #514|<br/><br/>|{ 514z }{ 514a }{ 514b }{ 514c }{ 514d }{ 514e }{ 514f }{ 514g }{ 514h }{ 514i }{ 514j }{ 514k }{ 514m }{ 514u }| #515|<br/><br/>|{ 515a }| #516|<br/><br/>|{ 516a }| #518|<br/><br/>|{ 5183 }{ 518a }| #520|<br/><br/>|{ 5203 }{ 520a }{ 520b }{ 520u }| #521|<br/><br/>|{ 5213 }{ 521a }{ 521b }| #522|<br/><br/>|{ 522a }| #524|<br/><br/>|{ 524a }| #525|<br/><br/>|{ 525a }| #526|<br/><br/>|{\n510i }{\n510a }{ 510b }{ 510c }{ 510d }{\n510x }| #530|<br/><br/>|{\n5063 }{\n506a }{ 506b }{ 506c }{ 506d }{\n506u }| #533|<br/><br/>|{\n5333 }{\n533a }{\n533b }{\n533c }{\n533d }{\n533e }{\n533f }{\n533m }{\n533n }| #534|<br/><br/>|{\n533p }{\n533a }{\n533b }{\n533c }{\n533d }{\n533e }{\n533f }{\n533m }{\n533n }{\n533t }{\n533x }{\n533z }| #535|<br/><br/>|{\n5353 }{\n535a }{\n535b }{\n535c }{\n535d }| #538|<br/><br/>|{\n5383 }{\n538a }{\n538i }{\n538u }| #540|<br/><br/>|{\n5403 }{\n540a }{ 540b }{ 540c }{ 540d }{\n520u }| #544|<br/><br/>|{\n5443 }{\n544a }{\n544b }{\n544c }{\n544d }{\n544e }{\n544n }| #545|<br/><br/>|{\n545a }{ 545b }{\n545u }| #546|<br/><br/>|{\n5463 }{\n546a }{ 546b }| #547|<br/><br/>|{\n547a }| #550|<br/><br/>|{ 550a }| #552|<br/><br/>|{ 552z }{ 552a }{ 552b }{ 552c }{ 552d }{ 552e }{ 552f }{ 552g }{ 552h }{ 552i }{ 552j }{ 552k }{ 552l }{ 552m }{ 552n }{ 562o }{ 552p }{ 552u }| #555|<br/><br/>|{ 5553 }{ 555a }{ 555b }{ 555c }{ 555d }{ 555u }| #556|<br/><br/>|{ 556a }{ 506z }| #563|<br/><br/>|{ 5633 }{ 563a }{ 563u }| #565|<br/><br/>|{ 5653 }{ 565a }{ 565b }{ 565c }{ 565d }{ 565e }| #567|<br/><br/>|{ 567a }| #580|<br/><br/>|{ 580a }| #581|<br/><br/>|{ 5633 }{ 581a }{ 581z }| #584|<br/><br/>|{ 5843 }{ 584a }{ 584b }| #585|<br/><br/>|{ 5853 }{ 585a }| #586|<br/><br/>|{ 5863 }{ 586a }| #020|<br/><br/><label>ISBN: </label>|{ 020a }{ 020c }| #022|<br/><br/><label>ISSN: </label>|{ 022a }| #222| = |{ 222a }{ 222b }| #210| = |{ 210a }{ 210b }| #024|<br/><br/><label>Standard No.: </label>|{ 024a }{ 024c }{ 024d }{ 0242 }| #027|<br/><br/><label>Standard Tech. Report. No.: </label>|{ 027a }| #028|<br/><br/><label>Publisher. No.: </label>|{ 028a }{ 028b }| #013|<br/><br/><label>Patent No.: </label>|{ 013a }{ 013b }{ 013c }{ 013d }{ 013e }{ 013f }| #030|<br/><br/><label>CODEN: </label>|{ 030a }| #037|<br/><br/><label>Source: </label>|{ 037a }{ 037b }{ 037c }{ 037f }{ 037g }{ 037n }| #010|<br/><br/><label>LCCN: </label>|{ 010a }| #015|<br/><br/><label>Nat. Bib. No.: </label>|{ 015a }{ 0152 }| #016|<br/><br/><label>Nat. Bib. Agency Control No.: </label>|{ 016a }{ 0162 }| #600|<br/><br/><label>Subjects--Personal Names: </label>|{\n6003 }{\n600a}{ 600b }{ 600c }{ 600d }{ 600e }{ 600f }{ 600g }{ 600h }{--600k}{ 600l }{ 600m }{ 600n }{ 600o }{--600p}{ 600r }{ 600s }{ 600t }{ 600u }{--600x}{--600z}{--600y}{--600v}| #610|<br/><br/><label>Subjects--Corporate Names: </label>|{\n6103 }{\n610a}{ 610b }{ 610c }{ 610d }{ 610e }{ 610f }{ 610g }{ 610h }{--610k}{ 610l }{ 610m }{ 610n }{ 610o }{--610p}{ 610r }{ 610s }{ 610t }{ 610u }{--610x}{--610z}{--610y}{--610v}| #611|<br/><br/><label>Subjects--Meeting Names: </label>|{\n6113 }{\n611a}{ 611b }{ 611c }{ 611d }{ 611e }{ 611f }{ 611g }{ 611h }{--611k}{ 611l }{ 611m }{ 611n }{ 611o }{--611p}{ 611r }{ 611s }{ 611t }{ 611u }{--611x}{--611z}{--611y}{--611v}| #630|<br/><br/><label>Subjects--Uniform Titles: </label>|{\n630a}{ 630b }{ 630c }{ 630d }{ 630e }{ 630f }{ 630g }{ 630h }{--630k }{ 630l }{ 630m }{ 630n }{ 630o }{--630p}{ 630r }{ 630s }{ 630t }{--630x}{--630z}{--630y}{--630v}| #648|<br/><br/><label>Subjects--Chronological Terms: </label>|{\n6483 }{\n648a }{--648x}{--648z}{--648y}{--648v}| #650|<br/><br/><label>Subjects--Topical Terms: </label>|{\n6503 }{\n650a}{ 650b }{ 650c }{ 650d }{ 650e }{--650x}{--650z}{--650y}{--650v}| #651|<br/><br/><label>Subjects--Geographic Terms: </label>|{\n6513 }{\n651a}{ 651b }{ 651c }{ 651d }{ 651e }{--651x}{--651z}{--651y}{--651v}| #653|<br/><br/><label>Subjects--Index Terms: </label>|{ 653a }| #654|<br/><br/><label>Subjects--Facted Index Terms: </label>|{\n6543 }{\n654a}{--654b}{--654x}{--654z}{--654y}{--654v}| #655|<br/><br/><label>Index Terms--Genre/Form: </label>|{\n6553 }{\n655a}{--655b}{--655x }{--655z}{--655y}{--655v}| #656|<br/><br/><label>Index Terms--Occupation: </label>|{\n6563 }{\n656a}{--656k}{--656x}{--656z}{--656y}{--656v}| #657|<br/><br/><label>Index Terms--Function: </label>|{\n6573 }{\n657a}{--657x}{--657z}{--657y}{--657v}| #658|<br/><br/><label>Index Terms--Curriculum Objective: </label>|{\n658a}{--658b}{--658c}{--658d}{--658v}| #050|<br/><br/><label>LC Class. No.: </label>|{ 050a }{ / 050b }| #082|<br/><br/><label>Dewey Class. No.: </label>|{ 082a }{ / 082b }| #080|<br/><br/><label>Universal Decimal Class. No.: </label>|{ 080a }{ 080x }{ / 080b }| #070|<br/><br/><label>National Agricultural Library Call No.: </label>|{ 070a }{ / 070b }| #060|<br/><br/><label>National Library of Medicine Call No.: </label>|{ 060a }{ / 060b }| #074|<br/><br/><label>GPO Item No.: </label>|{ 074a }| #086|<br/><br/><label>Gov. Doc. Class. No.: </label>|{ 086a }| #088|<br/><br/><label>Report. No.: </label>|{ 088a }|- Posted by Paul Poulain
Let me explain
itemcallnumber.To define a "book", you need two different things:
its classification => meaning what the book is related to. Many libraries use Dewey, but not all. Many use LCCN (not in France), or another classification (for example : AMS for mathematical libraries).
its physical location in the shelves => the "call number".
The difficulty here is that most libraries, and they are right, have call numbered their "books" like they have classified them. So, classification = callnumber. But that's not the same concept:
a single book (= 1 callnumber) can have X classifications in some cases (= some subjects)
X books can have the same callnumber, or different call numbers, even if they have a single classification (=when the library has a callnumber not 100% related to classification)
That's why I introduced
itemcallnumberin Koha 2.2 branch. We need a CLASSIFICATION at the biblio level and a CALL NUMBER at the item level! Usually they contain the same information, that's why there is a systempreference where you can say "OK, computer, automatically report subfield XXXy from biblio into item when adding an item."