From cf7b493432b9cf29f16e22c11edfdf2f2162c4b6 Mon Sep 17 00:00:00 2001
From: oleonard Sorting Field 1 and Sorting Field 2 may now be related to a list of Authorized Values. All you have to do is define an Asort1 or Asort2 category of authorised values and enter the desired values into these categories. You will then be able to use them through Add/Modify Bibliographic Record page 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. Book Funds may be ignored if you are setting your System Preferences to "simple" acquisitions: the funds are only useful when using "normal" acquisitions. "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. Each Book Fund has a unique fund code, limited to no more than five characters, that identifies it. You should decide on your fund codes (e.g. something like BOOKS, AV, MAGS, DATA for the four book funds described above) and enter the code in the "Book fund" box, then a full name in the "Name" box. Once you have set up a fund, you will see a link to a page for setting up the fund budget. Here you will enter the beginning and ending dates of your budget year and the amount of money in that particular budget line. Do not use any kind of currency notation (like "$") or commas when entering the number. (Commas will be converted to decimal points.) NOTE: Your dates will not saved correctly unless you have set your date format in the System Preferences section of the Parameters page -- DO THIS BEFORE setting budgets.) 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. 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. 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. You can define as many Authority types as you want. IMPORTANT
+ 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)
+ biblio frameworks are used to catalogue your biblios. Unlike Koha 2.0, in this version you can have more than 1 framework to catalogate differently various materials. You can, for example, define 1 framework for monographies, 1 framework for serials, 1 framework for URL... Once a framework type is created, you can clic on "MARC structure" to define the exact MARC structure. The first time, Koha will ask you to select an existing framework to copy into the new one. Thus, you don't have to define all the MARC structure Fill in information about your library service outlets on this page. 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." 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!) Here is where you define the types of users of your library and how they will be handled. 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 : 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). 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). Enrollment Fee and Reserve Fee (if any) should be entered either as whole numbers or with six decimal places, with no currency notation (e.g. "1.250000" instead of "$1.25"). Overdue Notice Required lets you bypass generating overdue notices for this user type. 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. 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. Define the currencies you deal with here. You should at least define your local currency here, giving it a name (like US DOLLAR or EURO) and setting the "rate" at 1. If you do business with vendors who charge in a different currency, enter a name for that currency (e.g. PESO) and set the approximate exchange rate compared to your currency. (Note: names are limited to 10 characters or less.) The exchange rate is used to calculate the remain balances in your materials budgets when you purchase materials using "normal" acquisitions. Issuing rules deals with 2 topics : 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. 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 The * 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 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. (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.) You can define as many itemtypes as you want. 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. The itemtype code is limited to four characters. This code is rarely displayed by Koha; instead the description of the type will be what users see. "Rental charge" is any amount you might charge to users for borrowing items of a certain type (like videos). "Renewals allowed" says how many times an items of this type may be renewed. Item types are useful for many things, and very important in controlling how Koha works : Setting up item types is one of the first things you should do after installing the Koha software. This page provides a simplified way to map your MARC tags and subfields to the non-MARC Koha database tables for default biblio framework. 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. 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. 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. 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. 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. 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. You can define as the marc tag structure for each biblio framework you have defined 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. 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. For each subfield you can set : 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. You can define as the marc tag structure for each biblio framework you have defined 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. 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. For each subfield you can set : 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. (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.) 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. Here you should list all of the words you wish Koha to ignore when performing catalog searches or building the keyword index. 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. (Hint: If you are proficient at MySQL, it is often faster and easier to find an existing stopwords list, edit it, put it in the correct format, and use the MySQL "Load Data Infile" command to import the list into the stopwords table. Many academic libraries publish their stopwords list on the Internet, or you can ask other Koha libraries if they would share their stopword list.) 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. ISBD -- Koha can display records in International Standard Bibliographic Description format. the syntax of this field is quite complex : 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 : #995|<br>Items :|{\n995b}{ - 995j}{/995k}| 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. 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 The UNIMARC (partial) definition for ISBD is #700|<label>Titre/auteur</label>|{700a}{701a}{702a}| ;
+ #200||{200a}{ [200b] }{. 200c}{ : 200e}{. 200h}{. 200i}{ / 200f}{ ; 200g}| Defines the Z39.50 servers you want Koha to search. 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. To add servers, you will need to know the domain name or IP address of the server, the port number to use, and the name of the database to access. This information is available for many servers worldwide by acessing the Index Data website at http://www.indexdata.dk/targettest/. All of the servers listed there accept anonymous connections. (Be sure to choose servers which deliver records in the proper MARC format for your Koha installation.) 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. 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. IMPORTANT NOTE : the z3950search will NOT work until your system administrator has not activated the z3950 client daemon on your server. The daemon is in KohaDirectory/script/z3950daemon. It should be added to rc.d to be launched during server boot. 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 %Times% returns every subscription containing Times in the title. Entering New York% returns every subscription with title starting with New York If you want to create a new subscription, click the "Add subscription" button. Once you have found the subscription you need, you can: 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 %Times% returns every subscription containing Times in the title. Entering New York% returns every subscription with title starting with New York If you want to create a new subscription, click on "Add subscription" This screen is divided in 2 parts The right part deals with issues. When you create a new subscription, the 1st issue is automatically calculated. When you want/need, you can define issues that have a new status: the left part contains 6 differents informations, that are automatically calculated for some of them, but that you can change
+ Koha calculates automatically the end of the subscription (based on the start date and the number of issues recieved). when a subscription has ended, you can't change the status of the last "waited number" (as it's not waited in fact). To be able to "recieve" this number, you must renew your subscription. Renewing a subscription means that you define some informations for the renewal. When those informations have been filled, a suggestion is automatically created in Koha. This suggestion can be managed by the librarian that orders books, as any other order (= budget and bookseller are defined here). Note that the subscription renewal done by the "serials librarian" is supposed to be immediate. We have decided to keep Koha as simple as possible. In fact, the subscription renewal won't be immediate, but we didn't wanted to add too much complexity.Add Bibliographic Record
+
+Book Fund Administration
+
+Authorised values management
+
+
+Authority types
+
+
+
+
+ Biblio framework
+ Help: Library Branches
+
+Borrower Categories
+
+Category Code and Description
+
+
+
+Enrollment Period
+Upper Age Limit and Age Required
+Enrollment Fee and Reserve Fee
+Overdue Notice Required
+MARC Check
+Currencies administration
+Issuing rules
+
+
+Issuing length and quantity
+Overdue charges
+Item types management
+
+
+Koha 2 MARC links
+MARC tag structure administration
+
+
+
+
diff --git a/koha-tmpl/intranet-tmpl/prog/en/help/admin/marctagstructure.tmpl b/koha-tmpl/intranet-tmpl/prog/en/help/admin/marctagstructure.tmpl
new file mode 100644
index 0000000000..1b42ae64b4
--- /dev/null
+++ b/koha-tmpl/intranet-tmpl/prog/en/help/admin/marctagstructure.tmpl
@@ -0,0 +1,26 @@
+Online Help: System Preferences -- MARC tag structure administration
+
+
+
+MARC tag structure administration
+
+
+
diff --git a/koha-tmpl/intranet-tmpl/prog/en/help/admin/printers.tmpl b/koha-tmpl/intranet-tmpl/prog/en/help/admin/printers.tmpl
new file mode 100644
index 0000000000..86458e3240
--- /dev/null
+++ b/koha-tmpl/intranet-tmpl/prog/en/help/admin/printers.tmpl
@@ -0,0 +1,9 @@
+Online Help: System Preferences -- Printer Administration
+
+Printer Administration
+Stop word administration page
+System preferences administration
+
+
+
diff --git a/koha-tmpl/intranet-tmpl/prog/en/help/admin/z3950servers.tmpl b/koha-tmpl/intranet-tmpl/prog/en/help/admin/z3950servers.tmpl
new file mode 100644
index 0000000000..2e2444ed4d
--- /dev/null
+++ b/koha-tmpl/intranet-tmpl/prog/en/help/admin/z3950servers.tmpl
@@ -0,0 +1,16 @@
+Online Help: System Preferences -- Z39.50 servers administration
+
+
+ #230||{ ; 230a}|
+ #205||{ ; 205a}{ , 205b}{ = 205d}{ / 205f}{ ; 205g}|
+ #210|<br/><label>Editeur</label>|{ ; 210a}{ (210b) }{ : 210c}{, 210d}|
+ #210|(|{210e}{(210f)}{ : 210g}{, 210h}|)
+ #215|<br/><label> </label>|{ ; 215a}{ : 215c}{ ; 215d}{ + 215e}|
+ #225|<br/><label>Description</label>|{ (225a}{ = 225d}{ : 225e}{. 225h}{. 225i}{ / 225f}{, I225x}{ ; 225v}|)
+ #606|<br/><label>Sujets</label>|{ 606a - }|<br/><br/>
+ #995|<br>Exemplaires :|{\n995b}{ - 995j}{/995k}|
+
Free Software ILSZ39.50 servers administration
+Serials subscription help
+
+
+
\ No newline at end of file
diff --git a/koha-tmpl/intranet-tmpl/prog/en/help/bull/bull-home.tmpl b/koha-tmpl/intranet-tmpl/prog/en/help/bull/bull-home.tmpl
new file mode 100644
index 0000000000..7a88662d71
--- /dev/null
+++ b/koha-tmpl/intranet-tmpl/prog/en/help/bull/bull-home.tmpl
@@ -0,0 +1,7 @@
+Online Help: Serials Subscriptions
+
+ Serials subscription help
+ Serials issues and summary
+ The right part
+
+
+ The left part
+
+
+ Subscription renewals
+
it 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 biblio managed by the subscription.
+it contains various information to calculate arrival dates.
+one field in this bloc should be filled : the subscription length can be calculated in weeks, months or number of issues to recieve
+The numbering of issues recieved can be a complex formulas. The "numbering formula" can be filled with any text and/or numbers. 3 special tokens {X} {Y} and {Z} can be user to define the calculation formula. XYZ values are calculated with the following method:
+N°2004/1, N°2004/2, N°2004/3, N°2004/4, N°2005/1, N°2005/2, N°2005/3, N°2005/4, N°2006/1
++ Note: when you add a subscription, Koha consider you already have done the order, or that you will do it 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 acquisition module. +
+ + \ No newline at end of file diff --git a/koha-tmpl/intranet-tmpl/prog/en/help/bull/subscription-detail.tmpl b/koha-tmpl/intranet-tmpl/prog/en/help/bull/subscription-detail.tmpl new file mode 100644 index 0000000000..32a9f9f388 --- /dev/null +++ b/koha-tmpl/intranet-tmpl/prog/en/help/bull/subscription-detail.tmpl @@ -0,0 +1,30 @@ +Online Help: Serials Subscription Detail + +it 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 biblio managed by the subscription.
+it contains various information to calculate arrival dates.
+one field in this bloc should be filled : the subscription length can be calculated in weeks, months or number of issues to recieve
+The numbering of items recieved can contain complex formulas. The "numbering formula" can be filled with any text and/or numbers. 3 special tokens {X} {Y} and {Z} can be user to define the calculation formula. XYZ values are calculated with the following method:
++
+ + \ No newline at end of file diff --git a/koha-tmpl/intranet-tmpl/prog/en/help/circ/circulation.tmpl b/koha-tmpl/intranet-tmpl/prog/en/help/circ/circulation.tmpl new file mode 100644 index 0000000000..4998cae75f --- /dev/null +++ b/koha-tmpl/intranet-tmpl/prog/en/help/circ/circulation.tmpl @@ -0,0 +1,16 @@ +Online Help: Circulation -- Issues + + +Before you begin, it is very important that you take note of the branch and printer settings and change them if necessary. This should only have to be done the first time you do circulations from a workstation, after which a browser cookie will remember the correct settings. If you do circulations under the wrong branch settings (for example, your branch setting is "Suburb," but you are actually working at the "Downtown" branch), then Koha will reset the location of all items scanned to the incorrect branch (Suburb) and the statistical reports will credit all circulations to the wrong branch.
+ +Now start by scanning the patron's barcode or type in their name to find their account. Once Koha has found the patron, you will see a new form for scanning or typing the item's identifying number (usually a barcode).
+ +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.
+ +If the item can be issued without problems, it will be done immediatly and shown (with other patron issues) at bottom.
+ +If the issuing is problematic, then another box will appear and ask for confirmation if possible. If the issuing is really impossible (for example, the barcode does not exist), then you can't confirm the issue. If it is possible but has something that needs confirmation (like item being issued to another patron, or patron having issued too many items), then you must confirm the issuing. If the confirmation means another operation (if item is issued to another patron, then issuing also means make the return), then it's also done
+ + diff --git a/koha-tmpl/intranet-tmpl/prog/en/help/circ/returns.tmpl b/koha-tmpl/intranet-tmpl/prog/en/help/circ/returns.tmpl new file mode 100644 index 0000000000..dbda64837e --- /dev/null +++ b/koha-tmpl/intranet-tmpl/prog/en/help/circ/returns.tmpl @@ -0,0 +1,14 @@ +Online Help: Circulation -- Returns + + +Before you begin, it is very important that you take note of the branch and printer settings and change them if necessary. This should only have to be done the first time you do circulations (or returns) from a workstation, after which a browser cookie will remember the correct settings. If you do returns under the wrong branch settings (for example, your branch setting is "Suburb," but you are actually working at the "Downtown" branch), then Koha will reset the location of all items scanned to the incorrect branch (Suburb).
+ +Now simply scan or type the returned item's identifying number (usually a barcode) in the box provided.
+ +The return is done and if there is something specific for the item or the patron (like patron having debts), a red box will warn you
+If the item has been requested by someone else, you also are asked to validate the request. If you confirm it, item is changed to a "waiting" status and you should warn the patron that the item is available
+If the item is requested by someone in another branch, then you must validate the transfer too
+ + diff --git a/koha-tmpl/intranet-tmpl/prog/en/help/export/marc.tmpl b/koha-tmpl/intranet-tmpl/prog/en/help/export/marc.tmpl new file mode 100644 index 0000000000..a3c474358e --- /dev/null +++ b/koha-tmpl/intranet-tmpl/prog/en/help/export/marc.tmpl @@ -0,0 +1,12 @@ +Online Help: MARC Export + + +This is a tool to export your bibliographic records in standard MARC communications format (ISO 2709). It exports only the basic bibliographic information with no holdings information other than any holdings information originally loaded into Koha using the bulkmarcimport tool.
+ +You are asked to provide a starting bibliographic record number and an ending number for the export. If you want to export all of your records, leave the start and end numbers blank.
+ +Records are downloaded to the workstation that requests the export and are saved in a file called "marc.pl."
+ + diff --git a/koha-tmpl/intranet-tmpl/prog/en/help/import/breeding.tmpl b/koha-tmpl/intranet-tmpl/prog/en/help/import/breeding.tmpl new file mode 100644 index 0000000000..b650ef8426 --- /dev/null +++ b/koha-tmpl/intranet-tmpl/prog/en/help/import/breeding.tmpl @@ -0,0 +1,25 @@ +Online Help: MARC Import + + +This is one of the screens you will see frequently if you are starting from scratch.
+ +It is useful to import a bunch of ISO 2709 biblios that can be used later for a quick cataloguing
+ +First, you need to browse your computer to find the MARC record that you grabbed for your item. Click on
+ +Choose File to browse.
+ +If you aren't sure if you've already imported a record, keep the radio button set to
+ +Ignore this one, keep the existing one.
+ +You can "name" the import to help you when you need to choose between more than 1 imported biblio (or just want to keep trace on where the biblios comes from)
+ +You can also change char encoding between MARC21 and UNIMARC
+ +You don't need to actually name every import, so you don't need to fill in this box if you don't want to. It is useful for telling imports apart if you've more than one of the same record.
+ +IMPORTANT : This tool is NOT intended to import ISO 2709 in your ACTIVE database. If you need to migrate data from another ILS, then you must consider $kohaInstall/scripts/misc/bulkmarcimport.pl
+ + diff --git a/koha-tmpl/intranet-tmpl/prog/en/help/members/memberentry.tmpl b/koha-tmpl/intranet-tmpl/prog/en/help/members/memberentry.tmpl new file mode 100644 index 0000000000..c32291683d --- /dev/null +++ b/koha-tmpl/intranet-tmpl/prog/en/help/members/memberentry.tmpl @@ -0,0 +1,19 @@ +Online Help: Adding a New Patron + +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.
+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.
+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.
+When you are done with the record, click the Save button at the bottom.
+The clear all Fields button will reset the page to a blank form in case you made a mistake.
+ +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.
+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.
+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.
+When you are done with the record, click the Save button at the bottom.
+The clear all Fields button will reset the page to a blank form in case you made a mistake.
+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.
+ + \ No newline at end of file diff --git a/koha-tmpl/intranet-tmpl/prog/en/help/members/members-home.tmpl b/koha-tmpl/intranet-tmpl/prog/en/help/members/members-home.tmpl new file mode 100644 index 0000000000..320a3c62f9 --- /dev/null +++ b/koha-tmpl/intranet-tmpl/prog/en/help/members/members-home.tmpl @@ -0,0 +1,15 @@ +Online Help: Members + +This is the Members portion of Koha.
+The Members portion stores the information you add about your patrons.
+To add a patron, type their name into the search box on the left, and +click the OK button.
+If there is already a borrower matching the name you searched, it will show +after you click OK. 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 patron.
+Alternatively, you can browse a section of borrowers by selecting the first +letter of the Patron's last name from the list on the right.
+ + diff --git a/koha-tmpl/intranet-tmpl/prog/en/help/members/moremember.tmpl b/koha-tmpl/intranet-tmpl/prog/en/help/members/moremember.tmpl new file mode 100644 index 0000000000..6a8c0c874e --- /dev/null +++ b/koha-tmpl/intranet-tmpl/prog/en/help/members/moremember.tmpl @@ -0,0 +1,17 @@ +Online Help: Member Information + +This screen shows the information associated with a given patron.
+On the top left is their address and card number.
+A patron's annual membership fee payment status also shows on this screen.
+Any fines a patron has will show up in the top middle of this screen.
+Any materials a patron has requested will show up on the top right of this screen.
+You can get information on what a patron has read in the past by clicking on the Reading Record button.
+Any items a patron currently has out will show up under "Items currently on issue".
+If you would like to edit a patron's information, click the modify button on the lower left.
+If you would like to PERMANENTLY delete a user, click the delete button on the lower left. A confirmation box will +appear, so don't worry about accidentally deleting a record. Just be absolutely sure before you delete!
+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.
+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.
+ + \ No newline at end of file diff --git a/koha-tmpl/intranet-tmpl/prog/en/help/nohelp.tmpl b/koha-tmpl/intranet-tmpl/prog/en/help/nohelp.tmpl new file mode 100644 index 0000000000..300f307f80 --- /dev/null +++ b/koha-tmpl/intranet-tmpl/prog/en/help/nohelp.tmpl @@ -0,0 +1,7 @@ +Online Help: No help for this topic! + + +Sorry, there is no help available for this topic
+ + \ No newline at end of file diff --git a/koha-tmpl/intranet-tmpl/prog/en/help/search.marc/search.tmpl b/koha-tmpl/intranet-tmpl/prog/en/help/search.marc/search.tmpl new file mode 100644 index 0000000000..6949682c1c --- /dev/null +++ b/koha-tmpl/intranet-tmpl/prog/en/help/search.marc/search.tmpl @@ -0,0 +1,29 @@ +Online Help: Search + +The search id divided in 2 differents parts :
+The usual fields are in the top part of the screen. They contains :
+Search method
+In the lower part of the search screen, the More fields box let you enter whatever you want : and, or, exclusions (not), search on any MARC field/subfield
+ +IMPORTANT NOTE : 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 ignored
+