* eventName | event that will trigger the calendar, without the "on" prefix (default: "click")
* ifFormat | date format that will be stored in the input field
* daFormat | the date format that will be used to display the date in displayArea
- * singleClick | (true/false) wether the calendar is in single click mode or not (default: true)
+ * singleClick | (true/false) whether the calendar is in single click mode or not (default: true)
* firstDay | numeric: 0 to 6. "0" means display Sunday first, "1" means display Monday first, etc.
* align | alignment (default: "Br"); if you don't know what's this see the calendar documentation
* range | array with 2 elements. Default: [1900, 2999] -- the range of years available
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<head>
<title>KOHA:_Labs Thesis Selection plugin</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<script language="JavaScript" type="text/javascript">
<!-- Hide from old browsers
<!-- TMPL_IF name="barcodereserv" --><!-- TMPL_VAR NAME="barcodereserv" -->
<!-- /TMPL_IF -->
<!-- TMPL_IF NAME="waitingposition" -->
- Hold priority :
+ Hold priority
<b> <!-- TMPL_VAR NAME="waitingposition" --> </b>
<!-- /TMPL_IF -->
</td>
<!-- /TMPL_IF -->
<!-- TMPL_IF name="transfered" -->
<br />
- <i>This hold has been transfered from library :
- <!-- TMPL_VAR NAME="frombranch" --> the : <!-- TMPL_VAR NAME="datesent" --> </i>
+ <i>This hold has been transfered from library
+ <!-- TMPL_VAR NAME="frombranch" --> on <!-- TMPL_VAR NAME="datesent" --> </i>
<!-- /TMPL_IF -->
<!-- TMPL_IF name="nottransfered" -->
<br />
- <i>This hold hasn't been transfered yet from library : <!-- TMPL_VAR NAME="nottransferedby" --></i>
+ <i>This hold hasn't been transfered yet from library <!-- TMPL_VAR NAME="nottransferedby" --></i>
<!-- /TMPL_IF -->
</td>
<td><!-- TMPL_VAR NAME="author" --></td>
<form method="post" action="/cgi-bin/koha/circ/overdue.pl">
<div id="filters">Filter on :<br />
Name or cardnumber :<input type="text" name="borname" value="<!--TMPL_VAR Name="borname"-->">
- Borrower categorycode :<select name="borcat" id="borcat"><option value="">Any</option>
+ Patron category :<select name="borcat" id="borcat"><option value="">Any</option>
<!-- TMPL_LOOP name="borcatloop" -->
<option value="<!-- TMPL_VAR name="value" -->" <!-- TMPL_IF name="selected" -->selected<!-- /TMPL_IF -->><!-- TMPL_VAR name="catname" --></option>
<!-- /TMPL_LOOP -->
</select>
- Borrower Flags :<!--TMPL_VAR Name="CGIflags" --><br/>
- Itemtype :<select name="itemtype" id="itemtype"><option value="">Any</option>
+ Patron flags :<!--TMPL_VAR Name="CGIflags" --><br/>
+ Item type :<select name="itemtype" id="itemtype"><option value="">Any</option>
<!-- TMPL_LOOP name="itemtypeloop" -->
<option value="<!-- TMPL_VAR name="value" -->" <!-- TMPL_IF name="selected" -->selected<!-- /TMPL_IF -->><!-- TMPL_VAR name="itemtypename" --></option>
<!-- /TMPL_LOOP -->
</select>
- branch :<select name="branch" id="branch">
+ Library :<select name="branch" id="branch">
<option value="">Any</option>
<!-- TMPL_LOOP name="branchloop" -->
<option value="<!-- TMPL_VAR name="value" -->" <!-- TMPL_IF name="selected" -->selected<!-- /TMPL_IF -->><!-- TMPL_VAR name="branchname" --></option>
Sort By<select name="order" tabindex="0" size="1" id="order">
<option <!--TMPL_UNLESS Name"order"-->selected<!-- /TMPL_UNLESS--> value="">Due Date</option>
-<option value="borrower">Borrower</option>
+<option value="borrower">Patron</option>
<option value="title">Title</option>
<option value="barcode">Barcode</option>
<option value="date_due desc">Due Date desc</option>
-<option value="borrower desc">Borrower desc</option>
+<option value="borrower desc">Patron desc</option>
<option value="title desc">Title desc</option>
<option value="barcode desc">Barcode</option>
</select>
<!-- TMPL_INCLUDE NAME="circ-menu.inc" -->
</div>
</div>
-<!-- TMPL_INCLUDE NAME="intranet-bottom.inc" -->
\ No newline at end of file
+<!-- TMPL_INCLUDE NAME="intranet-bottom.inc" -->
<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>repeatable : whether 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 : whether 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>
<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>things outside [] are kept as is (including HTML)</li>
- <li>repeatable fields are manages.</li>
+ <li>repeatable fields are managed.</li>
<ul>
</ul>
<p>IMPORTANT</p>
<!-- TMPL_INCLUDE NAME="doc-head-open.inc" -->
-<title>Online Help › System Preferences › Itemtypes Management</title>
+<title>Online Help › System Preferences › Item types Management</title>
<!-- TMPL_INCLUDE NAME="doc-head-close.inc" -->
</head>
<body>
<h1>Item types management</h1>
-<p>You can define as many itemtypes as you want.</p>
+<p>You can define as many item types as you want.</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>Item types are useful for many things, and <b>very</b> important in controlling how Koha works :</p>
<ul>
- <li>Borrowers can search on itemtypes</li>
- <li>Issuing rules are set for item types (and for borrower types / branches)</li>
+ <li>Patrons can search on item types</li>
+ <li>Issuing rules are set for item types (and for patron types / libraries)</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="intranet-bottom.inc" -->
<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>repeatable : whether 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 : whether 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>
<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>repeatable : whether 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 : whether 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>
<!-- TMPL_INCLUDE NAME="doc-head-open.inc" -->
-<title>Online Help › Borrowers</title>
+<title>Online Help › Patrons</title>
<!-- TMPL_INCLUDE NAME="doc-head-close.inc" -->
</head>
<body>
-<h1>Borrowers help</h1>
-<p>This is the Borrowers module of Koha.</p>
-<p>The Members portion stores the information you add about your patrons.</p>
+<h1>Patrons help</h1>
+<p>This is the Patrons module of Koha.</p>
+<p>The Patrons portion stores the information you add about your patrons.</p>
<p>To add a patron, type their name into the search box on the left, and
click the OK button.</p>
<p>If there is already a borrower matching the name you searched, it will show
<h3>Step 2 of 6: Pick a Report Type</h3>
<p>There are 3 types of reports that can be generated:</p>
<ul>
- <li><strong>Tabular :</strong>Simple report of columns only.</li>
- <li><strong>Matrix :</strong><em>Not finished</em></li>
- <li><strong>Summary :</strong><em>Not finished</em></li>
+ <li><strong>Tabular:</strong>Simple report of columns only.</li>
+ <li><strong>Matrix:</strong><em>Not finished</em></li>
+ <li><strong>Summary:</strong><em>Not finished</em></li>
</ul>
<h3>Step 3 of 6: Select Columns for Display</h3>
-<!-- TMPL_INCLUDE name="intranet-bottom.inc" -->
\ No newline at end of file
+<!-- TMPL_INCLUDE name="intranet-bottom.inc" -->
<!-- TMPL_IF Name="nok" -->
<div id="problem">
- <p>The following fields are wrong. Please fix it/them</p>
+ <p>The following fields are wrong. Please fix them</p>
<!-- TMPL_IF NAME="ERROR_login_exist" -->
<div id="ERROR_login_exist">login/password already exist</div>
<!-- /TMPL_IF -->
<fieldset class="rows" id="memberentry_contact">
<legend>Contact</legend><ol>
<!--TMPL_IF Name="C"-->
- <h2>Borrower</h2>
+ <h2>Patron</h2>
<li>
<!-- TMPL_IF NAME="mandatoryB_email" -->
<label for="B_email" class="required">
<td><input type="hidden" name="Filter" value="" /><input type="hidden" name="Filter" value="" /></td>
</tr>
<tr class="hilighted">
- <td>Borrower Category</td>
+ <td>Patron category</td>
<td><input type="radio" name="Line" value="borrowers.categorycode" /></td>
<td><input type="radio" name="Column" value="borrowers.categorycode" /></td>
<td><!-- TMPL_VAR NAME="CGIBorCat" --></td>
</tr>
<tr>
- <td>Document Type</td>
+ <td>Item type</td>
<td><input type="radio" name="Line" value="itemtype" /></td>
<td><input type="radio" name="Column" value="itemtype" /></td>
<td ><!-- TMPL_VAR NAME="CGIItemType" --></td>
</tr>
<tr class="hilighted">
- <td>Branch</td>
+ <td>Library</td>
<td><input type="radio" name="Line" value="branchcode" /></td>
<td><input type="radio" name="Column" value="branchcode" /></td>
<td><!-- TMPL_VAR NAME="CGIBranch" --></td>
<!-- TMPL_INCLUDE NAME="reports-menu.inc" -->
</div>
</div>
-<!-- TMPL_INCLUDE NAME="intranet-bottom.inc" -->
\ No newline at end of file
+<!-- TMPL_INCLUDE NAME="intranet-bottom.inc" -->
<ul>
<!--TMPL_LOOP Name="subscriptions"-->
- <li><a href="serials-collection.pl?subscriptionid=<!-- TMPL_VAR name="subscriptionid" -->" title="serial Collection for <!--TMPL_VAR Name="bibliotitle"-->">Serial collection</a></li>
+ <li><a href="serials-collection.pl?subscriptionid=<!-- TMPL_VAR name="subscriptionid" -->" title="serial collection for <!--TMPL_VAR Name="bibliotitle"-->">Serial collection</a></li>
<li><a href="subscription-detail.pl?subscriptionid=<!-- TMPL_VAR name="subscriptionid" -->" title="detail of the subscription">Subscription #<!-- TMPL_VAR name="subscriptionid" --></a></li>
<!--TMPL_IF name="abouttoexpire"--><a href="#" onclick="javascript:popup(<!--TMPL_VAR Name="subscriptionid"-->)">Renew <!--TMPL_VAR Name="subscriptionid"--></a>
<!--/TMPL_IF-->
<!-- /TMPL_IF -->
</div>
-<h2>waited or late numbers</h2>
+<h2>Awaited or late</h2>
<form method="post" name="f" action="serials-recieve.pl" onsubmit="return barcode_check()">
<input type="hidden" name="op" value="serialchangestatus" />
<input type="hidden" name="serial" value="<!-- TMPL_VAR name="serial" -->" />
projects / srvgit / commitdiff