</row>\r
<row>\r
<entry>\r
- <link linkend="report-introduction">Reports</link>\r
+ Reports\r
</entry>\r
<entry>Generate reports on any field in the Evergreen database</entry> \r
</row>\r
</row>\r
<row>\r
<entry>\r
- <link linkend="transit">Transit List</link>\r
+ Transit List\r
</entry>\r
<entry>View items in transit to or from your library during selected date\r
range</entry> \r
<para>There are also options in the <guilabel>Copy Editor</guilabel> for a copy to be\r
<guilabel>OPAC Visible</guilabel>-yes or no, <guilabel>Holdable</guilabel>-yes or no,\r
or <guilabel>Circulate</guilabel>-yes or no. If either the copy record or the shelving\r
- location is set to Circulate-no, then the item will not be able to circulate. See <xref\r
- linkend="add"/> for more about the <guilabel>Copy Editor.</guilabel></para>\r
+ location is set to Circulate-no, then the item will not be able to circulate.</para>\r
</tip>\r
<informalfigure>\r
<para>This is where you see the shelving locations in the <guilabel>Copy\r
<entry>Sets language used in staff client</entry>\r
<entry><link linkend="lsa-data-types">Text</link> (dollars)</entry>\r
\r
- <entry>Can be set for each workstation at <link linkend="intro-login"\r
- >login</link></entry>\r
+ <entry>Can be set for each workstation at login</entry>\r
</row>\r
\r
<row xml:id="lsa-do-not-automatically-delete">\r
<procedure>\r
\r
<step>\r
- <para>Open the <guilabel>Organizational Units</guilabel> interface as described in the steps\r
- <link linkend="server-main">above</link>.</para>\r
+ <para>Open the <guilabel>Organizational Units</guilabel> interface.</para>\r
</step>\r
<step>\r
<informalfigure>\r
<simplesect>\r
<title>Indexed-field Weighting<indexterm><primary>relevancy</primary><secondary>indexed-field weighting</secondary></indexterm> </title>\r
<para>Indexed-field weighting is configured in the Evergreen database in the weight column\r
- of the <link linkend="config.metabib_field">config.metabib_field</link> table, which follows the other four columns in this table:\r
+ of the <link linkend="config.table.metabib-field">config.metabib_field</link> table, which follows the other four columns in this table:\r
field_class, name, xpath, and format.</para>\r
- <para>The following is one representative line from the <link linkend="config.metabib_field">config.metabib_field</link> table:</para>\r
+ <para>The following is one representative line from the <link linkend="config.table.metabib-field">config.metabib_field</link> table:</para>\r
<screen> author | conference | //mods32:mods/mods32:name[@type='conference']/mods32:namePart[../mods32:role/mods32:roleTerm[text()='creator']] | mods32 | 1 ) </screen>\r
<para>The default value for index-field weights in config.metabib_field is 1. Adjust the\r
weighting of indexed fields to boost or lower the relevance score for matches on that\r
<para> Searching the out of the box <emphasis>keyword</emphasis> does not boost the ranking for terms appearing in, the title or subject fields since there is just one \r
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 \r
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 \r
- <link linkend="config.metabib_field">config.metabib_field</link> table. The following procedure will add a keyword|title index so that terms found in the title field of an \r
+ <link linkend="config.table.metabib-field">config.metabib_field</link> table. The following procedure will add a keyword|title index so that terms found in the title field of an \r
item are given more weight than terms in other fields. </para>\r
<procedure>\r
<step>\r
INSERT INTO metabib.keyword_field_entry \r
(source, field, value)\r
SELECT source, 17, value (the field value, 17, field be different in your database so you may need to check the \r
- <link linkend="config.metabib_field">config.metabib_field</link> for the id of your new index).\r
+ <link linkend="config.table.metabib-field">config.metabib_field</link> for the id of your new index).\r
FROM metabib.title_field_entry\r
WHERE field = 6;\r
</programlisting>\r
<step> \r
<para>Bump the relevance when the first search term appears first in the title in a keyword search.</para>\r
<para>17 = our new keyword|title index (This may be different in your database so you may need to check the \r
- <link linkend="config.metabib_field">config.metabib_field</link> for the id \r
+ <link linkend="config.table.metabib-field">config.metabib_field</link> for the id \r
of your new index).</para>\r
<programlisting>\r
INSERT INTO search.relevance_adjustment \r
<step>\r
<para>Boost the relevance for search terms appearing in the title in general</para>\r
<para>17 = our new keyword|title index (This may be different in your database so you may need to check the \r
- <link linkend="config.metabib_field">config.metabib_field</link> for the id \r
+ <link linkend="config.table.metabib-field">config.metabib_field</link> for the id \r
of your new index).</para>\r
<programlisting>\r
UPDATE config.metabib_field\r
</tbody>\r
</tgroup>\r
</informaltable>\r
- <simplesect xml:id="SIP_block_patron">\r
+ <simplesect xml:id="SIP_Block_Patron">\r
<title>01 Block Patron</title>\r
<para>A selfcheck will issue a <command>Block Patron</command> command if a patron leaves their card in a selfcheck machine or if the selfcheck detects tampering (such as attempts \r
to disable multiple items during a single item checkout, multiple failed pin entries, etc).</para><indexterm><primary>SelfCheck</primary></indexterm>\r
<title>25/26 Patron Enable</title>\r
<para>Not yet supported.</para>\r
</simplesect>\r
- <simplesect xml:id="sip_Renew">\r
+ <simplesect xml:id="SIP_Renew">\r
<title>29/30 Renew</title>\r
<para>Evergreen ACS status message indicates <emphasis>renew</emphasis> is supported.</para>\r
</simplesect>\r
projects / working / Evergreen.git / commitdiff