From 4ee0cbf5a179b2b103fbfd285ba0c076a140e732 Mon Sep 17 00:00:00 2001 From: "Nicole C. Engard" Date: Fri, 19 Jun 2015 11:08:56 -0500 Subject: [PATCH] Bug 14424: Admin Help Files for 3.20 This patch updates some of the help files for Admin areas in 3.20+ To test: * Visit * Frameworks, add field, add subfield * Column settings * Patron attributes * Circ rules * Confirm help loads up and is right Signed-off-by: Tomas Cohen Arazi Signed-off-by: Jonathan Druart Signed-off-by: Tomas Cohen Arazi (cherry picked from commit d3983e563ffbce5c3276108c5840394bcb7b8593) Signed-off-by: Chris Cormack --- .../en/modules/help/admin/biblio_framework.tt | 181 +++++++++++++++++- .../en/modules/help/admin/columns_settings.tt | 8 +- .../help/admin/marc_subfields_structure.tt | 120 ++++++------ .../en/modules/help/admin/marctagstructure.tt | 15 +- .../modules/help/admin/patron-attr-types.tt | 1 + .../prog/en/modules/help/admin/smart-rules.tt | 12 +- 6 files changed, 250 insertions(+), 87 deletions(-) diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/biblio_framework.tt b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/biblio_framework.tt index f8dd2a8122..be3df1d149 100644 --- a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/biblio_framework.tt +++ b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/biblio_framework.tt @@ -4,36 +4,199 @@

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.

+

Important: 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

+

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
      • +
    • 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 +
  • 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
      • +
    • 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
    • +
  • Once your Framework appears on the screen you can edit or delete each field by following the instructions for editing subfields
-

Edit Existing Frameworks

+

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

+

Add subfields to Frameworks

+ +

To add a field to a Framework click the 'New Tag' button at the top of the 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. The process of entering the settings for the new subfield is the same as those found in the editing subfields in frameworks section of the manual.

+ +

Edit Framework Subfields

+ +

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

+ +
    +
  • Each field has a tag (which is the MARC tag) that is uneditable +
      +
    • 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 Basic constraint 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.
        • +
      +
      • +
    +
    • +
  • For each subfield you can set the following Advanced constraint values +
      +
    • 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.
        • +
      +
      • +
    • Visibility +
        +
      • allows you to select from where this subfield is visible/hidden, simply check the boxes where you would like the field to show and uncheck the boxes where you would like it hidden.
        • +
      +
      • +
    • 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.
          • +
        +
        • +
      • Warning: This value should not change after data has been added to your catalog. If you need to change this value you must ask your system administrator to run misc/batchRebuildBiblioTables.pl.
        • +
      +
      • +
    • 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).
        • +
      +
      • +
    +
    • +
  • For each subfield you can set the following Other option values +
      +
    • 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
        • +
      +
      • +
    • 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.
        • +
      • Examples: +
          +
        • For call numbers there is an option to add a call number browser next to the the call number subfield. Simply choose the cn_browser.pl plugin. Learn more in the cataloging section of the manual.
          • +
        • 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
    • +
+ +

Import/Export Frameworks

+ +

Next to each framework is a link to either import or export the framework.

+ +
Export Framework
+ +

To export a framework simply click the 'Export' link to the right of framework title.

+ +

When you click 'Export' you will be prompted to choose what format to export the file in.

+ +

A framework exported this way can be imported into any other Koha installation using the import framework option.

+ +
Import Framework
+ +

An easy way to create a new framework is to import one created for your or another Koha installation. This framework would need to be exported from the other system using the instructions above to be available for import here.

+ +

To import a framework you first need to create a new framework. Once you have that framework, click 'Import' to the right of the new framework.

+ +

You will be prompted to find a file on your computer to import into the framework.

+ +

You will be asked to confirm your actions before the file is imported.

+ +

As your file is uploaded you will see an image that will confirm that the system is working.

+ +

Once your import is complete you will be brought to the framework edit tool where you can make any changes you need to the framework you imported.

+

See the full documentation for Frameworks in the manual (online).

[% INCLUDE 'help-bottom.inc' %] \ No newline at end of file diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/columns_settings.tt b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/columns_settings.tt index c34957134a..f31771fbd6 100644 --- a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/columns_settings.tt +++ b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/columns_settings.tt @@ -2,15 +2,15 @@

Columns settings

-

This administration area will help you hide or display columns on fixed tables throughout the staff client. Right now there is only one table, the currencies table, you can control with this, but more will come.

+

This administration area will help you hide or display columns on fixed tables throughout the staff client.

-

Clicking on the module you'd like to edit tables for will show you the options available to you. Right now only 'Administration' has any options.

+

Clicking on the module you'd like to edit tables for will show you the options available to you.

-

This area lets you control the columns that show in the Currency admin area. If nothing is hidden you will see no check marks and will see all of the columns when viewing the table.

+

This area lets you control the columns that show several of the modules in Koha. If nothing is hidden you will see no check marks and will see all of the columns when viewing the table.

If columns are hidden they will be checked off and hidden when you view the table.

-

You can also toggle columns using the 'Show/Hide Columns button in the top right of the page.

+

You can also toggle columns using the 'Show/Hide Columns' button in the top right of the page you altered the columns for.

See the full documentation for Columns settings in the manual (online).

diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/marc_subfields_structure.tt b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/marc_subfields_structure.tt index c949400e74..75d248d4d3 100644 --- a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/marc_subfields_structure.tt +++ b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/marc_subfields_structure.tt @@ -5,126 +5,116 @@

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

    -
  • Each field has a tag (which is the MARC tag) +
  • Each field has a tag (which is the MARC tag) that is uneditable
      -
    • 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
      • +
    • 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
    • -
  • 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 +
+ +

To edit the subfields associated with the tag, click 'Subfields' to the right of the tag on the 'MARC Structure' listing

+
    -
  • Text for librarian +
  • 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 Basic constraint values
      -
    • what appears before the subfield in the librarian interface
      • +
    • Text for librarian +
        +
      • what appears before the subfield in the librarian interface
      • -
    • Text for OPAC +
    • Text for OPAC +
        +
      • what appears before the field in the OPAC.
          -
        • what appears before the field in the OPAC.
          • -
        • If left empty, the text for librarian is used instead
          • +
        • 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 +
      • Repeatable
          -
        • the record will not be allowed to save unless you have a value assigned to this tag
          • +
        • the field will have a plus sign next to it allowing you to add multiples of that tag
        • -
      • Managed in tab +
      • Mandatory
          -
        • 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.
          • +
        • the record will not be allowed to save unless you have a value assigned to this tag
        • -
      -
        -
      • Default value +
      • Managed in tab
          -
        • 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.
          • +
        • 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.
      +
      • +
    • For each subfield you can set the following Advanced constraint values
        -
      • Visibility +
      • Default value
          -
        • Allows you to set the visibility options for a MARC field.
          • -
            -
          • OPAC - Checking this box determines whether the subfield is visible in the public interface. Unchecking it hides the field in the public interface.
            • -
          • Intranet - Checking this box determines whether the subfield is visible in the staff interface. Unchecking it hides the field in the staff interface.
            • -
          • Editor - Checking this box makes the subfield available to the MARC editor. Unchecking it indicates the field should not be shown in the editor.
            • -
          • Collapsed - Checking this box determines whether the subfield is expanded or collapsed in the MARC editor; the subfield will appear as a clickable link to expand and edit the subfield. Unchecking it indicates that the field will be expanded by default.
            • -
          • Flagged - This setting is exclusive of all other visibility options, and flags the field.
            • +
          • 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.
          -
        -
          -
        • Max length +
        • Visibility
            -
          • Set the max characters allowed for the subfield. If empty or 0, it defaults to 9999.
            • +
          • allows you to select from where this subfield is visible/hidden, simply check the boxes where you would like the field to show and uncheck the boxes where you would like it hidden.
          • -
        +
      • Is a URL
          -
        • Is a url -
            -
          • if checked, it means that the subfield is a url and can be clicked
            • +
          • if checked, it means that the subfield is a URL and can be clicked
          • -
        -
          -
        • Link +
        • 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 : +
          • 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.
              • +
            • 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.
            • -
          • NOTE: If you change this value you must ask your administrator to run misc/batchRebuildBiblioTables.pl.
            • +
          • Warning: This value should not change after data has been added to your catalog. If you need to change this value you must ask your system administrator to run misc/batchRebuildBiblioTables.pl.
          • -
        -
          -
        • Koha link +
        • 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).
            • +
          • 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).
        +
        • +
      • For each subfield you can set the following Other option values
          -
        • Authorized value +
        • 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
            • +
          • means the value cannot by typed by the librarian, but must be chosen from a pull down generated by the authorized value list
          • -
        -
          -
        • Thesaurus +
        • Thesaurus
            -
          • means that the value is not free text, but must be searched in the authority/thesaurus of the selected category
            • +
          • means that the value is not free text, but must be searched in the authority/thesaurus of the selected category
          • -
        +
      • Plugin
          -
        • Plugin +
        • means the value is calculated or managed by a plugin. Plugins can do almost anything.
          • +
        • Examples:
            -
          • 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)
            • +
          • For call numbers there is an option to add a call number browser next to the the call number subfield. Simply choose the cn_browser.pl plugin. Learn more in the cataloging section of the manual.
            • +
          • 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
      • +
    • To save your changes simply click the 'Save Changes' button at the top of the screen

    See the full documentation for MARC Frameworks in the manual (online).

    diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/marctagstructure.tt b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/marctagstructure.tt index 6a8b3f4779..a8ccb6c2e4 100644 --- a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/marctagstructure.tt +++ b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/marctagstructure.tt @@ -7,19 +7,18 @@

    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
      • +
    • 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.

    +

    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. The process of entering the settings for the new subfield is the same as those found in the editing subfields in frameworks section of the manual.

    See the full documentation for MARC Frameworks in the manual (online).

    diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/patron-attr-types.tt b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/patron-attr-types.tt index a4a7940ea3..9f26a626dd 100644 --- a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/patron-attr-types.tt +++ b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/patron-attr-types.tt @@ -28,6 +28,7 @@
  • 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. +
  • Unique attributes can be used as match points on the patron import tool
    • Important: This setting cannot be changed after an attribute is defined
    diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/smart-rules.tt b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/smart-rules.tt index 7aa2743814..1663128167 100644 --- a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/smart-rules.tt +++ b/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/smart-rules.tt @@ -70,9 +70,19 @@
  • If you're allowing renewals you can control how soon before the due date patrons can renew their materials with the 'No renewals before' box.
    • Items can be renewed at any time if this value is left blank. Otherwise items can only be renewed if the item is before the number in units (days/hours) entered in this box.
  • You can enable automatic renewals for certain items/patrons if you'd like. This will renew automatically following your circulation rules unless there is a hold on the item -
    • Important: You will need to enable the automatic renewal cron job for this to work.
    +
      +
    • Important: You will need to enable the automatic renewal cron job for this to work.
      • +
    • Important: This feature needs to have the "no renewal before" column filled in or it will auto renew everyday after the due date.
      • +
  • 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
    • +
  • Next you can decide if this patron/item combo are allowed to place holds on items that are on the shelf (or available in the library) or not. If you choose 'no' then items can only be placed on hold if checked out
    • +
  • You can also decide if patrons are allowed to place item specific holds on the item type in question. The options are: +
      +
    • Allow: Will allow patrons the option to choose next available or item specific
      • +
    • Don't allow: Will only allow patrons to choose next available
      • +
    • Force: Will only allow patrons to choose an specific item
      • +
  • 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
    • -- 2.39.5