Clean up 2.1 branch.
authorrsoulliere <robert.soulliere@mohawkcollege.ca>
Wed, 5 Oct 2011 18:52:47 +0000 (14:52 -0400)
committerrsoulliere <robert.soulliere@mohawkcollege.ca>
Wed, 5 Oct 2011 18:52:47 +0000 (14:52 -0400)
362 files changed:
admin/AdminMisc.xml [deleted file]
admin/Upgrading-Evergreen-2.0.xml [deleted file]
admin/acquisitions_admin_functions.xml [deleted file]
admin/actiontriggers.xml [deleted file]
admin/admin-booking.xml [deleted file]
admin/admin-intro.xml [deleted file]
admin/admin-lsa_2.0.xml [deleted file]
admin/localization.xml [deleted file]
admin/migratingdata_2.0.xml [deleted file]
admin/serversideinstallation_2.0.xml [deleted file]
admin/sip.xml [deleted file]
admin/staffclientinstallation.xml [deleted file]
admin/troubleshooting.xml [deleted file]
admin/z3950.xml [deleted file]
appendices/about_this_documentation.xml [deleted file]
appendices/bookindex.xml [deleted file]
appendices/glossary.xml [deleted file]
appendices/installchecklist.xml [deleted file]
appendices/more_info.xml [deleted file]
appendices/permissions.xml [deleted file]
appendices/schema.xml [deleted file]
appendices/schema.xml.bk [deleted file]
development/OpenSRF_intro.xml [deleted file]
development/customize_opac.xml [deleted file]
development/customizingstaffclient.xml [deleted file]
development/datamodelsandaccess.xml [deleted file]
development/development_intro.xml [deleted file]
development/directoriesandFiles.xml [deleted file]
development/installchecklist.xml [deleted file]
development/introduction_to_sql.xml [deleted file]
development/json.xml [deleted file]
development/supercat.xml [deleted file]
intro/about_evergreen.xml [deleted file]
intro/intro_intro.xml [deleted file]
intro/releasenotes.xml [deleted file]
media/1.png [deleted file]
media/10.png [deleted file]
media/11.png [deleted file]
media/12.png [deleted file]
media/13.png [deleted file]
media/14.png [deleted file]
media/15.png [deleted file]
media/2.png [deleted file]
media/3.png [deleted file]
media/4.png [deleted file]
media/5.png [deleted file]
media/6.png [deleted file]
media/7.png [deleted file]
media/8.png [deleted file]
media/9.png [deleted file]
media/acq__marc_search.png [deleted file]
media/acq_activate.png [deleted file]
media/acq_apply_claim_policy.png [deleted file]
media/acq_brief_record-2.png [deleted file]
media/acq_brief_record.png [deleted file]
media/acq_cancel_copy.png [deleted file]
media/acq_cancel_line_items.png [deleted file]
media/acq_cancel_order.png [deleted file]
media/acq_claim_item-2.png [deleted file]
media/acq_claim_item-3.png [deleted file]
media/acq_claim_item-4.png [deleted file]
media/acq_claim_item-5.png [deleted file]
media/acq_claim_item.png [deleted file]
media/acq_export_list.png [deleted file]
media/acq_funds-2.png [deleted file]
media/acq_funds.png [deleted file]
media/acq_invoice_blanket.png [deleted file]
media/acq_invoice_line_items.png [deleted file]
media/acq_invoice_link.png [deleted file]
media/acq_invoice_purchase_order.png [deleted file]
media/acq_invoice_view-2.png [deleted file]
media/acq_invoice_view.png [deleted file]
media/acq_line_items_add_copies-2.png [deleted file]
media/acq_line_items_add_copies-3.png [deleted file]
media/acq_line_items_add_copies.png [deleted file]
media/acq_line_items_add_notes.png [deleted file]
media/acq_line_items_alerts-2.png [deleted file]
media/acq_line_items_alerts.png [deleted file]
media/acq_line_items_link-2.png [deleted file]
media/acq_line_items_link.png [deleted file]
media/acq_line_items_update_barcodes.png [deleted file]
media/acq_line_items_view_history.png [deleted file]
media/acq_line_items_worksheet-2.png [deleted file]
media/acq_line_items_worksheet.png [deleted file]
media/acq_load_marc_records.png [deleted file]
media/acq_load_records.png [deleted file]
media/acq_marc_search-2.png [deleted file]
media/acq_marc_search.png [deleted file]
media/acq_purchase_order_add_charges.png [deleted file]
media/acq_purchase_order_add_note.png [deleted file]
media/acq_purchase_order_create.png [deleted file]
media/acq_purchase_order_history.png [deleted file]
media/acq_purchase_order_name.png [deleted file]
media/acq_purchase_order_print.png [deleted file]
media/acq_purchase_order_split-2.png [deleted file]
media/acq_purchase_order_split.png [deleted file]
media/acq_purchase_order_view-2.png [deleted file]
media/acq_purchase_order_view.png [deleted file]
media/acq_search.png [deleted file]
media/acq_selection_clone.png [deleted file]
media/acq_selection_create.png [deleted file]
media/acq_selection_mark_ready-2.png [deleted file]
media/acq_selection_mark_ready.png [deleted file]
media/acq_selection_merge.png [deleted file]
media/batch-receive-apply.png [deleted file]
media/batch-receive-autogen-1.png [deleted file]
media/batch-receive-autogen-2.png [deleted file]
media/batch-receive-choose-iss.png [deleted file]
media/batch-receive-partial.png [deleted file]
media/batch-receive-print-routing.png [deleted file]
media/batch-receive-receive.png [deleted file]
media/batch-receive-received.png [deleted file]
media/batch-receive-simple.png [deleted file]
media/caption-pattern-tab.png [deleted file]
media/caution.png [deleted file]
media/create-copy-template.png [deleted file]
media/create-distrib.png [deleted file]
media/create-iss-1.png [deleted file]
media/create-iss-2.png [deleted file]
media/create-many-streams.png [deleted file]
media/create-sub.png [deleted file]
media/create-template-1.png [deleted file]
media/create-template-10.png [deleted file]
media/create-template-11.png [deleted file]
media/create-template-12.png [deleted file]
media/create-template-13.png [deleted file]
media/create-template-15.png [deleted file]
media/create-template-16.png [deleted file]
media/create-template-17.png [deleted file]
media/create-template-19.png [deleted file]
media/create-template-2.png [deleted file]
media/create-template-20.png [deleted file]
media/create-template-21.png [deleted file]
media/create-template-22.png [deleted file]
media/create-template-23.png [deleted file]
media/create-template-24.png [deleted file]
media/create-template-25.png [deleted file]
media/create-template-26.png [deleted file]
media/create-template-27.png [deleted file]
media/create-template-28.png [deleted file]
media/create-template-29.png [deleted file]
media/create-template-3.png [deleted file]
media/create-template-30.png [deleted file]
media/create-template-31.png [deleted file]
media/create-template-32.png [deleted file]
media/create-template-33.png [deleted file]
media/create-template-34.png [deleted file]
media/create-template-35.png [deleted file]
media/create-template-4.png [deleted file]
media/create-template-5.png [deleted file]
media/create-template-6.png [deleted file]
media/create-template-7.png [deleted file]
media/create-template-8.png [deleted file]
media/create-template-9.png [deleted file]
media/create_an_issuance1.png [deleted file]
media/create_an_issuance2.png [deleted file]
media/create_an_issuance3.png [deleted file]
media/create_an_issuance4.png [deleted file]
media/create_an_issuance5.png [deleted file]
media/distribs-to-streams.png [deleted file]
media/evergreen_logo.gif [deleted file]
media/find-copy-template-menu.png [deleted file]
media/folder-1.png [deleted file]
media/folder-10.png [deleted file]
media/folder-11.png [deleted file]
media/folder-12.png [deleted file]
media/folder-13.png [deleted file]
media/folder-14.png [deleted file]
media/folder-7a.png [deleted file]
media/generate-report-1.png [deleted file]
media/generate-report-10.png [deleted file]
media/generate-report-14.png [deleted file]
media/generate-report-2.png [deleted file]
media/generate-report-3.png [deleted file]
media/generate-report-8.png [deleted file]
media/generate-report-9.png [deleted file]
media/generate_item_predictions1.png [deleted file]
media/generate_item_predictions2.png [deleted file]
media/generate_item_predictions3.png [deleted file]
media/generated-iss-delete-dummy.png [deleted file]
media/lsa-1.png [deleted file]
media/lsa-10.jpg [deleted file]
media/lsa-11.jpg [deleted file]
media/lsa-12.jpg [deleted file]
media/lsa-14.jpg [deleted file]
media/lsa-16.jpg [deleted file]
media/lsa-17.jpg [deleted file]
media/lsa-18.jpg [deleted file]
media/lsa-2.jpg [deleted file]
media/lsa-22.png [deleted file]
media/lsa-23.jpg [deleted file]
media/lsa-25.jpg [deleted file]
media/lsa-26.jpg [deleted file]
media/lsa-27.jpg [deleted file]
media/lsa-28.jpg [deleted file]
media/lsa-32.jpg [deleted file]
media/lsa-33.jpg [deleted file]
media/lsa-4.jpg [deleted file]
media/lsa-5.jpg [deleted file]
media/lsa-7.jpg [deleted file]
media/lsa-8.jpg [deleted file]
media/lsa-closed-mountain-1.png [deleted file]
media/lsa-closed-mountain-2.png [deleted file]
media/lsa-group-0.png [deleted file]
media/lsa-group-1.png [deleted file]
media/lsa-group-1a.png [deleted file]
media/lsa-group-2.png [deleted file]
media/lsa-group-3.png [deleted file]
media/lsa-group-4.png [deleted file]
media/lsa-group-5.png [deleted file]
media/lsa-group-6.png [deleted file]
media/main_logo.jpg [deleted file]
media/new-stream.png [deleted file]
media/note.png [deleted file]
media/pdf_icon.gif [deleted file]
media/predict-how-many.png [deleted file]
media/receipt-10.jpg [deleted file]
media/receipt-11.jpg [deleted file]
media/receipt-12.jpg [deleted file]
media/receipt-13.jpg [deleted file]
media/receipt-14.jpg [deleted file]
media/receipt-15.jpg [deleted file]
media/receipt-16.png [deleted file]
media/receipt-17.jpg [deleted file]
media/receipt-18.jpg [deleted file]
media/receipt-19.jpg [deleted file]
media/receipt-2.jpg [deleted file]
media/receipt-20.jpg [deleted file]
media/receipt-21.jpg [deleted file]
media/receipt-22.jpg [deleted file]
media/receipt-23.jpg [deleted file]
media/receipt-24.jpg [deleted file]
media/receipt-3.jpg [deleted file]
media/receipt-4.jpg [deleted file]
media/receipt-5.jpg [deleted file]
media/receipt-6.jpg [deleted file]
media/receipt-7.jpg [deleted file]
media/receipt-8.jpg [deleted file]
media/receipt-9.jpg [deleted file]
media/received-items-in-catalog.png [deleted file]
media/routing-list-add.png [deleted file]
media/routing-list-drag.png [deleted file]
media/routing-list-manage.png [deleted file]
media/save-scap.png [deleted file]
media/scap-wiz-page-1.png [deleted file]
media/scap-wiz-page-2.png [deleted file]
media/scap-wiz-page-3.png [deleted file]
media/scap-wiz-page-4.png [deleted file]
media/schema_diagram_acq_claiming.png [deleted file]
media/schema_diagram_acq_currency.png [deleted file]
media/schema_diagram_acq_distribution_formula.png [deleted file]
media/schema_diagram_acq_funds.png [deleted file]
media/schema_diagram_acq_invoice.png [deleted file]
media/schema_diagram_acq_line_Item_attributes.png [deleted file]
media/schema_diagram_acq_line_ltems.png [deleted file]
media/schema_diagram_acq_provider.png [deleted file]
media/schema_diagram_acq_user_request.png [deleted file]
media/schema_diagram_action_holds.png [deleted file]
media/schema_diagram_action_survey.png [deleted file]
media/schema_diagram_action_trigger.png [deleted file]
media/schema_diagram_actor.png [deleted file]
media/schema_diagram_asset.png [deleted file]
media/schema_diagram_authority.png [deleted file]
media/schema_diagram_biblio.png [deleted file]
media/schema_diagram_booking.png [deleted file]
media/schema_diagram_circ_matrix.png [deleted file]
media/schema_diagram_circulation.png [deleted file]
media/schema_diagram_config.png [deleted file]
media/schema_diagram_container.png [deleted file]
media/schema_diagram_hold_matrix.png [deleted file]
media/schema_diagram_metabib.png [deleted file]
media/schema_diagram_money.png [deleted file]
media/schema_diagram_offline.png [deleted file]
media/schema_diagram_permissions.png [deleted file]
media/schema_diagram_query.png [deleted file]
media/schema_diagram_reporter.png [deleted file]
media/schema_diagram_search.png [deleted file]
media/schema_diagram_serials_tables.png [deleted file]
media/schema_diagram_staging.png [deleted file]
media/schema_diagram_vandelay.png [deleted file]
media/serial_special_issue1.png [deleted file]
media/serial_special_issue2.png [deleted file]
media/serversideinstallation-staffclient-running-1.png [deleted file]
media/serversideinstallation-staffclient-running-2.png [deleted file]
media/serversideinstallation-staffclient-running-3.png [deleted file]
media/serversideinstallation-staffclient-running-4.png [deleted file]
media/serversideinstallation-testing-1.png [deleted file]
media/serversideinstallation-testing-2.png [deleted file]
media/serversideinstallation-virtual-vbox-install-1.png [deleted file]
media/serversideinstallation-virtual-vbox-install-2.png [deleted file]
media/serversideinstallation-virtual-vbox-install-3.png [deleted file]
media/serversideinstallation-virtual-vbox-install-4.png [deleted file]
media/serversideinstallation-virtual-vbox-install-5.png [deleted file]
media/serversideinstallation-virtual-vm-install-1.png [deleted file]
media/serversideinstallation-virtual-vm-install-10.png [deleted file]
media/serversideinstallation-virtual-vm-install-11.png [deleted file]
media/serversideinstallation-virtual-vm-install-12.png [deleted file]
media/serversideinstallation-virtual-vm-install-13.png [deleted file]
media/serversideinstallation-virtual-vm-install-14.png [deleted file]
media/serversideinstallation-virtual-vm-install-15.png [deleted file]
media/serversideinstallation-virtual-vm-install-16.png [deleted file]
media/serversideinstallation-virtual-vm-install-17.png [deleted file]
media/serversideinstallation-virtual-vm-install-18.png [deleted file]
media/serversideinstallation-virtual-vm-install-19.png [deleted file]
media/serversideinstallation-virtual-vm-install-2.png [deleted file]
media/serversideinstallation-virtual-vm-install-20.png [deleted file]
media/serversideinstallation-virtual-vm-install-21.png [deleted file]
media/serversideinstallation-virtual-vm-install-3.png [deleted file]
media/serversideinstallation-virtual-vm-install-4.png [deleted file]
media/serversideinstallation-virtual-vm-install-5.png [deleted file]
media/serversideinstallation-virtual-vm-install-6.png [deleted file]
media/serversideinstallation-virtual-vm-install-7.png [deleted file]
media/serversideinstallation-virtual-vm-install-8.png [deleted file]
media/serversideinstallation-virtual-vm-install-9.png [deleted file]
media/shared-template-6.png [deleted file]
media/shared-template-7.png [deleted file]
media/shared-template-9.png [deleted file]
media/small_logo_white.jpg [deleted file]
media/staffclientinstallation-staffclient-1.png [deleted file]
media/staffclientinstallation-staffclient-2.png [deleted file]
media/start-from-catalog.png [deleted file]
media/sub-details.png [deleted file]
media/subscription-manage.png [deleted file]
media/survey-1.png [deleted file]
media/survey-10.png [deleted file]
media/survey-2.png [deleted file]
media/survey-3.png [deleted file]
media/survey-4.png [deleted file]
media/survey-5.png [deleted file]
media/survey-6.png [deleted file]
media/survey-7.png [deleted file]
media/survey-8.png [deleted file]
media/survey-9.png [deleted file]
media/tip.png [deleted file]
media/view-output-1.png [deleted file]
media/view-output-2.png [deleted file]
media/view-output-3.png [deleted file]
media/view-output-4.png [deleted file]
media/view-output-5.png [deleted file]
media/warning.png [deleted file]
opac/opac_intro.xml [deleted file]
reports/report-add-data-source.xml [deleted file]
reports/report-create-template.xml [deleted file]
reports/report-exporting-report-templates-using-phppgadmin.xml [deleted file]
reports/report-folder.xml [deleted file]
reports/report-generate-report.xml [deleted file]
reports/report-intro.xml [deleted file]
reports/report-recurring-report.xml [deleted file]
reports/report-report-introduction.xml [deleted file]
reports/report-shared-template.xml [deleted file]
reports/report-startingreporter.xml [deleted file]
reports/report-template-terminology.xml [deleted file]
reports/report-view-output.xml [deleted file]
reports/report.diffs [deleted file]
stafftasks/acquisitions.xml [deleted file]
stafftasks/acquisitions_module-GPLS.xml [deleted file]
stafftasks/alternate_serial_control.xml [deleted file]
stafftasks/booking.xml [deleted file]
stafftasks/cataloging.xml [deleted file]
stafftasks/kcls_acquisitions.xml [deleted file]
stafftasks/serials-gpls.xml [deleted file]
stafftasks/stafftasks_intro.xml [deleted file]

diff --git a/admin/AdminMisc.xml b/admin/AdminMisc.xml
deleted file mode 100644 (file)
index ec6144e..0000000
+++ /dev/null
@@ -1,320 +0,0 @@
-<?xml version='1.0' encoding='UTF-8'?>\r
-<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"\r
-           xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="adminmisc">\r
-       <info>\r
-               \r
-       <title>Server Operations and Maintenance</title>\r
-       <indexterm><primary>receipt template editor</primary></indexterm>\r
-               <abstract>\r
-                       <para>This chapter deals with basic server operations such as starting and stopping <application>Evergreen</application> as well wall \r
-                       security, backing up and troubleshooting <application>Evergreen</application>.</para>\r
-               </abstract>\r
-       </info>    \r
-       <section xml:id="startingopensrf">\r
-               <title>Starting, Stopping and Restarting</title>\r
-               <para>Occasionally, you may need to restart <application>Evergreen</application>. It is imperative that you understand the basic \r
-               commands to stop and start the <application>Evergreen</application> server. You can start and stop <application>Evergreen</application> from the command line of \r
-               the server using the <command>osrf_ctl.sh</command> script located in the \r
-               <filename class="directory">openils/bin</filename> directory.</para>   \r
-               <note><para><command>The osrf_ctl.sh</command> command must be run as the <systemitem class="username">opensrf</systemitem> user.</para></note>\r
-               <para>To view help on <command>osrf_ctl.sh</command> and get all of its options, run:</para>\r
-               <screen><userinput>osrf_ctl.sh -h</userinput></screen>\r
-               <para>To start Evergreen, run:</para>\r
-               <screen><userinput>osrf_ctl.sh -l -a start_all</userinput></screen>\r
-               <para>The <option>-l</option> flag is used to indicate that Evergreen is configured to use <systemitem class="domainname">localhost</systemitem> as \r
-               the host. If you have configured <filename>opensrf.xml</filename> to use your real hostname, do not use the <option>-l</option> flag. The <option>-a</option> \r
-               option is required and indicates the <emphasis>action</emphasis> of the command. In this case \r
-               <option>start_all</option>.    \r
-               </para> \r
-               <note>\r
-                       <para>If you receive the error message: <errortext>osrf_ctl.sh: command not found</errortext>, then your environment variable \r
-                       <varname>PATH</varname><indexterm><primary>environment variable</primary><secondary>PATH</secondary></indexterm> does not include the \r
-                       <filename class="directory">/openils/bin</filename> directory. You can set it using the following command:</para>\r
-                       <screen><userinput>export <varname>PATH</varname>=$PATH:<filename class="directory">/openils/bin</filename></userinput></screen>\r
-                       <para>If you receive the error message <errortext>Can't locate OpenSRF/System.pm in @INC … BEGIN \r
-                       failed–compilation aborted</errortext>, then your environment variable <varname>PERL5LIB</varname><indexterm><primary>environment \r
-                       variable</primary><secondary>PERL5LIB</secondary></indexterm> does not \r
-                       include the <filename class="directory">/openils/lib/perl5</filename> directory.  You can set it \r
-                       using the following command:</para>\r
-                       <screen><userinput>export <varname>PERL5LIB</varname>=$PERL5LIB:<filename class="directory">/openils/lib/perl5</filename></userinput></screen>\r
-               </note>         \r
-               <para>It is also possible to start a specific service. For example:</para>\r
-               <screen><userinput>osrf_ctl.sh -l -a start_router</userinput></screen>\r
-               <para>will only start the <systemitem class="service">router</systemitem> service.</para>\r
-               <caution>\r
-                       <para>If you decide to start each service individually, you need to start them in a specific order \r
-                       for Evergreen to start correctly. Run the commands in this exact order:</para>\r
-                       <screen><userinput>osrf_ctl.sh -l -a start_router</userinput></screen>\r
-                       <screen><userinput>osrf_ctl.sh -l -a start_perl</userinput></screen>\r
-                       <screen><userinput>osrf_ctl.sh -l -a start_c</userinput></screen>\r
-               </caution>      \r
-               <para>After starting or restarting Evergreen, it is also necessary to restart the <systemitem class="service">Apache web server</systemitem>\r
-               <indexterm><primary>web server</primary><secondary>Apache</secondary></indexterm> for the OPAC to work correctly.</para>  \r
-               <para>To stop <application>Evergreen</application>, run:</para>\r
-               <screen><userinput>osrf_ctl.sh -l -a stop_all</userinput></screen>\r
-               <para>As with starting, you can choose to stop services individually.</para>\r
-               <para>To restart <application>Evergreen</application>, run:</para>\r
-               <screen><userinput>osrf_ctl.sh -l -a restart_all</userinput></screen>\r
-       </section>\r
-       <section xml:id="backingup">\r
-               <title>Backing Up</title>\r
-               <indexterm><primary>databases</primary><secondary>backing up</secondary></indexterm>\r
-       \r
-               <para>Backing up your system files and data is a critical task for server and database administrators. \r
-               Having a strategy for backing up and recovery could be the difference between a minor annoyance for users and\r
-               a complete catastrophe.</para>   \r
-               <simplesect>\r
-                       <title>Backing up the <application>Evergreen</application> Database</title><indexterm><primary>databases</primary></indexterm>\r
-                       <para>Most of the critical data for an <application>Evergreen</application> system – patrons, bibliographic records, holdings, \r
-                       transactions, bills – is stored in the <application>PostgreSQL</application><indexterm><primary>databases</primary>\r
-                       <secondary>PostgreSQL</secondary></indexterm>  database. You can therefore use normal \r
-                       <application>PostgreSQL</application> backup procedures to backup this data. For example, the simplest method of backing up the Evergreen\r
-                       database is to use the <command>pg_dump</command> command to create a live backup of the database without having to \r
-                       interrupt any Evergreen services. Here is an example pg_dump command which will dump a local Evergreen database into a the file <filename>evergreen_db.backup</filename>:</para>\r
-                       <screen><userinput>pg_dump -U evergreen -h localhost -f evergreen_db.backup evergreen</userinput></screen>\r
-                       <para>To restore the backed up database into a new database, create a new database using the \r
-                       template0 database template and the UTF8 encoding, and run the <command>psql</command> command, specifying the new \r
-                       database as your target:</para>\r
-                       <screen><userinput>createdb -T template0 -E UTF8 -U evergreen -h localhost new_evergreen</userinput></screen>\r
-                       <screen><userinput>psql -U evergreen -h localhost -f evergreen_db.backup new_evergreen</userinput></screen>\r
-                       <note>\r
-                               <para>This method of backup is only suitable for small Evergreen instances. Larger sites \r
-                               should consider implementing continuous archiving (also known as <quote>log shipping</quote>) to provide \r
-                               more granular backups with lower system overhead. More information on backing up <application>PostgreSQL</application> \r
-                               databases can be found in the official <link xl:href="http://www.postgresql.org/docs/"><application>PostgreSQL</application> documentation</link>.</para>\r
-                       </note>\r
-               </simplesect>\r
-               <simplesect>\r
-                       <title>Backing up Evergreen Files</title>\r
-                       <indexterm><primary>directories</primary><secondary>backing up</secondary></indexterm>\r
-                       <para>When you deploy Evergreen, you will probably customize many aspects of your system including \r
-                       the system configuration files, <application>Apache</application> configuration files, OPAC and Staff Client. In order to \r
-                       protect your investment of time, you should carefully consider the best approach to backing up \r
-                       files.</para>\r
-                       <para>There are a number of ways of tackling this problem. You could create a script that regularly \r
-                       creates a time-stamped tarball of all of these files and copies it to a remote server - but that \r
-                       would build up over time to hundreds of files. You could use <link xl:href="http://www.samba.org/rsync/"><application>rsync</application></link>\r
-                       <indexterm><primary>rsync</primary></indexterm> to ensure that the files of \r
-                       interest are regularly updated on a remote server - but then you would lose track of the changes to \r
-                       the files, should you make a change that introduces a problem down the road.</para>\r
-                       <para>Perhaps one of the best options is to use a version control system like <link xl:href="http://bazaar.canonical.com">\r
-                       <application>Bazaar</application></link><indexterm><primary>Version Control System</primary><secondary>Subversion</secondary></indexterm>, \r
-                       <link xl:href="http://git-scm.com/"><application>git</application></link><indexterm><primary>Version Control System</primary><secondary>git</secondary></indexterm> \r
-                       or <link xl:href="http://subversion.apache.org/"><application>Subversion</application></link><indexterm><primary>Version Control System</primary>\r
-                       <secondary>Subversion</secondary></indexterm> to regularly push updates of the files you care about to a repository on a \r
-                       remote server. This gives you the advantage of quickly being able to run through the history of the \r
-                       changes you made, with a commenting system that reminds you why each change was made, combined with \r
-                       remote storage of the pertinent files in case of disaster on site. In addition, your team can create \r
-                       local copies of the repository and test their own changes in isolation from the production \r
-                       system. Using a version control system also helps to recover system customizations after an \r
-                       upgrade.</para>\r
-               </simplesect>\r
-               <simplesect>\r
-                       <title>Full System Backup</title>\r
-                       <para>A full system backup archives every file on the file system. Some basic methods require you \r
-                       to shut down most system processes; other methods can use mirrored RAID<indexterm><primary>RAID</primary></indexterm> setups or \r
-                       SAN<indexterm><primary>SAN</primary></indexterm> storage to \r
-                       take <quote>snapshot</quote> backups of your full system while the system continues to run. The subject of how \r
-                       to implement full system backups is beyond the scope of this documentation.</para>\r
-               </simplesect>\r
-       </section>\r
-       <section xml:id="security">\r
-               <title>Security</title>\r
-               <indexterm><primary>security</primary></indexterm>\r
-               <para>As with an ILS and resource accessible from the world wide web careful consideration needs to be \r
-               given to the security of your <application>Evergreen</application> servers and database. While it is impossible to cover all aspects \r
-               of security, it is important to take several precautions when setting up production <application>Evergreen</application> site.</para>\r
-               <orderedlist>\r
-                       <listitem>\r
-                               <para>Change the Evergreen <systemitem class="username">admin</systemitem> password and keep it secure. The \r
-                               default admin password is known by anyone who has installed <application>Evergreen</application>. It is not a secret \r
-                               and needs to be changed by the Administrator. It should also only be shared by those who \r
-                               need the highest level of access to your system.</para>\r
-                       </listitem>\r
-                       <listitem>\r
-                               <para>Create strong passwords using a combination of numerical and alphabetical characters \r
-                               for all of the Administrative passwords including the <systemitem class="username">postgres</systemitem> and \r
-                               <systemitem class="username">opensrf</systemitem> users</para>     \r
-                       </listitem>\r
-                       <listitem>\r
-                               <para>Open ports in the firewall<indexterm><primary>firewall</primary></indexterm> with caution - It is only necessary to open ports \r
-                               <systemitem class="protocol">80</systemitem> and <systemitem class="protocol">443</systemitem>\r
-                               for <systemitem class="protocol">TCP</systemitem> connections to the Evergreen server from the OPAC and the staff client.  It is critical for administrators to \r
-                               understand the concepts of network security and take precautions to minimize vulnerabilities. \r
-                               </para>\r
-                       </listitem>\r
-                       <listitem>\r
-                               <para>Use permissions <indexterm><primary>permissions</primary></indexterm> and permission groups wisely - it is important to understand the \r
-                               purpose of the permissions and to only give users the level of access that they require.\r
-                               </para> \r
-                       </listitem>\r
-                                       </orderedlist>  \r
-       </section>\r
-       <section xml:id="logfiles">\r
-               <title>Managing Log Files</title>\r
-               <indexterm><primary>logs</primary><secondary>managing</secondary></indexterm>\r
-               <para><application>Evergreen</application> comes with a sophisticated logging system, but it is important to manage the <application>OpenSRF</application> \r
-               and <application>Evergreen</application> logs. This section will provide a couple of log management techniques and tools.</para>        \r
-               <simplesect>\r
-                       <title>Using the <systemitem class="service">logrotate</systemitem> Utility to Manage Log Size</title> \r
-                       <indexterm><primary>logs</primary><secondary>Log Rotate</secondary></indexterm>\r
-                        <para>Fortunately, this is not a new problem for <systemitem class="osname">Unix</systemitem> administrators, and there are a number of ways of keeping your logs under control. \r
-                       On <systemitem class="osname">Debian</systemitem> and <systemitem class="osname">Ubuntu</systemitem>, for example, \r
-                       the <systemitem class="service">logrotate</systemitem> utility controls when old log files are compressed and a new log file is started. \r
-                       <systemitem class="service">logrotate</systemitem> runs once a day and checks all log files that it knows about to see if a \r
-                       threshold of time or size has been reached and rotates the log files if a threshold condition has been met.</para>\r
-                       <para>To teach <systemitem class="service">logrotate</systemitem> to rotate Evergreen logs on a weekly basis, or if they are > 50MB in size, \r
-                       create a new file <filename>/etc/logrotate.d/evergreen</filename> with the following contents: </para>\r
-<programlisting>\r
-compress\r
-/openils/var/log/*.log {\r
-# keep the last 4 archived log files along with the current log file\r
- # log log.1.gz log.2.gz log.3.gz log.4.gz\r
- # and delete the oldest log file (what would have been log.5.gz)\r
-rotate 5\r
-# if the log file is > 50MB in size, rotate it immediately\r
-size 50M\r
- # for those logs that don't grow fast, rotate them weekly anyway\r
-  weekly\r
-}\r
-</programlisting>\r
-               </simplesect>\r
-               <simplesect>\r
-                       <title>Changing Logging Level for <application>Evergreen</application></title>\r
-                       <indexterm><primary>logs</primary><secondary>logging levels</secondary></indexterm>\r
-                       <para>Change the Log Levels in your config files. Changing the level of logging will help \r
-                       narrow down errors.</para> \r
-                       <tip>\r
-                               <para>A high logging level is not wise to do in a production environment since  it \r
-                               will produce vastly larger log files and thus reduce server performance.</para>\r
-                       </tip>\r
-                       <para>Change logging levels by editing the configuration file \r
-                       <filename>/openils/conf/opensrf_core.xml</filename><indexterm><primary>configuration files</primary><secondary>opensrf_core.xml</secondary></indexterm></para>\r
-                       <para>you will want to search for lines containing &lt;loglevel&gt;.</para>\r
-                       <para> the default setting for loglevel is 3 which will log <emphasis>errors</emphasis>, \r
-                       <emphasis>warnings</emphasis> and <emphasis>information</emphasis>.</para>\r
-                       <para>The next level is 4 which is for debugging and provides additional information \r
-                       helpful for the debugging process.</para>\r
-                       <para>Thus, lines with:</para>\r
-                       <programlisting>&lt;loglevel&gt;3&lt;/loglevel&gt;</programlisting>\r
-                       <para>Should be changed to:</para>\r
-                       <programlisting>&lt;loglevel&gt;4&lt;/loglevel&gt;</programlisting>\r
-                       <para>to allow debugging level logging</para>\r
-                       <para>Other logging levels include <emphasis>0</emphasis> for no logging, \r
-                       <emphasis>1</emphasis> for logging errors and <emphasis>2</emphasis> for logging warnings \r
-                       and errors.</para>\r
-               </simplesect>\r
-       </section>\r
-       <section xml:id="InstallingPostgreSQL">\r
-               <title>Installing PostgreSQL from Source</title>\r
-               <indexterm><primary>databases</primary><secondary>PostgreSQL</secondary></indexterm>\r
-               <para>Some <systemitem class="osname">Linux</systemitem> distributions, such as <systemitem class="osname">Debian Etch (4.0)</systemitem>, do not offer PostgreSQL \r
-               version 8.2 as an installable package. Before you continue, examine the software dependencies listed in <xref linkend="serversideinstall-software-dependencies"/> \r
-               to ensure that your Linux distribution supports the required version of PostgreSQL.</para>\r
-\r
-               <note>\r
-                       <para>Some <systemitem class="osname">Linux</systemitem> distributions, such as <systemitem class="osname">Debian Etch (4.0)</systemitem>, do not offer PostgreSQL \r
-               version 8.2 as an installable package. Before you continue, examine the software dependencies listed in <xref linkend="serversideinstall-software-dependencies"/> \r
-               to ensure that your Linux distribution supports the required version of PostgreSQL.</para>\r
-               </note>\r
-               \r
-               <procedure>\r
-                       <step>\r
-                               <para>Install the application <application>stow</application> on your system if it is not already installed. Issue the following command as \r
-                               the <systemitem class="username">root</systemitem> user:</para>\r
-<screen>\r
-<userinput>apt-get install stow</userinput>\r
-</screen>\r
-                       </step>\r
-                       <step>\r
-                               <para>Download, compile, and install the latest release for PostgreSQL 8.2 (which was version <literal>8.2.12</literal> at the time of this writing). \r
-                               As the <systemitem class="username">root</systemitem> user, follow these steps:</para>\r
-                               \r
-<screen>\r
-<userinput>\r
-wget http://wwwmaster.postgresql.org/redir/198/h/source/v8.2.17/postgresql-8.2.17.tar.bz2\r
-tar xzf postgresql-8.2.17.tar.gz\r
-cd postgresql-8.2.17\r
-./configure --with-perl --enable-integer-datetimes --with-openssl --prefix=/usr/local/stow/pgsql\r
-make\r
-make install\r
-cd contrib\r
-make\r
-make install\r
-cd xml2\r
-make\r
-make install\r
-cd /usr/local/stow\r
-stow pgsql\r
-</userinput>\r
-</screen>\r
-                               \r
-                       </step>\r
-                       <step>\r
-                               <para>Create the new user <systemitem class="username">postgres</systemitem> to run the PostgreSQL processes. \r
-                               As the <systemitem class="username">root</systemitem> user, execute this command:</para>\r
-                               <screen><userinput>adduser postgres</userinput></screen>\r
-                       </step>\r
-                       <step>\r
-                               <para>Initialize the database directory and start up PostgreSQL. As the <systemitem class="username">root</systemitem> user, follow these steps:</para>\r
-                               \r
-<screen>\r
-<userinput>\r
-mkdir -p /usr/local/pgsql/data\r
-chown postgres /usr/local/pgsql/data\r
-su - postgres\r
-initdb -D /usr/local/pgsql/data -E UNICODE --locale=C\r
-pg_ctl -D /usr/local/pgsql/data -l /home/postgres/logfile start\r
-</userinput>\r
-</screen>\r
-                               <note>\r
-                                       <para>If an error occurs during the final step above, review the path of the home directory for the \r
-                                       <systemitem class="username">postgres</systemitem> user. It may be <literal>/var/lib/postresql</literal> instead of <literal>/home/postres</literal>.</para>\r
-                               </note>\r
-                       </step>\r
-               </procedure>\r
-       </section>\r
-       <section xml:id="configuringPostgreSQL">\r
-               <title>Configuring PostgreSQL</title>\r
-               <indexterm><primary>databases</primary><secondary>PostgreSQL</secondary></indexterm>\r
-               <para>The values of several PostreSQL configuration parameters may be changed for enhanced performance. The following table lists the default values \r
-               and some suggested updates for several useful parameters:</para>\r
-               <table>\r
-                       <title>Suggested configuration values</title>\r
-                       <tgroup align="left" cols="3" colsep="1" rowsep="1">\r
-                               <colspec colnum="1" colwidth="1.0*"/>\r
-                               <colspec colnum="2" colwidth="1.0*"/>\r
-                               <colspec colnum="3" colwidth="1.0*"/>\r
-                               <thead>\r
-                                       <row>\r
-                                               <entry>Parameter</entry>\r
-                                               <entry>Default</entry>\r
-                                               <entry>Suggested</entry>\r
-                                       </row>\r
-                               </thead>\r
-                               <tbody>\r
-                                       <row>\r
-                                               <entry>default_statistics_target</entry>\r
-                                               <entry>10</entry>\r
-                                               <entry>100</entry>\r
-                                       </row>\r
-                                       <row>\r
-                                               <entry>work_mem</entry>\r
-                                               <entry>4Mb</entry>\r
-                                               <entry>128Mb</entry>\r
-                                       </row>\r
-                                       <row>\r
-                                               <entry>shared_buffers</entry>\r
-                                               <entry>8Mb</entry>\r
-                                               <entry>512Mb</entry>\r
-                                       </row>\r
-                                       <row>\r
-                                               <entry>effective_cache_size</entry>\r
-                                               <entry>128Mb</entry>\r
-                                               <entry>4Gb</entry>\r
-                                       </row>\r
-                               </tbody>\r
-                       </tgroup>\r
-               </table>\r
-       </section>\r
-</chapter>\r
diff --git a/admin/Upgrading-Evergreen-2.0.xml b/admin/Upgrading-Evergreen-2.0.xml
deleted file mode 100644 (file)
index 1e15a08..0000000
+++ /dev/null
@@ -1,504 +0,0 @@
-<?xml version='1.0' encoding='UTF-8'?>\r
-<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"\r
-       xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="upgradingevergreen-2.0">\r
-       <info>\r
-               <title>Upgrading Evergreen to 2.0</title>\r
-               <abstract>\r
-                       <para>This Chapter will explain the step-by-step process of upgrading <application>Evergreen\r
-                       </application> to 2.0, including steps to upgrade <application>OpenSRF</application>. Before \r
-                       upgrading, it is important to carefully plan an upgrade strategy to minimize system downtime and \r
-                       service interruptions. All of the steps in this chapter are to be completed from the command line.</para>\r
-                       \r
-               </abstract>\r
-       </info>    \r
-               <para>Evergreen 2.0 has several software requirements:</para>\r
-               <itemizedlist>\r
-                       <listitem>PostgreSQL: Version 8.4 is the minimum supported version of PostgreSQL. </listitem>\r
-                       <listitem>Linux: Evergreen 2.0 has been tested on Debian Squeeze (6.0) and Ubuntu Lucid Lynx (10.04). If you are running an older version of these distributions, \r
-                       you may want to upgrade befor installing Evergreen 2.0. For instructions on upgrading these distributions, visit the \r
-                       <ulink url="http://www.debian.org/releases/squeeze/">Debian</ulink> or <ulink url="https://help.ubuntu.com/community/LucidUpgrades">Ubuntu</ulink> websites.</listitem>\r
-               </itemizedlist>\r
-               <para>In the following instructions, you are asked to perform certain steps as either the <systemitem class="username">root</systemitem>  or \r
-               <systemitem class="username">opensrf</systemitem> user.</para>\r
-               <itemizedlist>\r
-                       <listitem>Debian: To become the <systemitem class="username">root</systemitem> user, issue the <command>su</command> command and enter the password of the \r
-                       <systemitem class="username">root</systemitem> user.</listitem>\r
-                       <listitem>Ubuntu: To become the <systemitem class="username">root</systemitem> user, issue the <command>sudo su</command> command and enter the password of your current user.</listitem>\r
-               </itemizedlist>\r
-               <para>To switch from the <systemitem class="username">root</systemitem> user to a different user, issue the <command>su - [user]</command> command; for example, \r
-               <command>su - opensrf</command>. Once you have become a non-root user, to become the <systemitem class="username">root</systemitem> user again simply issue the exit command.</para> \r
-               <para>In the following instructions, <filename class='directory'>/path/to/OpenSRF/</filename> represents the path to the OpenSRF source directory.</para>\r
-       <section xml:id="upgradingevergreen-stop_evergreen">\r
-               <title>Backing Up Data</title>\r
-               <procedure>\r
-                       <step>\r
-                               <para>As <systemitem class="username">root</systemitem>, stop the <application>Apache</application> \r
-                               web server<indexterm><primary>web server</primary><secondary>Apache</secondary></indexterm>.</para>\r
-                       </step>\r
-                       <step>\r
-                               <para>As the <systemitem class="username">opensrf</systemitem> user, stop all \r
-                               <application>Evergreen</application>\r
-                               and <application>OpenSRF</application> services:</para>\r
-                               <screen><userinput>osrf_ctl.sh -l -a stop_all</userinput></screen>\r
-                       </step>\r
-                       <step>\r
-                               <para>Back up of the <filename class='directory'>/openils</filename> \r
-                               directory.</para>\r
-                       </step>\r
-                       <step>\r
-                               <para><link linkend="backingup">Back up the <application>evergreen\r
-                               </application> database</link>.</para>\r
-                       </step>\r
-               </procedure>\r
-       </section>\r
-       <section xml:id="upgradingevergreen-upgradingOpenSRF">\r
-               <title>Upgrading OpenSRF to 2.0</title><indexterm><primary>OpenSRF</primary></indexterm>\r
-               <procedure>\r
-                       <step>\r
-                               <para>As the <systemitem class="username">opensrf</systemitem> user, download and extract the source files for <application>OpenSRF</application> \r
-                               2.0:</para>\r
-<screen><userinput>\r
-wget http://open-ils.org/downloads/opensrf-2.0.1.tar.gz\r
-tar xzf opensrf-2.0.1.tar.gz\r
-</userinput></screen>\r
-                               <para>A new directory opensrf-2.0.1 is created.</para>\r
-                               <note><para>For the latest edition of OpenSRF, check the Evergreen download page at \r
-                               <ulink url="http://www.open-ils.org/downloads.php" />.\r
-                               </para></note>\r
-                       </step>\r
-                       <step>  \r
-                               <para>As the <systemitem class="username">root</systemitem> user, install the software prerequisites using the automatic \r
-                               prerequisite installer.</para> \r
-<screen><userinput>\r
-aptitude install make\r
-cd /home/opensrf/opensrf-2.0.1\r
-</userinput></screen>          \r
-                               <para>Replace <option>[distribution]</option> below with the following value \r
-                               for your distribution:</para>\r
-                               <itemizedlist>\r
-                                       <listitem>\r
-                                               <para><option>debian-squeeze</option> for <systemitem class="osname">Debian Squeeze (6.0)</systemitem>\r
-                                               <indexterm><primary>Linux</primary><secondary>Debian</secondary></indexterm></para>\r
-                                       </listitem>\r
-                                       <listitem>\r
-                                               <para><option>fedora13</option> for <systemitem class="osname">Fedora 13</systemitem>\r
-                                               <indexterm><primary>Linux</primary><secondary>Fedora</secondary></indexterm></para>\r
-                                       </listitem>                     \r
-                                       <listitem>\r
-                                               <para><option>ubuntu-lucid</option> for <systemitem class="osname">Ubuntu Lucid Lynx\r
-                                               (10.04)</systemitem><indexterm><primary>Linux</primary><secondary>Ubuntu</secondary></indexterm></para>\r
-                                       </listitem>\r
-                                       <listitem>\r
-                                               <para><option>centos</option> for <systemitem class="osname">CentOS 5</systemitem>\r
-                                               <indexterm><primary>Linux</primary><secondary>CentOS</secondary></indexterm></para>\r
-                                       </listitem>\r
-                                       <listitem>\r
-                                               <para><option>rhel</option> for <systemitem class="osname">Red Hat Enterprise Linux 5</systemitem>\r
-                                               <indexterm><primary>Linux</primary><secondary>Red Hat</secondary></indexterm></para>\r
-                                       </listitem>\r
-                               </itemizedlist>\r
-<screen><userinput>\r
-make -f src/extras/Makefile.install [distribution]\r
-</userinput></screen>\r
-                               <para>This will install a number of packages required by OpenSRF on your system, \r
-                               including some Perl modules from <systemitem class="resource">CPAN</systemitem><indexterm><primary>Perl</primary><secondary>CPAN</secondary>\r
-                               </indexterm>. You can type <userinput>no</userinput> to the initial <systemitem class="resource">CPAN</systemitem> \r
-                               configuration prompt to allow it to automatically configure itself to download \r
-                               and install Perl modules from <systemitem class="resource">CPAN</systemitem>. The <systemitem class="resource">CPAN</systemitem> installer will ask you a number of \r
-                               times whether it should install prerequisite modules - type <userinput>yes</userinput>.</para>\r
-                       </step>\r
-                       <step>  \r
-                               <para>As the <systemitem class="username">opensrf</systemitem> user, configure and compile OpenSRF:</para> \r
-                               <note>You can include the <option>–enable-python</option> and <option>–enable-java</option> configure options if \r
-                               you want to include support for Python<indexterm><primary>Python</primary></indexterm> and Java\r
-                               <indexterm><primary>Java</primary></indexterm>, respectively.</note>\r
-<screen><userinput>\r
-cd /home/opensrf/opensrf-2.0.1\r
-./configure --prefix=/openils --sysconfdir=/openils/conf\r
-make\r
-</userinput></screen>          \r
-                       </step>\r
-                       <step>  \r
-                               <para>As the <systemitem class="username">root</systemitem> user, return to your OpenSRF build directory and install \r
-                               OpenSRF:</para>\r
-<screen><userinput>\r
-cd /home/opensrf/opensrf-2.0.1\r
-make install\r
-</userinput></screen>\r
-                       </step>\r
-                       <step>\r
-                               <para>As the <systemitem class="username">root</systemitem> user, change the ownership of the installed files to the \r
-                               <systemitem class="username">opensrf</systemitem> user:</para>\r
-                               <screen><userinput>chown -R opensrf:opensrf /openils</userinput></screen>\r
-                       </step>                 \r
-                       <step>\r
-                               <para>Jot down the usernames/passwords of the two Jabber users created when OpenSRF was previously installed these users will correspond to \r
-                               entries in opensrf_core.xml. </para>\r
-                       </step>\r
-                       <step>\r
-                               <para>Important: Backup your current opensrf.xml and opensrf_core.xml configuration files.</para>\r
-<screen>\r
-<userinput>cp -p /openils/conf/opensrf.xml /openils/conf/opensrf.xml.backup</userinput>\r
-<userinput>cp -p /openils/conf/opensrf_core.xml /openils/conf/opensrf_core.xml.backup</userinput>\r
-</screen>\r
-                       </step>\r
-                       <step>\r
-                               <para>As the <systemitem class="username">opensrf</systemitem> user, copy the <filename>/openils/conf/opensrf_core.xml</filename> and \r
-                               <filename>/openils/conf/opensrf.xml</filename> configuration files from the example templates:</para>\r
-<screen>\r
-<userinput>cp /openils/conf/opensrf.xml.example /openils/conf/opensrf.xml</userinput>\r
-<userinput>cp /openils/conf/opensrf_core.xml.example /openils/conf/opensrf_core.xml</userinput>\r
-</screen>\r
-                               <para>Edit <filename>/openils/conf/opensrf_core.xml</filename> to change the Jabber usernames and passwords you jotted down earlier.</para> \r
-                       </step>\r
-                       <step>\r
-                               <para>As the <systemitem class="username">root</systemitem> user, Run the following command:</para>\r
-<screen>\r
-<userinput>ldconfig</userinput>\r
-</screen>\r
-                       </step>\r
-                       <step>\r
-                               <para>Restart and Test OpenSRF</para>\r
-<screen><userinput>\r
-osrf_ctl.sh -l -a start_all\r
-/openils/bin/srfsh\r
-srfsh#  request opensrf.math add 2 2\r
-</userinput></screen>\r
-                               <para>You should see output such as:</para>\r
-<screen>\r
-Received Data: 4\r
-\r
-------------------------------------\r
-Request Completed Successfully\r
-Request Time in seconds: 0.007519\r
-------------------------------------\r
-\r
-srfsh#\r
-</screen>      \r
-                       </step> \r
-                       <step>                  \r
-                               <para>If test completed successful restore your Evergreen configuration files:</para>\r
-<screen><userinput>\r
-cp /openils/conf/opensrf.xml.backup /openils/conf/opensrf.xml\r
-cp /openils/conf/opensrf_core.xml.backup /openils/conf/opensrf_core.xml\r
-</userinput></screen>\r
-               \r
-                               <para>and move on to the next section to upgrade Evergreen. Otherwise, refer to the <link linkend="troubleshooting">troubleshooting</link> chapter \r
-                               of this documentation.</para> \r
-                       </step> \r
-               </procedure>    \r
-       </section>\r
-       <section xml:id="upgradingevergreen-upgrading_from_1.6_to_2.0">\r
-               <title>Upgrade <application>Evergreen</application> from 1.6.1 to 2.0</title>\r
-               <note>\r
-                       <para>PostgreSQL 8.4 is the minimum supported version of PostgreSQL.</para> \r
-                       <para>Evergreen 2.0 has been tested on Debian Squeeze (6.0) and Ubuntu Lucid (10.04). If you are runnung an older version of \r
-                       these distributions, you may want to upgrade befor installing Evergreen 2.0. For instructions on upgrading these distribuitions, visit the \r
-                       <ulink url="http://www.debian.org/releases/squeeze/">Debian</ulink> or <ulink url="https://help.ubuntu.com/community/LucidUpgrades">Ubuntu</ulink> websites.</para>\r
-               </note>\r
-               <procedure>\r
-                       <step>\r
-                               <para>As the <systemitem class="username">opensrf</systemitem> user, download and extract <application>Evergreen 2.0</application>\r
-                               </para>\r
-<screen><userinput>\r
-wget http://www.open-ils.org/downloads/Evergreen-ILS-2.0.9.tar.gz\r
-tar xzf Evergreen-ILS-2.0.9.tar.gz\r
-</userinput></screen>\r
-                               <note><para>For the latest edition of Evergreen 2.0, check the Evergreen download page at\r
-                               <ulink url="http://www.open-ils.org/downloads.php" /> and adjust upgrading instructions accordingly.</para></note>\r
-                       </step>\r
-                       <step>\r
-                               <para>As the <systemitem class="username">root</systemitem> user, install the prerequisites:</para> \r
-                               <screen><userinput>cd /home/opensrf/Evergreen-ILS-2.0.9</userinput></screen>    \r
-                               <para>On the next command, replace <option>[distribution]</option> with one of \r
-                               these values for your distribution of Debian or Ubuntu:</para>\r
-                               <itemizedlist>\r
-                                       \r
-                                       <listitem>\r
-                                               <para><option>debian-squeeze</option> for <systemitem class="osname">Debian Squeeze (6.0)</systemitem></para>\r
-                                       </listitem>\r
-                                       \r
-                                       <listitem>\r
-                                               <para><option>ubuntu-lucid</option> for  <systemitem class="osname">Ubuntu Lucid Lynx \r
-                                               (10.04)</systemitem></para>\r
-                                       </listitem>\r
-                               </itemizedlist>\r
-                               <screen><userinput>make -f Open-ILS/src/extras/Makefile.install <option>[distribution]</option></userinput></screen>\r
-                       </step>\r
-                       <step>\r
-                               <para>As the <systemitem class="username">opensrf</systemitem> user, configure and compile \r
-                               <application>Evergreen</application>:</para>\r
-                               <screen><userinput>cd /home/opensrf/Evergreen-ILS-2.0.9</userinput></screen>\r
-                               <screen><userinput>./configure --prefix=/openils --sysconfdir=/openils/conf</userinput></screen>\r
-                               <screen><userinput>make</userinput></screen>\r
-                       </step>\r
-                       <step>\r
-                               <para>As the <systemitem class="username">root</systemitem> user, install \r
-                               <application>Evergreen</application>:</para>\r
-                               <screen><userinput>make STAFF_CLIENT_BUILD_ID=rel_2_0_9 install</userinput></screen>\r
-                       </step>\r
-                       <step>\r
-                               <para>As the <emphasis>root</emphasis> user, change all files to be owned by the \r
-                               <emphasis>opensrf</emphasis> user and group:</para>\r
-                               <screen><userinput>chown -R opensrf:opensrf /openils</userinput></screen>\r
-                       </step>                 \r
-                       <step>\r
-                               <para>As the <systemitem class="username">opensrf</systemitem> user, update server symlink in <filename class="directory">/openils/var/web/xul/</filename>:</para>\r
-<screen><userinput>\r
-cd /openils/var/web/xul/\r
-rm server\r
-ln -s rel_2_0_9/server\r
-</userinput></screen>\r
-                       </step>\r
-                       <step>\r
-                               <para>Change to the <application>Evergreen</application> installation \r
-                               directory:</para>\r
-                               <screen><userinput>cd /home/opensrf/Evergreen-ILS-2.0.9</userinput></screen>\r
-                       </step>\r
-\r
-                       <step>\r
-                               <para>Update the <database>evergreen</database> database:</para>\r
-                               <note><para>It is recommended that you <link linkend="backingup">back up your Evergreen database</link> in order to restore your data if anything goes wrong.</para></note>\r
-                               <note><para>The <filename>1.6.1-2.0-upgrade-db.sql</filename> upgrade script may take a long time (hours) to process \r
-                                 on larger systems.</para></note>\r
-<screen>\r
-<userinput>\r
-psql -U evergreen -h localhost -f Open-ILS/src/sql/Pg/1.6.1-2.0-upgrade-db.sql evergreen\r
-psql -U evergreen -h localhost -f Open-ILS/src/sql/Pg/2.0.0-2.0.1-upgrade-db.sql evergreen\r
-psql -U evergreen -h localhost -f Open-ILS/src/sql/Pg/2.0.1-2.0.2-upgrade-db.sql evergreen\r
-psql -U evergreen -h localhost -f Open-ILS/src/sql/Pg/2.0.2-2.0.3-upgrade-db.sql evergreen\r
-psql -U evergreen -h localhost -f Open-ILS/src/sql/Pg/2.0.3-2.0.4-upgrade-db.sql evergreen\r
-psql -U evergreen -h localhost -f Open-ILS/src/sql/Pg/2.0.4-2.0.5-upgrade-db.sql evergreen\r
-psql -U evergreen -h localhost -f Open-ILS/src/sql/Pg/2.0.5-2.0.6-upgrade-db.sql evergreen\r
-psql -U evergreen -h localhost -f Open-ILS/src/sql/Pg/2.0.6-2.0.7-upgrade-db.sql evergreen\r
-psql -U evergreen -h localhost -f Open-ILS/src/sql/Pg/2.0.7-2.0.8-upgrade-db.sql evergreen\r
-psql -U evergreen -h localhost -f Open-ILS/src/sql/Pg/2.0.8-2.0.9-upgrade-db.sql evergreen\r
-\r
-</userinput>\r
-</screen>      \r
-                             \r
-                       </step>\r
-<step>\r
-                               <para>Run the <filename>reingest-1.6-2.0.pl</filename> script to generate an sql script. Then use the sql file to reingest bib records into your \r
-                               <database>evergreen</database> database. This is required to make the new facet sidebar in OPAC search results work and to upgrade the keyword indexes to use \r
-                               the revised NACO normalization routine.</para>\r
-                               <note><para>If you are running a large Evergreen installation, it is recommend that you examine the script first. Reingesting a large number of bibliographic records \r
-                               may take several hours.</para></note>\r
-<screen><userinput>perl Open-ILS/src/sql/Pg/reingest-1.6-2.0.pl</userinput></screen>\r
-<screen><userinput>psql -U evergreen -h localhost -f Open-ILS/src/sql/Pg/reingest-1.6-2.0.sql evergreen</userinput></screen>\r
-                       </step>\r
-                       <step>\r
-                               <para>As the <systemitem class="username">opensrf</systemitem> user, \r
-                               copy <filename>/openils/conf/oils_web.xml.example</filename> to <filename>/openils/conf/oils_web.xml</filename>\r
-                               . (If upgrading from 1.6.1.x, <filename>oils_web.xml</filename> should already exist.)</para>\r
-                               <indexterm><primary>configuration files</primary><secondary>oils_web.xml</secondary></indexterm>\r
-                               <screen><userinput>cp /openils/conf/oils_web.xml.example /openils/conf/oils_web.xml</userinput></screen>\r
-                       </step>\r
-                       <step>\r
-                               <para>Update <filename>opensrf_core.xml</filename> and <filename>opensrf.xml</filename> by copying the new example files \r
-                               (<filename>/openils/conf/opensrf_core.xml.example</filename> and <filename>/openils/conf/opensrf.xml</filename>).</para>\r
-                               <indexterm><primary>configuration files</primary><secondary>opensrf.xml</secondary></indexterm>\r
-                               <screen><userinput>cp /openils/conf/opensrf_core.xml.example /openils/conf/opensrf_core.xml</userinput></screen>\r
-                               <indexterm><primary>configuration files</primary><secondary>opensrf_core.xml</secondary></indexterm>\r
-                               <screen><userinput>cp /openils/conf/opensrf.xml.example /openils/conf/opensrf.xml</userinput></screen>\r
-                               <caution><para>Copying these configuration files will remove any customizations you have made to them. Remember to redo your customizations after copying \r
-                               them.</para></caution>\r
-                       </step>\r
-                       <step>\r
-                               <para>Update <filename>opensrf.xml</filename> with the database connection info:</para>\r
-<screen><userinput>\r
-perl Open-ILS/src/support-scripts/eg_db_config.pl --update-config \\r
---service all --create-offline --user evergreen --password evergreen \ \r
---hostname localhost --port 5432 --database evergreen\r
-</userinput></screen>\r
-                       </step>\r
-                       <step>\r
-                               <para>Update /etc/apache2/startup.pl by copying the example from \r
-                               Open-ILS/examples/apache/startup.pl.</para><indexterm><primary>configuration files</primary><secondary>startup.pl</secondary></indexterm>\r
-                       </step>\r
-                       <step>\r
-                               <para>Update /etc/apache2/eg_vhost.conf by copying the example from \r
-                               Open-ILS/examples/apache/eg_vhost.conf.</para><indexterm><primary>configuration files</primary><secondary>eg_vhost.conf</secondary></indexterm>\r
-                       </step>\r
-                       <step>\r
-                       <para>Update /etc/apache2/sites-available/eg.conf by copying the example from Open-ILS/\r
-                       examples/apache/eg.conf.</para><indexterm><primary>configuration files</primary><secondary>eg.conf</secondary></indexterm>\r
-                       </step>\r
-                       <caution>\r
-                               <para>Copying these Apache configuration files will remove any customizations you have made to them. Remember to redo your customizations after copying \r
-                               them. For example, if you purchased an SSL certificate, you \r
-                               will need to edit <filename>eg.conf</filename> to point to the appropriate SSL certificate files.</para>\r
-                               <indexterm><primary>SSL</primary><secondary>certificates</secondary></indexterm>\r
-                       </caution> \r
-               </procedure>    \r
-       </section>\r
-       <section xml:id="testing_after_upgrade">\r
-               <title>Restart Evergreen and Test</title>\r
-               <procedure>\r
-                       <step>\r
-                               <para>As the <systemitem class="username">opensrf</systemitem> user, start all \r
-                               <application>Evergreen</application> and <application>OpenSRF</application> \r
-                               services:</para>\r
-                               <screen><userinput>osrf_ctl.sh -l -a start_all</userinput></screen>\r
-                       </step>\r
-                       <step>\r
-                               <para>As the <systemitem class="username">opensrf</systemitem> user, run <command>autogen</command> to refresh the static \r
-                               organizational data files:</para><indexterm><primary>autogen</primary></indexterm>\r
-<screen><userinput>\r
-cd /openils/bin\r
-./autogen.sh -c /openils/conf/opensrf_core.xml -u\r
-</userinput></screen>\r
-                                       \r
-                       </step>\r
-                       <step>\r
-                               <para>Start <command>srfsh</command> and try logging in  using your <application>Evergreen</application>\r
-                               username and password:</para>\r
-<screen>\r
-<userinput>/openils/bin/srfsh</userinput>\r
-<prompt>srfsh%</prompt> <userinput>login <option>username</option> <option>password</option></userinput>\r
-</screen> \r
-                       </step> \r
-                       <step>\r
-                               <para>Start the <application>Apache</application> web server.</para>\r
-                       </step>\r
-               </procedure>\r
-               <note>\r
-                       <para>If you encounter errors, refer to the <link linkend="troubleshooting">troubleshooting \r
-                       section</link> of this documentation for tips \r
-                       on finding solutions and seeking further assistance from the Evergreen community.</para>  \r
-               </note>\r
-       </section>\r
-<section xml:id="upgrading_Postgresqlto9.0">\r
-               <title>Upgrading PostgreSQL from 8.4 to 9.0</title>\r
-               <simplesect>\r
-                       <title>Upgrading PostgreSQL on Debian Squeez</title>\r
-                       <procedure>\r
-                               <step>\r
-                                       <para>Stop Evergreen and disconnect clients from database.</para>\r
-                               </step>                 \r
-                               <step>\r
-                                       <para>Add the following line to <filename>/etc/apt/sources.list</filename>:</para> \r
-<programlisting>\r
-deb http://www.backports.org/debian squeeze-backports main contrib non-free\r
-</programlisting>\r
-                               </step>\r
-                               <step>\r
-                                       <para>Update the sources list on your server.</para>\r
-<screen><userinput>                            \r
-apt-get update\r
-</userinput></screen>\r
-                               </step>\r
-                               <step>\r
-                                       <para>Backup your databases</para>\r
-<screen><userinput>                            \r
-$ pg_dump [db connect args] [db name] > evergreen-backup.sql\r
-</userinput></screen>\r
-                               </step>\r
-                               <step>\r
-                                       <para>Install PostgreSQL 9.0 as well as the client, contrib and plperl support packages.</para>\r
-<screen><userinput>                            \r
-apt-get -t squeeze-backports install postgresql-9.0 postgresql-client-9.0 postgresql-contrib-9.0 postgresql-plperl-9.0\r
-</userinput></screen>\r
-                               </step>\r
-                               <step>\r
-                                       <para>Drop the empty 9.0 cluster.</para>\r
-<screen><userinput>                            \r
-pg_dropcluster --stop 9.0 main\r
-</userinput></screen>\r
-                               </step>\r
-                               <step>\r
-                                       <para>Update the 8.4 cluster (with evergreen database) to 9.0</para>\r
-<screen><userinput>                            \r
-pg_upgradecluster 8.4 main\r
-</userinput></screen>\r
-                               </step>\r
-                               <step>\r
-                                       <para>Test by logging into psql, checking the postgrSQL version and running a simple SELECT query.</para>\r
-<screen><userinput>    \r
-psql -U evergreen                      \r
-evergreen=# select version();\r
-evergreen=# select count(*) from biblio.record_entry;\r
-</userinput></screen>\r
-                               </step>\r
-                               <step>\r
-                                       <para>Restart Evergreen and Apache.</para>\r
-                               </step>\r
-                               <step>\r
-                                       <para>Drop old 8.4 cluster (optional).</para>\r
-<screen><userinput>    \r
-pg_dropcluster 8.4 main\r
-</userinput></screen>\r
-                               </step>\r
-                       </procedure>\r
-               </simplesect>\r
-                       <simplesect>\r
-                       <title>Upgrading PostgreSQL on Ubuntu 10.04</title>\r
-                       <procedure>\r
-                               <step>\r
-                                       <para>Stop Evergreen and disconnect clients from database.</para>\r
-                               </step>                 \r
-                               <step>\r
-                                       <para>Add the backport repository to your repository sources list:</para> \r
-<screen><userinput>\r
-sudo add-apt-repository ppa:pitti/postgresql\r
-</userinput></screen>\r
-                               </step>\r
-                               <step>\r
-                                       <para>Update the sources list on your server.</para>\r
-<screen><userinput>                            \r
-apt-get update\r
-</userinput></screen>\r
-                               </step>\r
-                               <step>\r
-                                       <para>As the <systemitem class="username">postgres</systemitem> user, backup your PostgreSQL databases.</para>\r
-<screen><userinput><![CDATA[                           \r
-pg_dumpall > data\r
-]]></userinput></screen>\r
-                               </step>\r
-                               <step>\r
-                                       <para>As <systemitem class="username">root</systemitem>, remove PostgreSQL 8.4 and install 9.0.</para>\r
-<screen><userinput>                            \r
-aptitude purge postgresql-8.4\r
-aptitude install postgresql-9.0 postgresql-client-9.0 postgresql-contrib-9.0 postgresql-plperl-9.0\r
-</userinput></screen>\r
-                               </step>\r
-                               <step>\r
-                                       <para>as the <systemitem class="username">postgres</systemitem> user, recreate empty evergreen databases with required language supports.</para>\r
-<screen><userinput>\r
-dropdb evergreen\r
-createdb -T template0 --lc-ctype=C --lc-collate=C -E UNICODE evergreen\r
-createlang plperl   evergreen\r
-createlang plperlu  evergreen\r
-createlang plpgsql  evergreen\r
-psql -f /usr/share/postgresql/9.0/contrib/tablefunc.sql evergreen\r
-psql -f /usr/share/postgresql/9.0/contrib/tsearch2.sql  evergreen\r
-psql -f /usr/share/postgresql/9.0/contrib/pgxml.sql     evergreen\r
-</userinput></screen>\r
-                               </step>\r
-                               <step>\r
-                                       <para>Update the 8.4 cluster (with evergreen database) to 9.0.</para>\r
-<screen><userinput>                            \r
-pg_upgradecluster 8.4 main\r
-</userinput></screen>\r
-                               </step>\r
-                               <step>\r
-                                       <para>as the <systemitem class="username">postgres</systemitem> user, load data from backup into PostgreSQL 9.0.</para>\r
-<screen><userinput><![CDATA[                           \r
-psql < data\r
-]]></userinput></screen>\r
-                               </step>\r
-                               <step>\r
-                                       <para>Restart Evergreen and Apache.</para>\r
-                               </step>\r
-                               <step>\r
-                                       <para>Test by logging into psql, checking the postgrSQL version and running a simple SELECT query.</para>\r
-<screen><userinput>    \r
-psql -U evergreen                      \r
-evergreen=# select version();\r
-evergreen=# select count(*) from biblio.record_entry;\r
-</userinput></screen>\r
-                               </step>\r
-                       </procedure>\r
-               </simplesect>\r
-       </section>\r
-</chapter>\r
diff --git a/admin/acquisitions_admin_functions.xml b/admin/acquisitions_admin_functions.xml
deleted file mode 100644 (file)
index f3a5ccc..0000000
+++ /dev/null
@@ -1,625 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>\r
-<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"\r
-           xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="acquisitions-module_admin_functions">\r
-<info>\r
-       <title>Administration Functions in the Acquisitions Module</title>\r
-       <abstract>The following documentation is intended for users who will be managing funds and providers, managing EDI accounts, and creating drop  down menus for invoices and purchase orders. This \r
-       documentation will describe the purpose of each menu item in the Acquisitions menu in the Admin module and will present instructions for using each item. Front line processes are documented in The \r
-       Acquisitions Module. This document is intended for first time users of the Acquisitions module as well as those who are familiar with the module and need only a        reference guide. The \r
-       contents of this document are ordered such that one who is new to the Acquisitions module could read through this document and set up the administrative portion of Acquisitions in Evergreen.\r
-       </abstract>\r
-</info>\r
-<section id="acq_admin_currency_types">\r
-       <title>Currency Types</title>\r
-       <simpara>Currency types can be created and applied to funds in the administrative module.\r
-       When a fund is applied to a copy or line item for purchase, the item will be purchased in\r
-       the currency associated with that fund.</simpara>\r
-       <simplesect>\r
-               <title>Create a currency type</title>\r
-               <procedure>\r
-               <step><simpara>To create a new currency type, click Admin &#8594; Server Administration &#8594; Acquisitions&#8594; Currency types.</simpara></step>\r
-               <step><simpara>Enter the currency code. No limits exist on the number of characters that can be entered in this field.</simpara></step>\r
-               <step><simpara>Enter the name of the currency type in Currency Label field. No limits exist on the number of characters that can be entered in\r
-               this field.</simpara></step>\r
-               <step><simpara>Click Save.</simpara></step>\r
-               </procedure>\r
-       </simplesect>\r
-       <simplesect>\r
-               <title>Edit a currency type</title>\r
-               <procedure>\r
-               <step><simpara>To edit a currency type, click your cursor in the row that you want to edit. The row will turn blue.</simpara></step>\r
-               <step><simpara>Double-click. The pop-up box will appear, and you can edit the fields.</simpara></step>\r
-               <step><simpara>After making changes, click Save.</simpara></step>\r
-               </procedure>\r
-               <note><simpara>From the currency types interface, you can delete currencies that have never been applied to funds or used to make purchases.</simpara></note>\r
-       </simplesect>\r
-</section>\r
-<section id="acq_admin_exchange_rates">\r
-       <title>Exchange Rates</title>\r
-       <simpara>Exchange rates define the rate of exchange between currencies. Evergreen will automatically calculate exchange rates for purchases.\r
-       Evergreen assumes that the currency of the purchasing fund is identical to the currency of the provider, but it provides for two unique\r
-       situations:\r
-       If the currency of the fund that is used for the purchase is different from the currency of the provider as listed in the provider\r
-       profile, then Evergreen will use the exchange rate to calculate the price of the item in the currency of the fund and debit the fund\r
-       accordingly.\r
-       When money is transferred between funds that use different currency types, Evergreen will automatically use the exchange rate to convert\r
-       the money to the currency of the receiving fund. During such transfers, however, staff can override the automatic conversion by providing\r
-       an explicit amount to credit to the receiving fund.</simpara>\r
-       <simplesect>\r
-               <title>Create an exchange rate</title>\r
-               <procedure>\r
-               <step><simpara>To create a new exchange rate, click Admin &#8594; Server Administration &#8594; Acquisitions &#8594; Exchange Rates.</simpara></step>\r
-               <step><simpara>Click New Exchange Rate.</simpara></step>\r
-               <step><simpara>Enter the From Currency from the drop down menu populated by the currency types.</simpara></step>\r
-               <step><simpara>Enter the To Currency from the drop down menu populated by the currency types.</simpara></step>\r
-               <step><simpara>Enter the exchange Ratio.</simpara></step>\r
-               <step><simpara>Click Save.</simpara></step>\r
-               </procedure>\r
-       </simplesect>\r
-       <simplesect>\r
-               <title>Edit an Exchange Rate</title>\r
-               <simpara>Edit an exchange rate just as you would edit a currency type.</simpara>\r
-       </simplesect>\r
-</section>\r
-<section id="acq_admin_funding_sources">\r
-       <title>Funding Sources</title>\r
-       <simpara>Funding sources allow you to specify the sources that contribute monies to your fund(s). You can create as few or as many funding\r
-       sources as you need.</simpara>\r
-       <simplesect>\r
-               <title>Create a funding source</title>\r
-               <procedure>\r
-               <step><simpara>To create a new funding source, click Admin &#8594; Server Administration &#8594; Acquisitions &#8594; Funding Source.</simpara></step>\r
-               <step><simpara>Enter a funding source name. No limits exist on the number of characters that can be entered in this field.</simpara></step>\r
-               <step><simpara>Select an owner from the drop down menu. The owner indicates the organizational unit(s) whose staff can use this funding source.\r
-               This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See\r
-               Admin &#8594; Server Administration &#8594; Organizational Units).</simpara>\r
-               <note><para>The rule of parental inheritance applies to this list. For example, if a system is made the owner of a funding source,\r
-               then users with appropriate permissions at the branches within the system could also use the funding source.</para></note>\r
-               </step>\r
-               <step><simpara>Create a code for the source. No limits exist on the number of characters that can be entered in this field.</simpara></step>\r
-               <step><simpara>Select a currency from the drop down menu. This menu is populated from the choices in the Currency Types interface.</simpara></step>\r
-               <step><simpara>Click Save.</simpara></step>\r
-               </procedure>\r
-       </simplesect>\r
-       <simplesect>\r
-               <title>Allocate Credits to Funding Sources</title>\r
-               <procedure>\r
-               <step><simpara>Apply a credit to this funding source.</simpara></step>\r
-               <step><simpara>Enter the amount of money that the funding source contributes to the organization. Funding sources are not tied to fiscal\r
-               or calendar years, so you can continue to add money to the same funding source over multiple years, e.g. County\r
-               Funding. Alternatively, you can name funding sources by year, e.g. County Funding 2010 and County Funding 2011, and apply\r
-               credits each year to the matching source.</simpara></step>\r
-               <step><simpara>To apply a credit, click on the hyperlinked name of the funding source. The Funding Source Details will appear.</simpara></step>\r
-               <step><simpara>Click Apply credit.</simpara></step>\r
-               <step><simpara>Enter an amount to apply to this funding source.</simpara></step>\r
-               <step><simpara>Enter a note. This field is optional.</simpara></step>\r
-               <step><simpara>Click Apply.</simpara></step>\r
-               </procedure>\r
-       </simplesect>\r
-       <simplesect>\r
-               <title>Allocate credits to funds</title>\r
-               <simpara>If you have already set up your funds, then you can then click the Allocate to Fund button to apply credits from the\r
-               funding sources to the funds. If you have not yet set up your funds, or you need to add a new one, you can allocate\r
-               credits to funds from the funds interface. See section 1.2 for more information.</simpara>\r
-               <procedure>\r
-               <step><simpara>To allocate credits to funds, click Allocate to Fund.</simpara></step>\r
-               <step><simpara>Enter the amount that you want to allocate.</simpara></step>\r
-               <step><simpara>Enter a note. This field is optional.</simpara></step>\r
-               <step><simpara>Click Apply.</simpara></step>\r
-               </procedure>\r
-       </simplesect>\r
-       <simplesect>\r
-               <title>Track Debits and Credits</title>\r
-               <simpara>You can track credits to and allocations from each funding source. These amounts are updated when credits and allocations are\r
-               made in the Funding Source Details. Access the Funding Source Details by clicking on the hyperlinked name of the Funding Source.</simpara>\r
-       </simplesect>\r
-</section>\r
-<section id="acq_admin_fund_tags">\r
-       <title>Fund Tags</title>\r
-       <simpara>You can apply tags to funds so that you can group funds for easy reporting. For example, you have three funds for children’s materials: Children’s Board Books, Children’s DVDs, and \r
-       Children’s CDs. Assign a fund tag of “children’s” to each fund.\r
-       When you need to report on the amount that has been spent on all children’s materials,\r
-       you can run a report on the fund tag to find total expenditures on children’s materials\r
-       rather than reporting on each individual fund.</simpara>\r
-       <simplesect>\r
-               <title>Create a Fund Tag</title>\r
-               <procedure>\r
-               <step><simpara>To create a fund tag, click Admin &#8594; Server Administration &#8594; Acquisitions &#8594; Fund Tags.</simpara></step>\r
-               <step><simpara>Click New Fund Tag. No limits exist on the number of characters that can be entered in this field.</simpara></step>\r
-               <step><simpara>Select a Fund Tag Owner from the drop down menu. The owner indicates the organizational unit(s) whose staff can use this\r
-               fund tag. This menu is populated with the shortnames that you created for your libraries in the organizational units tree\r
-               (See Admin &#8594; Server Administration &#8594; Organizational Units).</simpara>\r
-               <note><simpara>The rule of parental inheritance applies to this list.</simpara></note></step>\r
-               <step><simpara>Enter a Fund Tag Name. No limits exist on the number of characters that can be entered in this field.</simpara></step>\r
-               <step><simpara>Click Save.</simpara></step>\r
-               </procedure>\r
-       </simplesect>\r
-</section>\r
-<section id="acq_admin_funds">\r
-       <title>Funds</title>\r
-       <simpara>Funds allow you to allocate credits toward specific purchases. In the funds interface,\r
-       you can create funds; allocate credits from funding sources to funds; transfer money\r
-       between funds; and apply fund tags to funds.\r
-       Funds are created for a specific year, either fiscal or calendar. These funds are owned\r
-       by org units. At the top of the funds interface, you can set a contextual org unit and\r
-       year. The drop down menu at the top of the screen enables you to focus on funds that\r
-       are owned by specific organizational units during specific years.</simpara>\r
-       <simplesect>\r
-               <title>Create a fund</title>\r
-               <procedure>\r
-               <step><simpara>To create a new fund, click Admin &#8594; Server Administration &#8594; Acquisitions &#8594; Funds.</simpara></step>\r
-               <step><simpara>Enter a name for the fund. No limits exist on the number of characters that can be entered in this field.</simpara></step>\r
-               <step><simpara>Create a code for the fund. No limits exist on the number of characters that can be entered in this field.</simpara></step>\r
-               <step><simpara>Enter a year for the fund. This can be a fiscal year or a calendar year. The format of the year is YYYY.</simpara></step>\r
-               <step><simpara>Select an org unit from the drop down menu. The org unit indicates the organizational units whose staff can use this fund. This menu is populated with the \r
-               shortnames that you created for your libraries in the organizational units tree (See Admin &#8594; Server Administration &#8594; Organizational Units).</simpara>\r
-               <note><simpara>The rule of parental inheritance applies to this list. See section</simpara></note></step>\r
-               <step><simpara>Select a currency type from the drop down menu. This menu is comprised of entries in the currency types menu. When a fund\r
-               is applied to a line item or copy, the price of the item will be encumbered in the currency associated with the fund.</simpara></step>\r
-               <step><simpara>Click the Active box to activate this fund. You cannot make purchases from this fund if it is not active.</simpara></step>\r
-               <step><simpara>Enter a Balance Stop Percent. The balance stop percent prevents you from making purchases when only a specified amount of the fund remains. For example, if \r
-               you want to spend 95 percent of your funds, leaving a five percent balance in the fund, then you would enter 95 in the field.  When the fund reaches its balance stop percent, \r
-               it will appear in red when you apply funds to copies.</simpara></step>\r
-               <step><simpara>Enter a Balance Warning Percent. The balance warning percent gives you a warning that the fund is low. You can specify any percent. For example, if you want to spend \r
-               90 percent of your funds and be warned when the fund has only 10 percent of its balance remaining, then enter 90 in the field. When the fund reaches its balance warning percent, it will \r
-               appear in yellow when you apply funds to copies.</simpara></step>\r
-               <step><simpara>Check the Propagate box to propagate funds. When you propagate a fund, the ILS will create a new fund for the following fisca \r
-               year with the same parameters as your current fund. All of the settings transfer except for the year and the amount of\r
-               money in the fund. Propagation occurs during the fiscal year close-out operation.</simpara></step>\r
-               <step><simpara>Check the Rollover box if you want to roll over remaining funds into the same fund next year.</simpara></step>\r
-               <step><simpara>Click Save.</simpara></step>\r
-               </procedure>\r
-       </simplesect>\r
-       <simplesect>\r
-               <title>Allocate Credits from Funding Sources to Funds</title>\r
-               <simpara>Credits can be applied to funds from funding sources using the fund interface. The\r
-               credits that you apply to the fund can be applied later to purchases.</simpara>\r
-               <procedure>\r
-               <step><simpara>To access funds, click Admin &#8594; Server Administration &#8594; Acquisitions &#8594; Funds.</simpara></step>\r
-               <step><simpara>Click the hyperlinked name of the fund.</simpara></step>\r
-               <step><simpara>To add a credit to the fund, click the Create Allocation tab.</simpara></step>\r
-               <step><simpara>Choose a Funding Source from the drop down menu.</simpara></step>\r
-               <step><simpara>Enter an amount that you want to apply to the fund from the funding source.</simpara></step>\r
-               <step><simpara>Enter a note. This field is optional.</simpara></step>\r
-               <step><simpara>Click Apply.</simpara></step>\r
-               </procedure>\r
-       </simplesect>\r
-       <simplesect>\r
-               <title>Transfer credits between funds</title>\r
-               <simpara>The credits that you allocate to funds can be transferred between funds if desired. In\r
-               the following example, you can transfer $500.00 from the Young Adult Fiction fund to\r
-               the Children’s DVD fund.</simpara>\r
-               <procedure>\r
-               <step><simpara>To access funds, click Admin &#8594; Server Administration &#8594; Acquisitions &#8594; Funds.</simpara></step>\r
-               <step><simpara>Click the hyperlinked name of the originating fund.</simpara></step>\r
-               <step><simpara>The Fund Details screen appears. Click Transfer Money.</simpara></step>\r
-               <step><simpara>Enter the amount that you would like to transfer.</simpara></step>\r
-               <step><simpara>From the drop down menu, select the destination fund.\r
-               </simpara></step>\r
-               <step><simpara>Add a note. This field is optional.</simpara></step>\r
-               <step><simpara>Click Transfer.</simpara></step>\r
-               </procedure>\r
-       </simplesect>\r
-       <simplesect>\r
-               <title>Track Balances and Expenditures</title>\r
-               <simpara>The Fund Details allows you to track the fund’s balance, encumbrances, and amount\r
-               spent. It also allows you to track allocations from the funding source(s), debits, and\r
-               fund tags.</simpara>\r
-               <procedure>\r
-               <step><simpara>To access the fund details, click on the hyperlinked name of the fund that you\r
-               created.</simpara></step>\r
-               <step><simpara>The Summary allows you to track the following:</simpara>\r
-                       <orderedlist numeration="loweralpha">\r
-                               <listitem><simpara>Balance – The balance is calculated by subtracting both items that have been\r
-                               invoiced and encumbrances from the total allocated to the fund.</simpara></listitem>\r
-                               <listitem><simpara>Total Allocated – This amount is the total amount allocated from the Funding\r
-                               Source.</simpara></listitem>\r
-                               <listitem><simpara>Spent Balance – This balance is calculated by subtracting only the items that\r
-                               have been invoiced from the total allocated to the fund. It does not include\r
-                               encumbrances.</simpara></listitem>\r
-                               <listitem><simpara>Total Debits – The total debits are calculated by adding the cost of items that\r
-                               have been invoiced and encumbrances.</simpara></listitem>\r
-                               <listitem><simpara>Total Spent – The total spent is calculated by adding the cost of items that\r
-                               have been invoiced. It does not include encumbrances.</simpara></listitem>\r
-                               <listitem><simpara>Total Encumbered – The total encumbered is calculated by adding all\r
-                               encumbrances.</simpara></listitem>\r
-                       </orderedlist>\r
-               </step>\r
-               </procedure>\r
-       </simplesect>\r
-       <simplesect>\r
-               <title>Edit a Fund</title>\r
-               <simpara>Edit a fund just as you would edit a currency type.</simpara>\r
-       </simplesect>\r
-       <simplesect>\r
-               <title>Perform Year End Closeout Operation</title>\r
-               <simpara>The Year End Closeout Operation allows you to deactivate funds for the current year\r
-               and create analogous funds for the next year. It transfers encumbrances to the\r
-               analogous funds, and it rolls over any remaining funds if you checked the rollover box\r
-               when creating the fund.</simpara>\r
-               <procedure>\r
-               <step><simpara>To access the year end closeout of a fund, click Admin &#8594; Server Administration &#8594;\r
-               Acquisitions &#8594; Funds.</simpara></step>\r
-               <step><simpara>Click Fund Propagation and Rollover.</simpara></step>\r
-               <step><simpara>Check the box adjacent to Perform Fiscal Year Close-Out Operation.</simpara></step>\r
-               <step><simpara>Notice that the context org unit reflects the context org unit that you selected at\r
-               the top of the Funds screen.</simpara></step>\r
-               <step><simpara>If you want to perform the close-out operation on the context org unit and its child\r
-               units, then check the box adjacent to Include Funds for Descendant Org Units.</simpara></step>\r
-               <step><simpara>Check the box adjacent to dry run if you want to test changes to the funds before\r
-               they are enacted. Evergreen will generate a summary of the changes that would\r
-               occur during the selected operations. No data will be changed.</simpara></step>\r
-               <step><simpara>Click Process.</simpara></step>\r
-               <step><simpara>Evergreen will begin the propagation process. Evergreen will make a clone of each\r
-               fund, but it will increment the year by   .</simpara></step>\r
-               </procedure>\r
-       </simplesect>\r
-</section>\r
-<section id="acq_admin_providers">\r
-       <title>Providers</title>\r
-       <simpara>Providers are vendors. You can create a provider profile that includes contact\r
-       information for the provider, holdings information, invoices, and other information.</simpara>\r
-       <simplesect>\r
-               <title>Create a provider</title>\r
-               <procedure>\r
-               <step><simpara>To create a new provider, click Admin &#8594; Server Administration &#8594;Acquisitions &#8594;\r
-               Providers.</simpara></step>\r
-               <step><simpara>Enter the provider name.</simpara></step>\r
-               <step><simpara>Create a code for the provider. No limits exist on the number of characters that can\r
-               be entered in this field.</simpara></step>\r
-               <step><simpara>Select an owner from the drop down menu. The owner indicates the organizational units whose staff can use this provider. This menu is populated with the shortnames \r
-               that you created for your libraries in the organizational units tree (See Admin &#8594; Server Administration &#8594; Organizational Units).</simpara>\r
-               <note><simpara>The rule of parental inheritance applies to this list. See section   .1\r
-               for more information.</simpara></note></step>\r
-               <step><simpara>Select a currency from the drop down menu. This drop down list is populated by the\r
-               list of currencies available in the currency types.</simpara></step>\r
-               <step><simpara>A provider must be active in order for purchases to be made from that provider. To\r
-               activate the provider, check the box adjacent to Active. To deactivate a vendor,\r
-               uncheck the box.</simpara></step>\r
-               <step><simpara>Select a default claim policy from the drop down box. This list is derived from the\r
-               claim policies that can be created</simpara></step>\r
-               <step><simpara>Select an EDI default. This list is derived from the EDI accounts that can be created.</simpara></step>\r
-               <step><simpara>Enter the provider’s email address.</simpara></step>\r
-               <step><simpara>In the Fax Phone field, enter the provider’s fax number.</simpara></step>\r
-               <step><simpara>In the holdings tag field, enter the tag in which the provider places holdings data.</simpara></step>\r
-               <step><simpara>In the phone field, enter the provider’s phone number.</simpara></step>\r
-               <step><simpara>If prepayment is required to purchase from this provider, then check the box\r
-               adjacent to prepayment required.</simpara></step>\r
-               <step><simpara>Enter the Standard Address Number (SAN) for your provider.</simpara></step>\r
-               <step><simpara>Enter the web address for the provider’s website in the URL field.</simpara></step>\r
-               <step><simpara>Click Save.</simpara></step>\r
-               </procedure>\r
-       </simplesect>\r
-       <simplesect>\r
-               <title>Add contact and holdings information to providers</title>\r
-               <simpara>After you save the provider profile, the screen reloads so that you can save additional\r
-               information about the provider. You can also access this screen by clicking the\r
-               hyperlinked name of the provider on the Providers screen. The tabs allow you to add a\r
-               provider address and contact, attribute definitions, and holding subfields. You can also\r
-               view invoices associated with the provider.</simpara>\r
-               <procedure>\r
-               <step><simpara>Enter a Provider Address, and click Save.</simpara>\r
-               <note><simpara>Required fields for the provider address are: Street 1, city, state,\r
-               country, post code. You may have multiple valid addresses.</simpara></note></step>\r
-               <step><simpara>Enter the Provider Contact, and click Save.</simpara></step>\r
-               <step><simpara>Your vendor may include information that is specific to your organization in MARC\r
-               tags. You can specify the types of information that should be entered in each MARC\r
-               tag. Enter attribute definitions to correlate MARC tags with the information that\r
-               they should contain in incoming vendor records. Some technical knowledge is\r
-               required to enter XPath information.</simpara></step>\r
-               <step><simpara>You may have entered a holdings tag when you created the provider profile. You\r
-               can also enter holdings subfields. Holdings subfields allow you to specify subfields\r
-               within the holdings tag to which your vendor adds holdings information.</simpara></step>\r
-               <step><simpara>Click invoices to access invoices associated with a provider.</simpara></step>\r
-               </procedure>\r
-       </simplesect>\r
-       <simplesect>\r
-               <title>Edit a provider</title>\r
-               <simpara>Edit a provider just as you would edit a currency type.</simpara>\r
-               <note><simpara>You can delete providers only if no purchase orders have been assigned\r
-               to them.</simpara></note>\r
-       </simplesect>\r
-</section>\r
-<section id="acq_admin_edi">\r
-       <title>EDI</title>\r
-       <simpara>Many libraries use Electronic Data Interchange (EDI) accounts to order new acquisitions.\r
-       In Evergreen 2.0, users can set up EDI accounts and manage EDI messages in the admin\r
-       module. EDI messages and notes can be viewed in the acquisitions module.</simpara>\r
-       <note><simpara>The following fields are required to create an EDI account: host,\r
-       username, password, path, and incoming directory.</simpara></note>\r
-       <simplesect>\r
-               <title>EDI Accounts</title>\r
-               <simpara>Create EDI Accounts to communicate electronically with providers.</simpara>\r
-               <procedure>\r
-               <step><simpara>Create a label. The label allows you to differentiate between accounts for the same\r
-               provider. No limits exist on the number of characters that can be entered in this\r
-               field.</simpara></step>\r
-               <step><simpara>Enter a host. Your provider will provide you with the requisite FTP or SCP\r
-               information.</simpara></step>\r
-               <step><simpara>Enter the username that has been supplied by your provider.</simpara></step>\r
-               <step><simpara>Enter the password that has been supplied by your provider.</simpara></step>\r
-               <step><simpara>Enter account information. This field enables you to add a supplemental password\r
-               for entry to a remote system after log in has been completed. This field is optional\r
-               for the ILS but may be required by your provider.</simpara></step>\r
-               <step><simpara>Select an owner from the drop down menu. The owner indicates the organizational\r
-               units whose staff can use this EDI account. This menu is populated with the\r
-               shortnames that you created for your libraries in the organizational units tree (See\r
-               Admin &#8594; Server Administration &#8594; Organizational Units).</simpara>\r
-               <note><simpara>The rule of parental inheritance applies to this list.</simpara></note></step>\r
-               <step><simpara>The Last Activity updates automatically with any inbound or outbound\r
-               communication.</simpara></step>\r
-               <step><simpara>Select a provider from the drop down menu to whom this account belongs.</simpara></step>\r
-               <step><simpara>Enter a path. The path indicates the remote location on the server from which files\r
-               are pulled in to the ILS.</simpara></step>\r
-               <step><simpara>Enter the incoming directory. This directory indicates the location on your local\r
-               network to which the files download.</simpara></step>\r
-               <step><simpara>Enter the vendor account number supplied by your provider.</simpara></step>\r
-               <step><simpara>Enter the vendor account code supplied by your provider.</simpara></step>\r
-               <step><simpara>Click Save.</simpara></step>\r
-               </procedure>\r
-       </simplesect>\r
-       <simplesect>\r
-               <title>EDI Messages</title>\r
-               <simpara>The EDI messages screen displays all incoming and outgoing messages between the\r
-               library and the vendor.</simpara>\r
-       </simplesect>\r
-</section>\r
-<section id="acq_admin_claiming">\r
-       <title>Claiming</title>\r
-       <simpara>Evergreen 2.0 provides minimal claiming functionality. Currently, all claiming is manual,\r
-       but the admin module enables you to build claim policies and specify the action(s) that\r
-       users should take to claim items.</simpara>\r
-       <simplesect>\r
-               <title>Create a claim policy</title>\r
-               <simpara>The claim policy link enables you to name the claim policy and specify the organization\r
-               that owns it.</simpara>\r
-               <procedure>\r
-               <step><simpara>To create a claim policy, click Admin &#8594; Server Administration &#8594; Acquisitions &#8594;\r
-               Claim Policies.</simpara></step>\r
-               <step><simpara>Create a claim policy name. No limits exist on the number of characters that can be\r
-               entered in this field.</simpara></step>\r
-               <step><simpara>Select an org unit from the drop down menu. The org unit indicates the\r
-               organizational units whose staff can use this claim policy. This menu is populated\r
-               with the shortnames that you created for your libraries in the organizational units\r
-               tree (See Admin &#8594; Server Administration &#8594; Organizational Units).</simpara>\r
-               <note><simpara>The rule of parental inheritance applies to this list.</simpara></note></step>\r
-               <step><simpara>Enter a description. No limits exist on the number of characters that can be entered\r
-               in this field.</simpara></step>\r
-               <step><simpara>Click Save.</simpara></step>\r
-               </procedure>\r
-       </simplesect>\r
-       <simplesect>\r
-               <title>Create a claim type</title>\r
-               <simpara>The claim type link enables you to specify the reason for a type of claim.</simpara>\r
-               <procedure>\r
-               <step><simpara>To create a claim type, click Admin &#8594; Server Administration &#8594; Acquisitions &#8594;\r
-               Claim types.</simpara></step>\r
-               <step><simpara>Create a claim type. No limits exist on the number of characters that can be entered\r
-               in this field.</simpara></step>\r
-               <step><simpara>Select an org unit from the drop down menu. The org unit indicates the\r
-               organizational units whose staff can use this claim type. This menu is populated\r
-               with the shortnames that you created for your libraries in the organizational units\r
-               tree (See Admin &#8594; Server Administration &#8594; Organizational Units).</simpara>\r
-               <note><simpara>The rule of parental inheritance applies to this list.</simpara></note></step>\r
-               <step><simpara>Enter a description. No limits exist on the number of characters that can be entered\r
-               in this field.</simpara></step>\r
-               <step><simpara>Click Save.</simpara></step>\r
-               </procedure>\r
-       </simplesect>\r
-       <simplesect>\r
-               <title>Create a claim event type</title>\r
-               <simpara>The claim event type describes the physical action that should occur when an item\r
-               needs to be claimed. For example, the user should notify the vendor via email that the\r
-               library is claiming an item.</simpara>\r
-               <procedure>\r
-               <step><simpara>To access the claim event types, click Admin &#8594; Server Administration &#8594;\r
-               Acquisitions &#8594;Claim event type.</simpara></step>\r
-               <step><simpara>Enter a code for the claim event type. No limits exist on the number of characters\r
-               that can be entered in this field.</simpara></step>\r
-               <step><simpara>Select an org unit from the drop down menu. The org unit indicates the\r
-               organizational units whose staff can use this event type. This menu is populated\r
-               with the shortnames that you created for your libraries in the organizational units\r
-               tree (See Admin &#8594; Server Administration &#8594; Organizational Units).</simpara>\r
-               <note><simpara>The rule of parental inheritance applies to this list.</simpara></note></step>\r
-               <step><simpara>Enter a description. No limits exist on the number of characters that can be entered\r
-               in this field.</simpara></step>\r
-               <step><simpara>If this claim is initiated by the user, then check the box adjacent to Library Initiated.</simpara>\r
-               <note><simpara>Currently, all claims are initiated by a user. The ILS cannot automatically\r
-               claim an issue.</simpara></note></step>\r
-               <step><simpara>Click Save.</simpara></step>\r
-               </procedure>\r
-       </simplesect>\r
-       <simplesect>\r
-               <title>Create a claim policy action</title>\r
-               <simpara>The claim policy action enables you to specify how long a user should wait before\r
-               claiming the item.</simpara>\r
-               <procedure>\r
-               <step><simpara>To access claim policy actions, click Admin &#8594; Server Administration &#8594; Acquisitions\r
-               &#8594;Claim Policy Actions.</simpara></step>\r
-               <step><simpara>Select an Action (Event Type) from the drop down menu.</simpara></step>\r
-               <step><simpara>Enter an action interval. This field indicates how long a user should wait before\r
-               claiming the item.</simpara></step>\r
-               <step><simpara>In the Claim Policy ID field, select a claim policy from the drop down menu.</simpara></step>\r
-               <step><simpara>Click Save.</simpara></step>\r
-               </procedure>\r
-               <note><simpara>You can create claim cycles by adding multiple claim policy actions to a\r
-               claim policy.</simpara></note>\r
-       </simplesect>\r
-</section>\r
-<section id="acq_admin_invoice_menus">\r
-       <title>Invoice menus</title>\r
-       <simpara>Invoice menus allow you to create drop down menus that appear on invoices. You can\r
-       create an invoice item type or invoice payment method.</simpara>\r
-       <simplesect>\r
-               <title>Invoice item type</title>\r
-               <simpara>The invoice item type allows you to enter the types of additional charges that you can\r
-               add to an invoice. Examples of additional charge types might include taxes or\r
-               processing fees. Charges for bibliographic items are listed separately from these\r
-               additional charges. A default list of charge types displays, but you can add custom\r
-               charge types to this list.\r
-               Invoice item types can also be used when adding non-bibliographic items to a purchase\r
-               order. When invoiced, the invoice item type will copy from the purchase order to the\r
-               invoice.</simpara>\r
-               <procedure>\r
-               <step><simpara>To create a new charge type, click Admin &#8594; Server Administration &#8594; Acquisitions\r
-               &#8594; Invoice Item Type.</simpara></step>\r
-               <step><simpara>Click New Invoice Item Type.</simpara></step>\r
-               <step><simpara>Create a code for the charge type. No limits exist on the number of characters that\r
-               can be entered in this field.</simpara></step>\r
-               <step><simpara>Create a label. No limits exist on the number of characters that can be entered in\r
-               this field. The text in this field appears in the drop down menu on the invoice.</simpara></step>\r
-               <step><simpara>If items on the invoice were purchased with the monies in multiple funds, then you\r
-               can divide the additional charge across funds. Check the box adjacent to Prorate? if\r
-               you want to prorate the charge across funds.</simpara></step>\r
-               <step><simpara>Click Save.</simpara></step>\r
-               </procedure>\r
-       </simplesect>\r
-</section>\r
-<section id="acq_admin_invoice_payment_method">\r
-       <title>Invoice payment method</title>\r
-       <simpara>The invoice payment method allows you to predefine the type(s) of invoices and\r
-       payment method(s) that you accept. The text that you enter in the admin module will\r
-       appear as a drop down menu in the invoice type and payment method fields on the\r
-       invoice.</simpara>\r
-       <procedure>\r
-       <step><simpara>To create a new invoice payment method, click Admin &#8594; Server Administration &#8594;\r
-       Acquisitions &#8594; Invoice Payment Method.</simpara></step>\r
-       <step><simpara>Click New Invoice Payment Method.</simpara></step>\r
-       <step><simpara>Create a code for the invoice payment method. No limits exist on the number of\r
-       characters that can be entered in this field.</simpara></step>\r
-       <step><simpara>Create a name for the invoice payment method. No limits exist on the number of\r
-       characters that can be entered in this field. The text in this field appears in the drop\r
-       down menu on the invoice.</simpara></step>\r
-       <step><simpara>Click Save.</simpara></step>\r
-       </procedure>\r
-</section>\r
-<section id="acq_admin_distribution_formulas">\r
-       <title>Distribution Formulas</title>\r
-       <simpara>Distribution formulas allow you to specify the number of copies that should be\r
-       distributed to specific branches. You can create and reuse formulas as needed.</simpara>\r
-       <simplesect>\r
-               <title>Create a distribution formula</title>\r
-               <procedure>\r
-               <step><simpara>Click Admin &#8594; Server Administration &#8594; Acquisitions &#8594;Distribution Formulas.</simpara></step>\r
-               <step><simpara>Click New Formula.</simpara></step>\r
-               <step><simpara>Enter a Formula Name. No limits exist on the number of characters that can be\r
-               entered in this field.</simpara></step>\r
-               <step><simpara>Choose a Formula Owner from the drop down menu. The Formula Owner indicates\r
-               the organizational units whose staff can use this formula. This menu is populated\r
-               with the shortnames that you created for your libraries in the organizational units\r
-               tree (See Admin &#8594; Server Administration &#8594; Organizational Units).</simpara>\r
-               <note><simpara>The rule of parental inheritance applies to this list.</simpara></note></step>\r
-               <step><simpara>Ignore the Skip Count field. It has no purpose in 2.0.</simpara></step>\r
-               <step><simpara>Click Save.</simpara></step>\r
-               <step><simpara>Click New Entry.</simpara></step>\r
-               <step><simpara>Select an Owning Library from the drop down menu. This indicates the branch that\r
-               will receive the items. This menu is populated with the shortnames that you created\r
-               for your libraries in the organizational units tree (See Admin &#8594; Server\r
-               Administration &#8594; Organizational Units).</simpara></step>\r
-               <step><simpara>Select a Shelving Location from the drop down menu.</simpara></step>\r
-               <step><simpara>In the Item Count field, enter the number of items that should be distributed to the\r
-               branch. You can enter the number or use the arrows on the right side of the field.</simpara></step>\r
-               <step><simpara>Click Apply Changes. The screen will reload.</simpara></step>\r
-               <step><simpara>To view the changes to your formula, click Admin &#8594; Server Administration &#8594;\r
-               Acquisitions &#8594; Distribution Formulas. The item_count will reflect the entries to\r
-               your distribution formula.</simpara></step>\r
-               </procedure>\r
-               <note><simpara>To edit the Formula Name, click the hyperlinked name of the formula in\r
-               the top left corner. A pop up box will enable you to enter a new formula\r
-               name.</simpara></note>\r
-       </simplesect>\r
-       <simplesect>\r
-               <title>Edit a distribution formula</title>\r
-               <simpara>To edit a distribution formula, click the hyperlinked title of the formula.</simpara>\r
-       </simplesect>\r
-</section>\r
-<section id="acq_admin_line_item_features">\r
-       <title>Line item features</title>\r
-       <simpara>Line item alerts are predefined text that can be added to line items that are on selection\r
-       lists or purchase orders. You can define the alerts from which staff can choose. Line\r
-       item alerts appear in a pop up box when the line item, or any of its copies, are marked\r
-       as received.</simpara>\r
-       <simplesect>\r
-               <title>Create a line item alert</title>\r
-               <procedure>\r
-               <step><simpara>To create a line item alert, click Administration &#8594; Server Administration &#8594;\r
-               Acquisitions &#8594; Line Item Alerts.</simpara></step>\r
-               <step><simpara>Click New Line Item Alert Text.</simpara></step>\r
-               <step><simpara>Create a code for the text. No limits exist on the number of characters that can be\r
-               entered in this field.</simpara></step>\r
-               <step><simpara>Create a description for the text. No limits exist on the number of characters that can\r
-               be entered in this field.</simpara></step>\r
-               <step><simpara>Select an owning library from the drop down menu. The owning library indicates the\r
-               organizational units whose staff can use this alert. This menu is populated with the\r
-               shortnames that you created for your libraries in the organizational units tree (See\r
-               Admin &#8594; Server Administration &#8594; Organizational Units).\r
-               </simpara></step>\r
-               <step><simpara>Click Save.</simpara></step>\r
-               </procedure>\r
-       </simplesect>\r
-</section>\r
-<section id="acq_admin_line_item_marc_attribute_definitions">\r
-       <title>Line Item MARC Attribute Definitions</title>\r
-       <simpara>Line item attributes define the fields that Evergreen needs to extract from the\r
-       bibliographic records that are in the acquisitions database to display in the catalog.\r
-       Also, these attributes will appear as fields in the New Brief Record interface. You will be\r
-       able to enter information for the brief record in the fields where attributes have been\r
-       defined.</simpara>\r
-</section>\r
-<section id="acq_admin_cancel_suspend_reasons">\r
-       <title>Cancel/Suspend reasons</title>\r
-       <simpara>The Cancel reasons link enables you to predefine the reasons for which a line item or a\r
-       PO can be cancelled. A default list of reasons appears, but you can add custom reasons\r
-       to this list.\r
-       Applying the cancel reason will prevent the item from appearing in a claims list and will\r
-       allow you to cancel debits associated with the purchase.\r
-       Cancel reasons also enable you to suspend or delay a purchase. For example, you could\r
-       create a cancel reason of “back ordered,” and you could choose to keep the debits\r
-       associated with the purchase.</simpara>\r
-       <simplesect>\r
-               <title>Create a cancel/suspend reason</title>\r
-               <procedure>\r
-               <step><simpara>To add a new cancel reason, click Administration &#8594; Server Administration &#8594;\r
-               Acquisitions &#8594; Cancel reasons.</simpara></step>\r
-               <step><simpara>Click New Cancel Reason.</simpara></step>\r
-               <step><simpara>Select a using library from the drop down menu. The using library indicates the\r
-               organizational units whose staff can use this cancel reason. This menu is populated\r
-               with the shortnames that you created for your libraries in the organizational units\r
-               tree (See Admin &#8594; Server Administration &#8594; Organizational Units.)</simpara></step>\r
-               <step><simpara>Create a label for the cancel reason. This label will appear when you select a cancel\r
-               reason on an item or a PO.</simpara></step>\r
-               <step><simpara>Create a description of the cancel reason. This is a free text field and can be\r
-               comprised of any text of your choosing.</simpara></step>\r
-               <step><simpara>If you want to retain the debits associated with the cancelled purchase, click the box\r
-               adjacent to Keep Debits?</simpara></step>\r
-               <step><simpara>Click Save.</simpara></step>\r
-               </procedure>\r
-       </simplesect>\r
-</section>\r
-<section id="acq_admin_acquisitions_permissions_in_the_admin_module">\r
-       <title>Acquisitions Permissions in the Admin module</title>\r
-       <simpara>Several setting in the Library Settings area of the Admin module pertain to functions in\r
-       the Acquisitions module. You can access these settings by clicking Admin &#8594; Local\r
-       Administration &#8594;Library Settings Editor.</simpara>\r
-       <itemizedlist>\r
-       <listitem><simpara>CAT: Delete bib if all copies are deleted via Acquisitions lineitem cancellation – If\r
-       you cancel a line item, then all of the on order copies in the catalog are deleted. If,\r
-       when you cancel a line item, you also want to delete the bib record, then set this\r
-       setting to TRUE.</simpara></listitem>\r
-       <listitem><simpara>Default circulation modifier – This modifier would be applied to items that are\r
-       created in the acquisitions module</simpara></listitem>\r
-       <listitem><simpara>Default copy location – This copy location would be applied to items that are\r
-       created in the acquisitions module</simpara></listitem>\r
-       <listitem><simpara>Fund Spending Limit for Block - When the amount remaining in the fund, including\r
-       spent money and encumbrances, goes below this percentage, attempts to spend\r
-       from the fund will be blocked.</simpara></listitem>\r
-       <listitem><simpara>Fund Spending Limit for Warning - When the amount remaining in the fund,\r
-       including spent money and encumbrances, goes below this percentage, attempts to\r
-       spend from the fund will result in a warning to the staff.</simpara></listitem>\r
-       <listitem><simpara>Temporary barcode prefix - Temporary barcode prefix for items that are created in\r
-       the acquisitions module</simpara></listitem>\r
-       <listitem><simpara>Temporary call number prefix - Temporary call number prefix for items that are\r
-       created in the acquisitions module</simpara></listitem>\r
-       </itemizedlist>\r
-</section>\r
-</chapter>\r
diff --git a/admin/actiontriggers.xml b/admin/actiontriggers.xml
deleted file mode 100644 (file)
index adeb6f2..0000000
+++ /dev/null
@@ -1,314 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>\r
-<chapter xml:id="actiontriggers" xmlns="http://docbook.org/ns/docbook" version="5.0" xml:lang="EN"\r
-    xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:xlink="http://www.w3.org/1999/xlink">\r
-    <info>\r
-        <title>Action Triggers</title>\r
-       <indexterm><primary>action triggers</primary></indexterm>    \r
-       </info>\r
-       <para>Action Triggers were introduced to Evergreen in 1.6. They allow administrators the ability to set up actions for specific events. They are useful for notification events such as \r
-       hold notifications.</para>\r
-       \r
-                       \r
-       <para>To access the Action Triggers module, select\r
-               <menuchoice>\r
-                       <guimenu>Admin</guimenu>  \r
-                       <guisubmenu>Local Administration</guisubmenu>\r
-                       <guisubmenu>Notifications / Action triggers</guisubmenu>\r
-               </menuchoice>\r
-       </para>\r
-       <note><para>You must have Local Administrator permissions to access the Action Triggers module.</para></note>\r
-       <para>You will notice four tabs on this page: <guilabel><link linkend="eventdefinitions">Event Definitions</link></guilabel>, <guilabel><link linkend="Hooks">Hooks</link></guilabel>, \r
-       <guilabel><link linkend="Reactors">Reactors</link></guilabel> and <guilabel><link linkend="Validators">Validators</link></guilabel>.</para>\r
-               \r
-       <section xml:id="eventdefinitions">\r
-               <title>Event Definitions</title>\r
-               <indexterm><primary>action triggers</primary><secondary>event definitions</secondary></indexterm>   \r
-               <para><guilabel>Event Definitions</guilabel> is the main tab and contains the key fields when working with action triggers. These fields include:</para>\r
-                       <table xml:id="eventdefinitionstable">\r
-                               <title>Action Trigger Event Definitions</title>\r
-                               <tgroup cols="2">\r
-                                       <colspec colnum="1" colname="col1" colwidth="1.0*"/>\r
-                                       <colspec colnum="2" colname="col2" colwidth="3.0*"/>\r
-                                       <thead>\r
-                                               <row>\r
-                                                       <entry>Field</entry>\r
-                                                       <entry>Description</entry>\r
-                                               </row>\r
-                                       </thead>\r
-                                       <tbody>\r
-                                               <row>\r
-                                                       <entry><guilabel>Owning library</guilabel></entry>\r
-                                                       <entry>The shortname of the library for which the action / trigger / hook is defined.</entry>\r
-                                               </row>\r
-                                               <row>\r
-                                                       <entry><guilabel>Name</guilabel></entry>\r
-                                                       <entry>The name of the trigger event, that links to a trigger event environment containing a set of fields  \r
-                                                       that will be returned to the <link linkend="Validators">Validators</link> / <link linkend="Reactors">Reactors</link> for processing.</entry>\r
-                                               </row>\r
-                                               <row>\r
-                                                       <entry><guilabel><link linkend="Hooks">Hooks</link></guilabel></entry>\r
-                                                       <entry>The name of the trigger for the trigger event. The underlying action_trigger.hook table defines the Fieldmapper \r
-                                                       class in the core_type column off of which the rest of the field definitions <quote>hang</quote>. </entry>\r
-                                               </row>\r
-                                               <row>\r
-                                                       <entry><guilabel>Enabled</guilabel></entry>\r
-                                                       <entry>Sets the given trigger as enabled or disabled. This must be set to enabled for the Action trigger to run.</entry>\r
-                                               </row>\r
-                                               <row>\r
-                                                       <entry><guilabel>Processing Delay</guilabel></entry>\r
-                                                       <entry>Defines how long after a given trigger / hook event has occurred before the associated action (<quote>Reactor</quote>) \r
-                                                       will be taken.</entry>\r
-                                               </row>\r
-                                               <row>\r
-                                                       <entry><guilabel>Processing Delay Field</guilabel></entry>\r
-                                                       <entry>Defines the field associated with the event on which the processing delay is calculated. For example, the processing delay \r
-                                                       context field on the hold.capture hook (which has a core_type of ahr) is <emphasis>capture_time</emphasis>.</entry>\r
-                                               </row>\r
-                                               <row>\r
-                                                       <entry><guilabel>Processing Group Context Field</guilabel></entry>\r
-                                                       <entry>Used to batch actions based on its associated group.</entry>\r
-                                               </row>\r
-                                               <row>\r
-                                                       <entry><guilabel><link linkend="Validators">Validators</link></guilabel></entry>\r
-                                                       <entry>The subroutines receive the trigger environment as an argument (see the linked <emphasis>Name</emphasis> for \r
-                                                       the environment definition) and returns either <emphasis>1</emphasis> if the validator is <emphasis>true</emphasis> or <emphasis>0</emphasis> \r
-                                                       if the validator returns <emphasis>false</emphasis>.</entry>\r
-                                               </row>\r
-                                               <row>\r
-                                                       <entry><guilabel><link linkend="Reactors">Reactors</link></guilabel></entry>\r
-                                                       <entry>Links the action trigger to the Reactor.</entry>\r
-                                               </row>\r
-                                               <row>\r
-                                                       <entry><guilabel>Max Event Validity Delay</guilabel></entry>\r
-                                                       <entry>Define the threshold for how far back the action_trigger_runner.pl script should reach to generate \r
-                                                       a batch of events.</entry>\r
-                                               </row>\r
-                                       </tbody>        \r
-                               </tgroup>\r
-                       </table>\r
-               \r
-               <procedure>\r
-               <title>Creating Action Triggers</title>\r
-               <indexterm><primary>action triggers</primary><secondary>creating</secondary></indexterm>  \r
-                       <step>\r
-                               <para>From the top menu, select\r
-                                       <menuchoice>\r
-                                               <guimenu>Admin</guimenu>  \r
-                                               <guisubmenu>Local Administration</guisubmenu>\r
-                                               <guisubmenu>Notifications / Action triggers</guisubmenu>\r
-                                       </menuchoice>\r
-                               </para>\r
-                       </step>\r
-                       <step><para>Click on the <guibutton>New</guibutton> button.</para></step>\r
-                       <step><para>Select an <guilabel>Owning Library</guilabel>.</para></step>\r
-                       <step><para>Create a unique <guilabel>Name</guilabel> for your new action trigger.</para></step>                                \r
-                       <step><para>Select the <guilabel>Hook</guilabel>.</para></step>\r
-                       <step><para>Check the <guilabel>Enabled</guilabel> check box.</para></step>\r
-               \r
-                       <step><para>Create a unique <guilabel>Name</guilabel> for your new action trigger.</para></step>\r
-                       <step><para>Set the <guilabel>Processing Delay</guilabel> in the appropriate format. Eg. <emphasis class="bold">7 days</emphasis> to run 7 days from the trigger event \r
-                       or <emphasis class="bold">00:01:00</emphasis> to run 1 hour after the <guilabel>Processing Delay Context Field</guilabel>.</para></step>\r
-                       <step><para>Set the <guilabel>Processing Delay Context Field</guilabel> and <guilabel>Processing Group Context Field</guilabel>.</para></step>  \r
-                       <step><para>Select the <guilabel>Validator</guilabel>, <guilabel>Reactor</guilabel>, <guilabel>Failure Cleanup</guilabel> and <guilabel>Success Cleanup</guilabel>.\r
-                       </para></step>  \r
-                       <step><para>Set the <guilabel>Processing Delay Context Field</guilabel> and <guilabel>Processing Group Context Field</guilabel>.</para></step>  \r
-                       <step preformance="optional"><para>Enter text in the <guilabel>Template</guilabel> text box if required. These are for email messages. Here is an sample \r
-                       template for sending 90 day overdue notices:</para>\r
-<programlisting><![CDATA[\r
-\r
-[%- USE date -%]\r
-[%- user = target.0.usr -%]\r
-To: [%- params.recipient_email || user.email %]\r
-From: [%- params.sender_email || default_sender %]\r
-Subject: Overdue Items Marked Lost\r
-\r
-Dear [% user.family_name %], [% user.first_given_name %]\r
-The following items are 90 days overdue and have been marked LOST.\r
-[%- params.recipient_email || user.email %][%- params.sender_email || default_sender %]\r
-[% FOR circ IN target %]\r
-    Title: [% circ.target_copy.call_number.record.simple_record.title %] \r
-    Barcode: [% circ.target_copy.barcode %] \r
-    Due: [% date.format(helpers.format_date(circ.due_date), '%Y-%m-%d') %]\r
-    Item Cost: [% helpers.get_copy_price(circ.target_copy) %]\r
-    Total Owed For Transaction: [% circ.billable_transaction.summary.total_owed %]\r
-    Library: [% circ.circ_lib.name %]\r
-[% END %]\r
-\r
-\r
-[% FOR circ IN target %]\r
-    Title: [% circ.target_copy.call_number.record.simple_record.title %] \r
-    Barcode: [% circ.target_copy.barcode %] \r
-    Due: [% date.format(helpers.format_date(circ.due_date), '%Y-%m-%d') %]\r
-    Item Cost: [% helpers.get_copy_price(circ.target_copy) %]\r
-    Total Owed For Transaction: [% circ.billable_transaction.summary.total_owed %]\r
-    Library: [% circ.circ_lib.name %]\r
-[% END %]\r
-]]>\r
-</programlisting>      \r
-                       </step> \r
-                       <step><para>Once you are satisfied with your new event trigger , click the <guibutton>Save</guibutton> button located at the bottom of the \r
-                       form</para></step>\r
-               </procedure>\r
-               <tip><para>A quick and easy way to create new action triggers is to clone an existing action trigger.</para></tip>\r
-               <procedure>\r
-                       <title>Cloning Existing Action Triggers</title>\r
-                       <step>\r
-                               <para>Check the check box next to the action trigger you wish to clone</para>\r
-                       </step>\r
-                       <step>\r
-                               <para>Click the <guibutton>Clone Selected</guibutton> on the top left of the page.</para>\r
-                       </step>\r
-                       <step>\r
-                               <para>An editing window with open. Notice that the fields will be populated with content from the cloned action trigger. Edit as necessary and \r
-                       give the new action trigger a unique <guilabel>Name</guilabel>.</para>\r
-                       </step>\r
-                       <step>\r
-                               <para>Click <guilabel>Save</guilabel>.</para>\r
-                       </step>\r
-               </procedure>\r
-               <procedure>\r
-                       <title>Editing Action Triggers</title>\r
-                       <step>\r
-                               <para>Check the check box next to the action trigger you wish to delete</para>\r
-                       </step>\r
-                       <step>\r
-                               <para>Click the <guibutton>Delete Selected</guibutton> on the top left of the page.</para>\r
-                       </step>\r
-               </procedure>\r
-               \r
-               <note><para>Before deleting an action trigger, you should consider disabling it through the editing form. This way you can simply enable it if you decide that you would like to use \r
-               the action trigger in the future.</para></note>\r
-               <procedure>\r
-                       <title>Deleting Action Triggers</title>\r
-                       <step>\r
-                               <para>Check the check box next to the action trigger you wish to delete</para>\r
-                       </step>\r
-                       <step>\r
-                               <para>Click the <guibutton>Delete Selected</guibutton> on the top left of the page.</para>\r
-                       </step>\r
-               </procedure>\r
-       </section>\r
-       <section xml:id="Hooks">\r
-               <title>Hooks</title>\r
-               <indexterm><primary>action triggers</primary><secondary>hooks</secondary></indexterm>\r
-               <para><guilabel>Hooks</guilabel> define the Fieldmapper class in the core_type column off of which the rest of the field definitions <quote>hang</quote>.</para>\r
-               <table xml:id="Hookstable">\r
-                       <title>Hooks</title>\r
-                       <tgroup cols="2">\r
-                               <colspec colnum="1" colname="col1" colwidth="1.0*"/>\r
-                               <colspec colnum="2" colname="col2" colwidth="3.0*"/>\r
-                               <thead>\r
-                                       <row>\r
-                                               <entry>Field</entry>\r
-                                               <entry>Description</entry>\r
-                                       </row>\r
-                               </thead>\r
-                               <tbody>\r
-                                       <row>\r
-                                               <entry><guilabel>Hook Key</guilabel></entry>\r
-                                               <entry>A unique name given to the hook.</entry>\r
-                                       </row>\r
-                                       <row>\r
-                                               <entry><guilabel>Core Type</guilabel></entry>\r
-                                               <entry>Used to link the action trigger to the IDL class in fm_IDL.xml</entry>\r
-                                       </row>\r
-                                       <row>\r
-                                               <entry><guilabel>Description</guilabel></entry>\r
-                                               <entry>Text to describe the purpose of the hook. </entry>\r
-                                       </row>\r
-                                       <row>\r
-                                               <entry><guilabel>Passive</guilabel></entry>\r
-                                               <entry>Indicates whether or not an event is created by direct user action or is circumstantial.</entry>\r
-                                       </row>\r
-                               </tbody>        \r
-                       </tgroup>\r
-               </table>\r
-               <para>You may also create, edit and delete Hooks but the <guilabel>Core Type</guilabel> must refer to an IDL class in the fm_IDL.xml file.</para>\r
-       </section>      \r
-       <section xml:id="Reactors">\r
-               <title>Reactors</title>\r
-               <indexterm><primary>action triggers</primary><secondary>reactors</secondary></indexterm>\r
-               <para><guilabel>Reactors</guilabel> link the trigger definition to the action to be carried out.</para>\r
-               <table xml:id="Reactorstable">\r
-                       <title>Action Trigger Reactors</title>\r
-                       <tgroup cols="2">\r
-                               <colspec colnum="1" colname="col1" colwidth="1.0*"/>\r
-                               <colspec colnum="2" colname="col2" colwidth="3.0*"/>\r
-                               <thead>\r
-                                       <row>\r
-                                               <entry>Field</entry>\r
-                                               <entry>Description</entry>\r
-                                       </row>\r
-                               </thead>\r
-                               <tbody>\r
-                                       <row>\r
-                                               <entry><guilabel>Module Name</guilabel></entry>\r
-                                               <entry>The name of the Module to run if the action trigger is validated. It must be defined as a subroutine in \r
-                                               <filename>/openils/lib/perl5/OpenILS/Application/Trigger/Reactor.pm</filename> or as a module\r
-                                                in <filename>/openils/lib/perl5/OpenILS/Application/Trigger/Reactor/*.pm</filename>.</entry>\r
-                                       </row>\r
-                                       <row>\r
-                                               <entry><guilabel>Description</guilabel></entry>\r
-                                               <entry>Description of the Action to be carried out.</entry>\r
-                                       </row>\r
-                               </tbody>        \r
-                       </tgroup>\r
-               </table>\r
-               <para>You may also create, edit and delete Reactors. Just remember that their must be an associated subroutine or module in the Reactor Perl module.</para>\r
-       </section>      \r
-       <section xml:id="Validators">\r
-               <title>Validators</title>\r
-               <indexterm><primary>action triggers</primary><secondary>validators</secondary></indexterm>\r
-               <para><guilabel>Validators</guilabel> set the validation test to be preformed to determine whether the action trigger is executed.</para>\r
-               <table xml:id="Validatorstable">\r
-                       <title>Action Trigger Validators</title>\r
-                       \r
-                       <tgroup cols="2">\r
-                               <colspec colnum="1" colname="col1" colwidth="1.0*"/>\r
-                               <colspec colnum="2" colname="col2" colwidth="3.0*"/>\r
-                               <thead>\r
-                                       <row>\r
-                                               <entry>Field</entry>\r
-                                               <entry>Description</entry>\r
-                                       </row>\r
-                               </thead>\r
-                               <tbody>\r
-                                       <row>\r
-                                               <entry><guilabel>Module Name</guilabel></entry>\r
-                                               <entry>The name of the subroutine in \r
-                                               <filename>/openils/lib/perl5/OpenILS/Application/Trigger/Reactor.pm</filename> to validate the action trigger.</entry>\r
-                                       </row>\r
-                                       <row>\r
-                                               <entry><guilabel>Description</guilabel></entry>\r
-                                               <entry>Description of validation test to run.</entry>\r
-                                       </row>\r
-                               </tbody>        \r
-                       </tgroup>\r
-               </table>\r
-               <para>You may also create, edit and delete Validators. Just remember that their must be an associated subroutine in the <filename>Reactor.pm</filename> Perl module.</para>\r
-       </section>      \r
-       <section xml:id="ProcessingActionTriggers">     \r
-               <title>Processing Action Triggers</title>\r
-               <indexterm><primary>action triggers</primary><secondary>processing</secondary></indexterm>\r
-               <para>To run the action triggers, an Evergreen administrator will need to run the trigger processing script <command>/openils/bin/action_trigger_runner.pl \r
-               <option>--process-hooks</option> <option>--run-pending</option></command>. This should be set up as a cron job to run \r
-               periodically.</para> \r
-               <para>You have several options when running the script:</para>\r
-               <itemizedlist>\r
-                       <listitem><option>--run-pending</option>: Run the pending events.</listitem>\r
-                       <listitem><option>--process-hooks</option>: Create hook events</listitem>\r
-                       <listitem><option>--osrf-config=[<varname>config_file</varname>]</option>: OpenSRF core config file.  Defaults to: \r
-                       <filename>/openils/conf/opensrf_core.xml</filename>.</listitem>\r
-                       <listitem><option>--custom-filters=[<varname>filter_file</varname>]</option>: File containing a JSON Object which describes any hooks that should\r
-                       use a user-defined filter to find their target objects.  Defaults to: <filename>/openils/conf/action_trigger_filters.json</filename></listitem>\r
-                       <listitem><option>--max-sleep=[<varname>seconds</varname>]</option>: When in process-hooks mode, wait up to [<varname>seconds</varname>] for the lock file to go away.  \r
-                       Defaults to 3600 (1 hour).</listitem>\r
-                       <listitem><option>--hooks=hook1[,hook2,hook3,...]</option>: Define which hooks to create events for.  If none are defined, it defaults to the list of hooks defined \r
-                       in the <option>--custom-filters</option> option.</listitem>\r
-                       <listitem><option>--debug-stdout</option>: Print server responses to stdout (as JSON) for debugging.</listitem>\r
-                       <listitem><option>--lock-file=[<varname>file_name</varname>]</option>: Sets the lock file for the process.</listitem>\r
-                       <listitem><option>--help</option>: Show help information.</listitem>\r
-               </itemizedlist>\r
-       </section>                                                                                                                                      \r
-</chapter>\r
-\r
diff --git a/admin/admin-booking.xml b/admin/admin-booking.xml
deleted file mode 100644 (file)
index 1a5ae44..0000000
+++ /dev/null
@@ -1,310 +0,0 @@
-<?xml version='1.0' encoding='UTF-8'?>\r
-<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"\r
-   xml:lang="EN" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="admin-booking">\r
-   <info>\r
-      <title>Booking Module Administration</title>\r
-      <legalnotice>\r
-         <para><emphasis role="bold">Adapted with permission from original material by the <link\r
-                  xlink:title="http://docs.evergreen-ils.org/1.6/draft/html/"\r
-                  xlink:href="http://docs.evergreen-ils.org/1.6/draft/html/">Evergreen\r
-                  Community</link></emphasis></para>\r
-      </legalnotice>\r
-\r
-      <abstract>\r
-         <para>The Evergreen booking module is included in Evergreen 1.6.1.x and above.The following\r
-            documentation will include information about making cataloged items bookable; making\r
-            non-bibliographic items bookable; and setting permissions in the booking module for\r
-            staff.</para>\r
-      </abstract>\r
-   </info>\r
-   <section xml:id="MakeCataloguedItemBookable">\r
-      <title>Make a Cataloged Item Bookable in Advance</title>\r
-       <indexterm><primary>booking reservation</primary><secondary>making a cataloged item bookable</secondary></indexterm>\r
-      <para>If their permission settings allow, staff members can make items bookable. Staff members\r
-         can do this in advance of a booking request, or they can do it on the fly.</para>\r
-      <para>If you know in advance of the request that an item will need to be booked, you can make\r
-         the item bookable.</para>\r
-\r
-\r
-      <procedure>\r
-         <step>\r
-            <para>In the staff client, select <menuchoice>\r
-                  <guimenu>Search</guimenu>\r
-                  <guimenuitem>Search the Catalog</guimenuitem>\r
-               </menuchoice></para>\r
-         </step>\r
-         <step>\r
-            <para>Begin a title search to find an item.</para>\r
-         </step>\r
-         <step>\r
-            <para>Click the title of the item that you want to book.</para>\r
-         </step>\r
-\r
-         <step>\r
-            <para>The <guilabel>Record Summary</guilabel> will appear. In this view you can see\r
-               information about the item and its locations. Click <menuchoice>\r
-                  <guimenu>Actions for this Record</guimenu>\r
-                  <guimenuitem>Holdings Maintenance</guimenuitem>\r
-               </menuchoice> in the top right corner of the screen.</para>\r
-         </step>\r
-\r
-         <step>\r
-            <para>The <guilabel>Holdings Maintenance</guilabel> screen will appear. In this screen,\r
-               you can view the volumes and copies of an item avaialable at each branch. To view the\r
-               barcodes and other information for each copy, click the arrow adjacent to the branch\r
-               with the copy that you need to view. Click on successive arrows until you find the\r
-               copy that you need to view.</para>\r
-         </step>\r
-         <step>\r
-            <para>Select the item that you want to make bookable. Right click to open the menu, and\r
-               click <guimenuitem>Make Item Bookable</guimenuitem>.</para>\r
-         </step>\r
-         <step>\r
-            <para>The item has now been added to the list of resources that are bookable. To book\r
-               the item, return to the <guilabel>Record Summary</guilabel>, and proceed with\r
-               booking..</para>\r
-         </step>\r
-\r
-      </procedure>\r
-      <note>\r
-         <para>In Evergreen 1.6.1, there is no way to make an item “unbookable” after it has been\r
-            made bookable and has been reserved. The <guibutton>Delete Selected</guibutton> button\r
-            on this screen deletes the resource from the screen, but the item will be able to be\r
-            booked after it has been returned.</para>\r
-      </note>\r
-\r
-   </section>\r
-   <section xml:id="MakeItemBookableOnTheFly">\r
-      <title>Make a Cataloged Item Bookable On the Fly</title>\r
-      <para>If a patron wants to book an item immediately that does not have bookable status, you\r
-         can book the item on the fly if you have the appropriate permissions.</para>\r
-\r
-      <procedure>\r
-         <step>\r
-            <para>Follow steps one through five in <xref linkend="MakeCataloguedItemBookable"\r
-               />.</para>\r
-         </step>\r
-         <step>\r
-            <para>Select the item that you want to make bookable. Right click to open the menu, and\r
-               click <guimenuitem>Book Item Now</guimenuitem>.</para>\r
-         </step>\r
-         <step>\r
-            <para>A <guilabel>Reservations</guilabel> screen will appear in a new tab, and you can\r
-               make the reservation.</para>\r
-         </step>\r
-\r
-      </procedure>\r
-\r
-   </section>\r
-   <section xml:id="MakeNon-CataloguedItemBookable">\r
-      <title>Create a Bookable Status for Non-Bibliographic Items</title>\r
-       <indexterm><primary>booking reservation</primary><secondary>non-bibliographic items</secondary></indexterm>\r
-      <para>Staff with the required permissions can create a bookable status for non-bibliographic\r
-         items. For example, staff can book conference rooms or laptops. You will be able to create\r
-         types of resources, specify the names of individual resources within each type, and set\r
-         attributes to describe those resources. You can then bring the values together through the\r
-            <guilabel>Resource Attribute Map</guilabel>.</para>\r
-      <procedure>\r
-         <step>\r
-            <para>First, create the type of resource that you want to make bookable. Select <menuchoice>\r
-                  <guimenu>Admin</guimenu>\r
-                  <guisubmenu>Server Administration</guisubmenu>\r
-                  <guisubmenu>Booking</guisubmenu>\r
-                  <guimenuitem>Resource Types</guimenuitem>\r
-               </menuchoice>.</para>\r
-         </step>\r
-         <step>\r
-            <para>A list of resource types will appear. You may also see titles of cataloged items\r
-               on this screen if they were added using the <guilabel>Make Item Bookable</guilabel>\r
-               or <guilabel>Book Now</guilabel> links. You should not attempt to add cataloged items\r
-               on this screen; it is best to use the aforementioned links to make those items\r
-               bookable. In this screen, you will create a type of resource.</para>\r
-         </step>\r
-         <step>\r
-            <para>In the right corner, click <guibutton>New Resource Type</guibutton>.</para>\r
-         </step>\r
-         <step>\r
-            <para>A box will appear in which you will create a type of resource. In this box, you\r
-               can set fines, determine “elbow room” periods between reservations on this type of\r
-               resource, and indicate if this type of resource can be transferred to another\r
-               library. Click <guibutton>Save</guibutton> when you have entered the needed\r
-               information.</para>\r
-         </step>\r
-         <step>\r
-            <para>After you click <guibutton>Save</guibutton>, the box will disappear. Refresh the\r
-               screen to see the item that you have added.</para>\r
-         </step>\r
-         <step>\r
-            <para>Next, set the attributes for the type of resource that you have created. Select <menuchoice>\r
-                  <guimenu>Server Administration</guimenu>\r
-                  <guisubmenu>Booking</guisubmenu>\r
-                  <guimenuitem>Resource Attributes</guimenuitem>\r
-               </menuchoice>.</para>\r
-         </step>\r
-\r
-         <step>\r
-            <para>Click <guibutton>New Resource Attribute</guibutton>.</para>\r
-         </step>\r
-\r
-         <step>\r
-            <para>A box will appear in which you can add the attributes of the resource. Attributes\r
-               are descriptive information that is provided to the staff member when the booking\r
-               request is made. For example, an attribute of the projector may be a cart that allows\r
-               for its transportation. Other attributes might be number of seats available in a\r
-               room, or MAC or PC attributes for a laptop. Click <guibutton>Save</guibutton> when\r
-               the necessary information has been entered.</para>\r
-         </step>\r
-\r
-         <step>\r
-            <para>The box will disappear. Refresh the screen to see the added attribute.</para>\r
-         </step>\r
-\r
-         <step>\r
-            <para>Next, add the values for the resource attributes. A value can be a number, yes/no,\r
-               or any other meaningful information. Select <menuchoice>\r
-                  <guimenu>Server Administration</guimenu>\r
-                  <guisubmenu>Booking</guisubmenu>\r
-                  <guimenuitem>Resource Attribute Values</guimenuitem>\r
-               </menuchoice>.</para>\r
-         </step>\r
-\r
-         <step>\r
-            <para>Select <guibutton>New Resource Attribute Value</guibutton>.</para>\r
-         </step>\r
-\r
-         <step>\r
-            <para>A pop up box will appear. Select the <guilabel>Resource Attribute</guilabel> from\r
-               the drop down box. Add the value. You can add multiple values for this field. Click\r
-                  <guibutton>Save</guibutton> when the required information has been added.</para>\r
-         </step>\r
-\r
-         <step>\r
-            <para>If you refresh the screen, the attribute value may not appear, but it has been\r
-               saved.</para>\r
-         </step>\r
-\r
-         <step>\r
-            <para>Next, identify the specific objects that are associated with this resource type.\r
-               Click <menuchoice>\r
-                  <guimenu>Admin</guimenu>\r
-                  <guisubmenu>Server Administration</guisubmenu>\r
-                  <guisubmenu>Booking</guisubmenu>\r
-                  <guimenuitem>Resources</guimenuitem>\r
-               </menuchoice>.</para>\r
-         </step>\r
-\r
-         <step>\r
-            <para>Click <guibutton>New Resource</guibutton>.</para>\r
-         </step>\r
-\r
-         <step>\r
-            <para>A pop-up box will appear. Add information for the resource and click\r
-                  <guibutton>Save</guibutton>. Repeat this process for each resource.</para>\r
-         </step>\r
-\r
-         <step>\r
-            <para>Refresh the screen, and the resource(s) that you added will appear.</para>\r
-         </step>\r
-\r
-         <step>\r
-            <para>Finally, use <guilabel>Resource Attribute Maps</guilabel> to bring together the\r
-               resource and its attributes. Select <menuchoice>\r
-                  <guimenu>Admin</guimenu>\r
-                  <guisubmenu>Server Administration</guisubmenu>\r
-                  <guisubmenu>Booking</guisubmenu>\r
-                  <guimenuitem>Resource Attribute Maps</guimenuitem>\r
-               </menuchoice>.</para>\r
-         </step>\r
-\r
-         <step>\r
-            <para>Select <guibutton>New Resource Attribute Map</guibutton></para>\r
-         </step>\r
-\r
-         <step>\r
-            <para>Select the resource that you want to match with its attributes, then click\r
-                  <guibutton>Save</guibutton>. Repeat for all applicable resources.</para>\r
-         </step>\r
-\r
-         <step>\r
-            <para>You have now created bookable, non-bibliographic resource(s) with\r
-               attributes.</para>\r
-         </step>\r
-\r
-      </procedure>\r
-   </section>\r
-   <section xml:id="SettingBookingPermissions">\r
-      <title>Setting Booking Permissions</title>\r
-       <indexterm><primary>booking reservation</primary><secondary>setting booking permissions</secondary></indexterm>\r
-      <para>Administrators can set permissions so that staff members can view reservations, make\r
-         reservations, and make bibliographic or non-bibliographic items bookable.</para>\r
-\r
-      <para>If a staff member attempts to book an item for which they do not have the appropriate\r
-         permissions, they will receive an error message.</para>\r
-\r
-      <para>To set permissions, select <menuchoice>\r
-            <guimenu>Admin</guimenu>\r
-            <guisubmenu>Server Administration</guisubmenu>\r
-            <guimenuitem>Permissions</guimenuitem>\r
-         </menuchoice>.</para>\r
-\r
-      <para>Staff members should be assigned the following permissions to do common tasks in the\r
-         booking module. These permissions could be assigned to front line staff members, such as\r
-         circulation staff. Permissions with an asterisk (<emphasis role="bold">*</emphasis>) are\r
-         already included in the <emphasis role="bold">Staff</emphasis> permission group. All other\r
-         booking permissions must be applied individually.</para>\r
-\r
-      <itemizedlist>\r
-         <listitem>\r
-            <para><emphasis role="bold">View Reservations:</emphasis> VIEW_TRANSACTION*</para>\r
-         </listitem>\r
-         <listitem>\r
-            <para><emphasis role="bold">Use the pull list:</emphasis>\r
-               RETRIEVE_RESERVATION_PULL_LIST</para>\r
-         </listitem>\r
-         <listitem>\r
-            <para><emphasis role="bold">Capture reservations:</emphasis> CAPTURE_RESERVATION</para>\r
-         </listitem>\r
-         <listitem>\r
-            <para><emphasis role="bold">Assist patrons with pickup and return:</emphasis>\r
-               VIEW_USER*</para>\r
-         </listitem>\r
-         <listitem>\r
-            <para><emphasis role="bold">Create/update/delete reservations:</emphasis>\r
-               ADMIN_BOOKING_RESERVATION</para>\r
-         </listitem>\r
-      </itemizedlist>\r
-\r
-      <para>The following permissions allow users to do more advanced tasks, such as making items\r
-         bookable, booking items on the fly, and creating non-bibliographic resources for\r
-         booking.</para>\r
-\r
-      <itemizedlist>\r
-         <listitem>\r
-            <para><emphasis role="bold">Create/update/delete booking resource type:</emphasis>\r
-               ADMIN_BOOKING_RESOURCE_TYPE</para>\r
-         </listitem>\r
-         <listitem>\r
-            <para><emphasis role="bold">Create/update/delete booking resource attributes:</emphasis>\r
-               ADMIN_BOOKING_RESOURCE_ATTR</para>\r
-         </listitem>\r
-         <listitem>\r
-            <para><emphasis role="bold">Create/update/delete booking resource attribute\r
-                  values:</emphasis> ADMIN_BOOKING_RESOURCE_ATTR_VALUE</para>\r
-         </listitem>\r
-         <listitem>\r
-            <para><emphasis role="bold">Create/update/delete booking resource:</emphasis>\r
-               ADMIN_BOOKING_RESOURCE</para>\r
-         </listitem>\r
-         <listitem>\r
-            <para><emphasis role="bold">Create/update/delete booking resource attribute\r
-                  maps:</emphasis> ADMIN_BOOKING_RESOURCE_ATTR_MAP</para>\r
-         </listitem>\r
-      </itemizedlist>\r
-\r
-      <para>In addition to having the permissions listed above, staff members will need a valid\r
-         working location in their profiles. This should be done when registering new staff members.</para>\r
-\r
-      <!-- Pages 14-16 of source document from http://evergreen-ils.org/dokuwiki/doku.php?id=booking ommitted at conversion (Jeremy Buhler, Oct 6 2010).  Rationale: subject is covered elsewhere in the Book of Evergreen and it confuses 'working location' with 'home library', both of which should already be set for all staff accounts. -->\r
-\r
-   </section>\r
-</chapter>\r
diff --git a/admin/admin-intro.xml b/admin/admin-intro.xml
deleted file mode 100644 (file)
index 813ed6c..0000000
+++ /dev/null
@@ -1,15 +0,0 @@
-<partintro xmlns:xl="http://www.w3.org/1999/xlink" xml:id="admin_intro">\r
-       <para>This part of the documentation is intended for Evergreen administrators and requires root access to your <application>Evergreen</application> server(s) and administrator access to \r
-       the <application>Evergreen</application> \r
-       staff client. It deals with maintaining servers, installation, upgrading, and configuring both system wide and local library settings. \r
-       Some sections require understanding of <systemitem class="osname">Linux</systemitem> system administration while others require an understanding of your system hierarchy of locations \r
-       and users. Many procedures explained in the following \r
-       chapters are accomplished with <systemitem class="osname">Linux</systemitem> commands<indexterm><primary>Linux</primary><secondary>commands</secondary></indexterm> run from the \r
-       terminal without a Graphical User Interface (GUI).</para>\r
-       <para>In order to accomplish some of the tasks, prerequisite knowledge or experience will be required and you may need to consult system administration documentation for your \r
-       specific <systemitem class="osname">Linux</systemitem> distribution if you have limited <systemitem class="osname">Linux</systemitem> system experience. A vast ammount of free \r
-       resources can be found on the on the web for various experinece levels. You might also consider consulting <link xl:href="http://www.postgresql.org/docs/">\r
-       <application>PostgreSQL</application></link><indexterm><primary>databases</primary><secondary>PostgreSQL</secondary></indexterm> and \r
-       <link xl:href="http://httpd.apache.org/docs/"><application>Apache</application></link><indexterm><primary>Apache</primary></indexterm> documentation for a greater understanding \r
-       of the software stack on which <application>Evergreen</application> is built.</para>\r
-</partintro>\r
diff --git a/admin/admin-lsa_2.0.xml b/admin/admin-lsa_2.0.xml
deleted file mode 100644 (file)
index 4a59bcc..0000000
+++ /dev/null
@@ -1,1927 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>\r
-<chapter xml:id="lsa" xmlns="http://docbook.org/ns/docbook" version="5.0" xml:lang="EN"\r
-   xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:xlink="http://www.w3.org/1999/xlink">\r
-   <info>\r
-      <title>Local Administration Menu</title>\r
-   </info>\r
-   <section>\r
-      <info>\r
-         <title>Overview</title>\r
-      </info>\r
-         <para>Many Evergreen configuration options are available under the <menuchoice>\r
-               <guimenu>Admin (-)</guimenu>\r
-               <guimenuitem>Local Administration</guimenuitem>\r
-            </menuchoice> rollover menu.</para>\r
-         <para>Settings are also available from the <guilabel>Local Administration</guilabel> page.</para>\r
-      <para>Either access point can be used, but examples in this manual use the more comprehensive\r
-            <guilabel>Local Administration</guilabel> rollover menu.</para>\r
-      <para>Items on this menu are visible to anyone logged into the staff client but usually\r
-         require special permissions to edit. The following table describes each of the menu options. </para>\r
-      <informaltable>\r
-         <tgroup cols="2" align="left" colsep="1" rowsep="1">\r
-               <colspec colnum="1" colname="menu" colwidth="1.0*"/>\r
-               <colspec colnum="2" colname="description" colwidth="3.0*"/>\r
-            <thead>\r
-               <row>\r
-                  <entry>Menu option</entry>\r
-                  <entry>Description</entry>\r
-               </row>\r
-            </thead>\r
-            <tbody>\r
-               <row>\r
-                  <entry>\r
-                     <link linkend="lsa-receipt">Receipt Template Editor</link>\r
-                  </entry>\r
-                  <entry>Customize printed receipts (checkout receipts, hold slips, etc) for a\r
-                     single workstation</entry>     \r
-               </row>\r
-               <row>\r
-                  <entry>\r
-                     <link linkend="lsa-font">Global Font and Sound Settings</link>\r
-                  </entry>\r
-                  <entry>Change font size and sound settings for a single workstation</entry>              \r
-               </row>\r
-               <row>\r
-                  <entry>\r
-                     <link linkend="lsa-printer">Printer Settings Editor</link>\r
-                  </entry>\r
-                  <entry>Configure printer settings for a single workstation</entry>                \r
-               </row>\r
-               <row>\r
-                  <entry>\r
-                     <link linkend="lsa-closed">Closed Dates Editor</link>\r
-                  </entry>\r
-                  <entry>Set library closure dates (affects due dates and fines)</entry>                \r
-               </row>\r
-               <row>\r
-                  <entry>\r
-                     <link linkend="lsa-copy-locations">Copy Locations Editor</link>\r
-                  </entry>\r
-                  <entry>Create and edit copy locations, also known as shelving locations</entry>                \r
-               </row>\r
-               <row>\r
-                  <entry>\r
-                     <link linkend="lsa-library-settings">Library Settings Editor</link>\r
-                  </entry>\r
-                  <entry>Detailed library configuration settings</entry>                 \r
-               </row>\r
-               <row>\r
-                  <entry>\r
-                     <link linkend="lsa-noncat">Non-Catalogued Type Editor</link>\r
-                  </entry>\r
-                  <entry>Create and edit optional <guilabel>non-catalogued</guilabel> item\r
-                     types</entry>                 \r
-               </row>\r
-\r
-               <row>\r
-                  <entry>\r
-                     <link linkend="lsa-statcat">Statistical Categories Editor</link>\r
-                  </entry>\r
-                  <entry>Create and manage optional categories for detailed patron/item\r
-                     information</entry>                  \r
-               </row>\r
-               <row>\r
-                  <entry>Standing Penalties</entry>\r
-                  <entry>\r
-                     <emphasis>admin settings</emphasis>\r
-                  </entry>                \r
-               </row>\r
-               <row xml:id="lsa-group-penalty-table-entry">\r
-                  <entry>\r
-                     <link linkend="lsa-group-penalty">Group Penalty Thresholds</link>\r
-                  </entry>\r
-                  <entry> Set library-specific thresholds for maximum items out, maximum overdues,\r
-                     and maximum fines </entry>                 \r
-               </row>\r
-               <row>\r
-                  <entry>Field Documentation</entry>\r
-                  <entry>\r
-                     <emphasis>admin settings</emphasis>\r
-                  </entry>                  \r
-               </row>\r
-               <row>\r
-                  <entry>Notifications / Action Triggers</entry>\r
-                  <entry>\r
-                     <emphasis>admin settings</emphasis>\r
-                  </entry>                 \r
-               </row>\r
-               <row>\r
-                  <entry>\r
-                     <link linkend="lsa-survey">Surveys</link>\r
-                  </entry>\r
-                  <entry>Create patron surveys to be completed at patron registration</entry>                 \r
-               </row>\r
-               <row>\r
-                  <entry>\r
-                     Reports\r
-                  </entry>\r
-                  <entry>Generate reports on any field in the Evergreen database</entry>                  \r
-               </row>\r
-               <row>\r
-                  <entry>\r
-                     <link linkend="lsa-cash-reports">Cash Reports</link>\r
-                  </entry>\r
-                  <entry>View summary report of cash transactions for selected date range</entry>                  \r
-               </row>\r
-               <row>\r
-                  <entry>\r
-                       Transit List\r
-                  </entry>\r
-                  <entry>View items in transit to or from your library during selected date\r
-                     range</entry>              \r
-               </row>\r
-               <row>\r
-                  <entry>Circulation Policies</entry>\r
-                  <entry>\r
-                     <emphasis>admin settings</emphasis>\r
-                  </entry>  \r
-               </row>\r
-               <row>\r
-                  <entry>Hold Policies</entry>\r
-                  <entry>\r
-                     <emphasis>admin settings</emphasis>\r
-                  </entry>\r
-               </row>\r
-            </tbody>\r
-         </tgroup>\r
-      </informaltable>\r
-   </section>\r
-   <section xml:id="lsa-receipt">\r
-   <info>\r
-      <title>Receipt Template Editor</title>\r
-       <indexterm><primary>receipt template editor</primary></indexterm>\r
-   </info>\r
-\r
-   <para>This tip sheet will show you how to customize your receipts.  This example will walk you\r
-      through how to customize the receipt that is printed on checkout.  </para>\r
-\r
-   <para>Receipt templates are saved on the workstation, but it is possible to export the templates\r
-      to import to other workstations.  </para>\r
-\r
-<procedure>\r
-\r
-   <step>\r
-               <para>Select <menuchoice><guimenu>Admin (-)</guimenu><guisubmenu>Local Administration</guisubmenu><guimenuitem>Receipt Template Editor</guimenuitem></menuchoice>.  </para>\r
-   </step>\r
-\r
-\r
-   <step>\r
-     \r
-         <para>Select the <guimenuitem>checkout</guimenuitem> template from the dropdown menu.\r
-             </para>\r
-   </step>\r
-\r
-\r
-   <step>\r
-         <para>You can edit the <guilabel>Header</guilabel>, <guilabel>Line\r
-               Item</guilabel> or <guilabel>Footer</guilabel> on the right hand side.  </para>  \r
-   </step>\r
-\r
-  \r
-        <step><para>In the upper right hand corner you can see the available macros by clicking on the\r
-               <guibutton>Macros</guibutton> button.  A macro prints a real value from the database.\r
-            The macros that are available\r
-            vary slightly between types of receipt templates (i.e. bills, holds, items). </para>\r
-    </step>\r
-\r
-   \r
-       <step><informalfigure>  <para>Here are the available macros for an item receipt, like a checkout receipt.  </para>\r
-       <para>\r
-      <mediaobject>\r
-         <alt>screenshot of staff client</alt>\r
-         <imageobject role="html">\r
-            <imagedata scalefit="0" fileref="../media/receipt-5.jpg"/>\r
-         </imageobject>\r
-         <imageobject role="fo">\r
-            <imagedata scale="80" fileref="../media/receipt-5.jpg"/>\r
-         </imageobject>\r
-      </mediaobject>\r
-   </para></informalfigure></step>\r
-   \r
-  </procedure>\r
-   \r
-   <simplesect>\r
-      <info>\r
-         <title>Adding an image</title>\r
-      </info>\r
-\r
-<procedure>    \r
-           <step><para>You can edit the <guilabel>Header</guilabel> to have an image.  This is the default checkout <guilabel>Header</guilabel>.\r
-                </para>\r
-     </step>\r
-\r
-     \r
-            <step><para>Using HTML tags you can insert a link to an image that exists on the web.  The\r
-               link will end in <emphasis>.jpg</emphasis> or possibly <emphasis>.gif</emphasis>.  To\r
-               get this link you can right click on the image and choose <guimenuitem>Copy Image\r
-                  Location</guimenuitem> (<application>Firefox</application>).  </para>\r
-        \r
-<para>If you are using <application>Internet Explorer</application> right click and select <guimenuitem>Save Picture\r
-            As…</guimenuitem>\r
-      </para>\r
-\r
-  </step>\r
-\r
-           <step> <para>Enter the URL of the\r
-               link for the image that you just copied off a website. </para>\r
-         \r
-<para>By clicking outside the <guilabel>Header</guilabel> box the <guilabel>Preview</guilabel> will update to reflect the edit you just\r
-         made.  </para>\r
-\r
-      </step>\r
-  \r
-           <step><para>If the image runs into the text, add a &lt;br/&gt; after the\r
-               image to add a line break.</para>\r
-     </step></procedure>   \r
-      <tip><para>You may use most HTML tags.  See <link xlink:title="http://www.w3schools.com/html/" xlink:href="http://www.w3schools.com/html/">http://www.w3schools.com/html/</link> for more information on HTML tags.  </para></tip>\r
-   </simplesect>\r
-   <simplesect>\r
-      <info>\r
-         <title>Line Item</title>\r
-      </info>\r
-\r
-          <informalfigure>  <para>This is what the default <guilabel>Line Item</guilabel> looks like:</para>\r
-        \r
-      <para>\r
-         <mediaobject>\r
-            <alt>screenshot of staff client</alt>\r
-            <imageobject role="html">\r
-               <imagedata scalefit="1" fileref="../media/receipt-11.jpg"/>\r
-            </imageobject>\r
-            <imageobject role="fo">\r
-               <imagedata scalefit="1" width="100%" contentdepth="100%"\r
-                  fileref="../media/receipt-11.jpg"/>\r
-            </imageobject>\r
-         </mediaobject>\r
-      </para></informalfigure>\r
-\r
-      <para>In this example, the macro %barcode% prints the item barcodes of the books that were\r
-         checked out.  The macro %due_date% prints the due date for each item that was checked out.\r
-          </para>\r
-\r
-      <para>In this example, we will not make any changes to the <guilabel>Line Item</guilabel></para>\r
-\r
-      \r
-     <note> <para>The due date can only be printed in the YYYY-MM-DD format. </para></note>\r
-\r
-   </simplesect>\r
-   <simplesect>\r
-      <info>\r
-         <title>Editing the footer</title>\r
-      </info>\r
-\r
-     \r
-<procedure>          <step><informalfigure>  <para>This is what the default <guilabel>Footer</guilabel> looks like:</para>\r
-        \r
-      <para>\r
-         <mediaobject>\r
-            <alt>screenshot of staff client</alt>\r
-            <imageobject role="html">\r
-               <imagedata scalefit="1" fileref="../media/receipt-12.jpg"/>\r
-            </imageobject>\r
-            <imageobject role="fo">\r
-               <imagedata scalefit="1" width="100%" contentdepth="100%"\r
-                  fileref="../media/receipt-12.jpg"/>\r
-            </imageobject>\r
-         </mediaobject>\r
-      </para></informalfigure></step>\r
-\r
-     \r
-            <step><informalfigure><para>Remove the “You were helped by %STAFF_FIRSTNAME% &lt;br/&gt;”.  As many\r
-               libraries use a generic circulation login on the circulation desk, the “You were\r
-               helped by…” note isn’t meaningful.  </para>\r
-        \r
-      <para>\r
-         <mediaobject>\r
-            <alt>screenshot of staff client</alt>\r
-            <imageobject role="html">\r
-               <imagedata scalefit="1" fileref="../media/receipt-13.jpg"/>\r
-            </imageobject>\r
-            <imageobject role="fo">\r
-               <imagedata scalefit="1" width="100%" contentdepth="100%"\r
-                  fileref="../media/receipt-13.jpg"/>\r
-            </imageobject>\r
-         </mediaobject>\r
-      </para></informalfigure></step>\r
-\r
-          <step><informalfigure>  <para>Once you have the checkout template how you want it, click <guibutton>Save Locally</guibutton> to save\r
-               the template to your computer.  </para>\r
-       \r
-\r
-      <para>\r
-         <mediaobject>\r
-            <alt>screenshot of staff client</alt>\r
-            <imageobject>\r
-               <imagedata scalefit="0" fileref="../media/receipt-15.jpg"/>\r
-            </imageobject>\r
-            \r
-         </mediaobject>\r
-      </para></informalfigure></step>\r
-\r
-     \r
-            <step><informalfigure><para>Click OK.</para>\r
-       \r
-\r
-      <para>\r
-         <mediaobject>\r
-            <alt>screenshot of staff client</alt>\r
-            <imageobject role="html">\r
-               <imagedata scalefit="0" fileref="../media/receipt-16.png"/>\r
-            </imageobject>\r
-            <imageobject role="fo">\r
-               <imagedata scale="80" fileref="../media/receipt-16.png"/>\r
-            </imageobject>\r
-         </mediaobject>\r
-      </para></informalfigure></step></procedure>\r
-      \r
-     <tip> <para>The footer is a good place to advertise upcoming library programs or events.  </para></tip>\r
-      \r
-   </simplesect>\r
-   <simplesect>\r
-      <info>\r
-         <title>Exporting templates</title>\r
-      </info>\r
-\r
-      <para>As you can only save a template on to the computer you are working on you will need to\r
-         export the template if you have more than one computer that prints out receipts (i.e., more\r
-         than one computer on the circulation desk, or another computer in the workroom that you use\r
-         to checkin items or capture holds with).</para>\r
-\r
-      \r
-<procedure>           <step><informalfigure> <para>Click on <guilabel>Export</guilabel>.  </para>\r
-        \r
-\r
-      <para>\r
-         <mediaobject>\r
-            <alt>screenshot of staff client</alt>\r
-            <imageobject role="html">\r
-               <imagedata scalefit="0" fileref="../media/receipt-17.jpg"/>\r
-            </imageobject>\r
-            <imageobject role="fo">\r
-               <imagedata scale="80" fileref="../media/receipt-17.jpg"/>\r
-            </imageobject>\r
-         </mediaobject>\r
-      </para>\r
-</informalfigure></step>\r
-     \r
-     \r
-     \r
-            <step><informalfigure><para>Select the location to save the template to, name the template, and click <guibutton>Save</guibutton>.\r
-                </para>\r
-              <para>\r
-         <mediaobject>\r
-            <alt>screenshot of staff client</alt>\r
-            <imageobject role="html">\r
-               <imagedata scalefit="0" fileref="../media/receipt-18.jpg"/>\r
-            </imageobject>\r
-            <imageobject role="fo">\r
-               <imagedata scale="80" fileref="../media/receipt-18.jpg"/>\r
-            </imageobject>\r
-         </mediaobject>\r
-      </para>\r
-</informalfigure></step>\r
-      \r
-      \r
-      \r
-            <step><informalfigure><para>Click <guibutton>OK</guibutton>.  </para>\r
-               <para>\r
-         <mediaobject>\r
-            <alt>screenshot of staff client</alt>\r
-            <imageobject role="html">\r
-               <imagedata scalefit="0" fileref="../media/receipt-19.jpg"/>\r
-            </imageobject>\r
-            <imageobject role="fo">\r
-               <imagedata scale="80" fileref="../media/receipt-19.jpg"/>\r
-            </imageobject>\r
-         </mediaobject>\r
-      </para></informalfigure></step></procedure>\r
-\r
-   </simplesect>\r
-   <simplesect>\r
-      <info>\r
-         <title>Importing Templates</title>\r
-      </info>\r
-<procedure>\r
-     \r
-           <step><informalfigure> <para>Click <guibutton>Import</guibutton>.</para>\r
-        \r
-      <para>\r
-         <mediaobject>\r
-            <alt>screenshot of staff client</alt>\r
-            <imageobject role="html">\r
-               <imagedata scalefit="0" fileref="../media/receipt-20.jpg"/>\r
-            </imageobject>\r
-            <imageobject role="fo">\r
-               <imagedata scale="80" fileref="../media/receipt-20.jpg"/>\r
-            </imageobject>\r
-         </mediaobject>\r
-      </para></informalfigure></step>\r
-\r
-      \r
-            <step><informalfigure><para>Navigate to and select the template that you want to import.  Click <guibutton>Open</guibutton>. </para>\r
-        \r
-      <para>\r
-         <mediaobject>\r
-            <alt>screenshot of staff client</alt>\r
-            <imageobject role="html">\r
-               <imagedata scalefit="0" fileref="../media/receipt-21.jpg"/>\r
-            </imageobject>\r
-            <imageobject role="fo">\r
-               <imagedata scale="80" fileref="../media/receipt-21.jpg"/>\r
-            </imageobject>\r
-         </mediaobject>\r
-      </para></informalfigure></step>\r
-\r
-      \r
-         <step><informalfigure>   <para>Click <guibutton>OK</guibutton>.</para>\r
-        \r
-      <para>\r
-         <mediaobject>\r
-            <alt>screenshot of staff client</alt>\r
-            <imageobject role="html">\r
-               <imagedata scalefit="0" fileref="../media/receipt-22.jpg"/>\r
-            </imageobject>\r
-            <imageobject role="fo">\r
-               <imagedata scale="80" fileref="../media/receipt-22.jpg"/>\r
-            </imageobject>\r
-         </mediaobject>\r
-      </para></informalfigure></step>\r
-\r
-    \r
-    \r
-            <step><informalfigure><para>Click <guibutton>Save Locally</guibutton>.</para>\r
-             <para>\r
-         <mediaobject>\r
-            <alt>screenshot of staff client</alt>\r
-            <imageobject role="html">\r
-               <imagedata scalefit="0" fileref="../media/receipt-23.jpg"/>\r
-            </imageobject>\r
-            <imageobject role="fo">\r
-               <imagedata scale="80" fileref="../media/receipt-23.jpg"/>\r
-            </imageobject>\r
-         </mediaobject>\r
-      </para></informalfigure></step>\r
-\r
-    \r
-            <step><informalfigure><para>Click <guibutton>OK</guibutton>.</para>\r
-        \r
-\r
-      <para>\r
-         <mediaobject>\r
-            <alt>screenshot of staff client</alt>\r
-            <imageobject role="html">\r
-               <imagedata scalefit="0" fileref="../media/receipt-24.jpg"/>\r
-            </imageobject>\r
-            <imageobject role="fo">\r
-               <imagedata scale="80" fileref="../media/receipt-24.jpg"/>\r
-            </imageobject>\r
-         </mediaobject>\r
-      </para></informalfigure></step></procedure>\r
-   </simplesect>\r
-</section>\r
-   <section xml:id="lsa-font">\r
-      <info>\r
-         <title>Global Font and Sound Settings</title>\r
-       <indexterm><primary>staff client</primary><secondary>fonts</secondary></indexterm>\r
-       \r
-      </info>\r
-      <para><guilabel>Global Font and Sound Settings</guilabel> apply to the current workstation\r
-         only. Use to turn staff client sounds on/off or to adjust the font size in the staff client\r
-         interface. These settings do not affect OPAC font sizes.</para>\r
-      <procedure>\r
-         <step>\r
-            <para>Select <menuchoice>\r
-                  <guimenu>Admin (-)</guimenu>\r
-                  <guisubmenu>Local Administration</guisubmenu>\r
-                  <guimenuitem>Global Font and Sound Settings</guimenuitem>\r
-               </menuchoice>.</para>\r
-         </step>\r
-         <step>\r
-            <informalfigure>\r
-               <indexterm><primary>staff client</primary><secondary>sounds</secondary></indexterm>\r
-               <para>To turn off the system sounds, like the noise that happens when a patron with a\r
-                  block is retrieved check the <guilabel>disable sound</guilabel> box and click\r
-                     <guibutton>Save to Disk</guibutton>.  </para>\r
-               <para>\r
-                  <mediaobject>\r
-                     <alt>screenshot of staff client</alt>\r
-                     <imageobject>\r
-                        <imagedata scalefit="0" fileref="../media/lsa-4.jpg"/>\r
-                     </imageobject>\r
-                  </mediaobject>\r
-               </para>\r
-            </informalfigure>\r
-         </step>\r
-         <step>\r
-            <informalfigure>\r
-               <para>To change the size of the font, pick the desired option and click\r
-                     <guibutton>Save to Disk</guibutton>.  </para>\r
-               <para>\r
-                  <mediaobject>\r
-                     <alt>screenshot of staff client</alt>\r
-                     <imageobject>\r
-                        <imagedata scalefit="0" fileref="../media/lsa-5.jpg"/>\r
-                     </imageobject>\r
-\r
-                  </mediaobject>\r
-               </para>\r
-            </informalfigure>\r
-         </step>\r
-      </procedure>\r
-   </section>\r
-   <section xml:id="lsa-printer">\r
-      <info>\r
-         <title>Printer Settings Editor</title>\r
-       <indexterm><primary>staff client</primary><secondary>printer settings</secondary></indexterm>\r
-      </info>\r
-      <para>Use the <guilabel>Printer Settings Editor</guilabel> to configure printer output for\r
-         each workstation.</para>\r
-      <procedure>\r
-         <step>\r
-            <para>Select <menuchoice>\r
-                  <guimenu>Admin (-)</guimenu>\r
-                  <guisubmenu>Local Administration</guisubmenu>\r
-                  <guimenuitem>Printer Settings Editor</guimenuitem>\r
-               </menuchoice>.</para>\r
-         </step>\r
-         <step>\r
-            <informalfigure>\r
-               <para>From this screen you can print a test page, or alter the page settings for your\r
-                  receipt printer.  </para>\r
-               <para>\r
-                  <mediaobject>\r
-                     <alt>screenshot of staff client</alt>\r
-                     <imageobject>\r
-                        <imagedata width="100%" scalefit="1" fileref="../media/lsa-7.jpg"/>\r
-                     </imageobject>\r
-                  </mediaobject>\r
-               </para>\r
-            </informalfigure>\r
-         </step>\r
-         <step>\r
-            <informalfigure>\r
-               <para>Click on <guibutton>Page Settings</guibutton> to change printing format and\r
-                  option settings.  Click on the <guilabel>Margins &amp;\r
-                     Header/Footer</guilabel> tab to adjust </para>\r
-               <para>\r
-                  <mediaobject>\r
-                     <alt>screenshot of staff client</alt>\r
-                     <imageobject>\r
-                        <imagedata scalefit="0" fileref="../media/lsa-8.jpg"/>\r
-                     </imageobject>\r
-\r
-                  </mediaobject>\r
-               </para>\r
-            </informalfigure>\r
-         </step>\r
-      </procedure>\r
-   </section>\r
-   <section xml:id="lsa-closed">\r
-      <info>\r
-         <title>Closed Dates Editor</title>\r
-       <indexterm><primary>closed dates editor</primary></indexterm>\r
-      </info>\r
-      <para>These dates are in addition to your regular weekly closed days. Both regular closed days and those entered in the\r
-            <guilabel>Closed Dates Editor</guilabel> affect due dates and fines:</para>\r
-      <itemizedlist>\r
-         <listitem>\r
-            <formalpara>\r
-               <title>Due dates</title>\r
-               <indexterm><primary>closed dates editor</primary><secondary>due dates</secondary></indexterm>\r
-               <para>Due dates that would fall on closed days are automatically pushed forward to\r
-                  the next open day. Likewise, if an item is checked out at 8pm, for example, and\r
-                  would normally be due on a day when the library closes before 8pm, Evergreen\r
-                  pushes the due date forward to the next open day.</para>\r
-            </formalpara>\r
-         </listitem>\r
-         <listitem>\r
-            <formalpara>\r
-               <title>Overdue fines</title>\r
-               <indexterm><primary>closed dates editor</primary><secondary>fines</secondary></indexterm>\r
-               <para>Overdue fines are not charged on days when the library is closed.</para>\r
-            </formalpara>\r
-         </listitem>\r
-      </itemizedlist>     \r
-      <simplesect>\r
-         <title>Multi-Day Closing</title>\r
-         <procedure>\r
-            <step>\r
-               <para>Select <menuchoice>\r
-                     <guimenu>Admin (-)</guimenu>\r
-                     <guisubmenu>Local Administration</guisubmenu>\r
-                     <guimenuitem>Closed Dates Editor</guimenuitem>\r
-                  </menuchoice>.</para>\r
-            </step>\r
-            <step xml:id="lsa-multi-day-select">\r
-               <informalfigure>\r
-                  <para>Select <guibutton>Add Multi-Date Closing</guibutton> if your closed dates\r
-                     are entire business days.</para>\r
-                  <para>\r
-                     <mediaobject>\r
-                        <alt>screenshot of staff client</alt>\r
-                        <imageobject>\r
-                           <imagedata scalefit="0" fileref="../media/lsa-10.jpg"/>\r
-                        </imageobject>\r
-                     </mediaobject>\r
-                  </para>\r
-               </informalfigure>\r
-            </step>\r
-            <step>\r
-               <informalfigure>\r
-                  <para>Enter applicable dates and a descriptive reason for the closing and click\r
-                        <guibutton>Save</guibutton>.  Check the <guilabel>Apply to all of my\r
-                        libraries</guilabel> box if your library is a multi-branch system and the\r
-                     closing applies to all of your branches.  </para>\r
-                  <para>\r
-                     <mediaobject>\r
-                        <alt>screenshot of staff client</alt>\r
-                        <imageobject>\r
-                           <imagedata scalefit="0" fileref="../media/lsa-11.jpg"/>\r
-                        </imageobject>\r
-\r
-                     </mediaobject>\r
-                  </para>\r
-               </informalfigure>\r
-            </step>\r
-         </procedure>\r
-         <tip>\r
-            <para>You can type dates into fields using YYYY-MM-DD format or use calendar widgets to\r
-               choose dates.</para>\r
-         </tip>\r
-      </simplesect>\r
-      <simplesect>\r
-         <title>Detailed Closing</title>\r
-         <informalfigure>\r
-            <para>If your closed dates include a portion of a business day, select Add Detailed\r
-               Closing at <xref linkend="lsa-multi-day-select"/>, then enter detailed hours and\r
-               dates and click <guibutton>Save</guibutton>. Time format must be HH:MM.</para>\r
-            <para>\r
-               <mediaobject>\r
-                  <alt>screenshot of staff client</alt>\r
-                  <imageobject>\r
-                     <imagedata scalefit="0" fileref="../media/lsa-12.jpg"/>\r
-                  </imageobject>\r
-\r
-               </mediaobject>\r
-            </para>\r
-         </informalfigure>\r
-      </simplesect>  \r
-   </section>\r
-   <section xml:id="lsa-copy-locations">\r
-      <info>\r
-         <title>Copy Locations Editor</title>\r
-       <indexterm><primary>copy locations editor</primary></indexterm>\r
-      </info>\r
-      <procedure>\r
-         <step>\r
-            <para>Select <menuchoice>\r
-                  <guimenu>Admin (-)</guimenu>\r
-                  <guisubmenu>Local Administration</guisubmenu>\r
-                  <guimenuitem>Copy Locations Editor</guimenuitem>\r
-               </menuchoice>.</para>\r
-         </step>\r
-         <step>\r
-            <informalfigure>\r
-               <para>You can create new copy locations, or edit existing copy locations. To create a\r
-                  new shelving location type in the name, and select <guilabel>Yes</guilabel> or\r
-                     <guilabel>No</guilabel> for the various attributes: <guilabel>OPAC Visible,\r
-                     Holdable, Circulate,</guilabel> and <guilabel>Hold Verify</guilabel>.\r
-                     <guilabel>Holdable</guilabel> means a patron is able to place a hold on an item\r
-                  in this location; <guilabel>Hold Verify</guilabel> means staff will be prompted\r
-                  before an item is captured for a hold.  Finally click\r
-                     <guibutton>Create</guibutton>.</para>\r
-               <para>\r
-                  <mediaobject>\r
-                     <alt>screenshot of staff client</alt>\r
-                     <imageobject>\r
-                        <imagedata scalefit="0" fileref="../media/lsa-14.jpg"/>\r
-                     </imageobject>\r
-\r
-                  </mediaobject>\r
-               </para>\r
-            </informalfigure>\r
-         </step>\r
-         <step>\r
-            <informalfigure>\r
-               <para>In the bottom part of the <guilabel>Copy Locations Editor</guilabel> you can\r
-                  edit or delete existing copy locations. You cannot delete a location that contains\r
-                  items. In this example the copy location <guilabel>Adult Videos</guilabel> is\r
-                  being edited.</para>\r
-               <para>\r
-                  <mediaobject>\r
-                     <alt>screenshot of staff client</alt>\r
-                     <imageobject>\r
-                        <imagedata width="100%" scalefit="1" fileref="../media/lsa-16.jpg"/>\r
-                     </imageobject>\r
-                  </mediaobject>\r
-               </para>\r
-            </informalfigure>\r
-         </step>\r
-      </procedure>\r
-      <tip>\r
-         <para>There are also options in the <guilabel>Copy Editor</guilabel> for a copy to be\r
-               <guilabel>OPAC Visible</guilabel>-yes or no, <guilabel>Holdable</guilabel>-yes or no,\r
-            or <guilabel>Circulate</guilabel>-yes or no.  If either the copy record or the shelving\r
-            location is set to Circulate-no, then the item will not be able to circulate.</para>\r
-      </tip>\r
-      <informalfigure>\r
-         <para>This is where you see the shelving locations in the <guilabel>Copy\r
-            Editor</guilabel>:</para>\r
-\r
-         <para>\r
-            <mediaobject>\r
-               <alt>screenshot of staff client</alt>\r
-               <imageobject>\r
-                  <imagedata scalefit="0" fileref="../media/lsa-17.jpg"/>\r
-               </imageobject>\r
-            </mediaobject>\r
-         </para>\r
-      </informalfigure>\r
-      <para>This is where the shelving location appears in the OPAC.</para>\r
-      <para>\r
-         <mediaobject>\r
-            <alt>screenshot of staff client</alt>\r
-            <imageobject>\r
-               <imagedata scalefit="0" fileref="../media/lsa-18.jpg"/>\r
-            </imageobject>\r
-         </mediaobject>\r
-      </para>\r
-   </section>\r
-   <section xml:id="lsa-library-settings">\r
-      <info>\r
-         <title>Library Settings Editor</title>\r
-       <indexterm><primary>library settings editor</primary></indexterm>\r
-      </info>\r
-      <para>With the <guilabel>Library Settings Editor</guilabel> Local System Admnistrators (LSAs)\r
-         can optionally customize Evergreen's behaviour for a particular library or library system.\r
-         For descriptions of available settings see the <link\r
-            linkend="lsa-library-settings-overview">Settings Overview</link> table below. \r
-       </para>\r
-      <para>To open the <guilabel>Library Settings Editor</guilabel> select <menuchoice>\r
-            <guimenu>Admin (-)</guimenu>\r
-            <guisubmenu>Local Adminstration</guisubmenu>\r
-            <guimenuitem>Library Settings Editor</guimenuitem>\r
-         </menuchoice>. </para>\r
-      <simplesect>\r
-         <title>Settings Overview</title>\r
-         <para>This table describes available settings and shows which LSAs can change on a\r
-            per-library basis. Below the table is a list of <link\r
-               linkend="lsa-library-settings-data">data types</link> with details about acceptable\r
-            settings values.</para>\r
-         <informaltable xml:id="lsa-library-settings-overview">\r
-            <tgroup cols="4" align="left" colsep="1" rowsep="1">\r
-               <colspec colnum="1" colname="setting" colwidth="2.0*"/>\r
-               <colspec colnum="2" colname="description" colwidth="3.0*"/>\r
-               <colspec colnum="3" colname="type" colwidth="1.0*"/>\r
-               <colspec colnum="4" colname="notes" colwidth="2.0*"/>\r
-               <thead>\r
-                  <row>\r
-                     <entry>Setting</entry>\r
-                     <entry>Description</entry>\r
-                     <entry>Data type</entry>\r
-                     <entry>Notes</entry>\r
-                  </row>\r
-               </thead>\r
-               <tbody>\r
-                  <row>\r
-                     <entry>Alert on empty bib records</entry>\r
-                     <entry>Alert staff before the last copy for a record is deleted</entry>\r
-                     <entry><link linkend="lsa-data-types">True/false</link></entry>\r
-                    <entry></entry>\r
-                  </row>\r
-                  <row>\r
-                     <entry>Allow Credit Card Payments</entry>\r
-                     <entry>Not available</entry>\r
-                     <entry><link linkend="lsa-data-types">True/false</link></entry>  \r
-                     <entry></entry>\r
-                  </row>\r
-                  <row>\r
-                     <entry>Change reshelving status interval</entry>\r
-                     <entry>Amount of time to wait before changing an item from “reshelving” status\r
-                        to “available”</entry>\r
-                     <entry>\r
-                        <link linkend="lsa-data-types">Duration</link>\r
-                     </entry>\r
-                     <entry></entry>\r
-                  </row>\r
-                  <row>\r
-                     <entry>Charge item price when marked damaged </entry>\r
-                     <entry>If true Evergreen bills item price to the last patron who checked out\r
-                        the damaged item. Staff receive an alert with patron information and must\r
-                        confirm the billing.</entry>\r
-                     <entry>\r
-                        <link linkend="lsa-data-types">True/false</link>\r
-                     </entry>\r
-                    <entry>\r
-                     </entry>\r
-                  </row>\r
-                  <row>\r
-                     <entry>Charge processing fee for damaged items</entry>\r
-                     <entry>Optional processing fee billed to last patron who checked out the\r
-                        damaged item. Staff receive an alert with patron information and must\r
-                        confirm the billing.</entry>\r
-                     <entry><link linkend="lsa-data-types">Number</link> (dollars)</entry>\r
-                     <entry>Disabled when set to 0</entry>\r
-                  </row>\r
-                  <row>\r
-                     <entry>Circ: Lost items usable on checkin</entry>\r
-                     <entry>Lost items are usable on checkin instead of going 'home' first</entry>\r
-                     <entry>\r
-                        <link linkend="lsa-data-types">True/false</link>\r
-                     </entry>\r
-                     <entry/>\r
-                  </row>\r
-                  <row>\r
-                     <entry>Circ: Restore overdues on lost item return</entry>\r
-                     <entry>If true when a lost item is checked in overdue fines are charged (up to\r
-                        the maximum fines amount)</entry>\r
-                     <entry>\r
-                        <link linkend="lsa-data-types">True/false</link>\r
-                     </entry>\r
-                    \r
-                     <entry/>\r
-                  </row>\r
-\r
-                  <row>\r
-                     <entry>Circ: Void lost item billing when returned</entry>\r
-                     <entry>If true,when a lost item is checked in the item replacement bill (item\r
-                        price) is voided. If the patron has already paid the bill a credit is\r
-                        applied.</entry>\r
-                     <entry>\r
-                        <link linkend="lsa-data-types">True/false</link>\r
-                     </entry>\r
-                    \r
-                     <entry/>\r
-                  </row>\r
-\r
-                  <row>\r
-                     <entry>Circ: Void lost max interval</entry>\r
-                     <entry>Items that have been lost this long will not result in voided billings\r
-                        when returned. Only applies if <guilabel>Circ: Void lost item\r
-                           billing</guilabel> or <guilabel>Circ: Void processing fee on lost\r
-                           item</guilabel> are true.</entry>\r
-                     <entry>\r
-                        <link linkend="lsa-data-types">Duration</link>\r
-                     </entry>\r
-                    \r
-                     <entry/>\r
-                  </row>\r
-\r
-                  <row>\r
-                     <entry>Circ: Void processing fee on lost item return</entry>\r
-                     <entry>If true the processing fee is voided when a lost item is\r
-                        returned</entry>\r
-                     <entry>\r
-                        <link linkend="lsa-data-types">True/false</link>\r
-                     </entry>\r
-                    \r
-                     <entry/>\r
-                  </row>\r
-\r
-                  <row>\r
-                     <entry>Default Item Price</entry>\r
-                     <entry>Replacement charge for lost items if price is unset in the <guilabel>Copy Editor</guilabel>. \r
-                       Does not apply if item price is set to $0</entry>\r
-                     <entry><link linkend="lsa-data-types">Number</link> (dollars)</entry>\r
-                    \r
-                     <entry/>\r
-                  </row>\r
-\r
-                  <row>\r
-                     <entry>Default locale</entry>\r
-                     <entry>Sets language used in staff client</entry>\r
-                     <entry><link linkend="lsa-data-types">Text</link> (dollars)</entry>\r
-                     \r
-                     <entry>Can be set for each workstation at login</entry>\r
-                  </row>\r
-\r
-                  <row xml:id="lsa-do-not-automatically-delete">\r
-                     <entry>Do not automatically delete empty bib records</entry>\r
-                     <entry>If false bib records (aka MARC records) will automatically be deleted\r
-                        when the last attached volume is deleted </entry>\r
-                     <entry>\r
-                        <link linkend="lsa-data-types">True/false</link>\r
-                     </entry>\r
-                     \r
-                     <entry>Set to <emphasis>false</emphasis> to avoid orphaned bib records</entry>\r
-                  </row>\r
-\r
-                  <row xml:id="lsa-library-settings-button">\r
-                     <entry>GUI: Above-Tab Button Bar </entry>\r
-                     <entry>If true the staff client button bar\r
-                        appears by default on all workstations registered to your library; staff can\r
-                        override this setting at each login.</entry>\r
-                     <entry>\r
-                        <link linkend="lsa-data-types">True/false</link>\r
-                     </entry>\r
-                    \r
-                     <entry/>\r
-                  </row>\r
-\r
-                  <row xml:id="lsa-library-settings-horizontal">\r
-                     <entry>GUI: Alternative Horizontal Patron Summary Panel</entry>\r
-                     <entry>If true replaces the vertical patron summary panel with a horizontal one\r
-                        on all workstations registered to your library</entry>\r
-                     <entry>\r
-                        <link linkend="lsa-data-types">True/false</link>\r
-                     </entry>\r
-                    \r
-                     <entry/>\r
-                  </row>\r
-\r
-                  <row>\r
-                     <entry>GUI: Network Activity Meter</entry>\r
-                     <entry>If true displays a progress bar when the staff client is sending or\r
-                        receiving information from the Evergreen server</entry>\r
-                     <entry>\r
-                        <link linkend="lsa-data-types">True/false</link>\r
-                     </entry>\r
-                    \r
-                     <entry/>\r
-                  </row>\r
-                  <row>\r
-                     <entry>GUI: Patron display timeout interval</entry>\r
-                     <entry>Patron accounts opened in the staff client will close if inactive for\r
-                        this period of time</entry>\r
-                     <entry>\r
-                        <link linkend="lsa-data-types">Duration</link>\r
-                     </entry>\r
-                    \r
-                     <entry>Not functional in this version of Evergreen</entry>\r
-                  </row>\r
-\r
-                  <row>\r
-                     <entry>Holds: Estimated Wait (Days) </entry>\r
-                     <entry>Average number of days between check out and check in, multiplied by a\r
-                        patron's position in the hold queue to estimate wait for holds</entry>\r
-                     <entry>\r
-                        <link linkend="lsa-data-types">Number</link>\r
-                     </entry>\r
-                     \r
-                     <entry>Not yet implemented</entry>\r
-                  </row>\r
-\r
-                  <row>\r
-                     <entry>Holds: Expire Alert Interval</entry>\r
-                     <entry>Time before a hold expires at which to send an email notifying the\r
-                        patron</entry>\r
-                     <entry>\r
-                        <link linkend="lsa-data-types">Duration</link>\r
-                     </entry>\r
-                    \r
-                     <entry>Only applies if your library notifies patrons of expired holds. </entry>\r
-                  </row>\r
-\r
-                  <row>\r
-                     <entry>Holds: Expire Interval</entry>\r
-                     <entry>Amount of time until an unfulfilled hold expires</entry>\r
-                     <entry>\r
-                        <link linkend="lsa-data-types">Duration</link>\r
-                     </entry>\r
-                    \r
-                     <entry/>\r
-                  </row>\r
-\r
-                  <row>\r
-                     <entry>Holds: Hard boundary</entry>\r
-                     <entry>Administrative setting</entry>\r
-                     <entry>\r
-                        <link linkend="lsa-data-types">Number</link>\r
-                     </entry>\r
-                     \r
-                     <entry/>\r
-                  </row>\r
-                  <row>\r
-                     <entry>Holds: Soft boundary</entry>\r
-                     <entry>Administrative setting</entry>\r
-                     <entry>\r
-                        <link linkend="lsa-data-types">Number</link>\r
-                     </entry>\r
-                     \r
-                     <entry/>\r
-                  </row>\r
-\r
-                  <row>\r
-                     <entry>Holds: Soft stalling interval</entry>\r
-                     <entry>Administrative setting</entry>\r
-                     <entry>\r
-                        <link linkend="lsa-data-types">Duration</link>\r
-                     </entry>\r
-                     \r
-                     <entry/>\r
-                  </row>\r
-                  <row>\r
-                     <entry>Juvenile Age Threshold</entry>\r
-                     <entry>Upper cut-off age for patrons to be considered juvenile, calculated from\r
-                        date of birth in patron accounts</entry>\r
-                     <entry><link linkend="lsa-data-types">Duration</link> (years)</entry>\r
-                    \r
-                     <entry/>\r
-                  </row>\r
-\r
-                  <row>\r
-                     <entry>Lost Materials Processing Fee</entry>\r
-                     <entry>The amount charged in addition to item price when an item is marked los.\r
-                         </entry>\r
-                     <entry><link linkend="lsa-data-types">Number</link> (dollars)</entry>\r
-                    \r
-                     <entry/>\r
-                  </row>\r
-\r
-                  <row>\r
-                     <entry>Maximum previous checkouts displayed</entry>\r
-                     <entry>Number of previous circulations displayed in staff client</entry>\r
-                     <entry>\r
-                        <link linkend="lsa-data-types">Number</link>\r
-                     </entry>\r
-                    \r
-                     <entry/>\r
-                  </row>\r
-                  <row>\r
-                     <entry>OPAC Inactivity Timeout (in seconds)</entry>\r
-                     <entry>Number of seconds of inactivity before OPAC accounts are automatically\r
-                        logged out.</entry>\r
-                     <entry>\r
-                        <link linkend="lsa-data-types">Number</link>\r
-                     </entry>\r
-                    \r
-                     <entry/>\r
-                  </row>\r
-\r
-                  <row>\r
-                     <entry>OPAC: Allow pending addresses</entry>\r
-                     <entry>If true patrons can edit their addresses in the OPAC. Changes must be\r
-                        approved by staff</entry>\r
-                     <entry>\r
-                        <link linkend="lsa-data-types">True/false</link>\r
-                     </entry>\r
-                    \r
-                     <entry/>\r
-                  </row>\r
-                  <row>\r
-                     <entry>Password format</entry>\r
-                     <entry>Defines acceptable format for OPAC account passwords</entry>\r
-                     <entry> Regular expression </entry>\r
-                     \r
-                     <entry>Default requires that passwords "be at least 7 characters in length,\r
-                        contain at least one letter (a-z/A-Z), and contain at least one number.\r
-                        </entry>\r
-                  </row>\r
-\r
-                  <row>\r
-                     <entry>Patron barcode format </entry>\r
-                     <entry>Defines acceptable format for patron barcodes</entry>\r
-                     <entry> Regular expression </entry>\r
-                     \r
-                     <entry></entry>\r
-                  </row>\r
-\r
-                  <row xml:id="library-settings-phone-password">\r
-                     <entry>Patron: password from phone #</entry>\r
-                     <entry>If true the last 4 digits of the patron's phone number is the password\r
-                        for new accounts (password must still be changed at first OPAC\r
-                        login)</entry>\r
-                     <entry>\r
-                        <link linkend="lsa-data-types">True/false</link>\r
-                     </entry>\r
-                    \r
-                     <entry/>\r
-                  </row>\r
-                  <row>\r
-                     <entry>Selfcheck: Patron Login Timeout (in seconds)</entry>\r
-                     <entry>Administrative setting</entry>\r
-                     <entry>\r
-                        <link linkend="lsa-data-types">Number</link>\r
-                     </entry>\r
-                     \r
-                     <entry>Not for SIP connections</entry>\r
-                  </row>\r
-\r
-                  <row>\r
-                     <entry>Selfcheck: Pop-up alert for errors</entry>\r
-                     <entry>Administrative setting</entry>\r
-                     <entry>\r
-                        <link linkend="lsa-data-types">True/false</link>\r
-                     </entry>\r
-                     \r
-                     <entry>Not for SIP connections</entry>\r
-                  </row>\r
-                  <row>\r
-                     <entry>Selfcheck: Require patron password</entry>\r
-                     <entry>Administrative setting</entry>\r
-                     <entry>\r
-                        <link linkend="lsa-data-types">True/false</link>\r
-                     </entry>\r
-                     \r
-                     <entry>Not for SIP connections</entry>\r
-                  </row>\r
-\r
-                  <row>\r
-                     <entry>Sending email address for patron notices</entry>\r
-                     <entry>This email address is for automatically generated patron notices (e.g.\r
-                        email overdues, email holds notification).  It is good practice to set up a\r
-                        generic account, like info@nameofyourlibrary.ca, so that one person’s\r
-                        individual email inbox doesn’t get cluttered with emails that were not\r
-                        delivered.</entry>\r
-                     <entry>\r
-                        <link linkend="lsa-data-types">Text</link>\r
-                     </entry>\r
-                    \r
-                     <entry/>\r
-                  </row>\r
-\r
-                  <row xml:id="lsa-show-billing-tab-first">\r
-                     <entry>Show billing tab first when bills are present</entry>\r
-                     <entry>If true, accounts for patrons with bills will open to the billing tab\r
-                        instead of check out</entry>\r
-                     <entry>\r
-                        <link linkend="lsa-data-types">True/false</link>\r
-                     </entry>\r
-                     <entry></entry>\r
-                  </row>\r
-                  <row>\r
-                     <entry>Staff Login Inactivity Timeout (in seconds)</entry>\r
-                     <entry>Number of seconds of inactivity before staff client prompts for login\r
-                        and password.</entry>\r
-                     <entry>\r
-                        <link linkend="lsa-data-types">Number</link>\r
-                     </entry>\r
-                    <entry>\r
-                     </entry>\r
-                  </row>\r
-\r
-                  <row>\r
-                     <entry>Void overdue fines when items are marked lost</entry>\r
-                     <entry>If true overdue fines are voided when an item is marked lost</entry>\r
-                     <entry>\r
-                        <link linkend="lsa-data-types">True/false</link>\r
-                     </entry>\r
-                    <entry>\r
-                     </entry>\r
-                  </row>\r
-\r
-               </tbody>\r
-            </tgroup>\r
-         </informaltable>\r
-\r
-\r
-         <para xml:id="lsa-library-settings-data">Acceptable formats for each setting type are\r
-            listed below. Quotation marks are never required when updating settings in the staff\r
-            client.</para>\r
-\r
-\r
-         <informaltable xml:id="lsa-data-types">\r
-\r
-            <tgroup cols="2" align="left" colsep="1" rowsep="1">\r
-               <colspec colnum="1" colname="type" colwidth="1.0*"/>\r
-               <colspec colnum="2" colname="formatting" colwidth="5.0*"/>\r
-             \r
-\r
-               <thead>\r
-                  <row>\r
-                     <entry>Data type</entry>\r
-                     <entry>Formatting</entry>\r
-                  </row>\r
-               </thead>\r
-\r
-\r
-\r
-               <tbody>\r
-                  <row>\r
-                     <entry>True/false</entry>\r
-                     <entry>Select value from drop-down menu</entry>\r
-                  </row>\r
-                  <row>\r
-                     <entry>Number</entry>\r
-                     <entry>Enter a numerical value (decimals allowed in price settings)</entry>\r
-                  </row>\r
-                  <row>\r
-                     <entry>Duration</entry>\r
-                     <entry>Enter a number followed by a space and any of the following units:\r
-                        minutes, hours, days, months (30 minutes, 2 days, etc)</entry>\r
-                  </row>\r
-                  <row>\r
-                     <entry>Text</entry>\r
-                     <entry>Free text</entry>\r
-                  </row>\r
-\r
-\r
-               </tbody>\r
-            </tgroup>\r
-         </informaltable>\r
-\r
-\r
-      </simplesect>\r
-\r
-\r
-\r
-   </section>\r
-   <section xml:id="lsa-noncat">\r
-      <info>\r
-         <title>Non-Catalogued Type Editor </title>\r
-       <indexterm><primary>non-catalogued type editor</primary></indexterm>\r
-      </info>\r
-\r
-      <para>This is where you configure your non-catalogued types that appear in the dropdown menu\r
-         for non-catalogued circulations. </para>\r
-\r
-      <procedure>\r
-         <step>\r
-\r
-            <para>Select <menuchoice>\r
-                  <guimenu>Admin (-)</guimenu>\r
-                  <guisubmenu>Local Administration</guisubmenu>\r
-                  <guimenuitem>Non Catalogued Type Editor</guimenuitem>\r
-               </menuchoice>.</para>\r
-\r
-\r
-         </step>\r
-\r
-         <step>\r
-            <informalfigure>\r
-               <para>To set up a new non-catalogued type, type the name in the left hand box, and\r
-                  choose how many days the item will circulate for.  Click\r
-                     <guibutton>Create</guibutton>.</para>\r
-               <para>\r
-                  <mediaobject>\r
-                     <alt>screenshot of staff client</alt>\r
-                     <imageobject>\r
-                        <imagedata scalefit="0" fileref="../media/lsa-22.png"/>\r
-                     </imageobject>\r
-\r
-                  </mediaobject>\r
-               </para>\r
-            </informalfigure>\r
-            <para>Select the <guilabel>Circulate In-House</guilabel> box for non-catalogued items\r
-               that will circulate in house.  This can be used to manually track computer use, or\r
-               meeting room rentals.  </para>\r
-         </step>\r
-      </procedure>\r
-\r
-\r
-\r
-\r
-      <informalfigure>\r
-         <para>This is what the dropdown menu for non-catalogued circulations in the patron checkout\r
-            screen looks like:</para>\r
-\r
-         <para>\r
-            <mediaobject>\r
-               <alt>screenshot of staff client</alt>\r
-               <imageobject>\r
-                  <imagedata scalefit="0" fileref="../media/lsa-23.jpg"/>\r
-               </imageobject>\r
-\r
-            </mediaobject>\r
-         </para>\r
-      </informalfigure>\r
-   </section>