[Koha-cvs] koha/koha-tmpl/intranet-tmpl/katipo/en/help adm... [dev_week]
Robert Lyon
bob at katipo.co.nz
Wed Jul 26 00:16:36 CEST 2006
CVSROOT: /sources/koha
Module name: koha
Branch: dev_week
Changes by: Robert Lyon <bob_lyon> 06/07/25 22:16:36
Added files:
koha-tmpl/intranet-tmpl/katipo/en/help: admin-home.tmpl
boraccount.tmpl
bull-home.tmpl
detail.tmpl
mainpage.tmpl
mancredit.tmpl
maninvoice.tmpl
modbib.tmpl
modbibitem.tmpl
moditem.tmpl
moredetail.tmpl
nohelp.tmpl pay.tmpl
readingrec.tmpl
reports-home.tmpl
request.tmpl
koha-tmpl/intranet-tmpl/katipo/en/help/admin: aqbookfund.tmpl
aqbudget.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
koha-tmpl/intranet-tmpl/katipo/en/help/authorities:
authorities.tmpl
koha-tmpl/intranet-tmpl/katipo/en/help/bull: bull-home.tmpl
claims.tmpl
lateissues.tmpl
routing.tmpl
statecollection.tmpl
subscription-add.tmpl
subscription-detail.tmpl
koha-tmpl/intranet-tmpl/katipo/en/help/circ:
branchtransfers.tmpl
circulation.tmpl
returns.tmpl
koha-tmpl/intranet-tmpl/katipo/en/help/members:
jmemberentry.tmpl
member-flags.tmpl
member.tmpl
memberentry.tmpl
members-home.tmpl
moremember.tmpl
koha-tmpl/intranet-tmpl/katipo/en/help/reports:
acquisitions_stats.tmpl
bor_issues_top.tmpl
borrowers_out.tmpl
borrowers_stats.tmpl
cat_issues_top.tmpl
catalogue_stats.tmpl
inventory.tmpl
issues_stats.tmpl
reservereport.tmpl
koha-tmpl/intranet-tmpl/katipo/en/help/search.marc: search.tmpl
Log message:
Adding in the help files for the katipo template set
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/admin-home.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/boraccount.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/bull-home.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/detail.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/mainpage.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/mancredit.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/maninvoice.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/modbib.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/modbibitem.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/moditem.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/moredetail.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/nohelp.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/pay.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/readingrec.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/reports-home.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/request.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/admin/aqbookfund.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/admin/aqbudget.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/admin/authorised_values.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/admin/authtypes.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/admin/biblio_framework.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/admin/branches.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/admin/categorie.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/admin/checkmarc.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/admin/currency.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/admin/issuingrules.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/admin/itemtypes.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/admin/koha2marclinks.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/admin/marc_subfields_structure.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/admin/marctagstructure.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/admin/printers.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/admin/stopwords.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/admin/systempreferences.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/admin/z3950servers.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/authorities/authorities.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/bull/bull-home.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/bull/claims.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/bull/lateissues.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/bull/routing.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/bull/statecollection.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/bull/subscription-add.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/bull/subscription-detail.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/circ/branchtransfers.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/circ/circulation.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/circ/returns.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/members/jmemberentry.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/members/member-flags.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/members/member.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/members/memberentry.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/members/members-home.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/members/moremember.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/reports/acquisitions_stats.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/reports/bor_issues_top.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/reports/borrowers_out.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/reports/borrowers_stats.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/reports/cat_issues_top.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/reports/catalogue_stats.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/reports/inventory.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/reports/issues_stats.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/reports/reservereport.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/katipo/en/help/search.marc/search.tmpl?cvsroot=koha&only_with_tag=dev_week&rev=1.1.2.1
Patches:
Index: admin-home.tmpl
===================================================================
RCS file: admin-home.tmpl
diff -N admin-home.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ admin-home.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,7 @@
+<!-- TMPL_INCLUDE name="help-top.inc" -->
+<h1>Administration</h1>
+<p>From the administration section you can change the parameters which determine how Koha functions for your library</p>
+
+
+<br />
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: boraccount.tmpl
===================================================================
RCS file: boraccount.tmpl
diff -N boraccount.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ boraccount.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,8 @@
+<!-- TMPL_INCLUDE NAME="help-top.inc" -->
+
+<h1>Account Summary</h1>
+
+<p>From this screen you can view a borrower's accound details and create a Manual Invoice or create a Manual Credit for items which aren't shown on the Account Summary.</p>
+
+<br />
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: bull-home.tmpl
===================================================================
RCS file: bull-home.tmpl
diff -N bull-home.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ bull-home.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,23 @@
+<!-- TMPL_INCLUDE NAME="help-top.inc" -->
+<h1>Serials subscription help</h1>
+<p>The Serials subscriptions module allows you to manage subscription arrivals,
+scheduling and claims.</p>
+<p><b>Note:</b> Before a serial can be set up it must be entered into Koha through the Acquisitions process.</p>
+<ul><li>Type in the serial title (should not find anything if it is a new item). Users are meant to search before adding a new subscription just in case it is already set up. Search on either an ISSN or a title.
+ <li>If you enter a title, you can use the wildcard <b>%</b>.<br />
+Entering <b>%Times%</b> returns every subscription containing Times in the title.<br />
+Entering <b>New York%</b> returns every subscription with title starting with New York</li>
+ <li>If you want to create a new subscription, click on <a href="#" onclick="javascript:opener.location.href='/cgi-bin/koha/bull/subscription-add.pl'" class="button">Add subscription</a>
+ <li>Once you have found the subscription you need, you can: </li>
+ <ul><li>View subscription details</li>
+ <li>Recieve any item and/or manage what appears in subscription summary (in OPAC & Librarian interface)</li>
+ </ul>
+</ul>
+
+
+<h1>Serials routing list help</h1>
+<ul><li>Step 1: Go to <a href="#" onclick="javascript:opener.location.href='/cgi-bin/koha/bull-home.pl?routing=1'; return false">Create/Edit Routing List</a>
+ <li>Step 2: Type in the title of the serial that will be circulated
+ <li>Step 3: Pick the correct title and click the Routing List link
+</ul>
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: detail.tmpl
===================================================================
RCS file: detail.tmpl
diff -N detail.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ detail.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,16 @@
+<!-- TMPL_INCLUDE NAME="help-top.inc" -->
+
+<h1>Search Details</h1>
+<p>From this screen you can view and edit the biblio record, and view details about the items in the biblo.</p>
+<p>Koha has records in three parts: Biblio, Group and Item:</p>
+<ul>
+ <li>Biblio Record - This is the intellectual record for the work.</li>
+ <li>Group Record - This are the formats of the work; the item types. e.g., Adult Non Fiction, DVD</li>
+ <li>Item - The indivdual items in each group</li>
+</ul>
+<p>To view or edit the rest of the record for an item, click on the "barcode" link. You will see the group and item information together.</p>
+<p>Editing the biblio will update the record for all the items.<br />
+Make a new biblio or add items in acquisitions.<br />
+To move items to a new biblio you will need to re-aquire them and delete them from this biblio.</p>
+<br />
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: mainpage.tmpl
===================================================================
RCS file: mainpage.tmpl
diff -N mainpage.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ mainpage.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,6 @@
+<!-- TMPL_INCLUDE NAME="help-top.inc" -->
+
+<h1>Welcome to Koha</h1>
+<br />
+
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: mancredit.tmpl
===================================================================
RCS file: mancredit.tmpl
diff -N mancredit.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ mancredit.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,36 @@
+<!-- TMPL_INCLUDE NAME="help-top.inc" -->
+
+<h1>Create Credit</h1>
+<p>
+ From this screen you can create a Manual Credit for an item which isn't shown on the Account Summary.
+</p>
+<p>
+ This will be added to the account summary.
+</p>
+<ul>
+ <li>
+ <b>Type</b> - The category which will be invoiced
+ <ul>
+ <li>
+ Credit
+ </li>
+ <li>
+ Baycorp Adjustment - for debts placed with a debt recovery agency
+ </li>
+ <li>
+ Worked off
+ </li>
+ </ul></li>
+ <li>
+ <b>Item number</b> - The item which is being credited
+ </li>
+ <li>
+ <b>Description</b> - A brief description
+ </li>
+ <li>
+ <b>Amount</b> - The amount to be invoiced
+ </li>
+</ul>
+
+<br />
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: maninvoice.tmpl
===================================================================
RCS file: maninvoice.tmpl
diff -N maninvoice.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ maninvoice.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,45 @@
+<!-- TMPL_INCLUDE NAME="help-top.inc" -->
+
+<h1>Create Manual Invoice</h1>
+<p>
+ From this screen you can create a Manual Invoice for an item which isn't shown on the Account Summary.
+</p>
+<p>
+ This will be added to the account summary.
+</p>
+<ul>
+ <li>
+ <b>Type</b> - The category which will be invoiced
+ <ul>
+ <li>
+ Lost Item
+ </li>
+ <li>
+ Fine
+ </li>
+ <li>
+ Account Management Fee
+ </li>
+ <li>
+ New Card
+ </li>
+ <li>
+ Sundry
+ </li>
+ <li>
+ Cash Refund
+ </li>
+ </ul></li>
+ <li>
+ <b>Itemnumber</b> - The item which is being invoiced
+ </li>
+ <li>
+ <b>Description</b> - A brief description
+ </li>
+ <li>
+ <b>Amount</b> - The amount to be invoiced
+ </li>
+</ul>
+
+<br />
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: modbib.tmpl
===================================================================
RCS file: modbib.tmpl
diff -N modbib.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ modbib.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,28 @@
+<!-- TMPL_INCLUDE NAME="help-top.inc" -->
+
+<h1>Edit Biblio</h1>
+<p>From this screen you can view and edit the biblio record.</p>
+<ul>
+ <li>Author</li>
+ <li>Title</li>
+ <li>Abstract</li>
+ <li>Subject - Enter each subject on a new line.
+ <ul>
+ <li>If the subject does not exist in the subject authority file a warning page will appear when you save your changes.
+ <li>Highlight and copy the correct subject, hit the back arrow and paste it into the subject field.</li>
+ </ul></li>
+ <li>Copyright Date</li>
+ <li>Series Title</li>
+ <li>Additional Author</li>
+ <li>Subtitle</li>
+ <li>Unititle</li>
+ <li>Notes - any notes you wish patrons and librarians to see when they search.</li>
+ <li>Serial
+ <ul>
+ <li>1 to mark it as a serial</li>
+ <li>0 to mark it as not a serial</li>
+ </ul>
+ </li>
+</ul>
+<br />
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: modbibitem.tmpl
===================================================================
RCS file: modbibitem.tmpl
diff -N modbibitem.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ modbibitem.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,8 @@
+<!-- TMPL_INCLUDE NAME="help-top.inc" -->
+
+<h1>Modify Group</h1>
+<p>From this screen you can view and edit the group record.</p>
+<p> You must click on the appropriate radio button, and choose to either re-assign the item/s to a record already in the system (RE-ASSIGN TO EXISTING GROUP), or modify this record (MODIFY DETAILS).</p>
+<p>If your changes only apply to some items, tick the appropriate ones and a new group record will be created automatically for them. Those left un-ticked will keep the original Group Record.</p>
+<br />
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: moditem.tmpl
===================================================================
RCS file: moditem.tmpl
diff -N moditem.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ moditem.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,8 @@
+<!-- TMPL_INCLUDE NAME="help-top.inc" -->
+
+<h1>Modify Item</h1>
+<p>From this screen you can view and edit the item record.</p>
+<p><b>Home Branch</b> - enter the code for the branch</p>
+
+<br />
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: moredetail.tmpl
===================================================================
RCS file: moredetail.tmpl
diff -N moredetail.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ moredetail.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,7 @@
+<!-- TMPL_INCLUDE NAME="help-top.inc" -->
+
+<h1>Group and Item Details</h1>
+<p>From this screen you can view and edit the group record and details for each item in the group.</p>
+<p>The group record appears first on the page followed by the item details for each item in the group.</p>
+
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: nohelp.tmpl
===================================================================
RCS file: nohelp.tmpl
diff -N nohelp.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ nohelp.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,4 @@
+<!-- TMPL_INCLUDE NAME="help-top.inc" -->
+ <h1>Online Help</h1>
+ <p>Sorry, no help on this topic</p>
+<!-- TMPL_INCLUDE NAME="help-bottom.inc" -->
\ No newline at end of file
Index: pay.tmpl
===================================================================
RCS file: pay.tmpl
diff -N pay.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ pay.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,13 @@
+<!-- TMPL_INCLUDE NAME="help-top.inc" -->
+
+<h1>Pay Fines</h1>
+<p>
+ From this screen you can administer fines payments for borrowers.
+</p>
+<p>
+ For each fine you can choose to leave it unpaid, paid or written off.
+</p>
+
+
+<br />
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: readingrec.tmpl
===================================================================
RCS file: readingrec.tmpl
diff -N readingrec.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ readingrec.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,16 @@
+<!-- TMPL_INCLUDE name="help-top.inc" -->
+<h1>Reading Record</h1>
+
+<p>
+ This page shows the patron's reading record.
+</p>
+<p>
+ To view the full reading record, click on the "Full Output" button.
+</p>
+<p>
+ The record may be sorted by Title, Author, Date Due and Date Returned. Click on the column headings to do this.
+</p>
+
+
+<br />
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: reports-home.tmpl
===================================================================
RCS file: reports-home.tmpl
diff -N reports-home.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ reports-home.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,14 @@
+<!-- TMPL_INCLUDE name="help-top.inc" -->
+<h1>Reports</h1>
+<p>
+ From this screen you can generate statistics.
+</p>
+<p>
+ Most statistics are generated from 'wizard' interface to enable you to tailor reports to your needs.
+</p>
+<p>
+ You can choose to view the reports on screen or export them to a spreadsheet readable format.
+</p>
+
+<br />
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: request.tmpl
===================================================================
RCS file: request.tmpl
diff -N request.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ request.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,13 @@
+<!-- TMPL_INCLUDE name="help-top.inc" -->
+<h1>Requests</h1>
+<p>This page allows you to manage items which have been requested by borrowers.</p>
+<p>
+ You can rank new and existing requests as well as deleting those which are no longer valid.
+</p>
+<p>
+ Enter the Member Number for a borrower to request the item for them.
+</p>
+
+
+<br />
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: admin/aqbookfund.tmpl
===================================================================
RCS file: admin/aqbookfund.tmpl
diff -N admin/aqbookfund.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ admin/aqbookfund.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,29 @@
+<!-- TMPL_INCLUDE name="help-top.inc" -->
+
+<h1>Book Fund Administration</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><b>Note:</b> 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>
+
+<h4>Book fund codes</h4>
+<ul>
+ <li>Each Book Fund will have a unique fund code to identify it.</li>
+ <li>The code can have no more than five characters.</li>
+ <li>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" field, then a full name in the "Name" field.</li>
+</ul>
+
+<h4>Setting up the bookfund budget</h4>
+<ul>
+ <li>Once you have set up a fund, you will see a link to a page for setting up the fund budget.</li>
+ <li>Enter the beginning and end dates of your budget year and the amount of money in that particular budget line.</li>
+ <li>Do not use any kind of currency notation (like "$") or commas when entering the number. (Commas will be converted to decimal points.)</li>
+</ul>
+
+<p><b>Note:</b><br />
+The dates will not saved correctly unless you have set your date format in the System Preferences section of the Parameters page - <b>Do this before setting budgets.</b></p>
+
+<br />
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: admin/aqbudget.tmpl
===================================================================
RCS file: admin/aqbudget.tmpl
diff -N admin/aqbudget.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ admin/aqbudget.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,29 @@
+<!-- TMPL_INCLUDE name="help-top.inc" -->
+
+<h1>Book Fund Administration</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><b>Note:</b> 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>
+
+<h4>Book fund codes</h4>
+<ul>
+ <li>Each Book Fund will have a unique fund code to identify it.</li>
+ <li>The code can have no more than five characters.</li>
+ <li>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" field, then a full name in the "Name" field.</li>
+</ul>
+
+<h4>Setting up the bookfund budget</h4>
+<ul>
+ <li>Once you have set up a fund, you will see a link to a page for setting up the fund budget.</li>
+ <li>Enter the beginning and end dates of your budget year and the amount of money in that particular budget line.</li>
+ <li>Do not use any kind of currency notation (like "$") or commas when entering the number. (Commas will be converted to decimal points.)</li>
+</ul>
+
+<p><b>Note:</b><br />
+The dates will not saved correctly unless you have set your date format in the System Preferences section of the Parameters page - <b>Do this before setting budgets.</b></p>
+
+<br />
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: admin/authorised_values.tmpl
===================================================================
RCS file: admin/authorised_values.tmpl
diff -N admin/authorised_values.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ admin/authorised_values.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,18 @@
+<!-- TMPL_INCLUDE name="help-top.inc" -->
+<h1>Authorised values management</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>
+
+<h4>Tip:</h4>
+<ul><li>If a subfield is non mandatory, Koha automatically adds an empty value to the authorised value list, that is selected by default.
+ <li>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 !)
+</ul>
+
+<h4>Tip:</h4>
+<ul><li>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.
+ <li>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
+</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" -->
Index: admin/authtypes.tmpl
===================================================================
RCS file: admin/authtypes.tmpl
diff -N admin/authtypes.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ admin/authtypes.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,15 @@
+<!-- TMPL_INCLUDE NAME="help-top.inc" -->
+<h1>Authority types</h1>
+<p>You can define as many Authority types as you want.</p>
+<ul><li>Use the MARC structure button to define the MARC structure of a given authority type
+ <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 chosen in the biblio MARC editor.
+ <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>things outside [ ] are kept as is (including HTML)
+ <li>repeatable fields are managed.
+ </ul>
+</ul>
+
+<h4>Note</h4>
+<p>In the biblio framework, the reported tag MUST 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" -->
\ No newline at end of file
Index: admin/biblio_framework.tmpl
===================================================================
RCS file: admin/biblio_framework.tmpl
diff -N admin/biblio_framework.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ admin/biblio_framework.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,8 @@
+<!-- TMPL_INCLUDE NAME="help-top.inc" -->
+<h1>Biblio framework</h1>
+<p>You can have more than one framework to enable you to catalogate materials differently.</p>
+<p>
+You can, for example, define 1 framework for monographs, 1 framework for serials, 1 framework for URLs, etc.</p>
+<p>
+Once a framework type is created, you can click on "MARC structure" to define the exact MARC structure. The first time you do this, Koha will ask you to select an existing framework to copy into the new one, saving you from having to define all the MARC structure.</p>
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: admin/branches.tmpl
===================================================================
RCS file: admin/branches.tmpl
diff -N admin/branches.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ admin/branches.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,25 @@
+<!-- TMPL_INCLUDE NAME="help-top.inc" -->
+
+<h1>Library Branches</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>
+
+<h3>Categories</h3>
+<ul>
+ <li>
+ Issuing - Branches which can issue items from the main library catalogue in Koha.
+ </li>
+ <li>
+ Real Branch - Actual library branch. Setting this category will determine if the Branch opening hours appear on the OPAC homepage.
+ </li>
+ <li>
+ No categories set - If you don't set any categories, the branch details will not appear on the OPAC homepage and the Branch can't issue items . This is useful for "virtual" branches for transfers
+ </li>
+</ul>
+
+<br />
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: admin/categorie.tmpl
===================================================================
RCS file: admin/categorie.tmpl
diff -N admin/categorie.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ admin/categorie.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,25 @@
+<!-- TMPL_INCLUDE name="help-top.inc" -->
+<h1>Borrower Categories</h1>
+
+<p>Here is where you define the types of users of your library and how they will be handled.</p>
+
+<h2 class="help">Category Code and Description</h2>
+<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) is a borrower category that has a "guarantor"</li>
+</ul>
+
+<h2 class="help">Enrollment Period</h2>
+<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>
+
+<h2 class="help">Upper Age Limit and Age Required</h2>
+<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>
+
+<h2 class="help">Enrollment Fee and Reserve Fee</h2>
+<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").</p>
+
+<h2 class="help">Overdue Notice Required</h2>
+<p>Overdue Notice Required lets you bypass generating overdue notices for this user type.</p>
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: admin/checkmarc.tmpl
===================================================================
RCS file: admin/checkmarc.tmpl
diff -N admin/checkmarc.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ admin/checkmarc.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,5 @@
+<!-- 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" -->
Index: admin/currency.tmpl
===================================================================
RCS file: admin/currency.tmpl
diff -N admin/currency.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ admin/currency.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,12 @@
+<!-- TMPL_INCLUDE name="help-top.inc" -->
+<h1>Currencies administration</h1>
+<h4>Local currency</h4>
+<p>Give the local currency a rate of 1</p>
+
+<h4>Foreign Currencies</h4>
+<p>If you do business with vendors who charge in a different currency, enter a name for that currency (e.g. USD) and set the approximate exchange rate compared to your currency. </p>
+
+<p><b>Note:</b> names are limited to 10 characters or less</p>
+
+<p>The exchange rate is used to calculate the balances in your bookfund materials budgets when you purchase materials using "normal" acquisitions.</p>
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: admin/issuingrules.tmpl
===================================================================
RCS file: admin/issuingrules.tmpl
diff -N admin/issuingrules.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ admin/issuingrules.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,19 @@
+<!-- TMPL_INCLUDE name="help-top.inc" -->
+<h1>Issuing rules</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>Overdue charges</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" -->
\ No newline at end of file
Index: admin/itemtypes.tmpl
===================================================================
RCS file: admin/itemtypes.tmpl
diff -N admin/itemtypes.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ admin/itemtypes.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,22 @@
+<!-- TMPL_INCLUDE name="help-top.inc" -->
+<h1>Item types management</h1>
+<p>You can define as many itemtypes 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><b>Code:</b> The itemtype code is limited to four characters.</p>
+
+<p><b>Description:</b> This is the field that users see instead of the code</p>
+
+<p><b>Renewable:</b> How many times each item may be renewed to a borrower.</p>
+
+<p><b>Charge:</b> The amount you might charge to users for borrowing items of a certain type (for example, videos).</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 item types</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" -->
\ No newline at end of file
Index: admin/koha2marclinks.tmpl
===================================================================
RCS file: admin/koha2marclinks.tmpl
diff -N admin/koha2marclinks.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ admin/koha2marclinks.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,12 @@
+<!-- TMPL_INCLUDE name="help-top.inc" -->
+<h1>Koha 2 MARC links</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" -->
Index: admin/marc_subfields_structure.tmpl
===================================================================
RCS file: admin/marc_subfields_structure.tmpl
diff -N admin/marc_subfields_structure.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ admin/marc_subfields_structure.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,30 @@
+<!-- TMPL_INCLUDE name="help-top.inc" -->
+<h1>MARC tag structure administration</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 : if checked, the subfield is an URL, and can be clicked</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>link : If you enter a field/subfield here (200b), a little glass appears after the subfield. If the user clic on the glass, a search is done on the DB for the field/subfield with the same value. Can be used for 2 main topic :
+ <ul>
+ <li>on a field like author (200f in UNIMARC), put 200f here, you will be able to see all biblios with the same author</li>
+ <li>on a field that is a link (4xx) to reach another biblio. For example, put 011a in 464$x, will find the serial that was previously with this issn. With the 4xx pligin, you get a powerful tool to manage biblios connected to biblios</li>
+ </ul>
+</li>
+</ul>
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
Index: admin/marctagstructure.tmpl
===================================================================
RCS file: admin/marctagstructure.tmpl
diff -N admin/marctagstructure.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ admin/marctagstructure.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,30 @@
+<!-- TMPL_INCLUDE name="help-top.inc" -->
+<h1>MARC tag structure administration</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 a MARC tag structure for each biblio framework you have defined.</p>
+
+<h4>Deleting tags</h4>
+<p>If you are certain that you will never use a MARC tag, then you can delete it. However, this isn't recommended and it is probably better to leave it.</p>
+
+<h4>Adding tags</h4>
+<p>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>
+
+<h4>For each subfield you can set:</h4>
+<ul><li><b>repeatable:</b> 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><b>Mandatory:</b> wether the field is mandatory or not. If mandatory, the cataloger can't validate the biblio if the subfield is empty.
+ <li><b>Search also:</b> a list of field that Koha will also search on when the user do a search on the subfield
+ <li><b>Koha link:</b> very important as 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 wants to search on "title", this link is used to find what is searched (245 if you're MARC21, 200 if you're UNIMARC).
+ <li><b>Text for librarian:</b> what appears before the subfield in the librarian interface
+ <li><b>Text for OPAC:</b> what appears before the field in the OPAC. If empty, the text for librarian is used instead
+ <li><b>Managed in tab:</b> 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. This prevents Koha getting confused by repeatable fields.
+ <li><b>hidden:</b> the field is managed, but NOT shown in opac. It's usually for internal fields
+ <li><b>URL:</b> if checked, the subfield is an URL, and can be clicked
+ <li><b>Auth value:</b> means the value is not free, but in the authorised value list of the selected type
+ <li><b>thesaurus:</b> means that the value is not free, but can be searched in authority/thesaurus of the selected category
+ <li><b>plugin:</b> 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><b>link:</b> useless for instance
+</ul>
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
Index: admin/printers.tmpl
===================================================================
RCS file: admin/printers.tmpl
diff -N admin/printers.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ admin/printers.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,7 @@
+<!-- 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" -->
Index: admin/stopwords.tmpl
===================================================================
RCS file: admin/stopwords.tmpl
diff -N admin/stopwords.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ admin/stopwords.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,13 @@
+<!-- TMPL_INCLUDE name="help-top.inc" -->
+<h1>Stop word administration page</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><b>Hint:</b><br />
+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>
+
+<p><b>Note:</b><br />
+If you change something in this table, ask your administrator to run misc/rebuildnonmarc.pl script</p>
+
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
Index: admin/systempreferences.tmpl
===================================================================
RCS file: admin/systempreferences.tmpl
diff -N admin/systempreferences.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ admin/systempreferences.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,70 @@
+<!-- TMPL_INCLUDE name="help-top.inc" -->
+<h1>System preferences administration</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|<br>Items :|{\n995b}{ - 995j}{/995k}|</b></p>
+ <p>means the "block" 995 has <br>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>Titre/auteur</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|<br/><label>Editeur</label>|{ ; 210a}{ (210b) }{ : 210c}{, 210d}|<br/>
+ #210|(|{210e}{(210f)}{ : 210g}{, 210h}|)<br/>
+ #215|<br/><label> </label>|{ ; 215a}{ : 215c}{ ; 215d}{ + 215e}|<br/>
+ #225|<br/><label>Description</label>|{ (225a}{ = 225d}{ : 225e}{. 225h}{. 225i}{ / 225f}{, I225x}{ ; 225v}|)<br/>
+ #606|<br/><label>Sujets</label>|{ 606a - }|<br/><br/><br/>
+ #995|<br>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>LibraryName --</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" -->
Index: admin/z3950servers.tmpl
===================================================================
RCS file: admin/z3950servers.tmpl
diff -N admin/z3950servers.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ admin/z3950servers.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,17 @@
+<!-- TMPL_INCLUDE name="help-top.inc" -->
+<h1>Z39.50 servers administration</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 <a target="new" href="http://www.indexdata.dk/targettest/">http://www.indexdata.dk/targettest/</a>. 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><b>Note:</b><br />
+Your system administrator will need to activate the z3950 client daemon on your server before you can use the z3950search. 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" -->
\ No newline at end of file
Index: authorities/authorities.tmpl
===================================================================
RCS file: authorities/authorities.tmpl
diff -N authorities/authorities.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ authorities/authorities.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1 @@
+authority help
\ No newline at end of file
Index: bull/bull-home.tmpl
===================================================================
RCS file: bull/bull-home.tmpl
diff -N bull/bull-home.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ bull/bull-home.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,12 @@
+<!-- TMPL_INCLUDE NAME="help-top.inc" -->
+ <h1>Serials subscription help</h1>
+ <li>Search for a subscription by using the filter button (with a ISSN or a title). If you enter a title, you can use the wildcard % : entering <b>%Times%</b> returns every subscription containing Times in the title. Entering <b>New York%</b> returns every subscription with title starting with New York</li>
+ <li>If you want to create a new subscription, click on <a href="#" onclick="javascript:opener.location.href='/cgi-bin/koha/subscription-add.pl'" class="button">Add subscription</a>
+</ul>
+
+<h1>Serials routing list help</h1>
+<ul><li>Step 1: Go to <a href="#" onclick="javascript:opener.location.href='/cgi-bin/koha/bull-home.pl?routing=1'; return false">Create/Edit Routing List</a>
+ <li>Step 2: Type in the title of the serial that will be circulated
+ <li>Step 3: Pick the correct title and click the Routing List link
+</ul>
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: bull/claims.tmpl
===================================================================
RCS file: bull/claims.tmpl
diff -N bull/claims.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ bull/claims.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,6 @@
+<!-- TMPL_INCLUDE NAME="help-top.inc" -->
+<h1>Claims</h1>
+<p>Claims contain all the items indicated as missing. If you wish to place this information in a report then click Export Data. This will copy all the information over into a comma-delimited format (CSV) so that it can be viewed in a spreadsheet.</p>
+<p>
+You can select all or some of the missing items to be included into the CSV report. This can then be linked to a company "Claim Letter" template in a word processing document.</p>
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: bull/lateissues.tmpl
===================================================================
RCS file: bull/lateissues.tmpl
diff -N bull/lateissues.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ bull/lateissues.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,9 @@
+<!-- TMPL_INCLUDE NAME="help-top.inc" -->
+ <h1>Outstanding Issues</h1>
+<p>You can either filter by one supplier or view all missing and late issues by all suppliers.</p>
+<ul><li>If the issue has arrived then simply click <b>Receive</b> and you will be taken to the <b>Check-In</b> screen for that journal
+ <li>Make sure you change status to <b>Arrived</b> and enter a <b>Branch</b> and <b>Barcode</b>
+ <li>If the issue was on the missing issues list then it will be removed from the missing items list and missing items box</li>
+</ul>
+
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: bull/routing.tmpl
===================================================================
RCS file: bull/routing.tmpl
diff -N bull/routing.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ bull/routing.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,13 @@
+<!-- TMPL_INCLUDE NAME="help-top.inc" -->
+<h1>Routing List</h1>
+ <li>Step 1: <b>Add List Members</b> This brings up a separate box where you search for a name
+ <li>Step 2: <b>Add</b> Simply click the 'Add' button next to the appropriate name. You can select as many as you wish. Once you are finished close that window
+ <li>Step 3: The names will then be displayed in the Rank order that they were added. If you wish to ensure that a particular person receives this serial before another person then adjust the Rank order to suit by selecting the rank number from the appropriate drop down list
+ <li>Step 4: <b>Notes</b> If you wish to add a note to the Routing Slip you can place a message in this box. Please note: There is a default message that will always appear on the Routing Slip: "Please return this journal promptly as others are waiting". This can only be edited/removed by getting a system administrator to edit the template
+ <li>Step 5: Click <b>Save</b>
+ <li>Step 6: Click <b>OK, Preview Routing Slip</b> if you are happy with the saved information. This will open a new window with the slip in it
+ <li>Step 7: <b>Print</b> this will print the slip, close the new window and take you back to the subscription homepage for the main window
+</li><ul>
+<p>From now on there will be a Routing List button at the top of the check-in page to speed up the printing of routing slips for this subscription in the future</p>
+
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: bull/statecollection.tmpl
===================================================================
RCS file: bull/statecollection.tmpl
diff -N bull/statecollection.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ bull/statecollection.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,35 @@
+<!-- TMPL_INCLUDE NAME="help-top.inc" -->
+<h1>Receive issues (Check-In form)</h1>
+<ul><li>Step 1: Once the Serial Holdings Record has been filled out and saved.
+Click Receive button at the top
+ <li>Step 2: Check-In form<br>
+The form should be partly filled out already, showing the next expected issue to
+arrive. Check that the details are correct
+ <li>Step 3: Change the Status to whichever is correct:
+ <ul><li>Arrived
+ <li>Missing
+ <li>Late
+ <li>Not available
+ </ul>
+ <li>Step 4: Enter the Barcode<br>
+If a barcode is not needed, leave the system generated barcode in the box. For the item to show up in the Catalogue it must have a barcode attached to it
+ <li>Step 5: Save Changes<br>
+The details will then show up in the appropriate box below. If the issue is late then another set will appear showing the details for the late issue. This will remain there until it either arrives or is deemed missing or not available
+</ul>
+If the item is missing it will appear in the Missing Issues box below.
+
+<h1>Expiry and Renewal</h1>
+The number entered in the Subscription Length field in the Serial Holdings Record calculates the date the serial will expire on. Two warnings will occur:
+<ol><li>On the penultimate issue the user will be warned that the subscription will expire next issue
+ <li>A warning will come up if no more issues are expected on the Check-In screen:<br><b>
+Subscription has expired<br>
+Waited last issue status can't be changed. Renew your subscription
+</b>
+</ol>
+<ul><li>Step 1: Click Renew
+ <li>Step 2: Indicate the next subscription period<br>
+This will return the user to the Check-In screen and allow the user to check-in the next issue for the new subscription period
+</ul>
+<b>Please note:</b> By submitting a Renewal form a message will be placed in the Acquisitions system.<br>
+There will be a notice for Renewals and it is up to the person who does ordering to either Accept or Reject the renewal of the Order and place the order manually. koha does not have automatic ordering at this stage.
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: bull/subscription-add.tmpl
===================================================================
RCS file: bull/subscription-add.tmpl
diff -N bull/subscription-add.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ bull/subscription-add.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,136 @@
+<!-- TMPL_INCLUDE NAME="help-top.inc" -->
+<h1>Serial Holdings Record</h1>
+<p>There are 4 sections to this form:</p>
+<h3>Section 1: Subscription Information</h3>
+<ul><li>Step 1: Search for a Supplier<br>
+If you want to claim any issues then you need to elect a supplier at this point
+ <li>Step 2: Search for Biblio<br>
+it should find the item that was just set up in Acquisitions
+Create Biblio – if you have not yet set this up in Acquisitions it will take you
+back to Acquisitions Order Form
+ <li>Step 3: Fill out other details in the Subscription Information box
+</ul>
+<h3>Section 2: Planning</h3>
+<ul><li>Step 4: Fill out the details in the <a href="#planning">Planning</a> box<br>
+This is a critical component of managing serials. In order to make the
+system predict the next issue the user must fill out each of these fields.
+Once completed it will populate the Numbering Calculation box below
+</ul>
+<a href="#planning">More details about Planning</a>
+<h3>Section 3: Subscription length</h3>
+<ul><li>Step 5: Fill out the Subscription length box<br>
+Indicate the expected length of time that this serial will be subscribed to.
+Choose the most appropriate format:
+ <ul><li>Issues
+ <li>Weeks
+ <li>Months
+ </ul>
+This sets up the expiry date in the system and also alerts user the subscription is to expire on entering the penultimate issue
+</ul>
+<a name="planning"></a><h3>Section 4: Numbering Calculation</h3>
+<ul><li>Step 6: If a choice has been made in the Numbering Pattern section then the Numbering Calculation will automatically be filled out and presented in this section. However, if the Numbering Pattern is "None of the above" then a formula will be presented and the user must fill this out.<br>
+<a href="#calc">More detail about the Numbering Calculation formula</a>
+ <li>Step 7: Add Subscription<br>
+Once that is filled out then you see the completed details page.
+If there is a mistake you can go back and Edit the details<br>
+
+<h3>Planning</h3>
+<p>To explain the Planning component of the Serial Holdings Record:</p>
+<ol><li><b>First Issue ETA</b><br>
+Displays a calendar – choose the expected date of arrival in the library. This date is for
+administrative purposes only. It ties in with the Claims component of the Serials Module. It
+is not the date of the first issue. This is selected below in the <a href="#begins">Begins On</a> field
+ <li><b>Frequency</b><br>
+Drop down list of the main frequency patterns:
+ <ul><li>Unknown select this if none of the other choices are relevant
+ <li>1/day daily
+ <li>1/week weekly
+ <li>1/ 2 weeks (2/months) fortnightly
+ <li>1/3 weeks tri-weekly
+ <li>1/month monthly
+ <li>1 /2 months (6/year) bi-monthly
+ <li>1/3 months (1/quarter) quarterly
+ <li>1/quarter (seasonal) quarterly but related to seasons*
+ <li>2/year half yearly
+ <li>1/year annual
+ <li>1/ 2 years bi-annual
+ </ul>
+ <li><b>Numbering Pattern</b><br>
+Drop down list of the main numbering patterns:
+ <ul><li>Number
+ <li>Volume, Number, Issue
+ <li>Volume, Number
+ <li>Volume, Issue
+ <li>Number, Issue
+ <li>Seasonal only *Choose this if the publication pattern is only
+represented by seasons (ie. Summer, Autumn, Winter, Spring)
+ <li>None of the above
+ </ul>
+If it is "none of the above" this will bring up a <a href="#calc">Numbering Calculation formula</a> at the bottom of the screen
+ <li><a name="begins"></a><b>Begins on</b><br>
+Displays a calendar - choose the date of the first issue. For example, the library is subscribing to a monthly magazine and the first issue expected is the February issue. You would then choose 1st of February
+</ul>
+<a name="calc"></a><h3>Numbering Calculation formula</h3>
+The "numbering formula" can be filled with any text and/or numbers. Three special tokens <b>{X}, {Y}</b> and <b>{Z}</b> can be used to define the calculation formula. <b>X Y Z</b> values are calculated with the
+following method:
+<ul><li><b>Add:</b> the number here is added to X Y Z
+ <li><b>Once every:</b> the number before can be added on every issue or less often
+ <li><b>When more than:</b> if the calculated number is more than the value here
+ <li><b>Set back to:</b> if the previous condition is valid, the calculated number is set to this one instead
+ <li><b>Last value / begins with:</b> the last value calculated or the 1st value (when adding a subscription)
+</ul>
+<h4>Example 1</h4>
+<p>
+Many serials are identified by a custom numbering formula like "Vol. 4, No. 7, Issue. 8" (Volume 4,
+Number 7, Issue 8). The serials numbering formula calculator in Koha allows you to automate the
+updates of those values according to each serial's special formula. In this case, your Koha formula
+would look like this:
+<p><b>
+Vol. {X}, No. {Y}, Issue. {Z}
+</b></p>
+Each number in the formula is replaced by a variable. In the numbering calculation table you set
+the rules for how each number is incremented as each serial issue is acquired. Let's say in this
+example that your serial title releases 12 issues a year, that each 'number' collects 12 issues, and
+each 'Volume' collects 10 'Numbers.' <br>
+<br>
+Let's start with the <b>{Z}</b> column:
+<ul><li><b>Add:</b> 1
+ <li><b>Once every:</b> 1 - 'Issue' number increments by one each time an issue is published
+ <li><b>When more than:</b> 12 - The 'Issue' number resets every 12 issues
+ <li><b>Set back to:</b> 1 - resets to 1 every 12 issues
+ <li><b>Begins with:</b> 8 - The next issue should have this value
+</ul>
+In the <b>{Y}</b> column:
+<ul><li><b>Add:</b> 1 - Each 'Number' increments one at a time
+ <li><b>Once Every:</b> 12 - 'Number' increments by one every twelve issues
+ <li><b>When more than:</b> 10 - 'Number' resets every 120 issues (12 'Issues' x 10)
+ <li><b>Set back to:</b> 1 - reset to 1 every 120 issues
+ <li><b>Begins with:</b> 7 - The next issue should have this value for "Number"
+</ul>
+In the <b>{X}</b> column:
+<ul><li><b>Add:</b> 1 - 'Volume' increments by one every 120 issues
+ <li><b>Once Every:</b> 10 - 'Volume' increments by one every ten 'Issues'
+ <li><b>When more than:</b> 999999 - 'Volume' number should not reset to zero so set as very large number
+ <li><b>Set back to:</b> 0 - Shouldn't ever be reset
+ <li><b>Begins with:</b> 4 - The 'Volume' numbering should begin with 4
+</ul>
+
+With those values entered the numbering system for each new issue should look like this:
+<ul><li>Vol. 4, No. 7, Iss. 8
+ <li>Vol. 4, No. 7, Iss. 9
+ <li>Vol. 4, No. 7, Iss. 10
+ <li>Vol. 4, No. 7, Iss. 11
+ <li>Vol. 4, No. 7, Iss. 12 The "Issue" component rolls over after 12 issues and moves to the next number, eg. No. 8
+ <li>Vol. 4, No. 8, Iss. 1
+ <li>Vol. 4, No. 8, Iss. 2
+ <li>...
+ <li>Vol. 4, No. 10, Iss. 11
+ <li>Vol. 4, No. 10, Iss. 12 The "Volume" remains the same until it rolls over after 10 "Numbers", which rolls over after 12 "Issues". The volume will increment to the next number, eg. Volume 5
+ <li>Vol. 5, No. 1, Iss. 1
+ <li>Vol. 5, No. 1, Iss. 2
+</ul>
+<p><b>Note:</b><br>
+When you add a subscription Koha considers that you have already set up an order, or that you will do so soon. So, NO information is sent to the acquisition module. This is not the case when the subscription expires. In this case, a subscription renewal creates a "suggestion" that is sent to
+the acquisitions module.</p>
+
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: bull/subscription-detail.tmpl
===================================================================
RCS file: bull/subscription-detail.tmpl
diff -N bull/subscription-detail.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ bull/subscription-detail.tmpl 25 Jul 2006 22:16:35 -0000 1.1.2.1
@@ -0,0 +1,19 @@
+
+<!-- TMPL_INCLUDE NAME="help-top.inc" -->
+ <h1>Serials Subscription Detail</h1>
+<p>On this screen you can see the subscription detail and modify it if need be.</p>
+<h3>Subscription Information</h3>
+<p>
+This contains the name of the librarian that created the subscription, the name of the supplier providing the subscription, the cost and the budget affected. It also contains the title of the bibliographic record managed by the subscription.
+ </p>
+<h3>Planning Information</h3>
+<p>
+This contains the information to calculate the Publication Pattern and when the serial is expected to arrive in the library.
+ </p>
+<h3>Subscription length</h3>
+<p>
+This displays the expected length of the subscription. This can be indicated in either weeks, months or number of issues expected.
+ </p>
+<h3>Numbering calculation</h3>
+<p>This displays the formula for the Publication Pattern. </p>
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: circ/branchtransfers.tmpl
===================================================================
RCS file: circ/branchtransfers.tmpl
diff -N circ/branchtransfers.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ circ/branchtransfers.tmpl 25 Jul 2006 22:16:36 -0000 1.1.2.1
@@ -0,0 +1,12 @@
+<!-- TMPL_INCLUDE name="help-top.inc" -->
+<h1>Branch tansfers</h1>
+
+<p>From this screen you can enter information to transfer an item to another branch.</p>
+
+<h4>To transfer an item</h4>
+<ul><li>Select the Destination Branch
+ <li>Scan in or type the item's barcode
+</ul>
+
+<p>A completed transfer or an error message will then be displayed.</p>
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: circ/circulation.tmpl
===================================================================
RCS file: circ/circulation.tmpl
diff -N circ/circulation.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ circ/circulation.tmpl 25 Jul 2006 22:16:36 -0000 1.1.2.1
@@ -0,0 +1,28 @@
+<!-- TMPL_INCLUDE name="help-top.inc" -->
+<h1>Circulation / Issues help</h1>
+
+<h4>Branch and printer settings</h4>
+<p>Before you begin, it is very important that you take note of the branch and printer settings and change them if necessary. </p>
+
+<p>This should only have to be done the first time you do circulations from a workstation. </p>
+
+<p>Koha will report all issues and returns as being done from the branch displayed on your screen.</p>
+
+<h4>Enter the Borrower</h4>
+<p>Start by scanning the borrower's barcode or type in their name to find their account. Once Koha has found the borrower, you will see a new form for scanning or typing the item's identifying number (usually a barcode).</p>
+
+<h4>Date Due</h4>
+<ul><li>By default Koha will calculate the due date from parameters which have already been set up for the item type and user type.
+ <li>You can over-ride the pre-configured due date by selecting a Day/Month/Year
+ <li>If you wish to have this item and all subsequent items in this transaction to have a date due other than the default date due defined for the item type, use the "Sticky Due Date" to set the date due before scanning the first item.
+</ul>
+
+<h4>Scan the item to be issued</h4>
+<p>Issuing will be done immediatly and shown, with other borrower issues, at bottom of the screen.</p>
+
+<h4>Messages</h4>
+<p>If issuing the item is problematic, then a message box will appear asking for confirmation of the issue. For example, the item being issued to another borrower, or borrower having been issued too many items. If the confirmation involves another operation (if item is issued to another borrower, then issuing also means making a return), then it's also done at the same time.</p>
+
+<p>If issuing the item can't be done, then you can't confirm the issue. For example, if the barcode does not exist.</p>
+
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
Index: circ/returns.tmpl
===================================================================
RCS file: circ/returns.tmpl
diff -N circ/returns.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ circ/returns.tmpl 25 Jul 2006 22:16:36 -0000 1.1.2.1
@@ -0,0 +1,21 @@
+<!-- TMPL_INCLUDE name="help-top.inc" -->
+<h1>Circulation / Returns help</h1>
+
+<h4>Branch and printer settings</h4>
+<p>Before you begin, it is very important that you take note of the branch and printer settings and change them if necessary. </p>
+
+<p>This should only have to be done the first time you do circulations from a workstation. </p>
+
+<p>Koha will report all issues and returns as being done from the branch displayed on your screen.</p>
+
+<h4>To enact a return</h4>
+<p>Scan or type the returned item's identifying number (usually a barcode) in the field.</p>
+
+<h4>Messages</h4>
+<p>If there is something specific for the item or the borrower (like borrower having debts), a message box will warn you.</p>
+
+<p>If the item has been requested by someone else, you also are asked to validate the request. If you confirm it, the item status is changed to a "waiting" status and you can inform the borrower that the item is available.</p>
+
+<p>If the item is requested by someone in another branch, then you must validate the transfer too.</p>
+
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
Index: members/jmemberentry.tmpl
===================================================================
RCS file: members/jmemberentry.tmpl
diff -N members/jmemberentry.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ members/jmemberentry.tmpl 25 Jul 2006 22:16:36 -0000 1.1.2.1
@@ -0,0 +1,29 @@
+<!-- TMPL_INCLUDE name="help-top.inc" -->
+<h1>Add New Junior Member</h1>
+
+<!--<h2>Add Member, person</h2>-->
+<p>
+ This is the form for adding a new junior member to the database. The record is associated with the parent/guardian.
+</p>
+<p>
+ Every field with an asterisk must be completed, or you will get an error, and the record will not be added to the database.
+</p>
+<p>
+ When you are done with the record, click the Save button at the bottom.
+</p>
+<p>
+ The clear all Fields button will reset the page to a blank form if you made a mistake and wish to start again.
+</p>
+<p>
+ You can always come back and edit what you enter in the Add Member screen by searching for the borrower by using their last name or card number, selecting a user by clicking on the entry in the search list, and then clicking the Modify button on the member information screen.
+</p>
+<h4>Sort Fields</h4>
+<p>
+ The sort fields are free text available for your own requirements.
+</p>
+<p>
+ They can be useful for statistical purposes as they appear in the "Borrowers statistics" wizard.
+</p>
+
+<br />
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: members/member-flags.tmpl
===================================================================
RCS file: members/member-flags.tmpl
diff -N members/member-flags.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ members/member-flags.tmpl 25 Jul 2006 22:16:36 -0000 1.1.2.1
@@ -0,0 +1,107 @@
+<!-- TMPL_INCLUDE NAME="help-top.inc" -->
+
+<h1>Members Flags</h1>
+<p>
+ From this page you can refine the functions a member or librarian may perform</p>
+</p>
+<ul>
+ <li>
+ <b>
+ Superlibrarian
+ </b>
+ - Access to all librarian functions (Librarian)
+ </li>
+ <li>
+ <b>
+ Circulate
+ </b>
+ - Circulate books (Librarian - Issue and Return)
+ </li>
+ <li>
+ <b>
+ Catalogue
+ </b>
+ - View Catalogue (Librarian Interface)
+ </li>
+ <li>
+ <b>
+ Parameters
+ </b>
+ - Set Koha system paramters (Librarian)
+ </li>
+ <li>
+ <b>
+ Borrowers
+ </b>
+ - Add or modify borrowers (Librarian)
+ </li>
+ <li>
+ <b>
+ Permissions
+ </b>
+ - Set user permissions (Librarian - this page)
+ </li>
+ <li>
+ <b>
+ Reserveforothers
+ </b>
+ - Reserve books for patrons (Librarian)
+ </li>
+ <li>
+ <b>
+ Borrow
+ </b>
+ - Borrow books (Librarian and Patron - by default this is available)
+ </li>
+ <li>
+ <b>
+ Reserveforself
+ </b>
+ - Reserve books for self (Librarian and Patron)
+ </li>
+ <li>
+ <b>
+ Editcatalogue
+ </b>
+ - Edit Catalogue (Librarian - Modify bibliographic/holdings data)
+ </li>
+ <li>
+ <b>
+ Updatecharges
+ </b>
+ - Update borrower charges (Librarian)
+ </li>
+ <li>
+ <b>
+ Acquisition
+ </b>
+ - Acquisition and/or suggestion management (Librarian)
+ </li>
+ <li>
+ <b>
+ Management
+ </b>
+ - Set library management parameters (Librarian)
+ </li>
+ <li>
+ <b>
+ Tools
+ </b>
+ - Use tools (Librarian - export, import, barcodes)
+ </li>
+ <li>
+ <b>
+ Order
+ </b>
+ - Place orders in acquisitions (Librarian - can place orders in acquistions but not receive them)
+ </li>
+ <li>
+ <b>
+ Receive
+ </b>
+ - Receive orders in acquisitions (Librarian)
+ </li>
+</ul>
+
+<br />
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
Index: members/member.tmpl
===================================================================
RCS file: members/member.tmpl
diff -N members/member.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ members/member.tmpl 25 Jul 2006 22:16:36 -0000 1.1.2.1
@@ -0,0 +1,7 @@
+<!-- TMPL_INCLUDE name="help-top.inc" -->
+<h1>Members help</h1>
+<p>If your search returned a list of members you can click on their surname for more detailed information. If you wish you can re-order the list by either surname or card number from the dropdown and clicking 'Go'.</p>
+
+<p>If your search returned 'There are no results for your search' you can either refine your search, or add a new member by clicking the 'Add Adult Member' button</p>
+
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
Index: members/memberentry.tmpl
===================================================================
RCS file: members/memberentry.tmpl
diff -N members/memberentry.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ members/memberentry.tmpl 25 Jul 2006 22:16:36 -0000 1.1.2.1
@@ -0,0 +1,54 @@
+<!-- TMPL_INCLUDE name="help-top.inc" -->
+<h1>Add Member</h1>
+
+<!--<h2>Add Member, person</h2>-->
+<p>
+ This is the form for adding a new single member to the database.
+ <!--There is also a form for organisations, such as other libraries and non profit organisations you might lend to. You should use the Add Organisation tab at the top of the Member page for that.-->
+</p>
+<p>
+ Every field with an asterisk must be completed, or you will get an error, and the record will not be added to the database.
+</p>
+<p>
+ If you accidentally have two members with the same card number, the second duplicate will show up as just commas after you confirm the record.
+</p>
+<p>
+ When you are done with the record, click the Save button at the bottom.
+</p>
+<p>
+ The clear all Fields button will reset the page to a blank form if you made a mistake and wish to start again.
+</p>
+<p>
+ You can always come back and edit what you enter in the Add Member screen by searching for the borrower by using their last name or card number, selecting a user by clicking on the entry in the search list, and then clicking the Modify button on the member information screen.
+</p>
+<h4>Sort Fields</h4>
+<p>
+ The sort fields are free text available for your own requirements. They can be useful for statistical purposes as they appear in the "Borrowers statistics" wizard. For example, you may wish to flag members who belong particular clubs or interest groups.
+</p>
+<h4>Flags</h4>
+<p>
+ These flags appear during issuing and will prevent issues (unless overridden by the issuing librarian)
+</p>
+
+
+<!--
+<h2>Add Member, Institutional</h2>
+<p>
+ This is the form for adding a group of members. Suppose you had a YMCA group, or lend books to other Libraries. This would be the form to use for that purpose.
+</p>
+<p>
+ Every field with an asterisk must be filled out, or you will get an error, and the record will not be added to the database.
+</p>
+<p>
+ If you accidentally have two members with the same card number, the second duplicate will show up as just commas after you confirm the record.
+</p>
+<p>
+ When you are done with the record, click the Save button at the bottom.
+</p>
+<p>
+ The clear all Fields button will reset the page to a blank form in case you made a mistake.
+</p>
+-->
+
+<br />
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: members/members-home.tmpl
===================================================================
RCS file: members/members-home.tmpl
diff -N members/members-home.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ members/members-home.tmpl 25 Jul 2006 22:16:36 -0000 1.1.2.1
@@ -0,0 +1,23 @@
+<!-- TMPL_INCLUDE name="help-top.inc" -->
+<h1>Members</h1>
+<p>
+ From this screen you can manage the library patrons' information. From here you can renew items, view add, modify and delete records.
+</p>
+<p>
+ To check if a Member already exists, type their name, part name, or number into the search box, and click the GO button.
+</p>
+
+<p>
+ If there is already a Member matching the name you searched, it will show after you click GO. This can be particularly useful when people have lost their cards or when children forget their cards. That way, you can avoid having multiple numbers for the same Member.
+</p>
+
+<p>
+ If there is not a borrower matching your search, you can click the 'Add Adult Member' link
+</p>
+
+<p>
+ Alternatively, you can browse a section of borrowers by selecting the first letter of the Members's last name from the list.
+</p>
+
+<br />
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
Index: members/moremember.tmpl
===================================================================
RCS file: members/moremember.tmpl
diff -N members/moremember.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ members/moremember.tmpl 25 Jul 2006 22:16:36 -0000 1.1.2.1
@@ -0,0 +1,44 @@
+<!-- TMPL_INCLUDE name="help-top.inc" -->
+<h1>Member Information Screen</h1>
+<p>
+ This screen shows the information associated with a given patron.
+</p>
+<!--
+<p>
+ On the top left is their address and card number.
+</p>
+-->
+<p>
+ Guarantees are any members for which the member acts as a guarantor (eg Children and Junior Members). Clicking on their name/membership number will bring up their details.
+</p>
+<p>
+ A patron's annual membership fee payment status also shows on this screen.
+</p>
+<p>
+ Any fines a patron has will show up in the top middle of this screen.
+</p>
+
+<p>
+ Any materials a patron has requested will show up on the bottom.
+</p>
+<p>
+ You can get information on what a patron has read in the past by clicking on the Reading Record button.
+</p>
+<p>
+ Any items a patron currently has out will show up under "Items currently on issue".
+</p>
+<p>
+ If you would like to edit a patron's information, click the modify button on the lower left.
+</p>
+<p>
+ If you would like to PERMANENTLY delete a user, click the delete button. A confirmation box will appear, so don't worry about accidentally deleting a record. Just be absolutely sure before you delete!
+</p>
+<p>
+ The change password button allows a user to either set a new password or change their current password. This is useful to patrons that wish to place reserves online from home. You cannot see a password again once you change it, but you can reset a password.
+</p>
+<p>
+ Modify user flags allows an administrator to set which clerks, librarians, patrons, technical support people or trustees have access to certain parts of the database. Right now, one can either have permission to access everything on the Intranet side, or just have access to the OPAC.
+</p>
+
+<br />
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: reports/acquisitions_stats.tmpl
===================================================================
RCS file: reports/acquisitions_stats.tmpl
diff -N reports/acquisitions_stats.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ reports/acquisitions_stats.tmpl 25 Jul 2006 22:16:36 -0000 1.1.2.1
@@ -0,0 +1,34 @@
+<!-- TMPL_INCLUDE name="help-top.inc" -->
+<h1>Acquisitions Statistics</h1>
+<h3>Terms in Reports</h3>
+<ul>
+ <li>
+ Orders Placed / aqbasket.closedate - The date an acquistions basket was closed. This is when an order was completed.
+ </li>
+ <li>
+ Orders Received / aqorderdelivery.deliverydate - The number of items received from an order.
+ </li>
+ <li>
+ Items Acquired / items.dateaccessioned - the number of items which have been received and catalogued.
+ </li>
+ <li>
+ Book Seller / aqbooksellers.name
+ </li>
+ <li>
+ Document Type / biblioitems.itemtype
+ </li>
+ <li>
+ Budget / aqorderbreakdown.bookfundid
+ </li>
+ <li>
+ Sort1 / aqorders.sort1, aqorders.sort2 - Sorting fields you have entered
+ </li>
+</ul>
+
+<p>
+ You can choose to view the reports on screen or export them to a spreadsheet readable format. You will need to name the spreadsheet with an appropriate name as you save it.
+</p>
+
+
+<br />
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: reports/bor_issues_top.tmpl
===================================================================
RCS file: reports/bor_issues_top.tmpl
diff -N reports/bor_issues_top.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ reports/bor_issues_top.tmpl 25 Jul 2006 22:16:36 -0000 1.1.2.1
@@ -0,0 +1,12 @@
+<!-- TMPL_INCLUDE name="help-top.inc" -->
+<h1>Top List borrowers for Issues</h1>
+<p>
+ These reports list the most active borrowers
+</p>
+<p>
+ You can choose to view the reports on screen or export them to a spreadsheet readable format. You will need to name the spreadsheet with an appropriate name as you save it.
+</p>
+
+
+<br />
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: reports/borrowers_out.tmpl
===================================================================
RCS file: reports/borrowers_out.tmpl
diff -N reports/borrowers_out.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ reports/borrowers_out.tmpl 25 Jul 2006 22:16:36 -0000 1.1.2.1
@@ -0,0 +1,15 @@
+<!-- TMPL_INCLUDE name="help-top.inc" -->
+<h1>Borrowers with no Issues</h1>
+<p>
+ These reports list inactive borrowers.
+</p>
+<p>
+ You can limit the results by the number shown on the screen and by borrower category.
+</p>
+<p>
+ You can choose to view the reports on screen or export them to a spreadsheet readable format. You will need to name the spreadsheet with an appropriate name as you save it.
+</p>
+
+
+<br />
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: reports/borrowers_stats.tmpl
===================================================================
RCS file: reports/borrowers_stats.tmpl
diff -N reports/borrowers_stats.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ reports/borrowers_stats.tmpl 25 Jul 2006 22:16:36 -0000 1.1.2.1
@@ -0,0 +1,38 @@
+<!-- TMPL_INCLUDE name="help-top.inc" -->
+<h1>Borrowers statistics</h1>
+<h3>Terms in Reports</h3>
+<ul>
+ <li>
+ Borrower category / categorycode
+ </li>
+ <li>
+ Borrower Location / branchcode - the borrowers home branch
+ </li>
+ <li>
+ Borrower status
+ <ul>
+ <li>
+ debarred
+ </li>
+ <li>
+ gone no address
+ </li>
+ <li>
+ lost
+ </li>
+ </ul></li>
+ <li>
+ New Borrowers - New borrowers from the date you choose
+ </li>
+ <li>
+ Sort - sorting categories you have entered for borrowers.
+ </li>
+</ul>
+
+<p>
+ You can choose to view the reports on screen or export them to a spreadsheet readable format. You will need to name the spreadsheet with an appropriate name as you save it.
+</p>
+
+
+<br />
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: reports/cat_issues_top.tmpl
===================================================================
RCS file: reports/cat_issues_top.tmpl
diff -N reports/cat_issues_top.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ reports/cat_issues_top.tmpl 25 Jul 2006 22:16:36 -0000 1.1.2.1
@@ -0,0 +1,12 @@
+<!-- TMPL_INCLUDE name="help-top.inc" -->
+<h1>Top List On Catalogue Issues</h1>
+<p>
+ These reports rank the items which have been issued.
+</p>
+<p>
+ You can choose to view the reports on screen or export them to a spreadsheet readable format. You will need to name the spreadsheet with an appropriate name as you save it.
+</p>
+
+
+<br />
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: reports/catalogue_stats.tmpl
===================================================================
RCS file: reports/catalogue_stats.tmpl
diff -N reports/catalogue_stats.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ reports/catalogue_stats.tmpl 25 Jul 2006 22:16:36 -0000 1.1.2.1
@@ -0,0 +1,34 @@
+<!-- TMPL_INCLUDE name="help-top.inc" -->
+<h1>Catalogue statistics</h1>
+<h3>Terms in Reports</h3>
+<ul>
+ <li>
+ Dewey Classification - enter a range
+ </li>
+ <li>
+ Callnumber - enter a range
+ </li>
+ <li>
+ Document Type / itemtype
+ </li>
+ <li>
+ Publisher / publishercode - enter a full or part name.
+ </li>
+ <li>
+ Publication Year / publicationyear
+ </li>
+ <li>
+ Home Branch / items.homebranch - select a branch.
+ </li>
+ <li>
+ Location / items.location - select a branch
+ </li>
+</ul>
+
+<p>
+ You can choose to view the reports on screen or export them to a spreadsheet readable format. You will need to name the spreadsheet with an appropriate name as you save it.
+</p>
+
+
+<br />
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: reports/inventory.tmpl
===================================================================
RCS file: reports/inventory.tmpl
diff -N reports/inventory.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ reports/inventory.tmpl 25 Jul 2006 22:16:36 -0000 1.1.2.1
@@ -0,0 +1,12 @@
+<!-- TMPL_INCLUDE name="help-top.inc" -->
+<h1>Inventory/Stocktaking</h1>
+<p>
+ From this screen you can search for a selection of the catalogue based on MARC records.
+</p>
+<p>
+ Enter the range of records you wish to examine and a date from which you wish to search from (Not seen since).
+</p>
+
+
+<br />
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: reports/issues_stats.tmpl
===================================================================
RCS file: reports/issues_stats.tmpl
diff -N reports/issues_stats.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ reports/issues_stats.tmpl 25 Jul 2006 22:16:36 -0000 1.1.2.1
@@ -0,0 +1,30 @@
+<!-- TMPL_INCLUDE name="help-top.inc" -->
+<h1>Issues statistics</h1>
+<h3>Terms in Reports</h3>
+<ul>
+ <li>
+ Period / datetime
+ </li>
+ <li>
+ Borrower Category / borrowers.categorycode
+ </li>
+ <li>
+ Document Type / itemtype
+ </li>
+ <li>
+ Branch / branch
+ </li>
+ <li>
+ Sort - Borrowers sorting fields you have entered
+ </li>
+</ul>
+<p>
+ You can choose to view the statistics by total numbers - "Count issues" or rate - "Circulation rate".
+</p>
+<p>
+ You can choose to view the reports on screen or export them to a spreadsheet readable format. You will need to name the spreadsheet with an appropriate name as you save it.
+</p>
+
+
+<br />
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: reports/reservereport.tmpl
===================================================================
RCS file: reports/reservereport.tmpl
diff -N reports/reservereport.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ reports/reservereport.tmpl 25 Jul 2006 22:16:36 -0000 1.1.2.1
@@ -0,0 +1,12 @@
+<!-- TMPL_INCLUDE name="help-top.inc" -->
+<h1>Unfilled Reserves</h1>
+<p>This page shows current unfilled reserves.</p>
+<p>
+ Click on a borrower Name to view the membership record and manage the requested item.
+</p>
+<p>
+ Click on the Title to view the catalogue details.
+</p>
+
+<br />
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
Index: search.marc/search.tmpl
===================================================================
RCS file: search.marc/search.tmpl
diff -N search.marc/search.tmpl
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ search.marc/search.tmpl 25 Jul 2006 22:16:36 -0000 1.1.2.1
@@ -0,0 +1,36 @@
+<!-- TMPL_INCLUDE NAME="help-top.inc" -->
+ <h1>Search</h1>
+ <p>The search is divided into 2 different parts:</p>
+ <h2>Usual fields</h2>
+ <p>The usual fields are in the top part of the screen. They contain:</p>
+ <ul>
+ <li>Keyword: search on anything</li>
+ <li>Title</li>
+ <li>Author</li>
+ <li>Barcode: the library barcode of the book</li>
+ <li>Dewey</li>
+ <li>Call number</li>
+ <li>ISBN</li>
+ <li>Item type: select the item type here. If none is selected, the search is done on every item type</li>
+ <li>Branch: select a specific branch here. If none selected, the search is done on every branch</li>
+ </ul>
+ <h4>Search method</h4>
+ <ul>
+ <li>If you enter values in more than 1 field, the search is "and-ed" (biblios that contains <b>title</b> AND <b>author</b>)</li>
+ <li>A biblio is selected if it's field <b>contains</b> the term you entered</li>
+ <li>If you enter a * (or a %) at the end of a term, Koha searches for words starting with your term (entering <b>lower*</b> means : find biblios that have a <b>title containing a word starting by lower</b></li>
+ </ul>
+ <h4>Subject Search</h4>
+ <ul>
+ <li>Click on the Subject Search link to start a new search on the subject fields.</li>
+ </ul>
+ <h2>Complete MARC search</h2>
+ <p>In the lower part of the search screen, the <b>More fields</b> box let you enter whatever you want : and, or, exclusions (not), search on any MARC field/subfield</p>
+ <p><b>IMPORTANT NOTE : </b>for performance reasons, the * is valid only if you enter a word more than 3 letters long. for words of 3 letters or less, the * is <b>ignored</b></p>
+ <h4>Suggestions</h4>
+ <ul>
+ <li>The suggestions popup, is a list of alternate words from titles in the library and their frequency.</li>
+ <li>Clicking on a word in the popup will replace the word in the search field and add it to the search.</li>
+ </ul>
+ <br />
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
More information about the Koha-cvs
mailing list