[Koha-cvs] CVS: koha/koha-tmpl/intranet-tmpl/default/fr/help/admin aqbookfund.tmpl,NONE,1.1 authorised_values.tmpl,NONE,1.1 authtypes.tmpl,NONE,1.1 biblio_framework.tmpl,NONE,1.1 branches.tmpl,NONE,1.1 categorie.tmpl,NONE,1.1 checkmarc.tmpl,NONE,1.1 currency.tmpl,NONE,1.1 issuingrules.tmpl,NONE,1.1 itemtypes.tmpl,NONE,1.1 koha2marclinks.tmpl,NONE,1.1 marc_subfields_structure.tmpl,NONE,1.1 marctagstructure.tmpl,NONE,1.1 printers.tmpl,NONE,1.1 stopwords.tmpl,NONE,1.1 systempreferences.tmpl,NONE,1.1 z3950servers.tmpl,NONE,1.1

[Paul POULAIN]

Update of /cvsroot/koha/koha/koha-tmpl/intranet-tmpl/default/fr/help/admin
In directory 
sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv16670/koha-tmpl/intranet-tmpl/default/fr/help/admin

Added Files:
        aqbookfund.tmpl authorised_values.tmpl authtypes.tmpl 
        biblio_framework.tmpl branches.tmpl categorie.tmpl 
        checkmarc.tmpl currency.tmpl issuingrules.tmpl itemtypes.tmpl 
        koha2marclinks.tmpl marc_subfields_structure.tmpl 
        marctagstructure.tmpl printers.tmpl stopwords.tmpl 
        systempreferences.tmpl z3950servers.tmpl 
Log Message:
french translation of librarian interface

--- NEW FILE ---
<!-- TMPL_INCLUDE name="help-top.inc" -->

<h1>Gestion des fonds de livres</h1>

<p>The first time you access this page, you will be asked to add your first 
book fund -- thereafter you will also have the option of editing and deleting 
book funds.</p>

<p>Book Funds may be ignored if you are setting your System Preferences to 
"simple" acquisitions: the funds are only useful when using "normal" 
acquisitions.</p><br>

<p>"Book Funds" are accounts that you establish to keep track of your 
expenditures for library materials. They may be used for any kind of material, 
not just books, and should match the lines in your materials budget. For 
instance, if your library establishes a budget line for books, another for 
audiovisual materials, a third line for magazines, and a fourth budget line for 
electronic databases, then you would have four Book Funds.</p>

<p>Each Book Fund has a unique fund code, limited to no more than five 
characters, that identifies it. You should decide on your fund codes (e.g. 
something like BOOKS, AV, MAGS, DATA for the four book funds described above) 
and enter the code in the "Book fund" box, then a full name in the "Name" 
box.</p>

<p>Once you have set up a fund, you will see a link to a page for setting up 
the fund budget. Here you will enter the beginning and ending dates of your 
budget year and the amount of money in that particular budget line. Do not use 
any kind of currency notation (like "$") or commas when entering the number. 
(Commas will be converted to decimal points.) NOTE: Your dates will not saved 
correctly unless you have set your date format in the System Preferences 
section of the Parameters page -- DO THIS BEFORE setting budgets.)</p>

<!-- TMPL_INCLUDE name="help-bottom.inc" -->
--- NEW FILE ---
<!-- TMPL_INCLUDE name="help-top.inc" -->
<h1>Administration des valeurs autorisées</h1>
<p>Koha allows you to restrict the values that catalogers can place in some 
MARC subfields to certain pre-defined "authorised" values. These authorised 
values are defined here.</p>

<p>For example, if your Koha installation is used by several libraries, and you 
use MARC21, you might want to restrict the 850a MARC subfield to the instition 
codes for just those libraries. In that case, you could define a new authorised 
values category (perhaps called "INST") and enter the institution codes as the 
authorised values for that category. Once the 850a subfield is linked to the 
INST authorised values category in your MARC tag structure, catalogers must 
choose a value from the list you define here, and may not type in any other 
value.</p>
<ul>
<li>HINT : if a subfield is non mandatory, Koha automatically adds an empty 
value to the authorised value list, that is selected by default. If the 
subfield is mandatory, no empty value is added (and you should NOT add it in 
the list, as it's an illegal value !)</li>
<li>HINT2 : in the MARC editor, the list is ordered by Text, NOT by value. So 
you can define a default value by putting a space before the value you want to 
see first. For example, if your list is related to language, you can set "ENG" 
as authorised value and " English" as text. The space will order "ENG" as first 
default value, and the space won't be shown (because HTML automatically discard 
useless spaces). Super hint : you can put a value 1st with N spaces, then 
another one 2nd with N-1 space,..., a value in Nth position with 1 space. Don't 
abuse of this feature, it's easier to find a value in an alphabetical order. It 
should be used only to have a default value</li>
</ul>
<p>Koha automatically sets up authorised value categories for your item types 
and branch codes, and you can link these authorised values to MARC subfields 
when you set up your MARC tag structure.</p>
<!-- TMPL_INCLUDE name="help-bottom.inc" -->

--- NEW FILE ---
<!-- TMPL_INCLUDE NAME="help-top.inc" -->
        <h1>Types d'autorité</h1>
        <p>Vous pouvez définir autant de types d'Autorités que vous le 
souhaitez.</p>
        <ul>
                <li>with the MARC structure button, you can define the MARC 
structure of a given authority type</li>
                <li>The tag reported must contain a MARC tag number. Every 
subfield in the selected tag will be copied to the "destination tag" in the 
biblio. for example, in UNIMARC, the tag 200 ot personal authority will be 
reported to 600, 700, 701, depending on what is cliqued in the biblio MARC 
editor.</li>
                <li>The summary contains an "ISBD" like description to explain 
how the entry must be shown in the result list. The syntax is : 
                <ul>
                        <li>[xxxFFFSyyy] where xxx are up to 3 digits BEFORE 
the field, FFF the field number, S the subfield code, yyy up to 3 digits AFTER 
the field.</li>
                        <li>Les éléments en dehors de []sont pris comme (y 
compris HTML)</li>
                        <li>les champs répétables sont gérés</li>
                <ul>
        </ul>
        <p>REMARQUE IMPORTANTE :</p>
        <p>
                In the biblio framework, the reported tag <b>MUST</b> contain a 
$9 subfield, activated in the tab where the tag is, and hidden (hidden maybe 
omitted, but the field has no reason to appear anywhere). The $9 subfield in 
the biblio will contain the Authority number (the internal Koha number)
        </p>
<!-- TMPL_INCLUDE name="help-bottom.inc" -->
--- NEW FILE ---
<!-- TMPL_INCLUDE NAME="help-top.inc" -->
        <h1>Grille de catalogage</h1>
        <p> Les frameworks bibliographiques sont utilisés pour vos notices 
bibliographiques</p>
        <p>Unlike Koha 2.0, in this version you can have more than 1 framework 
to catalogate differently various materials. You can, for example, define 1 
framework for monographies, 1 framework for serials, 1 framework for URL...</p>
        <p>Once a framework type is created, you can clic on "MARC structure" 
to define the exact MARC structure. The first time, Koha will ask you to select 
an existing framework to copy into the new one. Thus, you don't have to define 
all the MARC structure</p>
<!-- TMPL_INCLUDE name="help-bottom.inc" -->
--- NEW FILE ---
<!-- TMPL_INCLUDE NAME="help-top.inc" -->

<h1>Sites de la Bibliothèque</h1>

<p>Fill in information about your library service outlets on this page.</p>

<p>Begin by defining your branch categories. If, for example, you have one main 
library and several branch libraries, you might set up an "M" (Main) category 
and a "B" (Branch) category, with descriptions "Main Library" and "Branch 
Library."</p>

<p>Now add the names and addresses, phone numbers, etc of your libraries in the 
"Branches" section. (All of your libraries should be described here, not just 
the branch libraries.) Give each library a unique and easily-remembered code 
(maximum of four characters). This code will be used in Koha's database to 
identify each library. When libraries are listed in Koha, they will be listed 
in alphabetical order by code. (Note that until you set your branch the first 
time you use a computer to circulate items in Koha, the branch will default to 
the first library in the alphabetical code list -- be careful to set the branch 
the first time you use Koha or whenever you add a new computer!)</p>
<!-- TMPL_INCLUDE name="help-bottom.inc" -->
--- NEW FILE ---
<!-- TMPL_INCLUDE name="help-top.inc" -->
<h1>Catégories de lecteur</h1>

<p>Here is where you define the types of users of your library and how they 
will be handled.</p>

<p>Start by assigning a Category Code and a Description to each borrower type. 
The code is limited on no more than two characters and may be anything you 
choose. Four codes, however, have special meaning for Koha :</p>
<ul>
        <li>"I" can be used for institutional members, like other libraries 
that borrow from you, in which case Koha expects slightly different information 
about the institution;</li>
        <li>"A" (Adult) and "W" can be linked as "guarantors" to other 
borrowers who are their dependents.</li>
        <li>"C" (Children) his a borrower category that has a "guarantor"</li>
</ul>

<p>Enrollment period is a number indicating how many years a user's enrollment 
is valid. If you consider enrollments to expire after four years for example 
(as in a school, perhaps), then set this number to 4. If enrollments never 
expire, set this to an impossibly high number (99).</p>

<p>Upper Age Limit and Age Required set the age parameters for this type of 
user. If you issue children's cards to users between the ages of 2 and 18, for 
example, then Age Required would be "2" and Upper Age Limit would be "18." If 
there is no upper age limit, set this value to 99 (the highest allowed).</p>

<p>Enrollment Fee and Reserve Fee (if any) should be entered either as whole 
numbers or with six decimal places, with no currency notation (e.g. "1.250000" 
instead of "$1.25"). Overdue Notice Required lets you bypass generating overdue 
notices for this user type, and Issue Limit sets the highest number of items 
which this type of user may have borrowed.</p>
<!-- TMPL_INCLUDE name="help-bottom.inc" -->
--- NEW FILE ---
<!-- TMPL_INCLUDE name="help-top.inc" -->
<p>Once you have completed the process of setting up your MARC tag structure 
(MarcTagstruct) and checked your MARC to Koha mapping (Koha2MarcLinks), click 
on this link to activate a small program that checks for major errors in your 
MARC setup.</p>

<p>This MARC check does not guarantee that you will like the first results of 
your efforts to set up your MARC displays, etc. -- it simply checks for major 
errors. You will probably revise your MARC setup several times before you are 
completely pleased with it. Be sure to run checkmarc after every revision.</p>
<!-- TMPL_INCLUDE name="help-bottom.inc" -->

--- NEW FILE ---
<!-- TMPL_INCLUDE name="help-top.inc" -->
<h1>Gestion des devises</h1>
<p>Définir les catégories de lecteurs</p>

<p>You should at least define your local currency here, giving it a name (like 
US DOLLAR or EURO) and setting the "rate" at 1. If you do business with vendors 
who charge in a different currency, enter a name for that currency (e.g. PESO) 
and set the approximate exchange rate compared to your currency. (Note: names 
are limited to 10 characters or less.) The exchange rate is used to calculate 
the remain balances in your materials budgets when you purchase materials using 
"normal" acquisitions.</p>
<!-- TMPL_INCLUDE name="help-bottom.inc" -->
--- NEW FILE ---
<!-- TMPL_INCLUDE name="help-top.inc" -->
<h1>Règles d'emprunt</h1>
<p>Issuing rules deals with 2 topics :</p>
<ul>
        <li>Issuing length and quantity : they say how many items and how long 
a borrower category can issue for an itemtype </li>
        <li>Overdue charges : they are based on the item type and borrower 
type. These charges are defined on this page.</li>
</ul>
<p>Itemtypes and borrower categories must be defined before issuing rules are 
defined. Your defined items types and borrower categories are then displayed in 
a grid on this page.</p>

<h2>Issuing length and quantity</h2>
<p>Each box in the grid contains 2 numbers, separated by commas, defining how 
many days a given borrower type can issue how many material. For example : 21,5 
means the borrower can issue up to 5 books for up to 21 days</p>
<p>The <b>*</b> have a specific meaning. They mean "any". If you set 21,5 for 
itemtype=*, borrower category=student, branch=main, then a student can't issue 
more than 5 items of ANY item type. This "any" box is cumulative with other 
boxes. It means that 21,5 as itemtype=book, 14,2 as itemtype=CD and 30,6 as 
itemtype=* (with category=student) means a student can issue up to 5 books, up 
to 2 CD but a maximum of 6 items (books or CD). In this case the "30 days" in 
itemtype=* is discarded and the issuing length is calculated on the exact 
itemtype</p>

<h2>Amendes pour retard</h2>
<p>Each box in the grid contains three numbers separated by commas, defining 
the fine, how many days overdue the item must be before the fine is assessed 
and a first notice prepared (the "grace period"), and how many days after that 
the fine is assessed again and a second notice sent. For example, if you charge 
adults 1 dollar (or euro, or whatever currency) for overdue videos after three 
days and add another dollar charge after another five days, put "1,3,5" in the 
box in the grid that aligns with "Adult" and "Video." If you charge adults 25 
cents for overdue fiction books after a grace period of seven days and repeat 
the charge seven days later, then the entry in the corresponding box in the 
grid would be ".25,7,7". After the first and second notice are given, Koha 
prepares a "final notice" after the number of days set by the final number in 
the grid and sets the charge to the maximum, which is 5.</p>

<p>(Note : fines are calculated by the fines2.pl script, located in misc 
directory. Ask your system administrator to put this script in crontab, after 
midnight, to have fines calculated every night.)</p>

<!-- TMPL_INCLUDE name="help-bottom.inc" -->
--- NEW FILE ---
<!-- TMPL_INCLUDE name="help-top.inc" -->
<h1>Gestion des types de documents</h1>
<p>Vous pouvez définir autant de types de documents que vous souhaitez.</p>

<p>The item types are the "categories" into which your library items fall. For 
instance, you probably want to have videocassettes in a different category from 
non-fiction books, and mysteries in a different category from children's 
picture books. If you already are using a commercial ILS, you almost certainly 
already have all of your materials divided up into such categories. Now you 
need to tell Koha what your categories are.</p>

<p>The itemtype code is limited to four characters. This code is rarely 
displayed by Koha; instead the description of the type will be what users 
see.</p>

<p>"Rental charge" is any amount you might charge to users for borrowing items 
of a certain type (like videos).</p>

<p>"Renewals allowed" says how many times an items of this type may be 
renewed.</p>

<p>Item types are useful for many things, and <b>very</b> important in 
controlling how Koha works :</p>
<ul>
    <li>Les lecteurs peuvent chercher parmi les types de documents</li>
    <li>Issuing rules are set for item types (and for borrower types / 
branches)</li>
</ul>
<p>Setting up item types is one of the first things you should do after 
installing the Koha software.</p>
<!-- TMPL_INCLUDE name="help-bottom.inc" -->
--- NEW FILE ---
<!-- TMPL_INCLUDE name="help-top.inc" -->
<h1>Liens MARC %s</h1>
<p>This page provides a simplified way to map your MARC tags and subfields to 
the non-MARC Koha database tables <b>for default biblio framework</b>. This can 
also be done while setting the MARC tag structure, but it is easier to see the 
relationship between the MARC database and the Koha database here.</p>

<p>The pull-down menu lists all the Koha tables that can receive values from 
the MARC records. The columns from each table are listed below the pull-down 
menu.</p>

<p>Do not expect to have every Koha table.column mapped to a MARC subfield. 
Some (such as biblionumber, biblioitemnumber, and itemnumber) are values 
generated by Koha and will probably be automatically mapped. Others are flags 
which are set in the course of normal circulation activities and will contain 
information that is not part of your MARC record.</p>

<p>This is a one-to-one mapping. In other words, a MARC tag/subfield can be 
mapped to one, and only one, Koha table.column.</p>

<p>MARC data that is not mapped to a Koha table does not disappear -- it is 
simply not available for display on circulation screens and on some search 
results screens.</p>
<!-- TMPL_INCLUDE name="help-bottom.inc" -->

--- NEW FILE ---
<!-- TMPL_INCLUDE name="help-top.inc" -->
<h1>Gestion de la structure des champs MARC</h1>
<p>Koha allows you to specify which MARC tags you want to use and which you 
want to ignore. When you downloaded and installed Koha, you also got the entire 
list of MARC21 tags and subfields in current use. Now you need to use the 
administration page to edit this list and tell Koha which tags you want to use 
and how you want to use them.</p>
<p>You can define as the marc tag structure for each biblio framework you have 
defined</p>

<p>If you are CERTAIN that you will never use a MARC tag, then you can delete 
it, but since this will not result in any appreciable improvement in 
performance, it is probably better to leave it. There will be tags you want to 
add, however. If you are using older MARC tags that are not in the list of tags 
supplied with Koha, then use the MARC tag structure administration page to add 
them. Similarly, you will probably need to add the holdings tag you currently 
use, or at least check the subfield structure of the 852 tag if you use it for 
holdings.</p>

<p>Editing the SubFields from the MARC tag structure page is very 
time-consuming, but also very important; be sure to click the subfield link for 
each tag in your MARC tag structure.</p>
<p>For each subfield you can set :</p>
<ul>
<li>repeatable : wether it can be repeated or not. If it can be repeated, 
separate the values by a | in the MARC editor when you want to have the 
subfield twice</li>
<li>Mandatory : wether the field is mandatory or not. If mandatory, the 
cataloger can't validate the biblio if the subfield is empty.</li>
<li>Search also : a list of field that Koha will also search on when the user 
do a search on the subfield</li>
<li>Koha link : <b>very important</b>. Koha is multi-MARC compliant. So, it 
does not know what the 245$a means, neither what 200$f (those 2 fields being 
both the title in MARC21 and UNIMARC !). So, in this list you can "map" a MARC 
subfield to it's meaning. Koha constantly maintains consistency between a 
subfield and it's meaning. When the user want to search on "title", this link 
is used to find what is searched (245 if you're MARC21, 200 if you're 
UNIMARC).</li>
<li>Text for librarian : what appears before the subfield in the librarian 
interface</li>
<li>Text for OPAC : what appears before the field in the OPAC. If empty, the 
text for librarian is used instead</li>
<li>Managed in tab : deals with the tab where the subfield is shown. Ignore 
means that the subfield is not managed. All subfields of a given field must be 
in the same tab or ignored : 1st it's more logic, 2nd, Koha would be confused 
to repeat repeatable fields otherwise !!!</li>
<li>hidden : means that the field is managed, but NOT shown in opac. It's 
usually for internal fields</li>
<li> URL si coché, indique que le champ est une URL valide et peut-être 
cliquée</li>
<li>Auth value : means the value is not free, but in the authorised value list 
of the selected type</li>
<li>thesaurus : means that the value is not free, but can be searched in 
authority/thesaurus of the selected category</li>
<li>plugin : means the value is calculated or managed by a plugin. Plugins can 
do almost anything. For example, in UNIMARC there are plugins for every 1xx 
fields that are coded fields. The plugin is a huge help for cataloger ! There 
are also two plugins (unimarc_plugin_210c and unimarc_plugin_225a that can 
"magically" find the editor from an ISBN, and the collection list for the 
editor)</li>
<li>La boucle est pour l'instant</li>
</ul>
<!-- TMPL_INCLUDE name="help-bottom.inc" -->

--- NEW FILE ---
<!-- TMPL_INCLUDE name="help-top.inc" -->
<h1>Gestion de la structure des champs MARC</h1>
<p>Koha allows you to specify which MARC tags you want to use and which you 
want to ignore. When you downloaded and installed Koha, you also got the entire 
list of MARC21 tags and subfields in current use. Now you need to use the 
administration page to edit this list and tell Koha which tags you want to use 
and how you want to use them.</p>
<p>You can define as the marc tag structure for each biblio framework you have 
defined</p>

<p>If you are CERTAIN that you will never use a MARC tag, then you can delete 
it, but since this will not result in any appreciable improvement in 
performance, it is probably better to leave it. There will be tags you want to 
add, however. If you are using older MARC tags that are not in the list of tags 
supplied with Koha, then use the MARC tag structure administration page to add 
them. Similarly, you will probably need to add the holdings tag you currently 
use, or at least check the subfield structure of the 852 tag if you use it for 
holdings.</p>

<p>Editing the SubFields from the MARC tag structure page is very 
time-consuming, but also very important; be sure to click the subfield link for 
each tag in your MARC tag structure.</p>
<p>For each subfield you can set :</p>
<ul>
<li>repeatable : wether it can be repeated or not. If it can be repeated, 
separate the values by a | in the MARC editor when you want to have the 
subfield twice</li>
<li>Mandatory : wether the field is mandatory or not. If mandatory, the 
cataloger can't validate the biblio if the subfield is empty.</li>
<li>Search also : a list of field that Koha will also search on when the user 
do a search on the subfield</li>
<li>Koha link : <b>very important</b>. Koha is multi-MARC compliant. So, it 
does not know what the 245$a means, neither what 200$f (those 2 fields being 
both the title in MARC21 and UNIMARC !). So, in this list you can "map" a MARC 
subfield to it's meaning. Koha constantly maintains consistency between a 
subfield and it's meaning. When the user want to search on "title", this link 
is used to find what is searched (245 if you're MARC21, 200 if you're 
UNIMARC).</li>
<li>Text for librarian : what appears before the subfield in the librarian 
interface</li>
<li>Text for OPAC : what appears before the field in the OPAC. If empty, the 
text for librarian is used instead</li>
<li>Managed in tab : deals with the tab where the subfield is shown. Ignore 
means that the subfield is not managed. All subfields of a given field must be 
in the same tab or ignored : 1st it's more logic, 2nd, Koha would be confused 
to repeat repeatable fields otherwise !!!</li>
<li>hidden : means that the field is managed, but NOT shown in opac. It's 
usually for internal fields</li>
<li> URL si coché, indique que le champ est une URL valide et peut-être 
cliquée</li>
<li>Auth value : means the value is not free, but in the authorised value list 
of the selected type</li>
<li>thesaurus : means that the value is not free, but can be searched in 
authority/thesaurus of the selected category</li>
<li>plugin : means the value is calculated or managed by a plugin. Plugins can 
do almost anything. For example, in UNIMARC there are plugins for every 1xx 
fields that are coded fields. The plugin is a huge help for cataloger ! There 
are also two plugins (unimarc_plugin_210c and unimarc_plugin_225a that can 
"magically" find the editor from an ISBN, and the collection list for the 
editor)</li>
<li>La boucle est pour l'instant</li>
</ul>
<!-- TMPL_INCLUDE name="help-bottom.inc" -->

--- NEW FILE ---
<!-- TMPL_INCLUDE name="help-top.inc" -->
<p>If you are going to be using a printer (or several printers) that are 
attached to your Koha server for producing statistical and operations reports, 
then you need to give each printer a name and tell Koha how to access it. You 
do this by telling Koha which print queue to use.</p>

<p>(In linux, each printer configuration in your printcap file defines a print 
queue. The default print queue is "lp," but if you use more than one printer 
you will have other queues, probably with names like "text" or "postscript." 
Tell Koha which printer queue(s) you want to use for printing reports directly 
from the server.)</p>

<p>Note that you can always print Koha screens directly to a printer attached 
to your workstation just by using your web browser's Print function.</p>
<!-- TMPL_INCLUDE name="help-bottom.inc" -->

--- NEW FILE ---
<!-- TMPL_INCLUDE name="help-top.inc" -->
<h1>Gestion des mots vides</h1>
<p>Here you should list all of the words you wish Koha to ignore when 
performing catalog searches or building the keyword index.</p>

<p>Normally, you will not want Koha to save keyword references to articles like 
"The" and "A" and other very common words. Saving keyword references to these 
words does not help to limit a search and will make the keyword index very 
large and "cluttered" with words that are not really useful. The "stopwords" 
list defines these unnecessary words for your installation.</p>

<p>(Hint: If you are proficient at MySQL, it is often faster and easier to find 
an existing stopwords list, edit it, put it in the correct format, and use the 
MySQL "Load Data Infile" command to import the list into the stopwords table. 
Many academic libraries publish their stopwords list on the Internet, or you 
can ask other Koha libraries if they would share their stopword list.)</p>
<!-- TMPL_INCLUDE name="help-bottom.inc" -->

--- NEW FILE ---
<!-- TMPL_INCLUDE name="help-top.inc" -->
<h1>Gestion des préférences système</h1>
<p>This page allows you to set the system preferences that control much of the 
basic behavior of Koha. These parameters should be set before any other 
parameters.</p>
<ul>
<li><b>acquisitions --</b> 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.</li>

<li><b>authoritysep --</b> The separator used in authority/thesaurus. Usually " 
-- ". Deprecated & useless in Koha 2.2</li>

<li><b>autoBarcode --</b> The barcode number to be assigned to items is 
automatically assigned (sequentially) by Koha if this is set to "yes" ("1" = 
"yes").</li>

<li><b>autoMemberNum --</b> 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").</li>

<li><b>checkdigit --</b> Validity checks on membership number (patron card 
number): none or "Katipo" style checks. In most cases, you will choose "none" 
because you will be using pre-printed barcodes.</li>

<li><b>dateformat --</b> Choose "metric," "us," or "iso" date format (us = 
mm/dd/yyyy, metric = dd/mm/yyy, ISO = yyyy/mm/dd). This controls how dates are 
displayed, not how they are stored in the database.</li>

<li><b>gist --</b> "gist" is "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. Set to "0" if you are not required to pay tax.</li>

<li><b>insecure --</b> The best choice is "no." If you choose "yes," users do 
not have to login and all information is open to anyone. Be careful if you set 
this to "yes!"</li>

<li>
        <p><b>ISBD --</b> Koha can display records in International Standard 
Bibliographic Description format. the syntax of this field is quite complex : 
</p>
        <p>it's divided into blocks, that can contain a text before, X fields, 
each having -or not- a string before, a string after, and a text after :</p>
        <p><b>#995|&lt;br&gt;Items :|{\n995b}{ - 995j}{/995k}|</b></p>
        <p>means the "block" 995 has &lt;br&gt;Items : BEFORE, then fields 
995b, 995j and 995k, repeated for each item (995 is an UNIMARC standard), then 
nothing after the block.</p>
        <p> The # means "beginning of a block", the | is the separator of each 
part, the {} being used for each subfield. A subfield can have up to 3 digits 
BEFORE and up to 3 digits AFTER each subfield</p>
        <p>The UNIMARC (partial) definition for ISBD is </p><i>
        <p>#700|<label>traducteur</label>|{700a}{701a}{702a}| ;
                #200||{200a}{ [200b] }{. 200c}{ : 200e}{. 200h}{. 200i}{ / 
200f}{ ; 200g}|<br/>
                #230||{ ; 230a}|<br/>
                #205||{ ; 205a}{ , 205b}{ = 205d}{ / 205f}{ ; 205g}|<br/>
                #210|&lt;br/&gt;&lt;label&gt;Editeur&lt;/label&gt;|{ ; 210a}{ 
(210b) }{ : 210c}{, 210d}|<br/>
                #210|(|{210e}{(210f)}{ : 210g}{, 210h}|)<br/>
                #215|&lt;br/&gt;&lt;label&gt;&nbsp;&lt;/label&gt;|{ ; 215a}{ : 
215c}{ ; 215d}{ + 215e}|<br/>
                #225|&lt;br/&gt;&lt;label&gt;Description&lt;/label&gt;|{ 
(225a}{ = 225d}{ : 225e}{. 225h}{. 225i}{ / 225f}{, I225x}{ ; 225v}|)<br/>
                #606|&lt;br/&gt;&lt;label&gt;Sujets&lt;/label&gt;|{ 606a - 
}|&lt;br/&gt;&lt;br/&gt;<br/>
                #995|&lt;br&gt;Exemplaires :|{\n995b}{ - 995j}{/995k}|<br/>
        </i></p>
</li>

<li><b>KohaAdminEmailAddress --</b> The email address that will receive 
requests from borrowers for modification of their records.</li>

<li><b>ldapserver and ldapinfos --</b> Koha 2.0 can use Perl LDAP (Lightweight 
Directory Access Protocol, see 
http://search.cpan.org/~gbarr/perl-ldap-0.3202/lib/Net/LDAP.pod) to manage user 
access and privileges. To avoid a useless Perl package for libraries without 
ldap, all what is related to LDAP has been moved to 
KohaInstall/modules/C4/Auth_with_ldap.pm. Ask your system administrator to set 
up LDAP with Auth_with_ldap.pm (perldoc Auth_with_ldap.pm for help). Those 2 
parameters are useless in 2.2 and have should not appear on a new install.</li>

<li><b>Bibliothèque</b> The library name or message that will be shown on the 
main OPAC page. You may use HTML tags to format the name. Example: Welcome to 
<i>Koha<br/>Free Software ILS</i></li>

<li><b>marc --</b> Turn on MARC support. Set to "no" if you do not intend to 
use MARC records.</li>

<li><b>marcflavour --</b> Your MARC flavor (MARC21 or UNIMARC). This choice 
tells Koha how to interpret your MARC records.</li>

<li><b>maxoutstanding --</b> The maximum amount of outstanding charges a 
borrower may have before he/she is barred from making reserve requests. The 
number represents units of your local currency (e.g. "5" means $5.00, if the 
dollar is your local currency.)</li>

<li><b>maxreserves --</b> The maximum number of reserves a member can make.</li>

<li><b>noissuescharge --</b> The maximum amount of outstanding charges a 
borrower may have before he/she is barred from checking out items. The number 
represents units of your local currency (e.g. "5" means $5.00, if the dollar is 
your local currency.)</li>

<li><b>opaclanguages --</b> Set your language preference. (Despite the name, 
this choice controls the language used for all Koha screens, not just the 
OPAC). The top language in your list will be tried first.</li>

<li><b>opacthemes --</b> Set the preferred order for themes. The top theme will 
be tried first.</li>

<li><b>printcirculationslips --</b> if set to 1, circulation "slips" are 
printed on your receipt printer. If set to 0, no slips are printed.</li>

<li><b>suggestion --</b> 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.</li>

<li><b>template --</b> Preference order for screen templates. Koha comes with 
several different options for templates that control the look and feel of your 
Koha screens, and you can also write your own templates.</li>

<li><b>timeout --</b> Inactivity timeout period (in seconds). If a workstation 
is idle for longer than this period, the user will have to login again.</li>

<li><b>virtualshelves --</b> Set virtual shelves management on or off ("1" or 
"0"). Users can set up and manage their own "virtual bookshelves" of favorite 
library items if this feature is turned on.</li>
<!-- TMPL_INCLUDE name="help-bottom.inc" -->

--- NEW FILE ---
<!-- TMPL_INCLUDE name="help-top.inc" -->
<h1>Gestion des serveurs Z39.50</h1>
<p>Defines the Z39.50 servers you want Koha to search.</p>

<p>Koha comes with one Z39.50 server site defined (the U.S. Library of 
Congress) for finding catalog records to import directly into your catalog. In 
this area, you can define other servers for searching.</p>

<p>To add servers, you will need to know the domain name or IP address of the 
server, the port number to use, and the name of the database to access. This 
information is available for many servers worldwide by acessing the Index Data 
website at http://www.indexdata.dk/targettest/. All of the servers listed there 
accept anonymous connections. (Be sure to choose servers which deliver records 
in the proper MARC format for your Koha installation.)</p>

<p>If you have a login name and password for other Z39.50 servers, Koha will 
save your user ID and password in addition to the other information it needs to 
make a connection. (For anonymous servers, leave the userid and password fields 
blank.) The other fields on the form control whether or not the server is 
automatically searched when you request a Z39.50 search (put a "1" in the 
"Checked" field) and the order in which it is checked.</p>

<p>It is a good idea to be selective in choosing servers. Defining more than 
five or six checked servers may slow down your Z39.50 search results, even if 
they are queried all together.</p>

<p>IMPORTANT NOTE : the z3950search will NOT work until your system 
administrator has not activated the z3950 client daemon on your server. The 
daemon is in KohaDirectory/script/z3950daemon. It should be added to rc.d to be 
launched during server boot.</p>

<!-- TMPL_INCLUDE name="help-bottom.inc" -->