From: Robert Soulliere Date: Mon, 13 Sep 2010 19:50:14 +0000 (-0400) Subject: More semantic clean up and indexing. X-Git-Url: https://old-git.evergreen-ils.org/?a=commitdiff_plain;h=cd1eaca741f330181baec0770c728d45fde0e3c6;p=Evergreen-DocBook.git More semantic clean up and indexing. --- diff --git a/1.6/admin/serveradministration.xml b/1.6/admin/serveradministration.xml index 454d1b2..a6908aa 100644 --- a/1.6/admin/serveradministration.xml +++ b/1.6/admin/serveradministration.xml @@ -4,9 +4,9 @@ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="serveradministrati Server Administration - Administration of Evergreen involves configuration done from both the Staff Client as well a + Administration of Evergreen involves configuration done from both the Staff Client as well a the command line. The goal of this chapter is to provide you with the procedures to help - you optimize your Evergreen system. + you optimize your Evergreen system.
@@ -58,7 +58,7 @@ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="serveradministrati Deleting Organization Types<indexterm><primary>organization types</primary><secondary>deleting</secondary></indexterm> - Select the organization type from the Organization Type + Select the organization type from the Organization Type tree. Click Delete. Click OK on the warning alert box. @@ -71,7 +71,7 @@ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="serveradministrati Editing Organization Types<indexterm><primary>organization types</primary><secondary>editing</secondary></indexterm> - Select the organization type you wish to edit from the + Select the organization type you wish to edit from the organization type tree. Make the changes in the right pane. Click Save to save your changes. @@ -95,7 +95,7 @@ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="serveradministrati Adding Organizational Units<indexterm><primary>organization units</primary><secondary>adding</secondary></indexterm> - Select an Organizational Unit from the organizational unit tree on the left and click + Select an Organizational Unit from the organizational unit tree on the left and click New Child. Make sure your new unit is selected and edit the Organizational Unit Name, Organizational Unit Policy Code, @@ -1607,7 +1607,7 @@ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="serveradministrati Click Add. Locate you new status and check the Holdable check box if you wish to all users to place holds on items in this status. Check - OPAC Visible if you wish for this status to appear in the public + OPAC Visible if you wish for this status to appear in the public OPAC. Click Save Changes at the bottom of the screen to save changes to the new status. @@ -1626,7 +1626,7 @@ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="serveradministrati Editing Copy Statuses Double click on a status name to change its name and enter the new name. To change whether a status is visible in the OPAC, check or uncheck - the OPAC Visible check box.To allow patrons the ability to + the OPAC Visible check box.To allow patrons the ability to hold items in that status, check the Holdable check box. To prevent users from holding items in that status, uncheck the Holdable check box. @@ -1644,8 +1644,8 @@ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="serveradministrati Adding Billing Types Click New Billing Type. Enter the name of the billing type. - Select the Org Unit to use this billing type. - Enter the Default Price. This is only the default since + Select the Org Unit to use this billing type. + Enter the Default Price. This is only the default since the actual price of a specific billing can be adjusted when staff create a billing Click Save to save the new billing type. @@ -1661,8 +1661,8 @@ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="serveradministrati Editing Billing Types Double click on a billing types to open the editing window. - Make desired changes to the name, - Org Unit and Default Price. + Make desired changes to the name, + Org Unit and Default Price. Once you have finished editing, click Save. @@ -1680,9 +1680,9 @@ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="serveradministrati Adding Circulation Modifiers Click New Circ Modifier. - Enter a Code, Name and - Description. - Select the SIP 2 Media Type. + Enter a Code, Name and + Description. + Select the SIP 2 Media Type. Check the Magnetic Media check box if the item is magnetic media such as a cassette tape. Click Save to save the new circulation @@ -1714,24 +1714,65 @@ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="serveradministrati Create a marc template in the directory /openils/var/templates/marc/. It should be in xml format. - Here is an example file k_video.xml: + Here is an example file k_book.xml: - - - Catalog Template Example - - - - - + + + 00620cam a2200205Ka 4500 + 070101s eng d + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + ]]> + - Add the template to the to the marctemplates list in the open-ils.cat section of the evergreen configuration file opensrf.xml + Add the template to the to the marctemplates list in the open-ils.cat section of the Evergreen configuration file + opensrf.xmlconfiguration filesopensrf.xml - Restart perl services for changes to take effect. - /openils/bin/osrf_ctl.sh -l -a restart_perl + Restart PerlPerl services for changes to take effect. + /openils/bin/osrf_ctl.sh -l -a restart_perl
@@ -1751,10 +1792,10 @@ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="serveradministrati Indexed-field Weighting<indexterm><primary>relevancy</primary><secondary>indexed-field weighting</secondary></indexterm> Indexed-field weighting is configured in the Evergreen database in the weight column - of the config.metabib_field table, which follows the other four columns in this table: + of the config.metabib_field table, which follows the other four columns in this table: field_class, name, xpath, and format. - The following is one representative line from the config.metabib_field table: - author | conference | //mods32:mods/mods32:name[@type='conference']/mods32:namePart[../mods32:role/mods32:roleTerm[text()='creator']] | mods32 | 1 ) + The following is one representative line from the config.metabib_field table: + author | conference | //mods32:mods/mods32:name[@type='conference']/mods32:namePart[../mods32:role/mods32:roleTerm[text()='creator']] | mods32 | 1 ) The default value for index-field weights in config.metabib_field is 1. Adjust the weighting of indexed fields to boost or lower the relevance score for matches on that indexed field. The weight value may be increased or decreased by whole integers. @@ -1769,7 +1810,7 @@ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="serveradministrati and is configured through floating-point multipliers in the multiplier column of the search.relevance_adjustment table. Weighting can be adjusted for one, more, or all multiplier fields in - search.relevance_adjustment. + search.relevance_adjustment. You can adjust the following three matchpoints: @@ -1960,12 +2001,12 @@ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="serveradministrati Searching the out of the box keyword does not boost the ranking for terms appearing in, the title or subject fields since there is just one keyword index which does not distinguish terms that appear in the title field from those in the notes field for example. In comparison, the title index is actually composed of a number of separate indexes: title|proper, title|uniform, title|alternative, title|translated, etc, that collectively form the title index. You can see this in the - config.metabib_field table. The following procedure will add a keyword|title index so that terms found in the title field of an item are given more weight than terms in - other fields. + config.metabib_field table. The following procedure will add a keyword|title index so that terms found in the title field of an + item are given more weight than terms in other fields. From the command line, access the PostgreSQL command line interface - psql -U evergreen + psql -U evergreen Clone the title|proper index to create a keyword|title index @@ -1985,14 +2026,15 @@ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="serveradministrati INSERT INTO metabib.keyword_field_entry (source, field, value) SELECT source, 17, value (the field value, 17, field be different in your database so you may need to check the - config.metabib_field for the id of your new index). + config.metabib_field for the id of your new index). FROM metabib.title_field_entry WHERE field = 6; Bump the relevance when the first search term appears first in the title in a keyword search. - 17 = our new keyword|title index (This may be different in your database so you may need to check the config.metabib_field for the id + 17 = our new keyword|title index (This may be different in your database so you may need to check the + config.metabib_field for the id of your new index). INSERT INTO search.relevance_adjustment @@ -2002,7 +2044,8 @@ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="serveradministrati Boost the relevance for search terms appearing in the title in general - 17 = our new keyword|title index (This may be different in your database so you may need to check the config.metabib_field for the id + 17 = our new keyword|title index (This may be different in your database so you may need to check the + config.metabib_field for the id of your new index). UPDATE config.metabib_field