</info>\r
<section xml:id="orgunitsandtypes">\r
<title>Organizational Unit Types and Organizational Units</title>\r
- <section xml:id="orgtypes">\r
+ <simplesect 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
<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
+ </simplesect>\r
\r
- <section xml:id="orgunits">\r
+ <simplesect 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
<step><para>Click <guibutton>Save</guibutton> to save your changes.</para></step>\r
</procedure>\r
\r
- </section>\r
- <section xml:id="server-hours">\r
+ </simplesect>\r
+ <simplesect xml:id="server-hours">\r
<info>\r
<title>Library Hours of Operation</title>\r
</info>\r
\r
</procedure>\r
\r
- </section>\r
+ </simplesect>\r
\r
\r
- <section xml:id="server-addresses">\r
+ <simplesect xml:id="server-addresses">\r
<info>\r
<title>Library Addresses</title>\r
</info>\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
+ linkend="server-main">previous simplesect</link>.</para>\r
</step>\r
<step>\r
<informalfigure>\r
correct addresses.</para>\r
</note>\r
\r
- </section>\r
+ </simplesect>\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
+ <para>This simplesect 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
</tip>\r
</abstract>\r
</info>\r
- <section>\r
+ <simplesect>\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
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
+ </simplesect>\r
+ <simplesect>\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
</tbody>\r
</tgroup>\r
</table>\r
- </section>\r
- <section>\r
+ </simplesect>\r
+ <simplesect>\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
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
+ </simplesect>\r
+ <simplesect>\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
<screen>WHERE id = 17;</screen>\r
</step>\r
</procedure> \r
- </section> \r
- </section>\r
- <section xml:id="grouppermissions">\r
+ </simplesect> \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
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
+ <simplesect>\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
+ <simplesect>\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
+ <para>The first simplesect of the User Permission Editor is the the Working Locations \r
+ simplesect. 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
+ </simplesect>\r
+ <simplesect>\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
+ </simplesect> \r
+ </simplesect>\r
+ <simplesect>\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
<step><para>Click <guibutton>Save Changes</guibutton> when you are finished all \r
the changes.</para></step>\r
</procedure>\r
- </section>\r
- <section>\r
+ </simplesect>\r
+ <simplesect>\r
<title>Permissions</title>\r
<table xml:id="permissiondescriptions">\r
<title>Permissions Table</title>\r
</tbody>\r
</tgroup>\r
</table> \r
- </section>\r
+ </simplesect>\r
</section>\r
<section>\r
<info>\r
</note>\r
\r
\r
- <section xml:id="staff_account_permissions">\r
+ <simplesect xml:id="staff_account_permissions">\r
<info>\r
<title>Staff Account Permissions</title>\r
</info>\r
</tbody>\r
</tgroup>\r
</informaltable>\r
- </section>\r
+ </simplesect>\r
\r
- <section xml:id="profiles-grant-permissions">\r
+ <simplesect 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
</para>\r
\r
</informalfigure>\r
- </step>\r
- \r
- </procedure>\r
-\r
- \r
- </section>\r
-</section>\r
+ </step> \r
+ </procedure>\r
+ \r
+ </simplesect>\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
<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>\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
\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
+ <para>Add the template to the to the <emphasis>marctemplates</emphasis> list in the open-ils.cat simplesect 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
</info> \r
<section xml:id="locatingrecords">\r
<title>Locating Records</title>\r
- <section xml:id="staffclientrecordsearch">\r
+ <simplesect xml:id="staffclientrecordsearch">\r
<title>Search</title>\r
<para>Search functionality may be functioned through:\r
<itemizedlist>\r
Use <emphasis>ocm</emphasis> as a prefix for OCLC numbers that are eight digits or shorter. Evergreen will automatically prefix the number with zeros so that it is nine digits. \r
(e.g. ocm01234567, or ocm00123456)\r
Do not use hyphens when searching by LCCN. Substitute a <emphasis>0</emphasis> in place of the hyphen. (e.g. 2001001234)</para></tip>\r
- </section>\r
- <section xml:id="MARCexpertsearch">\r
+ </simplesect>\r
+ <simplesect xml:id="MARCexpertsearch">\r
<title>MARC Expert Search</title>\r
<para>Located beneath the “Quick Search” box on the catalog search screen.</para>\r
<procedure>\r
</procedure>\r
<tip><para>To set default record views for a username, select <menuchoice><guimenu>Actions for this Record</guimenu> <guimenuitem>Set bottom interface as \r
Default</guimenuitem></menuchoice>.</para></tip>\r
- </section>\r
- <section xml:id="addingandeditingitems">\r
+ </simplesect>\r
+ <simplesect xml:id="addingandeditingitems">\r
<title>Adding and Editing Items</title>\r
- <section xml:id="adingholdingstotitlerecords">\r
+ <simplesect xml:id="adingholdingstotitlerecords">\r
<title>Adding Holdings to Title Rrcords</title> \r
<procedure>\r
<step><para>Retrieve an existing bibliographic record.</para></step>\r
</procedure>\r
<note><para>New items are assigned a status of In Process. Items must be checked in to become Available. Alternatively, use Edit Item Attributes from the Actions for Selected \r
Rows to change statuses to Available once records have been created and saved to database. The creation and use of item record templates is recommended. </para></note>\r
- </section>\r
- </section>\r
- <section xml:id="copyalertsandnotes">\r
+ </simplesect>\r
+ </simplesect>\r
+ <simplesect xml:id="copyalertsandnotes">\r
<title>Copy Alerts and Notes</title>\r
- <section xml:id="copyalerts">\r
+ <simplesect xml:id="copyalerts">\r
<title>Copy Alerts</title>\r
<para>Copy alerts are useful alerts for physical item copies.</para>\r
<para>Staff must be granted permission to override alerts at checkout or checkin.</para> \r
<step><para>Select all items to be changed by highlighting the first item in the list, holding down the <keycap>Shift</keycap> key, and clicking on the last item. Select several, non-sequential items, by holding down the <keycap>Ctrl</keycap> key and clicking on the required items.</para></step>\r
<step><para>Continue to <emphasis>Edit Item Attributes</emphasis>, as above.</para></step>\r
</procedure>\r
- </section>\r
- <section xml:id="viewingcopyalerts">\r
+ </simplesect>\r
+ <simplesect xml:id="viewingcopyalerts">\r
<title>Viewing Copy Alerts</title>\r
<para>Copy alerts may be viewed from the <emphasis>Item Status</emphasis> screen, at checkin, and at checkout.</para>\r
<para>To view alerts from the <emphasis>Item Status</emphasis>, enter the barcode number. Select the item and click <menuchoice><guimenu>Actions for Selected \r
<para>To view alerts from the Item Status, enter the barcode number. Select the item and click <menuchoice><guimenu>Actions for Selected Items</guimenu> \r
<guimenuitem>Show Item Details</guimenuitem></menuchoice>.</para>\r
<para>The copy alert will display automatically at checkout and checkin.</para>\r
- </section>\r
- <section xml:id="copynotes">\r
+ </simplesect>\r
+ <simplesect xml:id="copynotes">\r
<title>Copy Notes</title>\r
<para>Copy notes are informational only. They may be internal or made available to the public in the OPAC.</para> \r
<procedure>\r
<step><para>Click <guibutton>Add Note</guibutton> to display the new note.</para></step>\r
<step><para>Use the <guibutton>Delete This Note</guibutton> button to remove a note from a copy record.</para></step>\r
</procedure> \r
- </section>\r
- </section>\r
+ </simplesect>\r
+ </simplesect>\r
</section>\r
<section xml:id="addingnewbibliographicrecords">\r
<title>Adding New Bibliographic Records</title>\r
<para>Evergreen allows new bibliographic records to be added to the database through Z39.50 searching, MARC record file uploads, and original cataloging.</para> \r
- <section xml:id="ImportingMARCRecords-Z39">\r
+ <simplesect xml:id="ImportingMARCRecords-Z39">\r
<title>Importing MARC Records via the Z39.50 Interface</title>\r
<procedure>\r
<step><para><menuchoice><guimenu>Cataloging</guimenu> <guimenuitem>Import Record from Z39.50</guimenuitem></menuchoice></para></step>\r
<listitem>Export MARC records</listitem>\r
<listitem>Import or overlay MARC records</listitem>\r
</itemizedlist> \r
- </section> \r
- <section xml:id="importingrecords">\r
+ </simplesect> \r
+ <simplesect xml:id="importingrecords">\r
<title>Importing Records</title>\r
<procedure>\r
<step><para>Highlight the record and click <guibutton>MARC Editor for Import</guibutton>.</para></step>\r
</procedure>\r
<note><para>Select <guilabel>Fast Item Add</guilabel> to input the call number and barcode data from this screen. This box is \r
<emphasis>sticky</emphasis> for the login.</para></note>\r
- </section> \r
- <section xml:id="uploadingMARCfiles">\r
+ </simplesect> \r
+ <simplesect xml:id="uploadingMARCfiles">\r
<title>Uploading MARC files</title>\r
<para>Title records that do not already exist in the Evergreen database may be uploaded directly to the catalog through vendor-supplied MARC files. Multiple title records \r
can be uploaded and added at the same time.</para>\r
are not true matches, it is still possible to upload the selected records using the <guimenu>Actions</guimenu> drop-down menu.</para></step>\r
<note><para>The <guimenuitem>Import Attached Holdings</guimenuitem> option requires additional server configuration.</para></note>\r
</procedure>\r
- </section> \r
- <section xml:id="creatingnewMARCrecords">\r
+ </simplesect> \r
+ <simplesect xml:id="creatingnewMARCrecords">\r
<title>Creating New MARC Records</title>\r
<para>New MARC records may be created in Evergreen using MARC templates. For detailed information on MARC standards, visit the Library of Congress website: \r
<ulink url='http://www.loc.gov/marc/'>http://www.loc.gov/marc/</ulink></para>\r
<step><para>The record is created and will open in the current default view. Holdings may now be added.</para></step>\r
<note><para>If the <guilabel>Fast Item Add</guilabel> box was selected, the copy editor will open after <guibutton>Create Record</guibutton> is clicked.</para></note>\r
</procedure>\r
- </section>\r
+ </simplesect>\r
</section>\r
<section xml:id="MARCeditor">\r
<title>Working with the MARC Editor</title>\r
<para>The MARC Editor allows MARC tags, sub-fields, and indicators to be edited.</para> \r
<para>OPAC icons for text, moving pictures and sound rely on correct MARC coding in the leader and the 008, as do OPAC search filters such as publication date, item type, or \r
target audience. Bibliographic matching and de-duplicating also rely on correct MARC coding and consistency in use and content in particular MARC tags.</para> \r
- <section xml:id="editingMARCrecords">\r
+ <simplesect xml:id="editingMARCrecords">\r
<title>Editing MARC Records</title>\r
<procedure>\r
<step><para>Retrieve the record.</para></step>\r
<step><para>Click <guibutton>OK</guibutton>.</para></step> \r
</procedure>\r
<tip><para>The MARC Editor may be navigated using keyboard shortcuts. Click <guibutton>Help</guibutton> to see the shortcut menu from within the MARC Editor.</para></tip>\r
- </section> \r
- <section xml:id="MARCrecordleader">\r
+ </simplesect> \r
+ <simplesect xml:id="MARCrecordleader">\r
<title>MARC Record Leader and MARC fixed field 008</title>\r
<para>Parts of the leader and the 008 field can be edited in the MARC Editor via the fixed field editor box displayed above the MARC record. Information about the leader and \r
the 008 can be found on the Library of Congress’s MARC Standards page at <ulink url='http://www.loc.gov/marc/'>http://www.loc.gov/marc/</ulink>.</para>\r
<step><para>The OPAC icon for the appropriate material type will display.</para></step> \r
</procedure>\r
<tip><para>The MARC Editor may be navigated using keyboard shortcuts. Click <guibutton>Help</guibutton> to see the shortcut menu from within the MARC Editor.</para></tip>\r
- </section> \r
- <section xml:id="overlayingMARCrecords">\r
+ </simplesect> \r
+ <simplesect xml:id="overlayingMARCrecords">\r
<title>Overlaying MARC Records</title>\r
<para>Overlaying a MARC record replaces an existing MARC record while leaving all holdings, holds, active circulations, bills, and fines intact.</para>\r
<para>In Evergreen, a record must be <emphasis>marked</emphasis> for overlay. The mark for overlay is by login. Only one record at a time may be marked for overlay. When another \r
<step><para>Click <guibutton>Overlay</guibutton>.</para></step>\r
<step><para>Confirm the overlay. The record in Evergreen is overlaid with the new MARC record. All preexisting holdings remain intact.</para></step>\r
</procedure>\r
- </section>\r
+ </simplesect>\r
</section>\r
<section xml:id="cattemplates">\r
<title>Cataloging Templates</title>\r
- <para>This section explains creating, using, exporting, and importing item record templates for cataloging. Use of templates enhances item creation and helps ensure \r
+ <para>This simplesect explains creating, using, exporting, and importing item record templates for cataloging. Use of templates enhances item creation and helps ensure \r
consistency in record format in the database.</para> \r
\r
<procedure>\r
displayed data.</listitem>\r
</itemizedlist>\r
</tip>\r
- <section xml:id="addingcopyrecordscopybuckets">\r
+ <simplesect xml:id="addingcopyrecordscopybuckets">\r
<title>Adding Copy Records to Copy Buckets</title>\r
<para>While creating copy buckets is similar to creating record buckets (simply choose Copy Buckets in the menu choice), there are significant differences in adding copy \r
records to a bucket. Records must be added to copy buckets from the copy record level. This may be done from several locations within the Evergreen client.</para> \r
<step><para>Use <guibutton>Add All</guibutton> or select the appropriate items and <guibutton>Add Selected</guibutton> to move items to the bucket displayed in the \r
bottom pane.</para></step> \r
</procedure>\r
- </section>\r
- <section xml:id="WorkingwithRecordsinaBucket">\r
+ </simplesect>\r
+ <simplesect xml:id="WorkingwithRecordsinaBucket">\r
<title>Working with Records in a Bucket</title>\r
<para>Once records have been placed in a bucket, a variety of functions may be performed. </para> \r
\r
<step><para>Enter the desired bucket number and click <guibutton>OK</guibutton>.</para></step>\r
<step><para>The requested bucket now displays. The bucket number (assigned by Evergreen) and owner displays.</para></step>\r
</procedure>\r
- </section>\r
+ </simplesect>\r
</section>\r
<section xml:id="MergingBibliographicRecords">\r
<title>Merging Bibliographic Records</title>\r
<title>Batch deletions:</title>\r
<step><para>Create a copy bucket for the items to be deleted (<menuchoice><guimenu>Cataloging</guimenu> <guimenuitem>Manage Copy Buckets</guimenuitem>\r
</menuchoice>; create a New Bucket</para></step> \r
- <step><para>Enter the barcodes for the to-be-deleted items into the Pending Copies section of the Copy Buckets screen.</para></step> \r
+ <step><para>Enter the barcodes for the to-be-deleted items into the Pending Copies simplesect of the Copy Buckets screen.</para></step> \r
<step><para>Add All of the items to the selected bucket.</para></step> \r
<step><para>Delete All from Catalog.</para></step>\r
<step><para>The Deleted? status for each item will change from <emphasis>No</emphasis> to <emphasis>Yes</emphasis>.</para></step> \r
</info> \r
<section xml:id="patronrecords">\r
<title>Patron Records</title>\r
- <section xml:id="searchingpatrons">\r
+ <simplesect xml:id="searchingpatrons">\r
<title>Searching Patrons</title>\r
\r
<itemizedlist>\r
<listitem>Limit results to patrons in dropdown.</listitem>\r
</itemizedlist>\r
\r
- </section>\r
- <section xml:id="Registeringpatrons">\r
+ </simplesect>\r
+ <simplesect xml:id="Registeringpatrons">\r
<title>Registering New Patrons</title>\r
\r
<itemizedlist>\r
are automatically grouped together with the original record and share the same address, which can only be edited in the original record.</listitem>\r
<listitem>Staff accounts can be added here just like patron accounts.</listitem>\r
</itemizedlist>\r
- </section>\r
- <section xml:id="CloneUser">\r
+ </simplesect>\r
+ <simplesect xml:id="CloneUser">\r
<title>Clone User from Existing Group Member</title>\r
<procedure>\r
<step><para>Open patron record, click <guibutton>Other</guibutton>.</para></step>\r
<step><para>After saving the clone record, the User Editor reverts to another clone template; create additional family/group member records.</para></step>\r
<step><para>Close the <emphasis>Register Patron Clone for Group</emphasis> tab.</para></step>\r
</procedure>\r
- </section>\r
- <section xml:id="Updatingpatroninformation">\r
+ </simplesect>\r
+ <simplesect xml:id="Updatingpatroninformation">\r
<title>Updating patron information</title>\r
<procedure>\r
<step><para>Retrieve the patron record</para></step>\r
<step><para>Finish then click <guibutton>Save User</guibutton>.</para></step>\r
<step><para>Confirmation message, <emphasis>User updating is successful</emphasis></para></step>\r
</procedure>\r
- </section>\r
- <section xml:id="renewinglibrarycards">\r
+ </simplesect>\r
+ <simplesect xml:id="renewinglibrarycards">\r
<title>Extend Account Expiration Date</title>\r
<para>All patron accounts are set to <emphasis>expire</emphasis> in one year – this allows staff to verify patron contact information annually and update any out-of-date \r
information.</para>\r
<step><para>At Account Expiration Date, highlight the year and type the new year</para></step>\r
<step><para>Click <guimenuitem>7. Finish</guimenuitem>, click <guibutton>Save User</guibutton></para></step>\r
</procedure>\r
- </section>\r
- <section xml:id="lostlibrarycards">\r
+ </simplesect>\r
+ <simplesect xml:id="lostlibrarycards">\r
<title>Lost Library Cards</title>\r
<procedure>\r
<step><para>Retrieve the patron record.</para></step>\r
<para>A lost card cannot be reinstated (A warning message will display; use the new card to retrieve the user’s \r
record)</para>\r
</caution> \r
- </section>\r
- <section xml:id="Resettingpatronpassword">\r
+ </simplesect>\r
+ <simplesect xml:id="Resettingpatronpassword">\r
<title>Resetting a Patron's Password</title>\r
<procedure>\r
<step><para>Retrieve the record.</para></step>\r
<note>\r
<para>The existing password is not displayed in patron records for security reasons.</para>\r
</note> \r
- </section>\r
- <section xml:id="barringapatron">\r
+ </simplesect>\r
+ <simplesect xml:id="barringapatron">\r
<title>Barring a Patron</title>\r
<procedure>\r
<step><para>Select <guimenuitem>4: Groups and Permissions</guimenuitem>. Select the <guilabel>Barred</guilabel> checkbox.</para></step>\r
the OPAC to view their accounts.</para>\r
<para>Blocked: Often, these are system-generated blocks on patron accounts. Some examples:\r
<itemizedlist>\r
- <listitem>Patron exceeds fine threshold</listitem>\r
+ <listitem>Patron exceeds fine threshold</listitem>\r
<listitem>Patron exceeds max checked out item threshold.</listitem>\r
</itemizedlist> \r
</para>\r
<para>A notice appears when a staff person tries to checkout an item to blocked patrons, but staff may be given permissions \r
to override blocks.</para>\r
- </section>\r
- <section xml:id="patronalerts">\r
+ </simplesect>\r
+ <simplesect xml:id="patronalerts">\r
<title>Patron Alerts</title>\r
<para>There are two types of Patron Alerts:\r
<itemizedlist>\r
</para>\r
<para>A notice appears when a staff person tries to checkout an item to blocked patrons, but staff may be given permissions \r
to override blocks.</para>\r
- </section>\r
- <section xml:id="patronnotes">\r
+ </simplesect>\r
+ <simplesect xml:id="patronnotes">\r
<title>Patron Notes</title>\r
<para>See Notes message appears</para>\r
<para>Notes are strictly communicative and may made visible to the patron, via their account on the OPAC.</para>\r
<step><para>To delete a note, go to <menuchoice><guimenu>Other</guimenu> <guimenuitem>Notes</guimenuitem></menuchoice> and use the \r
<guibutton>Delete This Note</guibutton> button under each note.</para></step>\r
</procedure> \r
- </section>\r
- <section xml:id="mergingpatronrecords">\r
+ </simplesect>\r
+ <simplesect xml:id="mergingpatronrecords">\r
<title>Merging Patron Records</title>\r
<procedure>\r
<title>Merging patron Records From the patron search screen:</title> \r
<note><para>The merged record will still show under group members. Both members point to the same patron \r
record.</para></note>\r
</procedure>\r
- </section>\r
+ </simplesect>\r
</section>\r
<section xml:id="circulatingitems">\r
<title>Circulating Items</title>\r
<para>Pre-cataloged circulation: circulation of items that have a barcode but have not yet been cataloged. These items \r
may be checked out and then sent to cataloging when returned.</para>\r
<para>Non-cataloged circulation: circulation of items that are not in the catalog and do not have a barcode.</para> \r
- <section xml:id="checkout">\r
+ <simplesect xml:id="checkout">\r
<title>Check Out (<keycap>F1</keycap>)</title>\r
\r
<procedure>\r
<step><para>When finished, click <guibutton>Done</guibutton> to generate a receipt or to exit patron record, if not printing slip receipts. \r
</para></step>\r
</procedure>\r
- </section>\r
- <section xml:id="Precatalogeditems">\r
+ </simplesect>\r
+ <simplesect xml:id="Precatalogeditems">\r
<title>Pre-cataloged Items</title>\r
<para>Pre-cat items are those items that have yet to be added to the database or that have barcode labels, but are not attached to an existing bibliographic record.</para>\r
<caution><para>ONLY use Pre-Cat Checkout as a last resort, such as when a patron brings the item to the desk from the shelf and MUST have it that day. Otherwise, \r
<note><para>The item MUST be routed to your holdings maintenance staff to be added to the database before further \r
check outs.</para></note> \r
</procedure>\r
- </section>\r
- <section xml:id="noncatalogeditems">\r
+ </simplesect>\r
+ <simplesect xml:id="noncatalogeditems">\r
<title>Non-cataloged Items</title>\r
<para>Non-cataloged items may be more familiar as <emphasis>Ephemeral</emphasis> items – they are those items that libraries do not wish to catalog, \r
but do wish to track for circulation statistics.</para> \r
</procedure>\r
<para>Non-cataloged items do not appear in the list of items out unless you select that option.</para>\r
<para>Click OK.</para>\r
- </section>\r
- <section xml:id="duedates">\r
+ </simplesect>\r
+ <simplesect xml:id="duedates">\r
<title>Due Dates</title>\r
<para>Circulation periods are pre-set. When items are checked out, due dates are automatically calculated and \r
inserted into circulation records if the Due Date is set Normal on the Check Out screen. Different due dates \r
<step><para>The item is checked out with the special due date.</para></step> \r
<step><para>The special due date applies to all subsequent items until it is changed or the patron record is exited.</para></step>\r
</procedure>\r
- </section>\r
- <section xml:id="checkin">\r
- <title>Check In (F2)</title>\r
+ </simplesect>\r
+ <simplesect xml:id="checkin">\r
+ <title>Check In (<keycap>F2</keycap>)</title>\r
<procedure>\r
<title>Regular check in:</title> \r
<step><para>Click <guibutton>Check In</guibutton> button or hit <keycap>F2</keycap> to open Item Check In tab.\r
<step><para>Continue to scan barcodes until all items are discharged.</para></step>\r
<step><para>Close tab when done.</para></step>\r
</procedure>\r
- </section>\r
- <section xml:id="backdatedcheckin">\r
+ </simplesect>\r
+ <simplesect xml:id="backdatedcheckin">\r
<title>Backdated Check In</title>\r
<para>Used for checking items in from bookdrops or for unexpected closings.</para>\r
<procedure>\r
<step><para>When finishing backdated check-in, change the Effective Date back to the current \r
date or close tab.</para></step> \r
</procedure>\r
- </section>\r
- <section xml:id="Renewaleditingduedate">\r
+ </simplesect>\r
+ <simplesect xml:id="Renewaleditingduedate">\r
<title>Renewal and Editing Item's Due Date</title>\r
<para>Checked-out items can be renewed according to library policy. The new due date is calculated from the renewal \r
date. Existing loans may be extended to a specific date by editing the due date.</para>\r
</procedure>\r
<tip><para>Select multiple items by pressing down the <keycap>CTRL</keycap> key and clicking each item to edit.</para></tip>\r
<note><para>Editing the due date does not affect renewal count.</para></note>\r
- </section>\r
- <section xml:id="lostclaimedreturned">\r
- <title>Marking Items “Lost” and “Claimed Returned”</title>\r
+ </simplesect>\r
+ <simplesect xml:id="lostclaimedreturned">\r
+ <title>Marking Items <emphasis>Lost</emphasis> and <emphasis>Claimed Returned</emphasis></title>\r
<procedure>\r
<title>To mark items as lost:</title>\r
<step><para>Retrieve the patron record.</para></step> \r
<para>There is a <guibutton>Claims Returned Count</guibutton> in the Edit tab, <guimenuitem>Groups and Permissions</guimenuitem> section; this must be manually reset.</para>\r
<para>There are no alerts indicating claims returned items.</para>\r
</note>\r
- </section>\r
- <section xml:id="inhouseuse">\r
- <title>In-house Use (F6)</title>\r
+ </simplesect>\r
+ <simplesect xml:id="inhouseuse">\r
+ <title>In-house Use (<keycap>F6</keycap>)</title>\r
<para>May be used to record in-house use for both cataloged and non-cataloged items.</para>\r
\r
<procedure>\r
</procedure>\r
<para>The statistics on in-house use are separated from circulation statistics. In-house use count \r
of cataloged items is not included in the items' total use count.</para>\r
- </section>\r
- <section xml:id="itemstatus">\r
+ </simplesect>\r
+ <simplesect xml:id="itemstatus">\r
<title>Item Status (<keycap>F5</keycap>)</title>\r
<para>Many functions may be performed from the Item Status screen. This section will cover circulation-related functions:\r
checking item status, viewing past circulations, inserting item alert messages, and marking items missing or damaged.\r
<step><para>Patron record will display in a new Tab.</para></step>\r
</procedure>\r
<para>Past circulations can also be retrieved from a patron's Items Out screen.</para> \r
- </section>\r
- <section xml:id="markingitemsdamaged">\r
+ </simplesect>\r
+ <simplesect xml:id="markingitemsdamaged">\r
<title>Marking items <emphasis>damaged</emphasis> or <emphasis>missing</emphasis></title> \r
<procedure>\r
<step><para>Retrieve the item.</para></step> \r
</procedure>\r
<para>This procedure also allows items to be checked in or renewed through the <guimenuitem>Check in Items</guimenuitem> and <guimenuitem>Renew Items</guimenuitem> options on the \r
dropdown menu.</para> \r
- </section>\r
- <section xml:id="itemalerts">\r
+ </simplesect>\r
+ <simplesect xml:id="itemalerts">\r
<title>Item alerts</title>\r
<para>The Edit Item Attributes function on Actions for Selected Items allows editing of item records, such as inserting \r
item alerts.</para>\r
<step><para>Type in the message and click <guibutton>Apply</guibutton>.</para></step>\r
<step><para>Click <guibutton>Modify Copies</guibutton> and confirm.</para></step> \r
</procedure>\r
- </section>\r
+ </simplesect>\r
</section>\r
<section xml:id="billsandpayments">\r
<title>Bills and Payments</title>\r
- <section xml:id="circulationgrocerybills">\r
+ <simplesect xml:id="circulationgrocerybills">\r
<title>Circulation vs. Grocery Bills</title>\r
<para>There are two types of bills in Evergreen: Circulation bills and Grocery bills. </para>\r
<para>Circulation bills: system-generated (overdue fines, lost item cost, processing fees, etc.).</para>\r
<para>Overdue fines are added daily once an item is overdue. </para>\r
<para>When an item is marked as lost, bills may be automatically generated to cover the item's cost and a processing fee, according to library policy.</para>\r
<para>Grocery bills: staff-applied to patron accounts.</para> \r
- </section> \r
- <section xml:id="makingpayments">\r
+ </simplesect> \r
+ <simplesect xml:id="makingpayments">\r
<title>Making Payments</title> \r
<procedure>\r
<step><para>Retrieve the patron record.</para></step> \r
</procedure>\r
<note><para>Items marked with red are still checked out. It is possible for a patron to pay a bill while the item is still out and accruing fines.</para></note>\r
<tip><para>You may choose to annotate payment and fill in resulting text box according to library policy.</para></tip>\r
- </section>\r
- <section xml:id="makingchange">\r
+ </simplesect>\r
+ <simplesect xml:id="makingchange">\r
<title>Making Change</title> \r
<para>Change will be calculated if the payment amount is over the selected bill amount. After typing in a payment amount, click into the \r
<guilabel>=Change</guilabel> field. The change amount will\r
display. </para>\r
- </section>\r
- <section xml:id="voidforgive">\r
+ </simplesect>\r
+ <simplesect xml:id="voidforgive">\r
<title>Void vs. Forgive</title> \r
<para>Void clears all history of the bill, while forgive retains the history.</para> \r
<procedure>\r
<step><para>Apply Payment.</para></step> \r
</procedure>\r
\r
- <section xml:id="voidbills">\r
+ <simplesect xml:id="voidbills">\r
<para>Voiding bills:</para>\r
<para>Bills under one transaction are grouped in one bill line. Bills may be voided in part or in whole.</para> \r
<procedure> \r
<step><para>Void Selected Billings.</para></step> \r
<step><para>Confirm.</para></step> \r
</procedure> \r
- </section>\r
- </section>\r
- <section xml:id="newgrocerybills">\r
- <title>Adding New "Grocery" Bills</title>\r
+ </simplesect>\r
+ </simplesect>\r
+ <simplesect xml:id="newgrocerybills">\r
+ <title>Adding New Grocery Bills</title>\r
<para>A grocery bill can be added as a new bill or to an existing bill.</para> \r
<procedure> \r
<title>To add as a new bill:</title>\r
<step><para>Submit this Bill and confirm.</para></step> \r
<step><para>The Money Summary will adjust accordingly.</para></step> \r
</procedure> \r
- </section>\r
- <section xml:id="billhistory">\r
+ </simplesect>\r
+ <simplesect xml:id="billhistory">\r
<title>Bill History</title>\r
<para>The Bill History view includes specific details about the item as well as information about the \r
bill and payments.</para> \r
</procedure> \r
<note><para>Items may be deleted from the catalog even if a charge for that item is still attached to the patron's record. The charge will remain on the patron's account \r
after the deletion.</para></note>\r
- </section>\r
- <section xml:id="bills-refund">\r
+ </simplesect>\r
+ <simplesect xml:id="bills-refund">\r
<info><title>Refund</title></info>\r
<para>Sometimes paid bills need to be voided, such as when lost and paid items are returned. A negative balance may be \r
created once such bills are voided. To close such bills, staff may refund the balance amount or add a bill entry.</para>\r
</procedure>\r
<tip><para><guilabel>Refund</guilabel> button will automatically show up once a bill has a negative balance.</para>\r
<para>Refunds are reflected in the Cash Report.</para></tip>\r
- </section> \r
+ </simplesect> \r
</section>\r
<section xml:id="Holds">\r
<title>Holds</title>\r
<note><para>Items may be deleted from the catalog even if a charge for that item is still attached to the patron's record. The charge will remain on the patron's account \r
after the deletion.</para></note>\r
- <section xml:id="ViewingHolds">\r
+ <simplesect xml:id="ViewingHolds">\r
<title>Viewing Holds</title>\r
<procedure>\r
<step><para>Under Actions for this Record (<keycombo><keycap>Alt</keycap><keycap>A</keycap></keycombo>), select View Holds \r
Holdings Maintenance.</para></step> \r
<step><para>The View Holds screen opens.</para></step>\r
</procedure> \r
- </section> \r
- <section xml:id="placingholds">\r
+ </simplesect> \r
+ <simplesect xml:id="placingholds">\r
<title>Placing Holds</title>\r
<para>Holds may be placed by staff through the staff client or by patrons through the OPAC. This chapter explains placing holds through the client which can be placed for \r
from several different places.</para> \r
- </section>\r
- <section xml:id="holdslevels">\r
+ </simplesect>\r
+ <simplesect xml:id="holdslevels">\r
<title>Holds Levels</title>\r
<para>Evergreen has four hold levels. Library staff may place holds at all four levels, while patrons may only place Meta-record and Title-level holds.</para> \r
<table xml:id="holdslevelstable">\r
reflect newly placed holds.</para>\r
<para>If the hold fails, a dialog box will open up indicating that the hold you are trying to place is invalid. For instance, if you try to place a hold on an audiovisual \r
item where your library has no holdings, or if the patron has reached the limit of holds a person can place.</para>\r
- </section>\r
- <section xml:id="managingholds">\r
+ </simplesect>\r
+ <simplesect xml:id="managingholds">\r
<title>Managing Holds</title>\r
<para>Holds may be cancelled at any time by staff or patrons.</para> \r
<para>Before holds are captured, staff or patrons may: \r
</procedure> \r
<tip><para>Holds may be sorted on the View Holds screen. Click <guimenuitem>Request Date</guimenuitem> to find the position of a patron in the hold queue. Use the column \r
picker to display patron barcodes and names. Columns may be saved for a login using the <guibutton>Save Columns</guibutton> button.</para></tip> \r
- </section> \r
- <section xml:id="TransferringHolds">\r
+ </simplesect> \r
+ <simplesect xml:id="TransferringHolds">\r
<title>Transferring Holds</title>\r
<procedure>\r
<step><para>Open the record you need to transfer the hold from in one tab and the record you need to transfer the hold to in another tab.</para></step> \r
<step><para>Go to the tab where you have opened the record where you need to move the hold.</para></step> \r
<step><para>Then you will need to cancel the hold on the first record.</para></step> \r
</procedure> \r
- </section> \r
- <section xml:id="CancelingHolds">\r
+ </simplesect> \r
+ <simplesect xml:id="CancelingHolds">\r
<title>Canceling Holds</title>\r
<procedure>\r
<step><para>View the holds for the item.</para></step> \r
<step><para>If it is the correct hold, click <guibutton>Yes</guibutton> (<keycombo><keycap>Alt</keycap><keycap>Y</keycap></keycombo>).</para></step>\r
<step><para>The window will close, and the hold will disappear from the list.</para></step>\r
</procedure> \r
- </section>\r
- <section xml:id="RetargetingHolds">\r
+ </simplesect>\r
+ <simplesect xml:id="RetargetingHolds">\r
<title>Retargeting Holds</title>\r
<para>Holds need to be retargeted whenever a new item is added to a record, or after some types of item status changes, for instance when an item is changed from On Order \r
to In Process. The system does not automatically recognize the newly added items as available to fill holds. This also needs to be done if items marked as Damaged or \r
<step><para>When the screen refreshes, the holds will be retargeted the system will now recognize the new items and items with a new status as \r
available for holds.</para></step>\r
</procedure> \r
- </section>\r
- <section xml:id="holdspulllist">\r
+ </simplesect>\r
+ <simplesect xml:id="holdspulllist">\r
<title>Holds Pull List</title>\r
<para>Holds may have one of three statuses: <emphasis>Waiting for Copy</emphasis>, <emphasis>Waiting for Capture</emphasis>, or \r
<emphasis>Ready for Pickup</emphasis>.</para> \r
</procedure> \r
<note><para>The Holds Pull List is updated constantly. Once an item on the list is no longer available or a hold on the list is captured, the items will disappear \r
from the list. </para></note>\r
- <section xml:id="capturingholds">\r
+ <simplesect xml:id="capturingholds">\r
<title>Capturing Holds</title>\r
<para>Holds may be captured when a checked-out item is returned (checked in) or when an item on the Holds Pull List is retrieved and captured. When a hold is captured, a \r
hold slip may be printed and an email notification will be sent out, if enabled for the hold.</para> \r
</procedure> \r
<tip><para> Holds can also be captured on the <menuchoice><guimenu>Circulation</guimenu> <guimenuitem>Check In Items</guimenuitem></menuchoice> screen. \r
If the <guilabel>Auto-Print Hold</guilabel> and <guilabel>Transit Slips</guilabel> checkboxes are selected, hold slips will print automatically.</para></tip> \r
- </section>\r
- </section> \r
- <section xml:id="holdsshelflist">\r
+ </simplesect>\r
+ </simplesect> \r
+ <simplesect xml:id="holdsshelflist">\r
<title>Holds Shelf List</title>\r
<para>Items with Ready-for-pickup status are displayed on the Hold Shelf List. Hold Shelf List can help manage items on the hold shelf.</para> \r
<para>To view the holds shelf list:</para>\r
<step><para>Expired holds may be deleted from this screen.</para></step> \r
</procedure> \r
<caution><para>If you cancel a ready-for-pickup hold, you must check in the item to make it available for circulation.</para></caution>\r
- </section>\r
+ </simplesect>\r
</section>\r
<section xml:id="transititems">\r
<title>Transit Items</title>\r
<emphasis>In Transit</emphasis>. If the hold is captured from the <emphasis>Check In</emphasis> screen, a prompt to print the Transit/Hold slip will display. \r
If the hold is captured from the <emphasis>Capture Holds</emphasis> screen, a Transit/Hold slip will be printed automatically.</listitem>\r
</orderedlist>\r
- <section xml:id="receivingtransititems">\r
+ <simplesect xml:id="receivingtransititems">\r
<title>Receiving In Transit Items</title>\r
<para>All items received through transit must be checked in by the receiving branch. This changes the items' statuses from <emphasis>In Transit</emphasis> to \r
<emphasis>Reshelving</emphasis> or <emphasis>Ready for Pickup</emphasis>.</para> \r
- </section>\r
- <section xml:id="transitlist">\r
+ </simplesect>\r
+ <simplesect xml:id="transitlist">\r
<title>Transit List</title>\r
<para>The Transit List report may be used to as a tool to help manage your incoming and outgoing transits.</para>\r
<para>To access and use the Transit List report:</para>\r
<step><para>Click <guibutton>Transits Retrieve</guibutton>.</para></step> \r
<step><para>Items with an <emphasis>In Transit</emphasis> status for the selected time period are listed. </para></step>\r
</procedure> \r
- </section>\r
- <section xml:id="abortingtransits">\r
+ </simplesect>\r
+ <simplesect xml:id="abortingtransits">\r
<title>Aborting Transits</title>\r
<para>Transits may be aborted (cancelled) from multiple locations within Evergreen.</para>\r
<para>Use when processing missing in transit items or a patron requests an item that has just been returned and is in transit to its home library for reshelving. \r
<step><para>The transit is cancelled, but will still display in the list. </para></step> \r
<step><para>Click <guibutton>Retrieve Transits</guibutton>. The screen will refresh and the cancelled item(s) will no longer display as transits. </para></step> \r
</procedure> \r
- <section xml:id="cancellingtransitscheckout">\r
+ <simplesect xml:id="cancellingtransitscheckout">\r
<title>Cancelling Transits at Checkout</title>\r
<para>Items with a status of <emphasis>in transit</emphasis> trigger a notification when an attempt is made to check them out. To allow <emphasis>in transit</emphasis> \r
items to be checked out, override the block by clicking Abort Transit on the alert screen. Proceed by clicking <guibutton>Checkout</guibutton>.</para> \r
\r
- </section>\r
- <section xml:id="cancellingtransitsItemStatus">\r
+ </simplesect>\r
+ <simplesect xml:id="cancellingtransitsItemStatus">\r
<title>Cancelling Transits from Item Status</title>\r
<para>Items with a status of <emphasis>in transit</emphasis> trigger a notification when an attempt is made to check them out. To allow \r
<emphasis>in transit</emphasis> items to be checked out, override the block by clicking Abort Transit on the alert screen. Proceed by clicking Checkout.</para> \r
<step><para>At Aborting Transits pop-up, click <guibutton>Yes</guibutton></para></step> \r
<step><para>The item now has the status <emphasis>Reshelving</emphasis>.</para></step> \r
</procedure> \r
- </section>\r
- </section>\r
+ </simplesect>\r
+ </simplesect>\r
</section>\r
<section xml:id="offlinetransactions">\r
<title>Offline Transactions</title>\r
</para>\r
</informalfigure>\r
\r
- <section>\r
+ <simplesect>\r
<info>\r
<title>Patron Registration</title>\r
</info>\r
</mediaobject></para>\r
</informalfigure>\r
</step>\r
-\r
-\r
-\r
<step>\r
<informalfigure>\r
<para>Fill in the form with patron information. Use the drop down list if available.\r
<imagedata scalefit="0" fileref="../media/offline-26.png"/>\r
</imageobject>\r
</mediaobject></para>\r
-\r
</informalfigure>\r
-\r
</step>\r
-\r
-\r
-\r
-\r
-\r
</procedure>\r
-\r
- </section>\r
-\r
- <section xml:id="offline-check-out">\r
+ </simplesect>\r
+ <simplesect xml:id="offline-check-out">\r
<info>\r
<title>Check Out</title>\r
</info>\r
-\r
<procedure>\r
<step>\r
<informalfigure>\r
</mediaobject></para>\r
</informalfigure>\r
</step>\r
-\r
<step>\r
<informalfigure>\r
<para>The Standalone Check Out screen will open.</para>\r
</mediaobject></para>\r
</informalfigure>\r
</step>\r
-\r
<step>\r
<para>Make sure the date (on the left end of the menu bar) is correct.</para>\r
</step>\r
-\r
<step>\r
<informalfigure>\r
<para>Scan the patron's library card barcode in <guilabel>Enter the patron's\r
</mediaobject></para>\r
</informalfigure>\r
</step>\r
-\r
-\r
<step>\r
<informalfigure>\r
<para>Check that the due date is correct. You may delete then type in a due date in\r
</mediaobject></para>\r
</informalfigure>\r
</step>\r
-\r
-\r
<step>\r
<informalfigure>\r
<para>Scan the items' bacode in <guilabel>Enter the item barcode</guilabel> box. It\r
will appear on the right side of the screen. </para>\r
-\r
-\r
<para><mediaobject>\r
<imageobject>\r
<imagedata scalefit="0" fileref="../media/offline-7.png"/>\r
</mediaobject>\r
</para>\r
</informalfigure>\r
-\r
<informalfigure>\r
<para>Enter the number of items you want to check out, then click\r
<guibutton>OK</guibutton> on the prompt window.</para>\r
<imagedata scalefit="0" fileref="../media/offline-9.png"/>\r
</imageobject>\r
</mediaobject></para>\r
-\r
</informalfigure>\r
</step>\r
-\r
<step>\r
<para>Scan all items, changing the due date if necessary.</para>\r
</step>\r
-\r
<step>\r
<informalfigure>\r
<para>If you want to print receipt, make sure <guilabel>Print receipt?</guilabel>\r
<imagedata scalefit="0" fileref="../media/offline-10.png"/>\r
</imageobject>\r
</mediaobject></para>\r
-\r
</informalfigure>\r
</step>\r
-\r
<step>\r
<informalfigure>\r
<para>Click <guibutton>Save these transactions</guibutton>.</para>\r
<imagedata scalefit="0" fileref="../media/offline-11.png"/>\r
</imageobject>\r
</mediaobject></para>\r
-\r
-\r
</informalfigure>\r
</step>\r
</procedure>\r
happens to be used, it will be checked out with the previous author and title. If a new pre-cat barcode is attempted, \r
an error of ASSET NOT FOUND (item not found) will be returned upon processing offline transactions.</para>\r
</tip>\r
- </section>\r
-\r
- <section>\r
+ </simplesect>\r
+ <simplesect>\r
<info>\r
<title>Renew</title>\r
</info>\r
<para>To renew, you must know items barcode number. Patron's barcode is optional.</para>\r
<procedure>\r
-\r
<step>\r
-\r
<informalfigure>\r
<para>To access renew function, click <guibutton>Renew</guibutton> button on the top\r
menu bar.</para>\r
-\r
<para><mediaobject>\r
<imageobject>\r
<imagedata scalefit="0" fileref="../media/offline-12.png"/>\r
</imageobject>\r
</mediaobject></para>\r
</informalfigure>\r
-\r
</step>\r
<step>\r
<informalfigure>\r
<imagedata scalefit="0" fileref="../media/offline-13.png"/>\r
</imageobject>\r
</mediaobject></para>\r
-\r
</informalfigure>\r
</step>\r
-\r
<step>\r
<para>Follow the same procedure as checking out described above. Skip patron barcode if\r
you do not have it.</para>\r
</step>\r
-\r
-\r
</procedure>\r
- </section>\r
- <section>\r
+ </simplesect>\r
+ <simplesect>\r
<info>\r
<title>In House Use</title>\r
</info>\r
</mediaobject></para>\r
</informalfigure>\r
</step>\r
-\r
<step>\r
<informalfigure>\r
<para>Make sure the date is correct.</para>\r
</mediaobject></para>\r
</informalfigure>\r
</step>\r
-\r
<step>\r
<informalfigure>\r
<para>Type in the number in <guilabel>Enter the number of uses of the item</guilabel>\r
</imageobject>\r
</mediaobject></para>\r
</informalfigure>\r
-\r
</step>\r
-\r
<step>\r
<informalfigure>\r
<para>Scan or type in the item barcode number in <guilabel>Enter the item\r
<imagedata scalefit="0" fileref="../media/offline-17.png"/>\r
</imageobject>\r
</mediaobject></para>\r
-\r
</informalfigure>\r
</step>\r
-\r
<step>\r
<para>Repeat the above 2 steps until all items have been scanned.</para>\r
</step>\r
<imagedata scalefit="0" fileref="../media/offline-18.png"/>\r
</imageobject>\r
</mediaobject></para>\r
-\r
</informalfigure>\r
</step>\r
</procedure>\r
-\r
- </section>\r
- <section>\r
+ </simplesect>\r
+ <simplesect>\r
<info>\r
<title>Check In</title>\r
</info>\r
-\r
<procedure>\r
<step>\r
<informalfigure>\r
<imagedata scalefit="0" fileref="../media/offline-19.png"/>\r
</imageobject>\r
</mediaobject></para>\r
-\r
</informalfigure>\r
</step>\r
-\r
<step>\r
<informalfigure>\r
<para><guilabel>Check In</guilabel> screen will open.</para>\r
<imagedata scalefit="0" fileref="../media/offline-20.png"/>\r
</imageobject>\r
</mediaobject></para>\r
-\r
</informalfigure>\r
</step>\r
-\r
<step>\r
<informalfigure>\r
<para>Make sure the date is correct.</para>\r
<imagedata scalefit="0" fileref="../media/offline-21.png"/>\r
</imageobject>\r
</mediaobject></para>\r
-\r
</informalfigure>\r
</step>\r
-\r
<step>\r
<informalfigure>\r
<para>Scan the items barcode in <guilabel>Enter item barcode</guilabel> box. The\r
</mediaobject></para>\r
</informalfigure>\r
</step>\r
-\r
<step>\r
<para>Scan all items you want to check in.</para>\r
</step>\r
</mediaobject></para>\r
</informalfigure>\r
</step>\r
-\r
</procedure>\r
<caution>\r
<para>Without access to Evergreen database, items on holds or with special status will not\r
be captured in offline mode. Sitka Support Team recommends libraries not use check in\r
function on Standalone Interface if possible.</para>\r
</caution>\r
- </section>\r
-\r
-\r
- <section>\r
+ </simplesect>\r
+ <simplesect>\r
<info>\r
<title>Uploading offline transactions</title>\r
</info>\r
-\r
<para>Once you are able to connect to the server, you need to upload the offline transactions.\r
It is good practice to do this as soon as possible, but if the local system administrator\r
isn’t on site for a day or two do not panic.</para>\r
-\r
<para>The terms <guilabel>Offline Interface</guilabel> and <guilabel>Standalone\r
Interface</guilabel> mean the same thing - a separate program to handle simple\r
circulation tasks while the network is down. </para>\r
-\r
<para>Once you can connect to the server, there are 3 steps to uploading offline\r
transactions:</para>\r
-\r
<orderedlist inheritnum="ignore" continuation="restarts">\r
<listitem>\r
<para>Create a session: to be done by local\r
be done by local system administrators at an administration workstation.</para>\r
</listitem>\r
</orderedlist>\r
-\r
<para>Once the network has come back up, a local system administrator must first create a\r
session before uploading transactions. Then, staff can upload transactions from each of the\r
workstations used in offline circ to that session. Once all of the branch workstations\r
have uploaded their transactions to the session, the manager will process all the\r
transactions from all the workstations at once. </para>\r
-\r
<note>\r
<para>Circulation Staff uploading transactions to the session does not put the transactions\r
into the <application>Evergreen</application> database. The transactions will not be\r
sent to the <application>Evergreen</application> database until the manager processes\r
the session.</para>\r
</note>\r
-\r
<simplesect xml:id="offline-create">\r
<info>\r
<title>Create a Session</title>\r
</info>\r
-\r
<procedure>\r
<step>\r
<para>Log into Evergreen with a local system administrator username and\r
</para>\r
</informalfigure>\r
</step>\r
-\r
-\r
<step>\r
<para>The <guilabel>Offline Transactions</guilabel> screen will open. Previously\r
created sessions will be listed in the Offline Sessions section. Otherwise, the\r
Offline Sessions section will be blank. </para>\r
</step>\r
-\r
<step>\r
<informalfigure>\r
<para>In the upper <guilabel>Offline Sessions</guilabel> section, click on the\r
<imageobject>\r
<imagedata scalefit="0" fileref="../media/offline-28.png"/>\r
</imageobject>\r
-\r
</mediaobject>\r
</para>\r
</informalfigure>\r
</step>\r
-\r
-\r
<step>\r
<informalfigure>\r
<para>Enter a name for the session, like “Internet Down 2009-12-02”. Click\r
<imageobject>\r
<imagedata scalefit="0" fileref="../media/offline-29.png"/>\r
</imageobject>\r
-\r
</mediaobject>\r
</para>\r
</informalfigure>\r
</step>\r
-\r
-\r
<step>\r
<informalfigure>\r
<para>In the <guilabel>Offline Sessions</guilabel> section, highlight the session\r
</para>\r
</informalfigure>\r
</step>\r
-\r
-\r
<step>\r
<para>Inform library staff that the session has been created and what the session\r
name is. </para>\r
</step>\r
</procedure>\r
-\r
</simplesect>\r
<simplesect xml:id="offline-upload">\r
<info>\r
it's ready for your upload. There may be several sessions shown on the <guilabel>Offline\r
Transaction Management</guilabel> screen, so you will need the name of the correct\r
session from your local system administrator.</para>\r
-\r
<procedure>\r
<step>\r
<para>Log into <application>Evergreen</application> with your regular username and\r
password.</para>\r
</step>\r
-\r
-\r
<step>\r
<para>From the menu bar, select <menuchoice>\r
<guimenu>Admin (-)</guimenu>\r
<imageobject>\r
<imagedata width="100%" scalefit="1" fileref="../media/offline-31.png"/>\r
</imageobject>\r
-\r
-\r
</mediaobject>\r
</para>\r
</informalfigure>\r
</step>\r
-\r
-\r
-\r
-\r
<step>\r
<informalfigure>\r
<para>When the uploading is finished,select the session in Offline Sessions\r
</para>\r
</informalfigure>\r
</step>\r
-\r
-\r
<step>\r
<para>Inform your local system administrator that your transaction has been uploaded\r
to the session.</para>\r
</step>\r
-\r
</procedure>\r
-\r
<note>\r
<para>You will need to do this for each workstation you have used for offline\r
circulation. If your library has more than one workstations that have been used for\r
offline transactions you will see the other workstation sessions that have already\r
been uploaded. </para>\r
</note>\r
-\r
</simplesect>\r
<simplesect xml:id="offline-process">\r
<info>\r
<title>Process the Transactions</title>\r
</info>\r
-\r
<para>Wait until all the appropriate staff workstations have uploaded their transactions to\r
your session. You should see the workstations listed in the <guilabel>Uploaded\r
Transactions</guilabel> section. You'll need to be logged into\r
<application>Evergreen</application> as a local system administrator to do the\r
processing step.</para>\r
<procedure>\r
-\r
<step>\r
<para>Log into <application>Evergreen</application> with a local system\r
administrator's username and password.</para>\r
</step>\r
-\r
<step>\r
<para>From the menu bar, select <menuchoice>\r
<guimenu>Admin (-)</guimenu>\r
<guimenuitem>Offline Transaction Management</guimenuitem>\r
</menuchoice>.</para>\r
</step>\r
-\r
-\r
<step>\r
<informalfigure>\r
<para>Highlight the correct session and, if necessary,\r
<imageobject>\r
<imagedata width="100%" scalefit="1" fileref="../media/offline-33.png"/>\r
</imageobject>\r
-\r
</mediaobject>\r
</para>\r
</informalfigure>\r
</step>\r
-\r
-\r
<step>\r
<informalfigure>\r
<para>Click on the <guibutton>Process</guibutton> button. </para>\r
</para>\r
</informalfigure>\r
</step>\r
-\r
-\r
<step>\r
<informalfigure>\r
<para>The processing may take a while, depending on how many transactions you have\r
<imageobject>\r
<imagedata width="100%" scalefit="1" fileref="../media/offline-35.png"/>\r
</imageobject>\r
-\r
</mediaobject>\r
</para>\r
</informalfigure>\r
</step>\r
</procedure>\r
-\r
<note>\r
<para>The number in the <guilabel>Transactions Processed</guilabel> column is equal to\r
the number of items checked out or checked in. For example, if there are 5\r
<info>\r
<title>Exceptions</title>\r
</info>\r
-\r
<para>Exceptions are problems that were encountered during processing. For example, a\r
mis-scanned patron barcode, an open circulation, or an item that wasn’t checked in\r
before it was checked out to another patron, would be listed as an exception. Those\r
transactions causing exceptions may not be loaded into Evergreen database. Staff should\r
examine the exceptions and take necessary action.</para>\r
-\r
<informalfigure>\r
<para>The example below shows several exceptions:</para>\r
-\r
<para>\r
<mediaobject>\r
<alt>screenshot of staff client</alt>\r
</listitem>\r
</orderedlist>\r
</simplesect>\r
- </section>\r
+ </simplesect>\r
</section>\r
</chapter>\r
projects / Evergreen-DocBook.git / commitdiff