From de58d82465b1f7f3eeb4b7316cccb4297af71d9f Mon Sep 17 00:00:00 2001 From: "Nicole C. Engard" Date: Tue, 29 Mar 2011 17:35:41 -0400 Subject: [PATCH] Bug 5940: Admin Help Files for 3.4 Signed-off-by: Nicole C. Engard Signed-off-by: Ian Walls Signed-off-by: Chris Cormack --- .../en/modules/help/admin/admin-home.tmpl | 8 + .../modules/help/admin/aqbudgetperiods.tmpl | 16 +- .../prog/en/modules/help/admin/aqbudgets.tmpl | 22 +- .../prog/en/modules/help/admin/aqplan.tmpl | 4 +- .../help/admin/auth_subfields_structure.tmpl | 161 ++++++++-- .../help/admin/auth_tag_structure.tmpl | 24 ++ .../modules/help/admin/authorised_values.tmpl | 274 +++++++++--------- .../prog/en/modules/help/admin/authtypes.tmpl | 40 +-- .../modules/help/admin/biblio_framework.tmpl | 36 ++- .../help/admin/branch_transfer_limits.tmpl | 41 +-- .../prog/en/modules/help/admin/branches.tmpl | 95 +++--- .../prog/en/modules/help/admin/categorie.tmpl | 101 +++++-- .../prog/en/modules/help/admin/checkmarc.tmpl | 5 +- .../prog/en/modules/help/admin/cities.tmpl | 32 +- .../en/modules/help/admin/classsources.tmpl | 86 +++--- .../prog/en/modules/help/admin/currency.tmpl | 8 +- .../en/modules/help/admin/fieldmapping.tmpl | 12 +- .../help/admin/item_circulation_alerts.tmpl | 44 +-- .../prog/en/modules/help/admin/itemtypes.tmpl | 97 ++++--- .../en/modules/help/admin/koha2marclinks.tmpl | 12 +- .../help/admin/marc_subfields_structure.tmpl | 181 ++++++++---- .../modules/help/admin/marctagstructure.tmpl | 34 +-- .../en/modules/help/admin/matching-rules.tmpl | 50 +++- .../modules/help/admin/patron-attr-types.tmpl | 88 ++++-- .../en/modules/help/admin/preferences.tmpl | 18 +- .../prog/en/modules/help/admin/roadtype.tmpl | 24 +- .../en/modules/help/admin/smart-rules.tmpl | 125 ++++---- .../prog/en/modules/help/admin/stopwords.tmpl | 15 +- .../en/modules/help/admin/z3950servers.tmpl | 38 ++- 29 files changed, 1046 insertions(+), 645 deletions(-) create mode 100644 koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/auth_tag_structure.tmpl diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/admin-home.tmpl b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/admin-home.tmpl index 9024cf5783..755947722d 100644 --- a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/admin-home.tmpl +++ b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/admin-home.tmpl @@ -5,21 +5,29 @@

The administration area is where you set all of your preferences for the system. Preference are broken down into several categories.

Global System Preferences

+

Koha has an extensive set of system preferences. The system preferences control all the various features within Koha and whether they are active in your install or not. System preferences are generally set once at install and then not changed.

+

If you are not sure what combination of system preferences to use, try using one of the sample profiles at install.

+

IMPORTANT: many preferences interact with each other. Turning on one system preference may require that others are also set.

Basic Parameters

+

Basic parameters is where library policies are set and governed. It is best to set your system preferences, and then to work through the Basic Parameters in the order that they appear on this page.

+

Note not all basic parameters are required to be set. For example if you do not plan to use budget based acquisitions, then Accounts and Budgets, Currencies and Exchange Rates can be ignored.

Patrons and Circulation

+

These parameters help with the control of patron records and circulation rules. It is best to make sure you set the basic parameters before visiting this section.

Catalog

+

Catalog parameters assist in configuring the cataloging functionality within Koha.

Additional Parameters

+

This list of parameters includes functionality that didn't fit in any other category. These items are optional and may not need to be altered depending on how your library is using Koha.

\ No newline at end of file diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/aqbudgetperiods.tmpl b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/aqbudgetperiods.tmpl index de90fec6ab..a763c5519b 100644 --- a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/aqbudgetperiods.tmpl +++ b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/aqbudgetperiods.tmpl @@ -2,18 +2,20 @@

Budgets

-

Budgets are the top level used for tracking accounting values related to acquisitions. An example would be to create a budget for the current year and then breaking that into Funds for different areas of the library.

+

Budgets are the top level used for tracking accounting values related to acquisitions.

-

Add a budget

+

An example would be to create a budget for the current year and then breaking that into Funds for different areas of the library.

+ +

Add a budget

To add a budget click the 'New Budget' button.

    -
  • Choose the time period this budget is for, whether it's an academic year, a fiscal year, a quarter, etc.
    • -
  • The Description should be something that will help you identify the budget when ordering
    • -
  • In the amount box do not use any symbols, simply enter the amount of the budget with numbers and decimals.
    • -
  • Marking a budget active makes it usable when placing orders in the acquisitions module, even if the order is placed after the budget end date. This will allow you to record orders that were places in a previous budget period.
    • -
  • Locking a budget means that Funds will not be able to be modified by librarians
    • +
  • Choose the time period this budget is for, whether it's an academic year, a fiscal year, a quarter, etc.
    • +
  • The Description should be something that will help you identify the budget when ordering
    • +
  • In the amount box do not use any symbols, simply enter the amount of the budget with numbers and decimals.
    • +
  • Marking a budget active makes it usable when placing orders in the acquisitions module, even if the order is placed after the budget end date. This will allow you to record orders that were places in a previous budget period.
    • +
  • Locking a budget means that Funds will not be able to be modified by librarians

Once you have made your edits, click the 'Save Changes' button. You will be brought to a list of your existing budgets.

diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/aqbudgets.tmpl b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/aqbudgets.tmpl index 34d9640ffc..9c1261a885 100644 --- a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/aqbudgets.tmpl +++ b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/aqbudgets.tmpl @@ -2,9 +2,13 @@

Funds

+

Budgets are broken in to funds.

+ +

Add a Fund

+

A fund is added to a budget.

-

IMPORTANT: A budget must be defined before a fund can be created.

+

Important: A budget must be defined before a fund can be created.

To add a new fund click the New button and then choose which Budget you would like to add the fund to.

@@ -13,14 +17,14 @@

The three first fields are required, the rest are optional

    -
  • Fund Code is a unique identifer for your fund
    • -
  • The Fund Name should be something that librarians will understand
    • -
  • Amount should be entered with only numbers and decimals, no other characters
    • -
  • You can choose to assign this fund to a librarian. Doing so will make it so that only that librarian can make changes to the Fund
    • -
  • Choose which library will be using this fund
    • -
  • You can restrict who can order from this fund by choosing either the owner or the library from the 'Restrict access to' menu
    • -
  • Notes are simply for any descriptive notes you might want to add so that librarians know when to use this fund
    • -
  • Planning categories are used for statistical purposes. To learn more about planning categories, check out the Planning Category FAQ.
    • +
  • Fund Code is a unique identifier for your fund
    • +
  • The Fund Name should be something that librarians will understand
    • +
  • Amount should be entered with only numbers and decimals, no other characters
    • +
  • You can choose to assign this fund to a librarian. Doing so will make it so that only that librarian can make changes to the Fund
    • +
  • Choose which library will be using this fund
    • +
  • You can restrict who can order from this fund by choosing either the owner or the library from the 'Restrict access to' menu
    • +
  • Notes are simply for any descriptive notes you might want to add so that librarians know when to use this fund
    • +
  • Planning categories are used for statistical purposes. To learn more about planning categories, check out the Planning Category FAQ.

When complete, click 'Submit' and you will be brought to a list of all of the funds for the budget.

diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/aqplan.tmpl b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/aqplan.tmpl index 1b03ec0756..b9d09febe9 100644 --- a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/aqplan.tmpl +++ b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/aqplan.tmpl @@ -4,7 +4,9 @@

When viewing the list of funds click the 'Planning' button and choose how you would like to plan to spend your budget.

-

If you choose 'Plan by MONTHS' you will see the budgeted amount broken down by months

+

If you choose 'Plan by MONTHS' you will see the budgeted amount broken down by months.

+ +

To hide some of the columns you can click the minus sign (-) to the right (or below as in the screenshot above) the dates. To add more columns you can click the plus sign (+) found above the 'Auto-fill row' buttons.

From here you can plan your budget spending by manually entering values or by clicking the 'Auto-fill row' button. If you choose to auto-fill the form the system will try to divide the amount accordingly, you may have to make some edits to split things more accurately.

diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/auth_subfields_structure.tmpl b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/auth_subfields_structure.tmpl index 36c026eceb..04349827a6 100644 --- a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/auth_subfields_structure.tmpl +++ b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/auth_subfields_structure.tmpl @@ -1,37 +1,142 @@ -

MARC tag structure administration

+

MARC Record Subfields

-

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

+

Frameworks are made up of MARC fields and subfields. To make edits to most Frameworks you must edit the fields and subfields. Clicking 'Edit' to the right of each subfield will allow you to make changes to the text associated with the field

-

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 :

-
    -
  • repeatable : whether it can be repeated or not. If it can be repeated, separate the values by a | in the MARC editor when you want to have the subfield twice
    • -
  • Mandatory : whether the field is mandatory or not. If mandatory, the cataloger can't validate the biblio if the subfield is empty.
    • -
  • Search also : a list of field that Koha will also search on when the user do a search on the subfield
    • -
  • Koha link : very important. 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).
    • -
  • Text for librarian : what appears before the subfield in the librarian interface
    • -
  • Text for OPAC : what appears before the field in the OPAC. If empty, the text for librarian is used instead
    • -
  • Managed in tab : deals with the tab where the subfield is shown. Ignore means that the subfield is not managed.
    • - -
  • Display: allows you to select possible visibility conditions. It is used only with the 'MARC View'.
    • -
  • Is a linking field : Select this if you want to use this field for linking other authorities to this authority. The kohafield should be set to auth_header.linkid in this subfield(preferred) or any other subfield in this field : -
  • URL : if checked, the subfield is an URL, and can be clicked
    • -
  • Auth value : means the value is not free, but in the authorized value list of the selected type
    • -
  • thesaurus : shows the authority type
    • -
  • 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)
    • -
  • -
  • Example MARC21 Subject Headings Authority -
    • Use field 035$a for your auth_header.authid and 035$8 for auth_header.authtypecode. Make sure your zebra authorities index these fields
      • -
    • Use field 150 for your subject headings
      • -
    • Use field 750$9 (add subfield if not present) for auth_header.linkid . Select Is a linking field. You may use any subfield for linking as $9 is not hardcoded -
    • When you add or modify an authority clicking on ... that will appear next to 750$9 will let you search any authority and link it to this record. You may repeat tag 750 and add as many linkages as you like
    +
      +
    • Each field has a tag (which is the MARC tag) +
        +
      • The 'Label for lib' is what will show in the staff client if you have advancedMARCeditor set to display labels
        • +
      • The 'Label for OPAC' is what will show on the MARC view in the OPAC
        • +
      • If you check 'Repeatable' then the field will have a plus sign next to it allowing you to add multiples of that tag
        • +
      • If you check 'Mandatory' the record will not be allowed to save unless you have a value assigned to this tag
        • +
      • 'Authorized value' is where you define an authorized value that your catalogers can choose from a pull down to fill this field in +To edit the subfields associated with the tag, click 'Subfields' to the right of the tag on the 'MARC Structure' listing
        • +
      +
      • +
    • From the list of subfields you can click 'Delete' to the right of each to delete the subfields
      • +
    • To edit the subfields click 'Edit Subfields'
      • +
    • For each subfield you can set the following values +
        +
      • Text for librarian +
          +
        • what appears before the subfield in the librarian interface
          • +
        +
        • +
      • Text for OPAC +
          +
        • what appears before the field in the OPAC.
          • +
        • If left empty, the text for librarian is used instead
          • +
        +
        • +
      • Repeatable +
          +
        • the field will have a plus sign next to it allowing you to add multiples of that tag
          • +
        • +
      • Mandatory +
          +
        • the record will not be allowed to save unless you have a value assigned to this tag
          • +
        +
        • +
      • Managed in tab +
          +
        • defines the tab where the subfield is shown. All subfields of a given field must be in the same tab or ignored. Ignore means that the subfield is not managed.
        +
        • +
      +
        +
      • Default value +
          +
        • defines what you want to appear in the field by default, this will be editable, but it saves time if you use the same note over and over or the same value in a field often.
          • +
        +
        • +
      +
        +
      • hidden +
          +
        • allows you to select from 19 possible visibility conditions, 17 of which are implemented. They are the following: +
            +
          • -9 => Future use
            • +
          • -8 => Flag
            • +
          • -7 => OPAC !Intranet !Editor Collapsed
            • +
          • -6 => OPAC Intranet !Editor !Collapsed
            • +
          • -5 => OPAC Intranet !Editor Collapsed
            • +
          • -4 => OPAC !Intranet !Editor !Collapsed
            • +
          • -3 => OPAC !Intranet Editor Collapsed
            • +
          • -2 => OPAC !Intranet Editor !Collapsed
            • +
          • -1 => OPAC Intranet Editor Collapsed
            • +
          • 0 => OPAC Intranet Editor !Collapsed
            • +
          • 1 => !OPAC Intranet Editor Collapsed
            • +
          • 2 => !OPAC !Intranet Editor !Collapsed
            • +
          • 3 => !OPAC !Intranet Editor Collapsed
            • +
          • 4 => !OPAC Intranet Editor !Collapsed
            • +
          • 5 => !OPAC !Intranet !Editor Collapsed
            • +
          • 6 => !OPAC Intranet !Editor !Collapsed
            • +
          • 7 => !OPAC Intranet !Editor Collapsed
            • +
          • 8 => !OPAC !Intranet !Editor !Collapsed
            • +
          • 9 => Future use
            • +
          +
          • +
        • ( ! means 'not visible' or in the case of Collapsed 'not Collapsed')
          • +
        +
        • +
      +
        +
      • Is a URL +
          +
        • if checked, it means that the subfield is a URL and can be clicked
          • +
        +
        • +
      +
        +
      • Link +
          +
        • If you enter a field/subfield here (200b), a link appears after the subfield in the MARC Detail view. This view is present only in the staff client, not the OPAC. If the librarian clicks on the link, a search is done on the database for the field/subfield with the same value. This can be used for 2 main topics : +
            +
          • on a field like author (200f in UNIMARC), put 200f here, you will be able to see all bib records with the same author.
            • +
          • on a field that is a link (4xx) to reach another bib record. For example, put 011a in 464$x, will find the serials that are with this ISSN.
            • +
          +
          • +
        • Important: This value should not change after data has been added to your catalog
          • +
        +
        • +
      +
        +
      • Koha link +
          +
        • 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 its meaning. Koha constantly maintains consistency between a subfield and its 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).
          • +
        +
        • +
      +
        +
      • Authorized value +
          +
        • means the value cannot by typed by the librarian, but must be chosen from a pull down generated by the authorized value list
          • +
        • In the example above, the 504a field will show the MARC504 Authorized Values when cataloging
          • +
        +
        • +
      +
        +
      • Thesaurus +
          +
        • means that the value is not free text, but must be searched in the authority/thesaurus of the selected category
          • +
        +
        • +
      +
        +
      • 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)
          • +
        +
        • +
      +
      • +
    • To save your changes simply click the 'Save Changes' button at the top of the screen
      • +
    + diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/auth_tag_structure.tmpl b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/auth_tag_structure.tmpl new file mode 100644 index 0000000000..eab5f7f8f6 --- /dev/null +++ b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/auth_tag_structure.tmpl @@ -0,0 +1,24 @@ + + +

    Authority Record Tags

    + +

    To add a field to a Authority Framework click the 'New Tag' button at the top of the Authority Framework definition

    + +

    This will open up a blank form for entering MARC field data

    + +

    Enter the information about your new tag:

    + +
      +
    • The 'Tag' is the MARC field number
      • +
    • The 'Label for lib' is the text that will appear in the staff client when in the cataloging module
      • +
    • The 'Label for OPAC' is the text that will appear in the OPAC when viewing the MARC version of the record
      • +
    • If this field can be repeated, check the 'Repeatable' box
      • +
    • If this field is mandatory, check the 'Mandatory' box
      • +
    • If you want this field to be a pull down with limited possible answers, choose which 'Authorized value' list you want to use
      • +
    + +

    When you're finished, click 'Save Changes' and you will be presented with your new field

    + +

    To the right of the new field is a link to 'Subfields,' you will need to add subfields before this tag will appear in your MARC editor.

    + + \ No newline at end of file diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/authorised_values.tmpl b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/authorised_values.tmpl index 8f917a96b5..6f258a1dfe 100644 --- a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/authorised_values.tmpl +++ b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/authorised_values.tmpl @@ -1,141 +1,149 @@ -

    Authorized values management

    +

    Authorized Values

    -

    Koha allows you to restrict the values that catalogers can place in some MARC subfields to certain pre-defined "authorized" values. These authorized values are defined here.

    -
      -
    • HINT : if a subfield is non mandatory, Koha automatically adds an empty value to the authorized value list, that is selected by default. If the subfield is mandatory, no empty value is added (and you should NOT add it in the list, as it's an illegal value !)
      • -
    • HINT2 : in the MARC editor, the list is ordered by Text, NOT by value. So you can define a default value by putting a space before the value you want to see first. For example, if your list is related to language, you can set "ENG" as authorized value and " English" as text. The space will order "ENG" as first default value, and the space won't be shown (because HTML automatically discard useless spaces). Super hint : you can put a value 1st with N spaces, then another one 2nd with N-1 space,..., a value in Nth position with 1 space. Don't abuse of this feature, it's easier to find a value in an alphabetical order. It should be used only to have a default value
      • -
    -

    Koha automatically sets up authorized value categories for your item types and branch codes, and you can link these authorized values to MARC subfields when you set up your MARC tag structure.

    -

    -

    Why would I want to define authorized values for MARC tags?

    -

    Authorized Values create a 'controlled vocabulary' for your staff. As an example, let us assume that your Koha installation is used by several libraries, and you use MARC 21. You might want to restrict the 850a MARC subfield to the institution codes for just those libraries. In that case, you could define an authorized values category (perhaps called "INST") and enter the institution codes as the authorized values for that category.

    - -TIP: Koha automatically sets up authorized value categories for your item types and branch codes, and you can link these authorized values to MARC subfields when you set up your MARC tag structure. - - Existing Authorized Values -Koha comes with several other categories and pre-defined values your library is likely to use, for instance 'Lost'. +

    Authorized values can be used in several areas of Koha. One reason you would add an authorized value category would be to control the values that can be entered into MARC fields by catalogers.

    -
      -
    • Asort1 -
        -
      • attached to acquisitions, that can be used for stats purposes
        • -
      • -
    • Asort2 -
        -
      • attached to acquisitions, that can be used for stats purposes
        • -
      • -
    • Bsort1 -
        -
      • attached to patrons, that can be used for stats purposes
        • -
      • -
    • Bsort2 -
        -
      • attached to patrons, that can be used for stats purposes
        • -
      • -
    • CCODE -
        -
      • collection code (appears when editing at item)
        • -
      • -
    • DAMAGED -
        -
      • descriptions for items marked as damaged (appears when editing an item)
        • -
      • -
    • HINGS_AS -
        -
      • - -holdings coded value??
        • -
      • -
    • HINGS_C -
        -
      • - -holdings coded value??
        • -
      • -
    • HINGS_PF -
        -
      • - -holdings coded value??
        • -
      • -
    • HINGS_RD -
        -
      • - -holdings coded value??
        • -
      • -
    • HINGS_UT -
        -
      • - -holdings coded value??
        • -
      • -
    • LOC -
        -
      • -shelving location (usually appears when editing an item)
        • -
      • -
    • LOST -
        -
      • descriptions for the items marked as lost (appears when editing an item)
        • -
      • -
    • NOT_LOAN -
        -
      • reasons why a title is not for loan
        • -
      • -
    • RESTRICTED -
        -
      • ??
        • -
      • -
    • STACK -
        -
      • ??
        • -
      • -
    • SUGGEST -
        -
      • list of patron suggestion reject or accept reasons (appears when managing suggestions)
        • -
      • -
    • WITHDRAWN -
        -
      • description of a withdrawn item (appears when editing an item)
        • -
      • -
    - View Authorized Values +

    Existing Values

    -
      -
    • To view the authorized values defined for a category that already exists like 'Lost', choose 'Lost' from the category dropdown menu
      • -
    • Then, you can see the values defined for the category "Lost" and edit them if you like.
      • -
    - Add Authorized Value +

    Koha installs with pre-defined values that your library is likely to use, for instance 'Lost'.

    -
      -
    • To add a new value under an existing category, click "New authorized value for"
      • -
    • Enter the value and description and choose an icon if you'd like
      • -
    • When finished, click 'Save'
      • -

    - Edit authorized values

    -
      -
    • Choose a category from the 'Show Category' dropdown menu
      • -
    • Click 'Edit' beside the authorized value you wish to edit
      • -
    • Make the changes you'd like and click 'Save'
      • -
    • - -TIP: Be careful about changing the 'Authorized value' as it may be associated with existing records.
      • -

    - Add a new Authorized Value Category

    +
      +
    • Asort1 +
        +
      • Used for acquisitions statistical purposes
        • +
      +
      • +
    • Asort2 +
        +
      • Used for acquisitions statistical purposes
        • +
      +
      • +
    • BOR_NOTES +
        +
      • Values for custom patron notes that appear on the circulation screen and the OPAC
        • +
      +
      • +
    • Bsort1 +
        +
      • Used for patron statistical purposes
        • +
      +
      • +
    • Bsort2 +
        +
      • Used for patron statistical purposes
        • +
      +
      • +
    • CART +
        +
      • Is the shelving cart location, used by InProcessingToShelvingCart and ReturnToShelvingCart
        • +
      +
      • +
    • CCODE +
        +
      • Collection codes (appears when cataloging and working with items)
        • +
      +
      • +
    • DAMAGED +
        +
      • Descriptions for items marked as damaged (appears when cataloging and working with items)
        • +
      +
      • +
    • HINGS_AS +
        +
      • General Holdings: Acquisition Status Designator :: This data element specifies acquisition status for the unit at the time of the holdings report.a
        • +
      +
      • +
    • HINGS_C +
        +
      • General Holdings: Completeness Designator
        • +
      +
      • +
    • HINGS_PF +
        +
      • Physical Form Designators
        • +
      +
      • +
    • HINGS_RD +
        +
      • General Holdings: Retention Designator :: This data element specifies the retention policy for the unit at the time of the holdings report.
        • +
      +
      • +
    • HINGS_UT +
        +
      • General Holdings: Type of Unit Designator
        • +
      +
      • +
    • LOC +
        +
      • Shelving location (usually appears when adding or editing an item)
        • +
      +
      • +
    • LOST +
        +
      • Descriptions for the items marked as lost (appears when adding or editing an item)
        • +
      • Values given to lost statuses should be numeric and not alphabetical in order for statuses to appear properly
        • +
      +
      • +
    • MANUAL_INV +
        +
      • Values for manual invoicing types
        • +
      +
      • +
    • NOT_LOAN +
        +
      • Reasons why a title is not for loan
        • +
      +
      • +
    • PROC +
        +
      • The location to be used for NewItemsDefaultLocation (change description as desired), also the location expected by InProcessingToShelvingCart.
        • +
      +
      • +
    • RESTRICTED +
        +
      • Restricted status of an item
        • +
      +
      • +
    • SUGGEST +
        +
      • List of patron suggestion reject or accept reasons (appears when managing suggestions)
        • +
      +
      • +
    • WITHDRAWN +
        +
      • Description of a withdrawn item (appears when adding or editing an item)
        • +
      +
      • +
    + +

    Add new Authorized Value Category

    + +

    In addition to the existing categories that come by default with Koha, librarians can add their own authorized value categories to control data that is entered into the system. To add a new category:

    + +
      +
    • Click 'New Category'
      • +
    • Limit your Category to 11 characters (something short to make it clear what the category is for)
      • +
    • When adding a new category you're asked to create at least one authorized value +
        +
      • Enter a code for your Authorized Value into the 'Authorized value' field
        • +
      • Use the Description field for the actual value that will be entered
        • +
      +
      • +
    • Click 'Save'
      • +
    • Your new category and value will appear on the list of Authorized Values
      • +
    + +

    Add new Authorized Value

    + +

    New authorized values can be added to any existing or new category. To add a value:

    + +
      +
    • Click 'New authorized value for ...'
      • +
    • Enter a code for your Authorized Value into the 'Authorized value' field
      • +
    • Use the Description field for the actual value that will be entered
      • +
    • Click 'Save'
      • +
    • The new value will appear in the list along with existing values
      • +
    -


     -
      -
    • To add a new category, click 'New Category'
      • -
    • Fill in the 'Category', 'Authorized value' and 'Description' fields
      -
        -
      • - -IMPORTANT: The category name must be 8 characters or less. Also, just input one authorized value for the category. You can edit and add more after you save the category.
        • -
      • -
    • Click 'Save'
      • -
    • You've added a new category and can immediately start adding more authorized values to that category by clicking "New authorized value for..."
      • -
    \ No newline at end of file diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/authtypes.tmpl b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/authtypes.tmpl index 1ac50a6ea1..c28ee3f291 100644 --- a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/authtypes.tmpl +++ b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/authtypes.tmpl @@ -2,42 +2,8 @@

    Authority types

    -

    You can define as many Authority types as you want.

    -
      -
    • with the MARC structure button, you can define the MARC structure of a given authority type
      • -
    • The tag reported must contain a MARC tag number. Every subfield in the selected tag will be copied to the "destination tag" in the biblio. for example, in UNIMARC, the tag 200 ot personal authority will be reported to 600, 700, 701, depending on what is cliqued in the biblio MARC editor.
      • -
    • The summary contains an "ISBD" like description to explain how the entry must be shown in the result list. The syntax is : -
        -
      • [xxxFFFSyyy] where are up to 3 digits BEFORE the field, FFF the field number, S the subfield code, yyy up to 3 digits AFTER the field.
        • -
      • things outside [] are kept as is (including HTML)
        • -
      • repeatable fields are managed. -
          -
        • -

        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)

        -
      • -
    -

    Create Authority Types

    +

    Authority Types are basically MARC Frameworks for Authority records and because of that the rules below refer to the bibliographic frameworks.

    -

    Create and manage Authorities frameworks that define the characteristics of your MARC Records (field and subfield definitions). -To create a new framework...

    +

    Koha comes with many of the necessary Authority frameworks already installed.

    -
      -
    • Go to the 'Administration' module.
      • -
    • Select 'Authority types'
      • -
    • Click 'New Authority Framework'
      • -
    • Fill in the fields that describe your new authority type
      -
        -
      • - -TIP: In the 'Authority field to copy', enter the authority field that should be copied from the authority record to the bibliographic record. e.g., in MARC21, field 100 in the authority record should be copied to field 100 in the bibliographic record
        • -
      • -
    • Click 'Submit'
      • -
    • To update the MARC Framework for your new authority type, click 'MARC structure' next to the authority
      • -
    • From the following screen you can alter fields, subfields and add additional tags
      • -
    • By clicking on the 'edit' link you will be able to alter information related to the field
      • -
    • By clicking the 'subfields' link you will be able to alter all of the subfields associated with that field
      • -
    • By clicking 'Edit subfields' at the bottom of the screen you can alter the information for each subfield
      • -
    • After making your changes, click 'Save Changes' at the top of the screen
      • -
    • To delete a subfield, just click the 'delete' link next to the field you'd like to edit
      • -
    \ No newline at end of file + \ No newline at end of file diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/biblio_framework.tmpl b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/biblio_framework.tmpl index 0623905986..6f81db790d 100644 --- a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/biblio_framework.tmpl +++ b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/biblio_framework.tmpl @@ -1,9 +1,37 @@ -

    Biblio framework

    +

    MARC Bibliographic Frameworks

    -

    biblio frameworks are used to catalog 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

    +

    Think of Frameworks as templates for creating new bibliographic records. Koha comes with some predefined frameworks that can be edited or deleted, and librarians can create their own frameworks for content specific to their libraries.

    + +

    Do not delete or edit the Default Framework since this will cause problems with your cataloging records - always create a new template based on the Default Framework, or alter the other Frameworks.

    + +

    After clicking the 'MARC structure' link to the right of each framework you can decide how many fields you want to see on one screen by using the pagination options at the top of the table.

    + +

    Add New Framework

    + +

    To add a new framework

    + +
      +
    • Click 'New Framework' +
        +
      • Enter a code of 4 or fewer characters
        • +
      • Use the Description field to enter a more detailed definition of your framework
        • +
      +
      • +
    • Click 'Submit'
      • +
    • Once your Framework is added click 'MARC structure' to the right of it on the list of Frameworks +
        +
      • You will be asked to choose a Framework to base your new Framework off of, this will make it easier than starting from scratch
        • +
      +
      • +
    • Once your Framework appears on the screen you can edit or delete each field by following the instructions for editing subfields
      • +
    + +

    Edit Existing Frameworks

    + +

    Clicking 'Edit' to the right of a Framework will only allow you to edit the Description for the Framework

    + +

    To make edits to the fields associated with the Framework you must first click 'MARC Structure' and then follow the instructions for editing subfields

    \ No newline at end of file diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/branch_transfer_limits.tmpl b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/branch_transfer_limits.tmpl index d3e8555174..2b5a612065 100644 --- a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/branch_transfer_limits.tmpl +++ b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/branch_transfer_limits.tmpl @@ -1,28 +1,19 @@ +

    Library Transfer Limits

    -

    -Limit the ability to transfer items between libraries based on the -library sending, the library receiving, and the item type involved.

    - -

    IMPORTANT: These rules only go into effect if the preference UseBranchTransferLimits is set to ON.

    - -
      -
    • - Get there: More > Administration > General System Preferences > Circulation > UseBranchTransferLimits
      • -
    -

    Setting Limits
    -

    -
      -
    • Click 'Library Transfer Limits' -
      • -
    • Check the boxes for the items that should not be transferable -
        -
      • TIP: - If you accidentally click all the items that can be transferred, you - can click the 'Swap All' button to change your selection
        • -
      -
      • -
    • To prevent all transfers, click 'Check All'
      • -
    • If you need to restart you can click 'Uncheck All'
      • -
    + +

    Limit the ability to transfer items between libraries based on the library sending, the library receiving, and the collection code involved.

    + +

    These rules only go into effect if the preference UseBranchTransferLimits is set to 'enforce'.

    + +

    Before you begin you will want to choose which library you are setting these limits for.

    + +

    Transfer limits are set based on the collections codes you have applied via the Authorized Value administration area.

    + +

    Collection codes will appear as tabs above the checkboxes.

    + +

    Check the boxes for the libraries that you accept checkins from for the item type you have selected at the top.

    + +

    In the above example, Centerville library will allow patrons to return items from all libraries except Liberty and Franklin to their branch.

    + \ No newline at end of file diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/branches.tmpl b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/branches.tmpl index 2735178142..de30ed80f3 100644 --- a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/branches.tmpl +++ b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/branches.tmpl @@ -1,59 +1,50 @@ -

    Libraries and Groups

    +

    Libraries & Groups

    -
      -
    • Click on 'Libraries and groups'
      • - -
        -
      • TIP: The terms 'Library' and 'Branch' are interchangeable in Koha.
        • -
      - -
    • You can click the 'Edit' link, next to each library, to make changes.
      • -
    -

    Add a new Group

    - -What is Group(s) and why would I want to use it?
    -     -

    -A single branch library does not need to utilize the Group(s) feature. -

    -

    -Group(s) are used to divide your library system into categories. If, for example, you have -one main library and several branch libraries, you might set up an "M" -(Main) group and a "B" (Branch) group, with descriptions "Main -Library" and "Branch Libraries." Another example is a library system -which is divided into regions. You can create the "North Region" group, -which contains libraries A, B, and C and the "South Region" group, which -contains libraries D, E, and F. -

    -

    TIP: Start by adding your Groups/Categories (if you have any) before adding Libraries. -

    -
      -
    • To add a new group click 'New Group' -
        -
      • IMPORTANT: Right now category type is still in development.
        • -
      -
      • -
    • Enter the group information
      • -
    +

    When setting up your Koha system you will want to add information for every library that will be sharing your system. This data is used in several areas of Koha.

    + +

    When visiting this page you are presented with a list of the libraries and groups that have already been added to the system.

    + +

    Adding a Library

    + +

    To add a new library:

    -

    Add a new Library/Branch
    -

      -
    • To add a new library or branch click 'New Library' -
      • -
    • Enter the Library Code -
        -
      • TIP: 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.
        • -
      -
      • -
    +
  • Click 'New Library'
    • +
  • Fill in the data requested on the form that follows
      -
    • Enter all other information related to the library
      • -
    • Click 'Submit'
      • -
    • Your library will now be added to the list -
      • +
    • Of the fields listed, only 'Library code' and 'Name' are required
      • +
    • Be sure to enter a library email address to make sure that notices are sent to and from the right address
      • +
    • An IP address is required if you have enabled AutoLocation
      • +
    +
+ +

Editing/Deleting a Library

+ +

You will be unable to delete any library that has patrons or items attached to it.

+ +

Each library will have an 'Edit' link to the right of it. Click this link to edit/alter details associated with the library in question.

+ +

You will be unable to edit the 'Library code'

+ +

Adding a group

+ +

To add a Search Domain or Library Property Group click the 'New Group' button at the top of the screen.

+ +

Of the fields on the group form, 'Category code' and 'Name' are the only required fields

+ +

Search Domain Groups

+ +

Search Domain Groups allow you to search a group of libraries at the same time instead of searching just one library or all libraries.

+ +

To see Search Domain Groups in action visit the staff client advanced search page in your Koha system

+ +

Library Property Groups

+ +

You can assign specific categories to your libraries by adding groups for them.

+ +

Properties are then applied to libraries via the add or edit library form.

+ + \ No newline at end of file diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/categorie.tmpl b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/categorie.tmpl index 3acbc24f16..7fc3f5d3d9 100644 --- a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/categorie.tmpl +++ b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/categorie.tmpl @@ -2,32 +2,79 @@

Patron Categories

-

This is where you define the types of users of your library and how they will be handled.

- -

Categories, Descriptions and Types

-

Start by assigning a Category Code and a Description to each patron category. Each Category can be one of five types:

-
    -
  • Adult Patrons: can be linked as "guarantors" to other patrons who are their dependents. This is the default patron type.
    • -
  • Child Patrons: a patron category that has a "guarantor".
    • -
  • Organizational Patrons: can be used for institutional members, e.g. other libraries that borrow from you, in which case Koha expects slightly different information about the institution.
    • -
  • Professional Patrons: can also be associated with a guarantor (usually an organization).
    • -
  • Staff Members: A member of the library staff.
    • -
  • Statistical Patrons: checking out to this patron type creates a statistical (local use) record but does not actually circulate materials.
    • -
- -

Note on Permissions

-

Patrons in any category type may be assigned permissions in the staff interface. The Staff patron type has additional security features over the other types.

- -

Enrollment Period (months)

-

Enrollment period is a number indicating the length in months of a patron enrollment. If enrollments never expire, set this to an impossibly high number ( >= 99).

- -

Upper Age Limit and Age Required

-

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 999 (the highest allowed).

- -

Enrollment Fee and Reserve Fee

-

Enrollment Fee and Reserve Fee (if any) should be entered either as whole numbers or with (up to) six decimal places, with no currency notation (e.g. "1.250000" instead of "$1.25").

- -

Overdue Notice Required

-

Overdue Notice Required lets you bypass generating overdue notices for this user type.

+

Patron categories allow you to organize your patrons into different roles, age groups, and patron types.

+ +

Patrons are assigned to one of six main categories:

+ +
    +
  • Adult +
      +
    • Most common patron type, usually used for a general 'Patron' category.
      • +
    +
    • +
  • Child +
      +
    • Children patrons can have a guardian to be attached to them.
      • +
    +
    • +
  • Staff +
      +
    • Patrons within the staff category will have access to the staff client.
      • +
    +
    • +
  • Organizational +
      +
    • Organizational patrons are organizations. Organizations can be used as guarantors for Professional patrons.
      • +
    +
    • +
  • Professional +
      +
    • Professional patrons can be linked to Organizational patrons
      • +
    +
    • +
  • Statistical +
      +
    • This patron type is used strictly for statistical purposes, such as in house use of items.
      • +
    +
    • +
+ +

Adding a patron category

+ +

To add a new patron category click 'New Category' at the top of the page

+ +
    +
  • The 'Category Code' is an identifier for your new code. +
      +
    • Important: The category code is limited to 10 characters (numbers and letters)
      • +
    +
    • +
  • Enter a plain text version of the category in the 'Description' field.
    • +
  • Enrollment period (in months) should be filled in if you have a limited enrollment period for your patrons (eg. Student cards expire after 9 months or until a specific date) +
      +
    • Important: You cannot enter both a month limit and a date until. Choose to enter either one or the other.
      • +
    +
    • +
  • Some patron categories can have a minimum age (in years) requirement associated with them, enter this age in the 'Age required'
    • +
  • Patron categories can also have a maximum age (in years) associated with them (such as children), enter this age in the 'Upperage limit'
    • +
  • If you charge a membership fee for your patrons (such as those who live in another region) you can enter that in the 'Enrollment fee' field. +
      +
    • Important: Only enter numbers and decimals in this field
      • +
    +
    • +
  • If you want your patron to receive overdue notices, set the 'Overdue notice required' to 'Yes'
    • +
  • If you charge patrons for placing holds on items, enter the fee amount in the 'Hold fee' field. +
      +
    • Important: Only enter numbers and decimals in this field
      • +
    +
    • +
  • In the 'Category type' field choose one of the six main parent categories
    • +
  • Finally you can assign advanced messaging preferences by default to a patron category +
      +
    • Important: Requires that you have EnhancedMessagingPreferences enabled
      • +
    • Important: These can be changed for individual patrons, this setting is just a default to make it easier to set up messages for an entire category
      • +
    +
    • +
\ No newline at end of file diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/checkmarc.tmpl b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/checkmarc.tmpl index fb4376d75e..3bed7ff4b4 100644 --- a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/checkmarc.tmpl +++ b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/checkmarc.tmpl @@ -2,7 +2,8 @@

MARC Bibliographic Framework Test

-

Once you have completed the process of setting up your MARC Frameworks and checked your MARC to Koha mapping, this program checks for major errors in your MARC setup.

+

This tool checks the MARC structure in your frameworks.

+ +

If you change your MARC Bibliographic framework it's recommended that you run this tool to test for errors in your definition.

-

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 the MARC Bibliographic Framework Test after every revision.

\ No newline at end of file diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/cities.tmpl b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/cities.tmpl index 3f6fb1c16f..67880b002f 100644 --- a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/cities.tmpl +++ b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/cities.tmpl @@ -2,18 +2,20 @@

Cities and Towns

-

This parameter helps you define the cities and towns that your patrons live in. These will appear as a pull down on the patron add screen to make it easier for entering of consistent data.

-

Add a new city

-
    -
  • - Click 'New City'
    • -
  • - Enter the city or town name and the zipcode
    • -
  • - Click 'Submit'
    • -
  • - You can edit/delete your cities and towns from the main 'Cities and towns' page
    • -
  • - These fields will then appear when adding/editing a patron as a pull down to make it easier to enter data
    • -
- \ No newline at end of file +

To standardize patron input you can define cities or towns within your region so that when new patrons are added librarians simply have to select the town from a list instead of having to type the town and zip (or postal) code information.

+ +

Adding a City

+ +

To add a new city, click the 'New City' button at the top of the page and enter the city name, state and zip/postal code.

+ +

One you click Submit, your city will be saved and will be listed on the Cities and Towns page.

+ +

Cities can be edited or deleted at any time.

+ +

Viewing Cities on Patron Add Form

+ +

If you have defined local cities using the New city form, then when adding or editing a patron record you will see those cities in a pull down menu to make city selection easy.

+ +

This will allow for easy entry of local cities into the patron record without risking the potential for typos or mistaken zip/postal codes.

+ + \ No newline at end of file diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/classsources.tmpl b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/classsources.tmpl index 611476cbbc..fa5f914a9b 100644 --- a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/classsources.tmpl +++ b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/classsources.tmpl @@ -1,38 +1,56 @@ -

About Classification Sources

- -

Define classification sources (i.e., call number schemes) used by your collection. You can also define 'filing rules' used for sorting call numbers.

- -

IMPORTANT: You do not have the option to 'define' a new filing rule. Currently, the filing rules and sorting routines are statically defined with options available in the dropdown menu when creating or editing a 'classification source' or 'filing rule'.

- -

TIP: In the future, this features will be expanded to allow new filing rules to be created (defined) on the fly. In other words, in addition to choosing from a static sorting routine or filing rule, you will be able to actually to define new ones.

- -

To add a new 'Classification Source'...

-
    -
  • Click 'New Classification Source'
    • -
  • Enter a 'Classification source code'
    • -
  • Enter a 'Description' for your new classification source
    • -
  • Note if the classification source is in use (check the box for 'yes' and leave unchecked for 'no')
    • -
  • Choose a 'filing rule' from the dropdown menu to associate with your new classification source
    • -
  • Click 'Save'
    • -
-

IMPORTANT: 'Source in use?' controls whether source is available in item editor. For example, Koha ships with Dewey and LCC rules but a Dewey library may not want catalogers to mistakenly use LCC as an item callnumber type. To accomplish this, check box 'source in use?' only for the Dewey Classification Source and leave 'source in use' for all others unchecked.

- -

To add a new 'Filing Rule'...

-
    -
  • Click 'New Filing Rules'
    • -
  • Enter a 'Filing Rule Code'
    • -
  • Enter a 'Description' for your new filing rule
    • -
  • Choose a 'filing routine' from the dropdown menu to associate with your new filing rule
    • -
  • Click 'Save'
    • -
- -

To edit a new 'Classification Source' or 'Filing Rule'...

-
    -
  • Click 'edit' next to the 'classification source' or 'filing rule' you wish to edit
    • -
  • Edit
    • -
  • Click 'Save'
    • -
+

Classification Sources

+ +

Source of classification or shelving scheme is an Authorized Values category that is mapped to field 942$2 in Koha's MARC Bibliographic frameworks.

+ +

Commonly used values of this field are:

+ +
    +
  • ddc - Dewey Decimal Classification
    • +
  • lcc - Library of Congress Classification
    • +
+ +

If you chose to install classification sources during Koha's installation, you would see other values too:

+ +
    +
  • ANSCR (sound recordings)
    • +
  • SuDOC classification
    • +
  • Universal Decimal Classification
    • +
  • Other/Generic Classification
    • +
+ +

Adding/Editing Classification Sources

+ +

You can add your own source of classification by using the New Classification Source button. To edit use the Edit link.

+ +

When creating or editing:

+ +
    +
  • You will need to enter a code and a description.
    • +
  • Check the 'Source in use?' checkbox if you want the value to appear in the drop down list for this category.
    • +
  • Select the appropriate filing rule from the drop down list.
    • +
+ +

Classification Filing Rules

+ +

Filing rules determine the order in which items are placed on shelves.

+ +

Values that are pre-configured in Koha are:

+ +
    +
  • Dewey
    • +
  • LCC
    • +
  • Generic
    • +
+ +

Filing rules are mapped to Classification sources. You can setup new filing rules by using the New Filing Rule button. To edit use the Edit link.

+ +

When creating or editing:

+ +
    +
  • Enter a code and a description
    • +
  • Choose an appropriate filing routine - dewey, generic or lcc
    • +
\ No newline at end of file diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/currency.tmpl b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/currency.tmpl index 21eca0a08b..e5c3bdcf35 100644 --- a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/currency.tmpl +++ b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/currency.tmpl @@ -1,9 +1,11 @@ -

Currencies administration

+

Currencies and Exchange Rates

-

Define the currencies you deal with here.

+

If you place orders from more than one country you will want to input currency exchange rates so that your acquisitions module will properly calculate totals.

-

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.

+

Tip: This data is not automatically updated, so be sure to keep it up to date so that your accounting is kept correct.

+ +

The active currency is the main currency you use in your library. Your active currency will have a check mark in the 'Active' column. If you don't have an active currency you will see an error message telling you to choose an active currency.

\ No newline at end of file diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/fieldmapping.tmpl b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/fieldmapping.tmpl index 91cd13317a..6422e2d0f3 100644 --- a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/fieldmapping.tmpl +++ b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/fieldmapping.tmpl @@ -2,18 +2,22 @@

Keyword to MARC Mapping

-

This tool will allow you to map MARC fields to a set of predefined keywords.

+

This tool will allow you to map MARC fields to a set of predefined keywords.

-

At this time the only keyword in use is 'subtitle.'

+

At this time the only keyword in use is 'subtitle.'

-

Using this tool you can define what MARC field prints to the detail screen of the bibliographic record using keywords. The following example will use the subtitle field.

+

Using this tool you can define what MARC field prints to the detail screen of the bibliographic record using keywords. The following example will use the subtitle field.

-

Using the Framework pull down menu, choose the Framework you would like to apply this rule to. For example, the subtitle for books can be found in the 245$b field.

+

Using the Framework pull down menu, choose the Framework you would like to apply this rule to. For example, the subtitle for books can be found in the 245$b field.

However the subtitle for DVDs appears in 245$p

Using this tool you can tell Koha to print the right field as the subtitle when viewing the bibliographic record in the OPAC.

+

This tool can be used to chain together pieces of the record as well. If you want the series number to show in the title on your search results you simply have to map 490 $v to 'subtitle' along with the 245 $b.

+ +

Tip: Chain together the fields you want to show after the item title in the order in which you want them to appear.

+

Future developments will include additional keyword assigned fields.

\ No newline at end of file diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/item_circulation_alerts.tmpl b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/item_circulation_alerts.tmpl index f7b289fb22..8c8eb67931 100644 --- a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/item_circulation_alerts.tmpl +++ b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/item_circulation_alerts.tmpl @@ -1,36 +1,22 @@ +

Item Circulation Alerts

-

-This matrix is to be used to define rules for check-in and checkout -notifications for combinations of libraries, patron categories, and -item types -

+

Libraries can decide if they want to have patrons automatically notified of circulation events (check ins and check outs).

+ +

These preferences are set based on patron types and item types.

+ +

Important: These preference can be overwritten by changes in the individual patron's messaging preferences.

+ +

To set up circulation alerts:

+ +
    +
  • Choose your library from the pull down at the top of the screen
      -
    • - Click on 'Item Circulation Alerts' 
      • -
    • You will be presented with the option of choosing a branch or applying rules to all branches ('Default') -
      • -
    • Clicking on the squares in the matrix will change the color and also the email alert rules -
      • -
    • To set whether patrons receive alerts for checking books out, click the squares in the 'Check out' matrix -
        -
      • TIP: If you have the library select box set to 'Default' the matrix will apply to all libraries.
        • -
      -
      • -
    • To set whether patrons receive alerts for checking books in, click the squares in the 'Check in' matrix -
        -
      • TIP: - If you have the library select box set to a specific branch the matrix - will apply just to that branch, showing the branch code in the message. - -
        • -
      -
      • +
    • To set preferences for all libraries, keep the menu set to 'Default'
      • +
    +
    • +
  • By default all item types and all patrons are notified of check ins and check outs. To change this, click on the item/patron type combo that you would like to stop notices for.
-

Can I customize the email sent to my patrons?

-

-Yes, just go to Tools > Notices and edit the Check In and Check Out notices. -

\ No newline at end of file diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/itemtypes.tmpl b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/itemtypes.tmpl index 177e505be6..c47e696168 100644 --- a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/itemtypes.tmpl +++ b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/itemtypes.tmpl @@ -1,41 +1,60 @@ -

Item types management

- -

You can define as many item types 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" indicates 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 :

-
    -
  • Patrons can search on item types
    • -
  • Issuing rules are set for item types (and for patron types / libraries)
    • -
-

Setting up item types is one of the first things you should do after installing the Koha software.

- -

Adding & Editing New Item Types

-
    -
  • Your system will come with some predefined item types. From this screen you can edit or delete these items
    • -
  • To add a new item type click 'New Item Type'
    • -
  • Enter a short code for the 'Item Type'
    • -
  • Enter a longer explanation in the 'Description'
    • -
  • Feel free to choose an image for each item type (or selected the 'No image' option)
    • -
  • The 'Not for loan' option can be used for items that cannot be checked out of the library
    • -
  • 'Renewals' should include the number of times this item can be renewed
    • -
  • If you charge a rental fee for items (such as DVDs) enter that amount in the 'Rental charge' field
    • -
  • The summary field is used to edit the way this item displays on the search results page -
      -
    • - -TIP: For electronic resources you might want to enter - -<a href="[856u]">open site</a> - -to show the item link on the search results page
      • -
    • -
  • When you're finished click 'Save Changes'
    • -
-

Can I have a different type for new releases and older titles? -Yes. Just enter an item type for new items and assign different circulation rules for this item type. -

\ No newline at end of file +

Item Types

+ +

Koha allows you to organize your collection by item types and collection codes.

+ +

Item types typically refer to the material type (book, cd, dvd, etc), but can be used in any way that works for your library.

+ +

Adding Item Types

+ +

To add a new item type, simply click the 'New Item Type' button at the top of the Item Types page.

+ +
    +
  • In the 'Item Type' field, enter a short code for your item type
    • +
  • The description is the plain text definition of the item type
    • +
  • You can choose to have an image associated with your item type +
      +
    • You can choose from a series of image collections
      • +
    • You can link to a remote image
      • +
    • Or you can just have no image associated with the item type
      • +
    • Important: To have your item type images appear in the OPAC you need to set noItemTypeImages to 'Show' +
        +
      • Get there: More > Administration > Global System Preferences > Admin
        • +
      +
      • +
    +
    • +
  • For items that do not circulate, check the 'Not for loan' options +
      +
    • Items marked 'Not for loan' will appear in the catalog, but cannot be checked out to patrons
      • +
    +
    • +
  • Enter the total number of renewals allowed for the item type in the 'Renewals' box
    • +
  • For items that you charge a rental fee for, enter the total fee you charge in the 'Rental charge' field +
      +
    • Important: Do not enter symbols in this field, only numbers and decimal points (ex. $5.00 should be entered as 5 or 5.00)
      • +
    • This will charge the patron on checkout
      • +
    +
    • +
  • When finished, click 'Save Changes' +
      +
    • Tip: All fields, with the exception of the 'Item Type' will be editable from the Item Types list
      • +
    +
    • +
  • Your new item type will now appear on the list
    • +
+ +

Editing Item Types

+ +

Each item type has an Edit button beside it. To edit an item simply click the 'Edit' link.

+ +

You will not be able to edit the code you assigned as the 'Item Type' but you will be able to edit the description for the item.

+ +

Deleting Item Types

+ +

Each item has a Delete button beside it. To delete an item, simply click the 'Delete' link.

+ +

You will not be able to delete item types that are being used by items within your system.

+ + \ No newline at end of file diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/koha2marclinks.tmpl b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/koha2marclinks.tmpl index 80cf6c7e8e..e661b0fa6e 100644 --- a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/koha2marclinks.tmpl +++ b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/koha2marclinks.tmpl @@ -1,15 +1,15 @@ -

Koha 2 MARC links

+

Koha to MARC Mapping

-

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.

+

While Koha stores the entire MARC record, it also stores common fields for easy access in various tables in the database. Koha to MARC Mapping is used to tell Koha where to find these values in the MARC record. In many cases you will not have to change the default values set by in this tool on installation, but it is important to know that the tool is here and can be used at any time.

-

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.

+

The Koha to MARC Mapping page offers you the option of choosing from one of three tables in the database to assign values to.

-

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.

+

After choosing the table you would like to view, click 'OK.' To edit any mapping click on the 'Koha Filed' or the 'Edit' link.

-

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.

+

Choose which MARC field you would like to map to this Koha Field and click the 'OK' button. If you would like to clear all mappings, click the 'Click to "Unmap"' button.

-

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.

+

Important: At this time you can map only 1 MARC field to 1 Koha field. This means that you won't be able to map both the 100a and the 700a to the author field, you need to choose one or the other.

\ No newline at end of file diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/marc_subfields_structure.tmpl b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/marc_subfields_structure.tmpl index 68d09bcbcb..46ba4142ee 100644 --- a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/marc_subfields_structure.tmpl +++ b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/marc_subfields_structure.tmpl @@ -1,57 +1,140 @@ -

MARC tag structure administration

+

MARC Bibliographic Frameworks Subfields

-

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

+

Frameworks are made up of MARC fields and subfields. To make edits to most Frameworks you must edit the fields and subfields. Clicking 'Edit' to the right of each subfield will allow you to make changes to the text associated with the field

-

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 :

-
    -
  • repeatable : whether it can be repeated or not. If it can be repeated, separate the values by a | in the MARC editor when you want to have the subfield twice
    • -
  • Mandatory : whether the field is mandatory or not. If mandatory, the cataloger can't validate the biblio if the subfield is empty.
    • -
  • Search also : a list of field that Koha will also search on when the user do a search on the subfield
    • -
  • Koha link : very important. 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).
    • -
  • Text for librarian : what appears before the subfield in the librarian interface
    • -
  • Text for OPAC : what appears before the field in the OPAC. If empty, the text for librarian is used instead
    • -
  • 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 !!!
    • -
  • hidden : allows you to select from 19 possible visibility conditions, 17 of which are implemented. They are the following:
    • -
    -( ! means 'not visible' or in the case of Collapsed 'not -Collapsed') -

    - -9 => Future use
    - -8 => Flag
    - -7 => OPAC !Intranet !Editor Collapsed
    - -6 => OPAC Intranet !Editor !Collapsed
    - -5 => OPAC Intranet !Editor Collapsed
    - -4 => OPAC !Intranet !Editor !Collapsed
    - -3 => OPAC !Intranet Editor Collapsed
    - -2 => OPAC !Intranet Editor !Collapsed
    - -1 => OPAC Intranet Editor Collapsed
    - 0 => OPAC Intranet Editor !Collapsed
    - 1 => !OPAC Intranet Editor Collapsed
    - 2 => !OPAC !Intranet Editor !Collapsed
    - 3 => !OPAC !Intranet Editor Collapsed
    - 4 => !OPAC Intranet Editor !Collapsed
    - 5 => !OPAC !Intranet !Editor Collapsed
    - 6 => !OPAC Intranet !Editor !Collapsed
    - 7 => !OPAC Intranet !Editor Collapsed
    - 8 => !OPAC !Intranet !Editor !Collapsed
    - 9 => Future use
    -     -
  • URL : if checked, the subfield is an URL, and can be clicked
    • -
  • Auth value : means the value is not free, but in the authorized value list of the selected type
    • -
  • thesaurus : means that the value is not free, but can be searched in authority/thesaurus of the selected category
    • -
  • 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)
    • -
  • link : If you enter a field/subfield here (200b), a link appears after the subfield in the MARC Details view. This view is present only in intranet, not in Opac. If the librarian click on the link, a search  is done on the DB for the field/subfield with the same value. Can be used for 2 main topic : -
      -
    • on a field like author (200f in UNIMARC), put 200f here, you will be able to see all biblios with the same author.
      • -
    • on a field that is a link (4xx) to reach another biblio. For example, put 011a in 464$x, will find the serials that are with this issn.
      • -
    +
      +
    • Each field has a tag (which is the MARC tag) +
        +
      • The 'Label for lib' is what will show in the staff client if you have advancedMARCeditor set to display labels
        • +
      • The 'Label for OPAC' is what will show on the MARC view in the OPAC
        • +
      • If you check 'Repeatable' then the field will have a plus sign next to it allowing you to add multiples of that tag
        • +
      • If you check 'Mandatory' the record will not be allowed to save unless you have a value assigned to this tag
        • +
      • 'Authorized value' is where you define an authorized value that your catalogers can choose from a pull down to fill this field in +To edit the subfields associated with the tag, click 'Subfields' to the right of the tag on the 'MARC Structure' listing
        • +
      +
      • +
    • From the list of subfields you can click 'Delete' to the right of each to delete the subfields
      • +
    • To edit the subfields click 'Edit Subfields'
      • +
    • For each subfield you can set the following values +
        +
      • Text for librarian +
          +
        • what appears before the subfield in the librarian interface
          • +
        +
        • +
      • Text for OPAC +
          +
        • what appears before the field in the OPAC.
          • +
        • If left empty, the text for librarian is used instead
          • +
        +
        • +
      • Repeatable +
          +
        • the field will have a plus sign next to it allowing you to add multiples of that tag
          • +
        +
        • +
      • Mandatory +
          +
        • the record will not be allowed to save unless you have a value assigned to this tag
          • +
        +
        • +
      • Managed in tab +
          +
        • defines the tab where the subfield is shown. All subfields of a given field must be in the same tab or ignored. Ignore means that the subfield is not managed.
          • +
        +
        • +
      +
        +
      • Default value +
          +
        • defines what you want to appear in the field by default, this will be editable, but it saves time if you use the same note over and over or the same value in a field often.
          • +
        +
        • +
      +
        +
      • hidden +
          +
        • allows you to select from 19 possible visibility conditions, 17 of which are implemented. They are the following: +
            +
          • -9 => Future use
            • +
          • -8 => Flag
            • +
          • -7 => OPAC !Intranet !Editor Collapsed
            • +
          • -6 => OPAC Intranet !Editor !Collapsed
            • +
          • -5 => OPAC Intranet !Editor Collapsed
            • +
          • -4 => OPAC !Intranet !Editor !Collapsed
            • +
          • -3 => OPAC !Intranet Editor Collapsed
            • +
          • -2 => OPAC !Intranet Editor !Collapsed
            • +
          • -1 => OPAC Intranet Editor Collapsed
            • +
          • 0 => OPAC Intranet Editor !Collapsed
            • +
          • 1 => !OPAC Intranet Editor Collapsed
            • +
          • 2 => !OPAC !Intranet Editor !Collapsed
            • +
          • 3 => !OPAC !Intranet Editor Collapsed
            • +
          • 4 => !OPAC Intranet Editor !Collapsed
            • +
          • 5 => !OPAC !Intranet !Editor Collapsed
            • +
          • 6 => !OPAC Intranet !Editor !Collapsed
            • +
          • 7 => !OPAC Intranet !Editor Collapsed
            • +
          • 8 => !OPAC !Intranet !Editor !Collapsed
            • +
          • 9 => Future use
            • +
          +
          • +
        • ( ! means 'not visible' or in the case of Collapsed 'not Collapsed')
          • +
        +
        • +
      +
        +
      • Is a URL +
          +
        • if checked, it means that the subfield is a URL and can be clicked
          • +
        +
        • +
      +
        +
      • Link +
          +
        • If you enter a field/subfield here (200b), a link appears after the subfield in the MARC Detail view. This view is present only in the staff client, not the OPAC. If the librarian clicks on the link, a search is done on the database for the field/subfield with the same value. This can be used for 2 main topics : +
            +
          • on a field like author (200f in UNIMARC), put 200f here, you will be able to see all bib records with the same author.
            • +
          • on a field that is a link (4xx) to reach another bib record. For example, put 011a in 464$x, will find the serials that are with this ISSN.
            • +
          +
          • +
        • Important: This value should not change after data has been added to your catalog
          • +
        +
        • +
      +
        +
      • Koha link +
          +
        • 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 its meaning. Koha constantly maintains consistency between a subfield and its 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).
          • +
        +
        • +
      +
        +
      • Authorized value +
          +
        • means the value cannot by typed by the librarian, but must be chosen from a pull down generated by the authorized value list
          • +
        • In the example above, the 504a field will show the MARC504 Authorized Values when cataloging
          • +
        +
        • +
      +
        +
      • Thesaurus +
          +
        • means that the value is not free text, but must be searched in the authority/thesaurus of the selected category
          • +
        +
        • +
      +
        +
      • 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)
          • +
        +
        • +
      • +
    • To save your changes simply click the 'Save Changes' button at the top of the screen
    diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/marctagstructure.tmpl b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/marctagstructure.tmpl index 5ba040d696..506c3c186b 100644 --- a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/marctagstructure.tmpl +++ b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/marctagstructure.tmpl @@ -1,28 +1,24 @@ -

    MARC tag structure administration

    +

    MARC Bibliographic Frameworks Tags

    -

    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

    +

    To add a field to a Framework click the 'New Tag' button at the top of the Framework definition

    -

    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.

    +

    This will open up a blank form for entering MARC field data

    + +

    Enter the information about your new tag:

    -

    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 :

      -
    • repeatable : whether it can be repeated or not. If it can be repeated, separate the values by a | in the MARC editor when you want to have the subfield twice
      • -
    • Mandatory : whether the field is mandatory or not. If mandatory, the cataloger can't validate the biblio if the subfield is empty.
      • -
    • Search also : a list of field that Koha will also search on when the user do a search on the subfield
      • -
    • Koha link : very important. 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).
      • -
    • Text for librarian : what appears before the subfield in the librarian interface
      • -
    • Text for OPAC : what appears before the field in the OPAC. If empty, the text for librarian is used instead
      • -
    • 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 !!!
      • -
    • hidden : means that the field is managed, but NOT shown in opac. It's usually for internal fields
      • -
    • URL : if checked, the subfield is an URL, and can be clicked
      • -
    • Auth value : means the value is not free, but in the authorized value list of the selected type
      • -
    • thesaurus : means that the value is not free, but can be searched in authority/thesaurus of the selected category
      • -
    • 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)
      • -
    • link : useless for instance
      • +
    • The 'Tag' is the MARC field number
      • +
    • The 'Label for lib' is the text that will appear in the staff client when in the cataloging module
      • +
    • The 'Label for OPAC' is the text that will appear in the OPAC when viewing the MARC version of the record
      • +
    • If this field can be repeated, check the 'Repeatable' box
      • +
    • If this field is mandatory, check the 'Mandatory' box
      • +
    • If you want this field to be a pull down with limited possible answers, choose which 'Authorized value' list you want to use
    +

    When you're finished, click 'Save Changes' and you will be presented with your new field

    + +

    To the right of the new field is a link to 'Subfields,' you will need to add subfields before this tag will appear in your MARC editor.

    + \ No newline at end of file diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/matching-rules.tmpl b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/matching-rules.tmpl index 693119ef60..47210d5789 100644 --- a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/matching-rules.tmpl +++ b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/matching-rules.tmpl @@ -1,13 +1,49 @@ -

    Record Matching Rules

    -

    -IMPORTANT: This is an advanced feature and should not be altered without knowing how it will effect data migration.

    +

    Record Matching Rules

    -

    Use this tool to create rules to apply during the data migration process. It will prevent duplicates from coming into the system when importing MARC records. An import rule or matching rule consists of one or more 'match points' and zero or more 'match checks'. Each match point specifies a 'search index' and a MARC 'tag', 'subfield', or 'length' (fixed field position) when a record is imported. For each match point, a string is constructed from the tag specified in the match point and the related index is searched.

    +

    Record matching rules are used when importing MARC records into Koha.

    -

    The set of matching records are assigned a score (the value of which is determined by the match point rule). Then, the rest of the match points are considered and the scores of each set of matches is added up. The set of matching records whose total score is over a threshold value defined in the matching rule are candidate matches.

    +

    The rules that you set up here will be referenced with you Stage MARC Records for Import.

    -

    Match checks are applied for all candidate matches. Each match check specifies a tag in the incoming record and a tag in the possible matching record. The values must be the same for a match to be considered good (e.g., doing a match check on title, or publication date).

    +

    To create a new matching rule:

    - \ No newline at end of file +
      +
    • Click 'New Record Matching Rule' +
        +
      • Choose a unique name and enter it in the 'Matching rule code' field
        • +
      • 'Description' can be anything you want to make it clear to you what rule you're picking
        • +
      • 'Match threshold' - The total number of 'points' a biblio must earn to be considered a 'match'
        • +
      • Match points are set up to determine what fields to match on
        • +
      • 'Search index' can be found by looking at the ccl.properties file on your system which tells the zebra indexing what data to search for in the MARC data".
        • +
      • 'Score' - The number of 'points' a match on this field is worth. If the sum of each score is greater than the match threshold, the incoming record is a match to the existing record
        • +
      • Enter the MARC tag you want to match on in the 'Tag' field
        • +
      • Enter the MARC tag subfield you want to match on in the 'Subfields' field
        • +
      • 'Offset' - For use with control fields, 001-009
        • +
      • 'Length' - For use with control fields, 001-009
        • +
      • Koha only has one 'Normalization rule' that removes extra characters such as commas and semicolons. The value you enter in this field is irrelevant to the normalization process.
        • +
      • 'Required match checks' - ??
        • +
      +
      • +
    + +

    Sample Record Matching Rule: Control Number

    + +
      +
    • Match threshold: 100
      • +
    • Matchpoints (just the one):
      • +
    • Search index: Control-number
      • +
    • Score: 101
      • +
    • Tag: 001 +
        +
      • this field is for the control number assigned by the organization creating, using, or distributing the record
        • +
      +
      • +
    • Subfields: a
      • +
    • Offset: 0
      • +
    • Length: 0
      • +
    • Normalization rule: Control-number
      • +
    • Required Match checks: none (remove the blank one)
      • +
    + + diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/patron-attr-types.tmpl b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/patron-attr-types.tmpl index a8d7306592..27112e2624 100644 --- a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/patron-attr-types.tmpl +++ b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/patron-attr-types.tmpl @@ -1,33 +1,59 @@ -

    Patron attribute types

    A patron attribute (or extended patron attribute) is an additional piece of information associated with a patron record. Each attribute has a type that specifies whether the attribute is repeatable, can serve as a unique identifier, can take a password, and whether it can be used to search for patron records in the staff interface. -The list of attribute types is controlled by staff with 'superlibrarian' permissions.
    -
      -
    • Get there: Patrons > Patron Record > More > Set Permissions
      • -
    Once an attribute type is defined, values for that attribute can be added to the patron record via the staff interface or the batch patron import. -Two uses of extended attributes are: - -
      -
    • defining additional unique identifiers, such as a campus student ID number, a library staff HR number, and so on. These IDs can be used for searching or matching and overlaying records during a batch import.
      • -
    • additional statistical categories. For example, a library could define an attribute type for tracking the academic major of a student patron. Any number of attributes of this sort could be defined.
      • -
    The extended attributes feature is completely optional. If the 'ExtendPatronAttributes' system preference is OFF, customizable patron attributes will not be usable. -

    Add Patron Attribute

    -
      -
    • Click 'Patron attribute types'
      • -
    • - IMPORTANT: You will need to have ExtendedPatronAttributes turned on -
        -
      • Get there: More > Administration > General system preferences > Patrons > ExtendedPatronAttributes
        • -
      • -
    • To add a new Patron Attribute, click 'New Patron Attribute Type'
      • -
    • The 'Patron attribute type code' should be unique and is the only required field -
        -
      • TIP: This field is not editable once it is set
        • -
      • -
    • Fill in all of the fields you need for your attribute -
        -
      • TIP: The repeatibility and unique_id settings of an attribute type cannot be changed after creation - this is to avoid having to deal with changing constraints if an attribute type is already in use by patron records
        • -
      • -
    • Click 'Save'
      • -
    • TIP: An attribute type cannot be deleted if it is used by any patron records
      • -
    \ No newline at end of file +

    Patron Attribute Types

    + +

    Patron attributes can be used to define custom fields to associate with your patron records. In order to enable the use of custom fields you need to set the ExtendedPatronAttributes system preference.

    + +

    A common use for this field would be for a student ID number or a Driver's license number.

    + +

    Adding Patron Attributes

    + +

    To add a new Patron Attribute Type, click the 'New Patron Attribute Type' button at the top of the page

    + +
      +
    • In the 'Patron attribute type code', enter a short code to identify this field +
        +
      • This field is limited to 10 characters (numbers and letters only)
        • +
      • This setting cannot be changed after an attribute is defined
        • +
      +
      • +
    • In the 'Description' field, enter a longer (plain text) explanation of what this field will contain
      • +
    • Check the box next to 'Repeatable' to let a patron record have multiple values of this attribute. +
        +
      • This setting cannot be changed after an attribute is defined
        • +
      +
      • +
    • If 'Unique identifier' is checked, the attribute will be a unique identifier which means, if a value is given to a patron record, the same value cannot be given to a different record. +
        +
      • This setting cannot be changed after an attribute is defined
        • +
      +
      • +
    • Check 'Allow password' to make it possible to associate a password with this attribute.
      • +
    • Check 'Display in OPAC' to display this attribute on a patron's details page in the OPAC.
      • +
    • Check 'Searchable' to make this attribute searchable in the staff patron search.
      • +
    • Authorized value category; if one is selected, the patron record input page will only allow values to be chosen from the authorized value list. +
        +
      • You will first need to add an authorized value list for it to appear in this menu
        • +
      • An authorized value list is not enforced during batch patron import.
        • +
      +
      • +
    • Click Save to save your new attribute
      • +
    + +

    Once added your attribute will appear on the list of attributes and also on the patron record add/edit form

    + +

    Editing/Deleting Patron Attributes

    + +

    Each patron attribute has an edit and a delete link beside it on the list of attributes.

    + +

    Some fields in the attribute will not be editable once created:

    + +
      +
    • Patron attribute type code
      • +
    • Repeatable
      • +
    • Unique identifier
      • +
    + +

    You will be unable to delete an attribute if it's in use.

    + + \ No newline at end of file diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/preferences.tmpl b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/preferences.tmpl index ab68f16f0c..c2cf717058 100644 --- a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/preferences.tmpl +++ b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/preferences.tmpl @@ -1,9 +1,19 @@ -

    System preferences administration

    +

    System Preferences

    + +

    Global system preferences control the way your Koha system works in general. Set these preferences before anything else in Koha.

    + +

    System preferences can be searched (using any part of the preference name or description) using the search box on the 'Administration' page or the search box at the top of each system preferences page.

    + +

    When editing preferences a '(modified)' tag will appear next to items you change until you click the 'Save All' button

    + +

    After saving your preferences you'll get a confirmation message telling you what preferences were saved

    + +

    Each section of preferences can be sorted alphabetically by clicking the small down arrow to the right of the word 'Preference' in the header column

    -

    This page allows you to set the system preferences that control much of the basic behavior of Koha.

    Each of the tabs on the left holds several different preferences:

    +
    • Acquisitions: holds preferences related to acquisitions such as handling patron suggestions and local taxes.
    • Administration: holds administrative preferences such as admin email address, sessions and timout.
      • @@ -21,4 +31,6 @@
    • Serials holds all preferences related to managing serial subscriptions.
    • Staff Client: customize the staff client by editing the stylesheet and navigation menu.
    • Web Services: includes preferences related to services like OAI-PMH.
      • -
    \ No newline at end of file +
+ + \ No newline at end of file diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/roadtype.tmpl b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/roadtype.tmpl index 582553c88c..833e01e95e 100644 --- a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/roadtype.tmpl +++ b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/roadtype.tmpl @@ -1,15 +1,13 @@ -

Road Types

- -

The values defined in this preference will show up in a pull down menu when entering patron information.These values can be used in geographic statistics.

- -

Add a new road type

-
    -
  • Click 'New Road Type'
    • -
  • Enter a value such as Blvd., Avenue, Street or St.
    • -
  • Click 'Submit'
    • -
  • Your values will appear on the Road Types page
    • -
  • Your values will also appear as authorized values when entering or editing a patron
    • -
- \ No newline at end of file +

Adding Road Types

+ +

To add a road type, click 'New Road Type' and then enter the road type the way you'd like it displayed.

+ +

Once you submit the form, your new road type will be listed on the Road Types page

+ +

Viewing Road Types on Patron Add form

+ +

When adding or editing a patron, if you have road types defined, there will be a pull down to choose the road type from.

+ + \ No newline at end of file diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/smart-rules.tmpl b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/smart-rules.tmpl index 163c4ea6f5..c4473c5b50 100644 --- a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/smart-rules.tmpl +++ b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/smart-rules.tmpl @@ -2,78 +2,93 @@

Circulation and Fines Rules

-

These rules define how your items are circulated, how/when fines are calculated and how holds are handled. The rules are applied from most specific to less specific, using the first found in this order:

+

These rules define how your items are circulated, how/when fines are calculated and how holds are handled.

+ +

The rules are applied from most specific to less specific, using the first found in this order:

    -
  • same library, same patron type, same item type
    • -
  • same library, same patron type, default item type
    • -
  • same library, default patron type, same item type
    • -
  • same library, default patron type, default item type
    • -
  • default library, same patron type, same item type
    • -
  • default library, same patron type, default item type
    • -
  • default library, default patron type, same item type
    • -
  • default library, default patron type, default item type
+
  • same library, same patron type, all item types
    • +
  • same library, same patron type, alll item types
    • +
  • same library, all patron types, same item type
    • +
  • same library, all patron types, all item types
    • +
  • all libraries, same patron type, same item type
    • +
  • all libraries, same patron type, all item types
    • +
  • all libraries, all patron types, same item type
    • +
  • all libraries, all patron types, all item types
    • + + +

    Tip: If you are a single library system choose your branch name before creating rules (sometimes having only rules for the 'all libraries' option can cause issues with holds)

    -

    TIP: If you are a single library system, you can leave your library selection to 'default library' or choose your branch name and experience the same results.

    +

    Important: At the very least you will need to set an default circulation rule. This rule should be set for all item types, all libraries and all patron types. That will catch all instances that do not match a specific rule. When checking out if you do not have a rule for all libraries, all item types and all patron types then you may see patrons getting blocked from placing holds. You will also want a rule for your specific library set for all item types and all patron types to avoid this holds issue. Koha needs to know what rule to fall back on.

    -

    Default Issuing Rule

    +

    Default Circulation Rules

    -

    Using the issuing rules matrix you can define rules that depend on patron/item type combos. To set your rules, choose a library from the pull down:

    - -

    TIP: If you leave this set to 'Default' it will apply the rules to all libraries

    +

    Using the issuing rules matrix you can define rules that depend on patron/item type combos. To set your rules, choose a library from the pull down (or 'all libraries' if you want to apply these rules to all branches):

    -

    From the matrix you can choose any combination of patron categories and item types to apply the rules to.

    +

    From the matrix you can choose any combination of patron categories and item types to apply the rules to

    -
    • First choose which patron category you'd like the rule to be applied to. If you leave this to 'Default' it will apply to all patron categories
      • -
    • Choose the 'Item Type' you would like this rule to apply to. If you leave this to 'Default' it will apply to all item types
      • -
    • Limit the number of items a patron can have checked out at the same time by entering a number in the 'Current Checkouts Allowed' field
      • -
    • Define the period of time and item can be checked out to a patron by entering the number of days in the 'Loan Period' box.
      • -
    • 'Fine Amount' should have the amount you would like to charge for overdue items -
      • IMPORTANT: Enter only numbers and decimal points.
      • -
    • The 'Fine Grace Period' is the period of time an item can be overdue before you start charging fines.
      • -
    • Enter the 'Fine Charging Interval' in days (ex. charge fines every 1 day, or every 2 days)
      • -
    • If your library 'fines' patrons by suspending their account you can enter the number of days their fine should be suspended in the 'Suspension in Days' field
      • -
    • Next decide if the patron can renew this item type and if so, enter how many times they can renew it in the 'Renewals Allowed' box
      • -
    • If the patron can place holds on this item type, enter the total numbers of items (of this type) that can be put on hold in the 'Holds Allowed' field
      • -
    • Finally, if you charge a rental fee for the item type and want to give a specific patron type a discount on that fee, enter the percentage discount (without the % symbol) in the 'Rental Discount' field
    +
      +
    • First choose which patron category you'd like the rule to be applied to. If you leave this to 'All' it will apply to all patron categories
      • +
    • Choose the 'Item Type' you would like this rule to apply to. If you leave this to 'All' it will apply to all item types
      • +
    • Limit the number of items a patron can have checked out at the same time by entering a number in the 'Current Checkouts Allowed' field
      • +
    • Define the period of time and item can be checked out to a patron by entering the number of days in the 'Loan Period' box.
      • +
    • 'Fine Amount' should have the amount you would like to charge for overdue items +
        +
      • Enter only numbers and decimal points (no currency symbols).
        • +
      +
      • +
    • The 'Fine Grace Period' is the period of time an item can be overdue before you start charging fines.
      • +
    • Enter the 'Fine Charging Interval' in days (ex. charge fines every 1 day, or every 2 days)
      • +
    • If your library 'fines' patrons by suspending their account you can enter the number of days their fine should be suspended in the 'Suspension in Days' field
      • +
    • Next decide if the patron can renew this item type and if so, enter how many times they can renew it in the 'Renewals Allowed' box
      • +
    • If the patron can place holds on this item type, enter the total numbers of items (of this type) that can be put on hold in the 'Holds Allowed' field
      • +
    • Finally, if you charge a rental fee for the item type and want to give a specific patron type a discount on that fee, enter the percentage discount (without the % symbol) in the 'Rental Discount' field
      • +
    -

    When finished, click 'Add' to save your changes. To modify a rule, create a new one with the same patron type and item type. If you would like to delete your rule, simply click the 'Delete' link to the right of the rule.

    +

    When finished, click 'Add' to save your changes. To modify a rule, create a new one with the same patron type and item type. If you would like to delete your rule, simply click the 'Delete' link to the right of the rule.

    -

    To save time you can clone rules from one library to another by choosing the clone option above the rules matrix.

    +

    To save time you can clone rules from one library to another by choosing the clone option above the rules matrix.

    -

    After choosing to clone you will be presented with a confirmation message.

    +

    After choosing to clone you will be presented with a confirmation message.

    -

    Default Checkouts and Hold Policy

    +

    Default Checkouts and Hold Policy

    -

    You can set a default maximum number of checkouts and hold policy that will be used if none is defined below for a particular item type or category.

    +

    You can set a default maximum number of checkouts and hold policy that will be used if none is defined below for a particular item type or category.

    -

    From this menu you can set a default to apply to all item types and patrons in the library.

    +

    From this menu you can set a default to apply to all item types and patrons in the library.

    -
    • In 'Total Current Checkouts Allowed' enter the total number of items patrons can have checked out at one time
      • -
    • Control where patrons can place holds from using the 'Hold Policy' menu -
      • From Any Library: Patrons from any library may put this item on hold. (default if none is defined)
        • -
      • From Home Library: Only patrons from the item's home library may put this book on hold.
        • -
      • No Holds Allowed: No patron may put this book on hold.
      • -
    • Once your policy is set, you can unset it by clicking the 'Unset' link to the right of the rule
    +
      +
    • In 'Total Current Checkouts Allowed' enter the total number of items patrons can have checked out at one time
      • +
    • Control where patrons can place holds from using the 'Hold Policy' menu +
        +
      • From Any Library: Patrons from any library may put this item on hold. (default if none is defined)
        • +
      • From Home Library: Only patrons from the item's home library may put this book on hold.
        • +
      • No Holds Allowed: No patron may put this book on hold.
        • +
      +
      • +
    • Once your policy is set, you can unset it by clicking the 'Unset' link to the right of the rule
      • +
    -

    Checkouts Per Patron

    +

    Checkouts Per Patron

    -

    For this library, you can specify the maximum number of loans that a patron of a given category can make, regardless of the item type.

    - -

    TIP: If the total amount loanable for a given patron category is left blank, no limit applies, except possibly for a limit you define for a specific item type.

    +

    For this library, you can specify the maximum number of loans that a patron of a given category can make, regardless of the item type.

    -

    Item Hold Policies

    +

    If the total amount loanable for a given patron category is left blank, no limit applies, except possibly for a limit you define for a specific item type.

    + +

    Item Hold Policies

    + +

    For this library, you can edit rules for given itemtypes, regardless of the patron's category. Currently, this means hold policies.

    + +

    The various policies have the following effects:

    + +
      +
    • From Any Library: Patrons from any library may put this item on hold. (default if none is defined)
      • +
    • From Home Library: Only patrons from the item's home library may put this book on hold.
      • +
    • No Holds Allowed: No patron may put this book on hold.
      • +
    -

    For this library, you can edit rules for given itemtypes, regardless of the patron's category. Currently, this means hold policies.

    - -

    The various policies have the following effects:

    +

    Important: Note that if the system preference AllowHoldPolicyOverride set to 'allow', these policies can be overridden by your circulation staff.

    -
    • From Any Library: Patrons from any library may put this item on hold. (default if none is defined)
      • -
    • From Home Library: Only patrons from the item's home library may put this book on hold.
      • -
    • No Holds Allowed: No patron may put this book on hold.
    - -

    IMPORTANT: Note that if the system preference AllowHoldPolicyOverride set to 'allow', these policies can be overridden by your circulation staff.

    - -

    IMPORTANT: These policies are based on the patron's home branch, not the branch that the reserving staff member is from.

    +

    Important: These policies are based on the patron's home branch, not the branch that the reserving staff member is from.

    - + diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/stopwords.tmpl b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/stopwords.tmpl index 96ccd8a873..e3dd8d4df5 100644 --- a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/stopwords.tmpl +++ b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/stopwords.tmpl @@ -1,14 +1,15 @@ -

    Stop word administration page

    +

    Stop Words

    -

    Here you should list all of the words you wish Koha to ignore when performing catalog searches or building the keyword index.

    -

    Koha with Zebra

    -

    Zebra handles stopwords internally, and does so effectively and efficiently. In normal circumstances, there should be no reason for Koha to remove stopwords prior to submitting the search query to Zebra, and in most cases doing so will actually negatively affect relevance ranking and phrase searching without giving any performance benefit.

    +

    Important: If NoZebra is set to 'Use' this option will not appear on the administration menu

    -

    Koha without Zebra

    -

    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.

    +

    Stop words are words that you want the search system to ignore.

    -

    (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.)

    +

    Koha comes with a standard list of stop words that can be edited by visiting the Stop Word administration area.

    + +

    To add a new stop word to the list, click the 'New Stop Word' button and add the word you'd like ignored

    + +

    Important: If you change something in this table, ask your administrator to run misc/batchRebuildBiblioTables.pl script.

    diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/z3950servers.tmpl b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/z3950servers.tmpl index cf1625f3b8..c8cd0f74eb 100644 --- a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/z3950servers.tmpl +++ b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/z3950servers.tmpl @@ -1,15 +1,41 @@ -

    Z39.50 servers administration

    +

    Z39.50 Servers

    -

    Defines the Z39.50 servers you want Koha to search.

    +

    Koha has a powerful copy cataloging tool. Using Koha you can connect to any Z39.50 target that is publicly available or that you have the log in information to.

    -

    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.

    +

    Koha comes with a default list of Z39.50 targets set up that you can add to, edit or delete.

    -

    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.)

    +

    To find additional targets you use IndexData's IRSpy: http://irspy.indexdata.com

    -

    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.

    +

    Add a Z39.50 Target

    +
      +
    • From the main Z39.50 page, click 'New Z39.50 Server' +
        +
      • Userid and Password are only required for servers that are password protected
        • +
      +
      • +
    -

    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.

    +

    Suggested Z39.50 Targets

    + +

    The following targets have been used successfully by other Koha libraries (in the Americas):

    + +
      +
    • BIBLIOS z3950.biblios.net:210 bibliographic
      • +
    • BIG COUNTRY KOHA bcls.kohalibrary.com:210 bcls_koha
      • +
    • CUYAHOGA COUNTY PUBLIC webcat.cuyahoga.lib.oh.us:210 INNOPAC
      • +
    • GREATER SUDBURY PUBLIC 216.223.90.51:210 INNOPAC
      • +
    • HALIFAX PUBLIC catalogue.halifaxpubliclibraries.ca:210 horizon
      • +
    • HALTON HILLS PUBLIC cat.hhpl.on.ca:210 halton_hills
      • +
    • LIBRARY OF CONGRESS z3950.loc.gov:7090 Voyager
      • +
    • LONDON PUBLIC LIBRARY catalogue.londonpubliclibrary.ca:210 INNOPAC
      • +
    • MANITOBA PUBLIC library.gov.mb.ca:210 horizon
      • +
    • MILTON PL cat.mpl.on.ca:210 horizon
      • +
    • NATIONAL LIBRARY OF WALES cat.llgc.org.uk:210 default
      • +
    • TORONTO PUBLIC symphony.torontopubliclibrary.ca:2200 unicorn
      • +
    • TRI-UNI 129.97.129.194:7090 voyager
      • +
    • VANCOUVER PUBLIC LIBRARY z3950.vpl.ca:210 Horizon
      • +
    \ No newline at end of file -- 2.39.5