1 <?xml version='1.0' encoding='UTF-8'?>
\r
2 <chapter xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"
\r
3 xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="serveradministration">
\r
5 <title>Server Administration</title>
\r
7 <para>Administration of <application>Evergreen</application> involves configuration done from both the Staff Client as well a
\r
8 the command line. The goal of this chapter is to provide you with the procedures to help
\r
9 you optimize your <application>Evergreen</application> system.</para>
\r
12 <section xml:id="orgunitsandtypes">
\r
13 <title>Organizational Unit Types and Organizational Units</title>
\r
14 <simplesect xml:id="orgtypes">
\r
15 <title>Organizational Unit Types</title>
\r
16 <indexterm><primary>organizational unit types</primary></indexterm>
\r
17 <para>Organizational Unit Types are the terms used to refer to levels in the hierarchy of your
\r
18 library system(s). Examples could include>All-Encompassing Consortium, Consortium Within a
\r
19 Consortium, Library System, Branch, Bookmobile, Sub-Branch, Twig, etc.</para>
\r
20 <para>You can add or remove organizational unit types, and rename them as needed to match the
\r
21 organizational hierarchy that exists in reality for the libraries using your installation of
\r
22 Evergreen. Evergreen can support organizations as simple as a single library with one or more
\r
23 branches or as complex as a consortium composed of many independently governed library
\r
24 systems. Organizational unit types should never have proper names since they are only generic types .</para>
\r
25 <tip><para>It is a good idea to set up all of your organizational types and units before loading other data. In many cases, editing or deleting organizational units and types
\r
26 may be difficult once you have loaded records or users. </para></tip>
\r
27 <para>The fields in the organizational unit type record include:</para>
\r
29 <listitem><guilabel>Type Name</guilabel> - The name of the organization unit type.</listitem>
\r
30 <listitem><guilabel>Opac Label</guilabel> - This is the label displayed in the OPAC to describe the search
\r
31 range and the copy count columns for results. They are <emphasis>range
\r
32 relative</emphasis> labels.</listitem>
\r
34 <listitem><guilabel>Parent Type</guilabel> - The parent organizational unit type of this type.</listitem>
\r
35 <listitem><guilabel>Can Have Volumes</guilabel> - Flag that allows an organizational unit of this type to contain
\r
36 Volumes/Call Numbers and thus Copies.</listitem>
\r
37 <listitem><guilabel>Can Have Users</guilabel> - Flag that allows an Organizational unit of this type to be home to
\r
40 <para>An organizational unit type can be added, edited, or removed using the staff client.</para>
\r
41 <para>To navigate to the <emphasis>Organization Unit Types</emphasis> from the staff client select
\r
43 <guimenu>Admin</guimenu>
\r
44 <guisubmenu>Server Administration</guisubmenu>
\r
45 <guisubmenu>Organization Types</guisubmenu>
\r
49 <title>Adding Organization Types<indexterm><primary>organizational unit types</primary><secondary>adding</secondary></indexterm></title>
\r
50 <step><para>Select an organization type from the organization type tree on the left and
\r
51 click <guibutton>New Child</guibutton>.</para></step>
\r
52 <step><para>Make sure your new type is selected and edit the <guilabel>Type Name</guilabel>,
\r
53 <guilabel>OPAC Label</guilabel> and <guilabel>Parent Type</guilabel>.</para></step>
\r
54 <step><para>Change the <guilabel>Parent Type</guilabel> if necessary.</para></step>
\r
55 <step><para>Check the <guilabel>Can Have Volumes and Copies</guilabel> check box if the
\r
56 organization units of this type will have volumes and copies assigned to it.</para></step>
\r
57 <step><para>Check the <guilabel>Can Have Users</guilabel> check box if you will allow users
\r
58 to be have the organization units of this type as their home unit.</para></step>
\r
59 <step><para>Click <guibutton>Save</guibutton> to save your new organization type.
\r
61 <step><para>From the server command line, run autogen to apply the changes to the database and scripts. Run the following command as the opensrf user:</para>
\r
63 <userinput>/openils/bin/autogen.sh -c /openils/conf/opensrf_core.xml -u</userinput>
\r
67 <para>As root, restart the Apache server:</para>
\r
69 <userinput>/etc/init.d/apache2 restart</userinput>
\r
72 <step><para>The staff client will need to be restarted for changes to appear.</para>
\r
76 <title>Deleting Organization Types</title>
\r
77 <indexterm><primary>organizational unit types</primary><secondary>deleting</secondary></indexterm>
\r
78 <step><para>Select the <guilabel>organization type</guilabel> from the <guilabel>Organization Type</guilabel>
\r
80 <step><para>Click <guibutton>Delete</guibutton>.</para></step>
\r
81 <step><para>Click <guibutton>OK</guibutton> on the warning alert box.</para></step>
\r
82 <step><para>From the server command line, run autogen to apply the changes to the database and scripts. Run the following command as the opensrf user:</para>
\r
84 <userinput>/openils/bin/autogen.sh -c /openils/conf/opensrf_core.xml -u</userinput>
\r
88 <para>As root, restart the Apache server:</para>
\r
90 <userinput>/etc/init.d/apache2 restart</userinput>
\r
93 <step><para>The staff client will need to be restarted for changes to appear.</para>
\r
96 <para>You will not be able to delete organization types if organization units are
\r
97 assigned to that type. Before you can delete the organization
\r
98 Type, you must change the organization type of the units associated with the type
\r
99 or delete the units.</para>
\r
104 <title>Editing Organization Types<indexterm><primary>organizational unit types</primary><secondary>editing</secondary></indexterm></title>
\r
105 <step><para>Select the <guilabel>organization type</guilabel> you wish to edit from the
\r
106 organization type tree.</para></step>
\r
107 <step><para>Make the changes in the right pane.</para></step>
\r
108 <step><para>Click <guibutton>Save</guibutton> to save your changes.</para></step>
\r
109 <step><para>From the server command line, run autogen to apply the changes to the database and scripts. Run the following command as the opensrf user:</para>
\r
111 <userinput>/openils/bin/autogen.sh -c /openils/conf/opensrf_core.xml -u</userinput>
\r
115 <para>As root, restart the Apache server:</para>
\r
117 <userinput>/etc/init.d/apache2 restart</userinput>
\r
120 <step><para>The staff client will need to be restarted for changes to appear.</para>
\r
125 <simplesect xml:id="orgunits">
\r
126 <title>Organizational Units</title>
\r
127 <indexterm><primary>organizational units</primary></indexterm>
\r
129 <para>Organizational Units are the specific instances of the organization unit types that
\r
130 make up your library's hierarchy. These can include consortia, systems, branches,
\r
131 etc. The organizational units should have distinctive proper names such as
\r
132 <emphasis>Main Street Branch</emphasis> or <emphasis>Townsville Campus</emphasis>.</para>
\r
134 <para>To navigate to the organizational units administration page in the staff client select
\r
136 <guimenu>Admin</guimenu>
\r
137 <guisubmenu>Server Administration</guisubmenu>
\r
138 <guisubmenu>Organizational Units</guisubmenu>
\r
142 <title>Adding Organizational Units</title>
\r
143 <indexterm><primary>organization units</primary><secondary>adding</secondary></indexterm>
\r
144 <step><para>Select an <guilabel>Organizational Unit</guilabel> from the organizational unit tree on the left and click
\r
145 <guibutton>New Child</guibutton>.</para></step>
\r
146 <step><para>Make sure your new unit is selected and edit the <guilabel>Organizational Unit
\r
147 Name</guilabel>, <guilabel>Organizational Unit Policy Code</guilabel>,
\r
148 <guilabel>Main Email Address</guilabel> and <guilabel>Main Phone Number</guilabel>.</para>
\r
150 <para>The <emphasis>Organizational Unit Name</emphasis> is the name that will appear in the
\r
151 OPAC. The <emphasis>Policy Code</emphasis> is used by the system to associate policies and
\r
152 copies with the unit.</para>
\r
155 <step><para>Select the <guilabel>Organization Unit Type</guilabel> and
\r
156 <guilabel>Parent Organization Unit</guilabel>.</para></step>
\r
157 <step><para>Check the <guilabel>Can Have Volumes and Copies</guilabel> check box if the
\r
158 organization units of this type will have volumes and copies assigned to it.<indexterm><primary>organization units</primary><secondary>volumes
\r
159 and copies</secondary></indexterm></para></step>
\r
160 <step><para>Check the <guilabel>OPAC Visible</guilabel> check box if you want this location to be
\r
161 visible in the OPAC for searching.<indexterm><primary>Organization Units</primary><secondary>opac visible</secondary></indexterm></para></step>
\r
162 <step><para>Click <guibutton>Save</guibutton> to save your new organizational unit.</para></step>
\r
163 <step><para>From the server command line, run autogen to apply the changes to the database and scripts. Run the following command as the opensrf user:</para>
\r
165 <userinput>/openils/bin/autogen.sh -c /openils/conf/opensrf_core.xml -u</userinput>
\r
169 <para>As root, restart the Apache server:</para>
\r
171 <userinput>/etc/init.d/apache2 restart</userinput>
\r
175 <para>As root, restart the Apache server:</para>
\r
177 <userinput>/etc/init.d/apache2 restart</userinput>
\r
180 <step><para>The staff client will need to be restarted for changes to appear.</para>
\r
184 <title>Deleting Organizational Units</title>
\r
185 <indexterm><primary>organization units</primary><secondary>deleting</secondary></indexterm>
\r
186 <step><para>Select the <emphasis>organizational unit</emphasis> you wish to delete from the organizational unit tree in the left pane.</para></step>
\r
187 <step><para>Click<guibutton>Delete</guibutton>.</para></step>
\r
188 <step><para>Click <guibutton>OK</guibutton> on the warning alert box.</para></step>
\r
190 <para>From the server command line, run autogen to apply the changes to the database and scripts. Run the following command as the opensrf user:</para>
\r
192 <userinput>/openils/bin/autogen.sh -c /openils/conf/opensrf_core.xml -u</userinput>
\r
196 <para>As root, restart the Apache server:</para>
\r
198 <userinput>/etc/init.d/apache2 restart</userinput>
\r
201 <step><para>The staff client will need to be restarted for changes to appear.</para>
\r
204 <para>You will not be able to delete organizational units if you have
\r
205 users, workstations or copies assigned to the unit. Before you can delete the
\r
206 organizational unit, you must move its users, workstations, copies and other associated resources to other
\r
207 organizational units.</para>
\r
211 <title>Changing the Default Organizational Units and Types Using SQL</title>
\r
212 <para>Evergreen comes with several default organizational units set up out-of-the-box. Most libraries will want to customize the Org units with their own Organizational Units and
\r
213 types. The quickest way to do this is with SQL.</para>
\r
214 <note><para>The following procedure should only be done before you have migrated users and items into your system.</para></note>
\r
216 <para>Delete all but the core organizational unit:</para>
\r
217 <programlisting language="sql">
\r
219 DELETE FROM actor.org_unit WHERE id > 1;
\r
220 DELETE FROM actor.org_address WHERE id > 1;
\r
221 DELETE FROM actor.workstation WHERE owning_lib > 1;
\r
226 <para>Clean up our org unit types, in preparation for creating the organizational units hierarchy:</para>
\r
227 <programlisting language="sql">
\r
229 DELETE FROM actor.org_unit_type WHERE id > 2;
\r
230 UPDATE actor.org_unit_type SET name = 'System', can_have_users = TRUE
\r
232 UPDATE actor.org_unit_type SET name = 'Branch', can_have_users = TRUE,
\r
233 can_have_vols = TRUE WHERE id = 2;
\r
238 <para>Create a branch that hangs off the only remaining parent branch setting the addresses to the system address temporarily:</para>
\r
239 <programlisting language="sql">
\r
240 INSERT INTO actor.org_unit (parent_ou, ou_type, ill_address,
\r
241 holds_address, mailing_address, billing_address, shortname, name)
\r
242 VALUES (1, 2, 1, 1, 1, 1, 'MYBRANCH', 'My Branch');
\r
246 <para>Find out what ID was assigned to the new branch:</para>
\r
247 <programlisting language="sql">
\r
248 SELECT id FROM actor.org_unit WHERE shortname = 'MYBRANCH';
\r
252 <para>Create our required org address and update <database class="table">actor.org_unit</database> to point ot correct <database class="table">actor.org_address</database> <database class="field">id</database> (assuming output of last step was <quote>101</quote>, adjust accordingly.):</para>
\r
253 <programlisting language="sql">
\r
255 INSERT INTO actor.org_address (id, org_unit, street1, city, state,
\r
256 country, post_code)
\r
257 VALUES (2, 101, 'Fake Street', 'Fake', 'Fake', 'Fake', 'FOO BAR');
\r
259 UPDATE actor.org_unit SET ill_address= 2, holds_address = 2,
\r
260 mailing_address = 2, billing_address = 2 WHERE id = 101;
\r
265 <para>Run autogen.sh for your changes to be updated.</para>
\r
267 <userinput>./autogen.sh -c /openils/conf/opensrf_core.xml -u</userinput>
\r
271 <para>As root, restart the Apache server:</para>
\r
273 <userinput>/etc/init.d/apache2 restart</userinput>
\r
278 <title>Editing Organizational Units<indexterm><primary>organization units</primary><secondary>editing</secondary></indexterm></title>
\r
279 <step><para>Select the organizational unit you wish to edit from the
\r
280 organizational unit tree in the left pane.</para></step>
\r
281 <step><para>Edit the fields in the right pane.</para></step>
\r
282 <step><para>Click <guibutton>Save</guibutton> to save your changes.</para></step>
\r
283 <step><para>From the server command line, run autogen to apply the changes to the database and scripts. Run the following command as the opensrf user:</para>
\r
285 <userinput>/openils/bin/autogen.sh -c /openils/conf/opensrf_core.xml -u</userinput>
\r
289 <para>As root, restart the Apache server:</para>
\r
291 <userinput>/etc/init.d/apache2 restart</userinput>
\r
295 <step><para>The staff client will need to be restarted for changes to appear.</para>
\r
300 <simplesect xml:id="server-hours">
\r
302 <title>Library Hours of Operation<indexterm><primary>hours of operation</primary><secondary>setting</secondary></indexterm></title>
\r
305 <para>Local System Administrators can use the <guilabel>Organizational Units</guilabel> interface to set the library's hours of operation. These are regular weekly hours;
\r
306 holiday and other closures are recorded in the <link linkend="lsa-closed">Closed Dates
\r
307 Editor</link>.</para>
\r
309 <para>Hours of operation and closed dates affect due dates and overdue fines.</para>
\r
314 <title>Due dates<indexterm><primary>hours of operation</primary><secondary>due dates policy</secondary></indexterm></title>
\r
315 <para>Due dates that would fall on closed days are automatically pushed forward to
\r
316 the next open day. Likewise, if an item is checked out at 8pm, for example, and
\r
317 would normally be due on a day when the library closes before 8pm, Evergreen
\r
318 pushes the due date forward to the next open day.</para>
\r
323 <title>Overdue fines <indexterm><primary>hours of operation</primary><secondary>overdue fines policy</secondary></indexterm></title>
\r
324 <para>Overdue fines are not charged on days when the library is closed.</para>
\r
328 <para>To review or edit your library's hours of operation,</para>
\r
331 <para>Open the <guilabel>Organizational Units</guilabel> interface.</para>
\r
335 <para>Click the <guilabel>Hours of
\r
336 Operation</guilabel> tab.</para>
\r
339 <alt>organizational units, main settings</alt>
\r
341 <imagedata scalefit="0" fileref="../media/server-4.png"/>
\r
350 <para>Review your library's weekly hours, editing as necessary. To set a closed day
\r
351 click the corresponding <guibutton>Closed</guibutton> button. Closed days (Monday
\r
352 and Sunday in the example below) have open and close times of 12:00
\r
356 <alt>hours of operation interface</alt>
\r
358 <imagedata scalefit="0" fileref="../media/server-5.png"/>
\r
366 <para>Click <guibutton>Save</guibutton> to record any changes</para>
\r
375 <simplesect xml:id="server-addresses">
\r
377 <title>Library Addresses <indexterm><primary>library addresses </primary><secondary>setting</secondary></indexterm></title>
\r
380 <para>Addresses set in <menuchoice>
\r
381 <guimenu>Admin (-)</guimenu>
\r
382 <guisubmenu>Server Administrations</guisubmenu>
\r
383 <guimenuitem>Organizational Units</guimenuitem>
\r
384 </menuchoice> appear in patron email notifications, hold slips, and transit slips. Local
\r
385 System Administrators should ensure that the <guilabel>Physical</guilabel>,
\r
386 <guilabel>Holds</guilabel>, and <guilabel>Mailing</guilabel> addresses are set
\r
392 <para>Open the <guilabel>Organizational Units</guilabel> interface as described in the <link
\r
393 linkend="orgunits">previous section</link>.</para>
\r
398 <guilabel>Addresses</guilabel> tab.</para>
\r
401 <alt>organizational units, main settings</alt>
\r
403 <imagedata scalefit="0" fileref="../media/server-6.png"/>
\r
412 <para>There are four address tabs: <guilabel>Physical</guilabel>,
\r
413 <guilabel>Holds</guilabel>, <guilabel>Mailing</guilabel>, and
\r
414 <guilabel>ILL</guilabel>. The <guilabel>Holds Address</guilabel> appears on transit slips when items are sent to fulfill holds at another branch.</para>
\r
420 <para>Click <guibutton>Save</guibutton> to record changes for each tab.</para>
\r
426 <para>The <guilabel>Valid</guilabel> check box is an optional setting that does not affect current Evergreen functions.</para>
\r
433 <section xml:id="permissions">
\r
434 <title>User and Group Permissions <indexterm><primary>permissions</primary><secondary>group</secondary></indexterm></title>
\r
436 <para>It is essential to understand how user and group permissions can be used to allow staff
\r
437 to fulfill their roles while ensuring that they only have access to the appropriate level.</para>
\r
438 <para>Permissions in <application>Evergreen</application> are applied to a specific location and system depth based on the home
\r
439 library of the user. The user will only have that permission within the scope provided by the
\r
440 <emphasis>Depth</emphasis> field in relation to his/her working locations.</para>
\r
441 <para>Evergreen provides group application permissions in order to restrict which staff members
\r
442 have the ability to assign elevated permissions to a user, and which staff members have the ability
\r
443 to edit users in particular groups.</para>
\r
446 <title>User Permissions</title>
\r
447 <tip><para>The User permissions editor allows an administrator to set up permission for an individual user. However, In most cases, permissions can be controlled more
\r
448 efficiently at the group level with individuals being assigned to specific groups based on their roles in the library.</para></tip>
\r
449 <para>To open the user permission editor, select <menuchoice><guimenu>Admin</guimenu>
\r
450 <guisubmenu>User Permission Editor</guisubmenu></menuchoice>. Type the user's barcode when prompted.</para>
\r
452 <title>Working Locations</title>
\r
453 <para>You may select more than one working location for a user. This will effect
\r
454 the availability of certain permissions which are dependent on the user having the working location.</para>
\r
457 <title>User Permission Settings<indexterm><primary>permissions</primary><secondary>user</secondary></indexterm></title>
\r
458 <para>Below the working locations is the long list of all the permissions available on your
\r
459 system. For each permission you can apply it by checking the
\r
460 <emphasis>Applied</emphasis> check box. You can also select a depth to which the
\r
461 permission is applied and also make the permission <emphasis>grantable</emphasis>, allowing
\r
462 the user the ability to grant the permission to others.</para>
\r
466 <title>Group Permissions <indexterm><primary>permissions</primary><secondary>group</secondary></indexterm></title>
\r
467 <para>Most permissions should be assigned at the group level. Here you can create new
\r
468 groups based on the roles and responsibilities of the users in your system. Staff will be able to
\r
469 assign users to these groups when they register patrons.</para>
\r
470 <tip><para>It is a good idea to create your groups soon after creating your organizational units.
\r
471 It is also important to give careful consideration to the hierarchy of your groups to make
\r
472 permission assignment as efficient as possible.</para></tip>
\r
473 <para>To enter the <emphasis>Group Permission</emphasis> module from the staff client menu, select
\r
474 <menuchoice><guimenu>Admin</guimenu> <guisubmenu>Server Administration</guisubmenu>
\r
475 <guisubmenu>Permission Groups</guisubmenu></menuchoice></para>
\r
477 <title>Adding Groups</title>
\r
478 <step><para>Select the <guibutton>Group Configuration</guibutton> tab if not
\r
479 already selected in the right pane</para></step>
\r
480 <step><para>Click <guibutton>New Child</guibutton></para></step>
\r
481 <step><para>Enter a unique <guilabel>Group Name</guilabel></para></step>
\r
482 <step><para>Enter a <guilabel>Description</guilabel></para></step>
\r
483 <step><para>Select a <guilabel>Permission Interval</guilabel>. This will determine the
\r
484 default expiry date of user account when you register patrons and select
\r
485 their groups</para></step>
\r
486 <step><para>Selecting an <guilabel>Editing Permission</guilabel> will determine the group level the user will have for editing other users.</para></step>
\r
487 <step><para>Select the <guilabel>Parent Group</guilabel> for the group.</para>
\r
488 <note><para>The group will inherit its parent group's permissions so it is unnecessary to assign permissions already inherited from its parent.</para></note></step>
\r
489 <step><para>Click the <guibutton>Save</guibutton> button.</para></step>
\r
492 <title>Deleting Groups</title>
\r
493 <step><para>Select the group you wish to delete from the group tree on
\r
494 left pane.</para></step>
\r
495 <step><para>Click the <guibutton>Delete</guibutton> button.</para></step>
\r
496 <step><para>Click on <guibutton>OK</guibutton>to verify.</para></step>
\r
499 <title>Editing Groups</title>
\r
500 <step><para>Select the group you wish to edit from the group tree on left pane.</para></step>
\r
501 <step><para>Edit the fields you wish to change in the right pane.</para></step>
\r
502 <step><para>Click on <guibutton>Save</guibutton> to save changes.</para></step>
\r
505 <title>Adding Group Permissions</title>
\r
506 <step><para>Select the <guibutton>Group Permissions</guibutton> tab on the right
\r
508 <step><para>Click on <guibutton>New Mapping</guibutton>.</para></step>
\r
509 <step><para>Select the permission you would like to add from the
\r
510 <guibutton>Permission</guibutton> Select box.</para></step>
\r
511 <step><para>Select the <guibutton>Depth</guibutton> you wish to set the
\r
512 permission. This will determine if the group has the permission at a local level or across a
\r
513 system, or consortium, or other organizational unit type.</para></step>
\r
514 <step><para>check the <guibutton>Grantable</guibutton> check box to allow the user to
\r
515 grant the permission to others.</para></step>
\r
516 <step><para>Click <guibutton>Add Mapping</guibutton> to add the permission to the
\r
517 group</para></step>
\r
520 <title>Deleting Group Permissions</title>
\r
521 <step><para>Select the group permission you wish to delete.</para></step>
\r
522 <step><para>Click the <guibutton>Delete Selected</guibutton> button.</para></step>
\r
523 <step><para>Click on <guibutton>OK</guibutton> to verify</para></step>
\r
526 <title>Editing Group Permissions</title>
\r
527 <step><para>Click on the <guilabel>Depth</guilabel> or <guilabel>Grantable</guilabel>
\r
528 field for the permission setting you wish to change.</para></step>
\r
529 <step><para>Make changes to other permissions in the same way.</para></step>
\r
530 <step><para>Click <guibutton>Save Changes</guibutton> when you are finished all
\r
531 the changes.</para></step>
\r
535 <title>Permissions</title>
\r
537 <table xml:id="permissiondescriptions">
\r
538 <title>Permissions Table</title>
\r
540 <colspec colnum="1" colname="col1" colwidth="1.0*"/>
\r
541 <colspec colnum="2" colname="col2" colwidth="1.0*"/>
\r
544 <entry>Permission Name</entry>
\r
545 <entry>Permission Description</entry>
\r
550 <entry>ABORT_REMOTE_TRANSIT</entry>
\r
551 <entry>Allows user to abort a copy transit if the user is not at
\r
552 the transit source or destination</entry>
\r
555 <entry>ABORT_TRANSIT</entry>
\r
556 <entry>Allows user to abort a copy transit if the user is at the
\r
557 transit destination or source</entry>
\r
560 <entry>ASSIGN_WORK_ORG_UNIT</entry>
\r
561 <entry>Allows user to define where another staff member's
\r
562 permissions apply via the Permissions Editor interface.</entry>
\r
565 <entry>BAR_PATRON</entry>
\r
566 <entry>Allows user to bar a patron</entry>
\r
569 <entry>CANCEL_HOLDS</entry>
\r
570 <entry>Allows user to cancel holds</entry>
\r
573 <entry>CIRC_CLAIMS_RETURNED override</entry>
\r
574 <entry>Allows user to check in/out an item that is claims
\r
578 <entry>CIRC_EXCEEDS_COPY_RANGE override</entry>
\r
579 <entry>Allows user to override the copy exceeds range event</entry>
\r
582 <entry>CIRC_OVERRIDE_DUE_DATE</entry>
\r
583 <entry>Allows user to change due date</entry>
\r
586 <entry>CIRC_PERMIT_OVERRIDE</entry>
\r
587 <entry>Allows user to bypass the circ permit call for i
\r
591 <entry>COPY_ALERT_MESSAGE override</entry>
\r
592 <entry>Allows user to check in/out an item that has an alert
\r
596 <entry>COPY_BAD_STATUS override</entry>
\r
597 <entry>Allows user to check out an item in a non-circulating
\r
601 <entry>COPY_CHECKIN</entry>
\r
602 <entry>Allows user to check in a copy</entry>
\r
605 <entry>COPY_CHECKOUT</entry>
\r
606 <entry>Allows user to check out a copy</entry>
\r
609 <entry>COPY_CIRC_NOT_ALLOWED override</entry>
\r
610 <entry>Allows user to checkout an item that is marked as
\r
614 <entry>COPY_HOLDS</entry>
\r
615 <entry>Allows user to place a hold on a specific copy</entry>
\r
618 <entry>COPY_IS_REFERENCE override</entry>
\r
619 <entry>Allows user to override the copy_is_reference event</entry>
\r
623 <entry>COPY_NOT_AVAILABLE override</entry>
\r
624 <entry>Allows user to force checkout of Missing/Lost type
\r
628 <entry>COPY_STATUS_LOST override</entry>
\r
629 <entry>Allows user to remove the lost status from a copy</entry>
\r
632 <entry>COPY_STATUS_MISSING override</entry>
\r
633 <entry>Allows user to change the missing status on a copy</entry>
\r
636 <entry>COPY_TRANSIT_RECEIVE</entry>
\r
637 <entry>Allows user to close out a transit on a copy</entry>
\r
640 <entry>CREATE_BILL</entry>
\r
641 <entry>Allows user to create a new bill on a transaction</entry>
\r
644 <entry>CREATE_CONTAINER</entry>
\r
645 <entry>Allows user to create containers owned by other users
\r
646 (containers are Item Buckets, Volume Buckets, and Book Bags)</entry>
\r
649 <entry>CREATE_CONTAINER_ITEM</entry>
\r
650 <entry>Allows user to place an item in a container (even if the
\r
651 container is owned by other users).</entry>
\r
654 <entry>CREATE_COPY</entry>
\r
655 <entry>Allows user to create a new copy object</entry>
\r
658 <entry>CREATE_COPY_LOCATION</entry>
\r
659 <entry>Allows user to create a new copy location</entry>
\r
662 <entry>CREATE_COPY_NOTE</entry>
\r
663 <entry>Allows user to create a new copy note</entry>
\r
666 <entry>CREATE_COPY_STAT_CAT</entry>
\r
667 <entry>Allows user to create a statistical category for
\r
671 <entry>CREATE_COPY_STAT_CAT _ENTRY</entry>
\r
672 <entry>Allows user to create a new entry for a copy statistical
\r
676 <entry>CREATE_COPY_STAT_CAT _ENTRY_MAP</entry>
\r
677 <entry>Allows user to link a copy to a statistical category
\r
678 (i.e., allows user to specify the appropriate entry for a copy and
\r
679 given statistical category)</entry>
\r
682 <entry>CREATE_COPY_TRANSIT</entry>
\r
683 <entry>Allows user to create a transit</entry>
\r
686 <entry>CREATE_DUPLICATE_HOLDS</entry>
\r
687 <entry>Allows user to create duplicate holds (e.g. two holds on the
\r
688 same title)</entry>
\r
691 <entry>CREATE_HOLD_NOTIFICATION</entry>
\r
692 <entry>Allows user to create new hold notifications</entry>
\r
695 <entry>CREATE_IN_HOUSE_USE</entry>
\r
696 <entry>Allows user to create a new in-house-use</entry>
\r
699 <entry>CREATE_MARC</entry>
\r
700 <entry>Allows user to create new MARC records</entry>
\r
703 <entry>CREATE_MY_CONTAINER</entry>
\r
704 <entry>Allows user to create containers for self (containers are
\r
705 Item Buckets, Volume Buckets, and Book Bags).</entry>
\r
708 <entry>CREATE_NON_CAT_TYPE</entry>
\r
709 <entry>Allows user to create a new non-cataloged item type</entry>
\r
712 <entry>CREATE_PATRON_STAT _CAT</entry>
\r
713 <entry>Allows user to create a new patron statistical
\r
717 <entry>CREATE_PATRON_STAT _CAT_ENTRY</entry>
\r
718 <entry>Allows user to create a new possible entry for patron
\r
719 statistical categories</entry>
\r
722 <entry>CREATE_PATRON_STAT _CAT_ENTRY_MAP</entry>
\r
723 <entry>Allows user to link another user to a stat cat entry (i.e.,
\r
724 specify the patron's entry for a given statistical category)</entry>
\r
727 <entry>CREATE_PAYMENT</entry>
\r
728 <entry>Allows user to record payments in the Billing
\r
732 <entry>CREATE_TITLE_NOTE</entry>
\r
733 <entry>Allows user to create a new title note</entry>
\r
736 <entry>CREATE_TRANSACTION</entry>
\r
737 <entry>Allows user to create new billable transactions (these
\r
738 include checkouts and transactions created via the Bill Patron
\r
742 <entry>CREATE_TRANSIT</entry>
\r
743 <entry>Allows user to place item in transit</entry>
\r
746 <entry>CREATE_USER</entry>
\r
747 <entry>Allows user to create another user</entry>
\r
750 <entry>CREATE_USER_GROUP _LINK</entry>
\r
751 <entry>Allows user to add other users to permission groups</entry>
\r
754 <entry>CREATE_VOLUME</entry>
\r
755 <entry>Allows user to create a volume</entry>
\r
758 <entry>CREATE_VOLUME_NOTE</entry>
\r
759 <entry>Allows user to create a new volume note</entry>
\r
762 <entry>DELETE_CONTAINER</entry>
\r
763 <entry>Allows user to delete containers (containers are Item Buckets,
\r
764 Volume Buckets, and Book Bags).</entry>
\r
767 <entry>DELETE_CONTAINER _ITEM</entry>
\r
768 <entry>Allows user to remove items from buckets and bookbags</entry>
\r
771 <entry>DELETE_COPY</entry>
\r
772 <entry>Allows user to delete a copy</entry>
\r
775 <entry>DELETE_COPY _LOCATION</entry>
\r
776 <entry>Allows user to delete a copy location</entry>
\r
779 <entry>DELETE_COPY_NOTE</entry>
\r
780 <entry>Allows user to delete copy notes</entry>
\r
783 <entry>DELETE_COPY_STAT _CAT</entry>
\r
784 <entry>Allows user to delete a copy statistical category</entry>
\r
787 <entry>DELETE_COPY_STAT _CAT_ENTRY</entry>
\r
788 <entry>Allows user to delete an entry for a copy statistical
\r
792 <entry>DELETE_COPY_STAT _CAT_ENTRY_MAP</entry>
\r
793 <entry>Allows user to delete a copy stat cat entry map</entry>
\r
796 <entry>DELETE_NON_CAT_TYPE</entry>
\r
797 <entry>Allows user to delete a non cataloged type (the user still
\r
798 cannot deleted a non-cat type if any items of that type have
\r
799 circulated).</entry>
\r
802 <entry>DELETE_PATRON_STAT _CAT</entry>
\r
803 <entry>Allows user to delete a patron statistical category</entry>
\r
806 <entry>DELETE_PATRON_STAT _CAT_ENTRY</entry>
\r
807 <entry>Allows user to delete an entry for patron statistical
\r
811 <entry>DELETE_PATRON_STAT _CAT_ENTRY_MAP</entry>
\r
812 <entry>Allows user to remove a patron's entry for a given
\r
813 statistical category</entry>
\r
816 <entry>DELETE_RECORD</entry>
\r
817 <entry>Allows user to delete a bib record</entry>
\r
820 <entry>DELETE_TITLE_NOTE</entry>
\r
821 <entry>Allows user to delete title notes</entry>
\r
824 <entry>DELETE_USER</entry>
\r
825 <entry>Allows user to mark a user as deleted</entry>
\r
828 <entry>DELETE_VOLUME</entry>
\r
829 <entry>Allows user to delete a volume</entry>
\r
832 <entry>DELETE_VOLUME_NOTE</entry>
\r
833 <entry>Allows user to delete volume notes</entry>
\r
836 <entry>DELETE_WORKSTATION</entry>
\r
837 <entry>Allows user to remove an existing workstation so a new one
\r
838 can replace it</entry>
\r
841 <entry>EVERYTHING</entry>
\r
842 <entry> Every permission is granted (for sysadmins and developers
\r
846 <entry>HOLD_EXISTS.override</entry>
\r
847 <entry>Allows users to place multiple holds on a single
\r
848 copy/volume/title/metarecord (depending on hold type)</entry>
\r
851 <entry>IMPORT_MARC</entry>
\r
852 <entry>Allows user to import a MARC record via the z39.50
\r
856 <entry>ITEM_AGE_PROTECTED override</entry>
\r
857 <entry>Allows user to place a hold on an age-protected item</entry>
\r
859 <entry>ITEM_ON_HOLDS_SHELF override</entry>
\r
860 <entry>Allows user to check out an item that is on holds shelf for a
\r
861 different patron</entry>
\r
864 <entry>MAX_RENEWALS_REACHED override</entry>
\r
865 <entry>Allows user to renew an item past the maximum renewal
\r
869 <entry>MERGE_BIB_RECORDS</entry>
\r
870 <entry>Allows user to merge bib records and their associated data
\r
871 regardless of their bib/volume/copy level perms (in theory - as of
\r
872 1.2.2, users still must have VOLUME_UPDATE and UPDATE_VOLUME in
\r
873 order to merge records.</entry>
\r
876 <entry>MR_HOLDS</entry>
\r
877 <entry>Allows user to create a metarecord holds</entry>
\r
880 <entry>OFFLINE_EXECUTE</entry>
\r
881 <entry>Allows user to process an offline/standalone script
\r
885 <entry>OFFLINE_UPLOAD</entry>
\r
886 <entry>Allows user to upload an offline/standalone script</entry>
\r
889 <entry>OFFLINE_VIEW</entry>
\r
890 <entry>Allows user to view uploaded offline script information</entry>
\r
893 <entry>OPAC_LOGIN</entry>
\r
894 <entry>Allows user to login to the OPAC</entry>
\r
897 <entry>patron_exceeds_checkout _count.override</entry>
\r
898 <entry>Allow user to override checkout count failure</entry>
\r
901 <entry>patron_exceeds_fines override</entry>
\r
902 <entry>Allow user to override fine amount checkout failure</entry>
\r
905 <entry>patron_exceeds_overdue _count.override</entry>
\r
906 <entry>Allow user to override overdue count failure</entry>
\r
909 <entry>REGISTER_WORKSTATION</entry>
\r
910 <entry>Allows user to register a new workstation</entry>
\r
913 <entry>REMOTE_Z3950_QUERY</entry>
\r
914 <entry>Allows user to perform z3950 queries against remote
\r
918 <entry>REMOVE_USER_GROUP_LINK</entry>
\r
919 <entry>Allows user to remove other users from permission
\r
923 <entry>RENEW_CIRC</entry>
\r
924 <entry>Allows user to renew items</entry>
\r
927 <entry>RENEW_HOLD_OVERRIDE</entry>
\r
928 <entry>Allows user to continue to renew an item even if it is
\r
929 required for a hold.</entry>
\r
932 <entry>REQUEST_HOLDS</entry>
\r
933 <entry>Allows user to create holds for another user (if true, we
\r
934 still check to make sure they have permission to make the type of
\r
935 hold they are requesting, e.g. COPY_HOLDS)</entry>
\r
938 <entry>RUN_REPORTS</entry>
\r
939 <entry>Allows user to view the Reports Interface, create templates,
\r
940 and run reports</entry>
\r
943 <entry>SET_CIRC_CLAIMS _RETURNED</entry>
\r
944 <entry>Allows user to mark an item as claimed returned</entry>
\r
947 <entry>SET_CIRC_LOST</entry>
\r
948 <entry>Allows user to mark an item as lost</entry>
\r
951 <entry>SET_CIRC_MISSING</entry>
\r
952 <entry>Allows user to mark an item as missing</entry>
\r
955 <entry>SHARE_REPORT_FOLDER</entry>
\r
956 <entry>Allows user to share Template/Report/Output folders via the
\r
957 Reporting Interface</entry>
\r
960 <entry>STAFF_LOGIN</entry>
\r
961 <entry>Allows user to login to the staff client</entry>
\r
964 <entry>TITLE_HOLDS</entry>
\r
965 <entry> Allows user to place a hold at the title level</entry>
\r
968 <entry>UNBAR_PATRON</entry>
\r
969 <entry> Allows user to un-bar a patron</entry>
\r
972 <entry>UPDATE_BATCH_COPY</entry>
\r
973 <entry>Allows user to edit copies in batch</entry>
\r
976 <entry>UPDATE_CONTAINER</entry>
\r
977 <entry>Allows user to update another users Buckets or Book
\r
981 <entry>UPDATE_COPY</entry>
\r
982 <entry>Allows user to edit a copy</entry>
\r
985 <entry>UPDATE_COPY_LOCATION</entry>
\r
986 <entry>Allows user to edit a copy location</entry>
\r
989 <entry>UPDATE_COPY_STAT_CAT</entry>
\r
990 <entry>Allows user to change a copy statistical category</entry>
\r
993 <entry>UPDATE_COPY_STAT _CAT_ENTRY</entry>
\r
994 <entry>Allows user to change a copy statistical category entry</entry>
\r
997 <entry>UPDATE_HOLD</entry>
\r
998 <entry>Allows user to edit holds (such as change notification phone
\r
999 number or pickup library, as well as re-target the hold and capture
\r
1000 an item for hold or pickup)</entry>
\r
1003 <entry>UPDATE_MARC</entry>
\r
1004 <entry>Allows user to edit a marc record</entry>
\r
1007 <entry>UPDATE_NON_CAT _TYPE</entry>
\r
1008 <entry>Allows user to update a non cataloged type</entry>
\r
1011 <entry>UPDATE_ORG_SETTING</entry>
\r
1012 <entry>Allows user to update an org unit setting</entry>
\r
1015 <entry>UPDATE_ORG_UNIT</entry>
\r
1016 <entry>Allows user to change org unit settings</entry>
\r
1019 <entry>UPDATE_PATRON_STAT _CAT</entry>
\r
1020 <entry>Allows user to change a patron statistical category (such as
\r
1021 renaming the category)</entry>
\r
1024 <entry>UPDATE_PATRON_STAT _CAT_ENTRY</entry>
\r
1025 <entry>Allows user to change a patron stat cat entry(such as
\r
1026 renaming the entry)</entry>
\r
1029 <entry>UPDATE_RECORD</entry>
\r
1030 <entry>Allows user to undelete a MARC record</entry>
\r
1033 <entry>UPDATE_USER</entry>
\r
1034 <entry>Allows user to edit a user's record</entry>
\r
1037 <entry>UPDATE_VOLUME</entry>
\r
1038 <entry>Allows user to edit volumes - needed for merging records.
\r
1039 This is a duplicate of VOLUME_UPDATE; user must have both
\r
1040 permissions at appropriate level to merge records.</entry>
\r
1043 <entry>VIEW_CIRCULATIONS</entry>
\r
1044 <entry>Allows user to see what another user has checked out</entry>
\r
1047 <entry>VIEW_CONTAINER</entry>
\r
1048 <entry>Allows user to view buckets and bookbags</entry>
\r
1051 <entry>VIEW_COPY_CHECKOUT _HISTORY</entry>
\r
1052 <entry>Allows user to view which users have checked out a given
\r
1056 <entry>VIEW_COPY_NOTES</entry>
\r
1057 <entry>Allows user to view notes attached to a copy</entry>
\r
1060 <entry>VIEW_HOLD</entry>
\r
1061 <entry>Allows user to view another user's holds</entry>
\r
1064 <entry>VIEW_HOLD_NOTIFICATION</entry>
\r
1065 <entry>Allows user to view notifications attached to a hold</entry>
\r
1068 <entry>VIEW_HOLD_PERMIT</entry>
\r
1069 <entry>Allows user to see if another user has permission to place a
\r
1070 hold on a given copy</entry>
\r
1073 <entry>VIEW_PERM_GROUPS</entry>
\r
1074 <entry>Allows user to view permission groups.</entry>
\r
1077 <entry>VIEW_PERMISSION</entry>
\r
1078 <entry>Allows user to view user permissions within the user
\r
1079 permissions editor</entry>
\r
1082 <entry>VIEW_PERMIT_CHECKOUT</entry>
\r
1083 <entry>Allows user to see if another user can check out an item
\r
1084 (should be true for all staff)</entry>
\r
1087 <entry>VIEW_REPORT_OUTPUT</entry>
\r
1088 <entry>Allows user to view report output</entry>
\r
1091 <entry>VIEW_TITLE_NOTES</entry>
\r
1092 <entry>Allows user to view all notes attached to a title</entry>
\r
1095 <entry>VIEW_TRANSACTION</entry>
\r
1096 <entry>Allows user to see another users grocery/circ transactions
\r
1097 in the Bills Interface</entry>
\r
1100 <entry>VIEW_USER</entry>
\r
1101 <entry>Allows user to view another user's Patron Record</entry>
\r
1104 <entry>VIEW_USER_FINES _SUMMARY</entry>
\r
1105 <entry>Allows user to view bill details</entry>
\r
1108 <entry>VIEW_USER_TRANSACTIONS</entry>
\r
1109 <entry>*same as VIEW_TRANSACTION (duplicate perm)</entry>
\r
1112 <entry>VIEW_VOLUME_NOTES</entry>
\r
1113 <entry>Allows user to view all notes attached to a volume</entry>
\r
1116 <entry>VIEW_ZIP_DATA</entry>
\r
1117 <entry>Allows user to query the zip code data method</entry>
\r
1120 <entry>VOID_BILLING</entry>
\r
1121 <entry>Allows user to void a bill</entry>
\r
1124 <entry>VOLUME_HOLDS</entry>
\r
1125 <entry> Allows user to place a volume level hold</entry>
\r
1129 <entry>actor.org_unit.closed _date.create</entry>
\r
1130 <entry>Allows user to create a new closed date for a location</entry>
\r
1133 <entry>actor.org_unit.closed _date.delete</entry>
\r
1134 <entry>Allows user to remove a closed date interval for a given
\r
1138 <entry>actor.org_unit.closed _date.update</entry>
\r
1139 <entry>Allows user to update a closed date interval for a given
\r
1143 <entry>group_application.user</entry>
\r
1144 <entry>Allows user to add/remove users to/from the User group</entry>
\r
1147 <entry>group_application.user .patron</entry>
\r
1148 <entry>Allows user to add/remove users to/from the Patron
\r
1152 <entry>group_application.user. sip_client</entry>
\r
1153 <entry>Allows user to add/remove users to/from the SIP-Client
\r
1157 <entry>group_application.user. staff</entry>
\r
1158 <entry>Allows user to add/remove users to/from the Staff
\r
1162 <entry>group_application.user.staff. admin.global_admin</entry>
\r
1163 <entry>Allows user to add/remove users to/from the GlobalAdmin
\r
1167 <entry>group_application.user.staff. admin.lib_manager</entry>
\r
1168 <entry>Allows user to add/remove users to/from the LibraryManager
\r
1172 <entry>group_application.user.staff. admin.local_admin</entry>
\r
1173 <entry>Allows user to add/remove users to/from the LocalAdmin
\r
1177 <entry>group_application.user.staff.cat</entry>
\r
1178 <entry>Allows user to add/remove users to/from the Cataloger group</entry>
\r
1181 <entry>group_application.user. staff.cat.cat1</entry>
\r
1182 <entry>Allows user to add/remove users to/from the Cat1 group</entry>
\r
1185 <entry>group_application.user. staff.circ</entry>
\r
1186 <entry>Allows user to add/remove users to/from the Circulator
\r
1190 <entry>group_application.user. staff.supercat</entry>
\r
1191 <entry>Allows user to add/remove users to/from the Supercat
\r
1195 <entry>group_application.user. vendor</entry>
\r
1196 <entry>Allows user to add/remove users to/from the Vendor
\r
1200 <entry>money.collections_tracker. create</entry>
\r
1201 <entry>Allows user to put someone into collections</entry>
\r
1204 <entry>money.collections_tracker. delete</entry>
\r
1205 <entry>Allows user to take someone out of collections</entry>
\r
1213 <section xml:id="admin-staff_accounts">
\r
1215 <title>Staff Accounts</title>
\r
1219 <para> New staff accounts are created in much the same way as patron accounts, using <menuchoice>
\r
1220 <guimenu>Circulation</guimenu>
\r
1221 <guimenuitem>Register Patron</guimenuitem>
\r
1222 </menuchoice> or <keycombo>
\r
1223 <keycap>Shift</keycap>
\r
1224 <keycap>F1</keycap>
\r
1225 </keycombo>. Select one of the staff profiles from the <guilabel>Profile
\r
1226 Group</guilabel> drop-down menu. <indexterm><primary>staff accounts</primary></indexterm></para>
\r
1228 <para xml:id="profiles-working">Each new staff account must be assigned a <guilabel>Working
\r
1229 Location</guilabel><indexterm><primary>staff accounts</primary><secondary>working location</secondary></indexterm> which determines its access level in staff client interfaces.
\r
1230 Accounts migrated from legacy systems or created before the upgrade to Evergreen 1.6 already
\r
1231 have working locations assigned.</para>
\r
1236 <para>To assign a working location open the newly created staff account using
\r
1237 <keycap>F1</keycap> (retrieve patron) or <keycap>F4</keycap> (patron search).
\r
1242 <para>Select <menuchoice>
\r
1243 <guimenu>Other</guimenu>
\r
1244 <guimenuitem>User Permission Editor</guimenuitem>
\r
1245 </menuchoice></para>
\r
1248 <para>Place a check in the box next to the desired working location, then scroll to the
\r
1249 bottom of the display and click <guibutton>Save</guibutton>.</para>
\r
1257 <para>In multi-branch libraries it is possible to assign more than one working
\r
1262 <simplesect xml:id="staff_account_permissions">
\r
1264 <title>Staff Account Permissions <indexterm><primary>staff accounts</primary><secondary>permissions</secondary></indexterm> </title>
\r
1266 <para> To view a detailed list
\r
1267 of permissions for a particular Evergreen account go to <menuchoice>
\r
1268 <guimenu>Admin (-)</guimenu>
\r
1269 <guimenuitem>User permission editor</guimenuitem>
\r
1270 </menuchoice> in the staff client.</para>
\r
1272 <!-- <informaltable>
\r
1274 <tgroup cols="7" align="center" colsep="1" rowsep="1">
\r
1276 <colspec colnum="1" colname="col1" align="left" colwidth="2.0*"/>
\r
1277 <colspec colnum="2" colname="col2" colwidth="1.0*"/>
\r
1278 <colspec colnum="3" colname="col3" colwidth="1.0*"/>
\r
1279 <colspec colnum="4" colname="col4" colwidth="1.0*"/>
\r
1280 <colspec colnum="5" colname="col5" colwidth="1.0*"/>
\r
1281 <colspec colnum="6" colname="col6" colwidth="1.0*"/>
\r
1282 <colspec colnum="7" colname="col7" colwidth="1.0*"/>
\r
1285 <entry>Action</entry>
\r
1286 <entry>General Staff</entry>
\r
1287 <entry>Circulators</entry>
\r
1288 <entry>Circ + Copy Edit</entry>
\r
1289 <entry>Circ + Full Cat</entry>
\r
1290 <entry>Catalogers</entry>
\r
1291 <entry>Local System Admin.</entry>
\r
1297 <entry>Basic circulation functions</entry>
\r
1308 <entry>CheckIn bad status overrides</entry>
\r
1318 <entry>CheckIn Missing/Lost/ ClaimedReturned overrides</entry>
\r
1327 <entry>CheckOut overrides</entry>
\r
1337 <entry>MaxRenewal Reached override</entry>
\r
1349 <entry>Basic patron record</entry>
\r
1360 <entry>Bar patrons</entry>
\r
1369 <entry>Unbar patrons</entry>
\r
1379 <entry>Merge/delete patrons</entry>
\r
1389 <entry>Patron restriction overrides</entry>
\r
1399 <entry>Bills and payments</entry>
\r
1410 <entry>Holds</entry>
\r
1419 <entry>Copy/volume records</entry>
\r
1429 <entry>Bib records</entry>
\r
1438 <entry>Buckets</entry>
\r
1450 <entry>View report output</entry>
\r
1460 <entry>Create/run reports</entry>
\r
1470 <entry>Create/upload offline transactions</entry>
\r
1480 <entry>Process offline transactions</entry>
\r
1489 <entry>Transit</entry>
\r
1498 <entry>Abort remote transit</entry>
\r
1509 </informaltable>-->
\r
1512 <simplesect xml:id="profiles-grant-permissions">
\r
1513 <title>Granting Additional Permissions</title>
\r
1514 <para>A Local System Administrator (LSA) may selectively grant LSA permissions to other staff
\r
1515 accounts. In the example below a <emphasis>Circ +Full
\r
1516 Cat</emphasis> account is granted permission to process offline transactions, a function which otherwise requires an LSA login.</para>
\r
1520 <para>Log in as a Local System Administrator.</para>
\r
1523 <step><stepalternatives> <step>
\r
1525 <para>Select <menuchoice>
\r
1526 <guimenu>Admin (-)</guimenu>
\r
1527 <guimenuitem>User Permission Editor</guimenuitem>
\r
1528 </menuchoice> and enter the staff account barcode when prompted</para>
\r
1530 <para><emphasis role="bold">OR</emphasis></para>
\r
1534 <para>Retrieve the staff account first, then select <menuchoice>
\r
1535 <guimenu>Other</guimenu>
\r
1536 <guimenuitem>User Permission Editor</guimenuitem>
\r
1537 </menuchoice></para>
\r
1539 </step></stepalternatives></step>
\r
1543 <para>The <guilabel>User Permission Editor</guilabel> will load (this may take a
\r
1544 few seconds). Greyed-out permissions cannot be edited because they are
\r
1545 either a) already granted to the account, or b) not
\r
1546 available to any staff account, including LSAs.</para>
\r
1549 <alt>User permissions screen shot</alt>
\r
1551 <imagedata scalefit="0" fileref="../media/profile-5.png"/>
\r
1558 <inlinemediaobject>
\r
1560 <imagedata scalefit="0" fileref="../media/1.png"/>
\r
1562 </inlinemediaobject> List of permission names.</para>
\r
1565 <inlinemediaobject>
\r
1567 <imagedata scalefit="0" fileref="../media/2.png"/>
\r
1569 </inlinemediaobject>
\r
1570 If checked the permission is granted to this account.</para>
\r
1573 <inlinemediaobject>
\r
1575 <imagedata scalefit="0" fileref="../media/3.png"/>
\r
1577 </inlinemediaobject> <guilabel>Depth</guilabel> limits application to the staff member's library and should be left at the default.</para>
\r
1580 <inlinemediaobject>
\r
1582 <imagedata scalefit="0" fileref="../media/4.png"/>
\r
1584 </inlinemediaobject>
\r
1585 If checked this staff account will be able to grant the new privilege to other accounts (not recommended).
\r
1593 <para>To allow processing of offline transactions check the <emphasis>Applied</emphasis> column next to OFFLINE_EXECUTE.</para>
\r
1596 <alt>User permissions screen shot</alt>
\r
1598 <imagedata scalefit="0" fileref="../media/profile-6.png"/>
\r
1609 <para>Scroll down and click <guibutton>Save</guibutton> to apply the changes.</para>
\r
1612 <alt>User permissions screen shot</alt>
\r
1614 <imagedata scalefit="0" fileref="../media/profile-7.png"/>
\r
1626 <section xml:id="copystatus">
\r
1627 <title>Copy Status</title>
\r
1628 <indexterm><primary>copy status</primary></indexterm>
\r
1629 <para>To navigate to the copy status editor from the staff client menu, select
\r
1630 <menuchoice><guimenu>Admin</guimenu> <guisubmenu>Server Administration</guisubmenu>
\r
1631 <guisubmenu>Copy Statuses </guisubmenu></menuchoice></para>
\r
1632 <para>The Copy Status Editor is used to Add, edit and delete statuses of copies in your system.</para>
\r
1633 <para>Evergreen comes pre-loaded with a number of copy statuses.</para>
\r
1634 <table xml:id="copystatusestable">
\r
1635 <title>Copy Status Table</title>
\r
1637 <colspec colnum="1" colname="col1" colwidth="0.5*"/>
\r
1638 <colspec colnum="2" colname="col2" colwidth="1.0*"/>
\r
1639 <colspec colnum="3" colname="col3" colwidth="1.0*"/>
\r
1640 <colspec colnum="4" colname="col4" colwidth="1.0*"/>
\r
1644 <entry>Name</entry>
\r
1645 <entry>Holdable - default setting</entry>
\r
1646 <entry>OPAC Visible - default setting</entry>
\r
1652 <entry>Available</entry>
\r
1653 <entry>true</entry>
\r
1654 <entry>true</entry>
\r
1658 <entry>Checked out</entry>
\r
1659 <entry>true</entry>
\r
1660 <entry>true</entry>
\r
1664 <entry>Bindery</entry>
\r
1665 <entry>false</entry>
\r
1666 <entry>false</entry>
\r
1670 <entry>Lost</entry>
\r
1671 <entry>false</entry>
\r
1672 <entry>false</entry>
\r
1676 <entry>Missing</entry>
\r
1677 <entry>false</entry>
\r
1678 <entry>false</entry>
\r
1682 <entry>In process</entry>
\r
1683 <entry>false</entry>
\r
1684 <entry>true</entry>
\r
1688 <entry>In transit</entry>
\r
1689 <entry>true</entry>
\r
1690 <entry>true</entry>
\r
1694 <entry>Reshelving</entry>
\r
1695 <entry>true</entry>
\r
1696 <entry>true</entry>
\r
1700 <entry>On holds shelf</entry>
\r
1701 <entry>true</entry>
\r
1702 <entry>true</entry>
\r
1706 <entry>On order</entry>
\r
1707 <entry>true</entry>
\r
1708 <entry>true</entry>
\r
1712 <entry>ILL</entry>
\r
1713 <entry>true</entry>
\r
1714 <entry>false</entry>
\r
1718 <entry>Cataloging</entry>
\r
1719 <entry>true</entry>
\r
1720 <entry>false</entry>
\r
1724 <entry>Reserves</entry>
\r
1725 <entry>false</entry>
\r
1726 <entry>true</entry>
\r
1730 <entry>Discard/Weed</entry>
\r
1731 <entry>false</entry>
\r
1732 <entry>false</entry>
\r
1736 <entry>Damaged</entry>
\r
1737 <entry>false</entry>
\r
1738 <entry>false</entry>
\r
1742 <entry>On reservation shelf</entry>
\r
1743 <entry>true</entry>
\r
1744 <entry>false</entry>
\r
1749 <para>It is possible to add, delete and edit copy statuses.</para>
\r
1751 <title>Adding Copy Statuses</title>
\r
1752 <step><para>In the <guilabel>New Status</guilabel> field, enter the name of the
\r
1753 new status you wish to add.</para></step>
\r
1754 <step><para>Click <guibutton>Add</guibutton>.</para></step>
\r
1755 <step><para>Locate you new status and check the <emphasis>Holdable</emphasis> check box
\r
1756 if you wish to all users to place holds on items in this status. Check
\r
1757 <guilabel>OPAC Visible</guilabel> if you wish for this status to appear in the public
\r
1758 OPAC.</para></step>
\r
1759 <step><para>Click <guibutton>Save Changes</guibutton> at the bottom of the screen to
\r
1760 save changes to the new status.</para></step>
\r
1763 <title>Deleting Copy Statuses</title>
\r
1764 <step><para>Highlight the statuses you wish to delete. Hold the
\r
1765 <keycap>Shift</keycap> to select more than one status.</para></step>
\r
1766 <step><para>Click <guibutton>Delete Selected</guibutton>.</para></step>
\r
1767 <step><para>Click OK to verify.</para>
\r
1768 <note><para>You will not be able to delete statuses if copies currently
\r
1769 exist with that status.</para></note>
\r
1773 <title>Editing Copy Statuses</title>
\r
1774 <step><para>Double click on a status name to change its name and enter the new
\r
1775 name.</para> <para>To change whether a status is visible in the OPAC, check or uncheck
\r
1776 the <guilabel>OPAC Visible</guilabel> check box.</para><para>To allow patrons the ability to
\r
1777 hold items in that status, check the <emphasis>Holdable</emphasis> check box. To prevent
\r
1778 users from holding items in that status, uncheck the <emphasis>Holdable</emphasis>
\r
1779 check box. </para></step>
\r
1780 <step><para>Once you have finished editing the statuses, remember to click
\r
1781 <guibutton>Save Changes</guibutton>.</para></step>
\r
1784 <section xml:id="billingtypes">
\r
1785 <title>Billing Types</title>
\r
1786 <indexterm><primary>billing types</primary></indexterm>
\r
1787 <para>The billing types editor is used for creating, editing and deleting billing types.</para>
\r
1788 <para>To navigate to the billing types editor from the staff client menu, select
\r
1789 <menuchoice><guimenu>Admin</guimenu> <guisubmenu>Server Administration</guisubmenu>
\r
1790 <guisubmenu>Billing Types</guisubmenu></menuchoice></para>
\r
1792 <title>Adding Billing Types</title>
\r
1793 <indexterm><primary>billing types</primary><secondary>adding</secondary></indexterm>
\r
1794 <step><para>Click <guibutton>New Billing Type</guibutton>.</para></step>
\r
1795 <step><para>Enter the name of the billing type.</para></step>
\r
1796 <step><para>Select the <guilabel>Org Unit</guilabel> to use this billing type.</para></step>
\r
1797 <step><para>Enter the <guilabel>Default Price</guilabel>. This is only the default since
\r
1798 the actual price of a specific billing can be adjusted when staff create
\r
1799 a billing</para></step>
\r
1800 <step><para>Click <guibutton>Save</guibutton> to save the new billing type.</para></step>
\r
1803 <title>Deleting Billing Types</title>
\r
1804 <indexterm><primary>billing types</primary><secondary>deleting</secondary></indexterm>
\r
1805 <step><para>Check the check box of the billing type(s) you wish to delete.</para></step>
\r
1806 <step><para>Click <guibutton>Delete Selected</guibutton>.
\r
1807 <caution><para>The selected billing types will be deleted without a
\r
1808 verification alert.</para></caution>
\r
1812 <title>Editing Billing Types</title>
\r
1813 <indexterm><primary>billing types</primary><secondary>editing</secondary></indexterm>
\r
1814 <step><para>Double click on a billing types to open the editing window.</para></step>
\r
1815 <step><para>Make desired changes to the <guilabel>name</guilabel>,
\r
1816 <guilabel>Org Unit</guilabel> and <guilabel>Default Price</guilabel>.</para></step>
\r
1817 <step><para>Once you have finished editing, click
\r
1818 <guibutton>Save</guibutton>.</para></step>
\r
1822 <section xml:id="circmodifiers">
\r
1823 <title>Circulation Modifiers</title>
\r
1824 <indexterm><primary>circulation modifiers</primary></indexterm>
\r
1825 <para>The circulation modifier editor is used to create, edit and delete modifier categories to control
\r
1826 circulation policies on specific groups of items.</para>
\r
1827 <para>To navigate to the circulation modifiers editor from the staff client menu, select
\r
1829 <guimenu>Admin</guimenu> <guisubmenu>Server Administration</guisubmenu>
\r
1830 <guisubmenu>Circulation Modifiers</guisubmenu></menuchoice>.
\r
1833 <title>Adding Circulation Modifiers</title>
\r
1834 <indexterm><primary>circulation modifiers</primary><secondary>adding</secondary></indexterm>
\r
1835 <step><para>Click <guibutton>New Circ Modifier</guibutton>.</para></step>
\r
1836 <step><para>Enter a <guilabel>Code</guilabel>, <guilabel>Name</guilabel> and
\r
1837 <guilabel>Description</guilabel>.</para></step>
\r
1838 <step><para>Select the <guilabel>SIP 2 Media Type</guilabel>.</para></step>
\r
1839 <step><para>Check the <guibutton>Magnetic Media</guibutton> check box if the item is magnetic media such as a cassette
\r
1840 tape.</para></step>
\r
1841 <step><para>Click <guibutton>Save</guibutton> to save the new circulation
\r
1842 modifier.</para></step>
\r
1845 <title>Deleting Circulation Modifiers</title>
\r
1846 <indexterm><primary>circulation modifiers</primary><secondary>deleting</secondary></indexterm>
\r
1847 <step><para>Check the check box(es) next to the circulation modifiers(s) you wish to
\r
1848 delete.</para></step>
\r
1849 <step><para>Click <guibutton>Delete Selected</guibutton> near the top of the page.
\r
1850 <caution><para>The selected circulation modifiers will be deleted without a
\r
1851 verification alert.</para></caution>
\r
1855 <title>Editing Circulation Modifiers</title>
\r
1856 <indexterm><primary>circulation modifiers</primary><secondary>editing</secondary></indexterm>
\r
1857 <step><para>Double click on the row of the circulation modifier you wish to
\r
1858 edit.</para></step>
\r
1859 <step><para>Make desired changes.</para></step>
\r
1860 <step><para>Once you have finished editing, click
\r
1861 <guibutton>Save</guibutton>.</para></step>
\r
1864 <section xml:id="catalogingtemplates">
\r
1865 <title>Cataloging Templates</title>
\r
1866 <indexterm><primary>cataloging</primary><secondary>templates</secondary></indexterm>
\r
1867 <para>Cataloging templates are essential for making the cataloging process more efficient. Templates are used so that the basic structure of specific types of cataloging records can be loaded when the cataloger adds a new record</para>
\r
1869 <title>Adding Cataloging Templates</title>
\r
1872 Create a marc template in the directory <filename class="directory">/openils/var/templates/marc/</filename>. It should be in xml format.
\r
1873 Here is an example file <filename>k_book.xml</filename>:
\r
1875 <programlisting language="xml">
\r
1878 <leader>00620cam a2200205Ka 4500</leader>
\r
1879 <controlfield tag="008">070101s eng d</controlfield>
\r
1880 <datafield tag="010" ind1="" ind2="">
\r
1881 <subfield code="a"></subfield>
\r
1883 <datafield tag="020" ind1="" ind2="">
\r
1884 <subfield code="a"></subfield>
\r
1886 <datafield tag="082" ind1="0" ind2="4">
\r
1887 <subfield code="a"></subfield>
\r
1889 <datafield tag="092" ind1="" ind2="">
\r
1890 <subfield code="a"></subfield>
\r
1892 <datafield tag="100" ind1="" ind2="">
\r
1893 <subfield code="a"></subfield>
\r
1895 <datafield tag="245" ind1="" ind2="">
\r
1896 <subfield code="a"></subfield>
\r
1897 <subfield code="b"></subfield>
\r
1898 <subfield code="c"></subfield>
\r
1900 <datafield tag="260" ind1="" ind2="">
\r
1901 <subfield code="a"></subfield>
\r
1902 <subfield code="b"></subfield>
\r
1903 <subfield code="c"></subfield>
\r
1905 <datafield tag="300" ind1="" ind2="">
\r
1906 <subfield code="a"></subfield>
\r
1907 <subfield code="b"></subfield>
\r
1908 <subfield code="c"></subfield>
\r
1910 <datafield tag="500" ind1="" ind2="">
\r
1911 <subfield code="a"></subfield>
\r
1913 <datafield tag="650" ind1="" ind2="">
\r
1914 <subfield code="a"></subfield>
\r
1915 <subfield code="v"></subfield>
\r
1917 <datafield tag="650" ind1="" ind2="">
\r
1918 <subfield code="a"></subfield>
\r
1926 <para>Add the template to the to the <emphasis>marctemplates</emphasis> list in the open-ils.cat section of the Evergreen configuration file
\r
1927 <filename>opensrf.xml</filename><indexterm><primary>configuration files</primary><secondary>opensrf.xml</secondary></indexterm></para>
\r
1930 <para>Restart <systemitem class="service">Perl</systemitem><indexterm><primary>Perl</primary></indexterm> services for changes to take effect.</para>
\r
1931 <screen><userinput>/openils/bin/osrf_ctl.sh -l -a restart_perl</userinput></screen>
\r
1935 <section xml:id="relevancyrankings">
\r
1936 <title>Adjusting Search Relevancy Rankings</title>
\r
1937 <indexterm><primary>search relevancy</primary></indexterm>
\r
1940 <para>This section describes indexed field weighting and matchpoint weighting, which
\r
1941 control relevance ranking in Evergreen catalog search results. Adjusting relevancy can only be completed through access to the Evergreen database as of version 1.6.</para>
\r
1943 <para>In tuning search relevance, it is good practice to make incremental
\r
1944 adjustments, capture search logs, and assess results before making further
\r
1945 adjustments. </para>
\r
1950 <title>Indexed-field Weighting<indexterm><primary>search relevancy</primary><secondary>indexed-field weighting</secondary></indexterm> </title>
\r
1951 <para>Indexed-field weighting is configured in the Evergreen database in the weight column
\r
1952 of the <link linkend="config.table.metabib-field">config.metabib_field</link> table, which follows the other four columns in this table:
\r
1953 field_class, name, xpath, and format.</para>
\r
1954 <para>The following is one representative line from the <link linkend="config.table.metabib-field">config.metabib_field</link> table:</para>
\r
1956 author | conference | //mods32:mods/mods32:name[@type='conference']/mods32:
\r
1957 namePart[../mods32:role/mods32:roleTerm[text()='creator']] | mods32 | 1 )
\r
1959 <para>The default value for index-field weights in config.metabib_field is 1. Adjust the
\r
1960 weighting of indexed fields to boost or lower the relevance score for matches on that
\r
1961 indexed field. The weight value may be increased or decreased by whole integers. </para>
\r
1962 <para>For example, by increasing the weight of the title-proper field from 1 to 2, a search
\r
1963 for <emphasis role="bold">jaguar</emphasis> would double the relevance for the book titled
\r
1964 <emphasis role="italic">Aimee and Jaguar</emphasis> than for a record with the term
\r
1965 <emphasis role="bold">jaguar</emphasis> in another indexed field. </para>
\r
1968 <title>Match point Weighting</title>
\r
1969 <indexterm><primary>search relevancy</primary><secondary>match point weighting</secondary></indexterm>
\r
1970 <para> Match point weighting provides another way to fine-tune Evergreen relevance ranking,
\r
1971 and is configured through floating-point multipliers in the multiplier column of the
\r
1972 search.relevance_adjustment table.</para>
\r
1973 <para> Weighting can be adjusted for one, more, or all multiplier fields in
\r
1974 <link linkend="search.relevance">search.relevance_adjustment</link>.</para>
\r
1975 <para>You can adjust the following three matchpoints:</para>
\r
1978 <para>first_wordboosts relevance if the query is
\r
1979 one term long and matches the first term in the indexed field (search for <emphasis
\r
1980 role="bold">twain</emphasis>, get a bonus for <emphasis role="bold">twain, mark</emphasis>
\r
1981 but not <emphasis role="bold">mark twain</emphasis>)</para>
\r
1984 <para>word_order increases relevance for words
\r
1985 matching the order of search terms, so that the results for the search <emphasis
\r
1986 role="bold">legend suicide</emphasis> would match higher for the book <emphasis
\r
1987 role="italic">Legend of a Suicide</emphasis> than for the book,
\r
1988 <emphasis role="italic">Suicide Legend</emphasis></para>
\r
1991 <para>full_match boosts relevance when the full
\r
1992 query exactly matches the entire indexed field (after space, case, and diacritics are
\r
1993 normalized). So a title search for <emphasis role="italic">The Future of Ice</emphasis>
\r
1994 would get a relevance boost above <emphasis role="italic">Ice>Ages of the
\r
1995 Future</emphasis>.</para>
\r
1998 <para> Here are the default settings of the search.relevance_adjustment table: </para>
\r
1999 <table xml:id="search.relevance">
\r
2000 <title>search.relevance_adjustment table</title>
\r
2002 <colspec colnum="1" colname="col1" colwidth="1.0*"/>
\r
2003 <colspec colnum="2" colname="col2" colwidth="1.0*"/>
\r
2004 <colspec colnum="3" colname="col3" colwidth="1.0*"/>
\r
2005 <colspec colnum="4" colname="col4" colwidth="1.0*"/>
\r
2008 <entry>field_class</entry>
\r
2009 <entry>name</entry>
\r
2010 <entry>bump_type</entry>
\r
2011 <entry>multiplier</entry>
\r
2016 <entry>author</entry>
\r
2017 <entry>conference</entry>
\r
2018 <entry>first_word</entry>
\r
2019 <entry>1.5</entry>
\r
2022 <entry>author</entry>
\r
2023 <entry>corporate</entry>
\r
2024 <entry>first_word</entry>
\r
2025 <entry>1.5</entry>
\r
2028 <entry>author </entry>
\r
2029 <entry>other </entry>
\r
2030 <entry>first_word</entry>
\r
2031 <entry>1.5</entry>
\r
2034 <entry>author</entry>
\r
2035 <entry>personal</entry>
\r
2036 <entry>first_word</entry>
\r
2037 <entry>1.5</entry>
\r
2040 <entry>keyword</entry>
\r
2041 <entry>keyword</entry>
\r
2042 <entry>word_order</entry>
\r
2046 <entry>series</entry>
\r
2047 <entry>seriestitle</entry>
\r
2048 <entry>first_word</entry>
\r
2049 <entry>1.5</entry>
\r
2052 <entry>series</entry>
\r
2053 <entry>seriestitle</entry>
\r
2054 <entry>full_match</entry>
\r
2058 <entry>title</entry>
\r
2059 <entry>abbreviated</entry>
\r
2060 <entry>first_word</entry>
\r
2061 <entry>1.5</entry>
\r
2064 <entry>title</entry>
\r
2065 <entry>abbreviated</entry>
\r
2066 <entry>full_match</entry>
\r
2070 <entry>title</entry>
\r
2071 <entry>abbreviated</entry>
\r
2072 <entry>word_order</entry>
\r
2076 <entry>title</entry>
\r
2077 <entry>alternative</entry>
\r
2078 <entry>first_word</entry>
\r
2079 <entry>1.5</entry>
\r
2082 <entry>title</entry>
\r
2083 <entry>alternative</entry>
\r
2084 <entry>full_match</entry>
\r
2088 <entry>title</entry>
\r
2089 <entry>alternative</entry>
\r
2090 <entry>word_order</entry>
\r
2094 <entry>title</entry>
\r
2095 <entry>proper</entry>
\r
2096 <entry>first_word</entry>
\r
2097 <entry>1.5</entry>
\r
2100 <entry>title</entry>
\r
2101 <entry>proper</entry>
\r
2102 <entry>full_match</entry>
\r
2106 <entry>title</entry>
\r
2107 <entry>proper</entry>
\r
2108 <entry>word_order</entry>
\r
2112 <entry>title</entry>
\r
2113 <entry>translated</entry>
\r
2114 <entry>first_word</entry>
\r
2115 <entry>1.5</entry>
\r
2118 <entry>title</entry>
\r
2119 <entry>translated</entry>
\r
2120 <entry>full_match</entry>
\r
2124 <entry>title</entry>
\r
2125 <entry>translated</entry>
\r
2126 <entry>word_order</entry>
\r
2130 <entry>title</entry>
\r
2131 <entry>uniform</entry>
\r
2132 <entry>first_word</entry>
\r
2133 <entry>1.5</entry>
\r
2136 <entry>title</entry>
\r
2137 <entry>uniform</entry>
\r
2138 <entry>full_match</entry>
\r
2142 <entry>title</entry>
\r
2143 <entry>uniform</entry>
\r
2144 <entry>word_order</entry>
\r
2152 <title>Combining Index Weighting and Match point Weighting</title>
\r
2153 <indexterm><primary>search relevancy</primary><secondary>combining index weighting and match point weighting</secondary></indexterm>
\r
2155 <para>Index weighting and matchpoint weighting may be combined. The relevance boost of the combined
\r
2156 weighting is equal to the product of the two multiplied values. </para>
\r
2157 <para>If the relevance setting in the config.metabib_field were increased to 2, and the multiplier
\r
2158 set to 1.2 in the search.relevance_adjustment table, the resulting matchpoint increase would be
\r
2161 <para>In practice, these weights are applied serially -- first the index weight, then all
\r
2162 the matchpoint weights that apply -- because they are evaluated at different stages of the
\r
2163 search process.</para>
\r
2167 <title>Adjusting Relevancy for Keyword Searches</title>
\r
2168 <indexterm><primary>search relevancy</primary><secondary>keyword search adjusting</secondary></indexterm>
\r
2169 <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
2170 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
2171 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
2172 <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
2173 item are given more weight than terms in other fields. </para>
\r
2176 <para>From the command line, access the PostgreSQL command line interface</para>
\r
2177 <screen><userinput>psql -U evergreen</userinput></screen>
\r
2180 <para>Clone the title|proper index to create a keyword|title index</para>
\r
2181 <para>6 = the title|proper index</para>
\r
2183 INSERT INTO config.metabib_field
\r
2184 (field_class, name, xpath, weight, format, search_field, facet_field)
\r
2185 SELECT 'keyword', 'title', xpath, weight, format, search_field, facet_field
\r
2186 FROM config.metabib_field
\r
2191 <para>Populate the keyword|title index with a set of index entries cloned from the metabib.title_field_entry table;</para>
\r
2192 <para>6 = the title|proper index</para>
\r
2194 INSERT INTO metabib.keyword_field_entry
\r
2195 (source, field, value)
\r
2196 SELECT source, 17, value (the field value, 17, field be different in your database
\r
2197 so you may need to check the <link linkend="config.table.metabib-field">config.metabib_field</link>
\r
2198 for the id of your new index).
\r
2199 FROM metabib.title_field_entry
\r
2204 <para>Bump the relevance when the first search term appears first in the title in a keyword search.</para>
\r
2205 <para>17 = our new keyword|title index (This may be different in your database so you may need to check the
\r
2206 <link linkend="config.table.metabib-field">config.metabib_field</link> for the id
\r
2207 of your new index).</para>
\r
2209 INSERT INTO search.relevance_adjustment
\r
2210 (active, field, bump_type, multiplier)
\r
2211 VALUES (true, 17, 'first_word', 5);
\r
2215 <para>Boost the relevance for search terms appearing in the title in general</para>
\r
2216 <para>17 = our new keyword|title index (This may be different in your database so you may need to check the
\r
2217 <link linkend="config.table.metabib-field">config.metabib_field</link> for the id
\r
2218 of your new index).</para>
\r
2220 UPDATE config.metabib_field
\r
2228 <section xml:id="notifications">
\r
2229 <title>Notifications</title>
\r
2230 <para>Notifications can be set up for Holds, Overdue items and Predue items. There are two ways to configure notifications for each of these type of notifications.</para>
\r
2231 <section xml:id="Holdnotifications">
\r
2232 <title>Hold Notifications</title>
\r
2233 <indexterm><primary>notifications</primary><secondary>hold</secondary></indexterm>
\r
2234 <para>Hold notifications can be used so that library users are sent an email when their items are available for pickup. This notification is triggered when the item being held
\r
2235 is <emphasis>captured</emphasis> by a library staff member and the item is in the <emphasis>on holds shelf</emphasis> status. </para>
\r
2237 <title>Hold Notifications using the Action Trigger</title>
\r
2238 <para>The easiest way to set up hold notifications is to use the <link linkend="actiontriggers">Action Trigger</link> mechanism introduced in Evergreen 1.6.</para>
\r
2241 <para>From the staff client menu, Click on
\r
2243 <guimenu>Admin</guimenu>
\r
2244 <guisubmenu>Local Administration</guisubmenu>
\r
2245 <guisubmenu>Notifications / Action triggers</guisubmenu>
\r
2251 <para>Locate the Action Trigger Definition with the <guilabel>Name</guilabel> <guilabel>Hold Ready for Pickup Email Notification</guilabel>.</para>
\r
2254 <para>Double click on the item row to open the editing page, but <emphasis role="bold">not</emphasis> on the hyperlinked <guilabel>Name</guilabel></para>
\r
2257 <para>Check the <guilabel>Enabled</guilabel> check box to enable it.</para>
\r
2260 <para>Edit the <guilabel>Template</guilabel> text box to customize the body of the email as needed. Note that text between <quote>[% %]</quote> are variables to be
\r
2261 generated by the system. For example, <varname>[% user.family_name %]</varname> with be replaced by the family name of the user receiving a notice.</para>
\r
2264 <para>Click <guibutton>Save</guibutton> to save your changes.</para>
\r
2267 <para>Hold notices are now activated and will be processed the next time action triggers are processed. See <xref linkend="ProcessingActionTriggers" /> for
\r
2268 more details on processing action triggers.</para>
\r
2273 <title>Hold Notifications using the Evergreen Configuration File</title>
\r
2274 <para>An older method for Setting up hold notifications is through the Configuration file <filename>/openils/conf/opensrf.xml</filename>. </para>
\r
2277 <para>Open the file <filename>/openils/conf/opensrf.xml</filename> with your favorite text editor</para>
\r
2278 <para>Locate this section of the configuration file:</para>
\r
2280 <programlisting><![CDATA[
\r
2282 <email>true</email> <!-- set to true for hold notice emails -->
\r
2285 </programlisting>
\r
2288 <para>Ensure that <email> is set to <emphasis role="bold">true</emphasis>.</para>
\r
2291 <para>Locate the following section of the configuration file:</para>
\r
2292 <programlisting> <![CDATA[
\r
2295 <!-- global email notification settings -->
\r
2296 <template>/openils/var/data/hold_notification_template.example</template>
\r
2300 <para>Point the <template> variable to the hold notification template you will be using for hold notifications.</para>
\r
2303 <para>Locate the template and edit as desired. Use the example template provided as a guide.</para>
\r
2308 <section xml:id="overedueandpreduenotifications">
\r
2309 <title>Overdue and Predue Notifications</title>
\r
2310 <para>Overdue and Predue email notifications can be used to inform users that they have materials which are overdue or to warn them that materials are almost overdue.</para>
\r
2312 <title>Activating the Existing Overdue Action Triggers</title>
\r
2313 <indexterm><primary>notifications</primary><secondary>overdue</secondary><tertiary>activating action triggers</tertiary></indexterm>
\r
2314 <para>The easiest way to set up overdue notifications is to use the <link linkend="actiontriggers">Action Trigger</link> mechanism introduced in Evergreen 1.6.</para>
\r
2317 <para>From the staff client menu, Click on
\r
2319 <guimenu>Admin</guimenu>
\r
2320 <guisubmenu>Local Administration</guisubmenu>
\r
2321 <guisubmenu>Notifications / Action triggers</guisubmenu>
\r
2327 <para>Locate the Action Trigger Definition you wish to activate. There are several overdue notices preloaded wit Evergreen 1.6.</para>
\r
2330 <para>Double click on the item row to open the editing page, but <emphasis role="bold">not</emphasis> on the hyperlinked <guilabel>Name</guilabel></para>
\r
2333 <para>Check the <guilabel>Enabled</guilabel> check box to enable it.</para>
\r
2336 <para>Edit the <guilabel>Template</guilabel> text box to customize the body of the email as needed. Note that text between <quote>[% %]</quote> are variables to be
\r
2337 generated by the system. For example, <varname>[% user.family_name %]</varname> with be replaced by the family name of the user receiving a notice.</para>
\r
2340 <para>Click <guibutton>Save</guibutton> to save your changes.</para>
\r
2343 <para>Overdue notices are now activated and will be processed the next time action triggers are processed. See <xref linkend="ProcessingActionTriggers" /> for
\r
2344 more details on processing action triggers.</para>
\r
2349 <title>Creating Overdue and Predue Notifications by Cloning Existing Action Triggers</title>
\r
2350 <indexterm><primary>notifications</primary><secondary>overdue</secondary><tertiary>creating using action triggers</tertiary></indexterm>
\r
2351 <indexterm><primary>notifications</primary><secondary>predue</secondary><tertiary>creating using action triggers</tertiary></indexterm>
\r
2352 <para>If you wish to add overdue notices for different periods of time or wish to create a predue notice simply clone an existing overdue note, give it a
\r
2353 unique <guilabel>Name</guilabel>, customize as needed. and save.</para>
\r
2354 <para>There are no pre-existing predue notices so they will need to be created by cloning an existing overdue notice.
\r
2355 To make them predue notices, use a negative value in the <guilabel>Processing Delay Context Field</guilabel>. For example, to create a predue notice the day before the
\r
2356 due date, use the value <emphasis>-1 days</emphasis>.</para>
\r
2359 <title>Creating Overdue and Predue Notices using the Evergreen Configuration File</title>
\r
2360 <indexterm><primary>notifications</primary><secondary>overdue</secondary><tertiary>creating using the configuration file</tertiary></indexterm>
\r
2361 <indexterm><primary>notifications</primary><secondary>predue</secondary><tertiary>creating using the configuration file</tertiary></indexterm>
\r
2362 <para>It is also possible to create overdue and predue notices using the Evergreen configuration file <filename>/openils/conf/opensrf.xml</filename></para>
\r
2365 <para>Open <filename>/openils/conf/opensrf.xml</filename> with your favorite text editor.</para>
\r
2366 <para>Locate this section of the configuration file:</para>
\r
2368 <programlisting><
projects / working / Evergreen.git / blob