From 5ea8572747dd82677193117ad748795f85b67b74 Mon Sep 17 00:00:00 2001
From: tgarip1957 <tgarip1957>
Date: Fri, 19 May 2006 23:09:04 +0000
Subject: [PATCH] New help file for authority MARC structuring

---
 .../help/admin/auth_subfields_structure.tmpl  | 34 +++++++++++++++++++
 1 file changed, 34 insertions(+)
 create mode 100644 koha-tmpl/intranet-tmpl/prog/en/help/admin/auth_subfields_structure.tmpl

diff --git a/koha-tmpl/intranet-tmpl/prog/en/help/admin/auth_subfields_structure.tmpl b/koha-tmpl/intranet-tmpl/prog/en/help/admin/auth_subfields_structure.tmpl
new file mode 100644
index 0000000000..68d3edae93
--- /dev/null
+++ b/koha-tmpl/intranet-tmpl/prog/en/help/admin/auth_subfields_structure.tmpl
@@ -0,0 +1,34 @@
+<!-- TMPL_INCLUDE NAME="doc-head-open.inc" -->Online Help: System Preferences -- Authorities MARC tag structure administration<!-- TMPL_INCLUDE NAME="doc-head-close.inc" -->
+<div id="main-compact">
+<h1>MARC tag structure administration</h1>
+<p>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.</p>
+<p>You can define as the marc tag structure for each biblio framework you have defined</p>
+
+<p>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.</p>
+
+<p>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.</p>
+<p>For each subfield you can set :</p>
+<ul>
+<li>repeatable : wether 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</li>
+<li>Mandatory : wether the field is mandatory or not. If mandatory, the cataloger can't validate the biblio if the subfield is empty.</li>
+<li>Search also : a list of field that Koha will also search on when the user do a search on the subfield</li>
+<li>Koha link : <b>very important</b>. 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).</li>
+<li>Text for librarian : what appears before the subfield in the librarian interface</li>
+<li>Text for OPAC : what appears before the field in the OPAC. If empty, the text for librarian is used instead</li>
+<li>Managed in tab : deals with the tab where the subfield is shown. Ignore means that the subfield is not managed. </li>
+<li>hidden : allows you to select possible visibility conditions. Each section OPAC INTRANET or Editor can be set separately:</li>
+<li><b>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 :</b>
+<li>URL : if checked, the subfield is an URL, and can be clicked</li>
+<li>Auth value : means the value is not free, but in the authorised value list of the selected type</li>
+<li>thesaurus : shows the authority type</li>
+<li>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)</li>
+<li>
+<li><b>Example MARC21 Subject Headings Authority</b>
+<ul>Use field 035$a for your auth_header.authid and 035$8 for auth_header.authtypecode. Make sure your zebra authorities index these fields</ul>
+<ul>Use field 150 for your subject headings</ul>
+<ul>Use field 750$9 (add subfield if not present) for auth_header.linkid . Select <b>Is a linking field</b>. You may use any subfield for linking as $9 is not hardcoded
+<ul>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</u>
+</li>
+</ul>
+
+<!-- TMPL_INCLUDE name="help-bottom.inc" -->
-- 
2.39.5