View | Details | Raw Unified | Return to bug 7936
Collapse All | Expand All

(-)a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/admin-home.tt (-8 / +8 lines)
Lines 2-26 Link Here
2
2
3
<h1>Administration Help</h1>
3
<h1>Administration Help</h1>
4
4
5
<p>The administration area is where you set all of your preferences for the system. Preference are broken down into several categories.</p>
5
<p>The administration area is where you set all of your preferences for the system. Preference are broken down into several categories, detailed below.</p>
6
6
7
<h3>Global System Preferences</h3>
7
<h3>Global System Preferences</h3>
8
8
9
<p>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.</p>
9
<p>Koha has an extensive set of system preferences. The system preferences control all the various features within Koha, whether they are active in your install or not. System preferences are set at install and are generally not changed afterwards.</p>
10
10
11
<p>If  you are not sure what combination of system preferences to use, try using one of the sample profiles at install.</p>
11
<p>If you are not sure what combination of system preferences to use, try using one of the sample profiles at install.</p>
12
12
13
<p style="color: #990000">IMPORTANT: many preferences interact with each other. Turning on one system preference may require that others are also set.</p>
13
<p style="color: #990000">IMPORTANT: Many preferences interact with each other. Turning on one system preference may require that others are also set.</p>
14
14
15
<h3>Basic Parameters</h3>
15
<h3>Basic Parameters</h3>
16
16
17
<p>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.</p>
17
<p>"Basic Parameters" is where library policies are set and governed. It is best to set your system preferences and then work through the basic parameters in the order that they appear on this page.</p>
18
18
19
<p>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.</p>
19
<p>Please note that it is not required to set all the basic parameters. For example, if you do not plan to use budget based acquisitions, then 'Funds,' 'Budgets,' and 'Currencies and Exchange Rates' can be ignored.</p>
20
20
21
<h3>Patrons and Circulation</h3>
21
<h3>Patrons and Circulation</h3>
22
22
23
<p>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.</p>
23
<p>These parameters help control patron records and circulation rules. It is best to set the basic parameters before visiting this section.</p>
24
24
25
<h3>Catalog</h3>
25
<h3>Catalog</h3>
26
26
Lines 28-34 Link Here
28
28
29
<h3>Additional Parameters</h3>
29
<h3>Additional Parameters</h3>
30
30
31
<p>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.</p>
31
<p>This list of parameters includes functionalities that didn't fit in any other category.  These items are optional and may not need to be altered, depending on your library's needs.</p>
32
32
33
<p><strong>See the full documentation for system Administration in the <a href="http://manual.koha-community.org/3.8/en/administration.html">manual</a> (online).</strong></p>
33
<p><strong>See the full documentation for system Administration in the <a href="http://manual.koha-community.org/3.8/en/administration.html">manual</a> (online).</strong></p>
34
34
(-)a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/aqbudgetperiods.tt (-9 / +9 lines)
Lines 2-25 Link Here
2
2
3
<h1>Budgets</h1>
3
<h1>Budgets</h1>
4
4
5
<p>Budgets are the top level used for tracking accounting values related to acquisitions.</p>
5
<p>The 'Budgets' functionality is used for tracking accounting values related to acquisitions.</p>
6
6
7
<p>An example would be to create a budget for the current year and then breaking that into Funds for different areas of the library.</p>
7
<p>'Budgets' can be used to create a budget for the current year and then break it into Funds for different areas of the library.</p>
8
8
9
<h2>Add a budget</h2>
9
<h2>Add a budget</h2>
10
10
11
<p>To add a budget click the 'New Budget' button.</p>
11
<p>To add a budget, click the 'New Budget' button.</p>
12
12
13
<ul>
13
<ul>
14
	<li>Choose the time period this budget is for, whether it's an academic year, a fiscal year, a quarter, etc.</li>
14
    <li>Choose a time period for the budget, be it an academic year, a fiscal year, a quarter, or other unit of time.</li>
15
        <li>The Description should be something that will help you identify the budget when ordering</li>
15
    <li>The description should help you identify the budget when ordering.</li>
16
	<li>In the amount box do not use any symbols, simply enter the amount of the budget with numbers and decimals.</li>
16
    <li>Do not use any symbols other than the decimal separator in the amount box.</li>
17
	<li>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.</li>
17
    <li>Marking a budget 'Active' makes it usable when placing orders in the acquisitions module, even if an order is placed after the budget end date. This will allow you to record orders that were placed in a previous budget period.</li>
18
	<li>Locking a budget means that Funds will not be able to be modified by librarians</li>
18
    <li>Locking a budget prevents other librarians from modifying that fund.</li>
19
</ul>
19
</ul>
20
20
21
<p>Once you have made your edits, click the 'Save Changes' button. You will be brought to a list of your existing budgets.</p>
21
<p>Once you have made your edits, click the 'Save Changes' button. You will be brought to a list of your existing budgets.</p>
22
22
23
<p><strong>See the full documentation for Budgets in the <a href="http://manual.koha-community.org/3.8/en/acqadmin.html#budgetplanning">manual</a> (online).</strong></p>
23
<p><strong>See the full documentation for Budgets in the <a href="http://manual.koha-community.org/3.8/en/acqadmin.html#budgetplanning">manual</a> (online).</strong></p>
24
24
25
[% INCLUDE 'help-bottom.inc' %]
25
[% INCLUDE 'help-bottom.inc' %]
(-)a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/aqbudgets.tt (-14 / +14 lines)
Lines 6-36 Link Here
6
6
7
<h2>Add a Fund</h2>
7
<h2>Add a Fund</h2>
8
8
9
<p>A fund is added to a budget.</p>
9
<p>Funds can be added to a budget.</p>
10
10
11
<p style="color: #990000;">Important: A budget must be defined before a fund can be created.</p>
11
<p style="color: #990000;">Important: A budget must be defined before a fund can be created.</p>
12
12
13
<p>To add a new fund click the New button and then choose which Budget you would like to add the fund to.</p>
13
<p>To add a new fund, click the 'New' button and choose the budget to which you would like to add the fund.</p>
14
14
15
<p>In the form that appears you wan to enter the basics about your fund.</p>
15
<p>In the form that appears, enter the basics about your fund.</p>
16
16
17
<p>The three first fields are required, the rest are optional</p>
17
<p>The three first fields are required. The rest are optional.</p>
18
18
19
<ul>
19
<ul>
20
       <li>Fund Code is a unique identifier for your fund</li>
20
    <li>'Fund Code' is a unique identifier for your fund.</li>
21
        <li>The Fund Name should be something that librarians will understand</li>
21
    <li>Use a fund name that clearly describes said fund.</li>
22
	<li>Amount should be entered with only numbers and decimals, no other characters</li>
22
    <li>The fund's amount should be should only include numerals and a decimal separator. No other characters should be entered.</li>
23
	<li>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</li>
23
    <li>You can assign a fund to a particular librarian. This option will restrict making changes to that fund to the assigned librarian.</li>
24
	<li>Choose which library will be using this fund</li>
24
    <li>Choose which library will use the fund</li>
25
	<li>You can restrict who can order from this fund by choosing either the owner or the library from the 'Restrict access to' menu</li>
25
    <li>You can restrict who can order from a fund by selecting an owner or a library from the 'Restrict access to' menu.</li>
26
	<li>Notes are simply for any descriptive notes you might want to add so that librarians know when to use this fund</li>
26
    <li>The 'Notes' field is for descriptions to detail when librarians should use the fund.</li>
27
   <li>Planning categories are used for statistical purposes. To learn more about planning categories, check out the Planning Category FAQ.</li>
27
    li>Planning categories are used for statistical purposes. To learn more about planning categories, check out the Planning Category FAQ.</li>
28
</ul>
28
</ul>
29
29
30
<p>When complete, click 'Submit' and you will be brought to a list of all of the funds for the budget.</p>
30
<p>When complete, click 'Submit' and you will be brought to a list of all of the funds for the budget.</p>
31
31
32
<p>To the right of each fund you will find the 'Edit,' 'Delete,' and 'Add Child Fund' options. A child fund simply a sub-fund of the fund listed. An example would be to have a fund for 'Fiction' and under that have a fund for 'New Releases' and a fund for 'Science Fiction.' It is an optional way to further organize your finances.</p>
32
<p>To the right of each fund you will find the 'Edit,' 'Delete,' and 'Add Child Fund' options. A Child Fund a sub-fund of the parent fund. For example, one might have a parent fund for 'Fiction,' and Child Funds for 'New Releases' and 'Science Fiction.' It is an optional way to further organize your finances.</p>
33
33
34
<p><strong>See the full documentation for Funds in the <a href="http://manual.koha-community.org/3.8/en/acqadmin.html#funds">manual</a> (online).</strong></p>
34
<p><strong>See the full documentation for Funds in the <a href="http://manual.koha-community.org/3.8/en/acqadmin.html#funds">manual</a> (online).</strong></p>
35
35
36
[% INCLUDE 'help-bottom.inc' %]
36
[% INCLUDE 'help-bottom.inc' %]
(-)a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/aqplan.tt (-6 / +6 lines)
Lines 2-17 Link Here
2
2
3
<h1>Budget Planning</h1>
3
<h1>Budget Planning</h1>
4
4
5
<p>When viewing the list of funds click the 'Planning' button and choose how you would like to plan to spend your budget.</p>
5
<p>When viewing the list of funds, click the 'Budget Planning' button and choose how you would like to plan to spend your budget.</p>
6
6
7
<p>If you choose 'Plan by MONTHS' you will see the budgeted amount broken down by months.</p>
7
<p>If you choose 'Plan by Months' you will see the budgeted amount broken down by months.</p>
8
8
9
<p>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.</p>
9
<p>To hide some of the columns, click the minus sign (-) to the right or below the dates. To add more columns, click the plus sign (+) found above the 'Auto-fill row' buttons.</p>
10
10
11
<p>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.</p>
11
<p>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 automatically divide the total. Therefore, you may have to adjust the allocations manually to better reflect your library's needs.</p>
12
12
13
<p>Once your changes are made, click the 'Save' button. If you would like to export your data as a CSV file you can do so by entering a file name in the 'Output to a file named' field and clicking the 'Output' button.</p>
13
<p>Once your changes are made, click the 'Save' button. If you would like to export your data as a CSV file, enter a file name in the 'Output to a file named' field and click the 'Output' button.</p>
14
14
15
<p><strong>See the full documentation for Budget Planning in the <a href="http://manual.koha-community.org/3.8/en/acqadmin.html#fundsplanning">manual</a> (online).</strong></p>
15
<p><strong>See the full documentation for Budget Planning in the <a href="http://manual.koha-community.org/3.8/en/acqadmin.html#fundsplanning">manual</a> (online).</strong></p>
16
16
17
[% INCLUDE 'help-bottom.inc' %]
17
[% INCLUDE 'help-bottom.inc' %]
(-)a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/auth_subfields_structure.tt (-97 / +23 lines)
Lines 2-62 Link Here
2
2
3
<h1>MARC Record Subfields</h1>
3
<h1>MARC Record Subfields</h1>
4
4
5
<p>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</p>
5
<p>'Frameworks' are made up of MARC fields and subfields. To make edits to most frameworks, you must edit the fields and subfields. Click 'Edit' (on the right of each subfield) to make changes to the text associated with the field.</p>
6
6
7
<ul>
7
<ul>
8
	<li>Each field has a tag (which is the MARC tag)
8
     <li>Each field has a tag (the MARC tag).
9
<ul>
9
<ul>
10
	<li>The 'Label for lib' is what will show in the staff client if you have advancedMARCeditor set to display labels</li>
10
  <li>'Label for lib' is what will show in the staff client if you have advancedMARCeditor set to display labels.</li>
11
	<li>The 'Label for OPAC' is what will show on the MARC view in the OPAC</li>
11
   <li>'Label for OPAC' is what will show on the MARC view in the OPAC.</li>
12
	<li>If you check 'Repeatable' then the field will have a plus sign next to it allowing you to add multiples of that tag</li>
12
      <li>If you check 'Repeatable,' the field will have a plus sign next to it that will allow you to add multiples of that tag.</li>
13
	<li>If you check 'Mandatory' the record will not be allowed to save unless you have a value assigned to this tag</li>
13
       <li>If you check 'Mandatory,' the record will not be allowed to save unless you have a value assigned to this tag.</li>
14
	<li>'Authorized value' is where you define an authorized value that your catalogers can choose from a pull down to fill this field in
14
        <li>'Authorized value' is where you chose an authorized value list from which your catalogers can select a value for this subfield. To edit the subfields associated with the tag, click 'Subfields' to the right of the tag on the 'MARC Structure' listing.</li>
15
To edit the subfields associated with the tag, click 'Subfields' to the right of the tag on the 'MARC Structure' listing</li>
16
</ul>
15
</ul>
17
</li>
16
</li>
18
	<li>From the list of subfields you can click 'Delete' to the right of each to delete the subfields</li>
17
 <li>From the list of subfields, you can click 'Delete' to the right of each to erase the subfield in question.</li>
19
	<li>To edit the subfields click 'Edit Subfields'</li>
18
    <li>To edit the subfields, click 'Edit Subfields.'</li>
20
	<li>For each subfield you can set the following values
19
        <li>For each subfield, you can set the following values:
21
<ul>
20
<ul>
22
	<li>Text for librarian
21
  <li>'Text for librarian' is what appears before the subfield in the librarian interface.</li>
23
<ul>
22
  <li>'Text for OPAC' is what appears before the field in the OPAC.If left empty, the text for librarian is used instead</li>
24
	<li>what appears before the subfield in the librarian interface</li>
23
    <li>If 'Repeatable' is checked, the field  will have a plus sign next to it in the MARC cataloguing monologue which allows you to add multiples of that tag.</li>
25
</ul>
24
      <li>'Mandatory' prevents the user from saving a record  unless there is a value assigned to the tag.</li>
26
</li>
25
      <li>'Managed in tab' defines the tab where the subfield is shown. All subfields of a given field must either be in the same tab or ignored. 'Ignore' means that the subfield is not managed.</li>
27
	<li>Text for OPAC
26
      <li>'Default value' defines what you want to appear in the field by default. This field will be editable, but it saves time if you use the same note over and over.</li>
28
<ul>
27
       <li>'Hidden' allows you to select from nineteen possible visibility conditions, seventeen of which are implemented. They are the following:
29
	<li>what appears before the field in the OPAC.</li>
30
	<li>If left empty, the text for librarian is used instead</li>
31
</ul>
32
</li>
33
	<li>Repeatable
34
<ul>
35
	<li>the field will have a plus sign next to it allowing you to add multiples of that tag</li>
36
</ul>
37
</li>
38
	<li>Mandatory
39
<ul>
40
	<li>the record will not be allowed to save unless you have a value assigned to this tag</li>
41
</ul>
42
</li>
43
	<li>Managed in tab
44
<ul>
45
	<li>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.</li>
46
</ul>
47
</li>
48
</ul>
49
<ul>
50
	<li>Default value
51
<ul>
52
	<li>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.</li>
53
</ul>
54
</li>
55
</ul>
56
<ul>
57
	<li>hidden
58
<ul>
59
	<li>allows you to select from 19 possible visibility conditions, 17 of which are implemented. They are the following:
60
<ul>
28
<ul>
61
	<li>-9 =&gt; Future use</li>
29
	<li>-9 =&gt; Future use</li>
62
	<li>-8 =&gt; Flag</li>
30
	<li>-8 =&gt; Flag</li>
Lines 78-140 To edit the subfields associated with the tag, click 'Subfields' to the right of Link Here
78
	<li>8 =&gt; !OPAC !Intranet !Editor !Collapsed</li>
46
	<li>8 =&gt; !OPAC !Intranet !Editor !Collapsed</li>
79
	<li>9 =&gt; Future use</li>
47
	<li>9 =&gt; Future use</li>
80
</ul>
48
</ul>
81
</li>
82
       <li>( ! means 'not visible' or in the case of Collapsed 'not Collapsed')</li>
83
</ul>
84
</li>
85
</ul>
86
<ul>
87
   <li>Is a url
88
<ul>
89
      <li>if checked, it means that the subfield is a url and can be clicked</li>
90
</ul>
91
</li>
92
</ul>
93
<ul>
94
	<li>Link
95
<ul>
96
      <li>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 :
97
<ul>
98
	<li>on a field like author (200f in UNIMARC), put 200f here, you will be able to see all bib records with the same author.</li>
99
	<li>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.</li>
100
</ul>
101
</li>
102
	<li style="color: #990000;">Important: This value should not change after data has been added to your catalog</li>
103
</ul>
104
</li>
105
</ul>
106
<ul>
107
	<li>Koha link
108
<ul>
109
	<li>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).</li>
110
</ul>
49
</ul>
111
</li>
112
</ul>
113
<ul>
114
	<li>Authorized value
115
<ul>
50
<ul>
116
	<li>means the value cannot by typed by the librarian, but must be chosen from a pull down generated by the authorized value list</li>
51
    <li>(! means 'not visible' or in the case of collapsed 'not collapsed')</li>
117
      <li>In the example above, the 504a field will show the MARC504 Authorized Values when cataloging</li>
52
    <li>If 'Is a url' is checked, the subfield is a url and can be clicked</li>
53
    <li>'Authorized Value' allows the librarian to select an authorized value list from which cataloguers must choose an option.</li>
118
</ul>
54
</ul>
119
</li>
55
</li>
120
</ul>
56
</ul>
121
<ul>
57
<ul>
122
	<li>Thesaurus
58
    <li>The 'Thesaurus' chooses the authority file to which the field should be linked.</li>
123
<ul>
124
	<li>means that the value is not free text, but must be searched in the authority/thesaurus of the selected category</li>
125
</ul>
59
</ul>
126
</li>
127
</ul>
128
<ul>
129
	<li>Plugin
130
<ul>
60
<ul>
131
	<li>means the value is calculated or managed by a plugin. Plugins can do almost anything.</li>
61
    <li>'Plugin' allows the librarian to choose a plugin to calculate or manage a subfield. Plugins can do almost anything. For example, in UNIMARC there are plugins for all 1xx fields that are coded fields. There are also two plugins (unimarc_plugin_210c and unimarc_plugin_225a) that can find the editor from an ISBN, as well as the collection list for the editor.</li>
132
	<li>For example, in UNIMARC there are plugins for every 1xx fields that are coded fields. The plugin is a huge help for cataloger ! There are also two plugins (unimarc_plugin_210c and unimarc_plugin_225a that can "magically" find the editor from an ISBN, and the collection list for the editor)</li>
133
</ul>
62
</ul>
134
</li>
63
    <li>To save your changes, click the 'Save Changes' button at the top of the screen.</li>
135
</ul>
136
</li>
137
      <li>To save your changes simply click the 'Save Changes' button at the top of the screen</li>
138
</ul>
64
</ul>
139
65
140
<p><strong>See the full documentation for Authorities in the <a href="http://manual.koha-community.org/3.8/en/catadmin.html#authoritiesadmin">manual</a> (online).</strong></p>
66
<p><strong>See the full documentation for Authorities in the <a href="http://manual.koha-community.org/3.8/en/catadmin.html#authoritiesadmin">manual</a> (online).</strong></p>
(-)a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/auth_tag_structure.tt (-12 / +10 lines)
Lines 2-26 Link Here
2
2
3
<h1>Authority Record Tags</h1>
3
<h1>Authority Record Tags</h1>
4
4
5
<p>To add a field to a Authority Framework click the 'New Tag' button at the top of the Authority Framework definition</p>
5
<p>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.</p>
6
7
<p>This will open up a blank form for entering MARC field data</p>
8
6
9
<p>Enter the information about your new tag:</p>
7
<p>Enter the information about your new tag:</p>
10
8
11
<ul>
9
<ul>
12
	<li>The 'Tag' is the MARC field number</li>
10
      <li>The 'Tag' is the MARC field number.</li>
13
	<li>The 'Label for lib' is the text that will appear in the staff client when in the cataloging module</li>
11
   <li>The 'Label for lib' is the text that will appear in the staff client when in the cataloging module.</li>
14
	<li>The 'Label for OPAC' is the text that will appear in the OPAC when viewing the MARC version of the record</li>
12
   <li>The 'Label for OPAC' is the text that will appear in the OPAC when viewing the MARC version of the record.</li>
15
	<li>If this field can be repeated, check the 'Repeatable' box</li>
13
    <li>If this field can be repeated, check the 'Repeatable' box.</li>
16
	<li>If this field is mandatory, check the 'Mandatory' box</li>
14
    <li>If this field is mandatory, check the 'Mandatory' box.</li>
17
	<li>If you want this field to be a pull down with limited possible answers, choose which 'Authorized value' list you want to use</li>
15
        <li>If you want this field to be a drop-down menu with limited possible answers, choose which 'Authorized value' list you want to use.</li>
18
</ul>
16
</ul>
19
17
20
<p>When you're finished, click 'Save Changes' and you will be presented with your new field</p>
18
<p>When you're finished, click 'Save Changes' and you will be presented with your new field.</p>
21
19
22
<p>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.</p>
20
<p>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.</p>
23
21
24
<p><strong>See the full documentation for Authorities in the <a href="http://manual.koha-community.org/3.8/en/catadmin.html#authoritiesadmin">manual</a> (online).</strong></p>
22
<p><strong>See the full documentation for Authorities in the <a href="http://manual.koha-community.org/3.8/en/catadmin.html#authoritiesadmin">manual</a> (online).</strong></p>
25
23
26
[% INCLUDE 'help-bottom.inc' %]
24
[% INCLUDE 'help-bottom.inc' %]
(-)a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/authorised_values.tt (-124 / +38 lines)
Lines 2-151 Link Here
2
2
3
<h1>Authorized Values</h1>
3
<h1>Authorized Values</h1>
4
4
5
<p>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.</p>
5
<p>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.</p>
6
6
7
<h2>Existing Values</h2>
7
<h2>Existing Values</h2>
8
8
9
<p>Koha installs with pre-defined values that your library is likely to use, for instance 'Lost'.</p>
9
<p>Koha installs with pre-defined values that your library is likely to use, for instance, 'Lost.'</p> By default, this includes:
10
10
<ul>
11
<ul>
11
    <li>'Asort1,' for acquisitions statistical purposes.</li>
12
	<li>Asort1
12
    <li>'Asort2,' used for acquisitions statistical purposes.</li>
13
<ul>
13
    <li>'BOR_NOTES' is for values for custom patron notes that appear on the circulation screen and the OPAC.</li>
14
	<li>Used for acquisitions statistical purposes</li>
14
    <li>'Bsort1' is for patron statistical purposes.</li>
15
</ul>
15
    <li>'Bsort2' is used for patron statistical purposes.</li>
16
</li>
16
    <li>'CART' is the shelving cart location, used by InProcessingToShelvingCart and ReturnToShelvingCart</li>
17
	<li>Asort2
17
    <li>'CCODE' is for collection codes (appears when cataloging and working with items).</li>
18
<ul>
18
    <li>'DAMAGED' is for descriptions of damaged items, and appears when cataloging and working with items.</li>
19
	<li>Used for acquisitions statistical purposes</li>
19
    <li>'HINGS_AS' is for General Holdings: Acquisition Status Designator, a data element that specifies the acquisition status for the unit at the time of the holdings report.</li>
20
</ul>
20
    <li>'HINGS_C' is for General Holdings: Completeness Designator.</li>
21
</li>
21
    <li>'HINGS_PF' is for Physical Form Designators</li>
22
	<li>BOR_NOTES
22
    <li>'HINGS_RD' is for General Holdings: Retention Designator, a data element that specifies the retention policy for the unit at the time of the holdings report.</li>
23
<ul>
23
    <li>'HINGS_UT' is for General Holdings: Type of Unit Designator.</li>
24
	<li>Values for custom patron notes that appear on the circulation screen and the OPAC</li>
24
    <li>'LOC' is for the shelving location and usually appears when adding or editing an item.</li>
25
</ul>
25
    <li>'LOST' is for descriptions for items marked as lost. It appears when adding or editing an item. Values given to lost statuses should be numeric (not alphabetical) in order for statuses to appear properly.</li>
26
</li>
26
    <li>'MANUAL_INV' includes values for manual invoicing.</li>
27
	<li>Bsort1
27
    <li>'NOT_LOAN' is used to list reasons why a title is not for loan.</li>
28
<ul>
28
    <li>'PROC' is for the location to be used for NewItemsDefaultLocation (change description as desired), also the location expected by InProcessingToShelvingCart.</li>
29
	<li>Used for patron statistical purposes</li>
29
    <li>'RESTRICTED' is used for the restricted status of an item</li>
30
</ul>
30
    <li>'SUGGEST' is for a list of reasons to accept or reject patron suggestions. It appears when managing suggestions.</li>
31
</li>
31
    <li>'WITHDRAWN' is for a description of a withdrawn item. It appears when adding or editing an item.</li>
32
	<li>Bsort2
33
<ul>
34
	<li>Used for patron statistical purposes</li>
35
</ul>
36
</li>
37
	<li>CART
38
<ul>
39
	<li>Is the shelving cart location, used by InProcessingToShelvingCart and ReturnToShelvingCart</li>
40
</ul>
41
</li>
42
	<li>CCODE
43
<ul>
44
	<li>Collection codes (appears when cataloging and working with items)</li>
45
</ul>
46
</li>
47
	<li>DAMAGED
48
<ul>
49
	<li>Descriptions for items marked as damaged (appears when cataloging and working with items)</li>
50
</ul>
51
</li>
52
	<li>HINGS_AS
53
<ul>
54
       <li>General Holdings: Acquisition Status Designator :: This data element specifies acquisition status for the unit at the time of the holdings report.a</li>
55
</ul>
56
</li>
57
	<li>HINGS_C
58
<ul>
59
     <li>General Holdings: Completeness Designator</li>
60
</ul>
61
</li>
62
	<li>HINGS_PF
63
<ul>
64
      <li>Physical Form Designators</li>
65
</ul>
66
</li>
67
	<li>HINGS_RD
68
<ul>
69
      <li>General Holdings: Retention Designator :: This data element specifies the retention policy for the unit at the time of the holdings report.</li>
70
</ul>
71
</li>
72
	<li>HINGS_UT
73
<ul>
74
    <li>General Holdings: Type of Unit Designator</li>
75
</ul>
76
</li>
77
	<li>LOC
78
<ul>
79
	<li>Shelving location (usually appears when adding or editing an item)</li>
80
</ul>
81
</li>
82
	<li>LOST
83
<ul>
84
	<li>Descriptions for the items marked as lost (appears when adding or editing an item)</li>
85
	<li>Values given to lost statuses should be numeric and not alphabetical in order for statuses to appear properly</li>
86
</ul>
87
</li>
88
	<li>MANUAL_INV
89
<ul>
90
	<li>Values for manual invoicing types</li>
91
</ul>
92
</li>
93
	<li>NOT_LOAN
94
<ul>
95
	<li>Reasons why a title is not for loan</li>
96
</ul>
97
</li>
98
	<li>PROC
99
<ul>
100
	<li>The location to be used for NewItemsDefaultLocation (change description as desired), also the location expected by InProcessingToShelvingCart.</li>
101
</ul>
102
</li>
103
	<li>RESTRICTED
104
<ul>
105
	<li>Restricted status of an item</li>
106
</ul>
107
</li>
108
	<li>SUGGEST
109
<ul>
110
	<li>List of patron suggestion reject or accept reasons (appears when managing suggestions)</li>
111
</ul>
112
</li>
113
	<li>WITHDRAWN
114
<ul>
115
	<li>Description of a withdrawn item (appears when adding or editing an item)</li>
116
</ul>
117
</li>
118
</ul>
32
</ul>
119
33
120
<h2>Add new Authorized Value Category</h2>
34
<h2>Add New Authorized Value Category</h2>
121
35
122
<p>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:</p>
36
<p>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:</p>
123
37
124
<ul>
38
<ul>
125
  <li>Click 'New Category'</li>
39
    <li>Click 'New Category.'</li>
126
  <li>Limit your Category to 11 characters (something short to make it clear what the category is for)</li>
40
    <li>Limit your Category to eleven characters (something short to make it clear what the category is for).</li>
127
	<li>When adding a new category you're asked to create at least one authorized value
41
    <li>When adding a new category, you're asked to create at least one authorized value:
128
<ul>
42
<ul>
129
    <li>Enter a code for your Authorized Value into the 'Authorized value' field</li>
43
    <li>Enter a code for your Authorized Value into the 'Authorized value' field.</li>
130
      <li>Use the Description field for the actual value that will be entered</li>
44
    <li>Use the Description field for the actual value that will be entered.</li>
131
</ul>
45
</ul>
132
</li>
46
</li>
133
	<li>Click 'Save'</li>
47
    <li>Click 'Save.'</li>
134
        <li>Your new category and value will appear on the list of Authorized Values</li>
48
    <li>Your new category and value will appear on the list of Authorized Values.</li>
135
</ul>
49
</ul>
136
50
137
<h2>Add new Authorized Value</h2>
51
<h2>Add New Authorized Value</h2>
138
52
139
<p>New authorized values can be added to any existing or new category. To add a value:</p>
53
<p>New authorized values can be added to any existing or new category. To add a value:</p>
140
54
141
<ul>
55
<ul>
142
	<li>Click 'New authorized value for ...'</li>
56
	<li>Click 'New authorized value for ...'</li>
143
    <li>Enter a code for your Authorized Value into the 'Authorized value' field</li>
57
    <li>Enter a code for your Authorized Value into the 'Authorized value' field.</li>
144
      <li>Use the Description field for the actual value that will be entered</li>
58
    <li>Use the Description field for the actual value that will be entered.</li>
145
	<li>Click 'Save'</li>
59
    <li>Click 'Save.'</li>
146
	<li>The new value will appear in the list along with existing values</li>
60
    <li>The new value will appear in the list along with existing values.</li>
147
</ul>
61
</ul>
148
62
149
<p><strong>See the full documentation for Authorized Values in the <a href="http://manual.koha-community.org/3.8/en/basicparams.html#authorizedvalues">manual</a> (online).</strong></p>
63
<p><strong>See the full documentation for Authorized Values in the <a href="http://manual.koha-community.org/3.8/en/basicparams.html#authorizedvalues">manual</a> (online).</strong></p>
150
64
151
[% INCLUDE 'help-bottom.inc' %]
65
[% INCLUDE 'help-bottom.inc' %]
(-)a/koha-tmpl/intranet-tmpl/prog/en/modules/help/admin/authtypes.tt (-4 / +3 lines)
Lines 1-11 Link Here
1
[% INCLUDE 'help-top.inc' %]
1
[% INCLUDE 'help-top.inc' %]
2
2
3
<h1>Authority types</h1>
3
<h1>Authority Types</h1>
4
4
5
<p>Authority Types are basically MARC Frameworks for Authority records and because of that the rules below refer to the bibliographic frameworks.</p>
5
<p>Authority Types are MARC Frameworks for Authority records. Therefore, the rules below refer to the bibliographic frameworks.</p>
6
6
7
<p>Koha comes with many of the necessary Authority frameworks already installed.</p>
7
<p>Koha comes with many of the necessary Authority frameworks already installed.</p>
8
8
9
<p><strong>See the full documentation for Authorities in the <a href="http://manual.koha-community.org/3.8/en/catadmin.html#authoritiesadmin">manual</a> (online).</strong></p>
9
<p><strong>See the full documentation for Authorities in the <a href="http://manual.koha-community.org/3.8/en/catadmin.html#authoritiesadmin">manual</a> (online).</strong></p>
10
10
11
[% INCLUDE 'help-bottom.inc' %]
11
[% INCLUDE 'help-bottom.inc' %]
12
- 

Return to bug 7936