<title>Locating Records</title>\r
<simplesect xml:id="staffclientrecordsearch">\r
<title>Search</title>\r
+ <indexterm><primary>cataloguing</primary><secondary>locating records</secondary></indexterm>\r
<para>Search functionality may be functioned through:\r
<itemizedlist>\r
<listitem><menuchoice><guimenu>Cataloging</guimenu><guimenuitem>Search the Catalog</guimenuitem></menuchoice> </listitem>\r
</simplesect>\r
<simplesect xml:id="addingandeditingitems">\r
<title>Adding and Editing Items</title>\r
+ <indexterm><primary>cataloguing</primary><secondary>adding and editing items</secondary></indexterm>\r
<simplesect xml:id="adingholdingstotitlerecords">\r
- <title>Adding Holdings to Title Rrcords</title> \r
+ <title>Adding Holdings to Title Rrcords</title> \r
+ <indexterm><primary>cataloguing</primary><secondary>adding holdings</secondary></indexterm> \r
<procedure>\r
<step><para>Retrieve an existing bibliographic record.</para></step>\r
<step><para>Actions for this Record->Holdings Maintenance.</para></step>\r
- <step><para>The Record opens in <emphasis>record summary</emphasis> view. To display existing volume and copy records, check the boxes for <emphasis>Show Volumes</emphasis> and <emphasis>Show Items.</emphasis> \r
+ <step><para>The Record opens in <emphasis>record summary</emphasis> view. To display existing volume and copy records, check the boxes for \r
+ <emphasis>Show Volumes</emphasis> and <emphasis>Show Items.</emphasis> \r
These boxes are <emphasis>sticky</emphasis> and will remain checked for the login until manually de-selected.</para></step>\r
\r
<step><para>Highlight the appropriate library from the display.</para></step>\r
</simplesect>\r
<simplesect xml:id="copyalertsandnotes">\r
<title>Copy Alerts and Notes</title>\r
+ \r
<simplesect xml:id="copyalerts">\r
<title>Copy Alerts</title>\r
+ <indexterm><primary>cataloguing</primary><secondary>copy alerts</secondary></indexterm> \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
\r
</simplesect>\r
<simplesect xml:id="copynotes">\r
<title>Copy Notes</title>\r
+ <indexterm><primary>cataloguing</primary><secondary>copy notes</secondary></indexterm>\r
<para>Copy notes are informational only. They may be internal or made available to the public in the OPAC.</para> \r
<procedure>\r
<title>Accessing copy notes from the copy editor:</title>\r
</section>\r
<section xml:id="addingnewbibliographicrecords">\r
<title>Adding New Bibliographic Records</title>\r
+ <indexterm><primary>cataloguing</primary><secondary>adding bibliographic records</secondary></indexterm>\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
<simplesect xml:id="ImportingMARCRecords-Z39">\r
<title>Importing MARC Records via the Z39.50 Interface</title>\r
+ <indexterm><primary>Z39.50</primary><secondary>importing records</secondary></indexterm>\r
<procedure>\r
<step><para><menuchoice><guimenu>Cataloging</guimenu> <guimenuitem>Import Record from Z39.50</guimenuitem></menuchoice></para></step>\r
<step><para>Select single or multiple pre configured Z39.50 targets from the list. Only subscription services require logins. Once databases have \r
</simplesect> \r
<simplesect xml:id="importingrecords">\r
<title>Importing Records</title>\r
+ <indexterm><primary>cataloguing</primary><secondary>importing records</secondary></indexterm>\r
<procedure>\r
<step><para>Highlight the record and click <guibutton>MARC Editor for Import</guibutton>.</para></step>\r
<step><para>The record opens in the MARC Editor. Edit fixed and bibliographic fields. </para></step>\r
<emphasis>sticky</emphasis> for the login.</para></note>\r
</simplesect> \r
<simplesect xml:id="uploadingMARCfiles">\r
- <title>Uploading MARC files</title>\r
+ <title>Uploading MARC Files</title>\r
+ <indexterm><primary>cataloguing</primary><secondary>uploading MARC files</secondary></indexterm>\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
<procedure>\r
</simplesect> \r
<simplesect xml:id="creatingnewMARCrecords">\r
<title>Creating New MARC Records</title>\r
+ <indexterm><primary>cataloguing</primary><secondary>creating new MARC records</secondary></indexterm>\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
<procedure>\r
</section>\r
<section xml:id="MARCeditor">\r
<title>Working with the MARC Editor</title>\r
+ <indexterm><primary>cataloguing</primary><secondary>MARC editor</secondary></indexterm>\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
<simplesect xml:id="editingMARCrecords">\r
<title>Editing MARC Records</title>\r
+ <indexterm><primary>cataloguing</primary><secondary>editing MARC records</secondary></indexterm>\r
<procedure>\r
<step><para>Retrieve the record.</para></step>\r
<step><para><menuchoice><guimenu>Actions for this Record</guimenu> <guimenuitem>MARC Edit</guimenuitem></menuchoice>. </para></step>\r
</simplesect> \r
<simplesect xml:id="MARCrecordleader">\r
<title>MARC Record Leader and MARC fixed field 008</title>\r
+ <indexterm><primary>MARC</primary><secondary>MARC leader</secondary></indexterm>\r
+ <indexterm><primary>MARC</primary><secondary>fixed field 008</secondary></indexterm>\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
\r
<procedure>\r
- <title>To edit the MARC record leader:</title> \r
+ <title>To edit the MARC record leader</title> \r
<step><para>Retrieve and display the appropriate record in MARC Edit view.</para></step>\r
<step><para><emphasis>Click</emphasis> into any box displayed in the fixed field editor.</para></step>\r
<step><para>Press <keycap>Tab</keycap> or use the mouse to move between fields. </para></step> \r
</simplesect> \r
<simplesect xml:id="overlayingMARCrecords">\r
<title>Overlaying MARC Records</title>\r
+ <indexterm><primary>cataloguing</primary><secondary>overlaying MARC records</secondary></indexterm>\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
record is marked for overlay, the previously marked item is <emphasis>de-marked</emphasis>. Once a record is marked, it remains marked until overlaid or until the user logs out \r
of Evergreen.</para> \r
\r
<procedure>\r
- <title>Marking a record for overlay:</title>\r
+ <title>Marking a record for overlay</title>\r
<step><para>Search for and retrieve a record for overlay.</para></step>\r
<step><para>Select <menuchoice><guimenu>Actions for this Record</guimenu> <guimenuitem>Mark for Overlay</guimenuitem></menuchoice>. Record is now \r
<emphasis>marked</emphasis>.</para></step>\r
</procedure> \r
<procedure>\r
- <title>Overlaying the marked record:</title>\r
+ <title>Overlaying the marked record</title>\r
<step><para>Once the record is marked for overlay, proceed to search for and import the new record from a Z39.50 target.</para></step>\r
<step><para>Select <menuchoice><guimenu>Cataloging</guimenu> <guimenuitem>Import Record from Z39.50</guimenuitem></menuchoice>.</para></step>\r
<step><para>Choose targets and enter search terms.</para></step>\r
</section>\r
<section xml:id="cattemplates">\r
<title>Cataloging Templates</title>\r
+ <indexterm><primary>cataloguing</primary><secondary>templates</secondary></indexterm>\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
- <title>Creating item templates:</title>\r
+ <title>Creating item templates</title>\r
<step><para>Search for and retrieve a record.</para></step>\r
<step><para>Select <menuchoice><guimenu>Actions for this Record</guimenu> <guimenuitem>Holdings Maintenance</guimenuitem></menuchoice>.</para></step> \r
<step><para>Select an item record in list and click <menuchoice><guimenu>Actionsfor Selected Rows</guimenu> <guimenuitem>Edit Item Attributes</guimenuitem></menuchoice>.\r
</section> \r
<section xml:id="buckets">\r
<title>Buckets</title>\r
+ <indexterm><primary>cataloguing</primary><secondary>buckets</secondary></indexterm>\r
<para>The Buckets function in Evergreen groups records together and allows for batch changes and the creation of pull lists.</para> \r
<para>Batch changes allow many records to be grouped together for changes to be enacted on them all at once, instead performing individual edits. Buckets allow materials to be \r
tracked and worked by multiple staff members. </para> \r
</procedure>\r
\r
<procedure>\r
- <title>Creating record buckets from within a record:</title>\r
+ <title>Creating record buckets from within a record</title>\r
<step><para>Search for, retrieve, and display the desired bibliographic record.</para></step>\r
<step><para>Choose <menuchoice><guimenu>Actions for this Record</guimenu> <guimenuitem>Add to Bucket</guimenuitem></menuchoice>.</para></step> \r
<step><para>Select <guimenuitem>Add to New Bucket</guimenuitem>.</para></step> \r
<step><para>Continue to add records, if required.</para></step> \r
</procedure> \r
<procedure>\r
- <title>To work from within the buckets module:</title> \r
+ <title>To work from within the buckets module</title> \r
<step><para>Choose <menuchoice><guimenu>Cataloging </guimenu> <guimenuitem> Manage Record Buckets</guimenuitem></menuchoice>.</para></step>\r
<step><para>Select the Record Query tab on the left side of the screen.</para></step> \r
<step><para>Select the appropriate bucket and click <guibutton>Add to Selected Bucket</guibutton>.</para></step> \r
</tip>\r
<simplesect xml:id="addingcopyrecordscopybuckets">\r
<title>Adding Copy Records to Copy Buckets</title>\r
+ <indexterm><primary>cataloguing</primary><secondary>copy buckets</secondary></indexterm>\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
\r
</simplesect>\r
<simplesect xml:id="WorkingwithRecordsinaBucket">\r
<title>Working with Records in a Bucket</title>\r
+ <indexterm><primary>cataloguing</primary><secondary>record buckets</secondary></indexterm>\r
<para>Once records have been placed in a bucket, a variety of functions may be performed. </para> \r
\r
<procedure>\r
<title>To batch edit records:</title>\r
+ <indexterm><primary>cataloguing</primary><secondary>record buckets</secondary><tertiary>batch edit</tertiary></indexterm>\r
<step><para>Access the Copy Bucket view by choosing <menuchoice><guimenu>Edit</guimenu> \r
<guimenuitem>Copy Buckets</guimenuitem>\r
</menuchoice>.</para></step>\r
<step><para>Click <guibutton>OK</guibutton>.</para></step> \r
<step><para>The desired changes are made for all selected items.</para></step> \r
</procedure>\r
- <caution><para>Use caution when using the Transfer to Specific Volume action.</para></caution> \r
+ <caution><para>Use caution when using the <guilabel>Transfer to Specific Volume</guilabel> action.</para></caution> \r
<procedure>\r
- <title>Removing records from buckets:</title>\r
+ <title>Removing records from buckets</title>\r
+ <indexterm><primary>cataloguing</primary><secondary>buckets</secondary><tertiary>removing records</tertiary></indexterm>\r
<step><para>select the desired record.</para></step>\r
<step><para>Click <guibutton>Remove Selected from Bucket</guibutton></para></step>\r
</procedure>\r
<para>The same procedure is used for both Record and Copy Buckets</para>\r
\r
<procedure>\r
- <title>Retrieving shared buckets:</title> \r
+ <title>Retrieving </title>\r
+ <indexterm><primary>cataloguing</primary><secondary>shared buckets</secondary></indexterm>\r
<step><para>Access the copy or record bucket management screen as described above.</para></step>\r
<step><para>In drop down menu beside <guimenu>Choose a bucket…</guimenu> select <guimenuitem>Retrieve shared bucket</guimenuitem>.</para></step>\r
<step><para>Enter the desired bucket number and click <guibutton>OK</guibutton>.</para></step>\r
</section>\r
<section xml:id="MergingBibliographicRecords">\r
<title>Merging Bibliographic Records</title>\r
+ <indexterm><primary>cataloguing</primary><secondary>merging bibliographic records</secondary></indexterm>\r
<para>A common application for the merge function in Evergreen is to replace brief records with full records. This is only necessary when a full record cannot be located \r
in a Z39.50 target.</para>\r
<para>Any volume and copy records or holds associated with the brief record will be transferred to the full record upon merging.</para> \r
</section>\r
<section xml:id="Addingholdings">\r
<title>Adding holdings to title records</title>\r
+ <indexterm><primary>cataloguing</primary><secondary>adding holdings</secondary></indexterm>\r
<para>This lesson demonstrates adding your library’s volume and copy records to a title record. </para>\r
<procedure>\r
<step>\r
</section> \r
<section xml:id="PrintingSpineandPocketLabels">\r
<title>Printing Spine and Pocket Labels</title>\r
+ <indexterm><primary>labels</primary><secondary>spine</secondary></indexterm>\r
+ <indexterm><primary>labels</primary><secondary>pocket</secondary></indexterm>\r
<para>Copy buckets may be used to group items requiring labels.</para> \r
<procedure>\r
<step><para>Locate the correct copy bucket.</para></step>\r
</section>\r
<section xml:id="DeletingRecords">\r
<title>Deleting Records</title>\r
- \r
+ <indexterm><primary>cataloguing</primary><secondary>deleting records</secondary></indexterm> \r
<procedure>\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
<para>This chapter presents explains the circulation procedures carried out from the staff client.</para>\r
</abstract>\r
</info> \r
- <section xml:id="patronrecords">\r
+ <section xml:id="patronrecords"><indexterm><primary>circulation</primary><secondary>patron records</secondary></indexterm>\r
<title>Patron Records</title>\r
<simplesect xml:id="searchingpatrons">\r
<title>Searching Patrons</title>\r
\r
</simplesect>\r
<simplesect xml:id="Registeringpatrons">\r
- <title>Registering New Patrons</title>\r
+ <title>Registering New Patrons</title><indexterm><primary>circulation</primary><secondary>registering new patrons</secondary></indexterm>\r
\r
<itemizedlist>\r
<listitem>Mandatory fields = Red.</listitem>\r
</itemizedlist>\r
</simplesect>\r
<simplesect xml:id="CloneUser">\r
- <title>Clone User from Existing Group Member</title>\r
+ <title>Clone User from Existing Group Member</title><indexterm><primary>circulation</primary><secondary>cloning users</secondary></indexterm>\r
<procedure>\r
<step><para>Open patron record, click <guibutton>Other</guibutton>.</para></step>\r
<step><para>Select Group.</para></step>\r
</procedure>\r
</simplesect>\r
<simplesect xml:id="Updatingpatroninformation">\r
- <title>Updating patron information</title>\r
+ <title>Updating Patron Information</title><indexterm><primary>circulation</primary><secondary>updating patron information</secondary></indexterm>\r
<procedure>\r
<step><para>Retrieve the patron record</para></step>\r
<step><para>Edit</para></step>\r
</procedure>\r
</simplesect>\r
<simplesect xml:id="renewinglibrarycards">\r
- <title>Extend Account Expiration Date</title>\r
+ <title>Extend Account Expiration Date</title><indexterm><primary>circulation</primary><secondary>extending account expiration date</secondary></indexterm>\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
<note><para>There is no warning that the account will soon expire. </para></note>\r
</procedure>\r
</simplesect>\r
<simplesect xml:id="lostlibrarycards">\r
- <title>Lost Library Cards</title>\r
+ <title>Lost Library Cards</title><indexterm><primary>circulation</primary><secondary>lost library cards</secondary></indexterm>\r
<procedure>\r
<step><para>Retrieve the patron record.</para></step>\r
<step><para>Click <guibutton>Mark Lost</guibutton> button.</para></step>\r
</caution> \r
</simplesect>\r
<simplesect xml:id="Resettingpatronpassword">\r
- <title>Resetting a Patron's Password</title>\r
+ <title>Resetting a Patron's Password</title><indexterm><primary>circulation</primary><secondary>resetting patron password</secondary></indexterm>\r
<procedure>\r
<step><para>Retrieve the record.</para></step>\r
<step><para>Click <guibutton>Reset</guibutton> Button next to <guilabel>password</guilabel> field</para></step>\r
</note> \r
</simplesect>\r
<simplesect xml:id="barringapatron">\r
- <title>Barring a Patron</title>\r
+ <title>Barring a Patron</title><indexterm><primary>circulation</primary><secondary>barring patrons</secondary></indexterm>\r
<procedure>\r
<step><para>Select <guimenuitem>4: Groups and Permissions</guimenuitem>. Select the <guilabel>Barred</guilabel> checkbox.</para></step>\r
<step><para>The Alert Message is required.</para></step>\r
to override blocks.</para>\r
</simplesect>\r
<simplesect xml:id="patronalerts">\r
- <title>Patron Alerts</title>\r
+ <title>Patron Alerts</title><indexterm><primary>circulation</primary><secondary>patron alerts</secondary></indexterm>\r
<para>There are two types of Patron Alerts:\r
<itemizedlist>\r
<listitem>System-generated alerts: once the cause is resolved (e.g. patron's account has been renewed), the message \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
</simplesect>\r
- <simplesect xml:id="patronnotes">\r
+ <simplesect xml:id="patronnotes"><indexterm><primary>circulation</primary><secondary>patron notes</secondary></indexterm>\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
</procedure> \r
</simplesect>\r
<simplesect xml:id="mergingpatronrecords">\r
- <title>Merging Patron Records</title>\r
+ <title>Merging Patron Records</title><indexterm><primary>circulation</primary><secondary>merging patron records</secondary></indexterm>\r
<procedure>\r
<title>Merging patron Records From the patron search screen:</title> \r
<step><para>Search by the terms shared by the two records</para></step>\r
</simplesect>\r
</section>\r
<section xml:id="circulatingitems">\r
- <title>Circulating Items</title>\r
+ <title>Circulating Items</title><indexterm><primary>circulation</primary><secondary>circulating items</secondary></indexterm>\r
<para>Regular circulation: circulation of items in the regular collection.</para> \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
</procedure>\r
</simplesect>\r
<simplesect xml:id="Precatalogeditems">\r
- <title>Pre-cataloged Items</title>\r
+ <title>Pre-cataloged Items</title><indexterm><primary>circulation</primary><secondary>pre-cataloged items</secondary></indexterm>\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
ask the patron to wait until you can have the item correctly processed.</para></caution> \r
</procedure>\r
</simplesect>\r
<simplesect xml:id="noncatalogeditems">\r
- <title>Non-cataloged Items</title>\r
+ <title>Non-cataloged Items</title><indexterm><primary>circulation</primary><secondary>non-cataloged items</secondary></indexterm>\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
<para>Items are checked out with a due date but when the due date expires, the items disappear from the \r
<para>Click OK.</para>\r
</simplesect>\r
<simplesect xml:id="duedates">\r
- <title>Due Dates</title>\r
+ <title>Due Dates</title><indexterm><primary>circulation</primary><secondary>due dates</secondary></indexterm>\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
may be set to override this circulation period.</para>\r
</simplesect>\r
<simplesect xml:id="checkin">\r
<title>Check In (<keycap>F2</keycap>)</title>\r
+ <indexterm><primary>circulation</primary><secondary>check in</secondary></indexterm>\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
</procedure>\r
</simplesect>\r
<simplesect xml:id="backdatedcheckin">\r
- <title>Backdated Check In</title>\r
+ <title>Backdated Check In</title><indexterm><primary>circulation</primary><secondary>backdated check in</secondary></indexterm>\r
<para>Used for checking items in from bookdrops or for unexpected closings.</para>\r
<procedure>\r
<step><para>Click the <guibutton>Check In</guibutton> button or hit <keycap>F2</keycap>.</para></step> \r
</procedure>\r
</simplesect>\r
<simplesect xml:id="Renewaleditingduedate">\r
- <title>Renewal and Editing Item's Due Date</title>\r
+ <title>Renewal and Editing an Item's Due Date</title>\r
+ <indexterm><primary>circulation</primary><secondary>renewel</secondary><tertiary>Editing an item's due date</tertiary></indexterm>\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
</simplesect>\r
<simplesect xml:id="lostclaimedreturned">\r
<title>Marking Items <emphasis>Lost</emphasis> and <emphasis>Claimed Returned</emphasis></title>\r
+ <indexterm><primary>circulation</primary><secondary>lost items</secondary></indexterm>\r
<procedure>\r
<title>To mark items as lost:</title>\r
<step><para>Retrieve the patron record.</para></step> \r
If the lost item is returned, the bill and payment (if bill has been paid) will not be cancelled/refunded automatically. \r
These bills must be dealt with manually, as per local policy.</para></note>\r
<procedure>\r
- <title>Marking items as <emphasis>Claimed Returned:</emphasis></title>\r
+ <title>Marking items as <emphasis>Claimed Returned:</emphasis></title><indexterm><primary>circulation</primary><secondary>claimed returned</secondary></indexterm>\r
<step><para>Retrieve the patron record.</para></step> \r
<step><para>Click <guibutton>Items Out</guibutton>.</para></step> \r
<step><para>Select item(s).</para></step>\r
<para>There are no alerts indicating claims returned items.</para>\r
</note>\r
</simplesect>\r
- <simplesect xml:id="inhouseuse">\r
+ <simplesect xml:id="inhouseuse"><indexterm><primary>circulation</primary><secondary>in-house use</secondary></indexterm>\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
<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
</simplesect>\r
- <simplesect xml:id="itemstatus">\r
+ <simplesect xml:id="itemstatus"><indexterm><primary>circulation</primary><secondary>item status</secondary></indexterm>\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
<para>Past circulations can also be retrieved from a patron's Items Out screen.</para> \r
</simplesect>\r
<simplesect xml:id="markingitemsdamaged">\r
- <title>Marking items <emphasis>damaged</emphasis> or <emphasis>missing</emphasis></title> \r
+ <title>Marking items <emphasis>damaged</emphasis> or <emphasis>missing</emphasis></title>\r
+ <indexterm><primary>circulation</primary><secondary>damaged items</secondary></indexterm>\r
+ <indexterm><primary>circulation</primary><secondary>missing items</secondary></indexterm> \r
<procedure>\r
<step><para>Retrieve the item.</para></step> \r
<step><para>Select the item. </para></step> \r
</simplesect>\r
<simplesect xml:id="itemalerts">\r
<title>Item alerts</title>\r
+ <indexterm><primary>circulation</primary><secondary>item alerts</secondary></indexterm>\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
<procedure>\r
</section>\r
<section xml:id="billsandpayments">\r
<title>Bills and Payments</title>\r
+ <indexterm><primary>bills and payments</primary></indexterm>\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>Grocery bills: staff-applied to patron accounts.</para> \r
</simplesect> \r
<simplesect xml:id="makingpayments">\r
- <title>Making Payments</title> \r
+ <title>Making Payments</title> \r
+ <indexterm><primary>bills and payments</primary><secondary>making payments</secondary></indexterm> \r
<procedure>\r
<step><para>Retrieve the patron record.</para></step> \r
<step><para>Bills</para></step> \r
<tip><para>You may choose to annotate payment and fill in resulting text box according to library policy.</para></tip>\r
</simplesect>\r
<simplesect xml:id="makingchange">\r
- <title>Making Change</title> \r
+ <title>Making Change</title>\r
+ <indexterm><primary>bills and payments</primary><secondary>making change</secondary></indexterm> \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
</simplesect>\r
<simplesect xml:id="voidforgive">\r
<title>Void vs. Forgive</title> \r
+ \r
<para>Void clears all history of the bill, while forgive retains the history.</para> \r
- <procedure>\r
- <title>Forgiving bills:</title> \r
- <step><para>Retrieve the patron record.</para></step> \r
- <step><para>Choose <guimenuitem>forgive</guimenuitem> as the payment type </para></step> \r
- <step><para>Enter the amount to be forgiven. </para></step>\r
- <step><para>Apply Payment.</para></step> \r
- </procedure>\r
+ <simplesect xml:id="forgivebills">\r
+ <title>Forgiving Bills</title><indexterm><primary>bills and payments</primary><secondary>forgiving bills</secondary></indexterm> \r
+ <procedure>\r
+ <step><para>Retrieve the patron record.</para></step> \r
+ <step><para>Choose <guimenuitem>forgive</guimenuitem> as the payment type </para></step> \r
+ <step><para>Enter the amount to be forgiven. </para></step>\r
+ <step><para>Apply Payment.</para></step> \r
+ </procedure>\r
+ </simplesect>\r
\r
<simplesect xml:id="voidbills">\r
- <para>Voiding bills:</para>\r
+ <title>Voiding Bills</title>\r
+ <indexterm><primary>bills and payments</primary><secondary>voiding bills</secondary></indexterm>\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>Click <guibutton>Void All Billings</guibutton></para></step> \r
</simplesect>\r
<simplesect xml:id="newgrocerybills">\r
<title>Adding New Grocery Bills</title>\r
+ <indexterm><primary>bills and payments</primary><secondary>adding new grocery bills</secondary></indexterm>\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
+ <title>To add as a new bill</title>\r
<step><para>Retrieve the patron record. </para></step> \r
<step><para>Select <guimenuitem>Bills</guimenuitem>.</para></step>\r
<step><para>Click <guibutton>Bill Patron</guibutton>.</para></step> \r
</simplesect>\r
<simplesect xml:id="billhistory">\r
<title>Bill History</title>\r
+ <indexterm><primary>bills and payments</primary><secondary>bill history</secondary></indexterm>\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
after the deletion.</para></note>\r
</simplesect>\r
<simplesect xml:id="bills-refund">\r
- <info><title>Refund</title></info>\r
+ <title>Refund</title>\r
+ <indexterm><primary>bills and payments</primary><secondary>refunds</secondary></indexterm>\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
</section>\r
<section xml:id="Holds">\r
<title>Holds</title>\r
+ <indexterm><primary>holds</primary></indexterm>\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
<simplesect xml:id="ViewingHolds">\r
<title>Viewing Holds</title>\r
+ <indexterm><primary>holds</primary><secondary>viewing holds</secondary></indexterm>\r
<procedure>\r
<step><para>Under Actions for this Record (<keycombo><keycap>Alt</keycap><keycap>A</keycap></keycombo>), select View Holds \r
(<keycombo><keycap>Alt</keycap><keycap>S</keycap></keycombo>). You can do this from any record view. You do not have to be in \r
</simplesect> \r
<simplesect xml:id="placingholds">\r
<title>Placing Holds</title>\r
+ <indexterm><primary>holds</primary><secondary>placing holds</secondary></indexterm>\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
</simplesect>\r
<simplesect xml:id="holdslevels">\r
<title>Holds Levels</title>\r
+ <indexterm><primary>holds</primary><secondary>levels</secondary></indexterm>\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
<title>Hold Levels Explained:</title>\r
</simplesect>\r
<simplesect xml:id="managingholds">\r
<title>Managing Holds</title>\r
+ <indexterm><primary>holds</primary><secondary>managing</secondary></indexterm>\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
<itemizedlist>\r
</simplesect> \r
<simplesect xml:id="TransferringHolds">\r
<title>Transferring Holds</title>\r
+ <indexterm><primary>holds</primary><secondary>transferring</secondary></indexterm>\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>View the holds on the record where the hold is currently.</para></step>\r
</simplesect> \r
<simplesect xml:id="CancelingHolds">\r
<title>Canceling Holds</title>\r
+ <indexterm><primary>holds</primary><secondary>canceling</secondary></indexterm>\r
<procedure>\r
<step><para>View the holds for the item.</para></step> \r
<step><para>Highlight the hold you need to cancel.</para></step>\r
</simplesect>\r
<simplesect xml:id="RetargetingHolds">\r
<title>Retargeting Holds</title>\r
+ <indexterm><primary>holds</primary><secondary>retargeting</secondary></indexterm>\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
Missing or set to other non-circulating statuses are once again made available for circulation.</para> \r
</simplesect>\r
<simplesect xml:id="holdspulllist">\r
<title>Holds Pull List</title>\r
+ <indexterm><primary>holds</primary><secondary>pull list</secondary></indexterm>\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
<para><emphasis>Waiting-for-copy</emphasis>: all copies are checked out or otherwise unavailable.</para>\r
from the list. </para></note>\r
<simplesect xml:id="capturingholds">\r
<title>Capturing Holds</title>\r
+ <indexterm><primary>holds</primary><secondary>capturing</secondary></indexterm>\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
</simplesect> \r
<simplesect xml:id="holdsshelflist">\r
<title>Holds Shelf List</title>\r
+ <indexterm><primary>holds</primary><secondary>shelf list</secondary></indexterm>\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
<procedure>\r
</section>\r
<section xml:id="transititems">\r
<title>Transit Items</title>\r
+ <indexterm><primary>transit items</primary></indexterm>\r
<para>Evergreen’s In Transit feature tracks items transferring among branches. It allows patrons to return items at any branch and for holds to be placed on items at other branches.</para>\r
<para>When will an item go In Transit?</para> \r
<orderedlist>\r
</orderedlist>\r
<simplesect xml:id="receivingtransititems">\r
<title>Receiving In Transit Items</title>\r
+ <indexterm><primary>transit items</primary><secondary>receiving</secondary></indexterm>\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
</simplesect>\r
<simplesect xml:id="transitlist">\r
<title>Transit List</title>\r
+ <indexterm><primary>transit items</primary><secondary>rlist</secondary></indexterm>\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
<procedure>\r
</simplesect>\r
<simplesect xml:id="abortingtransits">\r
<title>Aborting Transits</title>\r
+ <indexterm><primary>transit items</primary><secondary>aborting</secondary></indexterm>\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
This procedure can be performed from the <emphasis>Transit List</emphasis> or from the <emphasis>Item Status</emphasis> screen.</para>\r
</procedure> \r
<simplesect xml:id="cancellingtransitscheckout">\r
<title>Cancelling Transits at Checkout</title>\r
+ <indexterm><primary>transit items</primary><secondary>cancelling</secondary></indexterm>\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="offlinetransactions">\r
<title>Offline Transactions</title>\r
- \r
+ <indexterm><primary>offline transactions</primary></indexterm>\r
<para>Evergreen's Standalone Interface/Offline Interface is designed to log transactions during\r
network outage, which can be uploaded and processed once network operations are\r
restored.</para>\r
\r
- <para>The terms “Offline Interface” and “Standalone Interface” mean the same thing - a separate\r
+ <para>The terms <emphasis>Offline Interface</emphasis> and <emphasis>Standalone Interface</emphasis> mean the same thing - a separate\r
program to handle simple circulation tasks while the network is down. </para>\r
\r
<informalfigure>\r
<simplesect>\r
<info>\r
<title>Patron Registration</title>\r
+ <indexterm><primary>offline transactions</primary><secondary>patron registration</secondary><seealso>circulation</seealso></indexterm>\r
</info>\r
<para>Patron registration on Evergreen Offline Interface records the minimum patron\r
information necessary to register a new patron.</para>\r
<simplesect xml:id="offline-check-out">\r
<info>\r
<title>Check Out</title>\r
+ <indexterm><primary>offline transactions</primary><secondary>check out</secondary><seealso>circulation</seealso></indexterm>\r
</info>\r
<procedure>\r
<step>\r
<simplesect>\r
<info>\r
<title>Renew</title>\r
+ <indexterm><primary>offline transactions</primary><secondary>renew</secondary><seealso>circulation</seealso></indexterm>\r
</info>\r
<para>To renew, you must know items barcode number. Patron's barcode is optional.</para>\r
<procedure>\r
<simplesect>\r
<info>\r
<title>In House Use</title>\r
+ <indexterm><primary>offline transactions</primary><secondary>in house use</secondary><seealso>circulation</seealso></indexterm>\r
</info>\r
<para/>\r
<procedure>\r
<simplesect>\r
<info>\r
<title>Check In</title>\r
+ <indexterm><primary>offline transactions</primary><secondary>Check In</secondary><seealso>circulation</seealso></indexterm>\r
</info>\r
<procedure>\r
<step>\r
<simplesect>\r
<info>\r
<title>Uploading offline transactions</title>\r
+ <indexterm><primary>offline transactions</primary><secondary>uploading</secondary></indexterm>\r
</info>\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
<simplesect xml:id="offline-create">\r
<info>\r
<title>Create a Session</title>\r
+ <indexterm><primary>offline transactions</primary><secondary>create a session</secondary></indexterm>\r
</info>\r
<procedure>\r
<step>\r
<simplesect xml:id="offline-upload">\r
<info>\r
<title>Upload Workstation Transactions to a Session</title>\r
+ <indexterm><primary>offline transactions</primary><secondary>upload workstation transactions to a session</secondary></indexterm>\r
</info>\r
\r
<para>Wait until the local system administrator has created a session and told you that\r
<simplesect xml:id="offline-process">\r
<info>\r
<title>Process the Transactions</title>\r
+ <indexterm><primary>offline transactions</primary><secondary>process transactions</secondary></indexterm>\r
</info>\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
<simplesect>\r
<info>\r
<title>Exceptions</title>\r
+ <indexterm><primary>offline transactions</primary><secondary>exceptions</secondary></indexterm>\r
</info>\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
projects / transitory.git / commitdiff