-<?xml version='1.0' encoding='UTF-8'?>
-<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"
-xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="serveradministration">
- <info>
- <title>Server Administration</title>
- <abstract>
- <para>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.</para>
- </abstract>
- </info>
- <section xml:id="orgtyes">
- <title>Organizational Unit Types and Organizational Units</title>
- <section>
- <title>Organizational Unit Types</title>
- <para>Organizational Unit Types are the terms used to refer to levels in the hierarchy of your
- library system(s). Examples could include>All-Encompassing Consortium, Consortium Within a
- Consortium, Library System, Branch, Bookmobile, Sub-Branch, Twig, etc.</para>
- <para>You can add or remove organizational unit types, and rename them as needed to match the
- organizational hierarchy that exists in reality for the libraries using your installation of
- Evergreen. Evergreen can support organizations as simple as a single library with one or more
- branches or as complex as a consortium composed of many independently governed library
- systems. Organizational unit types should never have proper names since they are only generic types .</para>
- <para>The fields in the organizational unit type record include:</para>
- <itemizedlist>
- <listitem>Type Name - The name of the organization unit type.</listitem>
- <listitem>Opac Label - This is the label displayed in the OPAC to describe the search
- range and the copy count columns for results. They are <emphasis>range
- relative</emphasis> labels.</listitem>
-
- <listitem>Parent Type - The parent organizational unit type of this type.</listitem>
- <listitem>Can Have Volumes - Flag that allows an organizational unit of this type to contain
- Volumes/Call Numbers and thus Copies.</listitem>
- <listitem>Can Have Users - Flag that allows an Organizational unit of this type to be home to
- Users.</listitem>
- </itemizedlist>
- <para>An organizational unit type can be added, edited, or removed using the staff client.</para>
- <para>To navigate to the <emphasis>Organization Unit Types</emphasis> from the staff client select
- <menuchoice>
- <guimenu>Admin</guimenu>
- <guisubmenu>Server Administration</guisubmenu>
- <guisubmenu>Organization Types</guisubmenu>
- </menuchoice>
- </para>
- <procedure>
- <title>Adding Organization Types</title>
- <step><para>Select an organization type from the organization type tree on the left and
- click <guibutton>New Child</guibutton>.</para></step>
- <step><para>Make sure your new type is selected and edit the <guilabel>Type Name</guilabel>,
- <guilabel>OPAC Label</guilabel> and <guilabel>Parent Type</guilabel>.</para></step>
- <step><para>Change the <guilabel>Parent Type</guilabel> if necessary.</para></step>
- <step><para>Check the <guilabel>Can Have Volumes and Copies</guilabel> checkbox if the
- organization units of this type will have volumes and copies assigned to it.</para></step>
- <step><para>Check the <guilabel>Can Have Users</guilabel> checkbox if you will allow users
- to be have the organization units of this type as their home unit.</para></step>
- <step><para>Click <guibutton>Save</guibutton> to save your new organization type.
- </para></step>
- </procedure>
- <procedure>
- <title>Deleting Organization Types</title>
- <step><para>Select the <emphasis>organization type</emphasis> from the <emphasis>Organization Type</emphasis>
- tree.</para></step>
- <step><para>Click <guibutton>Delete</guibutton>.</para></step>
- <step><para>Click <guibutton>OK</guibutton> on the warning alert box.</para></step>
- <note>
- <para>You will not be able to delete organization types if organization units are
- assigned to that type. Before you can delete the organization
- Type, you must change the organization type of the units associated with the type
- or delete the units.</para>
- </note>
- </procedure>
- <procedure>
- <title>Editing Organization Types</title>
- <step><para>Select the <emphasis>organization type</emphasis> you wish to edit from the
- organization type tree.</para></step>
- <step><para>Make the changes in the right pane.</para></step>
- <step><para>Click <guibutton>Save</guibutton> to save your changes.</para></step>
- </procedure>
- </section>
- </section>
- <section xml:id="orgunits">
- <title>Organizational Units</title>
- <abstract>
- <para>Organizational Units are the specific instances of the organization unit types that
- make up your library's hierarchy. These can include consortia, systems, branches,
- etc. The organizational units should have distictive proper names such as
- <emphasis>Main Street Branch</emphasis> or <emphasis>Townsville Campus</emphasis>.</para>
- </abstract>
- <para>To navigate to the organizational units adminstration page in the staff client select
- <menuchoice>
- <guimenu>Admin</guimenu>
- <guisubmenu>Server Administration</guisubmenu>
- <guisubmenu>Organizational Units</guisubmenu>
- </menuchoice>
- </para>
- <procedure>
- <title>Adding Organizational Units</title>
- <step><para>Select an <emphasis>Organizational Unit</emphasis> from the organizational unit tree on the left and click
- <guibutton>New Child</guibutton>.</para></step>
- <step><para>Make sure your new unit is selected and edit the <guilabel>Organizational Unit
- Name</guilabel>, <guilabel>Organizational Unit Policy Code</guilabel>,
- <guilabel>Main Email Address</guilabel> and <guilabel>Main Phone Number</guilabel>.</para>
- <note>
- <para>The <emphasis>Organizational Unit Name</emphasis> is the name that will appear in the
- OPAC. The <emphasis>Policy Code</emphasis> is used by the system to associate policies and
- copies with the unit.</para>
- </note>
- </step>
- <step><para>Select the <guilabel>Organization Unit Type</guilabel> and
- <guilabel>Parent Organization Unit</guilabel>.</para></step>
- <step><para>Check the <guilabel>Can Have Volumes and Copies</guilabel> checkbox if the
- organization units of this type will have volumes and copies assigned to it.</para></step>
- <step><para>Check the <guilabel>OPAC Visible</guilabel> checkbox if you want this location to be
- visible in the OPAC for searching.</para></step>
- <step><para>Click <guibutton>Save</guibutton> to save your new organizational unit.</para></step>
- </procedure>
- <procedure>
- <title>Deleting Organizational Units</title>
- <step><para>Select the <emphasis>organizational unit</emphasis> you wish to delete from the organzational unit tree in the left pane.</para></step>
- <step><para>Click<guibutton>Delete</guibutton>.</para></step>
- <step><para>Click <guibutton>OK</guibutton> on the warning alert box.</para></step>
- <note>
- <para>You will not be able to delete organizational units if you have
- users, workstations or copies assigned to the unit. Before you can delete the
- organizational unit, you must move its users, workstations, copies and other associated resources to other
- organizational units units.</para>
- </note>
- </procedure>
- <procedure>
- <title>Editing Organizational Units</title>
- <step><para>Select the organizational unit you wish to edit from the
- organizational unit tree in the left pane.</para></step>
- <step><para>Edit the fields in the right pane.</para></step>
- <step><para>Click <guibutton>Save</guibutton> to save your changes.</para></step>
- </procedure>
- </section>
- <section xml:id="relevancyrankings">
- <title>Adjusting Search Relevancy Rankings</title>
- <info>
- <abstract>
- <para>This section describes indexed field weighting and matchpoint weighting, which
- control relevance ranking in Evergreen catalog search results. Adjusting relavancy can only be completed through access to the Evergreen database as of version 1.6.</para>
- <tip>
- <para>In tuning search relevance, it is good practice to make incremental
- adjustments, capture search logs, and assess results before making further
- adjustments. </para>
- </tip>
- </abstract>
- </info>
- <section>
- <title>Indexed-field Weighting</title>
- <para>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:
- field_class, name, xpath, and format.</para>
- <para>The following is one representative line from the config.metabib_field table:</para>
- <para> author | conference | //mods32:mods/mods32:name[@type='conference']/mods32:namePart[../mods32:role/mods32:roleTerm[text()='creator']] | mods32 | 1 ) </para>
- <para>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. </para>
- <para>For example, by increasing the weight of the title-proper field from 1 to 2, a search
- for <emphasis role="bold">jaguar</emphasis> would double the relevance for the book titled
- <emphasis role="italic">Aimee and Jaguar</emphasis> than for a record with the term
- <emphasis role="bold">jaguar</emphasis> in another indexed field. </para>
- </section>
- <section>
- <title>Matchpoint Weighting</title>
- <para> Matchpoint weighting provides another way to fine-tune Evergreen relevance ranking,
- and is configured through floating-point multipliers in the multiplier column of the
- search.relevance_adjustment table.</para>
- <para> Weighting can be adjusted for one, more, or all multiplier fields in
- search.relevance_adjustment.</para>
- <para>You can adjust the following three matchpoints:</para>
- <itemizedlist>
- <listitem>
- <para><indexterm><primary>first_word</primary></indexterm> boosts relevance if the query is
- one term long and matches the first term in the indexed field (search for <emphasis
- role="bold">twain</emphasis>, get a bonus for <emphasis role="bold">twain, mark</emphasis>
- but not <emphasis role="bold">mark twain</emphasis>)</para>
- </listitem>
- <listitem>
- <para><indexterm><primary>word_order</primary></indexterm> increases relevance for words
- matching the order of search terms, so that the results for the search <emphasis
- role="bold">legend suicide</emphasis> would match higher for the book <emphasis
- role="italic">Legend of a Suicide</emphasis> than for the book,
- <emphasis role="italic">Suicide Legend</emphasis></para>
- </listitem>
- <listitem>
- <para><indexterm><primary>full_match</primary></indexterm> boosts relevance when the full
- query exactly matches the entire indexed field (after space, case, and diacritics are
- normalized). So a title search for <emphasis role="italic">The Future of Ice</emphasis>
- would get a relevance boost above <emphasis role="italic">Ice>Ages of the
- Future</emphasis>.</para>
- </listitem>
- </itemizedlist>
- <para> Here are the default settings of the search.relevance_adjustment table: </para>
- <table xml:id="search.relevance">
- <title>search.relevance_adjustment table</title>
- <tgroup cols="4">
- <thead>
- <row>
- <entry>field_class</entry>
- <entry>name</entry>
- <entry>bump_type</entry>
- <entry>multiplier</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>author</entry>
- <entry>conference</entry>
- <entry>first_word</entry>
- <entry>1.5</entry>
- </row>
- <row>
- <entry>author</entry>
- <entry>corporate</entry>
- <entry>first_word</entry>
- <entry>1.5</entry>
- </row>
- <row>
- <entry>author </entry>
- <entry>other </entry>
- <entry>first_word</entry>
- <entry>1.5</entry>
- </row>
- <row>
- <entry>author</entry>
- <entry>personal</entry>
- <entry>first_word</entry>
- <entry>1.5</entry>
- </row>
- <row>
- <entry>keyword</entry>
- <entry>keyword</entry>
- <entry>word_order</entry>
- <entry>10</entry>
- </row>
- <row>
- <entry>series</entry>
- <entry>seriestitle</entry>
- <entry>first_word</entry>
- <entry>1.5</entry>
- </row>
- <row>
- <entry>series</entry>
- <entry>seriestitle</entry>
- <entry>full_match</entry>
- <entry>20</entry>
- </row>
- <row>
- <entry>title</entry>
- <entry>abbreviated</entry>
- <entry>first_word</entry>
- <entry>1.5</entry>
- </row>
- <row>
- <entry>title</entry>
- <entry>abbreviated</entry>
- <entry>full_match</entry>
- <entry>20</entry>
- </row>
- <row>
- <entry>title</entry>
- <entry>abbreviated</entry>
- <entry>word_order</entry>
- <entry>10</entry>
- </row>
- <row>
- <entry>title</entry>
- <entry>alternative</entry>
- <entry>first_word</entry>
- <entry>1.5</entry>
- </row>
- <row>
- <entry>title</entry>
- <entry>alternative</entry>
- <entry>full_match</entry>
- <entry>20</entry>
- </row>
- <row>
- <entry>title</entry>
- <entry>alternative</entry>
- <entry>word_order</entry>
- <entry>10</entry>
- </row>
- <row>
- <entry>title</entry>
- <entry>proper</entry>
- <entry>first_word</entry>
- <entry>1.5</entry>
- </row>
- <row>
- <entry>title</entry>
- <entry>proper</entry>
- <entry>full_match</entry>
- <entry>20</entry>
- </row>
- <row>
- <entry>title</entry>
- <entry>proper</entry>
- <entry>word_order</entry>
- <entry>10</entry>
- </row>
- <row>
- <entry>title</entry>
- <entry>translated</entry>
- <entry>first_word</entry>
- <entry>1.5</entry>
- </row>
- <row>
- <entry>title</entry>
- <entry>translated</entry>
- <entry>full_match</entry>
- <entry>20</entry>
- </row>
- <row>
- <entry>title</entry>
- <entry>translated</entry>
- <entry>word_order</entry>
- <entry>10</entry>
- </row>
- <row>
- <entry>title</entry>
- <entry>uniform</entry>
- <entry>first_word</entry>
- <entry>1.5</entry>
- </row>
- <row>
- <entry>title</entry>
- <entry>uniform</entry>
- <entry>full_match</entry>
- <entry>20</entry>
- </row>
- <row>
- <entry>title</entry>
- <entry>uniform</entry>
- <entry>word_order</entry>
- <entry>10</entry>
- </row>
- </tbody>
- </tgroup>
- </table>
- </section>
- <section>
- <title>Combining Index Weighting and Matchpoint Weighting</title>
- <para>Index weighting and matchpoint weighting may be combined. The relevance boost of the combined
- weighting is equal to the product of the two multiplied values. </para>
- <para>If the relevance setting in the config.metabib_field were increased to 2, and the multiplier
- set to 1.2 in the search.relevance_adjustment table, the resulting matchpoint increase would be
- 240%. </para>
- <note>
- <para>In practice, these weights are applied serially -- first the index weight, then all
- the matchpoint weights that apply -- because they are evaluated at different stages of the
- search process.</para>
- </note>
- </section>
- <section>
- <title>Adjusting Relevancy for Keyword Searches</title>
- <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
- 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. </para>
- <procedure>
- <step>
- <para>From the command line, access the PorstgreSQL command line interface</para>
- <screen>psql -U evergreen</screen>
- </step>
- <step>
- <para>Clone the title|proper index to create a keyword|title index</para>
- <para>6 = the title|proper index</para>
- <screen>INSERT INTO config.metabib_field
- (field_class, name, xpath, weight,</screen>
- <screen>format, search_field, facet_field)</screen>
- <screen>SELECT 'keyword', 'title', xpath, weight, format,</screen>
- <screen>search_field, facet_field</screen>
- <screen>FROM config.metabib_field</screen>
- <screen>WHERE id = 6;</screen>
- </step>
- <step>
- <para>Populate the keyword|title index with a set of index entries cloned from the metabib.title_field_entry table;</para>
- <para>6 = the title|proper index</para>
- <screen>INSERT INTO metabib.keyword_field_entry (source, field, value)</screen>
- <screen>SELECT source, 17, value (the field value, 17, field be different
- in your database so you may need to check the
- <emphasis>config.metabib_field</emphasis> for the id of your new index).</screen>
- <screen>FROM metabib.title_field_entry</screen>
- <screen>WHERE field = 6;</screen>
- </step>
- <step>
- <para>Bump the relevance when the first search term appears first in the title in a keyword search.</para>
- <para>17 = our new keyword|title index (This may be different in your database so you may need to check the <emphasis>config.metabib_field</emphasis> for the id
- of your new index).</para>
- <screen>INSERT INTO search.relevance_adjustment
- (active, field, bump_type, multiplier)</screen>
- <screen>VALUES (true, 17, 'first_word', 5); </screen>
- </step>
- <step>
- <para>Boost the relevance for search terms appearing in the title in general</para>
- <para>17 = our new keyword|title index (This may be different in your database so you may need to check the <emphasis>config.metabib_field</emphasis> for the id
- of your new index).</para>
- <screen>UPDATE config.metabib_field</screen>
- <screen>SET weight = 10</screen>
- <screen>WHERE id = 17;</screen>
- </step>
- </procedure>
- </section>
- </section>
- <section xml:id="grouppermissions">
- <title>User and Group Permissions</title>
- <abstract>
- <para>It is essential to understand how user and group permissions can be used to allow staff
- to fulfil their roles while ensuring that they only have access to the appropriate level.</para>
- <para>Permissions in <application>Evergreen</application> are applied to a specific location and system depth based on the home
- library of the user. The user will only have that permission within the scope provided by the
- <emphasis>Depth</emphasis> field in relation to his/her working locations.</para>
- <para>Evergreen provides group application permissions in order to restrict which staff members
- have the ability to assign elevated permissions to a user, and which staff members have the ability
- to edit users in particular groups.</para>
- </abstract>
- <section>
- <title>User Permissions</title>
- <tip><para>Ihe User permissions editor allows an administrator to set up permission fopr an individual user. However, In most cases, permissions can be controlled more
- efficiently at the group level with individuals being assigned to specific groups based on their roles in the library.</para></tip>
- <para>To open the user permission editor, select <menuchoice><guimenu>Admin</guimenu>
- <guisubmenu>User Permission Editor</guisubmenu></menuchoice>. Type the user's barcode when prompted.</para>
- <section>
- <title>Working Locations</title>
- <para>The first section of the User Permission Editor is the the Working Locations
- section. You may select more than one working location for a user. This will effect
- the availability of certain permissions which are dependent on the user having the working location.</para>
- </section>
- <section>
- <title>User Permission Settings</title>
- <para>Below the working locations is the long list of all the permissions available on your
- system. For each permission you can apply it by checking the
- <emphasis>Applied</emphasis> check box. You can also select a depth to which the
- permission is applied and also make the permission <emphasis>grantable</emphasis>, allowing
- the user the ability to grant the permission to others.</para>
- </section>
- </section>
- <section>
- <title>Group Permissions</title>
- <para>Most permissions should be assigned at the group level. Here you can create new
- groups based on the roles and responsibilities of the users in your system. Staff will be able to
- assign users to these groups when they register patrons.</para>
- <tip><para>It is a good idea to create your groups soon after creating your organizational units.
- It is also imprtaant to give careful consideration to the hierarchy of your groups to make
- permission assignment as efficient as possible.</para></tip>
- <para>To enter the <emphasis>Group Permission</emphasis> module from the staff client menu, select
- <menuchoice><guimenu>Admin</guimenu> <guisubmenu>Server Administration</guisubmenu>
- <guisubmenu>Permission Groups</guisubmenu></menuchoice></para>
- <procedure>
- <title>Adding Groups</title>
- <step><para>Select the <guibutton>Group Configuration</guibutton> tab if not
- already selected in the right pane</para></step>
- <step><para>Click <guibutton>New Child</guibutton></para></step>
- <step><para>Enter a unique <guilabel>Group Name</guilabel></para></step>
- <step><para>Enter a <guilabel>Description</guilabel></para></step>
- <step><para>Select a <guilabel>Permission Interval</guilabel>. This will determine the
- default expiry date of user account when you register patrons and select
- their groups</para></step>
- <step><para>Selecting an <guilabel>Editing Permission</guilabel> will determine the group level the user will have for editing other users.</para></step>
- <step><para>Select the <guilabel>Parent Group</guilabel> for the group.</para>
- <note><para>The group will inherit its parent group's permissions so it is unecessary to assign permissions already inherited from its parent.</para></note></step>
- <step><para>Click the <guibutton>Save</guibutton> button.</para></step>
- </procedure>
- <procedure>
- <title>Deleting Groups</title>
- <step><para>Select the group you wish to delete from the group tree on
- left pane.</para></step>
- <step><para>Click the <guibutton>Delete</guibutton> button.</para></step>
- <step><para>Click on <guibutton>OK</guibutton>to verify.</para></step>
- </procedure>
- <procedure>
- <title>Editing Groups</title>
- <step><para>Select the group you wish to edit from the group tree on left pane.</para></step>
- <step><para>Edit the fields you wish to change in the right pane.</para></step>
- <step><para>Click on <guibutton>Save</guibutton> to save changes.</para></step>
- </procedure>
- <procedure>
- <title>Adding Group Permissions</title>
- <step><para>Select the <guibutton>Group Permissions</guibutton> tab on the right
- pane</para></step>
- <step><para>Click on <guibutton>New Mapping</guibutton>.</para></step>
- <step><para>Select the permission you would like to add from the
- <guibutton>Permission</guibutton> Select box.</para></step>
- <step><para>Select the <guibutton>Depth</guibutton> you wish to set the
- permission. This will determine if the group has the permission at a local level or across a
- system, or consortium, or other organizational unit type.</para></step>
- <step><para>check the <guibutton>Grantable</guibutton> check box to allow the user to
- grant the permission to others.</para></step>
- <step><para>Click <guibutton>Add Mapping</guibutton> to add the permission to the
- group</para></step>
- </procedure>
- <procedure>
- <title>Deleting Group Permissions</title>
- <step><para>Select the group permission you wish to delete.</para></step>
- <step><para>Click the <guibutton>Delete Selected</guibutton> button.</para></step>
- <step><para>Click on <guibutton>OK</guibutton> to verify</para></step>
- </procedure>
- <procedure>
- <title>Editing Group Permissions</title>
- <step><para>Click on the <guilabel>Depth</guilabel> or <guilabel>Grantable</guilabel>
- field for the permission setting you wish to change.</para></step>
- <step><para>Make changes to other permissions in the same way.</para></step>
- <step><para>Click <guibutton>Save Changes</guibutton> when you are finished all
- the changes.</para></step>
- </procedure>
- </section>
- <section>
- <title>Permissions</title>
- <table xml:id="permissiondescriptions">
- <title>Permissions Table</title>
- <tgroup cols="2">
- <thead>
- <row>
- <entry>Permission Name</entry>
- <entry>Permission Description</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>ABORT_REMOTE_TRANIST</entry>
- <entry>Allows user to abort a copy transit if the user is not at
- the transit source or destination</entry>
- </row>
- <row>
- <entry>ABORT_TRANSIT</entry>
- <entry>Allows user to abort a copy transit if the user is at the
- transit destination or source</entry>
- </row>
- <row>
- <entry>ASSIGN_WORK_ORG_UNIT </entry>
- <entry>Allows user to define where another staff member's
- permissions apply via the Permissions Editor interface.</entry>
- </row>
- <row>
- <entry>BAR_PATRON</entry>
- <entry>Allows user to bar a patron</entry>
- </row>
- <row>
- <entry>CANCEL_HOLDS</entry>
- <entry>Allows user to cancel holds</entry>
- </row>
- <row>
- <entry>CIRC_CLAIMS_RETURNED.override</entry>
- <entry>Allows user to check in/out an item that is claims
- returned</entry>
- </row>
- <row>
- <entry>CIRC_EXCEEDS_COPY_RANGE.override</entry>
- <entry>Allows user to override the copy exceeds range event</entry>
- </row>
- <row>
- <entry>CIRC_OVERRIDE_DUE_DATE</entry>
- <entry>Allows user to change due date</entry>
- </row>
- <row>
- <entry>CIRC_PERMIT_OVERRIDE</entry>
- <entry>Allows user to bypass the circ permit call for i
- checkout</entry>
- </row>
- <row>
- <entry>COPY_ALERT_MESSAGE.override</entry>
- <entry>Allows user to check in/out an item that has an alert
- message</entry>
- </row>
- <row>
- <entry>COPY_BAD_STATUS.override</entry>
- <entry>Allows user to check out an item in a non-circulatable
- status</entry>
- </row>
- <row>
- <entry>COPY_CHECKIN</entry>
- <entry>Allows user to check in a copy</entry>
- </row>
- <row>
- <entry>COPY_CHECKOUT</entry>
- <entry>Allows user to check out a copy</entry>
- </row>
- <row>
- <entry>COPY_CIRC_NOT_ALLOWED.override</entry>
- <entry>Allows user to checkout an item that is marked as
- non-circ</entry>
- </row>
- <row>
- <entry>COPY_HOLDS</entry>
- <entry>Allows user to place a hold on a specific copy</entry>
- </row>
- <row>
- <entry>COPY_IS_REFERENCE.override</entry>
- <entry>Allows user to override the copy_is_reference event</entry>
- </row>
-
- <row>
- <entry>COPY_NOT_AVAILABLE.override</entry>
- <entry>Allows user to force checkout of Missing/Lost type
- items</entry>
- </row>
- <row>
- <entry>COPY_STATUS_LOST.override</entry>
- <entry>Allows user to remove the lost status from a copy</entry>
- </row>
- <row>
- <entry>COPY_STATUS_MISSING.override</entry>
- <entry>Allows user to change the missing status on a copy</entry>
- </row>
- <row>
- <entry>COPY_TRANSIT_RECEIVE</entry>
- <entry>Allows user to close out a transit on a copy</entry>
- </row>
- <row>
- <entry>CREATE_BILL</entry>
- <entry>Allows user to create a new bill on a transaction</entry>
- </row>
- <row>
- <entry>CREATE_CONTAINER</entry>
- <entry>Allows user to create containers owned by other users
- (containers are Item Buckets, Volume Buckets, and Book Bags)</entry>
- </row>
- <row>
- <entry>CREATE_CONTAINER_ITEM</entry>
- <entry>Allows user to place an item in a container (even if the
- container is owned by other users).</entry>
- </row>
- <row>
- <entry>CREATE_COPY</entry>
- <entry>Allows user to create a new copy object</entry>
- </row>
- <row>
- <entry>CREATE_COPY_LOCATION</entry>
- <entry>Allows user to create a new copy location</entry>
- </row>
- <row>
- <entry>CREATE_COPY_NOTE</entry>
- <entry>Allows user to create a new copy note</entry>
- </row>
- <row>
- <entry>CREATE_COPY_STAT_CAT</entry>
- <entry>Allows user to create a statisitcal category for
- copies</entry>
- </row>
- <row>
- <entry>CREATE_COPY_STAT_CAT_ENTRY</entry>
- <entry>Allows user to create a new entry for a copy statistical
- category</entry>
- </row>
- <row>
- <entry>CREATE_COPY_STAT_CAT_ENTRY_MAP</entry>
- <entry>Allows user to link a copy to a statistical category
- (i.e., allows user to specify the appropriate entry for a copy and
- given statistical category)</entry>
- </row>
- <row>
- <entry>CREATE_COPY_TRANSIT</entry>
- <entry>Allows user to create a transit</entry>
- </row>
- <row>
- <entry>CREATE_DUPLICATE_HOLDS</entry>
- <entry>Allows user to create duplicate holds (e.g. two holds on the
- same title)</entry>
- </row>
- <row>
- <entry>CREATE_HOLD_NOTIFICATION</entry>
- <entry>Allows user to create new hold notifications</entry>
- </row>
- <row>
- <entry>CREATE_IN_HOUSE_USE</entry>
- <entry>Allows user to create a new in-house-use</entry>
- </row>
- <row>
- <entry>CREATE_MARC</entry>
- <entry>Allows user to create new MARC records</entry>
- </row>
- <row>
- <entry>CREATE_MY_CONTAINER</entry>
- <entry>Allows user to create containers for self (containers are
- Item Buckets, Volume Buckets, and Book Bags).</entry>
- </row>
- <row>
- <entry>CREATE_NON_CAT_TYPE</entry>
- <entry>Allows user to create a new non-cataloged item type</entry>
- </row>
- <row>
- <entry>CREATE_PATRON_STAT_CAT</entry>
- <entry>Allows user to create a new patron statistical
- category</entry>
- </row>
- <row>
- <entry>CREATE_PATRON_STAT_CAT_ENTRY</entry>
- <entry>Allows user to create a new possible entry for patron
- statistical categories</entry>
- </row>
- <row>
- <entry>CREATE_PATRON_STAT_CAT_ENTRY_MAP</entry>
- <entry>Allows user to link another user to a stat cat entry (i.e.,
- specify the patron's entry for a given statistical category)</entry>
- </row>
- <row>
- <entry>CREATE_PAYMENT</entry>
- <entry>Allows user to record payments in the Billing
- Interface</entry>
- </row>
- <row>
- <entry>CREATE_TITLE_NOTE</entry>
- <entry>Allows user to create a new title note</entry>
- </row>
- <row>
- <entry>CREATE_TRANSACTION</entry>
- <entry>Allows user to create new billable transactions (these
- include checkouts and transactions created via the Bill Patron
- operation)</entry>
- </row>
- <row>
- <entry>CREATE_TRANSIT</entry>
- <entry>Allows user to place item in transit</entry>
- </row>
- <row>
- <entry>CREATE_USER</entry>
- <entry>Allows user to create another user</entry>
- </row>
- <row>
- <entry>CREATE_USER_GROUP_LINK</entry>
- <entry>Allows user to add other users to permission groups</entry>
- </row>
- <row>
- <entry>CREATE_VOLUME</entry>
- <entry>Allows user to create a volume</entry>
- </row>
- <row>
- <entry>CREATE_VOLUME_NOTE</entry>
- <entry>Allows user to create a new volume note</entry>
- </row>
- <row>
- <entry>DELETE_CONTAINER</entry>
- <entry>Allows user to delete containers (containers are Item Buckets,
- Volume Buckets, and Book Bags).</entry>
- </row>
- <row>
- <entry>DELETE_CONTAINER_ITEM</entry>
- <entry>Allows user to remove items from buckets and bookbags</entry>
- </row>
- <row>
- <entry>DELETE_COPY</entry>
- <entry>Allows user to delete a copy</entry>
- </row>
- <row>
- <entry>DELETE_COPY_LOCATION</entry>
- <entry>Allows user to delete a copy location</entry>
- </row>
- <row>
- <entry>DELETE_COPY_NOTE</entry>
- <entry>Allows user to delete copy notes</entry>
- </row>
- <row>
- <entry>DELETE_COPY_STAT_CAT</entry>
- <entry>Allows user to delete a copy statistical category</entry>
- </row>
- <row>
- <entry>DELETE_COPY_STAT_CAT_ENTRY</entry>
- <entry>Allows user to delete an entry for a copy statistical
- category</entry>
- </row>
- <row>
- <entry>DELETE_COPY_STAT_CAT_ENTRY_MAP</entry>
- <entry>Allows user to delete a copy stat cat entry map</entry>
- </row>
- <row>
- <entry>DELETE_NON_CAT_TYPE</entry>
- <entry>Allows user to delete a non cataloged type (the user still
- cannot deleted a non-cat type if any items of that type have
- circulated).</entry>
- </row>
- <row>
- <entry>DELETE_PATRON_STAT_CAT</entry>
- <entry>Allows user to delete a patron statistical category</entry>
- </row>
- <row>
- <entry>DELETE_PATRON_STAT_CAT_ENTRY</entry>
- <entry>Allows user to delete an entry for patron statistical
- categories</entry>
- </row>
- <row>
- <entry>DELETE_PATRON_STAT_CAT_ENTRY_MAP</entry>
- <entry>Allows user to remove a patron's entry for a given
- statistical category</entry>
- </row>
- <row>
- <entry>DELETE_RECORD</entry>
- <entry>Allows user to delete a bib record</entry>
- </row>
- <row>
- <entry>DELETE_TITLE_NOTE</entry>
- <entry>Allows user to delete title notes</entry>
- </row>
- <row>
- <entry>DELETE_USER</entry>
- <entry>Allows user to mark a user as deleted</entry>
- </row>
- <row>
- <entry>DELETE_VOLUME</entry>
- <entry>Allows user to delete a volume</entry>
- </row>
- <row>
- <entry>DELETE_VOLUME_NOTE</entry>
- <entry>Allows user to delete volume notes</entry>
- </row>
- <row>
- <entry>DELETE_WORKSTATION</entry>
- <entry>Allows user to remove an existing workstation so a new one
- can replace it</entry>
- </row>
- <row>
- <entry>EVERYTHING</entry>
- <entry> Every permssion is granted (for sysadmins and developers
- only!)</entry>
- </row>
- <row>
- <entry>HOLD_EXISTS.override</entry>
- <entry>Allows users to place multiple holds on a single
- copy/volume/title/metarecord (depending on hold type)</entry>
- </row>
- <row>
- <entry>IMPORT_MARC</entry>
- <entry>Allows user to import a MARC record via the z39.50
- interface</entry>
- </row>
- <row>
- <entry>ITEM_AGE_PROTECTED.override</entry>
- <entry>Allows user to place a hold on an age-protected item</entry>
- </row> <row>
- <entry>ITEM_ON_HOLDS_SHELF.override</entry>
- <entry>Allows user to check out an item that is on holds shelf for a
- different patron</entry>
- </row>
- <row>
- <entry>MAX_RENEWALS_REACHED.override</entry>
- <entry>Allows user to renew an item past the maximun renewal
- count</entry>
- </row>
- <row>
- <entry>MERGE_BIB_RECORDS</entry>
- <entry>Allows user to merge bib records and their associated data
- regardless of their bib/volume/copy level perms (in theory - as of
- 1.2.2, users still must have VOLUME_UPDATE and UPDATE_VOLUME in
- order to merge records.</entry>
- </row>
- <row>
- <entry>MR_HOLDS</entry>
- <entry>Allows user to create a metarecord holds</entry>
- </row>
- <row>
- <entry>OFFLINE_EXECUTE</entry>
- <entry>Allows user to process an offline/standalone script
- batch</entry>
- </row>
- <row>
- <entry>OFFLINE_UPLOAD </entry>
- <entry>Allows user to upload an offline/standalone script</entry>
- </row>
- <row>
- <entry>OFFLINE_VIEW</entry>
- <entry>Allows user to view uploaded offline script information</entry>
- </row>
- <row>
- <entry>OPAC_LOGIN</entry>
- <entry>Allows user to login to the OPAC</entry>
- </row>
- <row>
- <entry>patron_exceeds_checkout_count.override</entry>
- <entry>Allow user to override checkout count failure</entry>
- </row>
- <row>
- <entry>patron_exceeds_fines .override</entry>
- <entry>Allow user to override fine amount checkout failure</entry>
- </row>
- <row>
- <entry>patron_exceeds_overdue_count .override</entry>
- <entry>Allow user to override overdue count failure</entry>
- </row>
- <row>
- <entry>REGISTER_WORKSTATION</entry>
- <entry>Allows user to register a new workstation</entry>
- </row>
- <row>
- <entry>REMOTE_Z3950_QUERY</entry>
- <entry>Allows user to perform z3950 queries against remote
- servers</entry>
- </row>
- <row>
- <entry>REMOVE_USER_GROUP_LINK</entry>
- <entry>Allows user to remove other users from permission
- groups</entry>
- </row>
- <row>
- <entry>RENEW_CIRC</entry>
- <entry>Allows user to renew items</entry>
- </row>
- <row>
- <entry>RENEW_HOLD_OVERRIDE</entry>
- <entry>Allows user to continue to renew an item even if it is
- required for a hold.</entry>
- </row>
- <row>
- <entry>REQUEST_HOLDS</entry>
- <entry>Allows user to create holds for another user (if true, we
- still check to make sure they have permission to make the type of
- hold they are requesting, e.g. COPY_HOLDS)</entry>
- </row>
- <row>
- <entry>RUN_REPORTS</entry>
- <entry>Allows user to view the Reports Interface, create templates,
- and run reports</entry>
- </row>
- <row>
- <entry>SET_CIRC_CLAIMS_RETURNED</entry>
- <entry>Allows user to mark an item as claimed returned</entry>
- </row>
- <row>
- <entry>SET_CIRC_LOST</entry>
- <entry>Allows user to mark an item as lost</entry>
- </row>
- <row>
- <entry>SET_CIRC_MISSING</entry>
- <entry>Allows user to mark an item as missing</entry>
- </row>
- <row>
- <entry>SHARE_REPORT_FOLDER</entry>
- <entry>Allows user to share Template/Report/Output folders via the
- Reporting Interface</entry>
- </row>
- <row>
- <entry>STAFF_LOGIN</entry>
- <entry>Allows user to login to the staff client</entry>
- </row>
- <row>
- <entry>TITLE_HOLDS</entry>
- <entry> Allows user to place a hold at the title level</entry>
- </row>
- <row>
- <entry>UNBAR_PATRON</entry>
- <entry> Allows user to un-bar a patron</entry>
- </row>
- <row>
- <entry>UPDATE_BATCH_COPY</entry>
- <entry>Allows user to edit copies in batch</entry>
- </row>
- <row>
- <entry>UPDATE_CONTAINER</entry>
- <entry>Allows user to update another users Buckets or Book
- Bags</entry>
- </row>
- <row>
- <entry>UPDATE_COPY</entry>
- <entry>Allows user to edit a copy</entry>
- </row>
- <row>
- <entry>UPDATE_COPY_LOCATION</entry>
- <entry>Allows user to edit a copy location</entry>
- </row>
- <row>
- <entry>UPDATE_COPY_STAT_CAT</entry>
- <entry>Allows user to change a copy statistical category</entry>
- </row>
- <row>
- <entry>UPDATE_COPY_STAT_CAT_ENTRY</entry>
- <entry>Allows user to change a copy statistical category entry</entry>
- </row>
- <row>
- <entry>UPDATE_HOLD</entry>
- <entry>Allows user to edit holds (such as change notification phone
- number or pickup library, as well as retarget the hold and capture
- an item for hold or pickup)</entry>
- </row>
- <row>
- <entry>UPDATE_MARC</entry>
- <entry>Allows user to edit a marc record</entry>
- </row>
- <row>
- <entry>UPDATE_NON_CAT_TYPE</entry>
- <entry>Allows user to update a non cataloged type</entry>
- </row>
- <row>
- <entry>UPDATE_ORG_SETTING</entry>
- <entry>Allows user to update an org unit setting</entry>
- </row>
- <row>
- <entry>UPDATE_ORG_UNIT</entry>
- <entry>Allows user to change org unit settings</entry>
- </row>
- <row>
- <entry>UPDATE_PATRON_STAT_CAT</entry>
- <entry>Allows user to change a patron statistical category (such as
- renaming the category)</entry>
- </row>
- <row>
- <entry>UPDATE_PATRON_STAT_CAT_ENTRY</entry>
- <entry>Allows user to change a patron stat cat entry(such as
- renaming the entry)</entry>
- </row>
- <row>
- <entry>UPDATE_RECORD</entry>
- <entry>Allows user to undelete a MARC record</entry>
- </row>
- <row>
- <entry>UPDATE_USER</entry>
- <entry>Allows user to edit a user's record</entry>
- </row>
- <row>
- <entry>UPDATE_VOLUME</entry>
- <entry>Allows user to edit volumes - needed for merging records.
- This is a duplicate of VOLUME_UPDATE; user must have both
- permissions at appropriate level to merge records.</entry>
- </row>
- <row>
- <entry>VIEW_CIRCULATIONS</entry>
- <entry>Allows user to see what another user has checked out</entry>
- </row>
- <row>
- <entry>VIEW_CONTAINER</entry>
- <entry>Allows user to view buckets and bookbags</entry>
- </row>
- <row>
- <entry>VIEW_COPY_CHECKOUT_HISTORY</entry>
- <entry>Allows user to view which users have checked out a given
- copy</entry>
- </row>
- <row>
- <entry>VIEW_COPY_NOTES</entry>
- <entry>Allows user to view notes attached to a copy</entry>
- </row>
- <row>
- <entry>VIEW_HOLD</entry>
- <entry>Allows user to view another user's holds</entry>
- </row>
- <row>
- <entry>VIEW_HOLD_NOTIFICATION</entry>
- <entry>Allows user to view notifications attached to a hold</entry>
- </row>
- <row>
- <entry>VIEW_HOLD_PERMIT</entry>
- <entry>Allows user to see if another user has permission to place a
- hold on a given copy</entry>
- </row>
- <row>
- <entry>VIEW_PERM_GROUPS</entry>
- <entry>Allows user to view permission groups.</entry>
- </row>
- <row>
- <entry>VIEW_PERMISSION</entry>
- <entry>Allows user to view user permissions within the user
- permissions editor</entry>
- </row>
- <row>
- <entry>VIEW_PERMIT_CHECKOUT</entry>
- <entry>Allows user to see if another user can check out an item
- (should be true for all staff)</entry>
- </row>
- <row>
- <entry>VIEW_REPORT_OUTPUT</entry>
- <entry>Allows user to view report output</entry>
- </row>
- <row>
- <entry>VIEW_TITLE_NOTES</entry>
- <entry>Allows user to view all notes attached to a title</entry>
- </row>
- <row>
- <entry>VIEW_TRANSACTION</entry>
- <entry>Allows user to see another users grocery/circ transactions
- in the Bills Interface</entry>
- </row>
- <row>
- <entry>VIEW_USER</entry>
- <entry>Allows user to view another user's Patron Record</entry>
- </row>
- <row>
- <entry>VIEW_USER_FINES_SUMMARY</entry>
- <entry>Allows user to view bill details</entry>
- </row>
- <row>
- <entry>VIEW_USER_TRANSACTIONS</entry>
- <entry>*same as VIEW_TRANSACTION (duplicate perm)</entry>
- </row>
- <row>
- <entry>VIEW_VOLUME_NOTES</entry>
- <entry>Allows user to view all notes attached to a volume</entry>
- </row>
- <row>
- <entry>VIEW_ZIP_DATA</entry>
- <entry>Allows user to query the zip code data method</entry>
- </row>
- <row>
- <entry>VOID_BILLING</entry>
- <entry>Allows user to void a bill</entry>
- </row>
- <row>
- <entry>VOLUME_HOLDS</entry>
- <entry> Allows user to place a volume level hold</entry>
- </row>
-
- <row>
- <entry>actor.org_unit.closed_date.create</entry>
- <entry>Allows user to create a new closed date for a location</entry>
- </row>
- <row>
- <entry>actor.org_unit.closed_date.delete</entry>
- <entry>Allows user to remove a closed date interval for a given
- location</entry>
- </row>
- <row>
- <entry>actor.org_unit.closed_date.update</entry>
- <entry>Allows user to update a closed date interval for a given
- location</entry>
- </row>
- <row>
- <entry>group_application.user</entry>
- <entry>Allows user to add/remove users to/from the User group</entry>
- </row>
- <row>
- <entry>group_application.user.patron</entry>
- <entry>Allows user to add/remove users to/from the Patron
- group</entry>
- </row>
- <row>
- <entry>group_application.user.sip_client</entry>
- <entry>Allows user to add/remove users to/from the SIP-Client
- group</entry>
- </row>
- <row>
- <entry>group_application.user.staff</entry>
- <entry>Allows user to add/remove users to/from the Staff
- group</entry>
- </row>
- <row>
- <entry>group_application.user.staff.admin.global_admin</entry>
- <entry>Allows user to add/remove users to/from the GlobalAdmin
- group</entry>
- </row>
- <row>
- <entry>group_application.user.staff.admin.lib_manager</entry>
- <entry>Allows user to add/remove users to/from the LibraryManager
- group</entry>
- </row>
- <row>
- <entry>group_application.user.staff.admin.local_admin</entry>
- <entry>Allows user to add/remove users to/from the LocalAdmin
- group</entry>
- </row>
- <row>
- <entry>group_application.user.staff.cat</entry>
- <entry>Allows user to add/remove users to/from the Cataloger group</entry>
- </row>
- <row>
- <entry>group_application.user.staff.cat.cat1</entry>
- <entry>Allows user to add/remove users to/from the Cat1 group</entry>
- </row>
- <row>
- <entry>group_application.user.staff.circ</entry>
- <entry>Allows user to add/remove users to/from the Circulator
- group</entry>
- </row>
- <row>
- <entry>group_application.user.staff.supercat</entry>
- <entry>Allows user to add/remove users to/from the Supercat
- group</entry>
- </row>
- <row>
- <entry>group_application.user.vendor</entry>
- <entry>Allows user to add/remove users to/from the Vendor
- group</entry>
- </row>
- <row>
- <entry>money.collections_tracker.create</entry>
- <entry>Allows user to put someone into collections</entry>
- </row>
- <row>
- <entry>money.collections_tracker.delete</entry>
- <entry>Allows user to take someone out of collections</entry>
- </row>
- </tbody>
- </tgroup>
- </table>
- </section>
- </section>
- <section xml:id="copystatus">
- <title>Copy Status</title>
- <para>To navigate to the copy status editor from the staff client menu, select
- <menuchoice><guimenu>Admin</guimenu> <guisubmenu>Server Administration</guisubmenu>
- <guisubmenu>Copy Statuses </guisubmenu></menuchoice></para>
- <para>The Copy Status Editor is used to Add, edit and delete statuses of copies in your system.</para>
- <para>Evergreen comes pre-loaded with a number of copy statuses.</para>
- <table xml:id="copystatusestable">
- <title>Copy Status Table</title>
- <tgroup cols="4">
- <thead>
- <row>
- <entry>ID</entry>
- <entry>Name</entry>
- <entry>Holdable - default setting</entry>
- <entry>OPAC Visible - default setting</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>0</entry>
- <entry>Available</entry>
- <entry>true</entry>
- <entry>true</entry>
- </row>
- <row>
- <entry>1</entry>
- <entry>Checked out</entry>
- <entry>true</entry>
- <entry>true</entry>
- </row>
- <row>
- <entry>2</entry>
- <entry>Bindery</entry>
- <entry>false</entry>
- <entry>false</entry>
- </row>
- <row>
- <entry>3</entry>
- <entry>Lost</entry>
- <entry>false</entry>
- <entry>false</entry>
- </row>
- <row>
- <entry>4</entry>
- <entry>Missing</entry>
- <entry>false</entry>
- <entry>false</entry>
- </row>
- <row>
- <entry>5</entry>
- <entry>In process</entry>
- <entry>false</entry>
- <entry>true</entry>
- </row>
- <row>
- <entry>6</entry>
- <entry>In transit</entry>
- <entry>true</entry>
- <entry>true</entry>
- </row>
- <row>
- <entry>7</entry>
- <entry>Reshelving</entry>
- <entry>true</entry>
- <entry>true</entry>
- </row>
- <row>
- <entry>8</entry>
- <entry>On holds shelf</entry>
- <entry>true</entry>
- <entry>true</entry>
- </row>
- <row>
- <entry>9</entry>
- <entry>On order</entry>
- <entry>true</entry>
- <entry>true</entry>
- </row>
- <row>
- <entry>10</entry>
- <entry>ILL</entry>
- <entry>true</entry>
- <entry>false</entry>
- </row>
- <row>
- <entry>11</entry>
- <entry>Cataloging</entry>
- <entry>true</entry>
- <entry>false</entry>
- </row>
- <row>
- <entry>12</entry>
- <entry>Reserves</entry>
- <entry>false</entry>
- <entry>true</entry>
- </row>
- <row>
- <entry>13</entry>
- <entry>Discard/Weed</entry>
- <entry>false</entry>
- <entry>false</entry>
- </row>
- <row>
- <entry>14</entry>
- <entry>Damaged</entry>
- <entry>false</entry>
- <entry>false</entry>
- </row>
- <row>
- <entry>15</entry>
- <entry>On reservation shelf</entry>
- <entry>true</entry>
- <entry>false</entry>
- </row>
- </tbody>
- </tgroup>
- </table>
- <para>It is possible to add, delete and edit copy statuses.</para>
- <procedure>
- <title>Adding Copy Statuses</title>
- <step><para>In the <guilabel>New Status</guilabel> field, enter the name of the
- new status you wish to add.</para></step>
- <step><para>Click <guibutton>Add</guibutton>.</para></step>
- <step><para>Locate you new status and check the <emphasis>Holdable</emphasis> check box
- if you wish to all users to place holds on items in this status. Check
- <emphasis>OPAC Visble</emphasis> if you wish for this status to appear in the public
- OPAC.</para></step>
- <step><para>Click <guibutton>Save Changes</guibutton> at the bottum of the screen to
- save changes to the new status.</para></step>
- </procedure>
- <procedure>
- <title>Deleting Copy Statuses</title>
- <step><para>Highlight the statuses you wish to delete. Hold the
- <keycap>Shift</keycap> to select more than one status.</para></step>
- <step><para>Click <guibutton>Delete Selected</guibutton>.</para></step>
- <step><para>Click OK to verify.</para>
- <note><para>You will not be able to delete statuses if copies currently
- exist with that status.</para></note>
- </step>
- </procedure>
- <procedure>
- <title>Editing Copy Statuses</title>
- <step><para>Double click on a status name to change its name and enter the new
- name.</para> <para>To change whether a status is visible in the OPAC, check or uncheck
- the <emphasis>OPAC Visible</emphasis> check box.</para><para>To allow patrons the ability to
- hold items in that status, check the <emphasis>Holdable</emphasis> check box. To prevent
- users from holding items in that status, uncheck the <emphasis>Holdable</emphasis>
- check box. </para></step>
- <step><para>Once you have finished editing the statuses, remember to click
- <guibutton>Save Changes</guibutton>.</para></step>
- </procedure>
- </section>
- <section xml:id="billingtypes">
- <title>Billing Types</title>
- <para>The billing types editor is used for creating, editing and deleting billing types.</para>
- <para>To navigate to the billing types editor from the staff client menu, select
- <menuchoice><guimenu>Admin</guimenu> <guisubmenu>Server Administration</guisubmenu>
- <guisubmenu>Billing Types</guisubmenu></menuchoice></para>
- <procedure>
- <title>Adding Billing Types</title>
- <step><para>Click <guibutton>New Billing Type</guibutton>.</para></step>
- <step><para>Enter the name of the billing type.</para></step>
- <step><para>Select the <emphasis>Org Unit</emphasis> to use this billing type.</para></step>
- <step><para>Enter the <emphasis>Default Price</emphasis>. This is only the default since
- the actual price of a specific billing can be adjusted when staff create
- a billing</para></step>
- <step><para>Click <guibutton>Save</guibutton> to save the new billing type.</para></step>
- </procedure>
- <procedure>
- <title>Deleting Billing Types</title>
- <step><para>Check the checkbox of the billing type(s) you wish to delete.</para></step>
- <step><para>Click <guibutton>Delete Selected</guibutton>.
- <warning><para>The selected billing types will be deleted without a
- verification alert.</para></warning>
- </para></step>
- </procedure>
- <procedure>
- <title>Editing Billing Types</title>
- <step><para>Double click on a billing types to open the editing window.</para></step>
- <step><para>Make desired changes to the <emphasis>name</emphasis>,
- <emphasis>Org Unit</emphasis> and <emphasis>Default Price</emphasis>.</para></step>
- <step><para>Once you have finished editing, click
- <guibutton>Save</guibutton>.</para></step>
- </procedure>
-
- </section>
- <section xml:id="circmodifiers">
- <title>Circulation Modifiers</title>
- <para>The circulation modifier editor is used to create, edit and delete modifier categories to control
- circulation policies on specific groups of items.</para>
- <para>To navigate to the circulation modifiers editor from the staff client menu, select
- <menuchoice>
- <guimenu>Admin</guimenu> <guisubmenu>Server Administration</guisubmenu>
- <guisubmenu>Circulation Modifiers</guisubmenu></menuchoice>.
- </para>
- <procedure>
- <title>Adding Circulation Modifiers</title>
- <step><para>Click <guibutton>New Circ Modifier</guibutton>.</para></step>
- <step><para>Enter a <emphasis>Code</emphasis>, <emphasis>Name</emphasis> and
- <emphasis>Description</emphasis>.</para></step>
- <step><para>Select the <emphasis>SIP 2 Media Type</emphasis>.</para></step>
- <step><para>Check the <guibutton>Magnetic Media</guibutton> check box if the item is magnetic media such as a casette
- tape.</para></step>
- <step><para>Click <guibutton>Save</guibutton> to save the new circulation
- modifier.</para></step>
- </procedure>
- <procedure>
- <title>Deleting Circulation Modifiers</title>
- <step><para>Check the check box(es) next to the circulation modifiers(s) you wish to
- delete.</para></step>
- <step><para>Click <guibutton>Delete Selected</guibutton> near the top of the page.
- <warning><para>The selected circulation modifiers will be deleted without a
- verification alert.</para></warning>
- </para></step>
- </procedure>
- <procedure>
- <title>Editing Circulation Modifiers</title>
- <step><para>Double click on the row of the cirlation modifier you wish to
- edit.</para></step>
- <step><para>Make desired changes.</para></step>
- <step><para>Once you have finished editing, click
- <guibutton>Save</guibutton>.</para></step>
- </procedure>
- </section>
- <section xml:id="catalogingtemplates">
- <title>Cataloging Templates</title>
- <para>Cataloging templates are essential for making the cataloguing process more efficient. Templates are used that that the basic structure of specific types of cataloguing records can loaded when the cataloguer adds a new record</para>
- <procedure>
- <title>Adding Cataloging Templates</title>
- <step>
- <para>
- Create a marc template in the directory <filename class="directory">/openils/var/templates/marc/</filename>. It should be in xml format.
- Here is an example file <filename>k_video.xml</filename>:
- </para>
- <para>
- <mediaobject xml:id="cattemplate">
- <alt>Catalog Template Example</alt>
- <imageobject>
- <imagedata scalefit="0" fileref="../media/k_book_record.png"/>
- </imageobject>
- </mediaobject>
- </para>
-
- </step>
- <step>
- <para>Add the template to the to the <emphasis>marctemplates</emphasis> list in the open-ils.cat section of the evergreen configuration file <filename>opensrf.xml</filename> </para>
- </step>
- <step>
- <para>Restart perl services for changes to take effect.</para>
- <screen>/openils/bin/osrf_ctl.sh -l -a restart_perl</screen>
- </step>
- </procedure>
- </section>
-</chapter>
+<?xml version='1.0' encoding='UTF-8'?>\r
+<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"\r
+xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="serveradministration">\r
+ <info>\r
+ <title>Server Administration</title>\r
+ <abstract>\r
+ <para>Administration of Evergreen involves configuration done from both the Staff Client as well a \r
+ the command line. The goal of this chapter is to provide you with the procedures to help \r
+ you optimize your Evergreen system.</para>\r
+ </abstract>\r
+ </info>\r
+ <section xml:id="orgunitsandtypes">\r
+ <title>Organizational Unit Types and Organizational Units</title>\r
+ <section xml:id="orgtypes">\r
+ <title>Organizational Unit Types</title>\r
+ <para>Organizational Unit Types are the terms used to refer to levels in the hierarchy of your \r
+ library system(s). Examples could include>All-Encompassing Consortium, Consortium Within a \r
+ Consortium, Library System, Branch, Bookmobile, Sub-Branch, Twig, etc.</para>\r
+ <para>You can add or remove organizational unit types, and rename them as needed to match the \r
+ organizational hierarchy that exists in reality for the libraries using your installation of \r
+ Evergreen. Evergreen can support organizations as simple as a single library with one or more \r
+ branches or as complex as a consortium composed of many independently governed library \r
+ systems. Organizational unit types should never have proper names since they are only generic types .</para>\r
+ <para>The fields in the organizational unit type record include:</para>\r
+ <itemizedlist>\r
+ <listitem>Type Name - The name of the organization unit type.</listitem>\r
+ <listitem>Opac Label - This is the label displayed in the OPAC to describe the search \r
+ range and the copy count columns for results. They are <emphasis>range \r
+ relative</emphasis> labels.</listitem>\r
+ \r
+ <listitem>Parent Type - The parent organizational unit type of this type.</listitem>\r
+ <listitem>Can Have Volumes - Flag that allows an organizational unit of this type to contain \r
+ Volumes/Call Numbers and thus Copies.</listitem>\r
+ <listitem>Can Have Users - Flag that allows an Organizational unit of this type to be home to \r
+ Users.</listitem>\r
+ </itemizedlist>\r
+ <para>An organizational unit type can be added, edited, or removed using the staff client.</para>\r
+ <para>To navigate to the <emphasis>Organization Unit Types</emphasis> from the staff client select \r
+ <menuchoice>\r
+ <guimenu>Admin</guimenu> \r
+ <guisubmenu>Server Administration</guisubmenu>\r
+ <guisubmenu>Organization Types</guisubmenu>\r
+ </menuchoice>\r
+ </para>\r
+ <procedure>\r
+ <title>Adding Organization Types</title>\r
+ <step><para>Select an organization type from the organization type tree on the left and \r
+ click <guibutton>New Child</guibutton>.</para></step>\r
+ <step><para>Make sure your new type is selected and edit the <guilabel>Type Name</guilabel>, \r
+ <guilabel>OPAC Label</guilabel> and <guilabel>Parent Type</guilabel>.</para></step>\r
+ <step><para>Change the <guilabel>Parent Type</guilabel> if necessary.</para></step>\r
+ <step><para>Check the <guilabel>Can Have Volumes and Copies</guilabel> checkbox if the \r
+ organization units of this type will have volumes and copies assigned to it.</para></step>\r
+ <step><para>Check the <guilabel>Can Have Users</guilabel> checkbox if you will allow users \r
+ to be have the organization units of this type as their home unit.</para></step>\r
+ <step><para>Click <guibutton>Save</guibutton> to save your new organization type.\r
+ </para></step> \r
+ </procedure>\r
+ <procedure>\r
+ <title>Deleting Organization Types</title>\r
+ <step><para>Select the <emphasis>organization type</emphasis> from the <emphasis>Organization Type</emphasis> \r
+ tree.</para></step>\r
+ <step><para>Click <guibutton>Delete</guibutton>.</para></step>\r
+ <step><para>Click <guibutton>OK</guibutton> on the warning alert box.</para></step>\r
+ <note>\r
+ <para>You will not be able to delete organization types if organization units are \r
+ assigned to that type. Before you can delete the organization \r
+ Type, you must change the organization type of the units associated with the type \r
+ or delete the units.</para>\r
+ </note>\r
+ </procedure>\r
+ <procedure>\r
+ <title>Editing Organization Types</title>\r
+ <step><para>Select the <emphasis>organization type</emphasis> you wish to edit from the \r
+ organization type tree.</para></step>\r
+ <step><para>Make the changes in the right pane.</para></step>\r
+ <step><para>Click <guibutton>Save</guibutton> to save your changes.</para></step>\r
+ </procedure>\r
+ </section>\r
+ \r
+ <section xml:id="orgunits">\r
+ <title>Organizational Units</title>\r
+ <abstract>\r
+ <para>Organizational Units are the specific instances of the organization unit types that \r
+ make up your library's hierarchy. These can include consortia, systems, branches, \r
+ etc. The organizational units should have distictive proper names such as \r
+ <emphasis>Main Street Branch</emphasis> or <emphasis>Townsville Campus</emphasis>.</para>\r
+ </abstract>\r
+ <para>To navigate to the organizational units adminstration page in the staff client select \r
+ <menuchoice>\r
+ <guimenu>Admin</guimenu> \r
+ <guisubmenu>Server Administration</guisubmenu>\r
+ <guisubmenu>Organizational Units</guisubmenu>\r
+ </menuchoice>\r
+ </para>\r
+ <procedure>\r
+ <title>Adding Organizational Units</title>\r
+ <step><para>Select an <emphasis>Organizational Unit</emphasis> from the organizational unit tree on the left and click \r
+ <guibutton>New Child</guibutton>.</para></step>\r
+ <step><para>Make sure your new unit is selected and edit the <guilabel>Organizational Unit \r
+ Name</guilabel>, <guilabel>Organizational Unit Policy Code</guilabel>, \r
+ <guilabel>Main Email Address</guilabel> and <guilabel>Main Phone Number</guilabel>.</para>\r
+ <note>\r
+ <para>The <emphasis>Organizational Unit Name</emphasis> is the name that will appear in the \r
+ OPAC. The <emphasis>Policy Code</emphasis> is used by the system to associate policies and \r
+ copies with the unit.</para>\r
+ </note>\r
+ </step>\r
+ <step><para>Select the <guilabel>Organization Unit Type</guilabel> and \r
+ <guilabel>Parent Organization Unit</guilabel>.</para></step>\r
+ <step><para>Check the <guilabel>Can Have Volumes and Copies</guilabel> checkbox if the \r
+ organization units of this type will have volumes and copies assigned to it.</para></step>\r
+ <step><para>Check the <guilabel>OPAC Visible</guilabel> checkbox if you want this location to be \r
+ visible in the OPAC for searching.</para></step>\r
+ <step><para>Click <guibutton>Save</guibutton> to save your new organizational unit.</para></step> \r
+ </procedure>\r
+ <procedure>\r
+ <title>Deleting Organizational Units</title>\r
+ <step><para>Select the <emphasis>organizational unit</emphasis> you wish to delete from the organzational unit tree in the left pane.</para></step>\r
+ <step><para>Click<guibutton>Delete</guibutton>.</para></step>\r
+ <step><para>Click <guibutton>OK</guibutton> on the warning alert box.</para></step>\r
+ <note>\r
+ <para>You will not be able to delete organizational units if you have \r
+ users, workstations or copies assigned to the unit. Before you can delete the \r
+ organizational unit, you must move its users, workstations, copies and other associated resources to other \r
+ organizational units units.</para>\r
+ </note>\r
+ </procedure>\r
+ <procedure>\r
+ <title>Editing Organizational Units</title>\r
+ <step><para>Select the organizational unit you wish to edit from the \r
+ organizational unit tree in the left pane.</para></step>\r
+ <step><para>Edit the fields in the right pane.</para></step>\r
+ <step><para>Click <guibutton>Save</guibutton> to save your changes.</para></step>\r
+ </procedure>\r
+ \r
+ </section>\r
+ <section xml:id="server-hours">\r
+ <info>\r
+ <title>Library Hours of Operation</title>\r
+ </info>\r
+\r
+ <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
+ holiday and other closures are recorded in the <link linkend="lsa-closed">Closed Dates\r
+ Editor</link>.</para>\r
+\r
+ <para>Hours of operation and closed dates affect due dates and overdue fines.</para>\r
+\r
+ <itemizedlist>\r
+ <listitem>\r
+ <formalpara>\r
+ <title>Due dates</title>\r
+ <para>Due dates that would fall on closed days are automatically pushed forward to\r
+ the next open day. Likewise, if an item is checked out at 8pm, for example, and\r
+ would normally be due on a day when the library closes before 8pm, Evergreen\r
+ pushes the due date forward to the next open day.</para>\r
+ </formalpara>\r
+ </listitem>\r
+ <listitem>\r
+ <formalpara>\r
+ <title>Overdue fines</title>\r
+ <para>Overdue fines are not charged on days when the library is closed.</para>\r
+ </formalpara>\r
+ </listitem>\r
+ </itemizedlist>\r
+\r
+ <para>To review or edit your library's hours of operation,</para>\r
+\r
+\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
+ </step>\r
+ <step>\r
+ <informalfigure>\r
+ <para>Click the <guilabel>Hours of\r
+ Operation</guilabel> tab.</para>\r
+ <para>\r
+ <mediaobject>\r
+ <alt>organizational units, main settings</alt>\r
+ <imageobject>\r
+ <imagedata scalefit="0" fileref="../media/server-4.png"/>\r
+ </imageobject>\r
+ </mediaobject>\r
+ </para>\r
+ </informalfigure>\r
+ </step>\r
+\r
+ <step>\r
+ <informalfigure>\r
+ <para>Review your library's weekly hours, editing as necessary. To set a closed day\r
+ click the corresponding <guibutton>Closed</guibutton> button. Closed days (Monday\r
+ and Sunday in the example below) have open and close times of 12:00\r
+ AM.</para>\r
+ <para>\r
+ <mediaobject>\r
+ <alt>hours of operation interface</alt>\r
+ <imageobject>\r
+ <imagedata scalefit="0" fileref="../media/server-5.png"/>\r
+ </imageobject>\r
+ </mediaobject>\r
+ </para>\r
+ </informalfigure>\r
+ </step>\r
+\r
+ <step>\r
+ <para>Click <guibutton>Save</guibutton> to record any changes</para>\r
+ </step>\r
+\r
+\r
+ </procedure>\r
+\r
+ </section>\r
+\r
+\r
+ <section xml:id="server-addresses">\r
+ <info>\r
+ <title>Library Addresses</title>\r
+ </info>\r
+\r
+ <para>Addresses set in <menuchoice>\r
+ <guimenu>Admin (-)</guimenu>\r
+ <guisubmenu>Server Administrations</guisubmenu>\r
+ <guimenuitem>Organizational Units</guimenuitem>\r
+ </menuchoice> appear in patron email notifications, hold slips, and transit slips. Local\r
+ System Adminstrators should ensure that the <guilabel>Physical</guilabel>,\r
+ <guilabel>Holds</guilabel>, and <guilabel>Mailing</guilabel> addresses are set\r
+ correctly.</para>\r
+\r
+ <procedure>\r
+\r
+ <step>\r
+ <para>Open the <guilabel>Organizational Units</guilabel> interface as described in the <link\r
+ linkend="server-main">previous section</link>.</para>\r
+ </step>\r
+ <step>\r
+ <informalfigure>\r
+ <para>Click the\r
+ <guilabel>Addresses</guilabel> tab.</para>\r
+ <para>\r
+ <mediaobject>\r
+ <alt>organizational units, main settings</alt>\r
+ <imageobject>\r
+ <imagedata scalefit="0" fileref="../media/server-6.png"/>\r
+ </imageobject>\r
+ </mediaobject>\r
+ </para>\r
+ </informalfigure>\r
+ </step>\r
+\r
+ <step>\r
+ \r
+ <para>There are four address tabs: <guilabel>Physical</guilabel>,\r
+ <guilabel>Holds</guilabel>, <guilabel>Mailing</guilabel>, and\r
+ <guilabel>ILL</guilabel>. Sitka Support recommends setting the first three at a\r
+ minimum. The <guilabel>Holds Address</guilabel> appears on transit slips when items are sent to fulfill holds at another branch.</para>\r
+ \r
+ \r
+ </step>\r
+\r
+ <step>\r
+ <para>Click <guibutton>Save</guibutton> to record changes for each tab.</para>\r
+ </step>\r
+\r
+ </procedure>\r
+\r
+ <note>\r
+ <para>The <guilabel>Valid</guilabel> checkbox is an optional setting that does not affect\r
+ current Evergreen functions, but the Sitka Support team recommends checking it for all\r
+ correct addresses.</para>\r
+ </note>\r
+\r
+ </section>\r
+\r
+ </section>\r
+ <section xml:id="relevancyrankings">\r
+ <title>Adjusting Search Relevancy Rankings</title>\r
+ <info>\r
+ <abstract>\r
+ <para>This section describes indexed field weighting and matchpoint weighting, which\r
+ control relevance ranking in Evergreen catalog search results. Adjusting relavancy can only be completed through access to the Evergreen database as of version 1.6.</para>\r
+ <tip>\r
+ <para>In tuning search relevance, it is good practice to make incremental\r
+ adjustments, capture search logs, and assess results before making further\r
+ adjustments. </para>\r
+ </tip>\r
+ </abstract>\r
+ </info>\r
+ <section>\r
+ <title>Indexed-field Weighting</title>\r
+ <para>Indexed-field weighting is configured in the Evergreen database in the weight column\r
+ of the config.metabib_field 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 config.metabib_field table:</para>\r
+ <para> author | conference | //mods32:mods/mods32:name[@type='conference']/mods32:namePart[../mods32:role/mods32:roleTerm[text()='creator']] | mods32 | 1 ) </para>\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
+ indexed field. The weight value may be increased or decreased by whole integers. </para>\r
+ <para>For example, by increasing the weight of the title-proper field from 1 to 2, a search\r
+ for <emphasis role="bold">jaguar</emphasis> would double the relevance for the book titled\r
+ <emphasis role="italic">Aimee and Jaguar</emphasis> than for a record with the term\r
+ <emphasis role="bold">jaguar</emphasis> in another indexed field. </para>\r
+ </section>\r
+ <section>\r
+ <title>Matchpoint Weighting</title>\r
+ <para> Matchpoint weighting provides another way to fine-tune Evergreen relevance ranking,\r
+ and is configured through floating-point multipliers in the multiplier column of the\r
+ search.relevance_adjustment table.</para>\r
+ <para> Weighting can be adjusted for one, more, or all multiplier fields in\r
+ search.relevance_adjustment.</para>\r
+ <para>You can adjust the following three matchpoints:</para> \r
+ <itemizedlist>\r
+ <listitem>\r
+ <para><indexterm><primary>first_word</primary></indexterm> boosts relevance if the query is \r
+ one term long and matches the first term in the indexed field (search for <emphasis \r
+ role="bold">twain</emphasis>, get a bonus for <emphasis role="bold">twain, mark</emphasis> \r
+ but not <emphasis role="bold">mark twain</emphasis>)</para>\r
+ </listitem>\r
+ <listitem>\r
+ <para><indexterm><primary>word_order</primary></indexterm> increases relevance for words \r
+ matching the order of search terms, so that the results for the search <emphasis \r
+ role="bold">legend suicide</emphasis> would match higher for the book <emphasis \r
+ role="italic">Legend of a Suicide</emphasis> than for the book, \r
+ <emphasis role="italic">Suicide Legend</emphasis></para>\r
+ </listitem>\r
+ <listitem>\r
+ <para><indexterm><primary>full_match</primary></indexterm> boosts relevance when the full \r
+ query exactly matches the entire indexed field (after space, case, and diacritics are \r
+ normalized). So a title search for <emphasis role="italic">The Future of Ice</emphasis> \r
+ would get a relevance boost above <emphasis role="italic">Ice>Ages of the \r
+ Future</emphasis>.</para>\r
+ </listitem>\r
+ </itemizedlist>\r
+ <para> Here are the default settings of the search.relevance_adjustment table: </para>\r
+ <table xml:id="search.relevance">\r
+ <title>search.relevance_adjustment table</title>\r
+ <tgroup cols="4">\r
+ <thead>\r
+ <row>\r
+ <entry>field_class</entry>\r
+ <entry>name</entry>\r
+ <entry>bump_type</entry>\r
+ <entry>multiplier</entry>\r
+ </row>\r
+ </thead>\r
+ <tbody>\r
+ <row>\r
+ <entry>author</entry>\r
+ <entry>conference</entry>\r
+ <entry>first_word</entry>\r
+ <entry>1.5</entry>\r
+ </row>\r
+ <row>\r
+ <entry>author</entry>\r
+ <entry>corporate</entry>\r
+ <entry>first_word</entry>\r
+ <entry>1.5</entry>\r
+ </row>\r
+ <row>\r
+ <entry>author </entry>\r
+ <entry>other </entry>\r
+ <entry>first_word</entry>\r
+ <entry>1.5</entry>\r
+ </row>\r
+ <row>\r
+ <entry>author</entry>\r
+ <entry>personal</entry>\r
+ <entry>first_word</entry>\r
+ <entry>1.5</entry>\r
+ </row>\r
+ <row>\r
+ <entry>keyword</entry>\r
+ <entry>keyword</entry>\r
+ <entry>word_order</entry>\r
+ <entry>10</entry>\r
+ </row>\r
+ <row>\r
+ <entry>series</entry>\r
+ <entry>seriestitle</entry>\r
+ <entry>first_word</entry>\r
+ <entry>1.5</entry>\r
+ </row>\r
+ <row>\r
+ <entry>series</entry>\r
+ <entry>seriestitle</entry>\r
+ <entry>full_match</entry>\r
+ <entry>20</entry>\r
+ </row>\r
+ <row>\r
+ <entry>title</entry>\r
+ <entry>abbreviated</entry>\r
+ <entry>first_word</entry>\r
+ <entry>1.5</entry>\r
+ </row>\r
+ <row>\r
+ <entry>title</entry>\r
+ <entry>abbreviated</entry>\r
+ <entry>full_match</entry>\r
+ <entry>20</entry>\r
+ </row>\r
+ <row>\r
+ <entry>title</entry>\r
+ <entry>abbreviated</entry>\r
+ <entry>word_order</entry>\r
+ <entry>10</entry>\r
+ </row>\r
+ <row>\r
+ <entry>title</entry>\r
+ <entry>alternative</entry>\r
+ <entry>first_word</entry>\r
+ <entry>1.5</entry>\r
+ </row>\r
+ <row>\r
+ <entry>title</entry>\r
+ <entry>alternative</entry>\r
+ <entry>full_match</entry>\r
+ <entry>20</entry>\r
+ </row>\r
+ <row>\r
+ <entry>title</entry>\r
+ <entry>alternative</entry>\r
+ <entry>word_order</entry>\r
+ <entry>10</entry>\r
+ </row>\r
+ <row>\r
+ <entry>title</entry>\r
+ <entry>proper</entry>\r
+ <entry>first_word</entry>\r
+ <entry>1.5</entry>\r
+ </row>\r
+ <row>\r
+ <entry>title</entry>\r
+ <entry>proper</entry>\r
+ <entry>full_match</entry>\r
+ <entry>20</entry>\r
+ </row>\r
+ <row>\r
+ <entry>title</entry>\r
+ <entry>proper</entry>\r
+ <entry>word_order</entry>\r
+ <entry>10</entry>\r
+ </row>\r
+ <row>\r
+ <entry>title</entry>\r
+ <entry>translated</entry>\r
+ <entry>first_word</entry>\r
+ <entry>1.5</entry>\r
+ </row>\r
+ <row>\r
+ <entry>title</entry>\r
+ <entry>translated</entry>\r
+ <entry>full_match</entry>\r
+ <entry>20</entry>\r
+ </row>\r
+ <row>\r
+ <entry>title</entry>\r
+ <entry>translated</entry>\r
+ <entry>word_order</entry>\r
+ <entry>10</entry>\r
+ </row>\r
+ <row>\r
+ <entry>title</entry>\r
+ <entry>uniform</entry>\r
+ <entry>first_word</entry>\r
+ <entry>1.5</entry>\r
+ </row>\r
+ <row>\r
+ <entry>title</entry>\r
+ <entry>uniform</entry>\r
+ <entry>full_match</entry>\r
+ <entry>20</entry>\r
+ </row>\r
+ <row>\r
+ <entry>title</entry>\r
+ <entry>uniform</entry>\r
+ <entry>word_order</entry>\r
+ <entry>10</entry>\r
+ </row>\r
+ </tbody>\r
+ </tgroup>\r
+ </table>\r
+ </section>\r
+ <section>\r
+ <title>Combining Index Weighting and Matchpoint Weighting</title>\r
+ <para>Index weighting and matchpoint weighting may be combined. The relevance boost of the combined \r
+ weighting is equal to the product of the two multiplied values. </para>\r
+ <para>If the relevance setting in the config.metabib_field were increased to 2, and the multiplier \r
+ set to 1.2 in the search.relevance_adjustment table, the resulting matchpoint increase would be \r
+ 240%. </para>\r
+ <note>\r
+ <para>In practice, these weights are applied serially -- first the index weight, then all \r
+ the matchpoint weights that apply -- because they are evaluated at different stages of the \r
+ search process.</para>\r
+ </note>\r
+ </section>\r
+ <section>\r
+ <title>Adjusting Relevancy for Keyword Searches</title>\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
+ 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 \r
+ other fields. </para>\r
+ <procedure>\r
+ <step>\r
+ <para>From the command line, access the PorstgreSQL command line interface</para>\r
+ <screen>psql -U evergreen</screen>\r
+ </step> \r
+ <step>\r
+ <para>Clone the title|proper index to create a keyword|title index</para>\r
+ <para>6 = the title|proper index</para>\r
+ <screen>INSERT INTO config.metabib_field \r
+ (field_class, name, xpath, weight,</screen>\r
+ <screen>format, search_field, facet_field)</screen>\r
+ <screen>SELECT 'keyword', 'title', xpath, weight, format,</screen> \r
+ <screen>search_field, facet_field</screen>\r
+ <screen>FROM config.metabib_field</screen>\r
+ <screen>WHERE id = 6;</screen>\r
+ </step>\r
+ <step>\r
+ <para>Populate the keyword|title index with a set of index entries cloned from the metabib.title_field_entry table;</para>\r
+ <para>6 = the title|proper index</para>\r
+ <screen>INSERT INTO metabib.keyword_field_entry (source, field, value)</screen>\r
+ <screen>SELECT source, 17, value (the field value, 17, field be different \r
+ in your database so you may need to check the \r
+ <emphasis>config.metabib_field</emphasis> for the id of your new index).</screen>\r
+ <screen>FROM metabib.title_field_entry</screen>\r
+ <screen>WHERE field = 6;</screen>\r
+ </step>\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 <emphasis>config.metabib_field</emphasis> for the id \r
+ of your new index).</para>\r
+ <screen>INSERT INTO search.relevance_adjustment \r
+ (active, field, bump_type, multiplier)</screen>\r
+ <screen>VALUES (true, 17, 'first_word', 5); </screen>\r
+ </step>\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 <emphasis>config.metabib_field</emphasis> for the id \r
+ of your new index).</para>\r
+ <screen>UPDATE config.metabib_field</screen>\r
+ <screen>SET weight = 10</screen>\r
+ <screen>WHERE id = 17;</screen>\r
+ </step>\r
+ </procedure> \r
+ </section> \r
+ </section>\r
+ <section xml:id="grouppermissions">\r
+ <title>User and Group Permissions</title>\r
+ <abstract>\r
+ <para>It is essential to understand how user and group permissions can be used to allow staff \r
+ to fulfil their roles while ensuring that they only have access to the appropriate level.</para> \r
+ <para>Permissions in <application>Evergreen</application> are applied to a specific location and system depth based on the home \r
+ library of the user. The user will only have that permission within the scope provided by the \r
+ <emphasis>Depth</emphasis> field in relation to his/her working locations.</para> \r
+ <para>Evergreen provides group application permissions in order to restrict which staff members \r
+ have the ability to assign elevated permissions to a user, and which staff members have the ability \r
+ to edit users in particular groups.</para>\r
+ </abstract>\r
+ <section>\r
+ <title>User Permissions</title>\r
+ <tip><para>Ihe User permissions editor allows an administrator to set up permission fopr an individual user. However, In most cases, permissions can be controlled more \r
+ efficiently at the group level with individuals being assigned to specific groups based on their roles in the library.</para></tip> \r
+ <para>To open the user permission editor, select <menuchoice><guimenu>Admin</guimenu> \r
+ <guisubmenu>User Permission Editor</guisubmenu></menuchoice>. Type the user's barcode when prompted.</para> \r
+ <section>\r
+ <title>Working Locations</title>\r
+ <para>The first section of the User Permission Editor is the the Working Locations \r
+ section. You may select more than one working location for a user. This will effect \r
+ the availability of certain permissions which are dependent on the user having the working location.</para> \r
+ </section>\r
+ <section>\r
+ <title>User Permission Settings</title>\r
+ <para>Below the working locations is the long list of all the permissions available on your \r
+ system. For each permission you can apply it by checking the \r
+ <emphasis>Applied</emphasis> check box. You can also select a depth to which the \r
+ permission is applied and also make the permission <emphasis>grantable</emphasis>, allowing \r
+ the user the ability to grant the permission to others.</para>\r
+ </section> \r
+ </section>\r
+ <section>\r
+ <title>Group Permissions</title>\r
+ <para>Most permissions should be assigned at the group level. Here you can create new \r
+ groups based on the roles and responsibilities of the users in your system. Staff will be able to \r
+ assign users to these groups when they register patrons.</para> \r
+ <tip><para>It is a good idea to create your groups soon after creating your organizational units.\r
+ It is also imprtaant to give careful consideration to the hierarchy of your groups to make \r
+ permission assignment as efficient as possible.</para></tip> \r
+ <para>To enter the <emphasis>Group Permission</emphasis> module from the staff client menu, select \r
+ <menuchoice><guimenu>Admin</guimenu> <guisubmenu>Server Administration</guisubmenu> \r
+ <guisubmenu>Permission Groups</guisubmenu></menuchoice></para>\r
+ <procedure>\r
+ <title>Adding Groups</title>\r
+ <step><para>Select the <guibutton>Group Configuration</guibutton> tab if not \r
+ already selected in the right pane</para></step>\r
+ <step><para>Click <guibutton>New Child</guibutton></para></step>\r
+ <step><para>Enter a unique <guilabel>Group Name</guilabel></para></step>\r
+ <step><para>Enter a <guilabel>Description</guilabel></para></step>\r
+ <step><para>Select a <guilabel>Permission Interval</guilabel>. This will determine the \r
+ default expiry date of user account when you register patrons and select \r
+ their groups</para></step>\r
+ <step><para>Selecting an <guilabel>Editing Permission</guilabel> will determine the group level the user will have for editing other users.</para></step>\r
+ <step><para>Select the <guilabel>Parent Group</guilabel> for the group.</para>\r
+ <note><para>The group will inherit its parent group's permissions so it is unecessary to assign permissions already inherited from its parent.</para></note></step>\r
+ <step><para>Click the <guibutton>Save</guibutton> button.</para></step> \r
+ </procedure>\r
+ <procedure>\r
+ <title>Deleting Groups</title>\r
+ <step><para>Select the group you wish to delete from the group tree on \r
+ left pane.</para></step>\r
+ <step><para>Click the <guibutton>Delete</guibutton> button.</para></step>\r
+ <step><para>Click on <guibutton>OK</guibutton>to verify.</para></step>\r
+ </procedure>\r
+ <procedure>\r
+ <title>Editing Groups</title>\r
+ <step><para>Select the group you wish to edit from the group tree on left pane.</para></step>\r
+ <step><para>Edit the fields you wish to change in the right pane.</para></step>\r
+ <step><para>Click on <guibutton>Save</guibutton> to save changes.</para></step> \r
+ </procedure>\r
+ <procedure>\r
+ <title>Adding Group Permissions</title>\r
+ <step><para>Select the <guibutton>Group Permissions</guibutton> tab on the right \r
+ pane</para></step>\r
+ <step><para>Click on <guibutton>New Mapping</guibutton>.</para></step>\r
+ <step><para>Select the permission you would like to add from the \r
+ <guibutton>Permission</guibutton> Select box.</para></step>\r
+ <step><para>Select the <guibutton>Depth</guibutton> you wish to set the \r
+ permission. This will determine if the group has the permission at a local level or across a\r
+ system, or consortium, or other organizational unit type.</para></step>\r
+ <step><para>check the <guibutton>Grantable</guibutton> check box to allow the user to \r
+ grant the permission to others.</para></step>\r
+ <step><para>Click <guibutton>Add Mapping</guibutton> to add the permission to the \r
+ group</para></step>\r
+ </procedure>\r
+ <procedure>\r
+ <title>Deleting Group Permissions</title>\r
+ <step><para>Select the group permission you wish to delete.</para></step>\r
+ <step><para>Click the <guibutton>Delete Selected</guibutton> button.</para></step>\r
+ <step><para>Click on <guibutton>OK</guibutton> to verify</para></step>\r
+ </procedure>\r
+ <procedure>\r
+ <title>Editing Group Permissions</title>\r
+ <step><para>Click on the <guilabel>Depth</guilabel> or <guilabel>Grantable</guilabel> \r
+ field for the permission setting you wish to change.</para></step>\r
+ <step><para>Make changes to other permissions in the same way.</para></step>\r
+ <step><para>Click <guibutton>Save Changes</guibutton> when you are finished all \r
+ the changes.</para></step>\r
+ </procedure>\r
+ </section>\r
+ <section>\r
+ <title>Permissions</title>\r
+ <table xml:id="permissiondescriptions">\r
+ <title>Permissions Table</title>\r
+ <tgroup cols="2">\r
+ <thead>\r
+ <row>\r
+ <entry>Permission Name</entry>\r
+ <entry>Permission Description</entry>\r
+ </row>\r
+ </thead>\r
+ <tbody>\r
+ <row>\r
+ <entry>ABORT_REMOTE_TRANIST</entry>\r
+ <entry>Allows user to abort a copy transit if the user is not at \r
+ the transit source or destination</entry>\r
+ </row>\r
+ <row>\r
+ <entry>ABORT_TRANSIT</entry>\r
+ <entry>Allows user to abort a copy transit if the user is at the \r
+ transit destination or source</entry>\r
+ </row>\r
+ <row>\r
+ <entry>ASSIGN_WORK_ORG_UNIT </entry>\r
+ <entry>Allows user to define where another staff member's \r
+ permissions apply via the Permissions Editor interface.</entry>\r
+ </row>\r
+ <row>\r
+ <entry>BAR_PATRON</entry>\r
+ <entry>Allows user to bar a patron</entry>\r
+ </row>\r
+ <row>\r
+ <entry>CANCEL_HOLDS</entry>\r
+ <entry>Allows user to cancel holds</entry>\r
+ </row>\r
+ <row>\r
+ <entry>CIRC_CLAIMS_RETURNED.override</entry>\r
+ <entry>Allows user to check in/out an item that is claims \r
+ returned</entry>\r
+ </row>\r
+ <row>\r
+ <entry>CIRC_EXCEEDS_COPY_RANGE.override</entry>\r
+ <entry>Allows user to override the copy exceeds range event</entry>\r
+ </row>\r
+ <row>\r
+ <entry>CIRC_OVERRIDE_DUE_DATE</entry>\r
+ <entry>Allows user to change due date</entry>\r
+ </row>\r
+ <row>\r
+ <entry>CIRC_PERMIT_OVERRIDE</entry>\r
+ <entry>Allows user to bypass the circ permit call for i\r
+ checkout</entry>\r
+ </row>\r
+ <row>\r
+ <entry>COPY_ALERT_MESSAGE.override</entry>\r
+ <entry>Allows user to check in/out an item that has an alert \r
+ message</entry>\r
+ </row>\r
+ <row>\r
+ <entry>COPY_BAD_STATUS.override</entry>\r
+ <entry>Allows user to check out an item in a non-circulatable \r
+ status</entry>\r
+ </row>\r
+ <row>\r
+ <entry>COPY_CHECKIN</entry>\r
+ <entry>Allows user to check in a copy</entry>\r
+ </row>\r
+ <row>\r
+ <entry>COPY_CHECKOUT</entry>\r
+ <entry>Allows user to check out a copy</entry>\r
+ </row>\r
+ <row>\r
+ <entry>COPY_CIRC_NOT_ALLOWED.override</entry>\r
+ <entry>Allows user to checkout an item that is marked as \r
+ non-circ</entry>\r
+ </row>\r
+ <row>\r
+ <entry>COPY_HOLDS</entry>\r
+ <entry>Allows user to place a hold on a specific copy</entry>\r
+ </row>\r
+ <row>\r
+ <entry>COPY_IS_REFERENCE.override</entry>\r
+ <entry>Allows user to override the copy_is_reference event</entry>\r
+ </row>\r
+ \r
+ <row>\r
+ <entry>COPY_NOT_AVAILABLE.override</entry>\r
+ <entry>Allows user to force checkout of Missing/Lost type \r
+ items</entry>\r
+ </row>\r
+ <row>\r
+ <entry>COPY_STATUS_LOST.override</entry>\r
+ <entry>Allows user to remove the lost status from a copy</entry>\r
+ </row>\r
+ <row>\r
+ <entry>COPY_STATUS_MISSING.override</entry>\r
+ <entry>Allows user to change the missing status on a copy</entry>\r
+ </row>\r
+ <row>\r
+ <entry>COPY_TRANSIT_RECEIVE</entry>\r
+ <entry>Allows user to close out a transit on a copy</entry>\r
+ </row>\r
+ <row>\r
+ <entry>CREATE_BILL</entry>\r
+ <entry>Allows user to create a new bill on a transaction</entry>\r
+ </row>\r
+ <row>\r
+ <entry>CREATE_CONTAINER</entry>\r
+ <entry>Allows user to create containers owned by other users \r
+ (containers are Item Buckets, Volume Buckets, and Book Bags)</entry>\r
+ </row>\r
+ <row>\r
+ <entry>CREATE_CONTAINER_ITEM</entry>\r
+ <entry>Allows user to place an item in a container (even if the \r
+ container is owned by other users).</entry>\r
+ </row>\r
+ <row>\r
+ <entry>CREATE_COPY</entry>\r
+ <entry>Allows user to create a new copy object</entry>\r
+ </row>\r
+ <row>\r
+ <entry>CREATE_COPY_LOCATION</entry>\r
+ <entry>Allows user to create a new copy location</entry>\r
+ </row>\r
+ <row>\r
+ <entry>CREATE_COPY_NOTE</entry>\r
+ <entry>Allows user to create a new copy note</entry>\r
+ </row>\r
+ <row>\r
+ <entry>CREATE_COPY_STAT_CAT</entry>\r
+ <entry>Allows user to create a statisitcal category for \r
+ copies</entry>\r
+ </row>\r
+ <row>\r
+ <entry>CREATE_COPY_STAT_CAT_ENTRY</entry>\r
+ <entry>Allows user to create a new entry for a copy statistical \r
+ category</entry>\r
+ </row>\r
+ <row>\r
+ <entry>CREATE_COPY_STAT_CAT_ENTRY_MAP</entry>\r
+ <entry>Allows user to link a copy to a statistical category \r
+ (i.e., allows user to specify the appropriate entry for a copy and \r
+ given statistical category)</entry>\r
+ </row>\r
+ <row>\r
+ <entry>CREATE_COPY_TRANSIT</entry>\r
+ <entry>Allows user to create a transit</entry>\r
+ </row>\r
+ <row>\r
+ <entry>CREATE_DUPLICATE_HOLDS</entry>\r
+ <entry>Allows user to create duplicate holds (e.g. two holds on the \r
+ same title)</entry>\r
+ </row>\r
+ <row>\r
+ <entry>CREATE_HOLD_NOTIFICATION</entry>\r
+ <entry>Allows user to create new hold notifications</entry>\r
+ </row>\r
+ <row>\r
+ <entry>CREATE_IN_HOUSE_USE</entry>\r
+ <entry>Allows user to create a new in-house-use</entry>\r
+ </row>\r
+ <row>\r
+ <entry>CREATE_MARC</entry>\r
+ <entry>Allows user to create new MARC records</entry>\r
+ </row>\r
+ <row>\r
+ <entry>CREATE_MY_CONTAINER</entry>\r
+ <entry>Allows user to create containers for self (containers are \r
+ Item Buckets, Volume Buckets, and Book Bags).</entry>\r
+ </row>\r
+ <row>\r
+ <entry>CREATE_NON_CAT_TYPE</entry>\r
+ <entry>Allows user to create a new non-cataloged item type</entry>\r
+ </row>\r
+ <row>\r
+ <entry>CREATE_PATRON_STAT_CAT</entry>\r
+ <entry>Allows user to create a new patron statistical \r
+ category</entry>\r
+ </row>\r
+ <row>\r
+ <entry>CREATE_PATRON_STAT_CAT_ENTRY</entry>\r
+ <entry>Allows user to create a new possible entry for patron \r
+ statistical categories</entry>\r
+ </row>\r
+ <row>\r
+ <entry>CREATE_PATRON_STAT_CAT_ENTRY_MAP</entry>\r
+ <entry>Allows user to link another user to a stat cat entry (i.e., \r
+ specify the patron's entry for a given statistical category)</entry>\r
+ </row>\r
+ <row>\r
+ <entry>CREATE_PAYMENT</entry>\r
+ <entry>Allows user to record payments in the Billing \r
+ Interface</entry>\r
+ </row>\r
+ <row>\r
+ <entry>CREATE_TITLE_NOTE</entry>\r
+ <entry>Allows user to create a new title note</entry>\r
+ </row>\r
+ <row>\r
+ <entry>CREATE_TRANSACTION</entry>\r
+ <entry>Allows user to create new billable transactions (these \r
+ include checkouts and transactions created via the Bill Patron \r
+ operation)</entry>\r
+ </row>\r
+ <row>\r
+ <entry>CREATE_TRANSIT</entry>\r
+ <entry>Allows user to place item in transit</entry>\r
+ </row>\r
+ <row>\r
+ <entry>CREATE_USER</entry>\r
+ <entry>Allows user to create another user</entry>\r
+ </row>\r
+ <row>\r
+ <entry>CREATE_USER_GROUP_LINK</entry>\r
+ <entry>Allows user to add other users to permission groups</entry>\r
+ </row>\r
+ <row>\r
+ <entry>CREATE_VOLUME</entry>\r
+ <entry>Allows user to create a volume</entry>\r
+ </row>\r
+ <row>\r
+ <entry>CREATE_VOLUME_NOTE</entry>\r
+ <entry>Allows user to create a new volume note</entry>\r
+ </row>\r
+ <row>\r
+ <entry>DELETE_CONTAINER</entry>\r
+ <entry>Allows user to delete containers (containers are Item Buckets, \r
+ Volume Buckets, and Book Bags).</entry>\r
+ </row>\r
+ <row>\r
+ <entry>DELETE_CONTAINER_ITEM</entry>\r
+ <entry>Allows user to remove items from buckets and bookbags</entry>\r
+ </row>\r
+ <row>\r
+ <entry>DELETE_COPY</entry>\r
+ <entry>Allows user to delete a copy</entry>\r
+ </row>\r
+ <row>\r
+ <entry>DELETE_COPY_LOCATION</entry>\r
+ <entry>Allows user to delete a copy location</entry>\r
+ </row>\r
+ <row>\r
+ <entry>DELETE_COPY_NOTE</entry>\r
+ <entry>Allows user to delete copy notes</entry>\r
+ </row>\r
+ <row>\r
+ <entry>DELETE_COPY_STAT_CAT</entry>\r
+ <entry>Allows user to delete a copy statistical category</entry>\r
+ </row>\r
+ <row>\r
+ <entry>DELETE_COPY_STAT_CAT_ENTRY</entry>\r
+ <entry>Allows user to delete an entry for a copy statistical \r
+ category</entry>\r
+ </row>\r
+ <row>\r
+ <entry>DELETE_COPY_STAT_CAT_ENTRY_MAP</entry>\r
+ <entry>Allows user to delete a copy stat cat entry map</entry>\r
+ </row>\r
+ <row>\r
+ <entry>DELETE_NON_CAT_TYPE</entry>\r
+ <entry>Allows user to delete a non cataloged type (the user still \r
+ cannot deleted a non-cat type if any items of that type have \r
+ circulated).</entry>\r
+ </row>\r
+ <row>\r
+ <entry>DELETE_PATRON_STAT_CAT</entry>\r
+ <entry>Allows user to delete a patron statistical category</entry>\r
+ </row>\r
+ <row>\r
+ <entry>DELETE_PATRON_STAT_CAT_ENTRY</entry>\r
+ <entry>Allows user to delete an entry for patron statistical \r
+ categories</entry>\r
+ </row>\r
+ <row>\r
+ <entry>DELETE_PATRON_STAT_CAT_ENTRY_MAP</entry>\r
+ <entry>Allows user to remove a patron's entry for a given \r
+ statistical category</entry>\r
+ </row>\r
+ <row>\r
+ <entry>DELETE_RECORD</entry>\r
+ <entry>Allows user to delete a bib record</entry>\r
+ </row>\r
+ <row>\r
+ <entry>DELETE_TITLE_NOTE</entry>\r
+ <entry>Allows user to delete title notes</entry>\r
+ </row>\r
+ <row>\r
+ <entry>DELETE_USER</entry>\r
+ <entry>Allows user to mark a user as deleted</entry>\r
+ </row>\r
+ <row>\r
+ <entry>DELETE_VOLUME</entry>\r
+ <entry>Allows user to delete a volume</entry>\r
+ </row>\r
+ <row>\r
+ <entry>DELETE_VOLUME_NOTE</entry>\r
+ <entry>Allows user to delete volume notes</entry>\r
+ </row>\r
+ <row>\r
+ <entry>DELETE_WORKSTATION</entry>\r
+ <entry>Allows user to remove an existing workstation so a new one \r
+ can replace it</entry>\r
+ </row>\r
+ <row>\r
+ <entry>EVERYTHING</entry>\r
+ <entry> Every permssion is granted (for sysadmins and developers \r
+ only!)</entry>\r
+ </row>\r
+ <row>\r
+ <entry>HOLD_EXISTS.override</entry>\r
+ <entry>Allows users to place multiple holds on a single \r
+ copy/volume/title/metarecord (depending on hold type)</entry>\r
+ </row>\r
+ <row>\r
+ <entry>IMPORT_MARC</entry>\r
+ <entry>Allows user to import a MARC record via the z39.50 \r
+ interface</entry>\r
+ </row>\r
+ <row>\r
+ <entry>ITEM_AGE_PROTECTED.override</entry>\r
+ <entry>Allows user to place a hold on an age-protected item</entry>\r
+ </row> <row>\r
+ <entry>ITEM_ON_HOLDS_SHELF.override</entry>\r
+ <entry>Allows user to check out an item that is on holds shelf for a \r
+ different patron</entry>\r
+ </row>\r
+ <row>\r
+ <entry>MAX_RENEWALS_REACHED.override</entry>\r
+ <entry>Allows user to renew an item past the maximun renewal \r
+ count</entry>\r
+ </row>\r
+ <row>\r
+ <entry>MERGE_BIB_RECORDS</entry>\r
+ <entry>Allows user to merge bib records and their associated data \r
+ regardless of their bib/volume/copy level perms (in theory - as of \r
+ 1.2.2, users still must have VOLUME_UPDATE and UPDATE_VOLUME in \r
+ order to merge records.</entry>\r
+ </row>\r
+ <row>\r
+ <entry>MR_HOLDS</entry>\r
+ <entry>Allows user to create a metarecord holds</entry>\r
+ </row>\r
+ <row>\r
+ <entry>OFFLINE_EXECUTE</entry>\r
+ <entry>Allows user to process an offline/standalone script \r
+ batch</entry>\r
+ </row>\r
+ <row>\r
+ <entry>OFFLINE_UPLOAD </entry>\r
+ <entry>Allows user to upload an offline/standalone script</entry>\r
+ </row>\r
+ <row>\r
+ <entry>OFFLINE_VIEW</entry>\r
+ <entry>Allows user to view uploaded offline script information</entry>\r
+ </row>\r
+ <row>\r
+ <entry>OPAC_LOGIN</entry>\r
+ <entry>Allows user to login to the OPAC</entry>\r
+ </row>\r
+ <row>\r
+ <entry>patron_exceeds_checkout_count.override</entry>\r
+ <entry>Allow user to override checkout count failure</entry>\r
+ </row>\r
+ <row>\r
+ <entry>patron_exceeds_fines .override</entry>\r
+ <entry>Allow user to override fine amount checkout failure</entry>\r
+ </row>\r
+ <row>\r
+ <entry>patron_exceeds_overdue_count .override</entry>\r
+ <entry>Allow user to override overdue count failure</entry>\r
+ </row>\r
+ <row>\r
+ <entry>REGISTER_WORKSTATION</entry>\r
+ <entry>Allows user to register a new workstation</entry>\r
+ </row>\r
+ <row>\r
+ <entry>REMOTE_Z3950_QUERY</entry>\r
+ <entry>Allows user to perform z3950 queries against remote \r
+ servers</entry>\r
+ </row>\r
+ <row>\r
+ <entry>REMOVE_USER_GROUP_LINK</entry>\r
+ <entry>Allows user to remove other users from permission \r
+ groups</entry>\r
+ </row>\r
+ <row>\r
+ <entry>RENEW_CIRC</entry>\r
+ <entry>Allows user to renew items</entry>\r
+ </row>\r
+ <row>\r
+ <entry>RENEW_HOLD_OVERRIDE</entry>\r
+ <entry>Allows user to continue to renew an item even if it is \r
+ required for a hold.</entry>\r
+ </row>\r
+ <row>\r
+ <entry>REQUEST_HOLDS</entry>\r
+ <entry>Allows user to create holds for another user (if true, we \r
+ still check to make sure they have permission to make the type of \r
+ hold they are requesting, e.g. COPY_HOLDS)</entry>\r
+ </row>\r
+ <row>\r
+ <entry>RUN_REPORTS</entry>\r
+ <entry>Allows user to view the Reports Interface, create templates, \r
+ and run reports</entry>\r
+ </row>\r
+ <row>\r
+ <entry>SET_CIRC_CLAIMS_RETURNED</entry>\r
+ <entry>Allows user to mark an item as claimed returned</entry>\r
+ </row>\r
+ <row>\r
+ <entry>SET_CIRC_LOST</entry>\r
+ <entry>Allows user to mark an item as lost</entry>\r
+ </row>\r
+ <row>\r
+ <entry>SET_CIRC_MISSING</entry>\r
+ <entry>Allows user to mark an item as missing</entry>\r
+ </row>\r
+ <row>\r
+ <entry>SHARE_REPORT_FOLDER</entry>\r
+ <entry>Allows user to share Template/Report/Output folders via the \r
+ Reporting Interface</entry>\r
+ </row>\r
+ <row>\r
+ <entry>STAFF_LOGIN</entry>\r
+ <entry>Allows user to login to the staff client</entry>\r
+ </row>\r
+ <row>\r
+ <entry>TITLE_HOLDS</entry>\r
+ <entry> Allows user to place a hold at the title level</entry>\r
+ </row>\r
+ <row>\r
+ <entry>UNBAR_PATRON</entry>\r
+ <entry> Allows user to un-bar a patron</entry>\r
+ </row>\r
+ <row>\r
+ <entry>UPDATE_BATCH_COPY</entry>\r
+ <entry>Allows user to edit copies in batch</entry>\r
+ </row>\r
+ <row>\r
+ <entry>UPDATE_CONTAINER</entry>\r
+ <entry>Allows user to update another users Buckets or Book \r
+ Bags</entry>\r
+ </row>\r
+ <row>\r
+ <entry>UPDATE_COPY</entry>\r
+ <entry>Allows user to edit a copy</entry>\r
+ </row>\r
+ <row>\r
+ <entry>UPDATE_COPY_LOCATION</entry>\r
+ <entry>Allows user to edit a copy location</entry>\r
+ </row>\r
+ <row>\r
+ <entry>UPDATE_COPY_STAT_CAT</entry>\r
+ <entry>Allows user to change a copy statistical category</entry>\r
+ </row>\r
+ <row>\r
+ <entry>UPDATE_COPY_STAT_CAT_ENTRY</entry>\r
+ <entry>Allows user to change a copy statistical category entry</entry>\r
+ </row>\r
+ <row>\r
+ <entry>UPDATE_HOLD</entry>\r
+ <entry>Allows user to edit holds (such as change notification phone \r
+ number or pickup library, as well as retarget the hold and capture \r
+ an item for hold or pickup)</entry>\r
+ </row>\r
+ <row>\r
+ <entry>UPDATE_MARC</entry>\r
+ <entry>Allows user to edit a marc record</entry>\r
+ </row>\r
+ <row>\r
+ <entry>UPDATE_NON_CAT_TYPE</entry>\r
+ <entry>Allows user to update a non cataloged type</entry>\r
+ </row>\r
+ <row>\r
+ <entry>UPDATE_ORG_SETTING</entry>\r
+ <entry>Allows user to update an org unit setting</entry>\r
+ </row>\r
+ <row>\r
+ <entry>UPDATE_ORG_UNIT</entry>\r
+ <entry>Allows user to change org unit settings</entry>\r
+ </row>\r
+ <row>\r
+ <entry>UPDATE_PATRON_STAT_CAT</entry>\r
+ <entry>Allows user to change a patron statistical category (such as \r
+ renaming the category)</entry>\r
+ </row>\r
+ <row>\r
+ <entry>UPDATE_PATRON_STAT_CAT_ENTRY</entry>\r
+ <entry>Allows user to change a patron stat cat entry(such as \r
+ renaming the entry)</entry>\r
+ </row>\r
+ <row>\r
+ <entry>UPDATE_RECORD</entry>\r
+ <entry>Allows user to undelete a MARC record</entry>\r
+ </row>\r
+ <row>\r
+ <entry>UPDATE_USER</entry>\r
+ <entry>Allows user to edit a user's record</entry>\r
+ </row>\r
+ <row>\r
+ <entry>UPDATE_VOLUME</entry>\r
+ <entry>Allows user to edit volumes - needed for merging records. \r
+ This is a duplicate of VOLUME_UPDATE; user must have both \r
+ permissions at appropriate level to merge records.</entry>\r
+ </row>\r
+ <row>\r
+ <entry>VIEW_CIRCULATIONS</entry>\r
+ <entry>Allows user to see what another user has checked out</entry>\r
+ </row>\r
+ <row>\r
+ <entry>VIEW_CONTAINER</entry>\r
+ <entry>Allows user to view buckets and bookbags</entry>\r
+ </row>\r
+ <row>\r
+ <entry>VIEW_COPY_CHECKOUT_HISTORY</entry>\r
+ <entry>Allows user to view which users have checked out a given \r
+ copy</entry>\r
+ </row>\r
+ <row>\r
+ <entry>VIEW_COPY_NOTES</entry>\r
+ <entry>Allows user to view notes attached to a copy</entry>\r
+ </row>\r
+ <row>\r
+ <entry>VIEW_HOLD</entry>\r
+ <entry>Allows user to view another user's holds</entry>\r
+ </row>\r
+ <row>\r
+ <entry>VIEW_HOLD_NOTIFICATION</entry>\r
+ <entry>Allows user to view notifications attached to a hold</entry>\r
+ </row>\r
+ <row>\r
+ <entry>VIEW_HOLD_PERMIT</entry>\r
+ <entry>Allows user to see if another user has permission to place a \r
+ hold on a given copy</entry>\r
+ </row>\r
+ <row>\r
+ <entry>VIEW_PERM_GROUPS</entry>\r
+ <entry>Allows user to view permission groups.</entry>\r
+ </row>\r
+ <row>\r
+ <entry>VIEW_PERMISSION</entry>\r
+ <entry>Allows user to view user permissions within the user \r
+ permissions editor</entry>\r
+ </row>\r
+ <row>\r
+ <entry>VIEW_PERMIT_CHECKOUT</entry>\r
+ <entry>Allows user to see if another user can check out an item \r
+ (should be true for all staff)</entry>\r
+ </row>\r
+ <row>\r
+ <entry>VIEW_REPORT_OUTPUT</entry>\r
+ <entry>Allows user to view report output</entry>\r
+ </row>\r
+ <row>\r
+ <entry>VIEW_TITLE_NOTES</entry>\r
+ <entry>Allows user to view all notes attached to a title</entry>\r
+ </row>\r
+ <row>\r
+ <entry>VIEW_TRANSACTION</entry>\r
+ <entry>Allows user to see another users grocery/circ transactions \r
+ in the Bills Interface</entry>\r
+ </row>\r
+ <row>\r
+ <entry>VIEW_USER</entry>\r
+ <entry>Allows user to view another user's Patron Record</entry>\r
+ </row>\r
+ <row>\r
+ <entry>VIEW_USER_FINES_SUMMARY</entry>\r
+ <entry>Allows user to view bill details</entry>\r
+ </row>\r
+ <row>\r
+ <entry>VIEW_USER_TRANSACTIONS</entry>\r
+ <entry>*same as VIEW_TRANSACTION (duplicate perm)</entry>\r
+ </row>\r
+ <row>\r
+ <entry>VIEW_VOLUME_NOTES</entry>\r
+ <entry>Allows user to view all notes attached to a volume</entry>\r
+ </row>\r
+ <row>\r
+ <entry>VIEW_ZIP_DATA</entry>\r
+ <entry>Allows user to query the zip code data method</entry>\r
+ </row>\r
+ <row>\r
+ <entry>VOID_BILLING</entry>\r
+ <entry>Allows user to void a bill</entry>\r
+ </row>\r
+ <row>\r
+ <entry>VOLUME_HOLDS</entry>\r
+ <entry> Allows user to place a volume level hold</entry>\r
+ </row>\r
+ \r
+ <row>\r
+ <entry>actor.org_unit.closed_date.create</entry>\r
+ <entry>Allows user to create a new closed date for a location</entry>\r
+ </row>\r
+ <row>\r
+ <entry>actor.org_unit.closed_date.delete</entry>\r
+ <entry>Allows user to remove a closed date interval for a given \r
+ location</entry>\r
+ </row>\r
+ <row>\r
+ <entry>actor.org_unit.closed_date.update</entry>\r
+ <entry>Allows user to update a closed date interval for a given \r
+ location</entry>\r
+ </row>\r
+ <row>\r
+ <entry>group_application.user</entry>\r
+ <entry>Allows user to add/remove users to/from the User group</entry>\r
+ </row>\r
+ <row>\r
+ <entry>group_application.user.patron</entry>\r
+ <entry>Allows user to add/remove users to/from the Patron \r
+ group</entry>\r
+ </row>\r
+ <row>\r
+ <entry>group_application.user.sip_client</entry>\r
+ <entry>Allows user to add/remove users to/from the SIP-Client \r
+ group</entry>\r
+ </row>\r
+ <row>\r
+ <entry>group_application.user.staff</entry>\r
+ <entry>Allows user to add/remove users to/from the Staff \r
+ group</entry>\r
+ </row>\r
+ <row>\r
+ <entry>group_application.user.staff.admin.global_admin</entry>\r
+ <entry>Allows user to add/remove users to/from the GlobalAdmin \r
+ group</entry>\r
+ </row>\r
+ <row>\r
+ <entry>group_application.user.staff.admin.lib_manager</entry>\r
+ <entry>Allows user to add/remove users to/from the LibraryManager \r
+ group</entry>\r
+ </row>\r
+ <row>\r
+ <entry>group_application.user.staff.admin.local_admin</entry>\r
+ <entry>Allows user to add/remove users to/from the LocalAdmin \r
+ group</entry>\r
+ </row>\r
+ <row>\r
+ <entry>group_application.user.staff.cat</entry>\r
+ <entry>Allows user to add/remove users to/from the Cataloger group</entry>\r
+ </row>\r
+ <row>\r
+ <entry>group_application.user.staff.cat.cat1</entry>\r
+ <entry>Allows user to add/remove users to/from the Cat1 group</entry>\r
+ </row>\r
+ <row>\r
+ <entry>group_application.user.staff.circ</entry>\r
+ <entry>Allows user to add/remove users to/from the Circulator \r
+ group</entry>\r
+ </row>\r
+ <row>\r
+ <entry>group_application.user.staff.supercat</entry>\r
+ <entry>Allows user to add/remove users to/from the Supercat \r
+ group</entry>\r
+ </row>\r
+ <row>\r
+ <entry>group_application.user.vendor</entry>\r
+ <entry>Allows user to add/remove users to/from the Vendor \r
+ group</entry>\r
+ </row>\r
+ <row>\r
+ <entry>money.collections_tracker.create</entry>\r
+ <entry>Allows user to put someone into collections</entry>\r
+ </row>\r
+ <row>\r
+ <entry>money.collections_tracker.delete</entry>\r
+ <entry>Allows user to take someone out of collections</entry>\r
+ </row>\r
+ </tbody>\r
+ </tgroup>\r
+ </table> \r
+ </section>\r
+ </section>\r
+ <section>\r
+ <info>\r
+\r
+ <title>Staff Accounts</title>\r
+ </info>\r
+\r
+ <informalfigure>\r
+ <para> New staff accounts are created in much the same way as patron accounts, using <menuchoice>\r
+ <guimenu>Circulation</guimenu>\r
+ <guimenuitem>Register Patron</guimenuitem>\r
+ </menuchoice> or <keycombo>\r
+ <keycap>Shift</keycap>\r
+ <keycap>F1</keycap>\r
+ </keycombo>. Select one of the staff profiles from the <guilabel>Profile\r
+ Group</guilabel> drop-down menu. </para>\r
+ <para>\r
+ <mediaobject>\r
+ <alt>User permissions screenshot</alt>\r
+ <imageobject>\r
+ <imagedata scalefit="0" fileref="../media/profile-2.png"/>\r
+ </imageobject>\r
+\r
+ </mediaobject>\r
+ </para>\r
+ </informalfigure>\r
+\r
+\r
+\r
+ <para xml:id="profiles-working">Each new staff account must be assigned a <guilabel>Working\r
+ Location</guilabel> which determines its access level in staff client interfaces.\r
+ Accounts migrated from legacy systems or created before the upgrade to Evergreen 1.6 already\r
+ have working locations assigned.</para>\r
+\r
+\r
+ <procedure>\r
+ <step>\r
+ <para>To assign a working location open the newly created staff account using\r
+ <keycap>F1</keycap> (retrieve patron) or <keycap>F4</keycap> (patron search).\r
+ </para>\r
+ </step>\r
+\r
+ <step>\r
+ <informalfigure>\r
+ <para>Select <menuchoice>\r
+ <guimenu>Other</guimenu>\r
+ <guimenuitem>User Permission Editor</guimenuitem>\r
+ </menuchoice></para>\r
+ <para>\r
+ <mediaobject>\r
+ <alt>User permissions screenshot</alt>\r
+ <imageobject>\r
+ <imagedata scalefit="0" fileref="../media/profile-1.png"/>\r
+ </imageobject>\r
+\r
+ </mediaobject>\r
+ </para>\r
+ </informalfigure>\r
+ </step>\r
+\r
+ <step>\r
+ <para>Place a check in the box next to the desired working location, then scroll to the\r
+ bottom of the display and click <guibutton>Save</guibutton>.</para>\r
+\r
+\r
+ </step>\r
+\r
+ </procedure>\r
+\r
+ <note>\r
+ <para>In multi-branch libraries it is possible to assign more than one working\r
+ location</para>\r
+ </note>\r
+\r
+\r
+ <section xml:id="staff_account_permissions">\r
+ <info>\r
+ <title>Staff Account Permissions</title>\r
+ </info>\r
+ <para>Below is a general outline of staff account permission levels. To view a detailed list\r
+ of permissions for a particular Evergreen account go to <menuchoice>\r
+ <guimenu>Admin (-)</guimenu>\r
+ <guimenuitem>User permission editor</guimenuitem>\r
+ </menuchoice> in the staff client.</para>\r
+\r
+ <informaltable>\r
+\r
+ <tgroup cols="7" align="center" colsep="1" rowsep="1">\r
+\r
+ <thead>\r
+ <row>\r
+ <entry>Action</entry>\r
+ <entry>General Staff</entry>\r
+ <entry>Circulators</entry>\r
+ <entry>Circ + Copy Edit</entry>\r
+ <entry>Circ + Full Cat</entry>\r
+ <entry>Catalogers</entry>\r
+ <entry>Local System Administrator (LSA)</entry>\r
+ </row>\r
+ </thead>\r
+\r
+ <tbody>\r
+ <row>\r
+ <entry>Basic circulation functions</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ </row>\r
+\r
+\r
+ <row>\r
+ <entry>CheckIn bad status overrides</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ </row>\r
+\r
+ <row>\r
+ <entry>CheckIn Missing/Lost/ClaimedReturned overrides</entry>\r
+ <entry/>\r
+ <entry/>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry/>\r
+ <entry>*</entry>\r
+ </row>\r
+ <row>\r
+ <entry>CheckOut overrides</entry>\r
+ <entry/>\r
+ <entry/>\r
+ <entry/>\r
+ <entry>*</entry>\r
+ <entry/>\r
+ <entry>*</entry>\r
+ </row>\r
+\r
+ <row>\r
+ <entry>MaxRenewalReached override</entry>\r
+ <entry/>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ </row>\r
+\r
+\r
+\r
+ <row>\r
+ <entry>Basic patron record</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ </row>\r
+\r
+\r
+ <row>\r
+ <entry>Bar patrons</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry/>\r
+ <entry>*</entry>\r
+ </row>\r
+ <row>\r
+ <entry>Unbar patrons</entry>\r
+ <entry/>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry/>\r
+ <entry>*</entry>\r
+ </row>\r
+\r
+ <row>\r
+ <entry>Merge/delete patrons</entry>\r
+ <entry/>\r
+ <entry/>\r
+ <entry/>\r
+ <entry/>\r
+ <entry/>\r
+ <entry>*</entry>\r
+ </row>\r
+\r
+ <row>\r
+ <entry>Patron restriction overrides</entry>\r
+ <entry/>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry/>\r
+ <entry>*</entry>\r
+ </row>\r
+\r
+ <row>\r
+ <entry>Bills and payments</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry/>\r
+ <entry>*</entry>\r
+ </row>\r
+\r
+\r
+ <row>\r
+ <entry>Holds</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ </row>\r
+ <row>\r
+ <entry>Copy/volume records</entry>\r
+ <entry/>\r
+ <entry/>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ </row>\r
+\r
+ <row>\r
+ <entry>Bib records</entry>\r
+ <entry/>\r
+ <entry/>\r
+ <entry/>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ </row>\r
+ <row>\r
+ <entry>Buckets</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ </row>\r
+\r
+\r
+\r
+ <row>\r
+ <entry>View report output</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ </row>\r
+\r
+ <row>\r
+ <entry>Create/run reports</entry>\r
+ <entry/>\r
+ <entry/>\r
+ <entry/>\r
+ <entry/>\r
+ <entry/>\r
+ <entry>*</entry>\r
+ </row>\r
+\r
+ <row>\r
+ <entry>Create/upload offline transactions</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ </row>\r
+\r
+ <row>\r
+ <entry>Process offline transactions</entry>\r
+ <entry/>\r
+ <entry/>\r
+ <entry/>\r
+ <entry/>\r
+ <entry/>\r
+ <entry>*</entry>\r
+ </row>\r
+ <row>\r
+ <entry>Transit</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ </row>\r
+ <row>\r
+ <entry>Abort remote transit</entry>\r
+ <entry/>\r
+ <entry/>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ <entry>*</entry>\r
+ </row>\r
+\r
+ </tbody>\r
+ </tgroup>\r
+ </informaltable>\r
+ </section>\r
+\r
+ <section xml:id="profiles-grant-permissions">\r
+ <title>Granting Additional Permissions</title>\r
+ <para>A Local System Administrator (LSA) may selectively grant LSA permissions to other staff\r
+ accounts. In the example below a <emphasis>Circ +Full\r
+ Cat</emphasis> account is granted permission to process offline transactions, a function which otherwise requires an LSA login.</para>\r
+\r
+ <procedure>\r
+ <step>\r
+ <para>Log in as a Local System Administrator.</para>\r
+ </step>\r
+\r
+ <step><stepalternatives> <step>\r
+ \r
+ <para>Select <menuchoice>\r
+ <guimenu>Admin (-)</guimenu>\r
+ <guimenuitem>User Permission Editor</guimenuitem>\r
+ </menuchoice> and enter the staff account barcode when prompted</para>\r
+ \r
+ <para><emphasis role="bold">OR</emphasis></para>\r
+ </step>\r
+ <step>\r
+ \r
+ <para>Retrieve the staff account first, then select <menuchoice>\r
+ <guimenu>Other</guimenu>\r
+ <guimenuitem>User Permission Editor</guimenuitem>\r
+ </menuchoice></para>\r
+ \r
+ </step></stepalternatives></step>\r
+\r
+ <step>\r
+ <informalfigure>\r
+ <para>The <guilabel>User Permission Editor</guilabel> will load (this may take a\r
+ few seconds). Greyed-out permissions cannot be edited because they are\r
+ either a) already granted to the account, or b) not\r
+ available to any staff account, including LSAs.</para>\r
+ <para>\r
+ <mediaobject>\r
+ <alt>User permissions screenshot</alt>\r
+ <imageobject>\r
+ <imagedata scalefit="0" fileref="../media/profile-5.png"/>\r
+ </imageobject>\r
+\r
+ </mediaobject>\r
+ </para>\r
+\r
+ <para>\r
+ <inlinemediaobject>\r
+ <imageobject>\r
+ <imagedata scalefit="0" fileref="../media/1.png"/>\r
+ </imageobject>\r
+ </inlinemediaobject> List of permission names. For help correlating permissions to specific Evergreen\r
+ functions please contact Sitka support.</para>\r
+\r
+ <para>\r
+ <inlinemediaobject>\r
+ <imageobject>\r
+ <imagedata scalefit="0" fileref="../media/2.png"/>\r
+ </imageobject>\r
+ </inlinemediaobject>\r
+ If checked the permission is granted to this account.</para>\r
+\r
+ <para>\r
+ <inlinemediaobject>\r
+ <imageobject>\r
+ <imagedata scalefit="0" fileref="../media/3.png"/>\r
+ </imageobject>\r
+ </inlinemediaobject> <guilabel>Depth</guilabel> limits application to the staff member's library and should be left at the default. Evergreen blocks attempts to set Federation- or Sitka-wide privileges.</para>\r
+\r
+ <para>\r
+ <inlinemediaobject>\r
+ <imageobject>\r
+ <imagedata scalefit="0" fileref="../media/4.png"/>\r
+ </imageobject>\r
+ </inlinemediaobject>\r
+ If checked this staff account will be able to grant the new privilege to other accounts (not recommended).\r
+ </para>\r
+\r
+ </informalfigure>\r
+ </step>\r
+ \r
+ <step>\r
+ <informalfigure>\r
+ <para>To allow processing of offline transactions check the <emphasis>Applied</emphasis> column next to OFFLINE_EXECUTE.</para>\r
+ <para>\r
+ <mediaobject>\r
+ <alt>User permissions screenshot</alt>\r
+ <imageobject>\r
+ <imagedata scalefit="0" fileref="../media/profile-6.png"/>\r
+ </imageobject>\r
+ \r
+ </mediaobject>\r
+ </para>\r
+ \r
+ </informalfigure>\r
+ </step>\r
+ \r
+ <step>\r
+ <informalfigure>\r
+ <para>Scroll down and click <guibutton>Save</guibutton> to apply the changes.</para>\r
+ <para>\r
+ <mediaobject>\r
+ <alt>User permissions screenshot</alt>\r
+ <imageobject>\r
+ <imagedata scalefit="0" fileref="../media/profile-7.png"/>\r
+ </imageobject>\r
+ \r
+ </mediaobject>\r
+ </para>\r
+ \r
+ </informalfigure>\r
+ </step>\r
+ \r
+ </procedure>\r
+\r
+ \r
+ </section>\r
+</section>\r
+ <section xml:id="copystatus">\r
+ <title>Copy Status</title>\r
+ <para>To navigate to the copy status editor from the staff client menu, select \r
+ <menuchoice><guimenu>Admin</guimenu> <guisubmenu>Server Administration</guisubmenu> \r
+ <guisubmenu>Copy Statuses </guisubmenu></menuchoice></para>\r
+ <para>The Copy Status Editor is used to Add, edit and delete statuses of copies in your system.</para>\r
+ <para>Evergreen comes pre-loaded with a number of copy statuses.</para> \r
+ <table xml:id="copystatusestable">\r
+ <title>Copy Status Table</title>\r
+ <tgroup cols="4">\r
+ <thead>\r
+ <row>\r
+ <entry>ID</entry>\r
+ <entry>Name</entry>\r
+ <entry>Holdable - default setting</entry>\r
+ <entry>OPAC Visible - default setting</entry>\r
+ </row>\r
+ </thead>\r
+ <tbody>\r
+ <row>\r
+ <entry>0</entry>\r
+ <entry>Available</entry>\r
+ <entry>true</entry>\r
+ <entry>true</entry>\r
+ </row>\r
+ <row>\r
+ <entry>1</entry>\r
+ <entry>Checked out</entry>\r
+ <entry>true</entry>\r
+ <entry>true</entry>\r
+ </row>\r
+ <row>\r
+ <entry>2</entry>\r
+ <entry>Bindery</entry>\r
+ <entry>false</entry>\r
+ <entry>false</entry>\r
+ </row>\r
+ <row>\r
+ <entry>3</entry>\r
+ <entry>Lost</entry>\r
+ <entry>false</entry>\r
+ <entry>false</entry>\r
+ </row>\r
+ <row>\r
+ <entry>4</entry>\r
+ <entry>Missing</entry>\r
+ <entry>false</entry>\r
+ <entry>false</entry>\r
+ </row>\r
+ <row>\r
+ <entry>5</entry>\r
+ <entry>In process</entry>\r
+ <entry>false</entry>\r
+ <entry>true</entry>\r
+ </row>\r
+ <row>\r
+ <entry>6</entry>\r
+ <entry>In transit</entry>\r
+ <entry>true</entry>\r
+ <entry>true</entry>\r
+ </row>\r
+ <row>\r
+ <entry>7</entry>\r
+ <entry>Reshelving</entry>\r
+ <entry>true</entry>\r
+ <entry>true</entry>\r
+ </row>\r
+ <row>\r
+ <entry>8</entry>\r
+ <entry>On holds shelf</entry>\r
+ <entry>true</entry>\r
+ <entry>true</entry>\r
+ </row>\r
+ <row>\r
+ <entry>9</entry>\r
+ <entry>On order</entry>\r
+ <entry>true</entry>\r
+ <entry>true</entry>\r
+ </row>\r
+ <row>\r
+ <entry>10</entry>\r
+ <entry>ILL</entry>\r
+ <entry>true</entry>\r
+ <entry>false</entry>\r
+ </row>\r
+ <row>\r
+ <entry>11</entry>\r
+ <entry>Cataloging</entry>\r
+ <entry>true</entry>\r
+ <entry>false</entry>\r
+ </row>\r
+ <row>\r
+ <entry>12</entry>\r
+ <entry>Reserves</entry>\r
+ <entry>false</entry>\r
+ <entry>true</entry>\r
+ </row>\r
+ <row>\r
+ <entry>13</entry>\r
+ <entry>Discard/Weed</entry>\r
+ <entry>false</entry>\r
+ <entry>false</entry>\r
+ </row>\r
+ <row>\r
+ <entry>14</entry>\r
+ <entry>Damaged</entry>\r
+ <entry>false</entry>\r
+ <entry>false</entry>\r
+ </row>\r
+ <row>\r
+ <entry>15</entry>\r
+ <entry>On reservation shelf</entry>\r
+ <entry>true</entry>\r
+ <entry>false</entry>\r
+ </row>\r
+ </tbody>\r
+ </tgroup>\r
+ </table>\r
+ <para>It is possible to add, delete and edit copy statuses.</para>\r
+ <procedure>\r
+ <title>Adding Copy Statuses</title>\r
+ <step><para>In the <guilabel>New Status</guilabel> field, enter the name of the \r
+ new status you wish to add.</para></step>\r
+ <step><para>Click <guibutton>Add</guibutton>.</para></step>\r
+ <step><para>Locate you new status and check the <emphasis>Holdable</emphasis> check box \r
+ if you wish to all users to place holds on items in this status. Check \r
+ <emphasis>OPAC Visble</emphasis> if you wish for this status to appear in the public \r
+ OPAC.</para></step>\r
+ <step><para>Click <guibutton>Save Changes</guibutton> at the bottum of the screen to \r
+ save changes to the new status.</para></step>\r
+ </procedure>\r
+ <procedure>\r
+ <title>Deleting Copy Statuses</title>\r
+ <step><para>Highlight the statuses you wish to delete. Hold the \r
+ <keycap>Shift</keycap> to select more than one status.</para></step>\r
+ <step><para>Click <guibutton>Delete Selected</guibutton>.</para></step>\r
+ <step><para>Click OK to verify.</para>\r
+ <note><para>You will not be able to delete statuses if copies currently \r
+ exist with that status.</para></note>\r
+ </step>\r
+ </procedure>\r
+ <procedure>\r
+ <title>Editing Copy Statuses</title>\r
+ <step><para>Double click on a status name to change its name and enter the new \r
+ name.</para> <para>To change whether a status is visible in the OPAC, check or uncheck \r
+ the <emphasis>OPAC Visible</emphasis> check box.</para><para>To allow patrons the ability to \r
+ hold items in that status, check the <emphasis>Holdable</emphasis> check box. To prevent \r
+ users from holding items in that status, uncheck the <emphasis>Holdable</emphasis> \r
+ check box. </para></step>\r
+ <step><para>Once you have finished editing the statuses, remember to click \r
+ <guibutton>Save Changes</guibutton>.</para></step> \r
+ </procedure>\r
+ </section>\r
+ <section xml:id="billingtypes">\r
+ <title>Billing Types</title>\r
+ <para>The billing types editor is used for creating, editing and deleting billing types.</para> \r
+ <para>To navigate to the billing types editor from the staff client menu, select \r
+ <menuchoice><guimenu>Admin</guimenu> <guisubmenu>Server Administration</guisubmenu> \r
+ <guisubmenu>Billing Types</guisubmenu></menuchoice></para>\r
+ <procedure>\r
+ <title>Adding Billing Types</title>\r
+ <step><para>Click <guibutton>New Billing Type</guibutton>.</para></step>\r
+ <step><para>Enter the name of the billing type.</para></step>\r
+ <step><para>Select the <emphasis>Org Unit</emphasis> to use this billing type.</para></step>\r
+ <step><para>Enter the <emphasis>Default Price</emphasis>. This is only the default since \r
+ the actual price of a specific billing can be adjusted when staff create \r
+ a billing</para></step>\r
+ <step><para>Click <guibutton>Save</guibutton> to save the new billing type.</para></step>\r
+ </procedure>\r
+ <procedure>\r
+ <title>Deleting Billing Types</title>\r
+ <step><para>Check the checkbox of the billing type(s) you wish to delete.</para></step>\r
+ <step><para>Click <guibutton>Delete Selected</guibutton>.\r
+ <warning><para>The selected billing types will be deleted without a \r
+ verification alert.</para></warning>\r
+ </para></step>\r
+ </procedure>\r
+ <procedure>\r
+ <title>Editing Billing Types</title>\r
+ <step><para>Double click on a billing types to open the editing window.</para></step> \r
+ <step><para>Make desired changes to the <emphasis>name</emphasis>, \r
+ <emphasis>Org Unit</emphasis> and <emphasis>Default Price</emphasis>.</para></step>\r
+ <step><para>Once you have finished editing, click \r
+ <guibutton>Save</guibutton>.</para></step> \r
+ </procedure>\r
+ \r
+ </section>\r
+ <section xml:id="circmodifiers">\r
+ <title>Circulation Modifiers</title>\r
+ <para>The circulation modifier editor is used to create, edit and delete modifier categories to control \r
+ circulation policies on specific groups of items.</para> \r
+ <para>To navigate to the circulation modifiers editor from the staff client menu, select \r
+ <menuchoice>\r
+ <guimenu>Admin</guimenu> <guisubmenu>Server Administration</guisubmenu> \r
+ <guisubmenu>Circulation Modifiers</guisubmenu></menuchoice>.\r
+ </para>\r
+ <procedure>\r
+ <title>Adding Circulation Modifiers</title>\r
+ <step><para>Click <guibutton>New Circ Modifier</guibutton>.</para></step>\r
+ <step><para>Enter a <emphasis>Code</emphasis>, <emphasis>Name</emphasis> and \r
+ <emphasis>Description</emphasis>.</para></step>\r
+ <step><para>Select the <emphasis>SIP 2 Media Type</emphasis>.</para></step>\r
+ <step><para>Check the <guibutton>Magnetic Media</guibutton> check box if the item is magnetic media such as a casette \r
+ tape.</para></step>\r
+ <step><para>Click <guibutton>Save</guibutton> to save the new circulation \r
+ modifier.</para></step>\r
+ </procedure>\r
+ <procedure>\r
+ <title>Deleting Circulation Modifiers</title>\r
+ <step><para>Check the check box(es) next to the circulation modifiers(s) you wish to \r
+ delete.</para></step>\r
+ <step><para>Click <guibutton>Delete Selected</guibutton> near the top of the page.\r
+ <warning><para>The selected circulation modifiers will be deleted without a \r
+ verification alert.</para></warning>\r
+ </para></step>\r
+ </procedure>\r
+ <procedure>\r
+ <title>Editing Circulation Modifiers</title>\r
+ <step><para>Double click on the row of the cirlation modifier you wish to \r
+ edit.</para></step> \r
+ <step><para>Make desired changes.</para></step>\r
+ <step><para>Once you have finished editing, click \r
+ <guibutton>Save</guibutton>.</para></step> \r
+ </procedure>\r
+ </section>\r
+ <section xml:id="catalogingtemplates">\r
+ <title>Cataloging Templates</title>\r
+ <para>Cataloging templates are essential for making the cataloguing process more efficient. Templates are used that that the basic structure of specific types of cataloguing records can loaded when the cataloguer adds a new record</para>\r
+ <procedure>\r
+ <title>Adding Cataloging Templates</title>\r
+ <step>\r
+ <para> \r
+ Create a marc template in the directory <filename class="directory">/openils/var/templates/marc/</filename>. It should be in xml format.\r
+ Here is an example file <filename>k_video.xml</filename>: \r
+ </para>\r
+ <para>\r
+ <mediaobject xml:id="cattemplate">\r
+ <alt>Catalog Template Example</alt>\r
+ <imageobject>\r
+ <imagedata scalefit="0" fileref="../media/k_book_record.png"/>\r
+ </imageobject>\r
+ </mediaobject>\r
+ </para>\r
+ \r
+ </step>\r
+ <step>\r
+ <para>Add the template to the to the <emphasis>marctemplates</emphasis> list in the open-ils.cat section of the evergreen configuration file <filename>opensrf.xml</filename> </para>\r
+ </step>\r
+ <step>\r
+ <para>Restart perl services for changes to take effect.</para>\r
+ <screen>/openils/bin/osrf_ctl.sh -l -a restart_perl</screen>\r
+ </step>\r
+ </procedure>\r
+ </section>\r
+</chapter>\r
projects / Evergreen-DocBook.git / commitdiff
