<!-- TMPL_INCLUDE NAME="help-top.inc" -->
-
- <h1>Authority types</h1>
- <p>You can define as many Authority types as you want.</p>
- <ul>
- <li>with the MARC structure button, you can define the MARC structure of a given authority type</li>
- <li>The tag reported must contain a MARC tag number. Every subfield in the selected tag will be copied to the "destination tag" in the biblio. for example, in UNIMARC, the tag 200 ot personal authority will be reported to 600, 700, 701, depending on what is cliqued in the biblio MARC editor.</li>
- <li>The summary contains an "ISBD" like description to explain how the entry must be shown in the result list. The syntax is :
- <ul>
- <li>[xxxFFFSyyy] where xxx are up to 3 digits BEFORE the field, FFF the field number, S the subfield code, yyy up to 3 digits AFTER the field.</li>
- <li>things outside [] are kept as is (including HTML)</li>
- <li>repeatable fields are managed.</li>
- <ul>
- </ul>
- <p>IMPORTANT</p>
- <p>
- In the biblio framework, the reported tag <b>MUST</b> contain a $9 subfield, activated in the tab where the tag is, and hidden (hidden maybe omitted, but the field has no reason to appear anywhere). The $9 subfield in the biblio will contain the Authority number (the internal Koha number)
- </p>
-
-<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
+ <h1>Authority types</h1> <p>You can define as many Authority types as you want.</p> <ul> <li>with the MARC structure button, you can define the MARC structure of a given authority type</li> <li>The tag reported must contain a MARC tag number. Every subfield in the selected tag will be copied to the "destination tag" in the biblio. for example, in UNIMARC, the tag 200 ot personal authority will be reported to 600, 700, 701, depending on what is cliqued in the biblio MARC editor.</li> <li>The summary contains an "ISBD" like description to explain how the entry must be shown in the result list. The syntax is : <ul> <li>[xxxFFFSyyy] where xxx are up to 3 digits BEFORE the field, FFF the field number, S the subfield code, yyy up to 3 digits AFTER the field.</li> <li>things outside [] are kept as is (including HTML)</li> <li>repeatable fields are managed.<ul> </ul></li> <p>IMPORTANT</p> <p> In the biblio framework, the reported tag <strong>MUST</strong> contain a $9 subfield, activated in the tab where the tag is, and hidden (hidden maybe omitted, but the field has no reason to appear anywhere). The $9 subfield in the biblio will contain the Authority number (the internal Koha number) </p></ul></li></ul><h1 id="v65u"><font size="4" id="pok7"><font id="j73r"><font id="dtv:1" color="#990000"><font id="hd0y" color="#000000">Create Authority Types<br /></font></font></font></font></h1>Create and manage Authorities frameworks that define the characteristics of your MARC Records (field and subfield definitions).<br /><br />To create a new framework...<br /> <br /> <ul><li> Go to the 'Administration' module. </li><li> Select 'Authority types'</li><li>Click 'New Authority Framework'</li><li>Fill in the fields that describe your new authority type<br /><ul><li><span style="background-color: #ffe599">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</span></li></ul></li><li>Click 'Submit'</li><li>To update the MARC Framework for your new authority type, click 'MARC structure' next to the authority</li><li>From the following screen you can alter fields, subfields and add additional tags</li><li>By clicking on the 'edit' link you will be able to alter information related to the field</li><li>By clicking the 'subfields' link you will be able to alter all of the subfields associated with that field</li><li>By clicking 'Edit subfields' at the bottom of the screen you can alter the information for each subfield</li><li>After making your changes, click 'Save Changes' at the top of the screen</li><li>To delete a subfield, just click the 'delete' link next to the field you'd like to edit</li></ul>
+<!-- TMPL_INCLUDE NAME="help-bottom.inc" -->
<!-- TMPL_INCLUDE NAME="help-top.inc" -->
-
-<h1>Help: Library Branches</h1>
-
-<p>Fill in information about your library service outlets on this page.</p>
-
-<p>Begin by defining your branch categories. If, for example, you have one main library and several branch libraries, you might set up an "M" (Main) category and a "B" (Branch) category, with descriptions "Main Library" and "Branch Library."</p>
-
-<p>Now add the names and addresses, phone numbers, etc of your libraries in the "Branches" section. (All of your libraries should be described here, not just the branch libraries.) Give each library a unique and easily-remembered code (maximum of four characters). This code will be used in Koha's database to identify each library. When libraries are listed in Koha, they will be listed in alphabetical order by code. (Note that until you set your branch the first time you use a computer to circulate items in Koha, the branch will default to the first library in the alphabetical code list -- be careful to set the branch the first time you use Koha or whenever you add a new computer!)</p>
-
-<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
+<h1>Library Branches</h1> <p>Fill in information about your library service outlets on this page.</p> <p>Begin by defining your branch categories. If, for example, you have one main library and several branch libraries, you might set up an "M" (Main) category and a "B" (Branch) category, with descriptions "Main Library" and "Branch Library."</p> <p>Now add the names and addresses, phone numbers, etc of your libraries in the "Branches" section. (All of your libraries should be described here, not just the branch libraries.) Give each library a unique and easily-remembered code (maximum of four characters). This code will be used in Koha's database to identify each library. When libraries are listed in Koha, they will be listed in alphabetical order by code. </p>
+<!-- TMPL_INCLUDE NAME="help-bottom.inc" -->
<!-- TMPL_INCLUDE NAME="help-top.inc" -->
-
-<h1>MARC Check</h1>
-<p>Once you have completed the process of setting up your MARC tag structure (MarcTagstruct) and checked your MARC to Koha mapping (TransformKohaToMarcLinks), click on this link to activate a small program that checks for major errors in your MARC setup.</p>
-
-<p>This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays, etc. -- it simply checks for major errors. You will probably revise your MARC setup several times before you are completely pleased with it. Be sure to run checkmarc after every revision.</p>
-
-<!-- TMPL_INCLUDE name="help-bottom.inc" -->
\ No newline at end of file
+<h1>MARC Bibliographic Framework Test</h1> <p>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.</p> <p>This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays, etc. -- it simply checks for major errors. You will probably revise your MARC setup several times before you are completely pleased with it. Be sure to run the MARC Bibliographic Framework Test after every revision.</p>
+<!-- TMPL_INCLUDE NAME="help-bottom.inc" -->
<!-- TMPL_INCLUDE NAME="help-top.inc" -->
-<h1>Serials Claims</h1><h2>What are Claims?</h2> <p>Claims are where an issue that was expected has not been received by the library. The claims interface is used to manage those claims, in particular provide the expected issue information that can be sent to the supplier. </p> <h2>How to lodge a Claim?</h2> <p>Make a selection from the drop down list. The "All Suppliers" count gives you a count of the total number of current item claims across all suppliers. </p><p>There are two ways to lodge a claim with the supplier:</p><ol><li>Using a Letter defined in Notices. Note that you will need to set up the notice. </li><li>Exporting the claims information. This downloads a CSV file to your local machine with all the claim data ready for additional formatting before sending to the supplier.</li></ol><h2>How to resolve a Claim?</h2> <p>The claim will be resolved once received status has changed. Search for the Subscription and then click "Serial receive" to locate the issue and change it's status. </p>
+<h1>Serials Claims</h1><h2>What are Claims?</h2> <p>Claims are notices that you send when an issue that was expected has not been received by the library.</p> <h2>How to lodge a Claim?</h2> <p>Make a selection from the drop down list. The "All Suppliers" count gives you a count of the total number of current item claims across all suppliers. </p><p>There are two ways to lodge a claim with the supplier:</p><ol><li>Using a Letter defined in Notices. Note that you will need to set up the notice. </li><li>Exporting the claims information. This downloads a CSV file to your local machine with all the claim data ready for additional formatting before sending to the supplier.</li></ol><h2>How to resolve a Claim?</h2> <p>The claim will be resolved once received status has changed. Search for the Subscription and then click "Serial receive" to locate the issue and change it's status. </p>
<!-- TMPL_INCLUDE NAME="help-bottom.inc" -->
projects / koha_gimpoz / commitdiff