From: Dan Scott Date: Mon, 21 May 2012 02:51:52 +0000 (-0400) Subject: Merge the Evergreen docs into the code repository X-Git-Url: https://old-git.evergreen-ils.org/?a=commitdiff_plain;h=4ea6279c37a5035472879281ae251aff9259554d;p=evergreen%2Ftadl.git Merge the Evergreen docs into the code repository Rather than maintaining two separate repositories, with dual maintenance of what are essentially single-sourced files in the release notes and the install instructions, make better use of the docs/ subfolder of the Evergreen repository. If this crazy scheme works, DIG can commit to the docs/ subfolder, and devs can commit there too. Signed-off-by: Dan Scott --- diff --git a/.gitignore b/.gitignore index d9e24bf06f..8b5efd3b5f 100644 --- a/.gitignore +++ b/.gitignore @@ -15,6 +15,8 @@ config.sub configure depcomp docs/RELEASE_NOTES_2_2.html +docs/root.html +docs/root.pdf install-sh libtool ltmain.sh diff --git a/acquisitions/introduction.txt b/acquisitions/introduction.txt deleted file mode 100644 index 4680506820..0000000000 --- a/acquisitions/introduction.txt +++ /dev/null @@ -1,25 +0,0 @@ -Acquisitions ------------- - -This section is intended for those who are responsible for managing and processing acquisitions. - -Before beginning to use Acquisitions, the following must be configured by an administrator: - -* Cancel/Suspend Reasons (optional) -* Claiming (optional) -* Currency Types (defaults exist) -* Distribution Formulas (optional) -* EDI Accounts (optional) (see link:../installation/edi_setup.txt[Setting Up EDI Acquisitions] under Software Installation) -* Exchange Rates (defaults exist) -* Funds and Fund Sources -* Invoice Types (defaults exist) and Invoice Payment Methods -* Line Item Features (optional) -* Merge Overlay Profiles and Record Match Sets (see link:../cataloging/batch_importing_MARC.txt[Batch Importing MARC Records] in Cataloging) -* Providers - -Acquisitons Workflow -~~~~~~~~~~~~~~~~~~~~ - -The following diagram shows how the workflow functions in Evergreen. One of the differences in this process you should notice is that when creating a selection list on the vendor site, libraries will be downloading and importing the vendor bibs and item records. - -image::media/acq_workflow.jpg[workflow diagram] diff --git a/acquisitions/receive_items_from_invoice.txt b/acquisitions/receive_items_from_invoice.txt deleted file mode 100644 index 8c0adca25b..0000000000 --- a/acquisitions/receive_items_from_invoice.txt +++ /dev/null @@ -1,73 +0,0 @@ -Receive Items From an Invoice ------------------------------ - -This feature enables users to receive items from an invoice. Staff can receive individual copies, or they can receive items in batch. - -Receive Items in Batch (List Mode) -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -In this example, we have created a purchase order, added line items and copies, and activated the purchase order. We will create an invoice from the purchase order, receive items, and invoice them. We will receive the items in batch from the invoice. - -1) Retrieve a purchase order. - -2) Click *Create Invoice*. - -image::media/Receive_Items_From_an_Invoice1.jpg[Receive_Items_From_an_Invoice1] - -3) The blank invoice appears. In the top half of the invoice, enter descriptive information about the invoice. In the bottom half of the invoice, enter the number of items for which you were invoiced, the amount that you were billed, and the amount that you paid. - - -image::media/Receive_Items_From_an_Invoice2.jpg[Receive_Items_From_an_Invoice2] - - -4) Click *Save*. You must choose a save option before you can receive items. - - -5) The screen refreshes. In the top right corner of the screen, click *Receive Items*. - - -6) The *Acquisitions Invoice Receiving* screen opens. By default, this screen enables users to receive items in batch, or *Numeric Mode*. You can select the number of copies that you want to receive; you are not receiving specific copies in this mode. - - -7) Select the number of copies that you want to receive. By default, the number that you invoiced will appear. In this example, we will receive one copy of each title. - - -NOTE: You cannot receive fewer items than 0 (zero) or more items than the number that you ordered. - - -8) Click *Receive Selected Copies*. - - -image::media/Receive_Items_From_an_Invoice4.jpg[Receive_Items_From_an_Invoice4] - - -9) When you are finished receiving items, close the screen. You can repeat this process as you receive more copies. - - - -Receive Specific Copies (Numeric Mode) -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -In this example, we have created a purchase order, added line items and copies, and activated the purchase order. We will create an invoice from the purchase order, receive items, and invoice them. We will receive specific copies from the invoice. This function may be useful to libraries who purchase items that have been barcoded by their vendor. - - -1) Complete steps 1-5 in the previous section. - -2) The *Acquisitions Invoice Receiving* screen by default enables user to receive items in batch, or *Numeric Mode*. Click *Use List Mode* to receive specific copies. - -3) Select the check boxes adjacent to the copies that you want to receive. Leave unchecked the copies that you do not want to receive. - -4) Click *Receive Selected Copies*. - -image::media/Receive_Items_From_an_Invoice5.jpg[Receive_Items_From_an_Invoice5] - - -The screen will refresh. Copies that have not yet been received remain on the screen so that you can receive them when they arrive. - - -5) When all copies on an invoice have been received, a message confirms that no copies remain to be received. - -6) The purchase order records that all items have been received. - -image::media/Receive_Items_From_an_Invoice7.jpg[Receive_Items_From_an_Invoice7] - diff --git a/acquisitions/selection_lists_po.txt b/acquisitions/selection_lists_po.txt deleted file mode 100644 index e308d056cc..0000000000 --- a/acquisitions/selection_lists_po.txt +++ /dev/null @@ -1,136 +0,0 @@ -Selection Lists and Purchase Orders ------------------------------------ - -Selection Lists -~~~~~~~~~~~~~~~ - -Selection lists allow you to create, manage, and save lists of items that you may want to purchase. To view your selection list, click Acquisitions -> My Selection Lists. Use the general search to view selection lists created by other users. - -Create a selection list -^^^^^^^^^^^^^^^^^^^^^^^ - -Selection lists can be created in four areas within the module. Selection lists can be created when you link:brief_records.txt[Add Brief Records], Upload MARC Order Records, or find records through the link:federated.txt[MARC Federated Search]. In each of these interfaces, you will find the Add to Selection List field. Enter the name of the selection list that you want to create in that field. - -Selection lists can also be created through the My Selection Lists interface: - -. Click Acquisitions -> My Selection Lists. -. Click the New Selection List drop down arrow. -. Enter the name of the selection list in the box that appears. -. Click Create. - -image::media/acq_selection_create.png[create selection list] - -Add items to a selection list -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -You can add items to a selection list in one of three ways: link:brief_records.txt[add a brief record]; upload MARC order records; add records through a link:federated.txt[federated search]; or use the link:federated.txt[View/Place Orders] menu item in the catalog. - -Clone selection lists -^^^^^^^^^^^^^^^^^^^^^ - -Cloning selection lists enables you to copy one selection list into a new selection list. You can maintain both copies of the list, or you can delete the previous list. - -. Click Acquisitions -> My Selection Lists. -. Check the box adjacent to the list that you want to clone. -. Click Clone Selected. -. Enter a name into the box that appears, and click Clone. - -image::media/acq_selection_clone.png[clone selection list] - -Merge selection lists -^^^^^^^^^^^^^^^^^^^^^ - -You can merge two or more selection lists into one selection list. - - -. Click Acquisitions -> My Selection Lists. -. Check the boxes adjacent to the selection lists that you want to merge, and click Merge Selected. -. Choose the Lead Selection List from the drop down menu. This is the list to which the items on the other list(s) will be transferred. -. Click Merge. - -image::media/acq_selection_merge.png[merge selection list] - -Delete selection lists -^^^^^^^^^^^^^^^^^^^^^^ - -You can delete selection lists that you do not want to save. You will not be able to retrieve these items through the General Search after you have deleted the list. You must delete all line items from a selection list before you can delete the list. - - -. Click Acquisitions -> My Selection Lists. -. Check the box adjacent to the selection list(s) that you want to delete. -. Click Delete Selected. - -Mark Ready for Selector -^^^^^^^^^^^^^^^^^^^^^^^ - -After an item has been added to a selection list or purchase order, you can mark it ready for selector. This step is optional but may be useful to individual workflows. - - -. If you want to mark part of a selection list ready for selector, then you can check the box(es) of the line item(s) that you wish to mark ready for selector. If you want to mark the entire list ready for selector, then skip to step 2. -. Click Actions -> Mark Ready for Selector. -. A pop up box will appear. Choose to mark the selected line items or all line items. -. Click Go. -. The screen will refresh. The marked line item(s) will be highlighted pink, and the status changes to selector~ready. - -image::media/acq_selection_mark_ready.png[mark ready] - -Convert selection list to purchase order -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -Use the Actions menu to convert a selection list to a purchase order. - - -. From a selection list, click Actions ~> Create Purchase Order. -. A pop up box will appear. -. Select the ordering agency from the drop down menu. -. Enter the provider. -. Check the box adjacent to prepayment required if prepayment is required. -. Choose if you will add All Lineitems or Selected Lineitems to your purchase order. -. Check the box if you want to Import Bibs and Create Copies in the catalog. -. Click Submit. - -Brief Records -~~~~~~~~~~~~~ - -Brief records are short bibliographic records with minimal information that are often used as placeholder records until items are received. Brief records can be added to selection lists or purchase orders and can be imported into the catalog. You can add brief records to new or existing selection lists. You can add brief records to new, pending or on~order purchase orders. - -Add brief records to a selection list -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -. Click Acquisitions -> New Brief Record. You can also add brief records to an existing selection list by clicking the Actions menu on the selection list and choosing Add Brief Record. -. Choose a selection list from the drop down menu, or enter the name of a new selection list. -. Enter bibliographic information in the desired fields. -. Click Save Record. - -image::media/acq_brief_record.png[] - -Add brief records to purchase orders -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -You can add brief records to new or existing purchase orders. - -. Open or create a purchase order. See the section on link:03~PO.txt[purchase orders] for more information. -. Click Add Brief Record. -. Enter bibliographic information in the desired fields. Notice that the record is added to the purchase order that you just created. -. Click Save Record. - -image::media/acq_brief_record-2.png[] - -MARC Federated Search -~~~~~~~~~~~~~~~~~~~~~ - -The MARC Federated Search enables you to import bibliographic records into a selection list or purchase order from a Z39.50 source. - -. Click Acquisitions -> MARC Federated Search. -. Check the boxes of Z39.50 services that you want to search. Your local Evergreen Catalog is checked by default. Click Submit. -+ ----- -image::media/acq_marc_search.png[search form] ----- -+ -. A list of results will appear. Click the "Copies" link to add copy information to the line item. See the link:line_items.txt[section on Line Items] for more information. -. Click the Notes link to add notes or line item alerts to the line item. See the link:line_items.txt[section on Line Items] for more information. -. Enter a price in the "Estimated Price" field. -. You can save the line item(s) to a selection list by checking the box on the line item and clicking Actions -> Save Items to Selection List. You can also create a purchase order from the line item(s) by checking the box on the line item and clicking Actions ~> Create Purchase Order. - -image::media/acq_marc_search-2.png[line item] diff --git a/acquisitions/vandelay_acquisitions_integration.txt b/acquisitions/vandelay_acquisitions_integration.txt deleted file mode 100644 index 51fc2fa472..0000000000 --- a/acquisitions/vandelay_acquisitions_integration.txt +++ /dev/null @@ -1,69 +0,0 @@ -Vandelay Integration into Acquisitions --------------------------------------- -The Acquisitions Load MARC Order Record interface enables you to add MARC records to selection lists and purchase orders and upload the records into the catalog. The Vandelay interface enables you to create specific match points between incoming MARC records and exisiting catalog records. Combining these two features enables you to track on order MARC records through the Acquisitions interface and to utilize the record matching mechanisms available in Vandelay. - -The purpose of this documentation is to describe the interaction between Vandelay and the Acquisitions MARC Batch Upload interface. For detailed instructions on - using the Acquisitions MARC Batch Upload interface, see the Evergreen Documentation Interest Group's Book of Evergreen, 2.1 documentation, Chapter 5, Load MARC -Order Records. For detailed instructions on using the Vandelay functions for record matching and importing, see the Evergreen Documentation Interest Group's Book of Evergreen, -2.2 documentation, Chapter 7, Batch Importing MARC Records. - -*Use Cases for Vandelay Integration into Acquisitions* - -You can add items to a selection list or purchase order and ignore the Vandelay options, or you can use both acquisitions and cataloging functions. In these examples, you will use both functions. - -Example 1: Using the Acquisitions MARC Batch Load interface, upload MARC records to a selection list and a Vandelay queue, and match queued records with existing catalog records. - -In this example, an acquisitions librarian has received a batch of MARC records from a vendor. She will add the records to a selection list and a Vandelay record queue. -A cataloger will later view the queue, edit the records, and import them into the catalog. - -. Click *Acquisitions -> Load MARC Order Records* -. Add MARC order records to a *Selection list* and/or a *Purchase Order.* Check the box to create a purchase order if desired. -. Select a *Provider* from the drop down menu, or begin typing the code for the provider, and the field will auto-fill. -. Select a *Context Org Unit* from the drop down menu, or begin typing the code for the context org unit, and the field will auto-fill. -. Select a *Selection List* from the drop down menu, or begin typing the name of the selection list. You can create a new list, or the field will auto-fill. -. Create a new record queue in Vandelay, or upload the records to an existing queue. -. Select a *Record Match Set*. -. Browse your computer to find the MARC file, and click *Upload*. -+ -image::media/Vandelay_Integration_into_Acquisitions1.jpg[Vandelay_Integration_into_Acquisitions1] -+ -. The processed items appear at the bottom of the screen. -+ -image::media/Vandelay_Integration_into_Acquisitions2.jpg[Vandelay_Integration_into_Acquisitions2] -. You can click the link(s) to access the selection list or the import queue. Click the link to *View Selection List*. -. Look at the first line item. The line item has not yet been linked to the catalog, but it is linked to a Vandelay record queue. Click the link to the *queue* to examine the MARC record. -+ -image::media/Vandelay_Integration_into_Acquisitions3.jpg[Vandelay_Integration_into_Acquisitions3] -. The Vandelay interface opens in a new tab. The bibliographic records appear in the queue. Records that have matches are identified in the queue. You can edit these records and/or import them into the catalog, completing the process. - -image::media/Vandelay_Integration_into_Acquisitions4.jpg[Vandelay_Integration_into_Acquisitions4] - -Example 2: Using the Acquisitions MARC Batch Load interface, upload MARC records to a selection list, and use the Vandelay options to import the records directly into the catalog. The Vandelay options will enable you to match incoming records with existing catalog records. - -In this example, a librarian will add MARC records to a selection list, create criteria for matching incoming and existing records, and import the matching and non-matching records into the catalog. - -. Click *Acquisitions* -> *Load MARC Order Records* -. Add MARC order records to a *Selection list* and/or a *Purchase Order.* Check the box to create a purchase order if desired. -. Select a *Provider* from the drop down menu, or begin typing the code for the provider, and the field will auto-fill. -. Select a *Context Org Unit* from the drop down menu, or begin typing the code for the context org unit, and the field will auto-fill. -. Select a *Selection List* from the drop down menu, or begin typing the name of the selection list. You can create a new list, or the field will auto-fill. -. Create a new record queue in Vandelay, or upload the records to an existing queue. -. Select a *Record Match Set*. -. Select *Merge Profile* -> *Match-Only Merge*. -. Check the box adjacent to *Merge on Best Match*. -. Browse your computer to find the MARC file, and click *Upload*. -+ -image::media/Vandelay_Integration_into_Acquisitions5.jpg[Vandelay_Integration_into_Acquisitions5] -+ -. Click the link to *View Selection List* Line items that do not match existing catalog records on title and ISBN contain the link, *link to catalog*. This link indicates that you could link the line item to a catalog record, but currently, no match exists between the line item and catalog records. Line items that do have matching records in the catalog contain the link, *catalog*. -+ -image::/media/Vandelay_Integration_into_Acquisitions6.jpg[Vandelay_Integration_into_Acquisitions6] -+ -. Click the *catalog* link to view the line item in the catalog. - -*Permissions to use this Feature* - -IMPORT_MARC - Using Vandelay to create new bib records now requres the IMPORT_MARC -permission (same as open-ils.cat.biblio.record.xml.import). If the permission fails, the queued record will fail import and be stamped with a new "import.record.perm_failure" vandelay import error - -IMPORT_ACQ_LINEITEM_BIB_RECORD_UPLOAD - This allows interfaces leveraging Vandelay, such as Acquisitions, to create a higher barrier to entry. This permission prevents users from creating new bib records directly from the ACQ vendor MARC file upload interface. diff --git a/admin/SMS_messaging.txt b/admin/SMS_messaging.txt deleted file mode 100644 index 94447002b2..0000000000 --- a/admin/SMS_messaging.txt +++ /dev/null @@ -1,122 +0,0 @@ -SMS Text Messaging ------------------- - -The SMS Text Messaging feature enables users to receive hold notices via text message. Users can opt-in to this hold notification as their default setting for all holds, or they -can receive specific hold notifications via text message. Users can also send call numbers and copy locations via text message. - -Administrative Setup -~~~~~~~~~~~~~~~~~~~~ - -You cannot receive text messages from Evergreen by default. You must enable this feature to receive hold notices and copy information from Evergreen via text message. - -Enable Text Messages -^^^^^^^^^^^^^^^^^^^^ - -. Click *Admin* -> *Local Admin* -> *Library Settings Editor.* -. Select the setting, *Enable features that send SMS text messages.* -. Set the value to *True,* and click *Update Setting.* - -image::media/SMS_Text_Messaging1.jpg[SMS_Text_Messaging1] - -Authenticate Patrons -^^^^^^^^^^^^^^^^^^^^ - -By default, you must be logged into your OPAC account to send a text message from Evergreen. However, if you disable this setting, you can text message copy information without having -to login to your OPAC account. - -To disable the patron login requirmement: - -. Click *Admin* -> *Local Administration* -> *Library Settings Editor.* -. Select the setting, *Disable auth requirement for texting call numbers*. -. Set the value to *True,* and click *Update Setting.* - -image::media/SMS_Text_Messaging2.jpg[SMS_Text_Messaging2] - -Configure SMS Carriers -^^^^^^^^^^^^^^^^^^^^^^ - -A list of SMS carriers that can transmit text messages to users is available in the staff client. Library staff can edit this list, or add new carriers. - -To add or edit SMS carriers: - -. Click *Admin* -> *Server Administration* -> *SMS Carriers*. -. To add a new carrier, click the *New Carrier* button in the top right corner of the screen. To edit an existing carrier, double click in any white space in the carrier's row. -+ -image::media/SMS_Text_Messaging3.jpg[SMS_Text_Messaging3] -+ -. Enter a (geographical) *Region*. -. Enter the carrier's *Name*. -. Enter an *Email Gateway.* The SMS carrier can provide you with the content for this field. The $number field is converted to the user's phone number when the text message is generated. -. Check the *Active* box to use this SMS Carrier. - -image::media/SMS_Text_Messaging4.jpg[SMS_Text_Messaging4] - -Configure Text Message Templates -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -Library staff control the content and format of text messages through the templates in Notifications/Action Triggers. Patrons cannot add free text to their text messages. - -To configure the text of the SMS text message: - -. Click *Admin* -> *Local Administration* -> *Notifications/Action Triggers.* -. Create a new A/T and template, or use or modify an existing template. For example, a default template, "Hold Ready for Pickup SMS Notification," notifies users that the hold is ready for pickup. -+ -image::media/SMS_Text_Messaging5.jpg[SMS_Text_Messaging5] -+ -. You can use the default template, or you can edit the template and add content specific to your library. Click the hyperlinked name to view and/or edit the hold notice. - -image::media/SMS_Text_Messaging6.jpg[SMS_Text_Messaging6] - -Receiving Holds Notices via Text Message -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -You can receive notification that your hold is ready for pickup from a text message that is sent to your mobile phone. - -. Login to your account. -+ -image::media/SMS_Text_Messaging12.jpg[SMS_Text_Messaging12] -+ -. Search the catalog. -. Retrieve a record, and click the *Place Hold* link. -. Select the option to retrieve hold notification via text message. -. Choose an SMS Carrier from the drop down menu. NOTE: You can enter your SMS carrier and phone number into your *Account Preferences* to skip steps five and six. -. Enter a phone number. -. Click *Submit.* - -image::media/SMS_Text_Messaging13.jpg[SMS_Text_Messaging13] - -Sending Copy Locations via Text Message -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - - -You can search the catalog for an item, and, after retrieving results for the item, click a hyperlink to send the copy location in a text message. - -. Login to your account in the OPAC. NOTE: If you have disabled the setting that requires patron login, then you do not have to login to their accounts to send text messages. -See *Administrative Setup* for more information. -+ -image::media/SMS_Text_Messaging7.jpg[SMS_Text_Messaging7] -+ -. Search the catalog, and retrieve a title with copies. -. Click the *Text* link adjacent to the call number. -+ -image::media/SMS_Text_Messaging8.jpg[SMS_Text_Messaging8] -+ -. The text of the SMS Text Message appears. -+ -image::media/SMS_Text_Messaging9.jpg[SMS_Text_Messaging9] -+ -. Choose an SMS Carrier from the drop down menu. NOTE: You can enter your SMS carrier and phone number into your *Account Preferences* to skip steps five and six. -. Enter a phone number. -+ -image::media/SMS_Text_Messaging10.jpg[SMS_Text_Messaging10] -+ -. Click *Submit*. -. The number and carrier are converted to an email address, and the text message is sent to your mobile phone. - -image::media/SMS_Text_Messaging11.jpg[SMS_Text_Messaging11] - -*Permissions to use this Feature* - -ADMIN_SMS_CARRIER - Enables users to add/create/delete SMS Carrier entries. - - diff --git a/admin/acquisitions_admin.txt b/admin/acquisitions_admin.txt deleted file mode 100644 index de4e329213..0000000000 --- a/admin/acquisitions_admin.txt +++ /dev/null @@ -1,490 +0,0 @@ -Acquisitions Administration ---------------------------- - -Acquisitions Permissions in the Admin module -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -Several setting in the Library Settings area of the Admin module pertain to functions in the Acquisitions module. You can access these settings by clicking _Admin -> Local Administration ->Library Settings Editor_. - -* CAT: Delete bib if all copies are deleted via Acquisitions lineitem cancellation - If you cancel a line item, then all of the on order copies in the catalog are deleted. If, when you cancel a line item, you also want to delete the bib record, then set this setting to TRUE. -* Default circulation modifier - This modifier would be applied to items that are created in the acquisitions module -* Default copy location - This copy location would be applied to items that are created in the acquisitions module -* Fund Spending Limit for Block - When the amount remaining in the fund, including spent money and encumbrances, goes below this percentage, attempts to spend from the fund will be blocked. -* Fund Spending Limit for Warning - When the amount remaining in the fund, including spent money and encumbrances, goes below this percentage, attempts to spend from the fund will result in a warning to the staff. -* Temporary barcode prefix - Temporary barcode prefix for items that are created in the acquisitions module -* Temporary call number prefix - Temporary call number prefix for items that are created in the acquisitions module - -Cancel/Suspend reasons -~~~~~~~~~~~~~~~~~~~~~~ - -The Cancel reasons link enables you to predefine the reasons for which a line item or a PO can be cancelled. A default list of reasons appears, but you can add custom reasons to this list. Applying the cancel reason will prevent the item from appearing in a claims list and will allow you to cancel debits associated with the purchase. Cancel reasons also enable you to suspend or delay a purchase. For example, you could create a cancel reason of 'back ordered,' and you could choose to keep the debits associated with the purchase. - -Create a cancel/suspend reason -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -. To add a new cancel reason, click _Administration -> Server Administration -> Acquisitions -> Cancel reasons_. - -. Click _New Cancel Reason_. - -. Select a using library from the drop down menu. The using library indicates the organizational units whose staff can use this cancel reason. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units.) - -. Create a label for the cancel reason. This label will appear when you select a cancel reason on an item or a PO. - -. Create a description of the cancel reason. This is a free text field and can be comprised of any text of your choosing. - -. If you want to retain the debits associated with the cancelled purchase, click the box adjacent to Keep Debits-> - -. Click _Save_. - -Claiming -~~~~~~~~ -Currently, all claiming is manual, but the admin module enables you to build claim policies and specify the action(s) that users should take to claim items. - -Create a claim policy -^^^^^^^^^^^^^^^^^^^^^ - -The claim policy link enables you to name the claim policy and specify the organization that owns it. - -. To create a claim policy, click _Admin -> Server Administration -> Acquisitions -> Claim Policies_. -. Create a claim policy name. No limits exist on the number of characters that can be entered in this field. -. Select an org unit from the drop down menu. The org unit indicates the organizational units whose staff can use this claim policy. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units). -+ -[NOTE] -The rule of parental inheritance applies to this list. -+ -. Enter a description. No limits exist on the number of characters that can be entered in this field. -. Click _Save_. - -Create a claim type -^^^^^^^^^^^^^^^^^^^ - -The claim type link enables you to specify the reason for a type of claim. - -. To create a claim type, click _Admin -> Server Administration -> Acquisitions -> Claim types_. -. Create a claim type. No limits exist on the number of characters that can be entered in this field. -. Select an org unit from the drop down menu. The org unit indicates the organizational units whose staff can use this claim type. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units). -+ -[NOTE] -The rule of parental inheritance applies to this list. -+ -. Enter a description. No limits exist on the number of characters that can be entered in this field. -. Click _Save_. - -Create a claim event type -^^^^^^^^^^^^^^^^^^^^^^^^^ - -The claim event type describes the physical action that should occur when an item needs to be claimed. For example, the user should notify the vendor via email that the library is claiming an item. - -. To access the claim event types, click _Admin -> Server Administration -> Acquisitions ->Claim event type_. -. Enter a code for the claim event type. No limits exist on the number of characters that can be entered in this field. -. Select an org unit from the drop down menu. The org unit indicates the organizational units whose staff can use this event type. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units). -+ -[NOTE] -The rule of parental inheritance applies to this list. -+ -. Enter a description. No limits exist on the number of characters that can be entered in this field. -. If this claim is initiated by the user, then check the box adjacent to Library Initiated. -+ -[NOTE] -Currently, all claims are initiated by a user. The ILS cannot automatically claim an issue. -+ -. Click _Save_. - -Create a claim policy action -^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -The claim policy action enables you to specify how long a user should wait before claiming the item. - -. To access claim policy actions, click _Admin -> Server Administration -> Acquisitions ->Claim Policy Actions_. - -. Select an Action (Event Type) from the drop down menu. - -. Enter an action interval. This field indicates how long a user should wait before claiming the item. - -. In the Claim Policy ID field, select a claim policy from the drop down menu. - -. Click _Save_. - -[NOTE] -You can create claim cycles by adding multiple claim policy actions to a claim policy. - -Currency Types -~~~~~~~~~~~~~~ - -Currency types can be created and applied to funds in the administrative module. When a fund is applied to a copy or line item for purchase, the item will be purchased in the currency associated with that fund. - -Create a currency type -^^^^^^^^^^^^^^^^^^^^^^ - -. To create a new currency type, click _Admin -> Server Administration -> Acquisitions -> Currency types_. - -. Enter the currency code. No limits exist on the number of characters that can be entered in this field. - -. Enter the name of the currency type in Currency Label field. No limits exist on the number of characters that can be entered in this field. - -. Click Save. - -Edit a currency type -^^^^^^^^^^^^^^^^^^^^ - -. To edit a currency type, click your cursor in the row that you want to edit. The row will turn blue. - -. Double~click. The pop~up box will appear, and you can edit the fields. - -. After making changes, click Save. - -[NOTE] -From the currency types interface, you can delete currencies that have never been applied to funds or used to make purchases. - -Distribution Formulas -~~~~~~~~~~~~~~~~~~~~~ - -Distribution formulas allow you to specify the number of copies that should be distributed to specific branches. You can create and reuse formulas as needed. - -Create a distribution formula -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -. Click _Admin -> Server Administration -> Acquisitions ->Distribution Formulas_. -. Click _New Formula_. -. Enter a Formula Name. No limits exist on the number of characters that can be entered in this field. -. Choose a Formula Owner from the drop down menu. The Formula Owner indicates the organizational units whose staff can use this formula. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units). -+ -[NOTE] -The rule of parental inheritance applies to this list. -+ -. Ignore the Skip Count field which is currently not used. -. Click _Save_. -. Click _New Entry_. -. Select an Owning Library from the drop down menu. This indicates the branch that will receive the items. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See _Admin -> Server Administration -> Organizational Units_). -. Select a Shelving Location from the drop down menu. -. In the Item Count field, enter the number of items that should be distributed to the branch. You can enter the number or use the arrows on the right side of the field. -. Click _Apply Changes_. The screen will reload. -. To view the changes to your formula, click Admin -> Server Administration -> Acquisitions -> Distribution Formulas. The item_count will reflect the entries to your distribution formula. - -[NOTE] -To edit the Formula Name, click the hyperlinked name of the formula in the top left corner. A pop up box will enable you to enter a new formula name. - -Edit a distribution formula -^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -To edit a distribution formula, click the hyperlinked title of the formula. - -EDI -~~~ -Many libraries use Electronic Data Interchange (EDI) accounts to order new acquisitions. Users can set up EDI accounts and manage EDI messages in the admin module. EDI messages and notes can be viewed in the acquisitions module. See also the link:../installation/edi_setup.txt[EDI Installation Instructions] because this is required for use of EDI. - -The following fields are required to create an EDI account: - -[NOTE] -host, username, password, path, and incoming directory. - -EDI Accounts -^^^^^^^^^^^^ - -Create EDI Accounts to communicate electronically with providers. - -. Create a label. The label allows you to differentiate between accounts for the same provider. No limits exist on the number of characters that can be entered in this field. -. Enter a host. Your provider will provide you with the requisite FTP or SCP information. -. Enter the username that has been supplied by your provider. -. Enter the password that has been supplied by your provider. -. Enter account information. This field enables you to add a supplemental password for entry to a remote system after log in has been completed. This field is optional for the ILS but may be required by your provider. -. Select an owner from the drop down menu. The owner indicates the organizational units whose staff can use this EDI account. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units). -+ -[NOTE] -The rule of parental inheritance applies to this list. -+ -. The Last Activity updates automatically with any inbound or outbound communication. -. Select a provider from the drop down menu to whom this account belongs. -. Enter a path. The path indicates the remote location on the server from which files are pulled in to the ILS. -. Enter the incoming directory. This directory indicates the location on your local network to which the files download. -. Enter the vendor account number supplied by your provider. -. Enter the vendor account code supplied by your provider. -. Click Save. - -EDI Messages -^^^^^^^^^^^^ - -The EDI messages screen displays all incoming and outgoing messages between the library and the vendor. - -Exchange Rates -~~~~~~~~~~~~~~ - -Exchange rates define the rate of exchange between currencies. Evergreen will automatically calculate exchange rates for purchases. Evergreen assumes that the currency of the purchasing fund is identical to the currency of the provider, but it provides for two unique situations: 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 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 accordingly. When money is transferred between funds that use different currency types, Evergreen will automatically use the exchange rate to convert the money to the currency of the receiving fund. During such transfers, however, staff can override the automatic conversion by providing an explicit amount to credit to the receiving fund. - -Create an exchange rate -^^^^^^^^^^^^^^^^^^^^^^^ - -. To create a new exchange rate, click _Admin -> Server Administration -> Acquisitions -> Exchange Rates_. - -. Click New Exchange Rate. - -. Enter the From Currency from the drop down menu populated by the currency types. - -. Enter the To Currency from the drop down menu populated by the currency types. - -. Enter the exchange Ratio. - -. Click _Save_. - -Edit an Exchange Rate -^^^^^^^^^^^^^^^^^^^^^ - -Edit an exchange rate just as you would edit a currency type. - -MARC Federated Search -~~~~~~~~~~~~~~~~~~~~~ - -The MARC Federated Search enables you to import bibliographic records into a selection list or purchase order from a Z39.50 source. - -. Click _Acquisitions -> MARC Federated Search_. -. Check the boxes of Z39.50 services that you want to search. Your local Evergreen Catalog is checked by default. Click Submit. -+ -image::media/acq_marc_search.png[search form] -+ -. A list of results will appear. Click the _Copies_ link to add copy information to the line item. See the link:line_items.txt[section on Line Items] for more information. -. Click the Notes link to add notes or line item alerts to the line item. See the link:line_items.txt[section on Line Items] for more information. -. Enter a price in the _Estimated Price_ field. -. You can save the line item(s) to a selection list by checking the box on the line item and clicking _Actions -> Save Items to Selection List_. You can also create a purchase order from the line item(s) by checking the box on the line item and clicking _Actions -> Create Purchase Order_. - -image::media/acq_marc_search-2.png[line item] - -Fund Tags -~~~~~~~~~ - -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 Children's CDs. Assign a fund tag of 'children's' to each fund. When you need to report on the amount that has been spent on all children's materials, you can run a report on the fund tag to find total expenditures on children's materials rather than reporting on each individual fund. - -Create a Fund Tag - -. To create a fund tag, click _Admin -> Server Administration -> Acquisitions -> Fund Tags_. -. Click _New Fund Tag_. No limits exist on the number of characters that can be entered in this field. -. Select a Fund Tag Owner from the drop down menu. The owner indicates the organizational unit(s) whose staff can use this fund tag. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units). -+ -[NOTE] -The rule of parental inheritance applies to this list. -+ -. Enter a Fund Tag Name. No limits exist on the number of characters that can be entered in this field. -. Click _Save_. - -Funding Sources -~~~~~~~~~~~~~~~ - -Funding sources allow you to specify the sources that contribute monies to your fund(s). You can create as few or as many funding sources as you need. These can be used to track exact ammounts for accounts in your general ledger. You can then use funds to track spending and purchases for specific collections. - -Create a funding source -^^^^^^^^^^^^^^^^^^^^^^^ - -. To create a new funding source, click _Admin -> Server Administration -> Acquisitions -> Funding Source_. -. Enter a funding source name. No limits exist on the number of characters that can be entered in this field. -. Select an owner from the drop down menu. The owner indicates the organizational unit(s) whose staff can use this funding source. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units). -+ -[NOTE] -The rule of parental inheritance applies to this list. For example, if a system is made the owner of a funding source, then users with appropriate permissions at the branches within the system could also use the funding source. -+ -. Create a code for the source. No limits exist on the number of characters that can be entered in this field. -. Select a currency from the drop down menu. This menu is populated from the choices in the Currency Types interface. -. Click _Save_. - -Allocate Credits to Funding Sources -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -. Apply a credit to this funding source. - -. Enter the amount of money that the funding source contributes to the organization. Funding sources are not tied to fiscal or calendar years, so you can continue to add money to the same funding source over multiple years, e.g. County Funding. Alternatively, you can name funding sources by year, e.g. County Funding 2010 and County Funding 2011, and apply credits each year to the matching source. - -. To apply a credit, click on the hyperlinked name of the funding source. The Funding Source Details will appear. - -. Click _Apply Credit_. - -. Enter an amount to apply to this funding source. - -. Enter a note. This field is optional. - -. Click _Apply_. - -Allocate credits to funds -^^^^^^^^^^^^^^^^^^^^^^^^^ - -If you have already set up your funds, then you can then click the Allocate to Fund button to apply credits from the 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 credits to funds from the funds interface. See section 1.2 for more information. - -. To allocate credits to funds, click _Allocate to Fund_. - -. Enter the amount that you want to allocate. - -. Enter a note. This field is optional. - -. Click _Apply_. - -Track Debits and Credits -^^^^^^^^^^^^^^^^^^^^^^^^ - -You can track credits to and allocations from each funding source. These amounts are updated when credits and allocations are made in the Funding Source Details. Access the Funding Source Details by clicking on the hyperlinked name of the Funding Source. - -Funds -~~~~~ - -Funds allow you to allocate credits toward specific purchases. In the funds interface, you can create funds; allocate credits from funding sources to funds; transfer money between funds; and apply fund tags to funds. Funds are created for a specific year, either fiscal or calendar. These funds are owned by org units. At the top of the funds interface, you can set a contextual org unit and year. The drop down menu at the top of the screen enables you to focus on funds that are owned by specific organizational units during specific years. - -Create a fund -^^^^^^^^^^^^^ - -. To create a new fund, click _Admin -> Server Administration -> Acquisitions -> Funds_. -. Enter a name for the fund. No limits exist on the number of characters that can be entered in this field. -. Create a code for the fund. No limits exist on the number of characters that can be entered in this field. -. Enter a year for the fund. This can be a fiscal year or a calendar year. The format of the year is YYYY. -. 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 shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units). -+ -[NOTE] -The rule of parental inheritance applies to this list. See section -+ -. Select a currency type from the drop down menu. This menu is comprised of entries in the currency types menu. When a fund is applied to a line item or copy, the price of the item will be encumbered in the currency associated with the fund. -. Click the Active box to activate this fund. You cannot make purchases from this fund if it is not active. -. 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 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, it will appear in red when you apply funds to copies. -. 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 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 appear in yellow when you apply funds to copies. -. Check the Propagate box to propagate funds. When you propagate a fund, the ILS will create a new fund for the following fisca year with the same parameters as your current fund. All of the settings transfer except for the year and the amount of money in the fund. Propagation occurs during the fiscal year close~out operation. -. Check the Rollover box if you want to roll over remaining funds into the same fund next year. -. Click _Save_. - -Allocate Credits from Funding Sources to Funds -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -Credits can be applied to funds from funding sources using the fund interface. The credits that you apply to the fund can be applied later to purchases. - -. To access funds, click _Admin -> Server Administration -> Acquisitions -> Funds_. - -. Click the hyperlinked name of the fund. - -. To add a credit to the fund, click the Create Allocation tab. - -. Choose a Funding Source from the drop down menu. - -. Enter an amount that you want to apply to the fund from the funding source. - -. Enter a note. This field is optional. - -. Click _Apply_. - -Transfer credits between funds -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -The credits that you allocate to funds can be transferred between funds if desired. In the following example, you can transfer $500.00 from the Young Adult Fiction fund to the Children's DVD fund. - -. To access funds, click _Admin -> Server Administration -> Acquisitions -> Funds_. - -. Click the hyperlinked name of the originating fund. - -. The Fund Details screen appears. Click Transfer Money. - -. Enter the amount that you would like to transfer. - -. From the drop down menu, select the destination fund. - -. Add a note. This field is optional. - -. Click _Transfer_. - -Track Balances and Expenditures -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -The Fund Details allows you to track the fund's balance, encumbrances, and amount spent. It also allows you to track allocations from the funding source(s), debits, and fund tags. - -. To access the fund details, click on the hyperlinked name of the fund that you created. - -. The Summary allows you to track the following: - -. Balance - The balance is calculated by subtracting both items that have been invoiced and encumbrances from the total allocated to the fund. -. Total Allocated - This amount is the total amount allocated from the Funding Source. -. Spent Balance - This balance is calculated by subtracting only the items that have been invoiced from the total allocated to the fund. It does not include encumbrances. -. Total Debits - The total debits are calculated by adding the cost of items that have been invoiced and encumbrances. -. Total Spent - The total spent is calculated by adding the cost of items that have been invoiced. It does not include encumbrances. -. Total Encumbered - The total encumbered is calculated by adding all encumbrances. - -Edit a Fund -^^^^^^^^^^^ - -Edit a fund just as you would edit a currency type. - -Perform Year End Closeout Operation -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -The Year End Closeout Operation allows you to deactivate funds for the current year and create analogous funds for the next year. It transfers encumbrances to the analogous funds, and it rolls over any remaining funds if you checked the rollover box when creating the fund. - -. To access the year end closeout of a fund, click Admin -> Server Administration -> Acquisitions -> Funds. - -. Click _Fund Propagation and Rollover_. - -. Check the box adjacent to _Perform Fiscal Year Close~Out Operation_. - -. Notice that the context org unit reflects the context org unit that you selected at the top of the Funds screen. - -. If you want to perform the close~out operation on the context org unit and its child units, then check the box adjacent to Include Funds for Descendant Org Units. - -. Check the box adjacent to dry run if you want to test changes to the funds before they are enacted. Evergreen will generate a summary of the changes that would occur during the selected operations. No data will be changed. - -. Click _Process_. - -. Evergreen will begin the propagation process. Evergreen will make a clone of each fund, but it will increment the year by . - -Invoice menus -~~~~~~~~~~~~~ - -Invoice menus allow you to create drop down menus that appear on invoices. You can create an invoice item type or invoice payment method. - -Invoice item type -^^^^^^^^^^^^^^^^^ - -The invoice item type allows you to enter the types of additional charges that you can add to an invoice. Examples of additional charge types might include taxes or processing fees. Charges for bibliographic items are listed separately from these additional charges. A default list of charge types displays, but you can add custom charge types to this list. Invoice item types can also be used when adding non~bibliographic items to a purchase order. When invoiced, the invoice item type will copy from the purchase order to the invoice. - -. To create a new charge type, click _Admin -> Server Administration -> Acquisitions -> Invoice Item Type_. - -. Click _New Invoice Item Type_. - -. Create a code for the charge type. No limits exist on the number of characters that can be entered in this field. - -. Create a label. No limits exist on the number of characters that can be entered in this field. The text in this field appears in the drop down menu on the invoice. - -. If items on the invoice were purchased with the monies in multiple funds, then you can divide the additional charge across funds. Check the box adjacent to Prorate-> if you want to prorate the charge across funds. - -. Click _Save_. - -Invoice payment method -^^^^^^^^^^^^^^^^^^^^^^ - -The invoice payment method allows you to predefine the type(s) of invoices and payment method(s) that you accept. The text that you enter in the admin module will appear as a drop down menu in the invoice type and payment method fields on the invoice. - -. To create a new invoice payment method, click _Admin -> Server Administration -> Acquisitions -> Invoice Payment Method_. - -. Click _New Invoice Payment Method_. - -. Create a code for the invoice payment method. No limits exist on the number of characters that can be entered in this field. - -. Create a name for the invoice payment method. No limits exist on the number of characters that can be entered in this field. The text in this field appears in the drop down menu on the invoice. - -. Click _Save_. - -Payment methods can be deleted from this screen. - -Line item features -~~~~~~~~~~~~~~~~~~ - -Line item alerts are predefined text that can be added to line items that are on selection lists or purchase orders. You can define the alerts from which staff can choose. Line item alerts appear in a pop up box when the line item, or any of its copies, are marked as received. - -Create a line item alert -^^^^^^^^^^^^^^^^^^^^^^^^ - -. To create a line item alert, click _Administration -> Server Administration -> Acquisitions -> Line Item Alerts_. - -. Click _New Line Item Alert Text_. - -. Create a code for the text. No limits exist on the number of characters that can be entered in this field. - -. Create a description for the text. No limits exist on the number of characters that can be entered in this field. - -. Select an owning library from the drop down menu. The owning library indicates the organizational units whose staff can use this alert. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units). - -. Click _Save_. - -Line Item MARC Attribute Definitions -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -Line item attributes define the fields that Evergreen needs to extract from the bibliographic records that are in the acquisitions database to display in the catalog. Also, these attributes will appear as fields in the New Brief Record interface. You will be able to enter information for the brief record in the fields where attributes have been defined. - diff --git a/admin/authorities.txt b/admin/authorities.txt deleted file mode 100644 index 722e411c69..0000000000 --- a/admin/authorities.txt +++ /dev/null @@ -1,170 +0,0 @@ -Authorities ------------ - -Authority Control Sets -~~~~~~~~~~~~~~~~~~~~~~ - - -The tags and subfields that display in authority records in Evergreen are -proscribed by control sets. The Library of Congress control set is the default -control set in Evergreen. In Evergreen release 2.2, you can create customized -control sets for authority records. Also, you can define thesauri and authority -fields for these control sets. - -Patrons and staff will be able to browse authorities in the OPAC. The following -fields are browsable by default: author, series, subject, title, and topic. You -will be able to add custom browse axes in addition to these default fields. - -Control Sets -^^^^^^^^^^^^ - -You can specify the MARC tags and subfields that an authority record should -contain. The Library of Congress control set exists in the staff client by -default. The control sets feature enables librarians to add or customize new -control sets. - -To access existing control sets, click *Admin* -> *Server Administration* -> -*Authorities* -> *Control Sets*. - -To add a *control set*: - -. Click *Admin* -> *Server Administration* -> *Authorities* -> *Control Sets*. -. Click *New Control Set*. . Add a *Name* to the control set. Enter any number -of characters. . Add a *Description* of the control set. Enter any number of -characters. . Click *Save*. - -image::media/Authority_Control_Sets1.jpg[Authority_Control_Sets1] - -Thesauri -~~~~~~~~ - -A thesaurus describes the semantic rules that govern the meaning of words in a -MARC record. The thesaurus code, which indicates the specific thesarus that -should control a MARC record, is encoded in a fixed field using the mnemonic -Subj in the authority record. Eleven thesauri associated with the Library of -Congress control set exist by default in the staff client. - -To access an existing thesaurus, click *Admin* -> *Server Administration* -> -*Authorities* -> *Control Sets*, and choose the hyperlinked thesaurus that you -want to access, or click *Admin* -> *Server Administration* -> *Authorities* -> -*Thesauri*. - - -To add a *Thesaurus*: - -. Click *Admin* -> *Server Administration* -> *Authorities* -> *Control Sets*, -and choose the hyperlinked thesaurus that you want to access, or click *Admin* --> *Server Administration* -> *Authorities* -> *Thesauri*. . Click *New -Thesaurus*. . Add a *Thesaurus Code*. Enter any single, upper case character. -This character will be entered in the fixed fields of the MARC record. . Add a -*Name* to the thesaurus. Enter any number of characters. . Add a *Description* -of the thesaurus. Enter any number of characters. - -image::media/Authority_Control_Sets2.jpg[Authority_Control_Sets2] - -Authority Fields -~~~~~~~~~~~~~~~~ - - -Authority fields indicate the tags and subfields that should be entered in the -authority record. Authority fields also enable you to specify the type of data -that should be entered in a tag. For example, in an authority record governed -by a Library of Congress control set, the 100 tag would contain a "Heading - -Personal Name." Authority fields also enable you to create the corresponding -tag in the bibliographic record that would contain the same data. - -To create an *Authority Field*: -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -. Click *Admin* -> *Server Administration* -> *Authorities* -> *Control Sets*. -. Click *Authority Fields*. The number in parentheses indicates the number of -authority fields that have been created for the control set. -. Click *New Authority Field*. -. Add a *Name* to the authority field. Enter any number of characters. -. Add a *Description* to describe the type of data that should be entered in -this tag. Enter any number of characters. -. Select a *Main Entry* if you are linking the tag(s) to another entry. -. Add a tag in the authority record. -. Add a subfield in the authority record. Multiple subfields should be entered -without commas or spaces. -. Click *Save*. -+ -image::media/Authority_Control_Sets3.jpg[Authority_Control_Sets3] -+ -.Create the corresponding tag in the bibliographic record that should contain -this information. Click the *None* link in the *Controlled Bib Fields* column. -. Click *New Control Set Bib Field*. -. Add the corresponding tag in the bibiographic record. -. Click *Save*. - -image::media/Authority_Control_Sets4.jpg[Authority_Control_Sets4] - - - -Browse Axes -~~~~~~~~~~~ - -Authority records can be browsed, by default, along five axes: author, series, -subject, title, and topic. Use the *Browse Axes* feature to create additional -axes. - - -Create a new *Browse Axis*: - -. Click *Admin* -> *Server Administration* -> *Authorities* -> *Browse Axes* -. Click *New Browse Axis*. -. Add a *code*. Do not enter any spaces. -. Add a *name* to the axis that will appear in the OPAC. Enter any number of -characters. -. Add a *description* of the axis. Enter any number of characters. -. Add a *sorter attribute*. The sorter attribute indicates the order in which -the results will be displayed. -+ -image::media/Authority_Control_Sets5.jpg[Authority_Control_Sets5] -. Assign the axis to an authority so that users can find the authority record -when browsing authorities. Click *Admin* -> *Server Administration* -> -*Authorities* -> *Control Sets*. -. Choose the control set to which you will add the axis. Click *Authority -Fields* -. Click the link in the *Axes* column of the tag of your choice. -. Click *New Browse Axis-Authority Field Map*. -. Select an *Axis* from the drop down menu. -. Click *Save*. - -image::media/Authority_Control_Sets6.jpg[Authority_Control_Sets6] - - -OPAC Searching of Authorities -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -Patrons and librarians can browse authorities through the OPAC. - - -To search for *Authorities*: - -. Click *Advanced Search* in the OPAC. -. Find the *Authority Browse* column in the left side of the screen. -. Select a browse axis, and enter a keyword. The terms in the middle of the -results list should yield the best match. -+ -image::media/Authority_Control_Sets7.jpg[Authority_Control_Sets7] -. Click *Submit*. -. A list of results will appear. The authorities with bibliographic records -attached will be listed in bold with the number of attached bibliographic -records in parentheses. -+ -image::media/Authority_Control_Sets8.jpg[Authority_Control_Sets8] -+ -. Click on the bolded text to view bibliographic records. - -image::media/Authority_Control_Sets9.jpg[Authority_Control_Sets9] - - -*Permissions to use this Feature* - - -To use authority control sets, you will need the following permissions: - -* CREATE_AUTHORITY_CONTROL_SET UPDATE_AUTHORITY_CONTROL_SET -* DELETE_AUTHORITY_CONTROL_SET - diff --git a/admin/auto_suggest_search.txt b/admin/auto_suggest_search.txt deleted file mode 100644 index fc01215650..0000000000 --- a/admin/auto_suggest_search.txt +++ /dev/null @@ -1,32 +0,0 @@ -Auto Suggest in Catalog Search ------------------------------- - -The auto suggest feature suggestions for completing search terms as the user enters his search query. Ten suggestions are the default, but the number of suggestions is configurable at -the database level. Scroll through suggestions with your mouse, or use the arrow keys to scroll through the suggestions. Select a suggestion to view records that are linked to -this suggestion. This feature is not turned on by default. You must turn it on in the Admin module. - - -Enabling this Feature -~~~~~~~~~~~~~~~~~~~~~ - -. To enable this feature, click *Admin* -> *Server Administration* -> *Global Flags*. -. Scroll down to item 10, OPAC. -. Double click anywhere in the row to edit the fields. -. Check the box adjacent to *Enabled* to turn on the feature. -. The *Value* field is optional. If you checked *Enabled* in step 4, and you leave this field empty, then Evergreen will only suggest searches for which there are any corresponding MARC records. -+ -note: If you checked *Enabled* in step 4, and you enter the string, *opac_visible*, into this field, then Evergreen will suggest searches for which -there are matching MARC records with copies within your search scope. For example, it will suggest MARC records with copies at your branch. -+ -. Click *Save.* - -image::media/Auto_Suggest_in_Catalog_Search2.jpg[Auto_Suggest_in_Catalog_Search2] - -Using this Feature -~~~~~~~~~~~~~~~~~~ - -. Enter search terms into the basic search field. Evergreen will automatically suggest search terms. -. Select a suggestion to view records that are linked to this suggestion. - -image::media/Auto_Suggest_in_Catalog_Search1.jpg[Auto_Suggest_in_Catalog_Search1] - diff --git a/admin/booking-admin.txt b/admin/booking-admin.txt deleted file mode 100644 index 5fc51e50b2..0000000000 --- a/admin/booking-admin.txt +++ /dev/null @@ -1,199 +0,0 @@ -Booking Module Administration ------------------------------ - -Creating Bookable Non-Bibliographic Resources -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -Staff with the required permissions (Circulator and above) can create bookable non-bibliographic resources such as laptops, projectors, and meeting rooms. - -The following pieces make up a non-bibliographic resource: - -* Resource Type -* Resource Attribute -* Resource Attribute Values -* Resource -* Resource Attribute Map - -You need to create resource types and resource attributes (features of the resource types), and add booking items (resources) to individual resource type. Each resource attribute may have multiple values. You need to link the applicable features (resource attributes and values) to individual item (resource) through the Resource Attribute Map. Before you create resources (booking items) you need to have a resource type and associated resource attributes and values, if any, for them. - -Create New Resource Type -^^^^^^^^^^^^^^^^^^^^^^^^ - -1) Select Admin --> Server Administration --> Booking --> Resource Types. - -image::media/booking-create-resourcetype-1.png[] - -2) A list of current resource types will appear. Use Back and Next buttons to browse the whole list. - -image::media/booking-create-resourcetype-2.png[] - -[NOTE] -You may also see cataloged items in the list. Those items have been marked bookable or booked before. - - -3) To create a new resource type, click New Resource Type in the top right corner, . - -image::media/booking-create-resourcetype-3.png[] - -4) A box will appear in which you create your new type of resource. - -image::media/booking-create-bookable-1.png[] - -* Resource Type Name - Give your resource a name. -* Fine Interval - How often will fines be charged? This period can be input in several ways: - -[NOTE] -==================================================================== -** second(s), minute(s), hour(s), day(s), week(s), month(s), year(s) -** sec(s), min(s) -** s, m, h -** 00:00:30, 00:01:00, 01:00:00 -=================================================================== - -* Fine Amount - The amount that will be charged at each Fine Interval. -* Owning Library - The home library of the resource. -* Catalog Item - (Function not currently available.) -* Transferable - This allows the item to be transferred between libraries. -* Inter-booking and Inter-circulation Interval - The amount of time required by your library between the return of a resource and a new reservation for the resource. This interval uses * the same input conventions as the Fine Interval. -* Max Fine Amount - The amount at which fines will stop generating. - -5) Click Save when you have entered the needed information. - -image::media/booking-create-resourcetype-4.png[] - -6) The new resource type will appear in the list. - -image::media/booking-create-resourcetype-5.png[] - -Create New Resource Attribute -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -1) Select Server Administration --> Booking --> Resource Attributes. - -2) Click New Resource Attribute in the top right corner. - -3) A box will appear in which you can add the attributes of the resource. Attributes are categories of descriptive information that are provided to the staff member when the booking request is made. For example, an attribute of a projector may be the type of projector. Other attributes might be the number of seats available in a room, or the computing platform of a laptop. - -image::media/booking-create-bookable-2.png[] - -* Resource Attribute Name - Give your attribute a name. -* Owning Library - The home library of the resource. -* Resource Type - Type in the first letter to list then choose the Resource Type to which the Attribute is applicable. -* Is Required - (Function not currently available.) - -4) Click Save when the necessary information has been entered. - -5) The added attribute will appear in the list. - -[NOTE] -One resource type may have multiple attributes. You may repeat the above procedure to add more. - -Create New Resource Attribute Value -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -1) One resource attribute may have multiple values. To add new attribute value, select Server Administration → Booking → Resource Attribute Values. - -2) Click New Resource Attribute Value in the top right corner. - -3) A box will appear in which you assign a value to a particular attribute. Values can be numbers, words, or a combination of them, that describe the particular aspects of the resource that have been defined as Attributes. As all values appear on the same list for selection, values should be as unique as possible. For example, a laptop may have a computing platform that is either PC or Mac. - -image::media/booking-create-bookable-3.png[] - -* Owning Library - The home library of the resource. -* Resource Attribute - The attribute you wish to assign the value to. -* Valid Value - Enter the value for your attribute. - -4) Click Save when the required information has been added. - -5) The attribute value will appear in the list. Each attribute should have at least two values attached to it; repeat this process for all applicable attribute values. - -Create New Resource -^^^^^^^^^^^^^^^^^^^ - -1) Add items to a resource type. Click Admin → Server Administration → Booking → Resources. - -2) Click New Resource in the top right corner. - -3) A box will appear. Add information for the resource. - -image::media/booking-create-bookable-4.png[] - -* Owning Library - The home library of the resource. -* Resource Type - Type in the first letter of the resource type's name to list then select the resource type for your item. -* Barcode - Barcode for the resource. -* Overbook - This allows a single item to be reserved, picked up, and returned by multiple patrons during overlapping or identical time periods. -* Is Deposit Required - (Function not currently available.) -* Deposit Amount - (Function not currently available.) -* User Fee - (Function not currently available.) - -4) Click Save when the required information has been added. - -5) The resource will appear in the list. - -[NOTE] -One resource type may have multiple resources attached. - -Map Resource Attributes and Values to Resources -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -1) Use Resource Attribute Maps to bring together the resources and their attributes and values. Select Admin → Server Administration → Booking → Resource Attribute Maps. - -2) Click New Resource Attribute Map in the right top corner. - -3) A box will appear in which you will map your attributes and values to your resources. - -image::media/booking-create-bookable-5.png[] - -* Resource - Enter the barcode of your resource. -* Resource Attribute - Select an attribute that belongs to the Resource Type. -* Attribute Value - Select a value that belongs to your chosen attribute and describes your resource. If your attribute and value do not belong together you will be unable to save. - -4) Click Save once you have entered the required information. - -[NOTE] -A resource may have multiple attributes and values. Repeat the above steps to map all. - -5) The resource attribute map will appear in the list. - -Once all attributes have been mapped your resource will be part of a hierarchy similar to the example below. - -image::media/booking-create-bookable-6.png[] - - -Editing Non-Bibliographic Resources -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -Staff with the required permissions can edit aspects of existing non-bibliographic resources. For example, resource type can be edited in the event that the fine amount for a laptop changes from $2.00 to $5.00. - -Editing Resource Types -^^^^^^^^^^^^^^^^^^^^^^ - -1) Bring up your list of resource types. Select Admin --> Server Administration --> Booking --> Resource Types. - -2) A list of current resource types will appear. - -3) Double click anywhere on the line of the resource type you would like to edit. - -4) The resource type box will appear. Make your changes and click Save. - -5) Following the same procedure you may edit Resource Attributes, Attributes Values, Resources and Attribute Map by selecting them on Admin --> Server Administration --> Booking menu. - - - - -Deleting Non-bibliographic Resources -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -1) To delete a booking resource, go to Admin → Server Administration → Booking → Resources. - -2) Select the checkbox in front the resource you want to delete. Click Delete Selected. The resource will disappear from the list. - -Following the same procedure you may delete Resource Attributes Maps. - -You may also delete Resource Attribute Values, Resource Attributes and Resource Types. But you have to delete them in the reverse order when you create them to make sure the entry is not in use when you try to delete it. - -This is the deletion order: Resource Attribut Map/Resources --> Resource Attribute Values --> Resource Attributes --> Resource Types. - - - - diff --git a/admin/cn_prefixes_and_suffixes.txt b/admin/cn_prefixes_and_suffixes.txt deleted file mode 100644 index 03b11c638f..0000000000 --- a/admin/cn_prefixes_and_suffixes.txt +++ /dev/null @@ -1,46 +0,0 @@ -Call Number Prefixes and Suffixes ---------------------------------- - -You can configure call number prefixes and suffixes in the Admin module. This feature ensures more precise cataloging because each cataloger will have access to an identical drop down menu of call number prefixes and suffixes that are used at his library. In addition, it may streamline cataloging workflow. Catalogers can use a drop down menu to enter call number prefixes and suffixes rather than entering them manually. You can also run reports on call number prefixes and suffixes that would facilitate collection development and maintenance. - - -Configure call number prefixes -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -Call number prefixes are codes that precede a call number. - -To configure call number prefixes: - -1. Select *Admin -> Server Administration -> Call Number Prefixes*. -2. Click *New Prefix*. -3. Enter the *call number label* that will appear on the item. -4. Select the *owning library* from the drop down menu. Staff at this library, and its descendant org units, with the appropriate permissions, will be able to apply this call number prefix. -5. Click *Save*. - - - -image::media/Call_Number_Prefixes_and_Suffixes_2_21.jpg[Call_Number_Prefixes_and_Suffixes_2_21] - - - -Configure call number suffixes -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -Call number suffixes are codes that succeed a call number. - -To configure call number suffixes: - -1. Select *Admin -> Server Administration -> Call Number Suffixes*. -2. Click *New Suffix*. -3. Enter the *call number label* that will appear on the item. -4. Select the *owning library* from the drop down menu. Staff at this library, and its descendant org units, with the appropriate permissions, will be able to apply this call number suffix. -5. Click *Save*. - - -image::media/Call_Number_Prefixes_and_Suffixes_2_22.jpg[Call_Number_Prefixes_and_Suffixes_2_22] - - -Apply Call Number Prefixes and Suffixes -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -You can apply call number prefixes and suffixes to items from a pre-configured list in the *Unified Volume/Copy Creator*. See the document, Unified Volume/Copy Creator, for an example. diff --git a/admin/customize_staff_client.txt b/admin/customize_staff_client.txt deleted file mode 100644 index c70ff58aed..0000000000 --- a/admin/customize_staff_client.txt +++ /dev/null @@ -1,59 +0,0 @@ -Customizing the Staff Client ----------------------------- - -Customizable Toolbar -~~~~~~~~~~~~~~~~~~~~ - - -By default, two toolbars are available in the staff client: circulation and -cataloging. This feature enables you to customize toolbars in the staff client. -You can create toolbars for specific org unit(s), workstation(s), or login(s). - - -Configure Toolbar -^^^^^^^^^^^^^^^^^ - -. Click *Admin* -> *Workstation Administration* -> *Toolbars* -> *Configure -Toolbars*. -. Click *New Toolbar*. -. *Enter label for toolbar*. -+ -image::media/Customizable_Toolbar1.jpg[Customizable_Toolbar1] -+ -. Click *Ok*. -.Select one of the buttons in the *Available* panel. The *Button ID* describes -that action that the button will take, and the *Label* will display in the -toolbar. -. Click the *--> A* button to add the selected function to the -*Selected* panel on the bottom right side of the screen. To remove a button, -click the *<--R* button. -+ -image::media/Customizable_Toolbar2.jpg[Customizable_Toolbar2] -+ -. Continue adding buttons if desired. The buttons will display in the order that you add -them. If you want to reorder the buttons, click the *Up* or *Down* buttons. -. To separate buttons onto left and right sides of the screen on the same -toolbar, select *toolbarspacer*, and click *--> A*. -+ -image::media/Customizable_Toolbar3.jpg[Customizable_Toolbar3] -+ -. To add a dividing line between buttons that appear on the same side of the -screen, select *toolbarseparator*, and click *-->A*. -+ -image::media/Customizable_Toolbar4.jpg[Customizable_Toolbar4] -+ -. At the bottom of the screen, choose the owner of this toolbar. -If you click *Owning Org Unit*, then the owning org unit that you specify will display this -toolbar. Select the owning org unit from the drop down menu. The rule of -parental inheritance applies, so all child units will inherit the toolbars of -their parental units. -If you click *Owning Workstation*, then the workstation to which you are logged -in when you created the toolbar will display this toolbar. -If you select *Owning User*, then your login has access to that toolbar. - . When you are finished creating the toolbar, click *Save Toolbar*. Any -toolbar to which you have access displays under *Admin -> Workstation -Administration -> Toolbars -> Current*. - -*Permissions* - -ADMIN_TOOLBAR - Allow a user to create, edit, and delete custom toolbars diff --git a/admin/hold_driven_recalls.txt b/admin/hold_driven_recalls.txt deleted file mode 100644 index c926e2c2e5..0000000000 --- a/admin/hold_driven_recalls.txt +++ /dev/null @@ -1,53 +0,0 @@ -Hold-driven recalls -=================== - -indexterm:[hold-driven recalls] -indexterm:[circulation, recalls, hold-driven] - -_Added in Evergreen 2.1_ - -In academic libraries, it is common for groups like faculty and graduate -students to have extended loan periods (for example, 120 days), while -others have more common loan periods such as 3 weeks. In these environments, -it is desirable to have a hold placed on an item that has been loaned out -for an extended period to trigger a 'recall', which: - - . Truncates the loan period - . Sets the remaining available renewals to 0 - . 'Optionally': Changes the fines associated with overdues for the new due - date - . 'Optionally': Notifies the current patron of the recall, including the - new due date and fine level - -Enabling hold-driven recalls ----------------------------- - -By default, holds do not trigger recalls. To enable hold-driven recalls -of circulating items, library settings must be changed as follows: - - . Click *Admin* -> *Local Administration* -> *Library Settings Editor.* - . Set the *Recalls: Circulation duration that triggers a recall - (recall threshold)* setting. The recall threshold is specified as an - interval (for example, "21 days"); any items with a loan duration of - less that this interval are not considered for a recall. - . Set the *Recalls: Truncated loan period (return interval)* setting. - The return interval is specified as an interval (for example, "7 days"). - The due date on the recalled item is changed to be the greater of either - the recall threshold or the return interval. - . 'Optionally': Set the *Recalls: An array of fine amount, fine interval, - and maximum fine* setting. If set, this applies the specified fine rules - to the current circulation period for the recalled item. - -When a hold is placed and no available copies are found by the hold targeter, -the recall logic checks to see if the recall threshold and return interval -settings are set; if so, then the hold targeter checks the currently -checked-out copies to determine if any of the currently circulating items at -the designated pickup library have a loan duration longer than the recall -threshold. If so, then the eligible item with the due date nearest to the -current date is recalled. - -Editing the item recall notification email template ---------------------------------------------------- -The template for the item recall notification email is contained in the -'Item Recall Email Notice' template, found under *Admin* -> *Local -Administration* -> *Notifications / Action Triggers*. diff --git a/admin/lsa-library_settings_editor.txt b/admin/lsa-library_settings_editor.txt deleted file mode 100644 index 3338812cdd..0000000000 --- a/admin/lsa-library_settings_editor.txt +++ /dev/null @@ -1,38 +0,0 @@ -Library Settings Editor ------------------------ - -Fine Accrual on Closed Dates -~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -By default, fines accrue only on dates that the library is open. This feature enables you to charge patrons fines on dates the library is closed. Fines accrue during scheduled closings as well as during normal weekly closed dates. - -To enable this feature: - -. Click *Admin* -> *Local Administration* -> *Library Settings* -> *Charge fines on overdue circulations when closed* -. Click *Edit*. -. Set the value to *True*. -. Click *Update Setting*. - - -Target Copies for Holds at Closed Libraries -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -By default, when a patron places a hold on a title, the hold targeter will search for copies to fill the hold only at circulating libraries that are open. Copies at closed libraries -are not targeted to fill holds. When turned on, this feature enables Evergreen to target copies that have closed circulating libraries to fill holds. Two new org unit settings control this feature. - -Use the following setting to target copies for holds at closed circulating libraries: - -. Click *Admin* -> *Local Administration* -> *Library Settings Editor* -> *Target copies for a hold even if copy's circ lib is closed* -. Set the value to *True* if you want to target copies for holds at closed circulating libraries. Set the value to *False*, or leave it unset, if you do not want to enable this feature. -. Click *Update Setting*. - -image::media/Target_Pickup_Lib1.jpg[Target_Pickup_Lib1] - -Use the following setting to target copies for holds IF AND ONLY IF the circulating library is the hold's pickup library. - -. Click *Admin* -> *Local Administration* -> *Library Settings Editor* -> *Target copies for a hold even if copy's circ lib is closed IF the circ lib is the hold's pickup lib* -. Set the value to *True* if you want to target copies for holds at closed circulating libraries when the circulating library of the item and the pickup library of the hold are -the same. Set the value to *False*, or leave it unset, if you do not want to enable this feature. -. Click *Update Setting*. - -image::media/Target_Pickup_Lib2.jpg[Target_Pickup_Lib2] diff --git a/admin/lsa-statcat.txt b/admin/lsa-statcat.txt deleted file mode 100644 index f3fef43c5d..0000000000 --- a/admin/lsa-statcat.txt +++ /dev/null @@ -1,79 +0,0 @@ -Statistical Categories Editor ------------------------------ - -This is where you configure your statistical categories (stat cats). Stat cats are a way to save and report on additional information that doesn’t fit elsewhere in Evergreen's default records. It is possible to have stat cats for copies or patrons. - -1. Click *Admin -> Local Administration -> Statistical Categories Editor.* - -2. To create a new stat cat, enter the name of the category and select either _patron_ or _copy_ from the *Type* dropdown menu. Each category type has a number of options you may set. - -*Copy Statistical Categories* - -Copy stat cats appear in the _Copy Editor_, also known as the _Edit Item Attributes_ screen. You might use copy stat cats to track books you have bought from a specific vendor, or donations. - -An example of the _Create a new statistical category_ controls for copies: - -image::media/lsa-statcat-1.png[Create copy stat cat] - -* _OPAC Visibility_: Should the category be displayed in the OPAC? -* _Required_: Must the category be assigned a value when editing the item attributes? -* _Archive with Circs_: Should the category and its values for the copy be archived with aged circulation data? -* _SIP Field_: Select the SIP field identifier that will contain the category and its value -* _SIP Format_: Specify the SIP format string - -Some sample copy stat cats: - -image::media/lsa-statcat-2.png[Sample copy stat cats] - -To add an entry, select _Add_. To edit an entry, select the entry you wish to edit from the drop-down list for the category. - -This is how the copy stat cats appear in the _Copy Editor_: - -image::media/lsa-statcat-3.png[Stat cats in Copy Editor] - -*Patron Statistical Categories* - -Patron stat cats can be used to keep track of information such as the high school a patron attends, or the home library for a consortium patron, e.g. Interlink, or patron preferences. They appear in the fifth section of the _Patron Registration_ or _Edit Patron_ screen. - -An example of the _Create a new statistical category_ controls for patrons: - -image::media/lsa-statcat-4.png[Create patron stat cat] - -* _OPAC Visibility_: Should the category be displayed in the OPAC? -* _Required_: Must the category be assigned a value when registering a new patron or editing an existing one? -* _Archive with Circs_: Should the category and its values for the patron be archived with aged circulation data? -* _Allow Free Text_: May the person registering/editing the patron information supply their own value for the category? -* _Show in Summary_: Display the category and its value in the patron summary view? -* _SIP Field_: Select the SIP field identifier that will contain the category and its value -* _SIP Format_: Specify the SIP format string - -[WARNING] -.WARNING -===================================== -If you make a category *required* and also *disallow free text*, make sure that you populate an entry list for the category so that the user may select a value. Failure to do so will result in an unsubmittable patron registration/edit form! -===================================== - -Some sample patron stat cats: - -image::media/lsa-statcat-5.png[Sample patron stat cats] - -To add an entry, click on _Add_ in the category row under the _Add Entry_ column: - -image::media/lsa-statcat-6.png[Add patron category entry] - -To edit an entry, select the entry you wish to edit from the drop-down list for the category: - -image::media/lsa-statcat-7.png[Edit patron category entry] - -An *organizational unit* (consortium, library system branch library, sub library, etc.) may create their own categories and entries, or supplement categories defined by a higher-level org unit with their own entries. - -An entry can be set as the *default* entry for a category and for an org unit. If an entry is set as the default, it will be automatically selected in the patron edit screen, provided no other value has been previously set for the patron. Only one default may be set per category for any given org unit. - -Lower-level org unit defaults override defaults set for higher-level org units; but in the absence of a default set for a given org unit, the nearest parent org unit default will be selected. - -Default entries for the focus location org unit are marked with an asterisk in the entry dropdowns. - -This is how patron stat cats appear in the patron registration/edit screen: - -image::media/lsa-statcat-8.png[Patron stat cats in registration screen] - diff --git a/admin/recent_staff_searches.txt b/admin/recent_staff_searches.txt deleted file mode 100644 index b297b8d065..0000000000 --- a/admin/recent_staff_searches.txt +++ /dev/null @@ -1,49 +0,0 @@ -Recent Staff Searches ---------------------- - -This feature enables you to view your recent searches as you perform them in the staff client. The number of searches that you can view is configurable. This feature is only available through the staff client; it is not available to patrons in the OPAC. - -*Administrative Settings* - -By default, ten searches will be saved as you search the staff client. If you want to change the number of saved searches, then you can configure the number of searches that you wish to save through the *Library Settings Editor* in the *Admin* module. - -To configure the number of recent staff searches: - -1. Click *Admin -> Local Administration -> Library Settings Editor.* - -2. Scroll to *OPAC: Number of staff client saved searches to display on left side of results and record details pages* - -3. Click *Edit*. - -4. Select a *Context* from the drop down menu. - -5. Enter the number of searches that you wish to save in the *Value* field. - -6. Click *Update Setting* - -image::media/Saved_Catalog_Searches_2_21.jpg[Saved_Catalog_Searches_2_21] - - -NOTE: To retain this setting, the system administrator must restart the web server. - - -If you do not want to save any searches, then you can turn off this feature. - -To deactivate this feature: - -1. Follow steps 1-4 (one through four) as listed in the previous section. - -2. In the *value* field, enter 0 (zero). - -3. Click *Update Setting.* This will prevent you from viewing any saved searches. - - -*Recent Staff Searches* - -Evergreen will save staff searches that are entered through either the basic or advanced search fields. To view recent staff searches: - -1. Enter a search term in either the basic or advanced search fields. - -2. Your search results for the current search will appear in the middle of the screen. The most recent searches will appear on the left side of the screen. - -image::media/Saved_Catalog_Searches_2_22.jpg[Saved_Catalog_Searches_2_22] diff --git a/admin/restrict_Z39.50_sources_by_perm_group.txt b/admin/restrict_Z39.50_sources_by_perm_group.txt deleted file mode 100644 index 2977cc3649..0000000000 --- a/admin/restrict_Z39.50_sources_by_perm_group.txt +++ /dev/null @@ -1,49 +0,0 @@ -Restrict Z39.50 Sources by Permission Group -------------------------------------------- - -In Evergreen versions preceeding 2.2, all users with cataloging privileges could view all of the Z39.50 servers that were available for use in the staff client. In Evergreen version 2.2, you can use a permission to restrict users' access to Z39.50 servers. You can apply a permission to the Z39.50 servers to restrict access to that server, and then assign that permission to users or groups so that they can access the restricted servers. - -Administrative Settings -~~~~~~~~~~~~~~~~~~~~~~~ - -You can add a permission to limit use of Z39.50 servers, or you can use an existing permission. - -NOTE: You must be authorized to add permission types at the database level to add a new permission. - -Add a new permission: - -1) Create a permission at the database level. - -2) Click *Admin -> Server Administration -> Permissions* to add a permission to the staff client. - -3) In the *New Permission* field, enter the text that describes the new permission. - -image::media/Restrict_Z39_50_Sources_by_Permission_Group1.jpg[] - -4) Click *Add*. - -5) The new permission appears in the list of permissions. - - - -Restrict Z39.50 Sources by Permission Group -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -1) Click *Admin -> Server Administration -> Z39.50 Servers* - -2) Click *New Z39.50 Server*, or double click on an existing Z39.50 server to restrict its use. - -3) Select the permission that you added to restrict Z39.50 use from the drop down menu. - -image::media/Restrict_Z39_50_Sources_by_Permission_Group2.jpg[] - -4) Click *Save*. - -5) Add the permission that you created to a user or user group so that they can access the restricted server. - - -image::media/Restrict_Z39_50_Sources_by_Permission_Group3.jpg[] - -6) Users that log in to the staff client and have that permission will be able to see the restricted Z39.50 server. - -NOTE: As an alternative to creating a new permission to restrict use, you can use a preexisting permission. For example, your library uses a permission group called SuperCat, and only members in this group should have access to a restricted Z39.50 source. Identify a permission that is unique to the SuperCat group (e.g. CREATE_MARC) and apply that permission to the restricted Z39.50 server. Because these users are in the only group with the permission, they will be the only group w/ access to the restricted server. diff --git a/admin/staff_client-double_clicking.txt b/admin/staff_client-double_clicking.txt deleted file mode 100644 index f08b00917c..0000000000 --- a/admin/staff_client-double_clicking.txt +++ /dev/null @@ -1,23 +0,0 @@ -New Options for Double Clicking -------------------------------- - -Double Click to Retrieve a Patron's Record -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -. Click *Search -> Search for Patrons* to access a patron's record -. Enter search terms. -. Retrieve a list of possible matches. Double click on the record that you want to open. - -image::media/Double_Click1.jpg[Double_Click1] - - -Double Click to Retrieve Item Attributes -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -. Enter search terms to retrieve a bibliographic record. -. Click *Actions for this Record* -> *Holdings Maintenance*. -. Double click on an item. -+ -image::media/Double_Click3.jpg[Double_Click3] -+ -. The copy information will appear in a new tab. diff --git a/admin/staff_client-recent_searches.txt b/admin/staff_client-recent_searches.txt deleted file mode 100644 index fd1f87bbc4..0000000000 --- a/admin/staff_client-recent_searches.txt +++ /dev/null @@ -1,42 +0,0 @@ -Recent Staff Searches ---------------------- - -This feature enables you to view your recent searches as you perform them in the staff client. The number of searches that you can view is configurable. This feature is only available through the staff client; it is not available to patrons in the OPAC. - -Administrative Settings -~~~~~~~~~~~~~~~~~~~~~~~ - -By default, ten searches will be saved as you search the staff client. If you want to change the number of saved searches, then you can configure the number of searches that you wish to save through the *Library Settings Editor* in the *Admin* module. - -To configure the number of recent staff searches: - -. Click *Admin -> Local Administration -> Library Settings Editor.* -. Scroll to *OPAC: Number of staff client saved searches to display on left side of results and record details pages* -. Click *Edit*. -. Select a *Context* from the drop down menu. -. Enter the number of searches that you wish to save in the *Value* field. -. Click *Update Setting* - -image::media/Saved_Catalog_Searches_2_21.jpg[Saved_Catalog_Searches_2_21] - - -NOTE: To retain this setting, the system administrator must restart the web server. - -If you do not want to save any searches, then you can turn off this feature. - -To deactivate this feature: - -. Follow steps 1-4 (one through four) as listed in the previous section. -. In the *value* field, enter 0 (zero). -. Click *Update Setting.* This will prevent you from viewing any saved searches. - - -Recent Staff Searches -~~~~~~~~~~~~~~~~~~~~~ - -Evergreen will save staff searches that are entered through either the basic or advanced search fields. To view recent staff searches: - -. Enter a search term in either the basic or advanced search fields. -. Your search results for the current search will appear in the middle of the screen. The most recent searches will appear on the left side of the screen. - -image::media/Saved_Catalog_Searches_2_22.jpg[Saved_Catalog_Searches_2_22] diff --git a/admin/staff_client-return_to_results_from_marc.txt b/admin/staff_client-return_to_results_from_marc.txt deleted file mode 100644 index 1e6efc53b3..0000000000 --- a/admin/staff_client-return_to_results_from_marc.txt +++ /dev/null @@ -1,6 +0,0 @@ -Return to Search Results from MARC Record ------------------------------------------ - -This feature enables you to return to your title search results directly from any view of the MARC record, including the OPAC View, MARC Record, MARC Edit, and Holdings Maintenance. You can use this feature to page through records in the MARC Record View or Edit interfaces. You do not have to return to the OPAC View to access title results. - -image::media/Search_Results1.jpg[Search_Results1] diff --git a/admin/staff_client-sorting_columns.txt b/admin/staff_client-sorting_columns.txt deleted file mode 100644 index 1f0e355d3d..0000000000 --- a/admin/staff_client-sorting_columns.txt +++ /dev/null @@ -1,59 +0,0 @@ -Sorting Columns ---------------- - -This feature enables you to sort display columns so that you can find easily the -information that you need on a screen that contains multiple columns. You can -sort display columns on any screen that is built on a grid, such as the Check In -screen or the On Shelf Pull List. - -You can also sort the columns on the following Administration screens: -Circulation Policies, Hold Policies, Circulation Limit Sets, Barcode Completion, -Acquisitions User Request List, and Vandelay Import Errors. - -You can sort items in an ascending or descending order, and you can prioritize -the order in which columns will sort. The following use cases illustrate how to -sort items within the Circulation and Administration interfaces. - -Sorting the On Shelf Pull List -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -You want to capture items that are on the shelf to fill current holds. To -simplify this process, you will sort the items on the On Shelf Pull List by Copy -Location and Call Number. - -. Click *Circulation* -> *Pull List for Hold Requests*. -. The first column that you want to sort is the column, Current Copy Location. Right click the column header, Current Copy Location. -. Click *Sort First (Descending)*. -+ -image::media/Sorting_Columns3.jpg[Sorting_Columns3] -+ -. The next column that you want to sort is the column, Call Number. Right click the column header, Call Number. -. Click *Sort Next (Ascending)*. -+ -image::media/Sorting_Columns4.jpg[Sorting_Columns4] -+ -. The pull list has now been sorted by copy location and call number. - -image::media/Sorting_Columns5.jpg[Sorting_Columns5] - -NOTE: If you wanted to sort more columns, you could continue the process by clicking *Sort Next* for any subsequent columns. - - -Sorting Circulation Policies -~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -You want to sort the display of circulation policies in your staff client. - -. Click *Administration* -> *Local Administration* -> *Circulation Policies*. -. Right click on any column header. -. A pop-up box appears. -+ -image::media/Sorting_Columns2.jpg[Sorting_Columns2] -+ -. Check the *Display* box if you want to display a column in the staff client. -. Check the *Auto Width* box if you want the width of the columns to adjust to fit the staff client. -. Select a sort priority. -.. A sort priority of "0" indicates that no sorting has been applied. Columns will display in their default order. -.. A sort priority of "1" indicates that ascending sorting should be applied to this column first. Subsequent sorts will be applied as you continue to enter increasing numbers. -.. A sort priority of "-1" indicates that descending sorting should be applied to this column. -. Click *Save*. The circulation policies will now sort according to your selections each time that you log into the staff client. diff --git a/admin/staff_client-tab_buttons.txt b/admin/staff_client-tab_buttons.txt deleted file mode 100644 index 34797f78b1..0000000000 --- a/admin/staff_client-tab_buttons.txt +++ /dev/null @@ -1,6 +0,0 @@ -Tab Buttons ------------ - -This feature enables you to add a new tab to the Evergreen staff client by clicking the + sign adjacent to the tab that you currently have opened. As in previous versions, you can also add new tabs by clicking *File -> New Tab*, or use the hotkey, Ctrl+T. - -image::media/New_Tab_Button1.jpg[New_Tab_Button1] diff --git a/admin/template_toolkit.txt b/admin/template_toolkit.txt deleted file mode 100644 index 3c624ae168..0000000000 --- a/admin/template_toolkit.txt +++ /dev/null @@ -1,294 +0,0 @@ -TPac Configuration and Customization ------------------------------------- - -Template toolkit documentation -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -For more general information about template toolkit see: http://template-toolkit.org/docs/index.html[official -documentation]. - -The purpose of this chapter is to focus on the -Evergreen-specific uses of Template Toolkit ('TT') in the OPAC. - -TPAC URL -~~~~~~~ - -The URL for the TPAC on a default Evergreen system is -http://localhost/eg/opac/home (adjust `localhost` to match your hostname or IP -address, naturally!) - -Perl modules used directly by TPAC -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - - * `Open-ILS/src/perlmods/lib/OpenILS/WWW/EGCatLoader.pm` - * `Open-ILS/src/perlmods/lib/OpenILS/WWW/EGCatLoader/Account.pm` - * `Open-ILS/src/perlmods/lib/OpenILS/WWW/EGCatLoader/Container.pm` - * `Open-ILS/src/perlmods/lib/OpenILS/WWW/EGCatLoader/Record.pm` - * `Open-ILS/src/perlmods/lib/OpenILS/WWW/EGCatLoader/Search.pm` - * `Open-ILS/src/perlmods/lib/OpenILS/WWW/EGCatLoader/Util.pm` - -Default templates -~~~~~~~~~~~~~~~~ - -The source template files are found in `Open-ILS/src/templates/opac`. - -These template files are installed in `/openils/var/templates/opac`. - -.NOTE -You should generally avoid touching the installed default template files, -unless you are contributing changes that you want Evergreen to adopt as a new -default. Even then, while you are developing your changes, consider using -template overrides rather than touching the installed templates until you are -ready to commit the changes to a branch. See below for information on template -overrides. - -Apache configuration files -~~~~~~~~~~~~~~~~~~~~~~~~~ - -The base Evergreen configuration file on Debian-based systems can be found in -`/etc/apache2/sites-enabled/eg.conf`. This file defines the basic virtual host -configuration for Evergreen (hostnames and ports), then single-sources the -bulk of the configuration for each virtual host by including -`/etc/apache2/eg_vhost.conf`. - -TPAC CSS and media files -~~~~~~~~~~~~~~~~~~~~~~~ - -The CSS files used by the default TPAC templates are stored in the repo in -`Open-ILS/web/css/skin/default/opac/` and installed in -`/openils/var/web/css/skin/default/opac/`. - -The media files--mostly PNG images--used by the default TPAC templates are -stored in the repo in `Open-ILS/web/images/` and installed in -`/openils/var/web/images/`. - -Mapping templates to URLs -~~~~~~~~~~~~~~~~~~~~~~~~~ - -The mapping for templates to URLs is straightforward. Following are a few -examples, where `` is a placeholder for one or more directories -that will be searched for a match: - - * `http://localhost/eg/opac/home` => `/openils/var//opac/home.tt2` - * `http://localhost/eg/opac/advanced` => `/openils/var//opac/advanced.tt2` - * `http://localhost/eg/opac/results` => `/openils/var//opac/results.tt2` - -The template files themselves can process, be wrapped by, or include other -template files. For example, the `home.tt2` template currently involves a -number of other template files to generate a single HTML file: - -.Example Template Toolkit file: opac/home.tt2 -[source, html] ------------------------------------------------------------------------------- -[% PROCESS "opac/parts/header.tt2"; - WRAPPER "opac/parts/base.tt2"; - INCLUDE "opac/parts/topnav.tt2"; - ctx.page_title = l("Home") %] -
- [% INCLUDE "opac/parts/searchbar.tt2" %] -
-
-
-
- [% INCLUDE "opac/parts/homesearch.tt2" %] -
-
-
-[% END %] ------------------------------------------------------------------------------- - -We will dissect this example in some more detail later, but the important -thing to note is that the file references are relative to the top of the -template directory. - -How to override templates -~~~~~~~~~~~~~~~~~~~~~~~~~ - -Overrides for templates go in a directory that parallels the structure of the -default templates directory. The overrides then get pulled in via the Apache -configuration. - -In the following example, we demonstrate how to create a file that overrides -the default "Advanced search page" (`advanced.tt2`) by adding a new templates -directory and editing the new file in that directory. - -.Adding an override for the Advanced search page (example) -[source, bash] ------------------------------------------------------------------------------- -bash$ mkdir -p /openils/var/templates_custom/opac -bash$ cp /openils/var/templates/opac/advanced.tt2 \ - /openils/var/templates_custom/opac/. -bash$ vim /openils/var/templates_custom/opac/advanced.tt2 ------------------------------------------------------------------------------- - -We now need to teach Apache about the new templates directory. Open `eg.conf` -and add the following `` element to each of the `` -elements in which you want to include the overrides. The default Evergreen -configuration includes a `VirtualHost` directive for port 80 (HTTP) and another -one for port 443 (HTTPS); you probably want to edit both, unless you want the -HTTP user experience to be different from the HTTPS user experience. - -.Configuring the custom templates directory in Apache's eg.conf -[source,xml] ------------------------------------------------------------------------------- - - # - - # - absorb the shared virtual host settings - Include eg_vhost.conf - - PerlAddVar OILSWebTemplatePath "/openils/var/templates_algoma" - - - # - ------------------------------------------------------------------------------- - -Finally, reload the Apache configuration to pick up the changes: - -.Reloading the Apache configuration -[source,bash] ------------------------------------------------------------------------------- -bash# /etc/init.d/apache2 reload ------------------------------------------------------------------------------- - -You should now be able to see your change at http://localhost/eg/opac/advanced - -Defining multiple layers of overrides -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -You can define multiple layers of overrides, so if you want every library in -your consortium to have the same basic customizations, and then apply -library-specific customizations, you can define two template directories for -each library. - -In the following example, we define the `template_CONS` directory as the set of -customizations to apply to all libraries, and `template_BR#` as the set of -customizations to apply to library BR1 and BR2. - -As the consortial customizations apply to all libraries, we can add the -extra template directory directly to `eg_vhost.conf`: - -.Apache configuration for all libraries (eg_vhost.conf) -[source,xml] ------------------------------------------------------------------------------- -# Templates will be loaded from the following paths in reverse order. -PerlAddVar OILSWebTemplatePath "/openils/var/templates" -PerlAddVar OILSWebTemplatePath "/openils/var/templates_CONS" ------------------------------------------------------------------------------- - -Then we define a virtual host for each library to add the second layer of -customized templates on a per-library basis. Note that for the sake of brevity -we only show the configuration for port 80. - -.Apache configuration for each virtual host (eg.conf) -[source,xml] ------------------------------------------------------------------------------- - - ServerName br1.concat.ca - DocumentRoot /openils/var/web/ - DirectoryIndex index.xml index.html index.xhtml - Include eg_vhost.conf - - PerlAddVar OILSWebTemplatePath "/openils/var/templates_BR1" - - - - - ServerName br2.concat.ca - DocumentRoot /openils/var/web/ - DirectoryIndex index.xml index.html index.xhtml - Include eg_vhost.conf - - PerlAddVar OILSWebTemplatePath "/openils/var/templates_BR2" - - ------------------------------------------------------------------------------- - -Changing some text in the TPAC -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -Out of the box, the TPAC includes a number of placeholder text and links. For -example, there is a set of links cleverly named 'Link 1', 'Link 2', and so on -in the header and footer of every page in the TPAC. Let's customize that for -our `templates_BR1` skin. - -To begin with, we need to find the page(s) that contain the text in question. -The simplest way to do that is with the handly utility `ack`, which is much -like `grep` but with built-in recursion and other tricks. On Debian-based -systems, the command is `ack-grep` as `ack` conflicts with an existing utility. -In the following example, we search for files that contain the text "Link 1": - -.Searching for text matching "Link 1" -[source,bash] ------------------------------------------------------------------------------- -bash$ ack-grep "Link 1" /openils/var/templates/opac -/openils/var/templates/opac/parts/topnav_links.tt2 -4: [% l('Link 1') %] ------------------------------------------------------------------------------- - -Next, we copy the file into our overrides directory and edit it with `vim`: - -.Copying the links file into the overrides directory -[source,bash] ------------------------------------------------------------------------------- -bash$ cp /openils/var/templates/opac/parts/topnav_links.tt2 \ - /openils/var/templates_BR1/opac/parts/topnav_links.tt2 -bash$ vim /openils/var/templates_BR1/opac/parts/topnav_links.tt2 ------------------------------------------------------------------------------- - -Finally, we edit the link text in `opac/parts/header.tt2`. - -.Content of the opac/parts/header.tt2 file -[source,html] ------------------------------------------------------------------------------- - ------------------------------------------------------------------------------- - -For the most part, the page looks like regular HTML, but note the `[%_("` -`")%]` that surrounds the text of each link. The `[% ... %]` signifies a TT -block, which can contain one or more TT processing instructions. `l(" ... ");` -is a function that marks text for localization (translation); a separate -process can subsequently extract localized text as GNU gettext-formatted PO -files. - -.NOTE -As Evergreen supports multiple languages, any customizations to Evergreen's -default text must use the localization function. Also, note that the -localization function supports placeholders such as `[_1]`, `[_2]` in the text; -these are replaced by the contents of variables passed as extra arguments to -the `l()` function. - -Once we have edited the link and link text to our satisfaction, we can load -the page in our Web browser and see the live changes immediately (assuming -we are looking at the BR1 overrides, of course). - -Troubleshooting -~~~~~~~~~~~~~~~ - -If there is a problem such as a TT syntax error, it generally shows up as a -an ugly server failure page. If you check the Apache error logs, you will -probably find some solid clues about the reason for the failure. For example, -in the following example the error message identifies the file in which the -problem occurred as well as the relevant line numbers: - -.Example error message in Apache error logs -[source,bash] ------------------------------------------------------------------------------- -bash# grep "template error" /var/log/apache2/error_log -[Tue Dec 06 02:12:09 2011] [warn] [client 127.0.0.1] egweb: template error: - file error - parse error - opac/parts/record/summary.tt2 line 112-121: - unexpected token (!=)\n [% last_cn = 0;\n FOR copy_info IN - ctx.copies;\n callnum = copy_info.call_number_label;\n ------------------------------------------------------------------------------- - diff --git a/admin/user_activity_type.txt b/admin/user_activity_type.txt deleted file mode 100644 index 979f4798b1..0000000000 --- a/admin/user_activity_type.txt +++ /dev/null @@ -1,32 +0,0 @@ -User Activity Types -------------------- - -The User Activity Types feature enables you to specify the user activity that you want to record in the database. You can use this feature for reporting purposes. This function will also display a last activity date in a user's account. - -Enabling this Feature -~~~~~~~~~~~~~~~~~~~~~ - -Click *Admin* -> *Server Administration* -> *User Activity Types* to access the default set of user activity types and to add new ones. The default set of user activity types records user logins to the Evergreen ILS and to third party products that communicate with Evergreen. - -The *Label* is a free text field that enables you to describe the activity that you are tracking. - -The *Event Caller* describes the third party software or Evergreen interface that interacts with the Evergreen database and is responsible for managing the communication between the parties. - -The *Event Type* describes the type of activity that Evergreen is tracking. Currently, this feature only tracks user authentication. - -The *Event Mechanism* describes the framework for communication between the third party software or OPAC and the database. Enter an event mechanism if you want to track the means by which the software communicates with the database. If you do not want to track how the softwares communicate, then leave this field empty. - -The *Enabled* field allows you to specify which types of user activity that you would like to track. - -The *Transient* column enables you to decide how many actions you want to track. If you want to track only the last activity, then enter *True.* If you want to trace all activity by the user, enter *False*. - -image::media/User_Activity_Types1A.jpg[User_Activity_Types1A] - - -Using this Feature -~~~~~~~~~~~~~~~~~~ - -The last activty date for user logins appears in the patron's summary. - -image::media/User_Activity_Types2A.jpg[User_Activity_Types2A] - diff --git a/attributions.txt b/attributions.txt deleted file mode 100644 index 3d8e6e07d9..0000000000 --- a/attributions.txt +++ /dev/null @@ -1,46 +0,0 @@ -[[attributions]] -Attributions -============ - -Copyright © 2009-2012 Evergreen DIG - -Copyright © 2007-2012 Equinox - -Copyright © 2007-2012 Dan Scott - -Copyright © 2009-2012 BC Libraries Cooperative (SITKA) - -Copyright © 2008-2012 King County Library System - -Copyright © 2009-2012 Pioneer Library System - -Copyright © 2009-2012 PALS - -Copyright © 2009-2012 Georgia Public Library Service - -Copyright © 2008-2012 Project Conifer - -Copyright © 2009-2012 Bibliomation - -Copyright © 2008-2012 Evergreen Indiana - -Copyright © 2008-2012 SC LENDS - - - -*Current DIG Members* - -* Hilary Caws-Elwitt, Susquehanna County Library -* Karen Collier, Kent County Public Library -* George Duimovich, NRCan Library -* Sally Fortin, Equinox Software -* Wolf Halton, Lyrasis -* June Rayner, eiNetwork -* Steve Sheppard -* Ben Shum, Bibliomation -* Roni Shwaish, eiNetwork -* Robert Soulliere, Mohawk College -* Tim Spindler, C/W MARS -* Lindsay Stratton, Pioneer Library System -* Yamil Suarez, Berklee College of Music -* Jenny Turner, PALS diff --git a/cataloging/batch_importing_MARC.txt b/cataloging/batch_importing_MARC.txt deleted file mode 100644 index 906af8cf5e..0000000000 --- a/cataloging/batch_importing_MARC.txt +++ /dev/null @@ -1,214 +0,0 @@ -Batch Importing MARC Records ----------------------------- - -The cataloging module in version 2.2 includes an enhanced MARC Batch Import interface. This interface features improved matching of records and managing of your import queue. In 2.2, you will be able to specify match points between incoming and existing records. You will also be able to apply filters to your queue that enable you to generate any errors that may have occurred during import. You will also be able to print your queue, email your queue, or export your queue as a CSV file. - -Permissions -~~~~~~~~~~~ - -To use match sets to import records, you will need the following permission: - -ADMIN_IMPORT_MATCH_SET - - -Record Display Attributes -~~~~~~~~~~~~~~~~~~~~~~~~~ - -This feature enables you to specify the tags and subfields that will display in records that appear in the import queue. - - -*Record Match Sets* - -This feature enables you to create custom match points that you can use to accurately match incoming records with existing catalog records. - - -In this example, to demonstrate matching on record attributes and MARC tags and subfields, we will create a record match set that defines a match based on the title of the record, in either the 240 or 245, and the fixed field, Lang. You can add multiple record attributes and MARC tags to customize a record match set. - - -1) Click *Cataloging -> MARC Batch Import/Export*. - -2) Create a new record match set. Click *Record Match Sets -> New Match Set*. - -3) Enter a name for the record match set. - -4) Select an *Owning Library* from the drop down menu. Staff with permissions at this location will be able to use this record match set. - -5) Select a *Match Set Type* from the drop down menu. You can create a match set for authority records or bibliographic records. - -6) Click *Save*. - - -image::media/Batch_Importing_MARC_Records1.jpg[Batch_Importing_MARC_Records1] - - -7) The screen will refresh to list the record match set that you created. Click the link to the record match set. - -8) Create an expression that will define the match points for the incoming record. You can choose from two areas to create a match: *Record Attribute* or *MARC Tag and Subfield*. You can use the Boolean operators AND and OR to combine these elements to create a match set. - -9) Select a *Record Attribute* from the drop-down menu. - -10) Enter a *Match Score.* The *Match Score* indicates the relative importance of that match point as Evergreen evaluates an incoming record against an existing record. You can enter any integer into this field. The number that you enter is only important as it relates to other match points. Recommended practice is that you create a match score of one (1) for the least important match point and assign increasing match points to the power of 2 to working points in increasing importance. - -11) Check the *Negate?* box if you want to negate the match point. Checking this box would be the equivalent of applying a Boolean operator of NOT to the match point. - - - -image::media/Batch_Importing_MARC_Records2.jpg[Batch_Importing_MARC_Records2] - - - -12) Click *Ok.* - -13) Drag the completed match point under the folder with the appropriately-named Boolean folder under the Expression tree. - - - -image::media/Batch_Importing_MARC_Records3.jpg[Batch_Importing_MARC_Records3] - - -The match point will nest underneath the folder in the Expression tree. - - -image::media/Batch_Importing_MARC_Records4.jpg[Batch_Importing_MARC_Records4] - - -14) Enter another *Boolean Operator* to further refine your match set. - -15) Click *Boolean Operator*. - -16) Select the *OR* operator from the drop down menu. - -17) Click *Ok*. - -18) Drag the operator to the expression tree. - - -image::media/Batch_Importing_MARC_Records5.jpg[Batch_Importing_MARC_Records5] - - -19) Click *MARC Tag and Subfield*. - -20) Enter a *MARC tag* on which you want the records to match. - -21) Enter a *subfield* on which you want the records to match. - -22) Enter a *Match Score.* The *Match Score* indicates the relative importance of that match point as Evergreen evaluates an incoming record against an existing record. You can enter any integer into this field. The number that you enter is only important as it relates to other match points. Recommended practice is that you create a match score of one (1) for the least important match point and assign increasing match points to the power of 2 to working points in increasing importance. - -23) Check the *Negate?* box if you want to negate the match point. Checking this box would be the equivalent of applying a Boolean operator of NOT to the match point. - - -24) Click *Ok.* - - -image::media/Batch_Importing_MARC_Records6.jpg[Batch_Importing_MARC_Records6] - - -25) Drag the completed match point under the folder with the appropriately-named Boolean folder under the Expression tree. The Expression will build across the top of the screen. - -26) Add additional MARC tags or record attributes to build the expression tree. - -27) Click *Save Changes to Expression*. - - -image::media/Batch_Importing_MARC_Records7.jpg[Batch_Importing_MARC_Records7] - - -*Replace Mode* - -Replace Mode enables you to replace an existing part of the expression tree with a new record attribute, MARC tag, or Boolean operator. For example, if the top of the tree is AND, in replace mode, you could change that to an OR. - - -1) Create a working match point. - -2) Click *Enter replace mode*. - -3) Highlight the piece of the tree that you want to replace. - -4) Drag the replacement piece over the highlighted piece. - -5) Click *Exit Replace Mode*. - - -*Quality Metrics* - - -1) Set the *Quality Metrics for this Match Set*. Quality metrics are used to determine the overall quality of a record. Each metric is given a weight and the total quality value for a record is equal to the sum of all metrics that apply to that record. For example, a record that has been cataloged thoroughly and contains accurate data would be more valuable than one of poor quality. You may want to ensure that the incoming record is of the same or better quality than the record that currently exists in your catalog; otherwise, you may want the match to fail. The quality metric is optional. - -2) You can create quality metrics based on the record attribute or the MARC Tag and Subfield. - -3) Click *Record Attribute.* - -4) Select an attribute from the drop down menu. - -5) Enter a value for the attribute. - -6.) Enter a match score. You can enter any integer into this field. The number that you enter is only important as it relates to other quality values for the current configuration. Higher scores would indicate increasing quality of incoming records. You can, as in the expression match score, increase the quality points by increasing subsequent records by a power of 2 (two). - -7) Click *Ok*. - - -image::media/Batch_Importing_MARC_Records8.jpg[Batch_Importing_MARC_Records8] - - - -*Import Records* - -The *Import Records* interface incorporates record match sets, quality metrics, more merging options, and improved ways to manage your queue. In this example, we will import a batch of records. One of the records in the queue will contain a matching record in the catalog that is of lower quality than the incoming record. We will import the record according to the guidelines set by our record match set, quality metrics, and merge/overlay choices that we will select. - - -1) Select a *Record Type* from the drop down menu. - -2) Create a queue to which you can upload your records, or add you records to an existing queue. Queues are linked to match sets and a holdings import profile. You cannot change a holdings import or record match set for a queue. - -3) Select a *Record Match Set* from the drop down menu. - -4) Select a *Holdings Import Profile* if you want to import holdings that are attached to your records. - -5) Select a *Record Source* from the drop down menu. - -6) Select a *Merge Profile*. Merge profiles enable you to specify which tags should be removed or preserved in incoming records. - -7) Choose one of the following import options if you want to auto-import records: - -a. *Merge on Single Match* - Using the Record Match Set, Evergreen will only attempt to perform the merge/overlay action if only one match was found in the catalog. - -b. *Merge on Best Match* - If more than one match is found in the catalog for a given record, Evergreen will attempt to perform the merge/overlay action with the best match as defined by the match score and quality metric. - -NOTE: Quality ratio affects only the *Merge on Single Match* and *Merge on Best Match* options. - -8) Enter a *Best/Single Match Minimum Quality Ratio.* Divide the incoming record quality score by the record quality score of the best match that might exist in the catalog. By default, Evergreen will assign any record a quality score of 1 (one). If you want to ensure that the inbound record is only imported when it has a higher quality than the best match, then you must enter a ratio that is higher than 1. For example, if you want the incoming record to have twice the quality of an existing record, then you should enter a 2 (two) in this field. If you want to bypass all quality restraints, enter a 0 (zero) in this field. - - -9) Select an *Insufficient Quality Fall-Through Profile* if desired. This field enables you to indicate that if the inbound record doees not meet the configured quality standards, then you may still import the record using an alternate merge profile. This field is typically used for selecting a merge profile that allows -the user to import holdings attached to a lower quality record without replacing the existing (target) record with the incoming record. This field is optional. - -10) *Browse* to find the appropriate file, and click *Upload*. The files will be uploaded to a queue. - - -image::media/Batch_Importing_MARC_Records9.jpg[Batch_Importing_MARC_Records9] - -11) The screen will display records that have been uploaded to your queue. - -image::media/Batch_Importing_MARC_Records15.jpg[Batch_Importing_MARC_Records15] - - -12) If Evergreen indicates that matching records exist, then click the *Matches* link to view the matching records. Check the box adjacent to the existing record that you want to merge with the incoming record. - -image::media/Batch_Importing_MARC_Records10.jpg[Batch_Importing_MARC_Records10] - -13) Click *Back to Import Queue*. - -14) Check the boxes of the records that you want to import, and click *Import Selected Records*, or click *Import All Records*. - -15) A pop up window will offer you the same import choices that were present on the *Import Records* screen. You can choose one of the import options, or click *Import*. - -image::media/Batch_Importing_MARC_Records9.jpg[Batch_Importing_MARC_Records9] - -16) The screen will refresh. The *Queue Summary* indicates that the record was imported. The *Import Time* column records the date that the record was imported. - -image::media/Batch_Importing_MARC_Records12.jpg[Batch_Importing_MARC_Records12] - -17) Search the catalog to confirm that the record was imported. - -image::media/Batch_Importing_MARC_Records14.jpg[Batch_Importing_MARC_Records14] - diff --git a/cataloging/conjoined_items.txt b/cataloging/conjoined_items.txt deleted file mode 100644 index 4c95842db5..0000000000 --- a/cataloging/conjoined_items.txt +++ /dev/null @@ -1,106 +0,0 @@ -Conjoined Items ---------------- - -Prior to Evergreen version 2.1, items could be attached to only one bibliographic record. The Conjoined Items feature in Evergreen 2.1 enables catalogers to link items to multiple bibliographic records. This feature will enable more precise cataloging. For example, catalogers will be able to indicate items that are printed back to back, are bilingual, are part of a bound volume, are part of a set, or are available as an e-reader pre-load. This feature will also help the user retrieve more relevant search results. For example, a librarian catalogs a multi-volume festschrift. She can create a bibliographic record for the festschrift and a record for each volume. She can link the items on each volume to the festschrift record so that a patron could search for a volume or the festschrift and retrieve information about both works. - -In the example below, a librarian has created a bibliographic record for two bestselling items. These books are available as physical copies in the library, and they are available as e-reader downloads. The librarian will link the copy of the Kindle to the bibliographic records that are available on the e-reader. - -Using the Conjoined Items Feature -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -The Conjoined Items feature was designed so that you can link items between bibliographic records when you have the item in hand, or when the item is not physically present. Both processes are described here. The steps are fewer if you have the item in hand, but both processes accomplish the same task. This documentalso demonstrates the process to edit or delete links between items and bibliographic records. Finally, the permission a cataloger needs to use this feature is listed. - -.Scenario 1: I want to link an item to another bibliographic record, but I do not have the item in hand - -1) Retrieve the bibliographic record to which you would like to link an item. - -2) Click *Actions for this Record -> Mark as Target for Conjoined Items.* - - -image::media/conj1.jpg[conj1] - - -3) A confirmation message will appear. Click *OK.* - -4) In a new tab, retrieve the bibliographic record with the item that you want to link to the other record. - -5) Click *Actions for this Record -> Holdings Maintenance.* - -6) Select the copy that you want to link to the other bibliographic record. Right-click, or click *Actions for Selected Rows -> Link as Conjoined Items to Previously Marked Bib Record.* - -image::media/conj2.jpg[conj2] - - -7) The *Manage Conjoined Items* interface opens in a new tab. This interface enables you to confirm the success of the link, and to change the peer type if desired. The *Result* column indicates that you created a successful link between the item and the bib record. - -image::media/conj3.jpg[conj3] - -The default peer type, *Back-to-back*, was set as the peer type for our item. To change a peer type after the link has been created, right-click or click *Actions for Selected Items -> Change Peer Type*. A drop down menu will appear. Select the desired peer type, and click *OK.* - - -image::media/conj4.jpg[conj4] - - -8) The *Result* column will indicate that the *Peer Type* [has been] *Updated.* - - -image::media/conj5.jpg[conj5] - - -9) To confirm the link between the item and the desired bib record, reload the tab containing the bib record to which you linked the item. Click the link for *Linked Titles.* - - -image::media/conj6.jpg[conj6] - - -10) To view the copy details, including the peer type, click *Copy Details.* - - -image::media/conj7.jpg[conj7] - - -Items can be linked to multiple bibliographic records simultaneously. If you click the linked titles button in the copy details, then you will retrieve a list of bibliographic records to which this item is linked. - - -image::media/conj8.jpg[conj8] - - -.Scenario 2: I want to link an item to another bibliographic record, and I do have the item in hand - -1) Retrieve the bibliographic record to which you would like to add the item. - -2) Click *Actions for this Record -> Manage Conjoined Items.* - - -image::media/conj9.jpg[conj9] - - -3) A note in the bottom left corner of the screen will confirm that the record was targeted for linkage with conjoined items, and the *Manage Conjoined Items* screen will appear. - -4) Select the peer type from the drop down menu, and scan in the barcode of the item that you want to link to this record. - -5) Click *Link to Bib (Submit).* - - -image::media/conj10.jpg[conj10] - - -6) The linked item will appear in the screen. The *Result* column indicates Success. - -7) To confirm the linkage, click *Actions for this Record -> OPAC View.* - -8) When the bibliographic record appears, click *Reload. Linked Titles* will show the linked title and item. - - -.Scenario 3: I want to edit or break the link between a copy and a bibliographic record - -1) Retrieve the bibliographic record that has a copy linked to it. - -2) Click *Actions for this Record -> Manage Conjoined Items.* - -3) Select the copy that you want to edit, and right-click or click *Actions for Selected Items.* - -4) Make any changes, and click *OK.* - - -UPDATE_COPY - Link items to bibliographic records diff --git a/cataloging/monograph_parts.txt b/cataloging/monograph_parts.txt deleted file mode 100644 index 122fcaea38..0000000000 --- a/cataloging/monograph_parts.txt +++ /dev/null @@ -1,57 +0,0 @@ -Monograph Parts ---------------- - -*Monograph Parts* enables you to differentiate between parts of monographs or other multi-part items. This feature enables catalogers to describe items more precisely by labeling the parts of an item. For example, catalogers might identify the parts of a monograph or the discs of a DVD set. This feature also allows patrons more flexibility when placing holds on multi-part items. A patron could place a hold on a specific disc of a DVD set if they want to access a specific season or episode rather than an entire series. - -Four new permissions are used by this functionality: CREATE_MONOGRAPH_PART, UPDATE_MONOGRAPH_PART, DELETE_MONOGRAPH_PART and MAP_MONOGRAPH_PART. Thes -e permissions should be assigned at the consorial level to those groups or users that will make use of the features described below. - - -Add a monograph part to an existing record -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -To add a monograph part to an existing record in the catalog: - -1) Retrieve a record. - -2) Click *Actions for this Record -> Manage Parts* - - -image::media/monograph_parts1.jpg[monograph_parts1] - - -3) Click *New Monograph Part* - -4) Enter the *label* that you want to appear to the user in the catalog, and click *Save*. This will create a list of monograph parts from which you can choose when you create a volume and copy. - - -image::media/monograph_parts2.jpg[monograph_parts2] - - -5) Add a volume and copy. To add a volume and copy to your workstation library, click the *Add Volumes* link in the *Record Summary* at the top of the bibliographic record, or click *Actions for this Record -> Add Volumes*. - -To add a volume and copy to your workstation library or other libraries, click *Actions for this Record -> Holdings Maintenance -> Add Volumes*. - - -image::media/monograph_parts3.jpg[monograph_parts3] - - -6) The *Unified Volume/Copy Creator* opens. Enter the number of volumes that you want to add to the catalog and the volume description. - -7) Enter the number of copies and barcode(s) of each item. - -8) Select the *part designation* from the drop down menu adjacent to the barcode field. - -9) Apply a template to the copies, or edit fields in the *Copy Editor*. - - -image::media/monograph_parts4.jpg[monograph_parts4] - - -10) Click *Create Volumes/Items*. - -11) The *Holdings Maintenance* screen will refresh to demonstrate the addition of the volume, copy, and part. These fields also appear in the OPAC View. - - -image::media/monograph_parts5.jpg[monograph_parts5] - diff --git a/cataloging/overlay_record_3950_import.txt b/cataloging/overlay_record_3950_import.txt deleted file mode 100644 index 73c63f1427..0000000000 --- a/cataloging/overlay_record_3950_import.txt +++ /dev/null @@ -1,55 +0,0 @@ -Overlay Existing Catalog Record via Z39.50 Import -------------------------------------------------- - -This feature enables you to replace a catalog record with a record obtained through a Z39.50 search. No new permissions or administrative settings are needed to use this feature. - -*To Overlay an Existing Record via Z39.50 Import:* - -1) Click *Cataloging -> Import Record from Z39.50* - -2) Select at least one *Service* in addition to the *Local Catalog* in the *Service and Credentials* window in the top right panel. - -3) Enter search terms in the *Query* window in the top left panel. - -4) Click *Search*. - -image::media/Overlay_Existing_Record_via_Z39_50_Import1.jpg[] - -5) The results will appear in the lower window. - -6) Select the record in the local catalog that you wish to overlay. - -7) Click *Mark Local Result as Overlay Target* - - -image::media/Overlay_Existing_Record_via_Z39_50_Import2.jpg[] - - -8) A confirmation message appears. Click *OK*. - -9) Select the record that you want to replace the existing catalog record. - -10) Click *Overlay.* - - -image::media/Overlay_Existing_Record_via_Z39_50_Import3.jpg[] - - -11) The record that you selected will open in the MARC Editor. Make any desired changes to the record, and click *Overlay Record*. - -image::media/Overlay_Existing_Record_via_Z39_50_Import4.jpg[] - - -12) The catalog record that you want to overlay will appear in a new window. Review the MARC record to verify that you are overlaying the correct catalog record. - -13) If the correct record appears, click *Overlay*. - - -image::media/Overlay_Existing_Record_via_Z39_50_Import5.jpg[] - -14) A confirmation message will appear to confirm that you have overlaid the record. Click *Ok*. - -15) The screen will refresh in the OPAC View to show that the record has been overlaid. - - -image::media/Overlay_Existing_Record_via_Z39_50_Import6.jpg[] diff --git a/circulation/README b/circulation/README deleted file mode 100644 index e69de29bb2..0000000000 diff --git a/circulation/booking.txt b/circulation/booking.txt deleted file mode 100644 index 730b890569..0000000000 --- a/circulation/booking.txt +++ /dev/null @@ -1,272 +0,0 @@ -Booking Module --------------- - -Creating a Booking Reservation -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -Only staff members may create reservations. A reservation can be started from a patron record, or a booking resource. To reserve catalogued items, you may start from searching the catalogue, if you do not know the booking item's barcode. - -To create a reservation from a patron record -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -1) Retrieve the patron’s record. - -2) Select Other --> Booking --> Create or Cancel Reservations. This takes you to the Reservations Screen. - -image::media/booking-create-1.png[] - -3) For non-catalogued items, choose a Bookable Resource Type and click Next. For catalogued items, enter the barcode in Enter the barcode of a catalogued, bookable resource box, then click Next beside the box. - -image::media/booking-create-2.png[] - -4) For non-catalogued resources, the Bookable Resource Type and the items associated with the type will appear. - -image::media/booking-create-3.png[] - -For catalogued items, the title and the item will display in the box. - -5) Select the date and time for the reservation in I need this resource... area. Click the date field. A calendar widget will be displayed for you to choose a date. Click the time field to choose time from the dropdown list. - -image::media/booking-create-4.png[] - -[NOTE] -If incorrect date and time is selected, the date/time boxes will appear in red. For example, if the time for which the reservation is set has already passed, the boxes will appear in red. There must be at least 15 minutes between the creation of the reservation and the start time of the reservation. - -6) For non-catalogued resources, patrons may specify special feature(s), if any, of the resource. With these attributes: allows you to do so. For example, if a patron is booking a laptop he/she can choose between PC and Mac and even choose a specific operating system if they need to. Click the drop down arrow to select your option from the list. - -image::media/booking-create-5.png[] - -7) Select the pickup location from the dropdown list. - -image::media/booking-create-6.png[] - -8) If there are multiple copies of the resource and any item listed is acceptable, click Reserve Any. To choose a specific item, select it -and then click Reserve Selected. - -image::media/booking-create-7.png[] - -9) A message will confirm that the action succeeded. Click OK on the prompt. - -10) The screen will refresh and the reservation will appear below the patron’s name at the bottom of the screen. - -image::media/booking-create-9.png[] - -To create a reservation from a booking resource -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -You need to know the barcode of the patron when you create a reservation for him/her from a booking resource. - -1) From the Booking menu, select Create Reservations - -image::media/booking-create-module-1.png[] - -2) Choose a Bookable Resource Type and click Next or enter the barcode of a catalogued resource and click Next. - -image::media/booking-create-module-2.png[] - -3) For non-catalogued resources, a screen showing the Bookable Resource Type and the items associated with the type will appear. - -image::media/booking-create-module-3.png[] - -For catalogued resources, the title and item will appear. - -4) Enter the user’s barcode in the Reserve to patron barcode box. The user’s existing reservations, if any, will appear at the bottom of the screen. - -image::media/booking-create-module-4.png[] - -5) Select the date and time for the reservation in I need this resource... area. Click the date field. A calendar widget will be displayed for you to choose a date. Click the time field to choose time from the dropdown list. - -image::media/booking-create-4.png[] - -[NOTE] -If incorrect date and time is selected, the date/time boxes will appear in red. For example, if the time for which the reservation is set has already passed, the boxes will appear in red. The times must be set correctly for the reservation to be created. There must be at least 15 minutes between the creation of the reservation and the start time of the reservation. - - -6) For non-catalogued resources, patrons may specify special feature(s), if any, of the resource. The With these attributes: allows you to do so. For example, if a patron is booking a laptop they can choose between PC and Mac and even choose a specific operating system if they need to. Click the dropdown arrow to select your option from the list. - -image::media/booking-create-5.png[] - -7) Select the pickup location from the dropdown list. - -image::media/booking-create-6.png[] - -8) If there are multiple copies of the resource and any item listed is acceptable, click Reserve Any. To choose a specific item, select it and then click Reserve Selected. - -image::media/booking-create-7.png[] - -9) A message will confirm that the action succeeded. Click OK on the prompt. - -10) The screen will refresh and the reservation will appear below the patron’s name at the bottom of the screen. - -image::media/booking-create-9.png[] - - -Search the catalogue to create a reservation -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -If you would like to reserve a catalogued item but do not know the item barcode, you may start with a catalogue search. - -1) In the staff client, select Cataloguing --> Search the Catalogue or keyboard shortcut F3 to search for the item you wish to reserve. You may search by any bibliographic information. - -2) Click the title to display the record summary. In the Copy Summary, select Copy Details in Actions column. - -3) The Copy Details will appear in a new row. In the barcode column, click the book now link. - -4) A screen showing the title and barcodes of available copies will appear. - -5) Enter the user’s barcode in the Reserve to patron barcode box. The user’s existing reservations, if any, will appear at the bottom of the screen. - -6) Select the date and time in I need this resource... section. If the date and time set is incorrect the boxes appear in red. For example, if the time for which the reservation is set has already passed, the boxes will appear in red. - -7) Select pickup location. If there are multiple copies and any of the listed items is acceptable, click Reserve Any. To choose a specific item, select it and then click Reserve Selected. - -8) A message will confirm that the action succeeded. Click OK on the prompt. - -9) The screen will refresh, and the reservation will appear below the user’s name. - -[NOTE] -Reservations on catalogued items can be created on Item Status (F5) screen. Select the item, then Actions for Selected Items → Book Item Now. - -Reservation Pull List -~~~~~~~~~~~~~~~~~~~~~ - -Reservation pull list can be generated dynamically on the Staff Client. - -1) To create a pull list, select Booking --> Pull List. - -image::media/booking-pull-1.png[] - -2) You can decide how many days in advance you would like to pull reserved items. Enter the number of days in the box adjacent to Generate list for this many days hence. For example, if you would like to pull items that are needed today, you can enter 1 in the box, and you will retrieve items that need to be pulled today. - -3) Click Fetch to retrieve the pull list. - -image::media/booking-pull-2.png[] - -4) The pull list will appear. Click Print to print the pull list. - -image::media/booking-pull-3.png[] - -Capturing Items for Reservations -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -Reservations must be captured before they are ready to be picked up by the patron. - -[CAUTION] -Always capture reservations in Booking Module. Check In function in Circulation does not function the same as Capture Resources. - -1) In the staff client, select Booking --> Capture Resources. - -image::media/booking-capture-1.png[] - -2) Scan the item barcode or type the barcode then click Capture. - -image::media/booking-capture-2.png[] - -3) The message Capture succeeded will appear to the right. Information about the item will appear below the message. Click Print button to print a slip for the reservation. - -image::media/booking-capture-3.png[] - - -Picking Up Reservations -~~~~~~~~~~~~~~~~~~~~~~~ - -[CAUTION] -Always use the dedicated Booking Module interfaces for tasks related to reservations. Items that have been captured for a reservation cannot be checked out using the Check Out interface, even if the patron is the reservation recipient. - -1) Ready-for-pickup reservations can be listed from Other --> Booking --> Pick Up Reservations within a patron record or Booking --> Pick Up Reservations. - - -image::media/booking-pickup-1.png[] - -image::media/booking-pickup-module-1.png[] - - -2) Scan the patron barcode if using Booking --> Pick Up Reservations. - -3) The reservation(s) available for pickup will display. Select those you want to pick up and click Pick Up. - -image::media/booking-pickup-2.png[] - -4) The screen will refresh to show that the patron has picked up the reservation(s). - -image::media/booking-pickup-3.png[] - - -Returning Reservations -~~~~~~~~~~~~~~~~~~~~~~ - -[CAUTION] -When a reserved item is brought back, staff must use the Booking Module to return the reservation. - -1) To return reservations, select Booking --> Return Reservations - -image::media/booking-return-module-1.png[] - -2) You can return the item by patron or item barcode. Here we choose Resource to return by item barcode. Scan or enter the barcode, and click Go. - -image::media/booking-return-module-2.png[] - -3) A pop up box will tell you that the item was returned. Click OK on the prompt. - -4) If we select Patron on the above screen, after scanning the patron's barcode, reservations currently out to that patron are displayed. Highlight the reservations you want to return, and click Return. - -image::media/booking-return-2.png[] - -5) The screen will refresh to show any resources that remain out and the reservations that have been returned. - -image::media/booking-return-module-4.png[] - -[NOTE] -Reservations can be returned from within patron records by selecting Other --> Booking --> Return Reservations - -Cancelling a Reservation -~~~~~~~~~~~~~~~~~~~~~~~~ - -A reservation can be cancelled in a patron’s record or reservation creation screen. - -Cancel a reservation from the patron record -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -1) Retrieve the patron's record. - -2) Select Other --> Booking --> Create or Cancel Reservations. - -image::media/booking-create-1.png[] - -3) The existing reservations will appear at the bottom of the screen. - -image::media/booking-cancel-1.png[] - -4) Highlight the reservation that you want to cancel. Click Cancel Selected. - -image::media/booking-cancel-2.png[] - -[NOTE] -Use Shift or Ctrl on keyboard and mouse click to select multiple reservations if needed. - -5) A pop-up window will confirm the cancellation. Click OK on the prompt. - -6) The screen will refresh, and the cancelled reservation(s) will disappear. - -image::media/booking-cancel-4.png[] - -Cancel a reservation on reservation creation screen -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -1) Access the reservation creation screen by selecting Booking --> Create Reservations. - -2) Select any Bookable Resource Type, then click Next. - -3) Scan or type in the patron barcode in Reserve to Patron box then hit Enter. - -4) Patron's existing reservations will display at the bottom of the screen. - -5) Select those that you want to cancel, then click Cancel Selected. - - - - - - - - diff --git a/circulation/circulating_items.txt b/circulation/circulating_items.txt deleted file mode 100644 index 51d653e66c..0000000000 --- a/circulation/circulating_items.txt +++ /dev/null @@ -1,327 +0,0 @@ -Circulating Items ------------------ - -Check Out (F1) -~~~~~~~~~~~~~~ - -Regular Items -^^^^^^^^^^^^^ - -1) To check out an item press *F1*, click *Check Out* on the Circulation toolbar, or select *Circulation* -> *Check Out Items*. - -image::media/checkout_menu.png[] - -2) Scan or enter patron's barcode and click *Submit* if entering barcode manually. If scanning, number is submitted automatically. - -image::media/retrieve_patron.png[] - -3) Scan or enter item barcode manually, clicking *Submit* if manual. - -image::media/checkout_item_barcode.png[] - -4) Due date is now displayed. - -image::media/due_date_display.png[] - -5) When all items are scanned, hit the *F1* key or click the *Check Out* button on the Circulation toolbar to generate slip receipt or to exit patron record if not printing slip receipts. - -Pre-cataloged Items -^^^^^^^^^^^^^^^^^^^ - -1) Go to patron's *Check Out* screen by clicking *Circulation* -> *Check Out Items*. - -2) Scan the item barcode. - -3) At prompt, click *Pre-Cataloged*. - -image::media/pre_cat_alert.png[] - -4) Enter required information and click *Check Out*. - -image::media/precat.png[] - -[TIP] -On check-in, Evergreen will prompt staff to re-route the item to cataloging. - -Due Dates -^^^^^^^^^ - -Circulation periods are pre-set. When items are checked out, due dates are automatically calculated and inserted into circulation records if the *Specific Due Date* checkbox is not selected on the Check Out screen. The *Specific Due Date* checkbox allows you to set a different due date to override the pre-set loan period. - -Before you scan the item, select the *Specific Due Date* checkbox. Use the calendar widget to select a date. Or click in day, month or year, then use the up or down arrows to make the change or simply delete the data, then enter again. Time is used for hourly loan only. This date applies to all items until you change the date, de-select the *Specific Due Date* checkbox, or quit the patron record. - -image::media/specify_due_date1.png[] - -image::media/specify_due_date2.png[] - -Check In (F2) -~~~~~~~~~~~~~ - -Regular check in -^^^^^^^^^^^^^^^^ - -1) To check in an item, select *Circulation -> Check In Items*, click *Check In* on the Circulation toolbar, or press *F2*. - -image::media/check_in_menu.png[] - -2) Scan item barcode or enter manually and click *Submit*. - -image::media/checkin_barcode.png[] - -3) If there is an overdue fine associated with the checkin, an alert will appear at the top of the screen with a fine tally for the current checkin session. To immediately handle fine payment, click the alert to jump to the patron's bill record. - -image::media/overdue_checkin.png[] - -Backdated check in -^^^^^^^^^^^^^^^^^^ - -This is useful for clearing a book drop. - -1) To change effective check-in date, select *Circulation* -> *Check In Items*, or press *F2*. Use the calendar widget to choose the effective date. - -image::media/backdate_checkin.png[] - -2) The top green bar changes to red. The new effective date is now displayed in the header. - -image::media/backdate_red.png[] - -3) Move the cursor to the *Barcode* field. Scan the items. When finishing backdated check-in, change the *Effective Date* back to today's date. - -Backdate Post-Checkin -^^^^^^^^^^^^^^^^^^^^^ - -After an item has been checked in, you may use the Backdate Post-Checkin function to backdate the check-in date. - -1) Select the item on the Check In screen, click Actions for Selected Items -> Backdate Post-Checkin. - -image::media/backdate_post_checkin.png[] - -2) Use the calendar widget to select an effective check-in date. Click Apply. Overdue fines, if any, will be adjusted according to the new effective check-in date. - -image::media/backdate_post_date.png[] - -[TIP] -Checkin Modifiers -=================================================== -At the right bottom corner there is a *Checkin Modifiers* pop-up list. The options are: - -- Ignore Pre-cat Items: no prompt when checking in a pre-cat item. Item will be routed to Cataloging with Cataloging status. -- Suppress Holds and Transit: item will not be used to fill holds or sent in transit. Item has Reshelving status. -- Amnesty Mode/Forgive Fines: overdue fines will be voided if already created or not be inserted if not yet created (e.g. hourly loans). -- Auto-Print Hold and Transit Slips: slips will be automatically printed without prompt for confirmation. - -These options may be selected simultaneously. The selected option is displayed in the header area. - -image::media/checkin_options.png[] - -==================================================== - -Renewal and Editing the Item's Due Date -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -Checked-out items can be renewed if your library's policy allows it. The new due date is calculated from the renewal date. Existing loans can also be extended to a specific date by editing the due date or renewing with a specific due date. - -Renewing via a Patron's Account -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -1) Retrieve the patron record and go to the *Items Out* screen. - -image::media/items_out_click.png[] - -2) Select the item you want to renew. *Click on Actions for Selected Items* -> *Renew*. If you want to renew all items in the account, click *Renew All* instead. - -image::media/renew_action.png[] - -3) If you want to specify the due date, click *Renew with Specific Due Date*. You will be prompted to select a due date. Once done, click *Apply*. - -image::media/renew_specific_date.png[] - -[TIP] -Renewal can also be done on the *Item Status* screen. See the section called <> for more information. - -Renewing by Item Barcode -^^^^^^^^^^^^^^^^^^^^^^^^ -1) To renew items by barcode, select *Circulation* -> *Renew Items* or press *CTRL-F2*. - -2) Scan or manually entire the item barcode. - -image::media/renew_item.png[] - -3) If you want to specify the due date, click *Specific Due Date* and select a new due date from the calendar. - -image::media/renew_item_calendar.png[] - -Editing Due Date -^^^^^^^^^^^^^^^^ - -1) Retrieve the patron record and go to the *Items Out* screen. - -2) Select the item you want to renew. Click on *Actions for Selected Items* -> *Edit Due Date*. - -image::media/edit_due_date_action.png[] - -3) Select a new due date in the pop-up window, then click *Apply*. - -[TIP] -You can select multiple items by pressing down the CTRL key on your keyboard and clicking each items you want to edit. - -[NOTE] -Editing a due date is not included in the renewal count. - -Marking Items Lost and Claimed Returned -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -Lost Items -^^^^^^^^^^ -1) To mark items Lost, retrieve patron record and click *Items Out*. - -2) Select the item. Click on *Actions for Selected Items* -> *Mark Lost (by Patron)*. - -image::media/mark_lost.png[] - -3) The lost item now displays in the *Lost/Claimed Returned/Long Overdue, Has Unpaid Billings* section of the patron record. - -image::media/lost_cr_section.png[] - -4) The lost item also adds to the count of *Lost* items in the patron summary on the left (or top) of the screen. - -image::media/patron_summary_checkouts.jpg[] - -[NOTE] -Lost Item Billing -======================== -- Marking an item Lost will automatically bill the patron the replacement cost of the item as recorded in the price field in the item record, and a processing fee as determined by your local policy. If the lost item has overdue charges, the overdue charges may be voided or retained based on local policy. -- A lost-then-returned item will disappear from the Items Out screen only when all bills linked to this particular circulation have been resolved. Bills may include replacement charges, processing fees, and manual charges added to the existing bills. -- The replacement fee and processing fee for lost-then-returned items may be voided if set by local policy. Overdue fines may be reinstated on lost-then-returned items if set by local policy. -========================== - -Refunds for Lost Items -^^^^^^^^^^^^^^^^^^^^^^^ - -If an item is returned after a lost bill has been paid and the library's policy is to void the replacement fee for lost-then-returned items, there will be a negative balance in the bill. A refund needs to be made to close the bill and the circulation record. Once the outstanding amount has been refunded, the bill and circulation record will be closed and the item will disappear from the Items Out screen. - -If you need to balance a bill with a negative amount and close the linked lost circulation record without making a refund (removing the item from the *Lost, Claimed Returned, Long Overdue, Has Unpaid Bills* panel on the *Items Out* screen), you need to add two dummy bills to the existing bills. The first one can be of any amount (e.g. $0.01), while the second should be of the absolute value of the negative amount. Then you need to void the first dummy bill. The reason for using a dummy bill is that Evergreen will check and close the circulation record only when payment is applied or bills are voided. - -Claimed Returned Items -^^^^^^^^^^^^^^^^^^^^^^^ - -1) To mark an item Claimed Returned, retrieve the patron record and go to the *Items Out* screen. - -2) Select the item, then select *Actions for Selected Items* -> *Mark Claimed Returned* from the dropdown menu. - -image::media/mark_claims_returned.png[] - -3) Select a date and click *Apply*. - -image::media/claimed_date.png[] - -4) The Claimed Returned item now displays in the *Lost/Claimed Returned/Long Overdue, Has Unpaid Billings* section of the patron record. - -image::media/lost_cr_section.png[] - -5) The Claimed Returned item adds to the count of Check Outs that are Claimed Returned in the patron summary on the left (or top) of the screen. It also adds to the total *Claims-returned Count* (including those that are current Check Outs and those that have since been returned) that is displayed when editing the patron's record. - -image::media/patron_summary_checkouts.jpg[] - -[NOTE] -More on Claimed Returned Items -==================================== -- The date entered for a Claimed Returned item establishes the fine. If the date given has passed, bills will be adjusted accordingly. -- When a Claimed Returned item is returned, if there is an outstanding bill associated with it, the item will not disappear from the *Items Out* screen. It will disappear when the outstanding bills are resolved. -- When an item is marked Claimed Returned, the value in *Claims-returned Count* field in the patron record is automatically increased. Staff can manually adjust this count by editing the patron record. -==================================== - -In-house Use (F6) -~~~~~~~~~~~~~~~~~ -1) To record in-house use, select *Circulation* -> *Record-In House Use*, click *Check Out* -> *Record In-House Use* on the circulation toolbar , or press *F6*. - -image::media/record_in_house_action.png[] - -2) To record in-house use for cataloged items, enter number of uses, scan barcode or type barcode and click *Submit*. - -image::media/in_house_use.png[] - -[NOTE] -The statistics of in-house use are separated from circulation statistics. The in-house use count of cataloged items is not included in the items' total use count. - -[[itemstatus]] -Item Status (F5) -~~~~~~~~~~~~~~~~ - -The Item Status screen is very useful. Many actions can be taken by either circulation staff or catalogers on this screen. Here we will cover some circulation-related functions, namely checking item status, viewing past circulations, inserting item alert messages, marking items missing or damaged, etc. - -Checking item status -^^^^^^^^^^^^^^^^^^^^ - -1) To check the status of an item, select *Search* -> *Search for copies by Barcode* or *Circulation* -> *Show Item Status by Barcode*; click the *Item Status button* on the circulation or cataloging toolbar; or press *F5*. - -image::media/item_status_menu.png[] - -2) Scan the barcode or type it and click *Submit*. The current status of the item is displayed with selected other fields. You can use the column picker to select more fields to view. - -image::media/item_status_barcode.png[] - -3) Click the *Alternate View* button, and the item summary and circulation history will be displayed. - -image::media/item_status_altview.png[] - -4) Click *List View* to go back. - -image::media/item_status_list_view.png[] - -[NOTE] -If the item's status is "Available", the displayed due date refers to the previous circulation's due date. - -[TIP] -Upload From File allows you to load multiple items saved in a file on your local computer. The file contains a list of the barcodes in text format. To ensure smooth uploading and further processing on the items, it is recommended that the list contains no more than 100 items. - -Viewing past circulations -^^^^^^^^^^^^^^^^^^^^^^^^^^ -1) To view past circulations, retrieve the item on the *Item Status* screen as described above. - -2) Select *Actions for Selected Items* -> *Show Last Few Circulations*. - -image::media/last_few_circs_action.png[] - -3) The item's recent circulation history is displayed. - -image::media/last_few_circs_display.png[] - -4) To retrieve the patron(s) of the last circulations, click the *Retrieve Last Patron* or the *Retrieve All These Patrons* button at the bottom of the above screen. Patron record(s) will be displayed in new tab(s). - -[TIP] -The number of items that displays in the circulation history can be set in Local *Administration* -> *Library Settings Editor*. - -[NOTE] -You can also retrieve the past circulations on the patron's Items Out screen and from the Check In screen. - -Marking items damaged or missing and other functions -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -1) To mark items damaged or missing, retrieve the item on the *Item Status* screen. - -2) Select the item. Click on *Actions for Selected Items* -> *Mark Item Damaged* or *Mark Item Missing*. - -image::media/mark_missing_damaged.png[] - -[NOTE} -Depending on the library's policy, when marking an item damaged, bills (cost and/or processing fee) may be inserted into the last borrower's account. - -3) Following the above procedure, you can check in and renew items by using the *Check in Items* and *Renew Items* on the dropdown menu. - -Item alerts -^^^^^^^^^^^ - -The *Edit Item Attributes* function on the *Actions for Selected Items* dropdown list allows you to edit item records. Here, we will show you how to insert item alert messages by this function. See cataloging instructions for more information on item editing. -1) Retrieve record on *Item Status* screen. - -2) Once item is displayed, highlight it and select *Actions for Selected Items* -> *Edit Item Attributes*. - -3) The item record is displayed in the *Copy Editor*. - -image::media/copy_edit_alert.png[] - -4) Click *Alert Message* in the *Miscellaneous* column. The background color of the box changes. Type in the message then click *Apply*. - -image::media/copy_alert_message.png[] - -5) Click *Modify Copies*, then confirm the action. diff --git a/development/README b/development/README deleted file mode 100644 index e69de29bb2..0000000000 diff --git a/development/updating_translations_launchpad.txt b/development/updating_translations_launchpad.txt deleted file mode 100644 index dc57f3490c..0000000000 --- a/development/updating_translations_launchpad.txt +++ /dev/null @@ -1,54 +0,0 @@ -Updating translations using Launchpad -===================================== - -This document describes how to update the translations in an Evergreen branch -by pulling them from Launchpad, as well as update the files to be translated -in Launchpad by updating the POT files in the Evergreen master branch. - -Prerequisites -------------- -You must install all of the Python prerequisites required for building -translations, per -http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-admin:customizations:i18n - -* https://bitbucket.org/izi/polib/wiki/Home[polib] -* http://translate.sourceforge.net[translate-toolkit] -* http://pypi.python.org/pypi/python-Levenshtein/[levenshtein] -* http://pypi.python.org/pypi/setuptools[setuptools] -* http://pypi.python.org/pypi/simplejson/[simplejson] -* http://lxml.de/[lxml] - -Updating the translations -------------------------- - -. Check out the latest translations from Launchpad by branching the Bazaar -repository: -+ -[source,bash] ------------------------------------------------------------------------------- -bzr branch lp:~denials/evergreen/translation-export ------------------------------------------------------------------------------- -+ -This creates a directory called "translation-export". -+ -. Ensure you have an updated Evergreen release branch. -. Run the `build/i18n/scripts/update_pofiles` script to copy the translations - into the right place and avoid any updates that are purely metadata (dates - generated, etc). -. Commit the lot! And backport to whatever release branches need the updates. -. Build updated POT files: -+ -[source,bash] ------------------------------------------------------------------------------- -cd build/i18n -make newpot ------------------------------------------------------------------------------- -+ -This will extract all of the strings from the latest version of the files in -Evergreen. -+ -. (This part needs automation): Then, via the magic of `git diff` and `git add`, -go through all of the changed files and determine which ones actually have -string changes. Recommended approach is to re-run `git diff` after each -`git add`. -. Commit the updated POT files and backport to the pertinent release branches. diff --git a/docs/RELEASE_NOTES_2_2.txt b/docs/RELEASE_NOTES_2_2.txt index 7d1c3f325f..e382742875 100644 --- a/docs/RELEASE_NOTES_2_2.txt +++ b/docs/RELEASE_NOTES_2_2.txt @@ -102,8 +102,10 @@ and deprecate the use of the JSPAC. Auto Suggest in Catalog Search ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -The auto suggest feature suggests the completion of search terms as the user -enters his query. By default, the user will see ten suggestions although this +The +http://docs.evergreen-ils.org/2.2/_auto_suggest_in_catalog_search_2.html[auto +suggest feature] suggests the completion of search terms as the user enters his +query. By default, the user will see ten suggestions although this number is configurable at the database level. Scroll through suggestions with your mouse, or use the arrow keys to scroll through the suggestions. Select a suggestion to view records that are linked to this suggestion. @@ -111,9 +113,6 @@ suggestion to view records that are linked to this suggestion. This feature is not turned on by default. You must turn it on in the Admin module. -Documentation for this feature is available in the Book of Evergreen -at http://docs.evergreen-ils.org/2.2/ - Copy Location Groups ^^^^^^^^^^^^^^^^^^^^ This feature allows staff to create and name sets of copy locations to use as diff --git a/docs/acquisitions/introduction.txt b/docs/acquisitions/introduction.txt new file mode 100644 index 0000000000..4680506820 --- /dev/null +++ b/docs/acquisitions/introduction.txt @@ -0,0 +1,25 @@ +Acquisitions +------------ + +This section is intended for those who are responsible for managing and processing acquisitions. + +Before beginning to use Acquisitions, the following must be configured by an administrator: + +* Cancel/Suspend Reasons (optional) +* Claiming (optional) +* Currency Types (defaults exist) +* Distribution Formulas (optional) +* EDI Accounts (optional) (see link:../installation/edi_setup.txt[Setting Up EDI Acquisitions] under Software Installation) +* Exchange Rates (defaults exist) +* Funds and Fund Sources +* Invoice Types (defaults exist) and Invoice Payment Methods +* Line Item Features (optional) +* Merge Overlay Profiles and Record Match Sets (see link:../cataloging/batch_importing_MARC.txt[Batch Importing MARC Records] in Cataloging) +* Providers + +Acquisitons Workflow +~~~~~~~~~~~~~~~~~~~~ + +The following diagram shows how the workflow functions in Evergreen. One of the differences in this process you should notice is that when creating a selection list on the vendor site, libraries will be downloading and importing the vendor bibs and item records. + +image::media/acq_workflow.jpg[workflow diagram] diff --git a/docs/acquisitions/receive_items_from_invoice.txt b/docs/acquisitions/receive_items_from_invoice.txt new file mode 100644 index 0000000000..8c0adca25b --- /dev/null +++ b/docs/acquisitions/receive_items_from_invoice.txt @@ -0,0 +1,73 @@ +Receive Items From an Invoice +----------------------------- + +This feature enables users to receive items from an invoice. Staff can receive individual copies, or they can receive items in batch. + +Receive Items in Batch (List Mode) +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +In this example, we have created a purchase order, added line items and copies, and activated the purchase order. We will create an invoice from the purchase order, receive items, and invoice them. We will receive the items in batch from the invoice. + +1) Retrieve a purchase order. + +2) Click *Create Invoice*. + +image::media/Receive_Items_From_an_Invoice1.jpg[Receive_Items_From_an_Invoice1] + +3) The blank invoice appears. In the top half of the invoice, enter descriptive information about the invoice. In the bottom half of the invoice, enter the number of items for which you were invoiced, the amount that you were billed, and the amount that you paid. + + +image::media/Receive_Items_From_an_Invoice2.jpg[Receive_Items_From_an_Invoice2] + + +4) Click *Save*. You must choose a save option before you can receive items. + + +5) The screen refreshes. In the top right corner of the screen, click *Receive Items*. + + +6) The *Acquisitions Invoice Receiving* screen opens. By default, this screen enables users to receive items in batch, or *Numeric Mode*. You can select the number of copies that you want to receive; you are not receiving specific copies in this mode. + + +7) Select the number of copies that you want to receive. By default, the number that you invoiced will appear. In this example, we will receive one copy of each title. + + +NOTE: You cannot receive fewer items than 0 (zero) or more items than the number that you ordered. + + +8) Click *Receive Selected Copies*. + + +image::media/Receive_Items_From_an_Invoice4.jpg[Receive_Items_From_an_Invoice4] + + +9) When you are finished receiving items, close the screen. You can repeat this process as you receive more copies. + + + +Receive Specific Copies (Numeric Mode) +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +In this example, we have created a purchase order, added line items and copies, and activated the purchase order. We will create an invoice from the purchase order, receive items, and invoice them. We will receive specific copies from the invoice. This function may be useful to libraries who purchase items that have been barcoded by their vendor. + + +1) Complete steps 1-5 in the previous section. + +2) The *Acquisitions Invoice Receiving* screen by default enables user to receive items in batch, or *Numeric Mode*. Click *Use List Mode* to receive specific copies. + +3) Select the check boxes adjacent to the copies that you want to receive. Leave unchecked the copies that you do not want to receive. + +4) Click *Receive Selected Copies*. + +image::media/Receive_Items_From_an_Invoice5.jpg[Receive_Items_From_an_Invoice5] + + +The screen will refresh. Copies that have not yet been received remain on the screen so that you can receive them when they arrive. + + +5) When all copies on an invoice have been received, a message confirms that no copies remain to be received. + +6) The purchase order records that all items have been received. + +image::media/Receive_Items_From_an_Invoice7.jpg[Receive_Items_From_an_Invoice7] + diff --git a/docs/acquisitions/selection_lists_po.txt b/docs/acquisitions/selection_lists_po.txt new file mode 100644 index 0000000000..e308d056cc --- /dev/null +++ b/docs/acquisitions/selection_lists_po.txt @@ -0,0 +1,136 @@ +Selection Lists and Purchase Orders +----------------------------------- + +Selection Lists +~~~~~~~~~~~~~~~ + +Selection lists allow you to create, manage, and save lists of items that you may want to purchase. To view your selection list, click Acquisitions -> My Selection Lists. Use the general search to view selection lists created by other users. + +Create a selection list +^^^^^^^^^^^^^^^^^^^^^^^ + +Selection lists can be created in four areas within the module. Selection lists can be created when you link:brief_records.txt[Add Brief Records], Upload MARC Order Records, or find records through the link:federated.txt[MARC Federated Search]. In each of these interfaces, you will find the Add to Selection List field. Enter the name of the selection list that you want to create in that field. + +Selection lists can also be created through the My Selection Lists interface: + +. Click Acquisitions -> My Selection Lists. +. Click the New Selection List drop down arrow. +. Enter the name of the selection list in the box that appears. +. Click Create. + +image::media/acq_selection_create.png[create selection list] + +Add items to a selection list +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +You can add items to a selection list in one of three ways: link:brief_records.txt[add a brief record]; upload MARC order records; add records through a link:federated.txt[federated search]; or use the link:federated.txt[View/Place Orders] menu item in the catalog. + +Clone selection lists +^^^^^^^^^^^^^^^^^^^^^ + +Cloning selection lists enables you to copy one selection list into a new selection list. You can maintain both copies of the list, or you can delete the previous list. + +. Click Acquisitions -> My Selection Lists. +. Check the box adjacent to the list that you want to clone. +. Click Clone Selected. +. Enter a name into the box that appears, and click Clone. + +image::media/acq_selection_clone.png[clone selection list] + +Merge selection lists +^^^^^^^^^^^^^^^^^^^^^ + +You can merge two or more selection lists into one selection list. + + +. Click Acquisitions -> My Selection Lists. +. Check the boxes adjacent to the selection lists that you want to merge, and click Merge Selected. +. Choose the Lead Selection List from the drop down menu. This is the list to which the items on the other list(s) will be transferred. +. Click Merge. + +image::media/acq_selection_merge.png[merge selection list] + +Delete selection lists +^^^^^^^^^^^^^^^^^^^^^^ + +You can delete selection lists that you do not want to save. You will not be able to retrieve these items through the General Search after you have deleted the list. You must delete all line items from a selection list before you can delete the list. + + +. Click Acquisitions -> My Selection Lists. +. Check the box adjacent to the selection list(s) that you want to delete. +. Click Delete Selected. + +Mark Ready for Selector +^^^^^^^^^^^^^^^^^^^^^^^ + +After an item has been added to a selection list or purchase order, you can mark it ready for selector. This step is optional but may be useful to individual workflows. + + +. If you want to mark part of a selection list ready for selector, then you can check the box(es) of the line item(s) that you wish to mark ready for selector. If you want to mark the entire list ready for selector, then skip to step 2. +. Click Actions -> Mark Ready for Selector. +. A pop up box will appear. Choose to mark the selected line items or all line items. +. Click Go. +. The screen will refresh. The marked line item(s) will be highlighted pink, and the status changes to selector~ready. + +image::media/acq_selection_mark_ready.png[mark ready] + +Convert selection list to purchase order +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +Use the Actions menu to convert a selection list to a purchase order. + + +. From a selection list, click Actions ~> Create Purchase Order. +. A pop up box will appear. +. Select the ordering agency from the drop down menu. +. Enter the provider. +. Check the box adjacent to prepayment required if prepayment is required. +. Choose if you will add All Lineitems or Selected Lineitems to your purchase order. +. Check the box if you want to Import Bibs and Create Copies in the catalog. +. Click Submit. + +Brief Records +~~~~~~~~~~~~~ + +Brief records are short bibliographic records with minimal information that are often used as placeholder records until items are received. Brief records can be added to selection lists or purchase orders and can be imported into the catalog. You can add brief records to new or existing selection lists. You can add brief records to new, pending or on~order purchase orders. + +Add brief records to a selection list +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +. Click Acquisitions -> New Brief Record. You can also add brief records to an existing selection list by clicking the Actions menu on the selection list and choosing Add Brief Record. +. Choose a selection list from the drop down menu, or enter the name of a new selection list. +. Enter bibliographic information in the desired fields. +. Click Save Record. + +image::media/acq_brief_record.png[] + +Add brief records to purchase orders +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +You can add brief records to new or existing purchase orders. + +. Open or create a purchase order. See the section on link:03~PO.txt[purchase orders] for more information. +. Click Add Brief Record. +. Enter bibliographic information in the desired fields. Notice that the record is added to the purchase order that you just created. +. Click Save Record. + +image::media/acq_brief_record-2.png[] + +MARC Federated Search +~~~~~~~~~~~~~~~~~~~~~ + +The MARC Federated Search enables you to import bibliographic records into a selection list or purchase order from a Z39.50 source. + +. Click Acquisitions -> MARC Federated Search. +. Check the boxes of Z39.50 services that you want to search. Your local Evergreen Catalog is checked by default. Click Submit. ++ +---- +image::media/acq_marc_search.png[search form] +---- ++ +. A list of results will appear. Click the "Copies" link to add copy information to the line item. See the link:line_items.txt[section on Line Items] for more information. +. Click the Notes link to add notes or line item alerts to the line item. See the link:line_items.txt[section on Line Items] for more information. +. Enter a price in the "Estimated Price" field. +. You can save the line item(s) to a selection list by checking the box on the line item and clicking Actions -> Save Items to Selection List. You can also create a purchase order from the line item(s) by checking the box on the line item and clicking Actions ~> Create Purchase Order. + +image::media/acq_marc_search-2.png[line item] diff --git a/docs/acquisitions/vandelay_acquisitions_integration.txt b/docs/acquisitions/vandelay_acquisitions_integration.txt new file mode 100644 index 0000000000..51fc2fa472 --- /dev/null +++ b/docs/acquisitions/vandelay_acquisitions_integration.txt @@ -0,0 +1,69 @@ +Vandelay Integration into Acquisitions +-------------------------------------- +The Acquisitions Load MARC Order Record interface enables you to add MARC records to selection lists and purchase orders and upload the records into the catalog. The Vandelay interface enables you to create specific match points between incoming MARC records and exisiting catalog records. Combining these two features enables you to track on order MARC records through the Acquisitions interface and to utilize the record matching mechanisms available in Vandelay. + +The purpose of this documentation is to describe the interaction between Vandelay and the Acquisitions MARC Batch Upload interface. For detailed instructions on + using the Acquisitions MARC Batch Upload interface, see the Evergreen Documentation Interest Group's Book of Evergreen, 2.1 documentation, Chapter 5, Load MARC +Order Records. For detailed instructions on using the Vandelay functions for record matching and importing, see the Evergreen Documentation Interest Group's Book of Evergreen, +2.2 documentation, Chapter 7, Batch Importing MARC Records. + +*Use Cases for Vandelay Integration into Acquisitions* + +You can add items to a selection list or purchase order and ignore the Vandelay options, or you can use both acquisitions and cataloging functions. In these examples, you will use both functions. + +Example 1: Using the Acquisitions MARC Batch Load interface, upload MARC records to a selection list and a Vandelay queue, and match queued records with existing catalog records. + +In this example, an acquisitions librarian has received a batch of MARC records from a vendor. She will add the records to a selection list and a Vandelay record queue. +A cataloger will later view the queue, edit the records, and import them into the catalog. + +. Click *Acquisitions -> Load MARC Order Records* +. Add MARC order records to a *Selection list* and/or a *Purchase Order.* Check the box to create a purchase order if desired. +. Select a *Provider* from the drop down menu, or begin typing the code for the provider, and the field will auto-fill. +. Select a *Context Org Unit* from the drop down menu, or begin typing the code for the context org unit, and the field will auto-fill. +. Select a *Selection List* from the drop down menu, or begin typing the name of the selection list. You can create a new list, or the field will auto-fill. +. Create a new record queue in Vandelay, or upload the records to an existing queue. +. Select a *Record Match Set*. +. Browse your computer to find the MARC file, and click *Upload*. ++ +image::media/Vandelay_Integration_into_Acquisitions1.jpg[Vandelay_Integration_into_Acquisitions1] ++ +. The processed items appear at the bottom of the screen. ++ +image::media/Vandelay_Integration_into_Acquisitions2.jpg[Vandelay_Integration_into_Acquisitions2] +. You can click the link(s) to access the selection list or the import queue. Click the link to *View Selection List*. +. Look at the first line item. The line item has not yet been linked to the catalog, but it is linked to a Vandelay record queue. Click the link to the *queue* to examine the MARC record. ++ +image::media/Vandelay_Integration_into_Acquisitions3.jpg[Vandelay_Integration_into_Acquisitions3] +. The Vandelay interface opens in a new tab. The bibliographic records appear in the queue. Records that have matches are identified in the queue. You can edit these records and/or import them into the catalog, completing the process. + +image::media/Vandelay_Integration_into_Acquisitions4.jpg[Vandelay_Integration_into_Acquisitions4] + +Example 2: Using the Acquisitions MARC Batch Load interface, upload MARC records to a selection list, and use the Vandelay options to import the records directly into the catalog. The Vandelay options will enable you to match incoming records with existing catalog records. + +In this example, a librarian will add MARC records to a selection list, create criteria for matching incoming and existing records, and import the matching and non-matching records into the catalog. + +. Click *Acquisitions* -> *Load MARC Order Records* +. Add MARC order records to a *Selection list* and/or a *Purchase Order.* Check the box to create a purchase order if desired. +. Select a *Provider* from the drop down menu, or begin typing the code for the provider, and the field will auto-fill. +. Select a *Context Org Unit* from the drop down menu, or begin typing the code for the context org unit, and the field will auto-fill. +. Select a *Selection List* from the drop down menu, or begin typing the name of the selection list. You can create a new list, or the field will auto-fill. +. Create a new record queue in Vandelay, or upload the records to an existing queue. +. Select a *Record Match Set*. +. Select *Merge Profile* -> *Match-Only Merge*. +. Check the box adjacent to *Merge on Best Match*. +. Browse your computer to find the MARC file, and click *Upload*. ++ +image::media/Vandelay_Integration_into_Acquisitions5.jpg[Vandelay_Integration_into_Acquisitions5] ++ +. Click the link to *View Selection List* Line items that do not match existing catalog records on title and ISBN contain the link, *link to catalog*. This link indicates that you could link the line item to a catalog record, but currently, no match exists between the line item and catalog records. Line items that do have matching records in the catalog contain the link, *catalog*. ++ +image::/media/Vandelay_Integration_into_Acquisitions6.jpg[Vandelay_Integration_into_Acquisitions6] ++ +. Click the *catalog* link to view the line item in the catalog. + +*Permissions to use this Feature* + +IMPORT_MARC - Using Vandelay to create new bib records now requres the IMPORT_MARC +permission (same as open-ils.cat.biblio.record.xml.import). If the permission fails, the queued record will fail import and be stamped with a new "import.record.perm_failure" vandelay import error + +IMPORT_ACQ_LINEITEM_BIB_RECORD_UPLOAD - This allows interfaces leveraging Vandelay, such as Acquisitions, to create a higher barrier to entry. This permission prevents users from creating new bib records directly from the ACQ vendor MARC file upload interface. diff --git a/docs/admin/SMS_messaging.txt b/docs/admin/SMS_messaging.txt new file mode 100644 index 0000000000..94447002b2 --- /dev/null +++ b/docs/admin/SMS_messaging.txt @@ -0,0 +1,122 @@ +SMS Text Messaging +------------------ + +The SMS Text Messaging feature enables users to receive hold notices via text message. Users can opt-in to this hold notification as their default setting for all holds, or they +can receive specific hold notifications via text message. Users can also send call numbers and copy locations via text message. + +Administrative Setup +~~~~~~~~~~~~~~~~~~~~ + +You cannot receive text messages from Evergreen by default. You must enable this feature to receive hold notices and copy information from Evergreen via text message. + +Enable Text Messages +^^^^^^^^^^^^^^^^^^^^ + +. Click *Admin* -> *Local Admin* -> *Library Settings Editor.* +. Select the setting, *Enable features that send SMS text messages.* +. Set the value to *True,* and click *Update Setting.* + +image::media/SMS_Text_Messaging1.jpg[SMS_Text_Messaging1] + +Authenticate Patrons +^^^^^^^^^^^^^^^^^^^^ + +By default, you must be logged into your OPAC account to send a text message from Evergreen. However, if you disable this setting, you can text message copy information without having +to login to your OPAC account. + +To disable the patron login requirmement: + +. Click *Admin* -> *Local Administration* -> *Library Settings Editor.* +. Select the setting, *Disable auth requirement for texting call numbers*. +. Set the value to *True,* and click *Update Setting.* + +image::media/SMS_Text_Messaging2.jpg[SMS_Text_Messaging2] + +Configure SMS Carriers +^^^^^^^^^^^^^^^^^^^^^^ + +A list of SMS carriers that can transmit text messages to users is available in the staff client. Library staff can edit this list, or add new carriers. + +To add or edit SMS carriers: + +. Click *Admin* -> *Server Administration* -> *SMS Carriers*. +. To add a new carrier, click the *New Carrier* button in the top right corner of the screen. To edit an existing carrier, double click in any white space in the carrier's row. ++ +image::media/SMS_Text_Messaging3.jpg[SMS_Text_Messaging3] ++ +. Enter a (geographical) *Region*. +. Enter the carrier's *Name*. +. Enter an *Email Gateway.* The SMS carrier can provide you with the content for this field. The $number field is converted to the user's phone number when the text message is generated. +. Check the *Active* box to use this SMS Carrier. + +image::media/SMS_Text_Messaging4.jpg[SMS_Text_Messaging4] + +Configure Text Message Templates +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +Library staff control the content and format of text messages through the templates in Notifications/Action Triggers. Patrons cannot add free text to their text messages. + +To configure the text of the SMS text message: + +. Click *Admin* -> *Local Administration* -> *Notifications/Action Triggers.* +. Create a new A/T and template, or use or modify an existing template. For example, a default template, "Hold Ready for Pickup SMS Notification," notifies users that the hold is ready for pickup. ++ +image::media/SMS_Text_Messaging5.jpg[SMS_Text_Messaging5] ++ +. You can use the default template, or you can edit the template and add content specific to your library. Click the hyperlinked name to view and/or edit the hold notice. + +image::media/SMS_Text_Messaging6.jpg[SMS_Text_Messaging6] + +Receiving Holds Notices via Text Message +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +You can receive notification that your hold is ready for pickup from a text message that is sent to your mobile phone. + +. Login to your account. ++ +image::media/SMS_Text_Messaging12.jpg[SMS_Text_Messaging12] ++ +. Search the catalog. +. Retrieve a record, and click the *Place Hold* link. +. Select the option to retrieve hold notification via text message. +. Choose an SMS Carrier from the drop down menu. NOTE: You can enter your SMS carrier and phone number into your *Account Preferences* to skip steps five and six. +. Enter a phone number. +. Click *Submit.* + +image::media/SMS_Text_Messaging13.jpg[SMS_Text_Messaging13] + +Sending Copy Locations via Text Message +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + + +You can search the catalog for an item, and, after retrieving results for the item, click a hyperlink to send the copy location in a text message. + +. Login to your account in the OPAC. NOTE: If you have disabled the setting that requires patron login, then you do not have to login to their accounts to send text messages. +See *Administrative Setup* for more information. ++ +image::media/SMS_Text_Messaging7.jpg[SMS_Text_Messaging7] ++ +. Search the catalog, and retrieve a title with copies. +. Click the *Text* link adjacent to the call number. ++ +image::media/SMS_Text_Messaging8.jpg[SMS_Text_Messaging8] ++ +. The text of the SMS Text Message appears. ++ +image::media/SMS_Text_Messaging9.jpg[SMS_Text_Messaging9] ++ +. Choose an SMS Carrier from the drop down menu. NOTE: You can enter your SMS carrier and phone number into your *Account Preferences* to skip steps five and six. +. Enter a phone number. ++ +image::media/SMS_Text_Messaging10.jpg[SMS_Text_Messaging10] ++ +. Click *Submit*. +. The number and carrier are converted to an email address, and the text message is sent to your mobile phone. + +image::media/SMS_Text_Messaging11.jpg[SMS_Text_Messaging11] + +*Permissions to use this Feature* + +ADMIN_SMS_CARRIER - Enables users to add/create/delete SMS Carrier entries. + + diff --git a/docs/admin/acquisitions_admin.txt b/docs/admin/acquisitions_admin.txt new file mode 100644 index 0000000000..de4e329213 --- /dev/null +++ b/docs/admin/acquisitions_admin.txt @@ -0,0 +1,490 @@ +Acquisitions Administration +--------------------------- + +Acquisitions Permissions in the Admin module +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Several setting in the Library Settings area of the Admin module pertain to functions in the Acquisitions module. You can access these settings by clicking _Admin -> Local Administration ->Library Settings Editor_. + +* CAT: Delete bib if all copies are deleted via Acquisitions lineitem cancellation - If you cancel a line item, then all of the on order copies in the catalog are deleted. If, when you cancel a line item, you also want to delete the bib record, then set this setting to TRUE. +* Default circulation modifier - This modifier would be applied to items that are created in the acquisitions module +* Default copy location - This copy location would be applied to items that are created in the acquisitions module +* Fund Spending Limit for Block - When the amount remaining in the fund, including spent money and encumbrances, goes below this percentage, attempts to spend from the fund will be blocked. +* Fund Spending Limit for Warning - When the amount remaining in the fund, including spent money and encumbrances, goes below this percentage, attempts to spend from the fund will result in a warning to the staff. +* Temporary barcode prefix - Temporary barcode prefix for items that are created in the acquisitions module +* Temporary call number prefix - Temporary call number prefix for items that are created in the acquisitions module + +Cancel/Suspend reasons +~~~~~~~~~~~~~~~~~~~~~~ + +The Cancel reasons link enables you to predefine the reasons for which a line item or a PO can be cancelled. A default list of reasons appears, but you can add custom reasons to this list. Applying the cancel reason will prevent the item from appearing in a claims list and will allow you to cancel debits associated with the purchase. Cancel reasons also enable you to suspend or delay a purchase. For example, you could create a cancel reason of 'back ordered,' and you could choose to keep the debits associated with the purchase. + +Create a cancel/suspend reason +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +. To add a new cancel reason, click _Administration -> Server Administration -> Acquisitions -> Cancel reasons_. + +. Click _New Cancel Reason_. + +. Select a using library from the drop down menu. The using library indicates the organizational units whose staff can use this cancel reason. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units.) + +. Create a label for the cancel reason. This label will appear when you select a cancel reason on an item or a PO. + +. Create a description of the cancel reason. This is a free text field and can be comprised of any text of your choosing. + +. If you want to retain the debits associated with the cancelled purchase, click the box adjacent to Keep Debits-> + +. Click _Save_. + +Claiming +~~~~~~~~ +Currently, all claiming is manual, but the admin module enables you to build claim policies and specify the action(s) that users should take to claim items. + +Create a claim policy +^^^^^^^^^^^^^^^^^^^^^ + +The claim policy link enables you to name the claim policy and specify the organization that owns it. + +. To create a claim policy, click _Admin -> Server Administration -> Acquisitions -> Claim Policies_. +. Create a claim policy name. No limits exist on the number of characters that can be entered in this field. +. Select an org unit from the drop down menu. The org unit indicates the organizational units whose staff can use this claim policy. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units). ++ +[NOTE] +The rule of parental inheritance applies to this list. ++ +. Enter a description. No limits exist on the number of characters that can be entered in this field. +. Click _Save_. + +Create a claim type +^^^^^^^^^^^^^^^^^^^ + +The claim type link enables you to specify the reason for a type of claim. + +. To create a claim type, click _Admin -> Server Administration -> Acquisitions -> Claim types_. +. Create a claim type. No limits exist on the number of characters that can be entered in this field. +. Select an org unit from the drop down menu. The org unit indicates the organizational units whose staff can use this claim type. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units). ++ +[NOTE] +The rule of parental inheritance applies to this list. ++ +. Enter a description. No limits exist on the number of characters that can be entered in this field. +. Click _Save_. + +Create a claim event type +^^^^^^^^^^^^^^^^^^^^^^^^^ + +The claim event type describes the physical action that should occur when an item needs to be claimed. For example, the user should notify the vendor via email that the library is claiming an item. + +. To access the claim event types, click _Admin -> Server Administration -> Acquisitions ->Claim event type_. +. Enter a code for the claim event type. No limits exist on the number of characters that can be entered in this field. +. Select an org unit from the drop down menu. The org unit indicates the organizational units whose staff can use this event type. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units). ++ +[NOTE] +The rule of parental inheritance applies to this list. ++ +. Enter a description. No limits exist on the number of characters that can be entered in this field. +. If this claim is initiated by the user, then check the box adjacent to Library Initiated. ++ +[NOTE] +Currently, all claims are initiated by a user. The ILS cannot automatically claim an issue. ++ +. Click _Save_. + +Create a claim policy action +^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +The claim policy action enables you to specify how long a user should wait before claiming the item. + +. To access claim policy actions, click _Admin -> Server Administration -> Acquisitions ->Claim Policy Actions_. + +. Select an Action (Event Type) from the drop down menu. + +. Enter an action interval. This field indicates how long a user should wait before claiming the item. + +. In the Claim Policy ID field, select a claim policy from the drop down menu. + +. Click _Save_. + +[NOTE] +You can create claim cycles by adding multiple claim policy actions to a claim policy. + +Currency Types +~~~~~~~~~~~~~~ + +Currency types can be created and applied to funds in the administrative module. When a fund is applied to a copy or line item for purchase, the item will be purchased in the currency associated with that fund. + +Create a currency type +^^^^^^^^^^^^^^^^^^^^^^ + +. To create a new currency type, click _Admin -> Server Administration -> Acquisitions -> Currency types_. + +. Enter the currency code. No limits exist on the number of characters that can be entered in this field. + +. Enter the name of the currency type in Currency Label field. No limits exist on the number of characters that can be entered in this field. + +. Click Save. + +Edit a currency type +^^^^^^^^^^^^^^^^^^^^ + +. To edit a currency type, click your cursor in the row that you want to edit. The row will turn blue. + +. Double~click. The pop~up box will appear, and you can edit the fields. + +. After making changes, click Save. + +[NOTE] +From the currency types interface, you can delete currencies that have never been applied to funds or used to make purchases. + +Distribution Formulas +~~~~~~~~~~~~~~~~~~~~~ + +Distribution formulas allow you to specify the number of copies that should be distributed to specific branches. You can create and reuse formulas as needed. + +Create a distribution formula +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +. Click _Admin -> Server Administration -> Acquisitions ->Distribution Formulas_. +. Click _New Formula_. +. Enter a Formula Name. No limits exist on the number of characters that can be entered in this field. +. Choose a Formula Owner from the drop down menu. The Formula Owner indicates the organizational units whose staff can use this formula. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units). ++ +[NOTE] +The rule of parental inheritance applies to this list. ++ +. Ignore the Skip Count field which is currently not used. +. Click _Save_. +. Click _New Entry_. +. Select an Owning Library from the drop down menu. This indicates the branch that will receive the items. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See _Admin -> Server Administration -> Organizational Units_). +. Select a Shelving Location from the drop down menu. +. In the Item Count field, enter the number of items that should be distributed to the branch. You can enter the number or use the arrows on the right side of the field. +. Click _Apply Changes_. The screen will reload. +. To view the changes to your formula, click Admin -> Server Administration -> Acquisitions -> Distribution Formulas. The item_count will reflect the entries to your distribution formula. + +[NOTE] +To edit the Formula Name, click the hyperlinked name of the formula in the top left corner. A pop up box will enable you to enter a new formula name. + +Edit a distribution formula +^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +To edit a distribution formula, click the hyperlinked title of the formula. + +EDI +~~~ +Many libraries use Electronic Data Interchange (EDI) accounts to order new acquisitions. Users can set up EDI accounts and manage EDI messages in the admin module. EDI messages and notes can be viewed in the acquisitions module. See also the link:../installation/edi_setup.txt[EDI Installation Instructions] because this is required for use of EDI. + +The following fields are required to create an EDI account: + +[NOTE] +host, username, password, path, and incoming directory. + +EDI Accounts +^^^^^^^^^^^^ + +Create EDI Accounts to communicate electronically with providers. + +. Create a label. The label allows you to differentiate between accounts for the same provider. No limits exist on the number of characters that can be entered in this field. +. Enter a host. Your provider will provide you with the requisite FTP or SCP information. +. Enter the username that has been supplied by your provider. +. Enter the password that has been supplied by your provider. +. Enter account information. This field enables you to add a supplemental password for entry to a remote system after log in has been completed. This field is optional for the ILS but may be required by your provider. +. Select an owner from the drop down menu. The owner indicates the organizational units whose staff can use this EDI account. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units). ++ +[NOTE] +The rule of parental inheritance applies to this list. ++ +. The Last Activity updates automatically with any inbound or outbound communication. +. Select a provider from the drop down menu to whom this account belongs. +. Enter a path. The path indicates the remote location on the server from which files are pulled in to the ILS. +. Enter the incoming directory. This directory indicates the location on your local network to which the files download. +. Enter the vendor account number supplied by your provider. +. Enter the vendor account code supplied by your provider. +. Click Save. + +EDI Messages +^^^^^^^^^^^^ + +The EDI messages screen displays all incoming and outgoing messages between the library and the vendor. + +Exchange Rates +~~~~~~~~~~~~~~ + +Exchange rates define the rate of exchange between currencies. Evergreen will automatically calculate exchange rates for purchases. Evergreen assumes that the currency of the purchasing fund is identical to the currency of the provider, but it provides for two unique situations: 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 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 accordingly. When money is transferred between funds that use different currency types, Evergreen will automatically use the exchange rate to convert the money to the currency of the receiving fund. During such transfers, however, staff can override the automatic conversion by providing an explicit amount to credit to the receiving fund. + +Create an exchange rate +^^^^^^^^^^^^^^^^^^^^^^^ + +. To create a new exchange rate, click _Admin -> Server Administration -> Acquisitions -> Exchange Rates_. + +. Click New Exchange Rate. + +. Enter the From Currency from the drop down menu populated by the currency types. + +. Enter the To Currency from the drop down menu populated by the currency types. + +. Enter the exchange Ratio. + +. Click _Save_. + +Edit an Exchange Rate +^^^^^^^^^^^^^^^^^^^^^ + +Edit an exchange rate just as you would edit a currency type. + +MARC Federated Search +~~~~~~~~~~~~~~~~~~~~~ + +The MARC Federated Search enables you to import bibliographic records into a selection list or purchase order from a Z39.50 source. + +. Click _Acquisitions -> MARC Federated Search_. +. Check the boxes of Z39.50 services that you want to search. Your local Evergreen Catalog is checked by default. Click Submit. ++ +image::media/acq_marc_search.png[search form] ++ +. A list of results will appear. Click the _Copies_ link to add copy information to the line item. See the link:line_items.txt[section on Line Items] for more information. +. Click the Notes link to add notes or line item alerts to the line item. See the link:line_items.txt[section on Line Items] for more information. +. Enter a price in the _Estimated Price_ field. +. You can save the line item(s) to a selection list by checking the box on the line item and clicking _Actions -> Save Items to Selection List_. You can also create a purchase order from the line item(s) by checking the box on the line item and clicking _Actions -> Create Purchase Order_. + +image::media/acq_marc_search-2.png[line item] + +Fund Tags +~~~~~~~~~ + +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 Children's CDs. Assign a fund tag of 'children's' to each fund. When you need to report on the amount that has been spent on all children's materials, you can run a report on the fund tag to find total expenditures on children's materials rather than reporting on each individual fund. + +Create a Fund Tag + +. To create a fund tag, click _Admin -> Server Administration -> Acquisitions -> Fund Tags_. +. Click _New Fund Tag_. No limits exist on the number of characters that can be entered in this field. +. Select a Fund Tag Owner from the drop down menu. The owner indicates the organizational unit(s) whose staff can use this fund tag. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units). ++ +[NOTE] +The rule of parental inheritance applies to this list. ++ +. Enter a Fund Tag Name. No limits exist on the number of characters that can be entered in this field. +. Click _Save_. + +Funding Sources +~~~~~~~~~~~~~~~ + +Funding sources allow you to specify the sources that contribute monies to your fund(s). You can create as few or as many funding sources as you need. These can be used to track exact ammounts for accounts in your general ledger. You can then use funds to track spending and purchases for specific collections. + +Create a funding source +^^^^^^^^^^^^^^^^^^^^^^^ + +. To create a new funding source, click _Admin -> Server Administration -> Acquisitions -> Funding Source_. +. Enter a funding source name. No limits exist on the number of characters that can be entered in this field. +. Select an owner from the drop down menu. The owner indicates the organizational unit(s) whose staff can use this funding source. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units). ++ +[NOTE] +The rule of parental inheritance applies to this list. For example, if a system is made the owner of a funding source, then users with appropriate permissions at the branches within the system could also use the funding source. ++ +. Create a code for the source. No limits exist on the number of characters that can be entered in this field. +. Select a currency from the drop down menu. This menu is populated from the choices in the Currency Types interface. +. Click _Save_. + +Allocate Credits to Funding Sources +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +. Apply a credit to this funding source. + +. Enter the amount of money that the funding source contributes to the organization. Funding sources are not tied to fiscal or calendar years, so you can continue to add money to the same funding source over multiple years, e.g. County Funding. Alternatively, you can name funding sources by year, e.g. County Funding 2010 and County Funding 2011, and apply credits each year to the matching source. + +. To apply a credit, click on the hyperlinked name of the funding source. The Funding Source Details will appear. + +. Click _Apply Credit_. + +. Enter an amount to apply to this funding source. + +. Enter a note. This field is optional. + +. Click _Apply_. + +Allocate credits to funds +^^^^^^^^^^^^^^^^^^^^^^^^^ + +If you have already set up your funds, then you can then click the Allocate to Fund button to apply credits from the 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 credits to funds from the funds interface. See section 1.2 for more information. + +. To allocate credits to funds, click _Allocate to Fund_. + +. Enter the amount that you want to allocate. + +. Enter a note. This field is optional. + +. Click _Apply_. + +Track Debits and Credits +^^^^^^^^^^^^^^^^^^^^^^^^ + +You can track credits to and allocations from each funding source. These amounts are updated when credits and allocations are made in the Funding Source Details. Access the Funding Source Details by clicking on the hyperlinked name of the Funding Source. + +Funds +~~~~~ + +Funds allow you to allocate credits toward specific purchases. In the funds interface, you can create funds; allocate credits from funding sources to funds; transfer money between funds; and apply fund tags to funds. Funds are created for a specific year, either fiscal or calendar. These funds are owned by org units. At the top of the funds interface, you can set a contextual org unit and year. The drop down menu at the top of the screen enables you to focus on funds that are owned by specific organizational units during specific years. + +Create a fund +^^^^^^^^^^^^^ + +. To create a new fund, click _Admin -> Server Administration -> Acquisitions -> Funds_. +. Enter a name for the fund. No limits exist on the number of characters that can be entered in this field. +. Create a code for the fund. No limits exist on the number of characters that can be entered in this field. +. Enter a year for the fund. This can be a fiscal year or a calendar year. The format of the year is YYYY. +. 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 shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units). ++ +[NOTE] +The rule of parental inheritance applies to this list. See section ++ +. Select a currency type from the drop down menu. This menu is comprised of entries in the currency types menu. When a fund is applied to a line item or copy, the price of the item will be encumbered in the currency associated with the fund. +. Click the Active box to activate this fund. You cannot make purchases from this fund if it is not active. +. 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 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, it will appear in red when you apply funds to copies. +. 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 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 appear in yellow when you apply funds to copies. +. Check the Propagate box to propagate funds. When you propagate a fund, the ILS will create a new fund for the following fisca year with the same parameters as your current fund. All of the settings transfer except for the year and the amount of money in the fund. Propagation occurs during the fiscal year close~out operation. +. Check the Rollover box if you want to roll over remaining funds into the same fund next year. +. Click _Save_. + +Allocate Credits from Funding Sources to Funds +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +Credits can be applied to funds from funding sources using the fund interface. The credits that you apply to the fund can be applied later to purchases. + +. To access funds, click _Admin -> Server Administration -> Acquisitions -> Funds_. + +. Click the hyperlinked name of the fund. + +. To add a credit to the fund, click the Create Allocation tab. + +. Choose a Funding Source from the drop down menu. + +. Enter an amount that you want to apply to the fund from the funding source. + +. Enter a note. This field is optional. + +. Click _Apply_. + +Transfer credits between funds +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +The credits that you allocate to funds can be transferred between funds if desired. In the following example, you can transfer $500.00 from the Young Adult Fiction fund to the Children's DVD fund. + +. To access funds, click _Admin -> Server Administration -> Acquisitions -> Funds_. + +. Click the hyperlinked name of the originating fund. + +. The Fund Details screen appears. Click Transfer Money. + +. Enter the amount that you would like to transfer. + +. From the drop down menu, select the destination fund. + +. Add a note. This field is optional. + +. Click _Transfer_. + +Track Balances and Expenditures +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +The Fund Details allows you to track the fund's balance, encumbrances, and amount spent. It also allows you to track allocations from the funding source(s), debits, and fund tags. + +. To access the fund details, click on the hyperlinked name of the fund that you created. + +. The Summary allows you to track the following: + +. Balance - The balance is calculated by subtracting both items that have been invoiced and encumbrances from the total allocated to the fund. +. Total Allocated - This amount is the total amount allocated from the Funding Source. +. Spent Balance - This balance is calculated by subtracting only the items that have been invoiced from the total allocated to the fund. It does not include encumbrances. +. Total Debits - The total debits are calculated by adding the cost of items that have been invoiced and encumbrances. +. Total Spent - The total spent is calculated by adding the cost of items that have been invoiced. It does not include encumbrances. +. Total Encumbered - The total encumbered is calculated by adding all encumbrances. + +Edit a Fund +^^^^^^^^^^^ + +Edit a fund just as you would edit a currency type. + +Perform Year End Closeout Operation +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +The Year End Closeout Operation allows you to deactivate funds for the current year and create analogous funds for the next year. It transfers encumbrances to the analogous funds, and it rolls over any remaining funds if you checked the rollover box when creating the fund. + +. To access the year end closeout of a fund, click Admin -> Server Administration -> Acquisitions -> Funds. + +. Click _Fund Propagation and Rollover_. + +. Check the box adjacent to _Perform Fiscal Year Close~Out Operation_. + +. Notice that the context org unit reflects the context org unit that you selected at the top of the Funds screen. + +. If you want to perform the close~out operation on the context org unit and its child units, then check the box adjacent to Include Funds for Descendant Org Units. + +. Check the box adjacent to dry run if you want to test changes to the funds before they are enacted. Evergreen will generate a summary of the changes that would occur during the selected operations. No data will be changed. + +. Click _Process_. + +. Evergreen will begin the propagation process. Evergreen will make a clone of each fund, but it will increment the year by . + +Invoice menus +~~~~~~~~~~~~~ + +Invoice menus allow you to create drop down menus that appear on invoices. You can create an invoice item type or invoice payment method. + +Invoice item type +^^^^^^^^^^^^^^^^^ + +The invoice item type allows you to enter the types of additional charges that you can add to an invoice. Examples of additional charge types might include taxes or processing fees. Charges for bibliographic items are listed separately from these additional charges. A default list of charge types displays, but you can add custom charge types to this list. Invoice item types can also be used when adding non~bibliographic items to a purchase order. When invoiced, the invoice item type will copy from the purchase order to the invoice. + +. To create a new charge type, click _Admin -> Server Administration -> Acquisitions -> Invoice Item Type_. + +. Click _New Invoice Item Type_. + +. Create a code for the charge type. No limits exist on the number of characters that can be entered in this field. + +. Create a label. No limits exist on the number of characters that can be entered in this field. The text in this field appears in the drop down menu on the invoice. + +. If items on the invoice were purchased with the monies in multiple funds, then you can divide the additional charge across funds. Check the box adjacent to Prorate-> if you want to prorate the charge across funds. + +. Click _Save_. + +Invoice payment method +^^^^^^^^^^^^^^^^^^^^^^ + +The invoice payment method allows you to predefine the type(s) of invoices and payment method(s) that you accept. The text that you enter in the admin module will appear as a drop down menu in the invoice type and payment method fields on the invoice. + +. To create a new invoice payment method, click _Admin -> Server Administration -> Acquisitions -> Invoice Payment Method_. + +. Click _New Invoice Payment Method_. + +. Create a code for the invoice payment method. No limits exist on the number of characters that can be entered in this field. + +. Create a name for the invoice payment method. No limits exist on the number of characters that can be entered in this field. The text in this field appears in the drop down menu on the invoice. + +. Click _Save_. + +Payment methods can be deleted from this screen. + +Line item features +~~~~~~~~~~~~~~~~~~ + +Line item alerts are predefined text that can be added to line items that are on selection lists or purchase orders. You can define the alerts from which staff can choose. Line item alerts appear in a pop up box when the line item, or any of its copies, are marked as received. + +Create a line item alert +^^^^^^^^^^^^^^^^^^^^^^^^ + +. To create a line item alert, click _Administration -> Server Administration -> Acquisitions -> Line Item Alerts_. + +. Click _New Line Item Alert Text_. + +. Create a code for the text. No limits exist on the number of characters that can be entered in this field. + +. Create a description for the text. No limits exist on the number of characters that can be entered in this field. + +. Select an owning library from the drop down menu. The owning library indicates the organizational units whose staff can use this alert. This menu is populated with the shortnames that you created for your libraries in the organizational units tree (See Admin -> Server Administration -> Organizational Units). + +. Click _Save_. + +Line Item MARC Attribute Definitions +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +Line item attributes define the fields that Evergreen needs to extract from the bibliographic records that are in the acquisitions database to display in the catalog. Also, these attributes will appear as fields in the New Brief Record interface. You will be able to enter information for the brief record in the fields where attributes have been defined. + diff --git a/docs/admin/authorities.txt b/docs/admin/authorities.txt new file mode 100644 index 0000000000..722e411c69 --- /dev/null +++ b/docs/admin/authorities.txt @@ -0,0 +1,170 @@ +Authorities +----------- + +Authority Control Sets +~~~~~~~~~~~~~~~~~~~~~~ + + +The tags and subfields that display in authority records in Evergreen are +proscribed by control sets. The Library of Congress control set is the default +control set in Evergreen. In Evergreen release 2.2, you can create customized +control sets for authority records. Also, you can define thesauri and authority +fields for these control sets. + +Patrons and staff will be able to browse authorities in the OPAC. The following +fields are browsable by default: author, series, subject, title, and topic. You +will be able to add custom browse axes in addition to these default fields. + +Control Sets +^^^^^^^^^^^^ + +You can specify the MARC tags and subfields that an authority record should +contain. The Library of Congress control set exists in the staff client by +default. The control sets feature enables librarians to add or customize new +control sets. + +To access existing control sets, click *Admin* -> *Server Administration* -> +*Authorities* -> *Control Sets*. + +To add a *control set*: + +. Click *Admin* -> *Server Administration* -> *Authorities* -> *Control Sets*. +. Click *New Control Set*. . Add a *Name* to the control set. Enter any number +of characters. . Add a *Description* of the control set. Enter any number of +characters. . Click *Save*. + +image::media/Authority_Control_Sets1.jpg[Authority_Control_Sets1] + +Thesauri +~~~~~~~~ + +A thesaurus describes the semantic rules that govern the meaning of words in a +MARC record. The thesaurus code, which indicates the specific thesarus that +should control a MARC record, is encoded in a fixed field using the mnemonic +Subj in the authority record. Eleven thesauri associated with the Library of +Congress control set exist by default in the staff client. + +To access an existing thesaurus, click *Admin* -> *Server Administration* -> +*Authorities* -> *Control Sets*, and choose the hyperlinked thesaurus that you +want to access, or click *Admin* -> *Server Administration* -> *Authorities* -> +*Thesauri*. + + +To add a *Thesaurus*: + +. Click *Admin* -> *Server Administration* -> *Authorities* -> *Control Sets*, +and choose the hyperlinked thesaurus that you want to access, or click *Admin* +-> *Server Administration* -> *Authorities* -> *Thesauri*. . Click *New +Thesaurus*. . Add a *Thesaurus Code*. Enter any single, upper case character. +This character will be entered in the fixed fields of the MARC record. . Add a +*Name* to the thesaurus. Enter any number of characters. . Add a *Description* +of the thesaurus. Enter any number of characters. + +image::media/Authority_Control_Sets2.jpg[Authority_Control_Sets2] + +Authority Fields +~~~~~~~~~~~~~~~~ + + +Authority fields indicate the tags and subfields that should be entered in the +authority record. Authority fields also enable you to specify the type of data +that should be entered in a tag. For example, in an authority record governed +by a Library of Congress control set, the 100 tag would contain a "Heading - +Personal Name." Authority fields also enable you to create the corresponding +tag in the bibliographic record that would contain the same data. + +To create an *Authority Field*: +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +. Click *Admin* -> *Server Administration* -> *Authorities* -> *Control Sets*. +. Click *Authority Fields*. The number in parentheses indicates the number of +authority fields that have been created for the control set. +. Click *New Authority Field*. +. Add a *Name* to the authority field. Enter any number of characters. +. Add a *Description* to describe the type of data that should be entered in +this tag. Enter any number of characters. +. Select a *Main Entry* if you are linking the tag(s) to another entry. +. Add a tag in the authority record. +. Add a subfield in the authority record. Multiple subfields should be entered +without commas or spaces. +. Click *Save*. ++ +image::media/Authority_Control_Sets3.jpg[Authority_Control_Sets3] ++ +.Create the corresponding tag in the bibliographic record that should contain +this information. Click the *None* link in the *Controlled Bib Fields* column. +. Click *New Control Set Bib Field*. +. Add the corresponding tag in the bibiographic record. +. Click *Save*. + +image::media/Authority_Control_Sets4.jpg[Authority_Control_Sets4] + + + +Browse Axes +~~~~~~~~~~~ + +Authority records can be browsed, by default, along five axes: author, series, +subject, title, and topic. Use the *Browse Axes* feature to create additional +axes. + + +Create a new *Browse Axis*: + +. Click *Admin* -> *Server Administration* -> *Authorities* -> *Browse Axes* +. Click *New Browse Axis*. +. Add a *code*. Do not enter any spaces. +. Add a *name* to the axis that will appear in the OPAC. Enter any number of +characters. +. Add a *description* of the axis. Enter any number of characters. +. Add a *sorter attribute*. The sorter attribute indicates the order in which +the results will be displayed. ++ +image::media/Authority_Control_Sets5.jpg[Authority_Control_Sets5] +. Assign the axis to an authority so that users can find the authority record +when browsing authorities. Click *Admin* -> *Server Administration* -> +*Authorities* -> *Control Sets*. +. Choose the control set to which you will add the axis. Click *Authority +Fields* +. Click the link in the *Axes* column of the tag of your choice. +. Click *New Browse Axis-Authority Field Map*. +. Select an *Axis* from the drop down menu. +. Click *Save*. + +image::media/Authority_Control_Sets6.jpg[Authority_Control_Sets6] + + +OPAC Searching of Authorities +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Patrons and librarians can browse authorities through the OPAC. + + +To search for *Authorities*: + +. Click *Advanced Search* in the OPAC. +. Find the *Authority Browse* column in the left side of the screen. +. Select a browse axis, and enter a keyword. The terms in the middle of the +results list should yield the best match. ++ +image::media/Authority_Control_Sets7.jpg[Authority_Control_Sets7] +. Click *Submit*. +. A list of results will appear. The authorities with bibliographic records +attached will be listed in bold with the number of attached bibliographic +records in parentheses. ++ +image::media/Authority_Control_Sets8.jpg[Authority_Control_Sets8] ++ +. Click on the bolded text to view bibliographic records. + +image::media/Authority_Control_Sets9.jpg[Authority_Control_Sets9] + + +*Permissions to use this Feature* + + +To use authority control sets, you will need the following permissions: + +* CREATE_AUTHORITY_CONTROL_SET UPDATE_AUTHORITY_CONTROL_SET +* DELETE_AUTHORITY_CONTROL_SET + diff --git a/docs/admin/auto_suggest_search.txt b/docs/admin/auto_suggest_search.txt new file mode 100644 index 0000000000..fc01215650 --- /dev/null +++ b/docs/admin/auto_suggest_search.txt @@ -0,0 +1,32 @@ +Auto Suggest in Catalog Search +------------------------------ + +The auto suggest feature suggestions for completing search terms as the user enters his search query. Ten suggestions are the default, but the number of suggestions is configurable at +the database level. Scroll through suggestions with your mouse, or use the arrow keys to scroll through the suggestions. Select a suggestion to view records that are linked to +this suggestion. This feature is not turned on by default. You must turn it on in the Admin module. + + +Enabling this Feature +~~~~~~~~~~~~~~~~~~~~~ + +. To enable this feature, click *Admin* -> *Server Administration* -> *Global Flags*. +. Scroll down to item 10, OPAC. +. Double click anywhere in the row to edit the fields. +. Check the box adjacent to *Enabled* to turn on the feature. +. The *Value* field is optional. If you checked *Enabled* in step 4, and you leave this field empty, then Evergreen will only suggest searches for which there are any corresponding MARC records. ++ +note: If you checked *Enabled* in step 4, and you enter the string, *opac_visible*, into this field, then Evergreen will suggest searches for which +there are matching MARC records with copies within your search scope. For example, it will suggest MARC records with copies at your branch. ++ +. Click *Save.* + +image::media/Auto_Suggest_in_Catalog_Search2.jpg[Auto_Suggest_in_Catalog_Search2] + +Using this Feature +~~~~~~~~~~~~~~~~~~ + +. Enter search terms into the basic search field. Evergreen will automatically suggest search terms. +. Select a suggestion to view records that are linked to this suggestion. + +image::media/Auto_Suggest_in_Catalog_Search1.jpg[Auto_Suggest_in_Catalog_Search1] + diff --git a/docs/admin/booking-admin.txt b/docs/admin/booking-admin.txt new file mode 100644 index 0000000000..5fc51e50b2 --- /dev/null +++ b/docs/admin/booking-admin.txt @@ -0,0 +1,199 @@ +Booking Module Administration +----------------------------- + +Creating Bookable Non-Bibliographic Resources +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Staff with the required permissions (Circulator and above) can create bookable non-bibliographic resources such as laptops, projectors, and meeting rooms. + +The following pieces make up a non-bibliographic resource: + +* Resource Type +* Resource Attribute +* Resource Attribute Values +* Resource +* Resource Attribute Map + +You need to create resource types and resource attributes (features of the resource types), and add booking items (resources) to individual resource type. Each resource attribute may have multiple values. You need to link the applicable features (resource attributes and values) to individual item (resource) through the Resource Attribute Map. Before you create resources (booking items) you need to have a resource type and associated resource attributes and values, if any, for them. + +Create New Resource Type +^^^^^^^^^^^^^^^^^^^^^^^^ + +1) Select Admin --> Server Administration --> Booking --> Resource Types. + +image::media/booking-create-resourcetype-1.png[] + +2) A list of current resource types will appear. Use Back and Next buttons to browse the whole list. + +image::media/booking-create-resourcetype-2.png[] + +[NOTE] +You may also see cataloged items in the list. Those items have been marked bookable or booked before. + + +3) To create a new resource type, click New Resource Type in the top right corner, . + +image::media/booking-create-resourcetype-3.png[] + +4) A box will appear in which you create your new type of resource. + +image::media/booking-create-bookable-1.png[] + +* Resource Type Name - Give your resource a name. +* Fine Interval - How often will fines be charged? This period can be input in several ways: + +[NOTE] +==================================================================== +** second(s), minute(s), hour(s), day(s), week(s), month(s), year(s) +** sec(s), min(s) +** s, m, h +** 00:00:30, 00:01:00, 01:00:00 +=================================================================== + +* Fine Amount - The amount that will be charged at each Fine Interval. +* Owning Library - The home library of the resource. +* Catalog Item - (Function not currently available.) +* Transferable - This allows the item to be transferred between libraries. +* Inter-booking and Inter-circulation Interval - The amount of time required by your library between the return of a resource and a new reservation for the resource. This interval uses * the same input conventions as the Fine Interval. +* Max Fine Amount - The amount at which fines will stop generating. + +5) Click Save when you have entered the needed information. + +image::media/booking-create-resourcetype-4.png[] + +6) The new resource type will appear in the list. + +image::media/booking-create-resourcetype-5.png[] + +Create New Resource Attribute +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +1) Select Server Administration --> Booking --> Resource Attributes. + +2) Click New Resource Attribute in the top right corner. + +3) A box will appear in which you can add the attributes of the resource. Attributes are categories of descriptive information that are provided to the staff member when the booking request is made. For example, an attribute of a projector may be the type of projector. Other attributes might be the number of seats available in a room, or the computing platform of a laptop. + +image::media/booking-create-bookable-2.png[] + +* Resource Attribute Name - Give your attribute a name. +* Owning Library - The home library of the resource. +* Resource Type - Type in the first letter to list then choose the Resource Type to which the Attribute is applicable. +* Is Required - (Function not currently available.) + +4) Click Save when the necessary information has been entered. + +5) The added attribute will appear in the list. + +[NOTE] +One resource type may have multiple attributes. You may repeat the above procedure to add more. + +Create New Resource Attribute Value +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +1) One resource attribute may have multiple values. To add new attribute value, select Server Administration → Booking → Resource Attribute Values. + +2) Click New Resource Attribute Value in the top right corner. + +3) A box will appear in which you assign a value to a particular attribute. Values can be numbers, words, or a combination of them, that describe the particular aspects of the resource that have been defined as Attributes. As all values appear on the same list for selection, values should be as unique as possible. For example, a laptop may have a computing platform that is either PC or Mac. + +image::media/booking-create-bookable-3.png[] + +* Owning Library - The home library of the resource. +* Resource Attribute - The attribute you wish to assign the value to. +* Valid Value - Enter the value for your attribute. + +4) Click Save when the required information has been added. + +5) The attribute value will appear in the list. Each attribute should have at least two values attached to it; repeat this process for all applicable attribute values. + +Create New Resource +^^^^^^^^^^^^^^^^^^^ + +1) Add items to a resource type. Click Admin → Server Administration → Booking → Resources. + +2) Click New Resource in the top right corner. + +3) A box will appear. Add information for the resource. + +image::media/booking-create-bookable-4.png[] + +* Owning Library - The home library of the resource. +* Resource Type - Type in the first letter of the resource type's name to list then select the resource type for your item. +* Barcode - Barcode for the resource. +* Overbook - This allows a single item to be reserved, picked up, and returned by multiple patrons during overlapping or identical time periods. +* Is Deposit Required - (Function not currently available.) +* Deposit Amount - (Function not currently available.) +* User Fee - (Function not currently available.) + +4) Click Save when the required information has been added. + +5) The resource will appear in the list. + +[NOTE] +One resource type may have multiple resources attached. + +Map Resource Attributes and Values to Resources +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +1) Use Resource Attribute Maps to bring together the resources and their attributes and values. Select Admin → Server Administration → Booking → Resource Attribute Maps. + +2) Click New Resource Attribute Map in the right top corner. + +3) A box will appear in which you will map your attributes and values to your resources. + +image::media/booking-create-bookable-5.png[] + +* Resource - Enter the barcode of your resource. +* Resource Attribute - Select an attribute that belongs to the Resource Type. +* Attribute Value - Select a value that belongs to your chosen attribute and describes your resource. If your attribute and value do not belong together you will be unable to save. + +4) Click Save once you have entered the required information. + +[NOTE] +A resource may have multiple attributes and values. Repeat the above steps to map all. + +5) The resource attribute map will appear in the list. + +Once all attributes have been mapped your resource will be part of a hierarchy similar to the example below. + +image::media/booking-create-bookable-6.png[] + + +Editing Non-Bibliographic Resources +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Staff with the required permissions can edit aspects of existing non-bibliographic resources. For example, resource type can be edited in the event that the fine amount for a laptop changes from $2.00 to $5.00. + +Editing Resource Types +^^^^^^^^^^^^^^^^^^^^^^ + +1) Bring up your list of resource types. Select Admin --> Server Administration --> Booking --> Resource Types. + +2) A list of current resource types will appear. + +3) Double click anywhere on the line of the resource type you would like to edit. + +4) The resource type box will appear. Make your changes and click Save. + +5) Following the same procedure you may edit Resource Attributes, Attributes Values, Resources and Attribute Map by selecting them on Admin --> Server Administration --> Booking menu. + + + + +Deleting Non-bibliographic Resources +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +1) To delete a booking resource, go to Admin → Server Administration → Booking → Resources. + +2) Select the checkbox in front the resource you want to delete. Click Delete Selected. The resource will disappear from the list. + +Following the same procedure you may delete Resource Attributes Maps. + +You may also delete Resource Attribute Values, Resource Attributes and Resource Types. But you have to delete them in the reverse order when you create them to make sure the entry is not in use when you try to delete it. + +This is the deletion order: Resource Attribut Map/Resources --> Resource Attribute Values --> Resource Attributes --> Resource Types. + + + + diff --git a/docs/admin/cn_prefixes_and_suffixes.txt b/docs/admin/cn_prefixes_and_suffixes.txt new file mode 100644 index 0000000000..03b11c638f --- /dev/null +++ b/docs/admin/cn_prefixes_and_suffixes.txt @@ -0,0 +1,46 @@ +Call Number Prefixes and Suffixes +--------------------------------- + +You can configure call number prefixes and suffixes in the Admin module. This feature ensures more precise cataloging because each cataloger will have access to an identical drop down menu of call number prefixes and suffixes that are used at his library. In addition, it may streamline cataloging workflow. Catalogers can use a drop down menu to enter call number prefixes and suffixes rather than entering them manually. You can also run reports on call number prefixes and suffixes that would facilitate collection development and maintenance. + + +Configure call number prefixes +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Call number prefixes are codes that precede a call number. + +To configure call number prefixes: + +1. Select *Admin -> Server Administration -> Call Number Prefixes*. +2. Click *New Prefix*. +3. Enter the *call number label* that will appear on the item. +4. Select the *owning library* from the drop down menu. Staff at this library, and its descendant org units, with the appropriate permissions, will be able to apply this call number prefix. +5. Click *Save*. + + + +image::media/Call_Number_Prefixes_and_Suffixes_2_21.jpg[Call_Number_Prefixes_and_Suffixes_2_21] + + + +Configure call number suffixes +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Call number suffixes are codes that succeed a call number. + +To configure call number suffixes: + +1. Select *Admin -> Server Administration -> Call Number Suffixes*. +2. Click *New Suffix*. +3. Enter the *call number label* that will appear on the item. +4. Select the *owning library* from the drop down menu. Staff at this library, and its descendant org units, with the appropriate permissions, will be able to apply this call number suffix. +5. Click *Save*. + + +image::media/Call_Number_Prefixes_and_Suffixes_2_22.jpg[Call_Number_Prefixes_and_Suffixes_2_22] + + +Apply Call Number Prefixes and Suffixes +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +You can apply call number prefixes and suffixes to items from a pre-configured list in the *Unified Volume/Copy Creator*. See the document, Unified Volume/Copy Creator, for an example. diff --git a/docs/admin/customize_staff_client.txt b/docs/admin/customize_staff_client.txt new file mode 100644 index 0000000000..c70ff58aed --- /dev/null +++ b/docs/admin/customize_staff_client.txt @@ -0,0 +1,59 @@ +Customizing the Staff Client +---------------------------- + +Customizable Toolbar +~~~~~~~~~~~~~~~~~~~~ + + +By default, two toolbars are available in the staff client: circulation and +cataloging. This feature enables you to customize toolbars in the staff client. +You can create toolbars for specific org unit(s), workstation(s), or login(s). + + +Configure Toolbar +^^^^^^^^^^^^^^^^^ + +. Click *Admin* -> *Workstation Administration* -> *Toolbars* -> *Configure +Toolbars*. +. Click *New Toolbar*. +. *Enter label for toolbar*. ++ +image::media/Customizable_Toolbar1.jpg[Customizable_Toolbar1] ++ +. Click *Ok*. +.Select one of the buttons in the *Available* panel. The *Button ID* describes +that action that the button will take, and the *Label* will display in the +toolbar. +. Click the *--> A* button to add the selected function to the +*Selected* panel on the bottom right side of the screen. To remove a button, +click the *<--R* button. ++ +image::media/Customizable_Toolbar2.jpg[Customizable_Toolbar2] ++ +. Continue adding buttons if desired. The buttons will display in the order that you add +them. If you want to reorder the buttons, click the *Up* or *Down* buttons. +. To separate buttons onto left and right sides of the screen on the same +toolbar, select *toolbarspacer*, and click *--> A*. ++ +image::media/Customizable_Toolbar3.jpg[Customizable_Toolbar3] ++ +. To add a dividing line between buttons that appear on the same side of the +screen, select *toolbarseparator*, and click *-->A*. ++ +image::media/Customizable_Toolbar4.jpg[Customizable_Toolbar4] ++ +. At the bottom of the screen, choose the owner of this toolbar. +If you click *Owning Org Unit*, then the owning org unit that you specify will display this +toolbar. Select the owning org unit from the drop down menu. The rule of +parental inheritance applies, so all child units will inherit the toolbars of +their parental units. +If you click *Owning Workstation*, then the workstation to which you are logged +in when you created the toolbar will display this toolbar. +If you select *Owning User*, then your login has access to that toolbar. + . When you are finished creating the toolbar, click *Save Toolbar*. Any +toolbar to which you have access displays under *Admin -> Workstation +Administration -> Toolbars -> Current*. + +*Permissions* + +ADMIN_TOOLBAR - Allow a user to create, edit, and delete custom toolbars diff --git a/docs/admin/hold_driven_recalls.txt b/docs/admin/hold_driven_recalls.txt new file mode 100644 index 0000000000..c926e2c2e5 --- /dev/null +++ b/docs/admin/hold_driven_recalls.txt @@ -0,0 +1,53 @@ +Hold-driven recalls +=================== + +indexterm:[hold-driven recalls] +indexterm:[circulation, recalls, hold-driven] + +_Added in Evergreen 2.1_ + +In academic libraries, it is common for groups like faculty and graduate +students to have extended loan periods (for example, 120 days), while +others have more common loan periods such as 3 weeks. In these environments, +it is desirable to have a hold placed on an item that has been loaned out +for an extended period to trigger a 'recall', which: + + . Truncates the loan period + . Sets the remaining available renewals to 0 + . 'Optionally': Changes the fines associated with overdues for the new due + date + . 'Optionally': Notifies the current patron of the recall, including the + new due date and fine level + +Enabling hold-driven recalls +---------------------------- + +By default, holds do not trigger recalls. To enable hold-driven recalls +of circulating items, library settings must be changed as follows: + + . Click *Admin* -> *Local Administration* -> *Library Settings Editor.* + . Set the *Recalls: Circulation duration that triggers a recall + (recall threshold)* setting. The recall threshold is specified as an + interval (for example, "21 days"); any items with a loan duration of + less that this interval are not considered for a recall. + . Set the *Recalls: Truncated loan period (return interval)* setting. + The return interval is specified as an interval (for example, "7 days"). + The due date on the recalled item is changed to be the greater of either + the recall threshold or the return interval. + . 'Optionally': Set the *Recalls: An array of fine amount, fine interval, + and maximum fine* setting. If set, this applies the specified fine rules + to the current circulation period for the recalled item. + +When a hold is placed and no available copies are found by the hold targeter, +the recall logic checks to see if the recall threshold and return interval +settings are set; if so, then the hold targeter checks the currently +checked-out copies to determine if any of the currently circulating items at +the designated pickup library have a loan duration longer than the recall +threshold. If so, then the eligible item with the due date nearest to the +current date is recalled. + +Editing the item recall notification email template +--------------------------------------------------- +The template for the item recall notification email is contained in the +'Item Recall Email Notice' template, found under *Admin* -> *Local +Administration* -> *Notifications / Action Triggers*. diff --git a/docs/admin/lsa-library_settings_editor.txt b/docs/admin/lsa-library_settings_editor.txt new file mode 100644 index 0000000000..3338812cdd --- /dev/null +++ b/docs/admin/lsa-library_settings_editor.txt @@ -0,0 +1,38 @@ +Library Settings Editor +----------------------- + +Fine Accrual on Closed Dates +~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +By default, fines accrue only on dates that the library is open. This feature enables you to charge patrons fines on dates the library is closed. Fines accrue during scheduled closings as well as during normal weekly closed dates. + +To enable this feature: + +. Click *Admin* -> *Local Administration* -> *Library Settings* -> *Charge fines on overdue circulations when closed* +. Click *Edit*. +. Set the value to *True*. +. Click *Update Setting*. + + +Target Copies for Holds at Closed Libraries +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +By default, when a patron places a hold on a title, the hold targeter will search for copies to fill the hold only at circulating libraries that are open. Copies at closed libraries +are not targeted to fill holds. When turned on, this feature enables Evergreen to target copies that have closed circulating libraries to fill holds. Two new org unit settings control this feature. + +Use the following setting to target copies for holds at closed circulating libraries: + +. Click *Admin* -> *Local Administration* -> *Library Settings Editor* -> *Target copies for a hold even if copy's circ lib is closed* +. Set the value to *True* if you want to target copies for holds at closed circulating libraries. Set the value to *False*, or leave it unset, if you do not want to enable this feature. +. Click *Update Setting*. + +image::media/Target_Pickup_Lib1.jpg[Target_Pickup_Lib1] + +Use the following setting to target copies for holds IF AND ONLY IF the circulating library is the hold's pickup library. + +. Click *Admin* -> *Local Administration* -> *Library Settings Editor* -> *Target copies for a hold even if copy's circ lib is closed IF the circ lib is the hold's pickup lib* +. Set the value to *True* if you want to target copies for holds at closed circulating libraries when the circulating library of the item and the pickup library of the hold are +the same. Set the value to *False*, or leave it unset, if you do not want to enable this feature. +. Click *Update Setting*. + +image::media/Target_Pickup_Lib2.jpg[Target_Pickup_Lib2] diff --git a/docs/admin/lsa-statcat.txt b/docs/admin/lsa-statcat.txt new file mode 100644 index 0000000000..f3fef43c5d --- /dev/null +++ b/docs/admin/lsa-statcat.txt @@ -0,0 +1,79 @@ +Statistical Categories Editor +----------------------------- + +This is where you configure your statistical categories (stat cats). Stat cats are a way to save and report on additional information that doesn’t fit elsewhere in Evergreen's default records. It is possible to have stat cats for copies or patrons. + +1. Click *Admin -> Local Administration -> Statistical Categories Editor.* + +2. To create a new stat cat, enter the name of the category and select either _patron_ or _copy_ from the *Type* dropdown menu. Each category type has a number of options you may set. + +*Copy Statistical Categories* + +Copy stat cats appear in the _Copy Editor_, also known as the _Edit Item Attributes_ screen. You might use copy stat cats to track books you have bought from a specific vendor, or donations. + +An example of the _Create a new statistical category_ controls for copies: + +image::media/lsa-statcat-1.png[Create copy stat cat] + +* _OPAC Visibility_: Should the category be displayed in the OPAC? +* _Required_: Must the category be assigned a value when editing the item attributes? +* _Archive with Circs_: Should the category and its values for the copy be archived with aged circulation data? +* _SIP Field_: Select the SIP field identifier that will contain the category and its value +* _SIP Format_: Specify the SIP format string + +Some sample copy stat cats: + +image::media/lsa-statcat-2.png[Sample copy stat cats] + +To add an entry, select _Add_. To edit an entry, select the entry you wish to edit from the drop-down list for the category. + +This is how the copy stat cats appear in the _Copy Editor_: + +image::media/lsa-statcat-3.png[Stat cats in Copy Editor] + +*Patron Statistical Categories* + +Patron stat cats can be used to keep track of information such as the high school a patron attends, or the home library for a consortium patron, e.g. Interlink, or patron preferences. They appear in the fifth section of the _Patron Registration_ or _Edit Patron_ screen. + +An example of the _Create a new statistical category_ controls for patrons: + +image::media/lsa-statcat-4.png[Create patron stat cat] + +* _OPAC Visibility_: Should the category be displayed in the OPAC? +* _Required_: Must the category be assigned a value when registering a new patron or editing an existing one? +* _Archive with Circs_: Should the category and its values for the patron be archived with aged circulation data? +* _Allow Free Text_: May the person registering/editing the patron information supply their own value for the category? +* _Show in Summary_: Display the category and its value in the patron summary view? +* _SIP Field_: Select the SIP field identifier that will contain the category and its value +* _SIP Format_: Specify the SIP format string + +[WARNING] +.WARNING +===================================== +If you make a category *required* and also *disallow free text*, make sure that you populate an entry list for the category so that the user may select a value. Failure to do so will result in an unsubmittable patron registration/edit form! +===================================== + +Some sample patron stat cats: + +image::media/lsa-statcat-5.png[Sample patron stat cats] + +To add an entry, click on _Add_ in the category row under the _Add Entry_ column: + +image::media/lsa-statcat-6.png[Add patron category entry] + +To edit an entry, select the entry you wish to edit from the drop-down list for the category: + +image::media/lsa-statcat-7.png[Edit patron category entry] + +An *organizational unit* (consortium, library system branch library, sub library, etc.) may create their own categories and entries, or supplement categories defined by a higher-level org unit with their own entries. + +An entry can be set as the *default* entry for a category and for an org unit. If an entry is set as the default, it will be automatically selected in the patron edit screen, provided no other value has been previously set for the patron. Only one default may be set per category for any given org unit. + +Lower-level org unit defaults override defaults set for higher-level org units; but in the absence of a default set for a given org unit, the nearest parent org unit default will be selected. + +Default entries for the focus location org unit are marked with an asterisk in the entry dropdowns. + +This is how patron stat cats appear in the patron registration/edit screen: + +image::media/lsa-statcat-8.png[Patron stat cats in registration screen] + diff --git a/docs/admin/recent_staff_searches.txt b/docs/admin/recent_staff_searches.txt new file mode 100644 index 0000000000..b297b8d065 --- /dev/null +++ b/docs/admin/recent_staff_searches.txt @@ -0,0 +1,49 @@ +Recent Staff Searches +--------------------- + +This feature enables you to view your recent searches as you perform them in the staff client. The number of searches that you can view is configurable. This feature is only available through the staff client; it is not available to patrons in the OPAC. + +*Administrative Settings* + +By default, ten searches will be saved as you search the staff client. If you want to change the number of saved searches, then you can configure the number of searches that you wish to save through the *Library Settings Editor* in the *Admin* module. + +To configure the number of recent staff searches: + +1. Click *Admin -> Local Administration -> Library Settings Editor.* + +2. Scroll to *OPAC: Number of staff client saved searches to display on left side of results and record details pages* + +3. Click *Edit*. + +4. Select a *Context* from the drop down menu. + +5. Enter the number of searches that you wish to save in the *Value* field. + +6. Click *Update Setting* + +image::media/Saved_Catalog_Searches_2_21.jpg[Saved_Catalog_Searches_2_21] + + +NOTE: To retain this setting, the system administrator must restart the web server. + + +If you do not want to save any searches, then you can turn off this feature. + +To deactivate this feature: + +1. Follow steps 1-4 (one through four) as listed in the previous section. + +2. In the *value* field, enter 0 (zero). + +3. Click *Update Setting.* This will prevent you from viewing any saved searches. + + +*Recent Staff Searches* + +Evergreen will save staff searches that are entered through either the basic or advanced search fields. To view recent staff searches: + +1. Enter a search term in either the basic or advanced search fields. + +2. Your search results for the current search will appear in the middle of the screen. The most recent searches will appear on the left side of the screen. + +image::media/Saved_Catalog_Searches_2_22.jpg[Saved_Catalog_Searches_2_22] diff --git a/docs/admin/restrict_Z39.50_sources_by_perm_group.txt b/docs/admin/restrict_Z39.50_sources_by_perm_group.txt new file mode 100644 index 0000000000..2977cc3649 --- /dev/null +++ b/docs/admin/restrict_Z39.50_sources_by_perm_group.txt @@ -0,0 +1,49 @@ +Restrict Z39.50 Sources by Permission Group +------------------------------------------- + +In Evergreen versions preceeding 2.2, all users with cataloging privileges could view all of the Z39.50 servers that were available for use in the staff client. In Evergreen version 2.2, you can use a permission to restrict users' access to Z39.50 servers. You can apply a permission to the Z39.50 servers to restrict access to that server, and then assign that permission to users or groups so that they can access the restricted servers. + +Administrative Settings +~~~~~~~~~~~~~~~~~~~~~~~ + +You can add a permission to limit use of Z39.50 servers, or you can use an existing permission. + +NOTE: You must be authorized to add permission types at the database level to add a new permission. + +Add a new permission: + +1) Create a permission at the database level. + +2) Click *Admin -> Server Administration -> Permissions* to add a permission to the staff client. + +3) In the *New Permission* field, enter the text that describes the new permission. + +image::media/Restrict_Z39_50_Sources_by_Permission_Group1.jpg[] + +4) Click *Add*. + +5) The new permission appears in the list of permissions. + + + +Restrict Z39.50 Sources by Permission Group +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +1) Click *Admin -> Server Administration -> Z39.50 Servers* + +2) Click *New Z39.50 Server*, or double click on an existing Z39.50 server to restrict its use. + +3) Select the permission that you added to restrict Z39.50 use from the drop down menu. + +image::media/Restrict_Z39_50_Sources_by_Permission_Group2.jpg[] + +4) Click *Save*. + +5) Add the permission that you created to a user or user group so that they can access the restricted server. + + +image::media/Restrict_Z39_50_Sources_by_Permission_Group3.jpg[] + +6) Users that log in to the staff client and have that permission will be able to see the restricted Z39.50 server. + +NOTE: As an alternative to creating a new permission to restrict use, you can use a preexisting permission. For example, your library uses a permission group called SuperCat, and only members in this group should have access to a restricted Z39.50 source. Identify a permission that is unique to the SuperCat group (e.g. CREATE_MARC) and apply that permission to the restricted Z39.50 server. Because these users are in the only group with the permission, they will be the only group w/ access to the restricted server. diff --git a/docs/admin/staff_client-double_clicking.txt b/docs/admin/staff_client-double_clicking.txt new file mode 100644 index 0000000000..f08b00917c --- /dev/null +++ b/docs/admin/staff_client-double_clicking.txt @@ -0,0 +1,23 @@ +New Options for Double Clicking +------------------------------- + +Double Click to Retrieve a Patron's Record +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +. Click *Search -> Search for Patrons* to access a patron's record +. Enter search terms. +. Retrieve a list of possible matches. Double click on the record that you want to open. + +image::media/Double_Click1.jpg[Double_Click1] + + +Double Click to Retrieve Item Attributes +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +. Enter search terms to retrieve a bibliographic record. +. Click *Actions for this Record* -> *Holdings Maintenance*. +. Double click on an item. ++ +image::media/Double_Click3.jpg[Double_Click3] ++ +. The copy information will appear in a new tab. diff --git a/docs/admin/staff_client-recent_searches.txt b/docs/admin/staff_client-recent_searches.txt new file mode 100644 index 0000000000..fd1f87bbc4 --- /dev/null +++ b/docs/admin/staff_client-recent_searches.txt @@ -0,0 +1,42 @@ +Recent Staff Searches +--------------------- + +This feature enables you to view your recent searches as you perform them in the staff client. The number of searches that you can view is configurable. This feature is only available through the staff client; it is not available to patrons in the OPAC. + +Administrative Settings +~~~~~~~~~~~~~~~~~~~~~~~ + +By default, ten searches will be saved as you search the staff client. If you want to change the number of saved searches, then you can configure the number of searches that you wish to save through the *Library Settings Editor* in the *Admin* module. + +To configure the number of recent staff searches: + +. Click *Admin -> Local Administration -> Library Settings Editor.* +. Scroll to *OPAC: Number of staff client saved searches to display on left side of results and record details pages* +. Click *Edit*. +. Select a *Context* from the drop down menu. +. Enter the number of searches that you wish to save in the *Value* field. +. Click *Update Setting* + +image::media/Saved_Catalog_Searches_2_21.jpg[Saved_Catalog_Searches_2_21] + + +NOTE: To retain this setting, the system administrator must restart the web server. + +If you do not want to save any searches, then you can turn off this feature. + +To deactivate this feature: + +. Follow steps 1-4 (one through four) as listed in the previous section. +. In the *value* field, enter 0 (zero). +. Click *Update Setting.* This will prevent you from viewing any saved searches. + + +Recent Staff Searches +~~~~~~~~~~~~~~~~~~~~~ + +Evergreen will save staff searches that are entered through either the basic or advanced search fields. To view recent staff searches: + +. Enter a search term in either the basic or advanced search fields. +. Your search results for the current search will appear in the middle of the screen. The most recent searches will appear on the left side of the screen. + +image::media/Saved_Catalog_Searches_2_22.jpg[Saved_Catalog_Searches_2_22] diff --git a/docs/admin/staff_client-return_to_results_from_marc.txt b/docs/admin/staff_client-return_to_results_from_marc.txt new file mode 100644 index 0000000000..1e6efc53b3 --- /dev/null +++ b/docs/admin/staff_client-return_to_results_from_marc.txt @@ -0,0 +1,6 @@ +Return to Search Results from MARC Record +----------------------------------------- + +This feature enables you to return to your title search results directly from any view of the MARC record, including the OPAC View, MARC Record, MARC Edit, and Holdings Maintenance. You can use this feature to page through records in the MARC Record View or Edit interfaces. You do not have to return to the OPAC View to access title results. + +image::media/Search_Results1.jpg[Search_Results1] diff --git a/docs/admin/staff_client-sorting_columns.txt b/docs/admin/staff_client-sorting_columns.txt new file mode 100644 index 0000000000..1f0e355d3d --- /dev/null +++ b/docs/admin/staff_client-sorting_columns.txt @@ -0,0 +1,59 @@ +Sorting Columns +--------------- + +This feature enables you to sort display columns so that you can find easily the +information that you need on a screen that contains multiple columns. You can +sort display columns on any screen that is built on a grid, such as the Check In +screen or the On Shelf Pull List. + +You can also sort the columns on the following Administration screens: +Circulation Policies, Hold Policies, Circulation Limit Sets, Barcode Completion, +Acquisitions User Request List, and Vandelay Import Errors. + +You can sort items in an ascending or descending order, and you can prioritize +the order in which columns will sort. The following use cases illustrate how to +sort items within the Circulation and Administration interfaces. + +Sorting the On Shelf Pull List +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +You want to capture items that are on the shelf to fill current holds. To +simplify this process, you will sort the items on the On Shelf Pull List by Copy +Location and Call Number. + +. Click *Circulation* -> *Pull List for Hold Requests*. +. The first column that you want to sort is the column, Current Copy Location. Right click the column header, Current Copy Location. +. Click *Sort First (Descending)*. ++ +image::media/Sorting_Columns3.jpg[Sorting_Columns3] ++ +. The next column that you want to sort is the column, Call Number. Right click the column header, Call Number. +. Click *Sort Next (Ascending)*. ++ +image::media/Sorting_Columns4.jpg[Sorting_Columns4] ++ +. The pull list has now been sorted by copy location and call number. + +image::media/Sorting_Columns5.jpg[Sorting_Columns5] + +NOTE: If you wanted to sort more columns, you could continue the process by clicking *Sort Next* for any subsequent columns. + + +Sorting Circulation Policies +~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +You want to sort the display of circulation policies in your staff client. + +. Click *Administration* -> *Local Administration* -> *Circulation Policies*. +. Right click on any column header. +. A pop-up box appears. ++ +image::media/Sorting_Columns2.jpg[Sorting_Columns2] ++ +. Check the *Display* box if you want to display a column in the staff client. +. Check the *Auto Width* box if you want the width of the columns to adjust to fit the staff client. +. Select a sort priority. +.. A sort priority of "0" indicates that no sorting has been applied. Columns will display in their default order. +.. A sort priority of "1" indicates that ascending sorting should be applied to this column first. Subsequent sorts will be applied as you continue to enter increasing numbers. +.. A sort priority of "-1" indicates that descending sorting should be applied to this column. +. Click *Save*. The circulation policies will now sort according to your selections each time that you log into the staff client. diff --git a/docs/admin/staff_client-tab_buttons.txt b/docs/admin/staff_client-tab_buttons.txt new file mode 100644 index 0000000000..34797f78b1 --- /dev/null +++ b/docs/admin/staff_client-tab_buttons.txt @@ -0,0 +1,6 @@ +Tab Buttons +----------- + +This feature enables you to add a new tab to the Evergreen staff client by clicking the + sign adjacent to the tab that you currently have opened. As in previous versions, you can also add new tabs by clicking *File -> New Tab*, or use the hotkey, Ctrl+T. + +image::media/New_Tab_Button1.jpg[New_Tab_Button1] diff --git a/docs/admin/template_toolkit.txt b/docs/admin/template_toolkit.txt new file mode 100644 index 0000000000..3c624ae168 --- /dev/null +++ b/docs/admin/template_toolkit.txt @@ -0,0 +1,294 @@ +TPac Configuration and Customization +------------------------------------ + +Template toolkit documentation +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +For more general information about template toolkit see: http://template-toolkit.org/docs/index.html[official +documentation]. + +The purpose of this chapter is to focus on the +Evergreen-specific uses of Template Toolkit ('TT') in the OPAC. + +TPAC URL +~~~~~~~ + +The URL for the TPAC on a default Evergreen system is +http://localhost/eg/opac/home (adjust `localhost` to match your hostname or IP +address, naturally!) + +Perl modules used directly by TPAC +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + + * `Open-ILS/src/perlmods/lib/OpenILS/WWW/EGCatLoader.pm` + * `Open-ILS/src/perlmods/lib/OpenILS/WWW/EGCatLoader/Account.pm` + * `Open-ILS/src/perlmods/lib/OpenILS/WWW/EGCatLoader/Container.pm` + * `Open-ILS/src/perlmods/lib/OpenILS/WWW/EGCatLoader/Record.pm` + * `Open-ILS/src/perlmods/lib/OpenILS/WWW/EGCatLoader/Search.pm` + * `Open-ILS/src/perlmods/lib/OpenILS/WWW/EGCatLoader/Util.pm` + +Default templates +~~~~~~~~~~~~~~~~ + +The source template files are found in `Open-ILS/src/templates/opac`. + +These template files are installed in `/openils/var/templates/opac`. + +.NOTE +You should generally avoid touching the installed default template files, +unless you are contributing changes that you want Evergreen to adopt as a new +default. Even then, while you are developing your changes, consider using +template overrides rather than touching the installed templates until you are +ready to commit the changes to a branch. See below for information on template +overrides. + +Apache configuration files +~~~~~~~~~~~~~~~~~~~~~~~~~ + +The base Evergreen configuration file on Debian-based systems can be found in +`/etc/apache2/sites-enabled/eg.conf`. This file defines the basic virtual host +configuration for Evergreen (hostnames and ports), then single-sources the +bulk of the configuration for each virtual host by including +`/etc/apache2/eg_vhost.conf`. + +TPAC CSS and media files +~~~~~~~~~~~~~~~~~~~~~~~ + +The CSS files used by the default TPAC templates are stored in the repo in +`Open-ILS/web/css/skin/default/opac/` and installed in +`/openils/var/web/css/skin/default/opac/`. + +The media files--mostly PNG images--used by the default TPAC templates are +stored in the repo in `Open-ILS/web/images/` and installed in +`/openils/var/web/images/`. + +Mapping templates to URLs +~~~~~~~~~~~~~~~~~~~~~~~~~ + +The mapping for templates to URLs is straightforward. Following are a few +examples, where `` is a placeholder for one or more directories +that will be searched for a match: + + * `http://localhost/eg/opac/home` => `/openils/var//opac/home.tt2` + * `http://localhost/eg/opac/advanced` => `/openils/var//opac/advanced.tt2` + * `http://localhost/eg/opac/results` => `/openils/var//opac/results.tt2` + +The template files themselves can process, be wrapped by, or include other +template files. For example, the `home.tt2` template currently involves a +number of other template files to generate a single HTML file: + +.Example Template Toolkit file: opac/home.tt2 +[source, html] +------------------------------------------------------------------------------ +[% PROCESS "opac/parts/header.tt2"; + WRAPPER "opac/parts/base.tt2"; + INCLUDE "opac/parts/topnav.tt2"; + ctx.page_title = l("Home") %] +
+ [% INCLUDE "opac/parts/searchbar.tt2" %] +
+
+
+
+ [% INCLUDE "opac/parts/homesearch.tt2" %] +
+
+
+[% END %] +------------------------------------------------------------------------------ + +We will dissect this example in some more detail later, but the important +thing to note is that the file references are relative to the top of the +template directory. + +How to override templates +~~~~~~~~~~~~~~~~~~~~~~~~~ + +Overrides for templates go in a directory that parallels the structure of the +default templates directory. The overrides then get pulled in via the Apache +configuration. + +In the following example, we demonstrate how to create a file that overrides +the default "Advanced search page" (`advanced.tt2`) by adding a new templates +directory and editing the new file in that directory. + +.Adding an override for the Advanced search page (example) +[source, bash] +------------------------------------------------------------------------------ +bash$ mkdir -p /openils/var/templates_custom/opac +bash$ cp /openils/var/templates/opac/advanced.tt2 \ + /openils/var/templates_custom/opac/. +bash$ vim /openils/var/templates_custom/opac/advanced.tt2 +------------------------------------------------------------------------------ + +We now need to teach Apache about the new templates directory. Open `eg.conf` +and add the following `` element to each of the `` +elements in which you want to include the overrides. The default Evergreen +configuration includes a `VirtualHost` directive for port 80 (HTTP) and another +one for port 443 (HTTPS); you probably want to edit both, unless you want the +HTTP user experience to be different from the HTTPS user experience. + +.Configuring the custom templates directory in Apache's eg.conf +[source,xml] +------------------------------------------------------------------------------ + + # + + # - absorb the shared virtual host settings + Include eg_vhost.conf + + PerlAddVar OILSWebTemplatePath "/openils/var/templates_algoma" + + + # + +------------------------------------------------------------------------------ + +Finally, reload the Apache configuration to pick up the changes: + +.Reloading the Apache configuration +[source,bash] +------------------------------------------------------------------------------ +bash# /etc/init.d/apache2 reload +------------------------------------------------------------------------------ + +You should now be able to see your change at http://localhost/eg/opac/advanced + +Defining multiple layers of overrides +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +You can define multiple layers of overrides, so if you want every library in +your consortium to have the same basic customizations, and then apply +library-specific customizations, you can define two template directories for +each library. + +In the following example, we define the `template_CONS` directory as the set of +customizations to apply to all libraries, and `template_BR#` as the set of +customizations to apply to library BR1 and BR2. + +As the consortial customizations apply to all libraries, we can add the +extra template directory directly to `eg_vhost.conf`: + +.Apache configuration for all libraries (eg_vhost.conf) +[source,xml] +------------------------------------------------------------------------------ +# Templates will be loaded from the following paths in reverse order. +PerlAddVar OILSWebTemplatePath "/openils/var/templates" +PerlAddVar OILSWebTemplatePath "/openils/var/templates_CONS" +------------------------------------------------------------------------------ + +Then we define a virtual host for each library to add the second layer of +customized templates on a per-library basis. Note that for the sake of brevity +we only show the configuration for port 80. + +.Apache configuration for each virtual host (eg.conf) +[source,xml] +------------------------------------------------------------------------------ + + ServerName br1.concat.ca + DocumentRoot /openils/var/web/ + DirectoryIndex index.xml index.html index.xhtml + Include eg_vhost.conf + + PerlAddVar OILSWebTemplatePath "/openils/var/templates_BR1" + + + + + ServerName br2.concat.ca + DocumentRoot /openils/var/web/ + DirectoryIndex index.xml index.html index.xhtml + Include eg_vhost.conf + + PerlAddVar OILSWebTemplatePath "/openils/var/templates_BR2" + + +------------------------------------------------------------------------------ + +Changing some text in the TPAC +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Out of the box, the TPAC includes a number of placeholder text and links. For +example, there is a set of links cleverly named 'Link 1', 'Link 2', and so on +in the header and footer of every page in the TPAC. Let's customize that for +our `templates_BR1` skin. + +To begin with, we need to find the page(s) that contain the text in question. +The simplest way to do that is with the handly utility `ack`, which is much +like `grep` but with built-in recursion and other tricks. On Debian-based +systems, the command is `ack-grep` as `ack` conflicts with an existing utility. +In the following example, we search for files that contain the text "Link 1": + +.Searching for text matching "Link 1" +[source,bash] +------------------------------------------------------------------------------ +bash$ ack-grep "Link 1" /openils/var/templates/opac +/openils/var/templates/opac/parts/topnav_links.tt2 +4: [% l('Link 1') %] +------------------------------------------------------------------------------ + +Next, we copy the file into our overrides directory and edit it with `vim`: + +.Copying the links file into the overrides directory +[source,bash] +------------------------------------------------------------------------------ +bash$ cp /openils/var/templates/opac/parts/topnav_links.tt2 \ + /openils/var/templates_BR1/opac/parts/topnav_links.tt2 +bash$ vim /openils/var/templates_BR1/opac/parts/topnav_links.tt2 +------------------------------------------------------------------------------ + +Finally, we edit the link text in `opac/parts/header.tt2`. + +.Content of the opac/parts/header.tt2 file +[source,html] +------------------------------------------------------------------------------ + +------------------------------------------------------------------------------ + +For the most part, the page looks like regular HTML, but note the `[%_("` +`")%]` that surrounds the text of each link. The `[% ... %]` signifies a TT +block, which can contain one or more TT processing instructions. `l(" ... ");` +is a function that marks text for localization (translation); a separate +process can subsequently extract localized text as GNU gettext-formatted PO +files. + +.NOTE +As Evergreen supports multiple languages, any customizations to Evergreen's +default text must use the localization function. Also, note that the +localization function supports placeholders such as `[_1]`, `[_2]` in the text; +these are replaced by the contents of variables passed as extra arguments to +the `l()` function. + +Once we have edited the link and link text to our satisfaction, we can load +the page in our Web browser and see the live changes immediately (assuming +we are looking at the BR1 overrides, of course). + +Troubleshooting +~~~~~~~~~~~~~~~ + +If there is a problem such as a TT syntax error, it generally shows up as a +an ugly server failure page. If you check the Apache error logs, you will +probably find some solid clues about the reason for the failure. For example, +in the following example the error message identifies the file in which the +problem occurred as well as the relevant line numbers: + +.Example error message in Apache error logs +[source,bash] +------------------------------------------------------------------------------ +bash# grep "template error" /var/log/apache2/error_log +[Tue Dec 06 02:12:09 2011] [warn] [client 127.0.0.1] egweb: template error: + file error - parse error - opac/parts/record/summary.tt2 line 112-121: + unexpected token (!=)\n [% last_cn = 0;\n FOR copy_info IN + ctx.copies;\n callnum = copy_info.call_number_label;\n +------------------------------------------------------------------------------ + diff --git a/docs/admin/user_activity_type.txt b/docs/admin/user_activity_type.txt new file mode 100644 index 0000000000..979f4798b1 --- /dev/null +++ b/docs/admin/user_activity_type.txt @@ -0,0 +1,32 @@ +User Activity Types +------------------- + +The User Activity Types feature enables you to specify the user activity that you want to record in the database. You can use this feature for reporting purposes. This function will also display a last activity date in a user's account. + +Enabling this Feature +~~~~~~~~~~~~~~~~~~~~~ + +Click *Admin* -> *Server Administration* -> *User Activity Types* to access the default set of user activity types and to add new ones. The default set of user activity types records user logins to the Evergreen ILS and to third party products that communicate with Evergreen. + +The *Label* is a free text field that enables you to describe the activity that you are tracking. + +The *Event Caller* describes the third party software or Evergreen interface that interacts with the Evergreen database and is responsible for managing the communication between the parties. + +The *Event Type* describes the type of activity that Evergreen is tracking. Currently, this feature only tracks user authentication. + +The *Event Mechanism* describes the framework for communication between the third party software or OPAC and the database. Enter an event mechanism if you want to track the means by which the software communicates with the database. If you do not want to track how the softwares communicate, then leave this field empty. + +The *Enabled* field allows you to specify which types of user activity that you would like to track. + +The *Transient* column enables you to decide how many actions you want to track. If you want to track only the last activity, then enter *True.* If you want to trace all activity by the user, enter *False*. + +image::media/User_Activity_Types1A.jpg[User_Activity_Types1A] + + +Using this Feature +~~~~~~~~~~~~~~~~~~ + +The last activty date for user logins appears in the patron's summary. + +image::media/User_Activity_Types2A.jpg[User_Activity_Types2A] + diff --git a/docs/attributions.txt b/docs/attributions.txt new file mode 100644 index 0000000000..3d8e6e07d9 --- /dev/null +++ b/docs/attributions.txt @@ -0,0 +1,46 @@ +[[attributions]] +Attributions +============ + +Copyright © 2009-2012 Evergreen DIG + +Copyright © 2007-2012 Equinox + +Copyright © 2007-2012 Dan Scott + +Copyright © 2009-2012 BC Libraries Cooperative (SITKA) + +Copyright © 2008-2012 King County Library System + +Copyright © 2009-2012 Pioneer Library System + +Copyright © 2009-2012 PALS + +Copyright © 2009-2012 Georgia Public Library Service + +Copyright © 2008-2012 Project Conifer + +Copyright © 2009-2012 Bibliomation + +Copyright © 2008-2012 Evergreen Indiana + +Copyright © 2008-2012 SC LENDS + + + +*Current DIG Members* + +* Hilary Caws-Elwitt, Susquehanna County Library +* Karen Collier, Kent County Public Library +* George Duimovich, NRCan Library +* Sally Fortin, Equinox Software +* Wolf Halton, Lyrasis +* June Rayner, eiNetwork +* Steve Sheppard +* Ben Shum, Bibliomation +* Roni Shwaish, eiNetwork +* Robert Soulliere, Mohawk College +* Tim Spindler, C/W MARS +* Lindsay Stratton, Pioneer Library System +* Yamil Suarez, Berklee College of Music +* Jenny Turner, PALS diff --git a/docs/cataloging/batch_importing_MARC.txt b/docs/cataloging/batch_importing_MARC.txt new file mode 100644 index 0000000000..906af8cf5e --- /dev/null +++ b/docs/cataloging/batch_importing_MARC.txt @@ -0,0 +1,214 @@ +Batch Importing MARC Records +---------------------------- + +The cataloging module in version 2.2 includes an enhanced MARC Batch Import interface. This interface features improved matching of records and managing of your import queue. In 2.2, you will be able to specify match points between incoming and existing records. You will also be able to apply filters to your queue that enable you to generate any errors that may have occurred during import. You will also be able to print your queue, email your queue, or export your queue as a CSV file. + +Permissions +~~~~~~~~~~~ + +To use match sets to import records, you will need the following permission: + +ADMIN_IMPORT_MATCH_SET + + +Record Display Attributes +~~~~~~~~~~~~~~~~~~~~~~~~~ + +This feature enables you to specify the tags and subfields that will display in records that appear in the import queue. + + +*Record Match Sets* + +This feature enables you to create custom match points that you can use to accurately match incoming records with existing catalog records. + + +In this example, to demonstrate matching on record attributes and MARC tags and subfields, we will create a record match set that defines a match based on the title of the record, in either the 240 or 245, and the fixed field, Lang. You can add multiple record attributes and MARC tags to customize a record match set. + + +1) Click *Cataloging -> MARC Batch Import/Export*. + +2) Create a new record match set. Click *Record Match Sets -> New Match Set*. + +3) Enter a name for the record match set. + +4) Select an *Owning Library* from the drop down menu. Staff with permissions at this location will be able to use this record match set. + +5) Select a *Match Set Type* from the drop down menu. You can create a match set for authority records or bibliographic records. + +6) Click *Save*. + + +image::media/Batch_Importing_MARC_Records1.jpg[Batch_Importing_MARC_Records1] + + +7) The screen will refresh to list the record match set that you created. Click the link to the record match set. + +8) Create an expression that will define the match points for the incoming record. You can choose from two areas to create a match: *Record Attribute* or *MARC Tag and Subfield*. You can use the Boolean operators AND and OR to combine these elements to create a match set. + +9) Select a *Record Attribute* from the drop-down menu. + +10) Enter a *Match Score.* The *Match Score* indicates the relative importance of that match point as Evergreen evaluates an incoming record against an existing record. You can enter any integer into this field. The number that you enter is only important as it relates to other match points. Recommended practice is that you create a match score of one (1) for the least important match point and assign increasing match points to the power of 2 to working points in increasing importance. + +11) Check the *Negate?* box if you want to negate the match point. Checking this box would be the equivalent of applying a Boolean operator of NOT to the match point. + + + +image::media/Batch_Importing_MARC_Records2.jpg[Batch_Importing_MARC_Records2] + + + +12) Click *Ok.* + +13) Drag the completed match point under the folder with the appropriately-named Boolean folder under the Expression tree. + + + +image::media/Batch_Importing_MARC_Records3.jpg[Batch_Importing_MARC_Records3] + + +The match point will nest underneath the folder in the Expression tree. + + +image::media/Batch_Importing_MARC_Records4.jpg[Batch_Importing_MARC_Records4] + + +14) Enter another *Boolean Operator* to further refine your match set. + +15) Click *Boolean Operator*. + +16) Select the *OR* operator from the drop down menu. + +17) Click *Ok*. + +18) Drag the operator to the expression tree. + + +image::media/Batch_Importing_MARC_Records5.jpg[Batch_Importing_MARC_Records5] + + +19) Click *MARC Tag and Subfield*. + +20) Enter a *MARC tag* on which you want the records to match. + +21) Enter a *subfield* on which you want the records to match. + +22) Enter a *Match Score.* The *Match Score* indicates the relative importance of that match point as Evergreen evaluates an incoming record against an existing record. You can enter any integer into this field. The number that you enter is only important as it relates to other match points. Recommended practice is that you create a match score of one (1) for the least important match point and assign increasing match points to the power of 2 to working points in increasing importance. + +23) Check the *Negate?* box if you want to negate the match point. Checking this box would be the equivalent of applying a Boolean operator of NOT to the match point. + + +24) Click *Ok.* + + +image::media/Batch_Importing_MARC_Records6.jpg[Batch_Importing_MARC_Records6] + + +25) Drag the completed match point under the folder with the appropriately-named Boolean folder under the Expression tree. The Expression will build across the top of the screen. + +26) Add additional MARC tags or record attributes to build the expression tree. + +27) Click *Save Changes to Expression*. + + +image::media/Batch_Importing_MARC_Records7.jpg[Batch_Importing_MARC_Records7] + + +*Replace Mode* + +Replace Mode enables you to replace an existing part of the expression tree with a new record attribute, MARC tag, or Boolean operator. For example, if the top of the tree is AND, in replace mode, you could change that to an OR. + + +1) Create a working match point. + +2) Click *Enter replace mode*. + +3) Highlight the piece of the tree that you want to replace. + +4) Drag the replacement piece over the highlighted piece. + +5) Click *Exit Replace Mode*. + + +*Quality Metrics* + + +1) Set the *Quality Metrics for this Match Set*. Quality metrics are used to determine the overall quality of a record. Each metric is given a weight and the total quality value for a record is equal to the sum of all metrics that apply to that record. For example, a record that has been cataloged thoroughly and contains accurate data would be more valuable than one of poor quality. You may want to ensure that the incoming record is of the same or better quality than the record that currently exists in your catalog; otherwise, you may want the match to fail. The quality metric is optional. + +2) You can create quality metrics based on the record attribute or the MARC Tag and Subfield. + +3) Click *Record Attribute.* + +4) Select an attribute from the drop down menu. + +5) Enter a value for the attribute. + +6.) Enter a match score. You can enter any integer into this field. The number that you enter is only important as it relates to other quality values for the current configuration. Higher scores would indicate increasing quality of incoming records. You can, as in the expression match score, increase the quality points by increasing subsequent records by a power of 2 (two). + +7) Click *Ok*. + + +image::media/Batch_Importing_MARC_Records8.jpg[Batch_Importing_MARC_Records8] + + + +*Import Records* + +The *Import Records* interface incorporates record match sets, quality metrics, more merging options, and improved ways to manage your queue. In this example, we will import a batch of records. One of the records in the queue will contain a matching record in the catalog that is of lower quality than the incoming record. We will import the record according to the guidelines set by our record match set, quality metrics, and merge/overlay choices that we will select. + + +1) Select a *Record Type* from the drop down menu. + +2) Create a queue to which you can upload your records, or add you records to an existing queue. Queues are linked to match sets and a holdings import profile. You cannot change a holdings import or record match set for a queue. + +3) Select a *Record Match Set* from the drop down menu. + +4) Select a *Holdings Import Profile* if you want to import holdings that are attached to your records. + +5) Select a *Record Source* from the drop down menu. + +6) Select a *Merge Profile*. Merge profiles enable you to specify which tags should be removed or preserved in incoming records. + +7) Choose one of the following import options if you want to auto-import records: + +a. *Merge on Single Match* - Using the Record Match Set, Evergreen will only attempt to perform the merge/overlay action if only one match was found in the catalog. + +b. *Merge on Best Match* - If more than one match is found in the catalog for a given record, Evergreen will attempt to perform the merge/overlay action with the best match as defined by the match score and quality metric. + +NOTE: Quality ratio affects only the *Merge on Single Match* and *Merge on Best Match* options. + +8) Enter a *Best/Single Match Minimum Quality Ratio.* Divide the incoming record quality score by the record quality score of the best match that might exist in the catalog. By default, Evergreen will assign any record a quality score of 1 (one). If you want to ensure that the inbound record is only imported when it has a higher quality than the best match, then you must enter a ratio that is higher than 1. For example, if you want the incoming record to have twice the quality of an existing record, then you should enter a 2 (two) in this field. If you want to bypass all quality restraints, enter a 0 (zero) in this field. + + +9) Select an *Insufficient Quality Fall-Through Profile* if desired. This field enables you to indicate that if the inbound record doees not meet the configured quality standards, then you may still import the record using an alternate merge profile. This field is typically used for selecting a merge profile that allows +the user to import holdings attached to a lower quality record without replacing the existing (target) record with the incoming record. This field is optional. + +10) *Browse* to find the appropriate file, and click *Upload*. The files will be uploaded to a queue. + + +image::media/Batch_Importing_MARC_Records9.jpg[Batch_Importing_MARC_Records9] + +11) The screen will display records that have been uploaded to your queue. + +image::media/Batch_Importing_MARC_Records15.jpg[Batch_Importing_MARC_Records15] + + +12) If Evergreen indicates that matching records exist, then click the *Matches* link to view the matching records. Check the box adjacent to the existing record that you want to merge with the incoming record. + +image::media/Batch_Importing_MARC_Records10.jpg[Batch_Importing_MARC_Records10] + +13) Click *Back to Import Queue*. + +14) Check the boxes of the records that you want to import, and click *Import Selected Records*, or click *Import All Records*. + +15) A pop up window will offer you the same import choices that were present on the *Import Records* screen. You can choose one of the import options, or click *Import*. + +image::media/Batch_Importing_MARC_Records9.jpg[Batch_Importing_MARC_Records9] + +16) The screen will refresh. The *Queue Summary* indicates that the record was imported. The *Import Time* column records the date that the record was imported. + +image::media/Batch_Importing_MARC_Records12.jpg[Batch_Importing_MARC_Records12] + +17) Search the catalog to confirm that the record was imported. + +image::media/Batch_Importing_MARC_Records14.jpg[Batch_Importing_MARC_Records14] + diff --git a/docs/cataloging/conjoined_items.txt b/docs/cataloging/conjoined_items.txt new file mode 100644 index 0000000000..4c95842db5 --- /dev/null +++ b/docs/cataloging/conjoined_items.txt @@ -0,0 +1,106 @@ +Conjoined Items +--------------- + +Prior to Evergreen version 2.1, items could be attached to only one bibliographic record. The Conjoined Items feature in Evergreen 2.1 enables catalogers to link items to multiple bibliographic records. This feature will enable more precise cataloging. For example, catalogers will be able to indicate items that are printed back to back, are bilingual, are part of a bound volume, are part of a set, or are available as an e-reader pre-load. This feature will also help the user retrieve more relevant search results. For example, a librarian catalogs a multi-volume festschrift. She can create a bibliographic record for the festschrift and a record for each volume. She can link the items on each volume to the festschrift record so that a patron could search for a volume or the festschrift and retrieve information about both works. + +In the example below, a librarian has created a bibliographic record for two bestselling items. These books are available as physical copies in the library, and they are available as e-reader downloads. The librarian will link the copy of the Kindle to the bibliographic records that are available on the e-reader. + +Using the Conjoined Items Feature +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +The Conjoined Items feature was designed so that you can link items between bibliographic records when you have the item in hand, or when the item is not physically present. Both processes are described here. The steps are fewer if you have the item in hand, but both processes accomplish the same task. This documentalso demonstrates the process to edit or delete links between items and bibliographic records. Finally, the permission a cataloger needs to use this feature is listed. + +.Scenario 1: I want to link an item to another bibliographic record, but I do not have the item in hand + +1) Retrieve the bibliographic record to which you would like to link an item. + +2) Click *Actions for this Record -> Mark as Target for Conjoined Items.* + + +image::media/conj1.jpg[conj1] + + +3) A confirmation message will appear. Click *OK.* + +4) In a new tab, retrieve the bibliographic record with the item that you want to link to the other record. + +5) Click *Actions for this Record -> Holdings Maintenance.* + +6) Select the copy that you want to link to the other bibliographic record. Right-click, or click *Actions for Selected Rows -> Link as Conjoined Items to Previously Marked Bib Record.* + +image::media/conj2.jpg[conj2] + + +7) The *Manage Conjoined Items* interface opens in a new tab. This interface enables you to confirm the success of the link, and to change the peer type if desired. The *Result* column indicates that you created a successful link between the item and the bib record. + +image::media/conj3.jpg[conj3] + +The default peer type, *Back-to-back*, was set as the peer type for our item. To change a peer type after the link has been created, right-click or click *Actions for Selected Items -> Change Peer Type*. A drop down menu will appear. Select the desired peer type, and click *OK.* + + +image::media/conj4.jpg[conj4] + + +8) The *Result* column will indicate that the *Peer Type* [has been] *Updated.* + + +image::media/conj5.jpg[conj5] + + +9) To confirm the link between the item and the desired bib record, reload the tab containing the bib record to which you linked the item. Click the link for *Linked Titles.* + + +image::media/conj6.jpg[conj6] + + +10) To view the copy details, including the peer type, click *Copy Details.* + + +image::media/conj7.jpg[conj7] + + +Items can be linked to multiple bibliographic records simultaneously. If you click the linked titles button in the copy details, then you will retrieve a list of bibliographic records to which this item is linked. + + +image::media/conj8.jpg[conj8] + + +.Scenario 2: I want to link an item to another bibliographic record, and I do have the item in hand + +1) Retrieve the bibliographic record to which you would like to add the item. + +2) Click *Actions for this Record -> Manage Conjoined Items.* + + +image::media/conj9.jpg[conj9] + + +3) A note in the bottom left corner of the screen will confirm that the record was targeted for linkage with conjoined items, and the *Manage Conjoined Items* screen will appear. + +4) Select the peer type from the drop down menu, and scan in the barcode of the item that you want to link to this record. + +5) Click *Link to Bib (Submit).* + + +image::media/conj10.jpg[conj10] + + +6) The linked item will appear in the screen. The *Result* column indicates Success. + +7) To confirm the linkage, click *Actions for this Record -> OPAC View.* + +8) When the bibliographic record appears, click *Reload. Linked Titles* will show the linked title and item. + + +.Scenario 3: I want to edit or break the link between a copy and a bibliographic record + +1) Retrieve the bibliographic record that has a copy linked to it. + +2) Click *Actions for this Record -> Manage Conjoined Items.* + +3) Select the copy that you want to edit, and right-click or click *Actions for Selected Items.* + +4) Make any changes, and click *OK.* + + +UPDATE_COPY - Link items to bibliographic records diff --git a/docs/cataloging/monograph_parts.txt b/docs/cataloging/monograph_parts.txt new file mode 100644 index 0000000000..122fcaea38 --- /dev/null +++ b/docs/cataloging/monograph_parts.txt @@ -0,0 +1,57 @@ +Monograph Parts +--------------- + +*Monograph Parts* enables you to differentiate between parts of monographs or other multi-part items. This feature enables catalogers to describe items more precisely by labeling the parts of an item. For example, catalogers might identify the parts of a monograph or the discs of a DVD set. This feature also allows patrons more flexibility when placing holds on multi-part items. A patron could place a hold on a specific disc of a DVD set if they want to access a specific season or episode rather than an entire series. + +Four new permissions are used by this functionality: CREATE_MONOGRAPH_PART, UPDATE_MONOGRAPH_PART, DELETE_MONOGRAPH_PART and MAP_MONOGRAPH_PART. Thes +e permissions should be assigned at the consorial level to those groups or users that will make use of the features described below. + + +Add a monograph part to an existing record +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +To add a monograph part to an existing record in the catalog: + +1) Retrieve a record. + +2) Click *Actions for this Record -> Manage Parts* + + +image::media/monograph_parts1.jpg[monograph_parts1] + + +3) Click *New Monograph Part* + +4) Enter the *label* that you want to appear to the user in the catalog, and click *Save*. This will create a list of monograph parts from which you can choose when you create a volume and copy. + + +image::media/monograph_parts2.jpg[monograph_parts2] + + +5) Add a volume and copy. To add a volume and copy to your workstation library, click the *Add Volumes* link in the *Record Summary* at the top of the bibliographic record, or click *Actions for this Record -> Add Volumes*. + +To add a volume and copy to your workstation library or other libraries, click *Actions for this Record -> Holdings Maintenance -> Add Volumes*. + + +image::media/monograph_parts3.jpg[monograph_parts3] + + +6) The *Unified Volume/Copy Creator* opens. Enter the number of volumes that you want to add to the catalog and the volume description. + +7) Enter the number of copies and barcode(s) of each item. + +8) Select the *part designation* from the drop down menu adjacent to the barcode field. + +9) Apply a template to the copies, or edit fields in the *Copy Editor*. + + +image::media/monograph_parts4.jpg[monograph_parts4] + + +10) Click *Create Volumes/Items*. + +11) The *Holdings Maintenance* screen will refresh to demonstrate the addition of the volume, copy, and part. These fields also appear in the OPAC View. + + +image::media/monograph_parts5.jpg[monograph_parts5] + diff --git a/docs/cataloging/overlay_record_3950_import.txt b/docs/cataloging/overlay_record_3950_import.txt new file mode 100644 index 0000000000..73c63f1427 --- /dev/null +++ b/docs/cataloging/overlay_record_3950_import.txt @@ -0,0 +1,55 @@ +Overlay Existing Catalog Record via Z39.50 Import +------------------------------------------------- + +This feature enables you to replace a catalog record with a record obtained through a Z39.50 search. No new permissions or administrative settings are needed to use this feature. + +*To Overlay an Existing Record via Z39.50 Import:* + +1) Click *Cataloging -> Import Record from Z39.50* + +2) Select at least one *Service* in addition to the *Local Catalog* in the *Service and Credentials* window in the top right panel. + +3) Enter search terms in the *Query* window in the top left panel. + +4) Click *Search*. + +image::media/Overlay_Existing_Record_via_Z39_50_Import1.jpg[] + +5) The results will appear in the lower window. + +6) Select the record in the local catalog that you wish to overlay. + +7) Click *Mark Local Result as Overlay Target* + + +image::media/Overlay_Existing_Record_via_Z39_50_Import2.jpg[] + + +8) A confirmation message appears. Click *OK*. + +9) Select the record that you want to replace the existing catalog record. + +10) Click *Overlay.* + + +image::media/Overlay_Existing_Record_via_Z39_50_Import3.jpg[] + + +11) The record that you selected will open in the MARC Editor. Make any desired changes to the record, and click *Overlay Record*. + +image::media/Overlay_Existing_Record_via_Z39_50_Import4.jpg[] + + +12) The catalog record that you want to overlay will appear in a new window. Review the MARC record to verify that you are overlaying the correct catalog record. + +13) If the correct record appears, click *Overlay*. + + +image::media/Overlay_Existing_Record_via_Z39_50_Import5.jpg[] + +14) A confirmation message will appear to confirm that you have overlaid the record. Click *Ok*. + +15) The screen will refresh in the OPAC View to show that the record has been overlaid. + + +image::media/Overlay_Existing_Record_via_Z39_50_Import6.jpg[] diff --git a/docs/circulation/README b/docs/circulation/README new file mode 100644 index 0000000000..e69de29bb2 diff --git a/docs/circulation/booking.txt b/docs/circulation/booking.txt new file mode 100644 index 0000000000..730b890569 --- /dev/null +++ b/docs/circulation/booking.txt @@ -0,0 +1,272 @@ +Booking Module +-------------- + +Creating a Booking Reservation +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Only staff members may create reservations. A reservation can be started from a patron record, or a booking resource. To reserve catalogued items, you may start from searching the catalogue, if you do not know the booking item's barcode. + +To create a reservation from a patron record +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +1) Retrieve the patron’s record. + +2) Select Other --> Booking --> Create or Cancel Reservations. This takes you to the Reservations Screen. + +image::media/booking-create-1.png[] + +3) For non-catalogued items, choose a Bookable Resource Type and click Next. For catalogued items, enter the barcode in Enter the barcode of a catalogued, bookable resource box, then click Next beside the box. + +image::media/booking-create-2.png[] + +4) For non-catalogued resources, the Bookable Resource Type and the items associated with the type will appear. + +image::media/booking-create-3.png[] + +For catalogued items, the title and the item will display in the box. + +5) Select the date and time for the reservation in I need this resource... area. Click the date field. A calendar widget will be displayed for you to choose a date. Click the time field to choose time from the dropdown list. + +image::media/booking-create-4.png[] + +[NOTE] +If incorrect date and time is selected, the date/time boxes will appear in red. For example, if the time for which the reservation is set has already passed, the boxes will appear in red. There must be at least 15 minutes between the creation of the reservation and the start time of the reservation. + +6) For non-catalogued resources, patrons may specify special feature(s), if any, of the resource. With these attributes: allows you to do so. For example, if a patron is booking a laptop he/she can choose between PC and Mac and even choose a specific operating system if they need to. Click the drop down arrow to select your option from the list. + +image::media/booking-create-5.png[] + +7) Select the pickup location from the dropdown list. + +image::media/booking-create-6.png[] + +8) If there are multiple copies of the resource and any item listed is acceptable, click Reserve Any. To choose a specific item, select it +and then click Reserve Selected. + +image::media/booking-create-7.png[] + +9) A message will confirm that the action succeeded. Click OK on the prompt. + +10) The screen will refresh and the reservation will appear below the patron’s name at the bottom of the screen. + +image::media/booking-create-9.png[] + +To create a reservation from a booking resource +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +You need to know the barcode of the patron when you create a reservation for him/her from a booking resource. + +1) From the Booking menu, select Create Reservations + +image::media/booking-create-module-1.png[] + +2) Choose a Bookable Resource Type and click Next or enter the barcode of a catalogued resource and click Next. + +image::media/booking-create-module-2.png[] + +3) For non-catalogued resources, a screen showing the Bookable Resource Type and the items associated with the type will appear. + +image::media/booking-create-module-3.png[] + +For catalogued resources, the title and item will appear. + +4) Enter the user’s barcode in the Reserve to patron barcode box. The user’s existing reservations, if any, will appear at the bottom of the screen. + +image::media/booking-create-module-4.png[] + +5) Select the date and time for the reservation in I need this resource... area. Click the date field. A calendar widget will be displayed for you to choose a date. Click the time field to choose time from the dropdown list. + +image::media/booking-create-4.png[] + +[NOTE] +If incorrect date and time is selected, the date/time boxes will appear in red. For example, if the time for which the reservation is set has already passed, the boxes will appear in red. The times must be set correctly for the reservation to be created. There must be at least 15 minutes between the creation of the reservation and the start time of the reservation. + + +6) For non-catalogued resources, patrons may specify special feature(s), if any, of the resource. The With these attributes: allows you to do so. For example, if a patron is booking a laptop they can choose between PC and Mac and even choose a specific operating system if they need to. Click the dropdown arrow to select your option from the list. + +image::media/booking-create-5.png[] + +7) Select the pickup location from the dropdown list. + +image::media/booking-create-6.png[] + +8) If there are multiple copies of the resource and any item listed is acceptable, click Reserve Any. To choose a specific item, select it and then click Reserve Selected. + +image::media/booking-create-7.png[] + +9) A message will confirm that the action succeeded. Click OK on the prompt. + +10) The screen will refresh and the reservation will appear below the patron’s name at the bottom of the screen. + +image::media/booking-create-9.png[] + + +Search the catalogue to create a reservation +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +If you would like to reserve a catalogued item but do not know the item barcode, you may start with a catalogue search. + +1) In the staff client, select Cataloguing --> Search the Catalogue or keyboard shortcut F3 to search for the item you wish to reserve. You may search by any bibliographic information. + +2) Click the title to display the record summary. In the Copy Summary, select Copy Details in Actions column. + +3) The Copy Details will appear in a new row. In the barcode column, click the book now link. + +4) A screen showing the title and barcodes of available copies will appear. + +5) Enter the user’s barcode in the Reserve to patron barcode box. The user’s existing reservations, if any, will appear at the bottom of the screen. + +6) Select the date and time in I need this resource... section. If the date and time set is incorrect the boxes appear in red. For example, if the time for which the reservation is set has already passed, the boxes will appear in red. + +7) Select pickup location. If there are multiple copies and any of the listed items is acceptable, click Reserve Any. To choose a specific item, select it and then click Reserve Selected. + +8) A message will confirm that the action succeeded. Click OK on the prompt. + +9) The screen will refresh, and the reservation will appear below the user’s name. + +[NOTE] +Reservations on catalogued items can be created on Item Status (F5) screen. Select the item, then Actions for Selected Items → Book Item Now. + +Reservation Pull List +~~~~~~~~~~~~~~~~~~~~~ + +Reservation pull list can be generated dynamically on the Staff Client. + +1) To create a pull list, select Booking --> Pull List. + +image::media/booking-pull-1.png[] + +2) You can decide how many days in advance you would like to pull reserved items. Enter the number of days in the box adjacent to Generate list for this many days hence. For example, if you would like to pull items that are needed today, you can enter 1 in the box, and you will retrieve items that need to be pulled today. + +3) Click Fetch to retrieve the pull list. + +image::media/booking-pull-2.png[] + +4) The pull list will appear. Click Print to print the pull list. + +image::media/booking-pull-3.png[] + +Capturing Items for Reservations +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Reservations must be captured before they are ready to be picked up by the patron. + +[CAUTION] +Always capture reservations in Booking Module. Check In function in Circulation does not function the same as Capture Resources. + +1) In the staff client, select Booking --> Capture Resources. + +image::media/booking-capture-1.png[] + +2) Scan the item barcode or type the barcode then click Capture. + +image::media/booking-capture-2.png[] + +3) The message Capture succeeded will appear to the right. Information about the item will appear below the message. Click Print button to print a slip for the reservation. + +image::media/booking-capture-3.png[] + + +Picking Up Reservations +~~~~~~~~~~~~~~~~~~~~~~~ + +[CAUTION] +Always use the dedicated Booking Module interfaces for tasks related to reservations. Items that have been captured for a reservation cannot be checked out using the Check Out interface, even if the patron is the reservation recipient. + +1) Ready-for-pickup reservations can be listed from Other --> Booking --> Pick Up Reservations within a patron record or Booking --> Pick Up Reservations. + + +image::media/booking-pickup-1.png[] + +image::media/booking-pickup-module-1.png[] + + +2) Scan the patron barcode if using Booking --> Pick Up Reservations. + +3) The reservation(s) available for pickup will display. Select those you want to pick up and click Pick Up. + +image::media/booking-pickup-2.png[] + +4) The screen will refresh to show that the patron has picked up the reservation(s). + +image::media/booking-pickup-3.png[] + + +Returning Reservations +~~~~~~~~~~~~~~~~~~~~~~ + +[CAUTION] +When a reserved item is brought back, staff must use the Booking Module to return the reservation. + +1) To return reservations, select Booking --> Return Reservations + +image::media/booking-return-module-1.png[] + +2) You can return the item by patron or item barcode. Here we choose Resource to return by item barcode. Scan or enter the barcode, and click Go. + +image::media/booking-return-module-2.png[] + +3) A pop up box will tell you that the item was returned. Click OK on the prompt. + +4) If we select Patron on the above screen, after scanning the patron's barcode, reservations currently out to that patron are displayed. Highlight the reservations you want to return, and click Return. + +image::media/booking-return-2.png[] + +5) The screen will refresh to show any resources that remain out and the reservations that have been returned. + +image::media/booking-return-module-4.png[] + +[NOTE] +Reservations can be returned from within patron records by selecting Other --> Booking --> Return Reservations + +Cancelling a Reservation +~~~~~~~~~~~~~~~~~~~~~~~~ + +A reservation can be cancelled in a patron’s record or reservation creation screen. + +Cancel a reservation from the patron record +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +1) Retrieve the patron's record. + +2) Select Other --> Booking --> Create or Cancel Reservations. + +image::media/booking-create-1.png[] + +3) The existing reservations will appear at the bottom of the screen. + +image::media/booking-cancel-1.png[] + +4) Highlight the reservation that you want to cancel. Click Cancel Selected. + +image::media/booking-cancel-2.png[] + +[NOTE] +Use Shift or Ctrl on keyboard and mouse click to select multiple reservations if needed. + +5) A pop-up window will confirm the cancellation. Click OK on the prompt. + +6) The screen will refresh, and the cancelled reservation(s) will disappear. + +image::media/booking-cancel-4.png[] + +Cancel a reservation on reservation creation screen +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +1) Access the reservation creation screen by selecting Booking --> Create Reservations. + +2) Select any Bookable Resource Type, then click Next. + +3) Scan or type in the patron barcode in Reserve to Patron box then hit Enter. + +4) Patron's existing reservations will display at the bottom of the screen. + +5) Select those that you want to cancel, then click Cancel Selected. + + + + + + + + diff --git a/docs/circulation/circulating_items.txt b/docs/circulation/circulating_items.txt new file mode 100644 index 0000000000..51d653e66c --- /dev/null +++ b/docs/circulation/circulating_items.txt @@ -0,0 +1,327 @@ +Circulating Items +----------------- + +Check Out (F1) +~~~~~~~~~~~~~~ + +Regular Items +^^^^^^^^^^^^^ + +1) To check out an item press *F1*, click *Check Out* on the Circulation toolbar, or select *Circulation* -> *Check Out Items*. + +image::media/checkout_menu.png[] + +2) Scan or enter patron's barcode and click *Submit* if entering barcode manually. If scanning, number is submitted automatically. + +image::media/retrieve_patron.png[] + +3) Scan or enter item barcode manually, clicking *Submit* if manual. + +image::media/checkout_item_barcode.png[] + +4) Due date is now displayed. + +image::media/due_date_display.png[] + +5) When all items are scanned, hit the *F1* key or click the *Check Out* button on the Circulation toolbar to generate slip receipt or to exit patron record if not printing slip receipts. + +Pre-cataloged Items +^^^^^^^^^^^^^^^^^^^ + +1) Go to patron's *Check Out* screen by clicking *Circulation* -> *Check Out Items*. + +2) Scan the item barcode. + +3) At prompt, click *Pre-Cataloged*. + +image::media/pre_cat_alert.png[] + +4) Enter required information and click *Check Out*. + +image::media/precat.png[] + +[TIP] +On check-in, Evergreen will prompt staff to re-route the item to cataloging. + +Due Dates +^^^^^^^^^ + +Circulation periods are pre-set. When items are checked out, due dates are automatically calculated and inserted into circulation records if the *Specific Due Date* checkbox is not selected on the Check Out screen. The *Specific Due Date* checkbox allows you to set a different due date to override the pre-set loan period. + +Before you scan the item, select the *Specific Due Date* checkbox. Use the calendar widget to select a date. Or click in day, month or year, then use the up or down arrows to make the change or simply delete the data, then enter again. Time is used for hourly loan only. This date applies to all items until you change the date, de-select the *Specific Due Date* checkbox, or quit the patron record. + +image::media/specify_due_date1.png[] + +image::media/specify_due_date2.png[] + +Check In (F2) +~~~~~~~~~~~~~ + +Regular check in +^^^^^^^^^^^^^^^^ + +1) To check in an item, select *Circulation -> Check In Items*, click *Check In* on the Circulation toolbar, or press *F2*. + +image::media/check_in_menu.png[] + +2) Scan item barcode or enter manually and click *Submit*. + +image::media/checkin_barcode.png[] + +3) If there is an overdue fine associated with the checkin, an alert will appear at the top of the screen with a fine tally for the current checkin session. To immediately handle fine payment, click the alert to jump to the patron's bill record. + +image::media/overdue_checkin.png[] + +Backdated check in +^^^^^^^^^^^^^^^^^^ + +This is useful for clearing a book drop. + +1) To change effective check-in date, select *Circulation* -> *Check In Items*, or press *F2*. Use the calendar widget to choose the effective date. + +image::media/backdate_checkin.png[] + +2) The top green bar changes to red. The new effective date is now displayed in the header. + +image::media/backdate_red.png[] + +3) Move the cursor to the *Barcode* field. Scan the items. When finishing backdated check-in, change the *Effective Date* back to today's date. + +Backdate Post-Checkin +^^^^^^^^^^^^^^^^^^^^^ + +After an item has been checked in, you may use the Backdate Post-Checkin function to backdate the check-in date. + +1) Select the item on the Check In screen, click Actions for Selected Items -> Backdate Post-Checkin. + +image::media/backdate_post_checkin.png[] + +2) Use the calendar widget to select an effective check-in date. Click Apply. Overdue fines, if any, will be adjusted according to the new effective check-in date. + +image::media/backdate_post_date.png[] + +[TIP] +Checkin Modifiers +=================================================== +At the right bottom corner there is a *Checkin Modifiers* pop-up list. The options are: + +- Ignore Pre-cat Items: no prompt when checking in a pre-cat item. Item will be routed to Cataloging with Cataloging status. +- Suppress Holds and Transit: item will not be used to fill holds or sent in transit. Item has Reshelving status. +- Amnesty Mode/Forgive Fines: overdue fines will be voided if already created or not be inserted if not yet created (e.g. hourly loans). +- Auto-Print Hold and Transit Slips: slips will be automatically printed without prompt for confirmation. + +These options may be selected simultaneously. The selected option is displayed in the header area. + +image::media/checkin_options.png[] + +==================================================== + +Renewal and Editing the Item's Due Date +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Checked-out items can be renewed if your library's policy allows it. The new due date is calculated from the renewal date. Existing loans can also be extended to a specific date by editing the due date or renewing with a specific due date. + +Renewing via a Patron's Account +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +1) Retrieve the patron record and go to the *Items Out* screen. + +image::media/items_out_click.png[] + +2) Select the item you want to renew. *Click on Actions for Selected Items* -> *Renew*. If you want to renew all items in the account, click *Renew All* instead. + +image::media/renew_action.png[] + +3) If you want to specify the due date, click *Renew with Specific Due Date*. You will be prompted to select a due date. Once done, click *Apply*. + +image::media/renew_specific_date.png[] + +[TIP] +Renewal can also be done on the *Item Status* screen. See the section called <> for more information. + +Renewing by Item Barcode +^^^^^^^^^^^^^^^^^^^^^^^^ +1) To renew items by barcode, select *Circulation* -> *Renew Items* or press *CTRL-F2*. + +2) Scan or manually entire the item barcode. + +image::media/renew_item.png[] + +3) If you want to specify the due date, click *Specific Due Date* and select a new due date from the calendar. + +image::media/renew_item_calendar.png[] + +Editing Due Date +^^^^^^^^^^^^^^^^ + +1) Retrieve the patron record and go to the *Items Out* screen. + +2) Select the item you want to renew. Click on *Actions for Selected Items* -> *Edit Due Date*. + +image::media/edit_due_date_action.png[] + +3) Select a new due date in the pop-up window, then click *Apply*. + +[TIP] +You can select multiple items by pressing down the CTRL key on your keyboard and clicking each items you want to edit. + +[NOTE] +Editing a due date is not included in the renewal count. + +Marking Items Lost and Claimed Returned +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Lost Items +^^^^^^^^^^ +1) To mark items Lost, retrieve patron record and click *Items Out*. + +2) Select the item. Click on *Actions for Selected Items* -> *Mark Lost (by Patron)*. + +image::media/mark_lost.png[] + +3) The lost item now displays in the *Lost/Claimed Returned/Long Overdue, Has Unpaid Billings* section of the patron record. + +image::media/lost_cr_section.png[] + +4) The lost item also adds to the count of *Lost* items in the patron summary on the left (or top) of the screen. + +image::media/patron_summary_checkouts.jpg[] + +[NOTE] +Lost Item Billing +======================== +- Marking an item Lost will automatically bill the patron the replacement cost of the item as recorded in the price field in the item record, and a processing fee as determined by your local policy. If the lost item has overdue charges, the overdue charges may be voided or retained based on local policy. +- A lost-then-returned item will disappear from the Items Out screen only when all bills linked to this particular circulation have been resolved. Bills may include replacement charges, processing fees, and manual charges added to the existing bills. +- The replacement fee and processing fee for lost-then-returned items may be voided if set by local policy. Overdue fines may be reinstated on lost-then-returned items if set by local policy. +========================== + +Refunds for Lost Items +^^^^^^^^^^^^^^^^^^^^^^^ + +If an item is returned after a lost bill has been paid and the library's policy is to void the replacement fee for lost-then-returned items, there will be a negative balance in the bill. A refund needs to be made to close the bill and the circulation record. Once the outstanding amount has been refunded, the bill and circulation record will be closed and the item will disappear from the Items Out screen. + +If you need to balance a bill with a negative amount and close the linked lost circulation record without making a refund (removing the item from the *Lost, Claimed Returned, Long Overdue, Has Unpaid Bills* panel on the *Items Out* screen), you need to add two dummy bills to the existing bills. The first one can be of any amount (e.g. $0.01), while the second should be of the absolute value of the negative amount. Then you need to void the first dummy bill. The reason for using a dummy bill is that Evergreen will check and close the circulation record only when payment is applied or bills are voided. + +Claimed Returned Items +^^^^^^^^^^^^^^^^^^^^^^^ + +1) To mark an item Claimed Returned, retrieve the patron record and go to the *Items Out* screen. + +2) Select the item, then select *Actions for Selected Items* -> *Mark Claimed Returned* from the dropdown menu. + +image::media/mark_claims_returned.png[] + +3) Select a date and click *Apply*. + +image::media/claimed_date.png[] + +4) The Claimed Returned item now displays in the *Lost/Claimed Returned/Long Overdue, Has Unpaid Billings* section of the patron record. + +image::media/lost_cr_section.png[] + +5) The Claimed Returned item adds to the count of Check Outs that are Claimed Returned in the patron summary on the left (or top) of the screen. It also adds to the total *Claims-returned Count* (including those that are current Check Outs and those that have since been returned) that is displayed when editing the patron's record. + +image::media/patron_summary_checkouts.jpg[] + +[NOTE] +More on Claimed Returned Items +==================================== +- The date entered for a Claimed Returned item establishes the fine. If the date given has passed, bills will be adjusted accordingly. +- When a Claimed Returned item is returned, if there is an outstanding bill associated with it, the item will not disappear from the *Items Out* screen. It will disappear when the outstanding bills are resolved. +- When an item is marked Claimed Returned, the value in *Claims-returned Count* field in the patron record is automatically increased. Staff can manually adjust this count by editing the patron record. +==================================== + +In-house Use (F6) +~~~~~~~~~~~~~~~~~ +1) To record in-house use, select *Circulation* -> *Record-In House Use*, click *Check Out* -> *Record In-House Use* on the circulation toolbar , or press *F6*. + +image::media/record_in_house_action.png[] + +2) To record in-house use for cataloged items, enter number of uses, scan barcode or type barcode and click *Submit*. + +image::media/in_house_use.png[] + +[NOTE] +The statistics of in-house use are separated from circulation statistics. The in-house use count of cataloged items is not included in the items' total use count. + +[[itemstatus]] +Item Status (F5) +~~~~~~~~~~~~~~~~ + +The Item Status screen is very useful. Many actions can be taken by either circulation staff or catalogers on this screen. Here we will cover some circulation-related functions, namely checking item status, viewing past circulations, inserting item alert messages, marking items missing or damaged, etc. + +Checking item status +^^^^^^^^^^^^^^^^^^^^ + +1) To check the status of an item, select *Search* -> *Search for copies by Barcode* or *Circulation* -> *Show Item Status by Barcode*; click the *Item Status button* on the circulation or cataloging toolbar; or press *F5*. + +image::media/item_status_menu.png[] + +2) Scan the barcode or type it and click *Submit*. The current status of the item is displayed with selected other fields. You can use the column picker to select more fields to view. + +image::media/item_status_barcode.png[] + +3) Click the *Alternate View* button, and the item summary and circulation history will be displayed. + +image::media/item_status_altview.png[] + +4) Click *List View* to go back. + +image::media/item_status_list_view.png[] + +[NOTE] +If the item's status is "Available", the displayed due date refers to the previous circulation's due date. + +[TIP] +Upload From File allows you to load multiple items saved in a file on your local computer. The file contains a list of the barcodes in text format. To ensure smooth uploading and further processing on the items, it is recommended that the list contains no more than 100 items. + +Viewing past circulations +^^^^^^^^^^^^^^^^^^^^^^^^^^ +1) To view past circulations, retrieve the item on the *Item Status* screen as described above. + +2) Select *Actions for Selected Items* -> *Show Last Few Circulations*. + +image::media/last_few_circs_action.png[] + +3) The item's recent circulation history is displayed. + +image::media/last_few_circs_display.png[] + +4) To retrieve the patron(s) of the last circulations, click the *Retrieve Last Patron* or the *Retrieve All These Patrons* button at the bottom of the above screen. Patron record(s) will be displayed in new tab(s). + +[TIP] +The number of items that displays in the circulation history can be set in Local *Administration* -> *Library Settings Editor*. + +[NOTE] +You can also retrieve the past circulations on the patron's Items Out screen and from the Check In screen. + +Marking items damaged or missing and other functions +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +1) To mark items damaged or missing, retrieve the item on the *Item Status* screen. + +2) Select the item. Click on *Actions for Selected Items* -> *Mark Item Damaged* or *Mark Item Missing*. + +image::media/mark_missing_damaged.png[] + +[NOTE} +Depending on the library's policy, when marking an item damaged, bills (cost and/or processing fee) may be inserted into the last borrower's account. + +3) Following the above procedure, you can check in and renew items by using the *Check in Items* and *Renew Items* on the dropdown menu. + +Item alerts +^^^^^^^^^^^ + +The *Edit Item Attributes* function on the *Actions for Selected Items* dropdown list allows you to edit item records. Here, we will show you how to insert item alert messages by this function. See cataloging instructions for more information on item editing. +1) Retrieve record on *Item Status* screen. + +2) Once item is displayed, highlight it and select *Actions for Selected Items* -> *Edit Item Attributes*. + +3) The item record is displayed in the *Copy Editor*. + +image::media/copy_edit_alert.png[] + +4) Click *Alert Message* in the *Miscellaneous* column. The background color of the box changes. Type in the message then click *Apply*. + +image::media/copy_alert_message.png[] + +5) Click *Modify Copies*, then confirm the action. diff --git a/docs/development/README b/docs/development/README new file mode 100644 index 0000000000..e69de29bb2 diff --git a/docs/development/updating_translations_launchpad.txt b/docs/development/updating_translations_launchpad.txt new file mode 100644 index 0000000000..dc57f3490c --- /dev/null +++ b/docs/development/updating_translations_launchpad.txt @@ -0,0 +1,54 @@ +Updating translations using Launchpad +===================================== + +This document describes how to update the translations in an Evergreen branch +by pulling them from Launchpad, as well as update the files to be translated +in Launchpad by updating the POT files in the Evergreen master branch. + +Prerequisites +------------- +You must install all of the Python prerequisites required for building +translations, per +http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-admin:customizations:i18n + +* https://bitbucket.org/izi/polib/wiki/Home[polib] +* http://translate.sourceforge.net[translate-toolkit] +* http://pypi.python.org/pypi/python-Levenshtein/[levenshtein] +* http://pypi.python.org/pypi/setuptools[setuptools] +* http://pypi.python.org/pypi/simplejson/[simplejson] +* http://lxml.de/[lxml] + +Updating the translations +------------------------- + +. Check out the latest translations from Launchpad by branching the Bazaar +repository: ++ +[source,bash] +------------------------------------------------------------------------------ +bzr branch lp:~denials/evergreen/translation-export +------------------------------------------------------------------------------ ++ +This creates a directory called "translation-export". ++ +. Ensure you have an updated Evergreen release branch. +. Run the `build/i18n/scripts/update_pofiles` script to copy the translations + into the right place and avoid any updates that are purely metadata (dates + generated, etc). +. Commit the lot! And backport to whatever release branches need the updates. +. Build updated POT files: ++ +[source,bash] +------------------------------------------------------------------------------ +cd build/i18n +make newpot +------------------------------------------------------------------------------ ++ +This will extract all of the strings from the latest version of the files in +Evergreen. ++ +. (This part needs automation): Then, via the magic of `git diff` and `git add`, +go through all of the changed files and determine which ones actually have +string changes. Recommended approach is to re-run `git diff` after each +`git add`. +. Commit the updated POT files and backport to the pertinent release branches. diff --git a/docs/installation/edi_setup.txt b/docs/installation/edi_setup.txt new file mode 100644 index 0000000000..ececa1564f --- /dev/null +++ b/docs/installation/edi_setup.txt @@ -0,0 +1,212 @@ +Setting Up EDI Acquisitions +--------------------------- + +Introduction +~~~~~~~~~~~~ + +Electronic Data Interchange (EDI) is used to exchange information between +participating vendors and Evergreen. This chapter contains technical +information for installation and configuration of the components necessary +to run EDI Acquisitions for Evergreen. + +Installation +~~~~~~~~~~~~ + +Install EDI Translator +^^^^^^^^^^^^^^^^^^^^^^ + +The EDI Translator is used to convert data into EDI format. It runs +on localhost and listens on port 9191 by default. This is controlled via +the edi_webrick.cnf file located in the edi_translator directory. It should +not be necessary to edit this configuration if you install EDI Translator +on the same server used for running Action/Triggers events. + +[NOTE] +If you are running Evergreen with a multi-server configuration, make sure +to install EDI Translator on the same server used for Action/Trigger event +generation. + +.Steps for Installing + +1. As the *opensrf* user, copy the EDI Translator code found in + Open-ILS/src/edi_translator to somewhere accessible + (for example, /openils/var/edi): ++ +[source, bash] +-------------------------------------------------- +cp -r Open-ILS/src/edi_translator /openils/var/edi +-------------------------------------------------- +2. Navigate to where you have saved the code to begin next step: ++ +[source, bash] +------------------- +cd /openils/var/edi +------------------- +3. Next, as the *root* user (or a user with sudo rights), install the + dependencies, via "install.sh". This will perform some apt-get routines + to install the code needed for the EDI translator to function. + (Note: subversion must be installed first) ++ +[source, bash] +----------- +./install.sh +----------- +4. Now, we're ready to start "edi_webrick.bash" which is the script that calls + the "Ruby" code to translate EDI. This script needs to be started in + order for EDI to function so please take appropriate measures to ensure this + starts following reboots/upgrades/etc. As the *opensrf* user: ++ +[source, bash] +----------------- +./edi_webrick.bash +----------------- +5. You can check to see if EDI translator is running. + * Using the command "ps aux | grep edi" should show you something similar + if the script is running properly: ++ +[source, bash] +------------------------------------------------------------------------------------------ +root 30349 0.8 0.1 52620 10824 pts/0 S 13:04 0:00 ruby ./edi_webrick.rb +------------------------------------------------------------------------------------------ + * To shutdown EDI Translator you can use something like pkill (assuming + no other ruby processes are running on that server): ++ +[source, bash] +----------------------- +kill -INT $(pgrep ruby) +----------------------- + +Install EDI Scripts +^^^^^^^^^^^^^^^^^^^ + +The EDI scripts are "edi_pusher.pl" and "edi_fetcher.pl" and are used to +"push" and "fetch" EDI messages for configured EDI accounts. + +1. As the *opensrf* user, copy edi_pusher.pl and edi_fetcher.pl from + Open-ILS/src/support-scripts into /openils/bin: ++ +[source, bash] +-------------------------------------------------- +cp Open-ILS/src/support-scripts/edi_pusher.pl /openils/bin +cp Open-ILS/src/support-scripts/edi_fetcher.pl /openils/bin +-------------------------------------------------- +2. Setup the edi_pusher.pl and edi_fetcher.pl scripts to run as cron jobs + in order to regularly push and receive EDI messages. + * Add to the opensrf user's crontab the following entries: ++ +[source, bash] +----------------------------------------------------------------------- +10 * * * * cd /openils/bin && /usr/bin/perl ./edi_pusher.pl > /dev/null +0 1 * * * cd /openils/bin && /usr/bin/perl ./edi_fetcher.pl > /dev/null +----------------------------------------------------------------------- + * The example for edi_pusher.pl sets the script to run at + 10 minutes past the hour, every hour. + * The example for edi_fetcher.pl sets the script to run at + 1 AM every night. + +[NOTE] +You may choose to run the EDI scripts more or less frequently based on the +necessary response times from your vendors. + +Configuration +~~~~~~~~~~~~~ + +Configuring Providers +^^^^^^^^^^^^^^^^^^^^^ + +Look in Admin > Server Administration > Acquisitions > Providers + +[options="header"] +|====================================================================================== +|Column |Description/Notes +|Provider Name |A unique name to identify the provider +|Code |A unique code to identify the provider +|Owner |The org unit who will "own" the provider. +|Currency |The currency format the provider accepts +|Active |Whether or not the Provider is "active" for use +|Default Claim Policy|?? +|EDI Default |The default "EDI Account" to use (see EDI Accounts Configuration) +|Email |The email address for the provider +|Fax Phone |A fax number for the provider +|Holdings Tag |The holdings tag to be utilized (usually 852, for Evergreen) +|Phone |A phone number for the provider +|Prepayment Required |Whether or not prepayment is required +|SAN |The vendor provided, org unit specific SAN code +|URL |The vendor website +|====================================================================================== + +Configuring EDI Accounts +^^^^^^^^^^^^^^^^^^^^^^^^ + +Look in Admin > Server Administration > Acquisitions > EDI Accounts + +[options="header"] +|=============================================================================================================== +|Column |Description/Notes +|Label |A unique name to identify the provider +|Host |FTP/SFTP/SSH hostname - vendor assigned +|Username |FTP/SFTP/SSH username - vendor assigned +|Password |FTP/SFTP/SSH password - vendor assigned +|Account |Vendor assigned account number associated with your organization +|Owner |The organizational unit who owns the EDI account +|Last Activity |The date of last activity for the account +|Provider |This is a link to one of the "codes" in the "Providers" interface +|Path |The path on the vendor's server where Evergreen will send it's outgoing .epo files +|Incoming Directory |The path on the vendor's server where "incoming" .epo files are stored +|Vendor Account Number|Vendor assigned account number. +|Vendor Assigned Code |Usually a sub-account designation. Can be used with or without the Vendor Account Number. +|=============================================================================================================== + +Configuring Organizational Unit SAN code +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +Look in Admin > Server Settings > Organizational Units + +This interface allows a library to configure their SAN, alongside +their address, phone, etc. + +Troubleshooting +~~~~~~~~~~~~~~~ + +PO JEDI Template Issues +^^^^^^^^^^^^^^^^^^^^^^^ + +Some libraries may run into issues with the action/trigger (PO JEDI). +The template has to be modified to handle different vendor codes that +may be used. For instance, if you use "ingra" instead of INGRAM this +may cause a problem because they are hardcoded in the template. The +following is an example of one modification that seems to work. + +.Original template has: + +[source, bash] +---------------------------------------------------------------------------------------------------------------------------------------------- +"buyer":[ + [% IF target.provider.edi_default.vendcode && (target.provider.code == 'BT' || target.provider.name.match('(?i)^BAKER & TAYLOR')) -%] + {"id-qualifier": 91, "id":"[% target.ordering_agency.mailing_address.san _ ' ' _ target.provider.edi_default.vendcode %]"} + [%- ELSIF target.provider.edi_default.vendcode && target.provider.code == 'INGRAM' -%] + {"id":"[% target.ordering_agency.mailing_address.san %]"}, + {"id-qualifier": 91, "id":"[% target.provider.edi_default.vendcode %]"} + [%- ELSE -%] + {"id":"[% target.ordering_agency.mailing_address.san %]"} + [%- END -%] +], +---------------------------------------------------------------------------------------------------------------------------------------------- + +.Modified template has the following where it matches on provider SAN instead of code: + +[source, bash] +------------------------------------------------------------------------------------------------------------------------------------------ +"buyer":[ + [% IF target.provider.edi_default.vendcode && (target.provider.san == '1556150') -%] + {"id-qualifier": 91, "id":"[% target.ordering_agency.mailing_address.san _ ' ' _ target.provider.edi_default.vendcode %]"} + {"id-qualifier": 91, "id":"[% target.ordering_agency.mailing_address.san _ ' ' _ target.provider.edi_default.vendcode %]"} + [%- ELSIF target.provider.edi_default.vendcode && (target.provider.san == '1697978') -%] + {"id":"[% target.ordering_agency.mailing_address.san %]"}, + {"id-qualifier": 91, "id":"[% target.provider.edi_default.vendcode %]"} + [%- ELSE -%] + {"id":"[% target.ordering_agency.mailing_address.san %]"} + [%- END -%] +], +------------------------------------------------------------------------------------------------------------------------------------------ + diff --git a/docs/installation/server_installation.txt b/docs/installation/server_installation.txt new file mode 100644 index 0000000000..0f52df4b14 --- /dev/null +++ b/docs/installation/server_installation.txt @@ -0,0 +1,549 @@ +README for Evergreen 2.2 +======================== +:toc: +:numbered: + +Preamble: referenced user accounts +---------------------------------- + +In subsequent sections, we will refer to a number of different accounts, as +follows: + + * Linux user accounts: + ** The *user* Linux account is the account that you use to log onto the + Linux system as a regular user. + ** The *root* Linux account is an account that has system administrator + privileges. On Debian and Fedora you can switch to this account from + your *user* account by issuing the `su -` command and entering the + password for the *root* account when prompted. On Ubuntu you can switch + to this account from your *user* account using the `sudo su -` command + and entering the password for your *user* account when prompted. + ** The *opensrf* Linux account is an account that you create when installing + OpenSRF. You can switch to this account from the *root* account by + issuing the `su - opensrf` command. + ** The *postgres* Linux account is created automatically when you install + the PostgreSQL database server. You can switch to this account from the + *root* account by issuing the `su - postgres` command. + * PostgreSQL user accounts: + ** The *evergreen* PostgreSQL account is a superuser account that you will + create to connect to the PostgreSQL database server. + * Evergreen administrator account: + ** The *egadmin* Evergreen account is an administrator account for + Evergreen that you will use to test connectivity and configure your + Evergreen instance. + +Preamble: Developer instructions +-------------------------------- + +[NOTE] +Skip this section if you are using an official release tarball downloaded +from http://evergreen-ils.org/downloads + +Developers working directly with the source code from the Git repository, +rather than an official release tarball, must install some extra packages +and perform one step before they can proceed with the `./configure` step. + +As the *root* Linux account, install the following packages: + + * autoconf + * automake + * libtool + +As the *user* Linux account, issue the following command in the Evergreen +source directory to generate the configure script and Makefiles: + +[source, bash] +------------------------------------------------------------------------------ +autoreconf -i +------------------------------------------------------------------------------ + +After running `make install`, developers also need to install the Dojo Toolkit +set of JavaScript libraries. The appropriate version of Dojo is included +in Evergreen release tarballs. Developers should install the Dojo 1.3.3 +version of Dojo by issuing the following commands as the *opensrf* Linux +account: + +[source, bash] +------------------------------------------------------------------------------ +wget http://download.dojotoolkit.org/release-1.3.3/dojo-release-1.3.3.tar.gz +tar -C /openils/var/web/js -xzf dojo-release-1.3.3.tar.gz +cp -r /openils/var/web/js/dojo-release-1.3.3/* /openils/var/web/js/dojo/. +------------------------------------------------------------------------------ + +Installing prerequisites +------------------------ + +Evergreen has a number of prerequisite packages that must be installed +before you can successfully configure, compile, and install Evergreen. + +1. Begin by installing the most recent version of OpenSRF (2.1 or later). + You can download OpenSRF releases from http://evergreen-ils.org/opensrf.php +2. On many distributions, it is necessary to install PostgreSQL 9 from external + repositories. ++ + * On Debian Squeeze, open `/etc/apt/sources.list` in a text editor as the + *root* Linux account and add the following line: ++ +[source, bash] +------------------------------------------------------------------------------ +deb http://backports.debian.org/debian-backports squeeze-backports main contrib +------------------------------------------------------------------------------ ++ + * On Ubuntu Lucid, you can use a PPA (personal package archive), which are + package sources hosted on Launchpad. The one most commonly used by Evergreen + Community members is maintained by Martin Pitt, who also maintains the + official PostgreSQL packages for Ubuntu. As the *root* Linux account, issue + the following commands to add the PPA source: ++ +[source, bash] +------------------------------------------------------------------------------ +apt-get install python-software-properties +add-apt-repository ppa:pitti/postgresql +------------------------------------------------------------------------------ ++ + * Ubuntu Precise comes with PostgreSQL 9, so no additional steps are required. ++ + * Fedora 16 comes with PostgreSQL 9, so no additional steps are required. ++ +3. On Debian and Ubuntu, run `aptitude update` as the *root* Linux account to + retrieve the new packages from the backports repository. +4. Issue the following commands as the *root* Linux account to install + prerequisites using the `Makefile.install` prerequisite installer, + substituting `debian-squeeze`, `fedora16`, `ubuntu-lucid`, or + `ubuntu-precise` for below: ++ +[source, bash] +------------------------------------------------------------------------------ +make -f Open-ILS/src/extras/Makefile.install +------------------------------------------------------------------------------ ++ +5. Add the libdbi-libdbd libraries to the system dynamic library path by + issuing the following commands as the *root* Linux account: ++ +[NOTE] +You should skip this step if installing on Ubuntu Precise. The ubuntu-precise +target uses libdbd-pgsql from packages. ++ +.Debian / Ubuntu Lucid +[source, bash] +------------------------------------------------------------------------------ +echo "/usr/local/lib/dbd" > /etc/ld.so.conf.d/eg.conf +ldconfig +------------------------------------------------------------------------------ ++ +.Fedora +[source, bash] +------------------------------------------------------------------------------ +echo "/usr/lib64/dbd" > /etc/ld.so.conf.d/eg.conf +ldconfig +------------------------------------------------------------------------------ + +Configuration and compilation instructions +------------------------------------------ + +For the time being, we are still installing everything in the `/openils/` +directory. From the Evergreen source directory, issue the following commands as +the *user* Linux account to configure and build Evergreen: + +[source, bash] +------------------------------------------------------------------------------ +./configure --prefix=/openils --sysconfdir=/openils/conf +make +------------------------------------------------------------------------------ + +Installation instructions +------------------------- + +1. Once you have configured and compiled Evergreen, issue the following + command as the *root* Linux account to install Evergreen, build the server + portion of the staff client, and copy example configuration files to + `/openils/conf`. + Change the value of the `STAFF_CLIENT_STAMP_ID` variable to match the version + of the staff client that you will use to connect to the Evergreen server. ++ +[source, bash] +------------------------------------------------------------------------------ +make STAFF_CLIENT_STAMP_ID=rel_2_2 install +------------------------------------------------------------------------------ ++ +2. The server portion of the staff client expects `http://hostname/xul/server` + to resolve. Issue the following commands as the *root* Linux account to + create a symbolic link pointing to the `server` subdirectory of the server + portion of the staff client that we just built using the staff client ID + 'rel_name': ++ +[source, bash] +------------------------------------------------------------------------------ +cd /openils/var/web/xul +ln -sf rel_name/server server +------------------------------------------------------------------------------ + +Change ownership of the Evergreen files +--------------------------------------- + +All files in the `/openils/` directory and subdirectories must be owned by the +`opensrf` user. Issue the following command as the *root* Linux account to +change the ownership on the files: + +[source, bash] +------------------------------------------------------------------------------ +chown -R opensrf:opensrf /openils +------------------------------------------------------------------------------ + +Configure the Apache Web server +------------------------------- + +1. Use the example configuration files in `Open-ILS/examples/apache/` to +configure your Web server for the Evergreen catalog, staff client, Web +services, and administration interfaces. Issue the following commands as the +*root* Linux account: ++ +.Debian and Ubuntu +[source,bash] +------------------------------------------------------------------------------ +cp Open-ILS/examples/apache/eg.conf /etc/apache2/sites-available/ +cp Open-ILS/examples/apache/eg_vhost.conf /etc/apache2/ +cp Open-ILS/examples/apache/startup.pl /etc/apache2/ +# Now set up SSL +mkdir /etc/apache2/ssl +cd /etc/apache2/ssl +------------------------------------------------------------------------------ ++ +.Fedora +[source,bash] +------------------------------------------------------------------------------ +cp Open-ILS/examples/apache/eg.conf /etc/httpd/conf.d/ +cp Open-ILS/examples/apache/eg_vhost.conf /etc/httpd/ +cp Open-ILS/examples/apache/startup.pl /etc/httpd/ +# Now set up SSL +mkdir /etc/httpd/ssl +cd /etc/httpd/ssl +------------------------------------------------------------------------------ ++ +2. The `openssl` command cuts a new SSL key for your Apache server. For a +production server, you should purchase a signed SSL certificate, but you can +just use a self-signed certificate and accept the warnings in the staff client +and browser during testing and development. Create an SSL key for the Apache +server by issuing the following command as the *root* Linux account: ++ +[source,bash] +------------------------------------------------------------------------------ +openssl req -new -x509 -days 365 -nodes -out server.crt -keyout server.key +------------------------------------------------------------------------------ ++ +3. As the *root* Linux account, edit the `eg.conf` file that you copied into +place. + a. Replace `Allow from 10.0.0.0/8` with `Allow from all` (to enable + access to the offline upload / execute interface from any workstation on + any network - note that you must secure this for a production instance) + b. (Fedora): Change references from the non-existent `/etc/apache2/` directory + to `/etc/httpd/`. +4. Change the user for the Apache server. + * (Debian and Ubuntu): As the *root* Linux account, edit + `/etc/apache2/envvars`. Change `export APACHE_RUN_USER=www-data` to + `export APACHE_RUN_USER=opensrf`. + * (Fedora): As the *root* Linux account , edit `/etc/httpd/conf/httpd.conf`. + Change `User apache` to `User opensrf`. +5. Configure Apache with performance settings appropriate for Evergreen: + * (Debian and Ubuntu): As the *root* Linux account, edit + `/etc/apache2/apache2.conf`: + * (Fedora): As the *root* Linux account, edit `/etc/httpd/conf/httpd.conf`: + a. Change `KeepAliveTimeout` to `1`. Higher values reduce the chance of + a request timing out unexpectedly, but increase the risk of using up + all available Apache child processes. + b. 'Optional': Change `MaxKeepAliveRequests` to `100` + c. Update the prefork configuration section to suit your environment. The + following settings apply to a busy system: ++ +[source,bash] +------------------------------------------------------------------------------ + + StartServers 20 + MinSpareServers 5 + MaxSpareServers 15 + MaxClients 150 + MaxRequestsPerChild 10000 + +------------------------------------------------------------------------------ ++ +6. (Fedora): As the *root* Linux account, edit the `/etc/httpd/eg_vhost.conf` + file to change references from the non-existent `/etc/apache2/` directory + to `/etc/httpd/`. +7. (Debian and Ubuntu): As the *root* Linux account, enable the Evergreen site: ++ +[source,bash] +------------------------------------------------------------------------------ +a2dissite default # OPTIONAL: disable the default site (the "It Works" page) +a2ensite eg.conf +------------------------------------------------------------------------------ + +Configure OpenSRF for the Evergreen application +----------------------------------------------- +There are a number of example OpenSRF configuration files in `/openils/conf/` +that you can use as a template for your Evergreen installation. Issue the +following commands as the *opensrf* Linux account: + +[source, bash] +------------------------------------------------------------------------------ +cp -b /openils/conf/opensrf_core.xml.example /openils/conf/opensrf_core.xml +cp -b /openils/conf/opensrf.xml.example /openils/conf/opensrf.xml +------------------------------------------------------------------------------ + +When you installed OpenSRF, you created four Jabber users on two +separate domains and edited the `opensrf_core.xml` file accordingly. Please +refer back to the OpenSRF README and, as the *opensrf* Linux account, edit the +Evergreen version of the `opensrf_core.xml` file using the same Jabber users +and domains as you used while installing and testing OpenSRF. + +[NOTE] +The `-b` flag tells the `cp` command to create a backup version of the +destination file. The backup version of the destination file has a tilde (`~`) +appended to the file name, so if you have forgotten the Jabber users and +domains, you can retrieve the settings from the backup version of the files. + +`eg_db_config.pl`, described in the following section, sets the database +connection information in `opensrf.xml` for you. + +Creating the Evergreen database +------------------------------- + +By default, the `Makefile.install` prerequisite installer does not install +the PostgreSQL 9 database server required by every Evergreen system; +for production use, most libraries install the PostgreSQL database server on a +dedicated machine. You can install the packages required by Debian or Ubuntu Lucid +on the machine of your choice using the following commands as the *root* +Linux account: + +.(Debian and Ubuntu Lucid) Installing PostgreSQL 9.1 server packages +[source, bash] +------------------------------------------------------------------------------ +make -f Open-ILS/src/extras/Makefile.install install_pgsql_server_backport_debs_91 +------------------------------------------------------------------------------ + +.(Ubuntu Precise) Installing PostgreSQL 9.1 server packages +[source, bash] +------------------------------------------------------------------------------ +make -f Open-ILS/src/extras/Makefile.install install_pgsql_server_debs_91 +------------------------------------------------------------------------------ + +You can install the packages required by Fedora on the machine of your choice +using the following commands as the *root* Linux account: + +.(Fedora 16) Installing PostgreSQL server packages +[source, bash] +------------------------------------------------------------------------------ +make -f Open-ILS/src/extras/Makefile.install install_fedora_pgsql_server +postgresql-setup initdb +------------------------------------------------------------------------------ + +For a standalone PostgreSQL server, install the following Perl modules as the +*root* Linux account: + +.(Debian / Ubuntu) Installing additional Perl modules on a standalone PostgreSQL 9 server +[source, bash] +------------------------------------------------------------------------------ +aptitude install gcc libxml-libxml-perl libxml-libxslt-perl +cpan Business::ISBN +cpan JSON::XS +cpan Library::CallNumber::LC +cpan MARC::Record +cpan MARC::File::XML +cpan UUID::Tiny +------------------------------------------------------------------------------ + +.(Fedora 16) Installing additional Perl modules on a standalone PostgreSQL 9 server +[source, bash] +------------------------------------------------------------------------------ +yum install gcc perl-XML-LibXML perl-XML-LibXSLT perl-Business-ISBN +cpan Library::CallNumber::LC +cpan MARC::Record +cpan MARC::File::XML +cpan UUID::Tiny +------------------------------------------------------------------------------ + +You need to create a PostgreSQL superuser to create and access the database. +Issue the following command as the *postgres* Linux account to create a new +PostgreSQL superuser named `evergreen`. When prompted, enter the new user's +password: + +[source, bash] +------------------------------------------------------------------------------ +createuser -s -P evergreen +------------------------------------------------------------------------------ + +Once you have created the *evergreen* PostgreSQL account, you also need to +create the database and schema, and configure your configuration files to point +at the database server. Issue the following command as the *root* Linux account +from inside the Evergreen source directory, replacing , , +, , and with the appropriate values for your +PostgreSQL database (where and are for the *evergreen* +PostgreSQL account you just created), and replace and +with the values you want for the *egadmin* Evergreen administrator account: + +[source, bash] +------------------------------------------------------------------------------ +perl Open-ILS/src/support-scripts/eg_db_config.pl --update-config \ + --service all --create-database --create-schema --create-offline \ + --user --password --hostname --port \ + --database --admin-user --admin-pass +------------------------------------------------------------------------------ + +This creates the database and schema and configures all of the services in +your `/openils/conf/opensrf.xml` configuration file to point to that database. +It also creates the configuration files required by the Evergreen `cgi-bin` +administration scripts, and sets the user name and password for the *egadmin* +Evergreen administrator account to your requested values. + +Creating the database on a remote server +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +In a production instance of Evergreen, your PostgreSQL server should be +installed on a dedicated server. + +PostgreSQL 9.1 and later +^^^^^^^^^^^^^^^^^^^^^^^^ +To create the database instance on a remote database server running PostgreSQL +9.1 or later, simply use the `--create-database` flag on `eg_db_config.pl`. + +For PostgreSQL 9.0 +^^^^^^^^^^^^^^^^^^ +To create the database instance on a remote database server running PostgreSQL +9.0, you can either: + + * Install the PostgreSQL contrib modules on the machine on which you + are installing the Evergreen code, and use the `--create-database` + option from that machine, or + * Copy the `Open-ILS/src/sql/Pg/create_database.sql` script to your + PostgreSQL server and invoke it as the *postgres* Linux account: ++ +[source, bash] +------------------------------------------------------------------------------ +psql -vdb_name= -vcontrib_dir=`pg_config --sharedir`/contrib -f create_database.sql +------------------------------------------------------------------------------ + +Then you can issue the `eg_db_config.pl` command as above _without_ the +`--create-database` argument to create your schema and configure your +configuration files. + +Starting Evergreen +------------------ +1. As the *root* Linux account, start the `memcached` and `ejabberd` services +(if they aren't already running): ++ +[source, bash] +------------------------------------------------------------------------------ +/etc/init.d/ejabberd start +/etc/init.d/memcached start +------------------------------------------------------------------------------ ++ +2. As the *opensrf* Linux account, start Evergreen. The `-l` flag in the +following command is only necessary if you want to force Evergreen to treat the +hostname as `localhost`; if you configured `opensrf.xml` using the real +hostname of your machine as returned by `perl -ENet::Domain 'print +Net::Domain::hostfqdn() . "\n";'`, you should not use the `-l` flag. ++ +[source, bash] +------------------------------------------------------------------------------ +osrf_ctl.sh -l -a start_all +------------------------------------------------------------------------------ ++ + ** If you receive the error message `bash: osrf_ctl.sh: command not found`, + then your environment variable `PATH` does not include the `/openils/bin` + directory; this should have been set in the *opensrf* Linux account's + `.bashrc` configuration file. To manually set the `PATH` variable, edit the + configuration file `~/.bashrc` as the *opensrf* Linux account and add the + following line: ++ +[source, bash] +------------------------------------------------------------------------------ +export PATH=$PATH:/openils/bin +------------------------------------------------------------------------------ ++ +3. As the *opensrf* Linux account, generate the Web files needed by the staff + client and catalogue and update the organization unit proximity (you need to do + this the first time you start Evergreen, and after that each time you change + the library hierarchy in `config.cgi`): ++ +[source, bash] +------------------------------------------------------------------------------ +autogen.sh -u +------------------------------------------------------------------------------ ++ +4. As the *root* Linux account, restart the Apache Web server: ++ +[source, bash] +------------------------------------------------------------------------------ +/etc/init.d/apache2 restart +------------------------------------------------------------------------------ ++ +If the Apache Web server was running when you started the OpenSRF services, you +might not be able to successfully log in to the OPAC or staff client until the +Apache Web server is restarted. + +Testing connections to Evergreen +-------------------------------- + +Once you have installed and started Evergreen, test your connection to +Evergreen via `srfsh`. As the *opensrf* Linux account, issue the following +commands to start `srfsh` and try to log onto the Evergreen server using the +*egadmin* Evergreen administrator user name and password that you set using the +`eg_db_config.pl` command: + +[source, bash] +------------------------------------------------------------------------------ +/openils/bin/srfsh +srfsh% login +------------------------------------------------------------------------------ + +You should see a result like: + + Received Data: "250bf1518c7527a03249858687714376" + ------------------------------------ + Request Completed Successfully + Request Time in seconds: 0.045286 + ------------------------------------ + + Received Data: { + "ilsevent":0, + "textcode":"SUCCESS", + "desc":" ", + "pid":21616, + "stacktrace":"oils_auth.c:304", + "payload":{ + "authtoken":"e5f9827cc0f93b503a1cc66bee6bdd1a", + "authtime":420 + } + + } + + ------------------------------------ + Request Completed Successfully + Request Time in seconds: 1.336568 + ------------------------------------ + +If this does not work, it's time to do some troubleshooting. + + * As the *opensrf* Linux acccount, run the `settings-tester.pl` script to see + if it finds any system configuration problems. The script is found at + `Open-ILS/src/support-scripts/settings-tester.pl` in the Evergreen source + tree. + * Follow the steps in the http://evergreen-ils.org/dokuwiki/doku.php?id=troubleshooting:checking_for_errors[troubleshooting guide]. + * If you have faithfully followed the entire set of installation steps + listed here, you are probably extremely close to a working system. + Gather your configuration files and log files and contact the + http://open-ils.org/listserv.php[Evergreen development mailing list] + for assistance before making any drastic changes to your system + configuration. + +Getting help +------------ + +Need help installing or using Evergreen? Join the mailing lists at +http://evergreen-ils.org/listserv.php or contact us on the Freenode +IRC network on the #evergreen channel. + +License +------- +This work is licensed under the Creative Commons Attribution-ShareAlike 3.0 +Unported License. To view a copy of this license, visit +http://creativecommons.org/licenses/by-sa/3.0/ or send a letter to Creative +Commons, 444 Castro Street, Suite 900, Mountain View, California, 94041, USA. diff --git a/docs/installation/server_upgrade.txt b/docs/installation/server_upgrade.txt new file mode 100644 index 0000000000..f8c25ff301 --- /dev/null +++ b/docs/installation/server_upgrade.txt @@ -0,0 +1,244 @@ +Upgrading the Evergreen Server +------------------------------ +Before upgrading, it is important to carefully plan an upgrade strategy to minimize system downtime and service interruptions. +All of the steps in this chapter are to be completed from the command line. + +Software Prerequisites: +~~~~~~~~~~~~~~~~~~~~~~~ + + * **PostgreSQL**: Version 9.1 is recommended. The minimum supported version + is 9.0. + * **Linux**: Evergreen 2.0 has been tested on Debian Squeeze (6.0), + Ubuntu Lucid Lynx (10.04) and Ubuntu Precise Pangolin (12.04). If you are + running an older version of these distributions, you may want to upgrade + before upgrading Evergreen. For instructions on upgrading these + distributions, visit the Debian or Ubuntu websites. + * **OpenSRF**: The minimum supported version of OpenSRF is 2.1.0. + +In the following instructions, you are asked to perform certain steps as either the root or opensrf user. + + * **Debian**: To become the root user, issue the `su` command and enter the password of the root user. + * **Ubuntu**: To become the root user, issue the `sudo su` command and enter the password of your current user. + +To switch from the root user to a different user, issue the `su - [user]` +command; for example, `su - opensrf`. Once you have become a non-root user, to +become the root user again simply issue the `exit` command. + +[CAUTION] +Pay attention to error output as you run these scripts. If you encounter errors +that you cannot resolve yourself through additional troubleshooting, please +report the errors to the http://evergreen-ils.org/listserv.php[Evergreen +Technical Discussion List]. + +Upgrade the Evergreen database schema +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +The upgrade of the Evergreen database schema is the lengthiest part of the +upgrade process for sites with a significant amount of production data. + +Before running the upgrade script against your production Evergreen database, +back up your database, restore it to a test server, and run the upgrade script +against the test server. This enables you to determine how long the upgrade +will take and whether any local customizations present problems for the +stock upgrade script that require further tailoring of the upgrade script. +The backup also enables you to cleanly restore your production data if +anything goes wrong during the upgrade. + +Run the following script as a user with the ability to connect to the +database server. Adjust the arguments to the `psql` command to reflect your +database server connection information: + +[source, bash] +---------------------------------------------------------- +cd /home/opensrf/Evergreen-ILS-2.1-rc1/Open-ILS/src/sql/Pg +psql -U evergreen -h localhost -f version_upgrade/2.1-2.2-upgrade-db.sql evergreen +---------------------------------------------------------- + +Upgrade the Evergreen code +~~~~~~~~~~~~~~~~~~~~~~~~~~ +The following steps guide you through a simplistic upgrade of a production +server. You must adjust these steps to accommodate your customizations such +as catalogue skins. + +. Stop Evergreen and back up your data: + .. As root, stop the Apache web server. + .. As the opensrf user, stop all Evergreen and OpenSRF services: ++ +[source, bash] +----------------------------- +osrf_ctl.sh -l -a stop_all +----------------------------- ++ + .. Back up the /openils directory. +. Upgrade OpenSRF. Download and install the latest version of OpenSRF from +the http://evergreen-ils.org/opensrf.php[OpenSRF download page]. +. As the opensrf user, download and extract Evergreen 2.2: ++ +[source, bash] +----------------------------------------------- +wget http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.2-rc1.tar.gz +tar xzf Evergreen-ILS-2.2-rc1.tar.gz +----------------------------------------------- ++ +[NOTE] +For the latest edition of Evergreen, check the http://evergreen-ils.org/downloads.php[Evergreen download page] and adjust upgrading instructions accordingly. ++ +. As the root user, install the prerequisites: ++ +[source, bash] +---------------------------------------------- +cd /home/opensrf/Evergreen-ILS-2.2-rc1 +--------------------------------------------- ++ +On the next command, replace `[distribution]` with one of these values for your +distribution of Debian or Ubuntu: + + * `debian-squeeze` for Debian Squeeze (6.0) + * `ubuntu-lucid` for Ubuntu Lucid Lynx (10.04) + * `ubuntu-precise` for Ubuntu Precise Pangolin (12.04) ++ +[source, bash] +------------------------------------------------------------ +make -f Open-ILS/src/extras/Makefile.install [distribution] +------------------------------------------------------------ ++ +. As the opensrf user, configure and compile Evergreen: ++ +[source, bash] +------------------------------------------------------------ +cd /home/opensrf/Evergreen-ILS-2.2-rc1 +./configure --prefix=/openils --sysconfdir=/openils/conf +make +------------------------------------------------------------ ++ +. As the root user, install Evergreen: ++ +[source, bash] +------------------------------------------------------------ +cd /home/opensrf/Evergreen-ILS-2.2-rc1 +make STAFF_CLIENT_STAMP_ID=rel_2_2_rc1 install +------------------------------------------------------------ ++ +. As the root user, change all files to be owned by the opensrf user and group: ++ +[source, bash] +------------------------------------------------------------ +chown -R opensrf:opensrf /openils +------------------------------------------------------------ ++ +. As the opensrf user, update the configuration files: ++ +[source, bash] +----------------------------------------------------------- +cd /home/opensrf/Evergreen-ILS-2.2-rc1 + +perl Open-ILS/src/support-scripts/eg_db_config.pl \ +--create-offline --user evergreen --password evergreen \ +--hostname localhost --port 5432 --database evergreen +---------------------------------------------------------- ++ +. As the opensrf user, update the server symlink in /openils/var/web/xul/: ++ +[source, bash] +----------------------------------------------------------- +cd /openils/var/web/xul/ +rm server +ln -s rel_2_2_rc1/server +---------------------------------------------------------- ++ +. As the opensrf user, update opensrf_core.xml and opensrf.xml by copying the + new example files (/openils/conf/opensrf_core.xml.example and + /openils/conf/opensrf.xml). ++ +[source, bash] +---------------------------------------------------------- +cp /openils/conf/opensrf_core.xml.example /openils/conf/opensrf_core.xml +cp /openils/conf/opensrf.xml.example /openils/conf/opensrf.xml +---------------------------------------------------------- ++ +[CAUTION] +Copying these configuration files will remove any customizations you have made to them. Remember to redo your customizations after copying them. ++ +. Update Apache files: ++ +[CAUTION] +Copying these Apache configuration files will remove any customizations you have made to them. Remember to redo your customizations after copying them. +For example, if you purchased an SSL certificate, you will need to edit eg.conf to point to the appropriate SSL certificate files. ++ +.. Update /etc/apache2/startup.pl by copying the example from Open-ILS/examples/apache/startup.pl. +.. Update /etc/apache2/eg_vhost.conf by copying the example from Open-ILS/examples/apache/eg_vhost.conf. +.. Update /etc/apache2/sites-available/eg.conf by copying the example from Open-ILS/ examples/apache/eg.conf. +. Update opensrf.xml with the database connection info: ++ +As the opensrf user, if you are happy with the default settings in +opensrf.xml.example, then: ++ +[source, bash] +------------------------------------------------------------------------- +cp -b /openils/conf/opensrf.xml.example /openils/conf/opensrf.xml +cd /home/opensrf/Evergreen-ILS-2.2-rc1 +perl Open-ILS/src/support-scripts/eg_db_config.pl --update-config --service all \ +--database evergreen --host localhost --user evergreen --password evergreen +------------------------------------------------------------------------- ++ +Otherwise, compare /openils/conf/opensrf.xml with /openils/conf/opensrf.xml.example and manually copy the new pieces into place in your existing opensrf.xml file + +Restart Evergreen and Test +~~~~~~~~~~~~~~~~~~~~~~~~~~ +. As the opensrf user, start all Evergreen and OpenSRF services: ++ +[source, bash] +-------------------------------------------------------------- +osrf_ctl.sh -l -a start_all +-------------------------------------------------------------- ++ +. As the opensrf user, run autogen to refresh the static organizational data files: ++ +[source, bash] +-------------------------------------------------------------- +cd /openils/bin +../autogen.sh +-------------------------------------------------------------- ++ +. Start srfsh and try logging in using your Evergreen username and password: ++ +[source, bash] +-------------------------------------------------------------- +/openils/bin/srfsh +srfsh% login username password +-------------------------------------------------------------- ++ +You should see a result like: ++ +[source, bash] +------------------------------------------------------ +Received Data: "250bf1518c7527a03249858687714376" + ------------------------------------ + Request Completed Successfully + Request Time in seconds: 0.045286 + ------------------------------------ + + Received Data: { + "ilsevent":0, + "textcode":"SUCCESS", + "desc":" ", + "pid":21616, + "stacktrace":"oils_auth.c:304", + "payload":{ + "authtoken":"e5f9827cc0f93b503a1cc66bee6bdd1a", + "authtime":420 + } + + } + + ------------------------------------ + Request Completed Successfully + Request Time in seconds: 1.336568 + ------------------------------------ +---------------------------------------------------------- ++ +If this does not work, it's time to do some troubleshooting. ++ +. As the root user, start the Apache web server. ++ +If you encounter errors, refer to the troubleshooting section of this documentation for tips on finding solutions and seeking further assistance +from the Evergreen community. diff --git a/docs/installation/system_requirements.txt b/docs/installation/system_requirements.txt new file mode 100644 index 0000000000..765da132e2 --- /dev/null +++ b/docs/installation/system_requirements.txt @@ -0,0 +1,32 @@ +System Requirements +------------------- + +Server Minimum Requirements +~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +The following are the base requirements setting Evergreen up on a test server: + + * An available desktop, server or virtual image + * 1GB RAM, or more if your server also runs a graphical desktop + * Linux Operating System + * Ports 80 and 443 should be opened in your firewall for TCP connections to allow OPAC and staff client connections to the Evergreen server. + +Staff Client Requirements +~~~~~~~~~~~~~~~~~~~~~~~~~ + +Staff terminals connect to the central database using the Evergreen staff client, available for download from The Evergreen download page. +The staff client must be installed on each staff workstation and requires at minimum: + + * Windows (XP, Vista, or 7), Mac OS X, or Linux operating system + * a reliable high speed Internet connection + * 512Mb of RAM + * The staff client uses the TCP protocal on ports 80 and 443 to communicate with the Evergreen server. + +*Barcode Scanners* + +Evergreen will work with virtually any barcode scanner – if it worked with your legacy system it should work on Evergreen. + +*Printers* + +Evergreen can use any printer configured for your terminal to print receipts, check-out slips, holds lists, etc. The single exception is spine label printing, +which is still under development. Evergreen currently formats spine labels for output to a label roll printer. If you do not have a roll printer manual formatting may be required. diff --git a/docs/licensing.txt b/docs/licensing.txt new file mode 100644 index 0000000000..a9f2ec39d5 --- /dev/null +++ b/docs/licensing.txt @@ -0,0 +1,13 @@ +Licensing +========= + +Creative Commons License +------------------------ + +image::media/ccbysa.png["CC-BY-SA",link="http://creativecommons.org/licenses/by-sa/3.0/"] + +This work is licensed under a +link:http://creativecommons.org/licenses/by-sa/3.0/[Creative +Commons Attribution-ShareAlike 3.0 Unported License]. + + diff --git a/docs/media/1.png b/docs/media/1.png new file mode 100644 index 0000000000..7d473430b7 Binary files /dev/null and b/docs/media/1.png differ diff --git a/docs/media/10.png b/docs/media/10.png new file mode 100644 index 0000000000..997bbc8246 Binary files /dev/null and b/docs/media/10.png differ diff --git a/docs/media/11.png b/docs/media/11.png new file mode 100644 index 0000000000..ce47dac3f5 Binary files /dev/null and b/docs/media/11.png differ diff --git a/docs/media/12.png b/docs/media/12.png new file mode 100644 index 0000000000..31daf4e2f2 Binary files /dev/null and b/docs/media/12.png differ diff --git a/docs/media/13.png b/docs/media/13.png new file mode 100644 index 0000000000..14021a89c2 Binary files /dev/null and b/docs/media/13.png differ diff --git a/docs/media/14.png b/docs/media/14.png new file mode 100644 index 0000000000..64014b75fe Binary files /dev/null and b/docs/media/14.png differ diff --git a/docs/media/15.png b/docs/media/15.png new file mode 100644 index 0000000000..0d65765fcf Binary files /dev/null and b/docs/media/15.png differ diff --git a/docs/media/2.png b/docs/media/2.png new file mode 100644 index 0000000000..5d09341b2f Binary files /dev/null and b/docs/media/2.png differ diff --git a/docs/media/3.png b/docs/media/3.png new file mode 100644 index 0000000000..ef7b700471 Binary files /dev/null and b/docs/media/3.png differ diff --git a/docs/media/4.png b/docs/media/4.png new file mode 100644 index 0000000000..adb8364eb5 Binary files /dev/null and b/docs/media/4.png differ diff --git a/docs/media/5.png b/docs/media/5.png new file mode 100644 index 0000000000..4d7eb46002 Binary files /dev/null and b/docs/media/5.png differ diff --git a/docs/media/6.png b/docs/media/6.png new file mode 100644 index 0000000000..0ba694af6c Binary files /dev/null and b/docs/media/6.png differ diff --git a/docs/media/7.png b/docs/media/7.png new file mode 100644 index 0000000000..472e96f8ac Binary files /dev/null and b/docs/media/7.png differ diff --git a/docs/media/8.png b/docs/media/8.png new file mode 100644 index 0000000000..5e60973c21 Binary files /dev/null and b/docs/media/8.png differ diff --git a/docs/media/9.png b/docs/media/9.png new file mode 100644 index 0000000000..a0676d26cc Binary files /dev/null and b/docs/media/9.png differ diff --git a/docs/media/Authority_Control_Sets1.jpg b/docs/media/Authority_Control_Sets1.jpg new file mode 100644 index 0000000000..9ecdc58489 Binary files /dev/null and b/docs/media/Authority_Control_Sets1.jpg differ diff --git a/docs/media/Authority_Control_Sets1.jpg.1 b/docs/media/Authority_Control_Sets1.jpg.1 new file mode 100644 index 0000000000..9ecdc58489 Binary files /dev/null and b/docs/media/Authority_Control_Sets1.jpg.1 differ diff --git a/docs/media/Authority_Control_Sets2.jpg b/docs/media/Authority_Control_Sets2.jpg new file mode 100644 index 0000000000..4bea42d834 Binary files /dev/null and b/docs/media/Authority_Control_Sets2.jpg differ diff --git a/docs/media/Authority_Control_Sets2.jpg.1 b/docs/media/Authority_Control_Sets2.jpg.1 new file mode 100644 index 0000000000..4bea42d834 Binary files /dev/null and b/docs/media/Authority_Control_Sets2.jpg.1 differ diff --git a/docs/media/Authority_Control_Sets3.jpg b/docs/media/Authority_Control_Sets3.jpg new file mode 100644 index 0000000000..50beca2a86 Binary files /dev/null and b/docs/media/Authority_Control_Sets3.jpg differ diff --git a/docs/media/Authority_Control_Sets3.jpg.1 b/docs/media/Authority_Control_Sets3.jpg.1 new file mode 100644 index 0000000000..50beca2a86 Binary files /dev/null and b/docs/media/Authority_Control_Sets3.jpg.1 differ diff --git a/docs/media/Authority_Control_Sets4.jpg b/docs/media/Authority_Control_Sets4.jpg new file mode 100644 index 0000000000..b563a56400 Binary files /dev/null and b/docs/media/Authority_Control_Sets4.jpg differ diff --git a/docs/media/Authority_Control_Sets4.jpg.1 b/docs/media/Authority_Control_Sets4.jpg.1 new file mode 100644 index 0000000000..b563a56400 Binary files /dev/null and b/docs/media/Authority_Control_Sets4.jpg.1 differ diff --git a/docs/media/Authority_Control_Sets5.jpg b/docs/media/Authority_Control_Sets5.jpg new file mode 100644 index 0000000000..a853f4b56c Binary files /dev/null and b/docs/media/Authority_Control_Sets5.jpg differ diff --git a/docs/media/Authority_Control_Sets5.jpg.1 b/docs/media/Authority_Control_Sets5.jpg.1 new file mode 100644 index 0000000000..a853f4b56c Binary files /dev/null and b/docs/media/Authority_Control_Sets5.jpg.1 differ diff --git a/docs/media/Authority_Control_Sets6.jpg b/docs/media/Authority_Control_Sets6.jpg new file mode 100644 index 0000000000..646a4fa9ce Binary files /dev/null and b/docs/media/Authority_Control_Sets6.jpg differ diff --git a/docs/media/Authority_Control_Sets6.jpg.1 b/docs/media/Authority_Control_Sets6.jpg.1 new file mode 100644 index 0000000000..646a4fa9ce Binary files /dev/null and b/docs/media/Authority_Control_Sets6.jpg.1 differ diff --git a/docs/media/Authority_Control_Sets7.jpg b/docs/media/Authority_Control_Sets7.jpg new file mode 100644 index 0000000000..7f318024ee Binary files /dev/null and b/docs/media/Authority_Control_Sets7.jpg differ diff --git a/docs/media/Authority_Control_Sets7.jpg.1 b/docs/media/Authority_Control_Sets7.jpg.1 new file mode 100644 index 0000000000..7f318024ee Binary files /dev/null and b/docs/media/Authority_Control_Sets7.jpg.1 differ diff --git a/docs/media/Authority_Control_Sets8.jpg b/docs/media/Authority_Control_Sets8.jpg new file mode 100644 index 0000000000..b4d776a1a1 Binary files /dev/null and b/docs/media/Authority_Control_Sets8.jpg differ diff --git a/docs/media/Authority_Control_Sets8.jpg.1 b/docs/media/Authority_Control_Sets8.jpg.1 new file mode 100644 index 0000000000..b4d776a1a1 Binary files /dev/null and b/docs/media/Authority_Control_Sets8.jpg.1 differ diff --git a/docs/media/Authority_Control_Sets9.jpg b/docs/media/Authority_Control_Sets9.jpg new file mode 100644 index 0000000000..d9d11c8ff6 Binary files /dev/null and b/docs/media/Authority_Control_Sets9.jpg differ diff --git a/docs/media/Authority_Control_Sets9.jpg.1 b/docs/media/Authority_Control_Sets9.jpg.1 new file mode 100644 index 0000000000..d9d11c8ff6 Binary files /dev/null and b/docs/media/Authority_Control_Sets9.jpg.1 differ diff --git a/docs/media/Auto_Suggest_in_Catalog_Search1.jpg b/docs/media/Auto_Suggest_in_Catalog_Search1.jpg new file mode 100644 index 0000000000..6cbf623590 Binary files /dev/null and b/docs/media/Auto_Suggest_in_Catalog_Search1.jpg differ diff --git a/docs/media/Auto_Suggest_in_Catalog_Search2.jpg b/docs/media/Auto_Suggest_in_Catalog_Search2.jpg new file mode 100644 index 0000000000..c17abdb305 Binary files /dev/null and b/docs/media/Auto_Suggest_in_Catalog_Search2.jpg differ diff --git a/docs/media/Batch_Importing_MARC_Records1.jpg b/docs/media/Batch_Importing_MARC_Records1.jpg new file mode 100644 index 0000000000..ae0962afbb Binary files /dev/null and b/docs/media/Batch_Importing_MARC_Records1.jpg differ diff --git a/docs/media/Batch_Importing_MARC_Records10.jpg b/docs/media/Batch_Importing_MARC_Records10.jpg new file mode 100644 index 0000000000..089c9a1ed2 Binary files /dev/null and b/docs/media/Batch_Importing_MARC_Records10.jpg differ diff --git a/docs/media/Batch_Importing_MARC_Records11.jpg b/docs/media/Batch_Importing_MARC_Records11.jpg new file mode 100644 index 0000000000..089c9a1ed2 Binary files /dev/null and b/docs/media/Batch_Importing_MARC_Records11.jpg differ diff --git a/docs/media/Batch_Importing_MARC_Records12.jpg b/docs/media/Batch_Importing_MARC_Records12.jpg new file mode 100644 index 0000000000..d51536e5d2 Binary files /dev/null and b/docs/media/Batch_Importing_MARC_Records12.jpg differ diff --git a/docs/media/Batch_Importing_MARC_Records13.jpg b/docs/media/Batch_Importing_MARC_Records13.jpg new file mode 100644 index 0000000000..d51536e5d2 Binary files /dev/null and b/docs/media/Batch_Importing_MARC_Records13.jpg differ diff --git a/docs/media/Batch_Importing_MARC_Records14.jpg b/docs/media/Batch_Importing_MARC_Records14.jpg new file mode 100644 index 0000000000..f192db2533 Binary files /dev/null and b/docs/media/Batch_Importing_MARC_Records14.jpg differ diff --git a/docs/media/Batch_Importing_MARC_Records15.jpg b/docs/media/Batch_Importing_MARC_Records15.jpg new file mode 100644 index 0000000000..1413bc5c77 Binary files /dev/null and b/docs/media/Batch_Importing_MARC_Records15.jpg differ diff --git a/docs/media/Batch_Importing_MARC_Records2.jpg b/docs/media/Batch_Importing_MARC_Records2.jpg new file mode 100644 index 0000000000..b022f873ae Binary files /dev/null and b/docs/media/Batch_Importing_MARC_Records2.jpg differ diff --git a/docs/media/Batch_Importing_MARC_Records3.jpg b/docs/media/Batch_Importing_MARC_Records3.jpg new file mode 100644 index 0000000000..124712c72e Binary files /dev/null and b/docs/media/Batch_Importing_MARC_Records3.jpg differ diff --git a/docs/media/Batch_Importing_MARC_Records4.jpg b/docs/media/Batch_Importing_MARC_Records4.jpg new file mode 100644 index 0000000000..4d556a1bfb Binary files /dev/null and b/docs/media/Batch_Importing_MARC_Records4.jpg differ diff --git a/docs/media/Batch_Importing_MARC_Records5.jpg b/docs/media/Batch_Importing_MARC_Records5.jpg new file mode 100644 index 0000000000..3410561afa Binary files /dev/null and b/docs/media/Batch_Importing_MARC_Records5.jpg differ diff --git a/docs/media/Batch_Importing_MARC_Records6.jpg b/docs/media/Batch_Importing_MARC_Records6.jpg new file mode 100644 index 0000000000..b0dfc8a7a1 Binary files /dev/null and b/docs/media/Batch_Importing_MARC_Records6.jpg differ diff --git a/docs/media/Batch_Importing_MARC_Records7.jpg b/docs/media/Batch_Importing_MARC_Records7.jpg new file mode 100644 index 0000000000..e26303ea81 Binary files /dev/null and b/docs/media/Batch_Importing_MARC_Records7.jpg differ diff --git a/docs/media/Batch_Importing_MARC_Records8.jpg b/docs/media/Batch_Importing_MARC_Records8.jpg new file mode 100644 index 0000000000..c8cf321bc2 Binary files /dev/null and b/docs/media/Batch_Importing_MARC_Records8.jpg differ diff --git a/docs/media/Batch_Importing_MARC_Records9.jpg b/docs/media/Batch_Importing_MARC_Records9.jpg new file mode 100644 index 0000000000..315f5b938a Binary files /dev/null and b/docs/media/Batch_Importing_MARC_Records9.jpg differ diff --git a/docs/media/Call_Number_Prefixes_and_Suffixes_2_21.jpg b/docs/media/Call_Number_Prefixes_and_Suffixes_2_21.jpg new file mode 100644 index 0000000000..825b46c2f6 Binary files /dev/null and b/docs/media/Call_Number_Prefixes_and_Suffixes_2_21.jpg differ diff --git a/docs/media/Call_Number_Prefixes_and_Suffixes_2_22.jpg b/docs/media/Call_Number_Prefixes_and_Suffixes_2_22.jpg new file mode 100644 index 0000000000..1d3f8b621b Binary files /dev/null and b/docs/media/Call_Number_Prefixes_and_Suffixes_2_22.jpg differ diff --git a/docs/media/Call_Number_Prefixes_and_Suffixes_2_22.jpg.1 b/docs/media/Call_Number_Prefixes_and_Suffixes_2_22.jpg.1 new file mode 100644 index 0000000000..1d3f8b621b Binary files /dev/null and b/docs/media/Call_Number_Prefixes_and_Suffixes_2_22.jpg.1 differ diff --git a/docs/media/Customizable_Toolbar1.jpg b/docs/media/Customizable_Toolbar1.jpg new file mode 100644 index 0000000000..5bd5f53639 Binary files /dev/null and b/docs/media/Customizable_Toolbar1.jpg differ diff --git a/docs/media/Customizable_Toolbar2.jpg b/docs/media/Customizable_Toolbar2.jpg new file mode 100644 index 0000000000..3aed02b630 Binary files /dev/null and b/docs/media/Customizable_Toolbar2.jpg differ diff --git a/docs/media/Customizable_Toolbar3.jpg b/docs/media/Customizable_Toolbar3.jpg new file mode 100644 index 0000000000..ae4cbbf1ba Binary files /dev/null and b/docs/media/Customizable_Toolbar3.jpg differ diff --git a/docs/media/Customizable_Toolbar4.jpg b/docs/media/Customizable_Toolbar4.jpg new file mode 100644 index 0000000000..e5c1399010 Binary files /dev/null and b/docs/media/Customizable_Toolbar4.jpg differ diff --git a/docs/media/Double_Click1.jpg b/docs/media/Double_Click1.jpg new file mode 100644 index 0000000000..87bd0b514c Binary files /dev/null and b/docs/media/Double_Click1.jpg differ diff --git a/docs/media/Double_Click2.jpg b/docs/media/Double_Click2.jpg new file mode 100644 index 0000000000..0b94ba07fa Binary files /dev/null and b/docs/media/Double_Click2.jpg differ diff --git a/docs/media/Double_Click3.jpg b/docs/media/Double_Click3.jpg new file mode 100644 index 0000000000..0b94ba07fa Binary files /dev/null and b/docs/media/Double_Click3.jpg differ diff --git a/docs/media/My_Lists1.jpg b/docs/media/My_Lists1.jpg new file mode 100644 index 0000000000..d0eded2bd5 Binary files /dev/null and b/docs/media/My_Lists1.jpg differ diff --git a/docs/media/My_Lists3.jpg b/docs/media/My_Lists3.jpg new file mode 100644 index 0000000000..b3fdf1fb1a Binary files /dev/null and b/docs/media/My_Lists3.jpg differ diff --git a/docs/media/My_Lists4.jpg b/docs/media/My_Lists4.jpg new file mode 100644 index 0000000000..97a22cb355 Binary files /dev/null and b/docs/media/My_Lists4.jpg differ diff --git a/docs/media/My_Lists5.jpg b/docs/media/My_Lists5.jpg new file mode 100644 index 0000000000..cc02d75b43 Binary files /dev/null and b/docs/media/My_Lists5.jpg differ diff --git a/docs/media/My_Lists6.jpg b/docs/media/My_Lists6.jpg new file mode 100644 index 0000000000..cb08f337a7 Binary files /dev/null and b/docs/media/My_Lists6.jpg differ diff --git a/docs/media/My_Lists7.jpg b/docs/media/My_Lists7.jpg new file mode 100644 index 0000000000..ac1645bc30 Binary files /dev/null and b/docs/media/My_Lists7.jpg differ diff --git a/docs/media/New_Tab_Button1.jpg b/docs/media/New_Tab_Button1.jpg new file mode 100644 index 0000000000..b2d261acae Binary files /dev/null and b/docs/media/New_Tab_Button1.jpg differ diff --git a/docs/media/Overlay_Existing_Record_via_Z39_50_Import1.jpg b/docs/media/Overlay_Existing_Record_via_Z39_50_Import1.jpg new file mode 100644 index 0000000000..33e96b56e1 Binary files /dev/null and b/docs/media/Overlay_Existing_Record_via_Z39_50_Import1.jpg differ diff --git a/docs/media/Overlay_Existing_Record_via_Z39_50_Import2.jpg b/docs/media/Overlay_Existing_Record_via_Z39_50_Import2.jpg new file mode 100644 index 0000000000..32da4092cc Binary files /dev/null and b/docs/media/Overlay_Existing_Record_via_Z39_50_Import2.jpg differ diff --git a/docs/media/Overlay_Existing_Record_via_Z39_50_Import3.jpg b/docs/media/Overlay_Existing_Record_via_Z39_50_Import3.jpg new file mode 100644 index 0000000000..e6b563b620 Binary files /dev/null and b/docs/media/Overlay_Existing_Record_via_Z39_50_Import3.jpg differ diff --git a/docs/media/Overlay_Existing_Record_via_Z39_50_Import4.jpg b/docs/media/Overlay_Existing_Record_via_Z39_50_Import4.jpg new file mode 100644 index 0000000000..bb6049bb87 Binary files /dev/null and b/docs/media/Overlay_Existing_Record_via_Z39_50_Import4.jpg differ diff --git a/docs/media/Overlay_Existing_Record_via_Z39_50_Import5.jpg b/docs/media/Overlay_Existing_Record_via_Z39_50_Import5.jpg new file mode 100644 index 0000000000..96c2169d28 Binary files /dev/null and b/docs/media/Overlay_Existing_Record_via_Z39_50_Import5.jpg differ diff --git a/docs/media/Overlay_Existing_Record_via_Z39_50_Import6.jpg b/docs/media/Overlay_Existing_Record_via_Z39_50_Import6.jpg new file mode 100644 index 0000000000..37b9a8ed15 Binary files /dev/null and b/docs/media/Overlay_Existing_Record_via_Z39_50_Import6.jpg differ diff --git a/docs/media/Receive_Items_From_an_Invoice1.jpg b/docs/media/Receive_Items_From_an_Invoice1.jpg new file mode 100644 index 0000000000..120894cf1b Binary files /dev/null and b/docs/media/Receive_Items_From_an_Invoice1.jpg differ diff --git a/docs/media/Receive_Items_From_an_Invoice2.jpg b/docs/media/Receive_Items_From_an_Invoice2.jpg new file mode 100644 index 0000000000..266610b8c2 Binary files /dev/null and b/docs/media/Receive_Items_From_an_Invoice2.jpg differ diff --git a/docs/media/Receive_Items_From_an_Invoice3.jpg b/docs/media/Receive_Items_From_an_Invoice3.jpg new file mode 100644 index 0000000000..a9005da372 Binary files /dev/null and b/docs/media/Receive_Items_From_an_Invoice3.jpg differ diff --git a/docs/media/Receive_Items_From_an_Invoice4.jpg b/docs/media/Receive_Items_From_an_Invoice4.jpg new file mode 100644 index 0000000000..60f7eb1043 Binary files /dev/null and b/docs/media/Receive_Items_From_an_Invoice4.jpg differ diff --git a/docs/media/Receive_Items_From_an_Invoice5.jpg b/docs/media/Receive_Items_From_an_Invoice5.jpg new file mode 100644 index 0000000000..bd9a45b7e5 Binary files /dev/null and b/docs/media/Receive_Items_From_an_Invoice5.jpg differ diff --git a/docs/media/Receive_Items_From_an_Invoice6.jpg b/docs/media/Receive_Items_From_an_Invoice6.jpg new file mode 100644 index 0000000000..907f4f185e Binary files /dev/null and b/docs/media/Receive_Items_From_an_Invoice6.jpg differ diff --git a/docs/media/Receive_Items_From_an_Invoice7.jpg b/docs/media/Receive_Items_From_an_Invoice7.jpg new file mode 100644 index 0000000000..77785d506b Binary files /dev/null and b/docs/media/Receive_Items_From_an_Invoice7.jpg differ diff --git a/docs/media/Restrict_Z39_50_Sources_by_Permission_Group1.jpg b/docs/media/Restrict_Z39_50_Sources_by_Permission_Group1.jpg new file mode 100644 index 0000000000..7be1b6f554 Binary files /dev/null and b/docs/media/Restrict_Z39_50_Sources_by_Permission_Group1.jpg differ diff --git a/docs/media/Restrict_Z39_50_Sources_by_Permission_Group2.jpg b/docs/media/Restrict_Z39_50_Sources_by_Permission_Group2.jpg new file mode 100644 index 0000000000..107f24bc0e Binary files /dev/null and b/docs/media/Restrict_Z39_50_Sources_by_Permission_Group2.jpg differ diff --git a/docs/media/Restrict_Z39_50_Sources_by_Permission_Group3.jpg b/docs/media/Restrict_Z39_50_Sources_by_Permission_Group3.jpg new file mode 100644 index 0000000000..fd84093379 Binary files /dev/null and b/docs/media/Restrict_Z39_50_Sources_by_Permission_Group3.jpg differ diff --git a/docs/media/SMS_Text_Messaging1.jpg b/docs/media/SMS_Text_Messaging1.jpg new file mode 100644 index 0000000000..6bbfa99e31 Binary files /dev/null and b/docs/media/SMS_Text_Messaging1.jpg differ diff --git a/docs/media/SMS_Text_Messaging10.jpg b/docs/media/SMS_Text_Messaging10.jpg new file mode 100644 index 0000000000..ec9da2715e Binary files /dev/null and b/docs/media/SMS_Text_Messaging10.jpg differ diff --git a/docs/media/SMS_Text_Messaging11.jpg b/docs/media/SMS_Text_Messaging11.jpg new file mode 100644 index 0000000000..fea6a7098f Binary files /dev/null and b/docs/media/SMS_Text_Messaging11.jpg differ diff --git a/docs/media/SMS_Text_Messaging12.jpg b/docs/media/SMS_Text_Messaging12.jpg new file mode 100644 index 0000000000..cf012f0ff4 Binary files /dev/null and b/docs/media/SMS_Text_Messaging12.jpg differ diff --git a/docs/media/SMS_Text_Messaging13.jpg b/docs/media/SMS_Text_Messaging13.jpg new file mode 100644 index 0000000000..541fc26811 Binary files /dev/null and b/docs/media/SMS_Text_Messaging13.jpg differ diff --git a/docs/media/SMS_Text_Messaging2.jpg b/docs/media/SMS_Text_Messaging2.jpg new file mode 100644 index 0000000000..81f1ba021c Binary files /dev/null and b/docs/media/SMS_Text_Messaging2.jpg differ diff --git a/docs/media/SMS_Text_Messaging3.jpg b/docs/media/SMS_Text_Messaging3.jpg new file mode 100644 index 0000000000..f03f42e5a9 Binary files /dev/null and b/docs/media/SMS_Text_Messaging3.jpg differ diff --git a/docs/media/SMS_Text_Messaging4.jpg b/docs/media/SMS_Text_Messaging4.jpg new file mode 100644 index 0000000000..ef001919d4 Binary files /dev/null and b/docs/media/SMS_Text_Messaging4.jpg differ diff --git a/docs/media/SMS_Text_Messaging5.jpg b/docs/media/SMS_Text_Messaging5.jpg new file mode 100644 index 0000000000..94b7913afc Binary files /dev/null and b/docs/media/SMS_Text_Messaging5.jpg differ diff --git a/docs/media/SMS_Text_Messaging6.jpg b/docs/media/SMS_Text_Messaging6.jpg new file mode 100644 index 0000000000..e8ecc432c5 Binary files /dev/null and b/docs/media/SMS_Text_Messaging6.jpg differ diff --git a/docs/media/SMS_Text_Messaging7.jpg b/docs/media/SMS_Text_Messaging7.jpg new file mode 100644 index 0000000000..cf012f0ff4 Binary files /dev/null and b/docs/media/SMS_Text_Messaging7.jpg differ diff --git a/docs/media/SMS_Text_Messaging8.jpg b/docs/media/SMS_Text_Messaging8.jpg new file mode 100644 index 0000000000..17fceac30b Binary files /dev/null and b/docs/media/SMS_Text_Messaging8.jpg differ diff --git a/docs/media/SMS_Text_Messaging9.jpg b/docs/media/SMS_Text_Messaging9.jpg new file mode 100644 index 0000000000..a86fa150d5 Binary files /dev/null and b/docs/media/SMS_Text_Messaging9.jpg differ diff --git a/docs/media/Saved_Catalog_Searches_2_21.jpg b/docs/media/Saved_Catalog_Searches_2_21.jpg new file mode 100644 index 0000000000..ce22623f15 Binary files /dev/null and b/docs/media/Saved_Catalog_Searches_2_21.jpg differ diff --git a/docs/media/Saved_Catalog_Searches_2_21.jpg.1 b/docs/media/Saved_Catalog_Searches_2_21.jpg.1 new file mode 100644 index 0000000000..ce22623f15 Binary files /dev/null and b/docs/media/Saved_Catalog_Searches_2_21.jpg.1 differ diff --git a/docs/media/Saved_Catalog_Searches_2_22.jpg b/docs/media/Saved_Catalog_Searches_2_22.jpg new file mode 100644 index 0000000000..426e3994bf Binary files /dev/null and b/docs/media/Saved_Catalog_Searches_2_22.jpg differ diff --git a/docs/media/Saved_Catalog_Searches_2_22.jpg.1 b/docs/media/Saved_Catalog_Searches_2_22.jpg.1 new file mode 100644 index 0000000000..426e3994bf Binary files /dev/null and b/docs/media/Saved_Catalog_Searches_2_22.jpg.1 differ diff --git a/docs/media/Search_Results1.jpg b/docs/media/Search_Results1.jpg new file mode 100644 index 0000000000..a41532156c Binary files /dev/null and b/docs/media/Search_Results1.jpg differ diff --git a/docs/media/Sorting_Columns2.jpg b/docs/media/Sorting_Columns2.jpg new file mode 100644 index 0000000000..6510ea4aa7 Binary files /dev/null and b/docs/media/Sorting_Columns2.jpg differ diff --git a/docs/media/Sorting_Columns3.jpg b/docs/media/Sorting_Columns3.jpg new file mode 100644 index 0000000000..57ba1bdfa4 Binary files /dev/null and b/docs/media/Sorting_Columns3.jpg differ diff --git a/docs/media/Sorting_Columns3.jpg.1 b/docs/media/Sorting_Columns3.jpg.1 new file mode 100644 index 0000000000..57ba1bdfa4 Binary files /dev/null and b/docs/media/Sorting_Columns3.jpg.1 differ diff --git a/docs/media/Sorting_Columns4.jpg b/docs/media/Sorting_Columns4.jpg new file mode 100644 index 0000000000..9d38c39241 Binary files /dev/null and b/docs/media/Sorting_Columns4.jpg differ diff --git a/docs/media/Sorting_Columns5.jpg b/docs/media/Sorting_Columns5.jpg new file mode 100644 index 0000000000..98d573a3ee Binary files /dev/null and b/docs/media/Sorting_Columns5.jpg differ diff --git a/docs/media/Target_Pickup_Lib1.jpg b/docs/media/Target_Pickup_Lib1.jpg new file mode 100644 index 0000000000..bbb7c01555 Binary files /dev/null and b/docs/media/Target_Pickup_Lib1.jpg differ diff --git a/docs/media/Target_Pickup_Lib2.jpg b/docs/media/Target_Pickup_Lib2.jpg new file mode 100644 index 0000000000..bbb7c01555 Binary files /dev/null and b/docs/media/Target_Pickup_Lib2.jpg differ diff --git a/docs/media/User_Activity_Types1A.jpg b/docs/media/User_Activity_Types1A.jpg new file mode 100644 index 0000000000..69d6ab4d39 Binary files /dev/null and b/docs/media/User_Activity_Types1A.jpg differ diff --git a/docs/media/User_Activity_Types2A.jpg b/docs/media/User_Activity_Types2A.jpg new file mode 100644 index 0000000000..63048ca1a6 Binary files /dev/null and b/docs/media/User_Activity_Types2A.jpg differ diff --git a/docs/media/Vandelay_Integration_into_Acquisitions1.jpg b/docs/media/Vandelay_Integration_into_Acquisitions1.jpg new file mode 100644 index 0000000000..909e14e9ee Binary files /dev/null and b/docs/media/Vandelay_Integration_into_Acquisitions1.jpg differ diff --git a/docs/media/Vandelay_Integration_into_Acquisitions2.jpg b/docs/media/Vandelay_Integration_into_Acquisitions2.jpg new file mode 100644 index 0000000000..afc195b847 Binary files /dev/null and b/docs/media/Vandelay_Integration_into_Acquisitions2.jpg differ diff --git a/docs/media/Vandelay_Integration_into_Acquisitions3.jpg b/docs/media/Vandelay_Integration_into_Acquisitions3.jpg new file mode 100644 index 0000000000..1190fb1dd5 Binary files /dev/null and b/docs/media/Vandelay_Integration_into_Acquisitions3.jpg differ diff --git a/docs/media/Vandelay_Integration_into_Acquisitions4.jpg b/docs/media/Vandelay_Integration_into_Acquisitions4.jpg new file mode 100644 index 0000000000..7f1c6a7135 Binary files /dev/null and b/docs/media/Vandelay_Integration_into_Acquisitions4.jpg differ diff --git a/docs/media/Vandelay_Integration_into_Acquisitions5.jpg b/docs/media/Vandelay_Integration_into_Acquisitions5.jpg new file mode 100644 index 0000000000..fd072cae6a Binary files /dev/null and b/docs/media/Vandelay_Integration_into_Acquisitions5.jpg differ diff --git a/docs/media/Vandelay_Integration_into_Acquisitions6.jpg b/docs/media/Vandelay_Integration_into_Acquisitions6.jpg new file mode 100644 index 0000000000..90dde3c635 Binary files /dev/null and b/docs/media/Vandelay_Integration_into_Acquisitions6.jpg differ diff --git a/docs/media/acq_activate.png b/docs/media/acq_activate.png new file mode 100644 index 0000000000..3ee9088adc Binary files /dev/null and b/docs/media/acq_activate.png differ diff --git a/docs/media/acq_apply_claim_policy.png b/docs/media/acq_apply_claim_policy.png new file mode 100644 index 0000000000..6b7dd93897 Binary files /dev/null and b/docs/media/acq_apply_claim_policy.png differ diff --git a/docs/media/acq_brief_record-2.png b/docs/media/acq_brief_record-2.png new file mode 100644 index 0000000000..264213ce31 Binary files /dev/null and b/docs/media/acq_brief_record-2.png differ diff --git a/docs/media/acq_brief_record.png b/docs/media/acq_brief_record.png new file mode 100644 index 0000000000..25fdefe7ba Binary files /dev/null and b/docs/media/acq_brief_record.png differ diff --git a/docs/media/acq_cancel_copy.png b/docs/media/acq_cancel_copy.png new file mode 100644 index 0000000000..2ed7dc1651 Binary files /dev/null and b/docs/media/acq_cancel_copy.png differ diff --git a/docs/media/acq_cancel_line_items.png b/docs/media/acq_cancel_line_items.png new file mode 100644 index 0000000000..541436346b Binary files /dev/null and b/docs/media/acq_cancel_line_items.png differ diff --git a/docs/media/acq_claim_item-2.png b/docs/media/acq_claim_item-2.png new file mode 100644 index 0000000000..453f02c112 Binary files /dev/null and b/docs/media/acq_claim_item-2.png differ diff --git a/docs/media/acq_claim_item-3.png b/docs/media/acq_claim_item-3.png new file mode 100644 index 0000000000..79bbe07811 Binary files /dev/null and b/docs/media/acq_claim_item-3.png differ diff --git a/docs/media/acq_claim_item-4.png b/docs/media/acq_claim_item-4.png new file mode 100644 index 0000000000..ada7330467 Binary files /dev/null and b/docs/media/acq_claim_item-4.png differ diff --git a/docs/media/acq_claim_item-5.png b/docs/media/acq_claim_item-5.png new file mode 100644 index 0000000000..e1729e2606 Binary files /dev/null and b/docs/media/acq_claim_item-5.png differ diff --git a/docs/media/acq_claim_item.png b/docs/media/acq_claim_item.png new file mode 100644 index 0000000000..540605f6b7 Binary files /dev/null and b/docs/media/acq_claim_item.png differ diff --git a/docs/media/acq_export_list.png b/docs/media/acq_export_list.png new file mode 100644 index 0000000000..f5c531704d Binary files /dev/null and b/docs/media/acq_export_list.png differ diff --git a/docs/media/acq_funds-2.png b/docs/media/acq_funds-2.png new file mode 100644 index 0000000000..259edaa3e2 Binary files /dev/null and b/docs/media/acq_funds-2.png differ diff --git a/docs/media/acq_funds.png b/docs/media/acq_funds.png new file mode 100644 index 0000000000..ad408031dc Binary files /dev/null and b/docs/media/acq_funds.png differ diff --git a/docs/media/acq_invoice_blanket.png b/docs/media/acq_invoice_blanket.png new file mode 100644 index 0000000000..227727ee2b Binary files /dev/null and b/docs/media/acq_invoice_blanket.png differ diff --git a/docs/media/acq_invoice_line_items.png b/docs/media/acq_invoice_line_items.png new file mode 100644 index 0000000000..0a572f9b4e Binary files /dev/null and b/docs/media/acq_invoice_line_items.png differ diff --git a/docs/media/acq_invoice_link.png b/docs/media/acq_invoice_link.png new file mode 100644 index 0000000000..6bc7c1b3dd Binary files /dev/null and b/docs/media/acq_invoice_link.png differ diff --git a/docs/media/acq_invoice_purchase_order.png b/docs/media/acq_invoice_purchase_order.png new file mode 100644 index 0000000000..0a572f9b4e Binary files /dev/null and b/docs/media/acq_invoice_purchase_order.png differ diff --git a/docs/media/acq_invoice_view-2.png b/docs/media/acq_invoice_view-2.png new file mode 100644 index 0000000000..abac114908 Binary files /dev/null and b/docs/media/acq_invoice_view-2.png differ diff --git a/docs/media/acq_invoice_view.png b/docs/media/acq_invoice_view.png new file mode 100644 index 0000000000..616380cee3 Binary files /dev/null and b/docs/media/acq_invoice_view.png differ diff --git a/docs/media/acq_line_items_add_copies-2.png b/docs/media/acq_line_items_add_copies-2.png new file mode 100644 index 0000000000..8b1178d2cb Binary files /dev/null and b/docs/media/acq_line_items_add_copies-2.png differ diff --git a/docs/media/acq_line_items_add_copies-3.png b/docs/media/acq_line_items_add_copies-3.png new file mode 100644 index 0000000000..ee9a6d58e2 Binary files /dev/null and b/docs/media/acq_line_items_add_copies-3.png differ diff --git a/docs/media/acq_line_items_add_copies.png b/docs/media/acq_line_items_add_copies.png new file mode 100644 index 0000000000..699a70a93d Binary files /dev/null and b/docs/media/acq_line_items_add_copies.png differ diff --git a/docs/media/acq_line_items_add_notes.png b/docs/media/acq_line_items_add_notes.png new file mode 100644 index 0000000000..f4e580ba94 Binary files /dev/null and b/docs/media/acq_line_items_add_notes.png differ diff --git a/docs/media/acq_line_items_alerts-2.png b/docs/media/acq_line_items_alerts-2.png new file mode 100644 index 0000000000..7bc899c4be Binary files /dev/null and b/docs/media/acq_line_items_alerts-2.png differ diff --git a/docs/media/acq_line_items_alerts.png b/docs/media/acq_line_items_alerts.png new file mode 100644 index 0000000000..15003be799 Binary files /dev/null and b/docs/media/acq_line_items_alerts.png differ diff --git a/docs/media/acq_line_items_link-2.png b/docs/media/acq_line_items_link-2.png new file mode 100644 index 0000000000..d0ef1936f9 Binary files /dev/null and b/docs/media/acq_line_items_link-2.png differ diff --git a/docs/media/acq_line_items_link.png b/docs/media/acq_line_items_link.png new file mode 100644 index 0000000000..11c1cd115b Binary files /dev/null and b/docs/media/acq_line_items_link.png differ diff --git a/docs/media/acq_line_items_update_barcodes.png b/docs/media/acq_line_items_update_barcodes.png new file mode 100644 index 0000000000..b95368d28c Binary files /dev/null and b/docs/media/acq_line_items_update_barcodes.png differ diff --git a/docs/media/acq_line_items_view_history.png b/docs/media/acq_line_items_view_history.png new file mode 100644 index 0000000000..b6a03abb84 Binary files /dev/null and b/docs/media/acq_line_items_view_history.png differ diff --git a/docs/media/acq_line_items_worksheet.png b/docs/media/acq_line_items_worksheet.png new file mode 100644 index 0000000000..54e465b893 Binary files /dev/null and b/docs/media/acq_line_items_worksheet.png differ diff --git a/docs/media/acq_load_records.png b/docs/media/acq_load_records.png new file mode 100644 index 0000000000..5b73687d73 Binary files /dev/null and b/docs/media/acq_load_records.png differ diff --git a/docs/media/acq_marc_search-2.png b/docs/media/acq_marc_search-2.png new file mode 100644 index 0000000000..a317bf0f7a Binary files /dev/null and b/docs/media/acq_marc_search-2.png differ diff --git a/docs/media/acq_marc_search.png b/docs/media/acq_marc_search.png new file mode 100644 index 0000000000..391ae435a2 Binary files /dev/null and b/docs/media/acq_marc_search.png differ diff --git a/docs/media/acq_purchase_order_add_charges.png b/docs/media/acq_purchase_order_add_charges.png new file mode 100644 index 0000000000..3ee9088adc Binary files /dev/null and b/docs/media/acq_purchase_order_add_charges.png differ diff --git a/docs/media/acq_purchase_order_add_note.png b/docs/media/acq_purchase_order_add_note.png new file mode 100644 index 0000000000..e3d9e059af Binary files /dev/null and b/docs/media/acq_purchase_order_add_note.png differ diff --git a/docs/media/acq_purchase_order_create.png b/docs/media/acq_purchase_order_create.png new file mode 100644 index 0000000000..71704bc09f Binary files /dev/null and b/docs/media/acq_purchase_order_create.png differ diff --git a/docs/media/acq_purchase_order_history.png b/docs/media/acq_purchase_order_history.png new file mode 100644 index 0000000000..8f4c5fe466 Binary files /dev/null and b/docs/media/acq_purchase_order_history.png differ diff --git a/docs/media/acq_purchase_order_name.png b/docs/media/acq_purchase_order_name.png new file mode 100644 index 0000000000..6eaac45816 Binary files /dev/null and b/docs/media/acq_purchase_order_name.png differ diff --git a/docs/media/acq_purchase_order_print.png b/docs/media/acq_purchase_order_print.png new file mode 100644 index 0000000000..d4a14feb5c Binary files /dev/null and b/docs/media/acq_purchase_order_print.png differ diff --git a/docs/media/acq_purchase_order_split-2.png b/docs/media/acq_purchase_order_split-2.png new file mode 100644 index 0000000000..a1fa5e3fd1 Binary files /dev/null and b/docs/media/acq_purchase_order_split-2.png differ diff --git a/docs/media/acq_purchase_order_split.png b/docs/media/acq_purchase_order_split.png new file mode 100644 index 0000000000..b47702282e Binary files /dev/null and b/docs/media/acq_purchase_order_split.png differ diff --git a/docs/media/acq_purchase_order_view-2.png b/docs/media/acq_purchase_order_view-2.png new file mode 100644 index 0000000000..81465c80a9 Binary files /dev/null and b/docs/media/acq_purchase_order_view-2.png differ diff --git a/docs/media/acq_purchase_order_view.png b/docs/media/acq_purchase_order_view.png new file mode 100644 index 0000000000..2bb5c94754 Binary files /dev/null and b/docs/media/acq_purchase_order_view.png differ diff --git a/docs/media/acq_search.png b/docs/media/acq_search.png new file mode 100644 index 0000000000..2bb5e85f5e Binary files /dev/null and b/docs/media/acq_search.png differ diff --git a/docs/media/acq_selection_clone.png b/docs/media/acq_selection_clone.png new file mode 100644 index 0000000000..d4183b5cb1 Binary files /dev/null and b/docs/media/acq_selection_clone.png differ diff --git a/docs/media/acq_selection_create.png b/docs/media/acq_selection_create.png new file mode 100644 index 0000000000..f248d0ae9e Binary files /dev/null and b/docs/media/acq_selection_create.png differ diff --git a/docs/media/acq_selection_mark_ready-2.png b/docs/media/acq_selection_mark_ready-2.png new file mode 100644 index 0000000000..1452cae29d Binary files /dev/null and b/docs/media/acq_selection_mark_ready-2.png differ diff --git a/docs/media/acq_selection_mark_ready.png b/docs/media/acq_selection_mark_ready.png new file mode 100644 index 0000000000..3eb558659e Binary files /dev/null and b/docs/media/acq_selection_mark_ready.png differ diff --git a/docs/media/acq_selection_merge.png b/docs/media/acq_selection_merge.png new file mode 100644 index 0000000000..e1f740c246 Binary files /dev/null and b/docs/media/acq_selection_merge.png differ diff --git a/docs/media/acq_workflow.jpg b/docs/media/acq_workflow.jpg new file mode 100644 index 0000000000..1143cfa017 Binary files /dev/null and b/docs/media/acq_workflow.jpg differ diff --git a/docs/media/add_holdings-1.png b/docs/media/add_holdings-1.png new file mode 100644 index 0000000000..07baaa0192 Binary files /dev/null and b/docs/media/add_holdings-1.png differ diff --git a/docs/media/add_holdings-2.png b/docs/media/add_holdings-2.png new file mode 100644 index 0000000000..4176df14ef Binary files /dev/null and b/docs/media/add_holdings-2.png differ diff --git a/docs/media/add_holdings-3.png b/docs/media/add_holdings-3.png new file mode 100644 index 0000000000..a847eb6afc Binary files /dev/null and b/docs/media/add_holdings-3.png differ diff --git a/docs/media/add_holdings-4.png b/docs/media/add_holdings-4.png new file mode 100644 index 0000000000..6359f1d0f1 Binary files /dev/null and b/docs/media/add_holdings-4.png differ diff --git a/docs/media/add_holdings-5.png b/docs/media/add_holdings-5.png new file mode 100644 index 0000000000..3a25250aec Binary files /dev/null and b/docs/media/add_holdings-5.png differ diff --git a/docs/media/application-pdf.png b/docs/media/application-pdf.png new file mode 100644 index 0000000000..6fdfae9930 Binary files /dev/null and b/docs/media/application-pdf.png differ diff --git a/docs/media/ascv-distr.jpg b/docs/media/ascv-distr.jpg new file mode 100644 index 0000000000..77c151e215 Binary files /dev/null and b/docs/media/ascv-distr.jpg differ diff --git a/docs/media/ascv-issues.jpg b/docs/media/ascv-issues.jpg new file mode 100644 index 0000000000..ab6d13c945 Binary files /dev/null and b/docs/media/ascv-issues.jpg differ diff --git a/docs/media/ascv-sub.jpg b/docs/media/ascv-sub.jpg new file mode 100644 index 0000000000..a44bdbbba6 Binary files /dev/null and b/docs/media/ascv-sub.jpg differ diff --git a/docs/media/backdate_checkin.png b/docs/media/backdate_checkin.png new file mode 100644 index 0000000000..ae0ef539f6 Binary files /dev/null and b/docs/media/backdate_checkin.png differ diff --git a/docs/media/backdate_post_checkin.png b/docs/media/backdate_post_checkin.png new file mode 100644 index 0000000000..03b54a92cc Binary files /dev/null and b/docs/media/backdate_post_checkin.png differ diff --git a/docs/media/backdate_post_date.png b/docs/media/backdate_post_date.png new file mode 100644 index 0000000000..501483588c Binary files /dev/null and b/docs/media/backdate_post_date.png differ diff --git a/docs/media/backdate_red.png b/docs/media/backdate_red.png new file mode 100644 index 0000000000..5d7c6c9c26 Binary files /dev/null and b/docs/media/backdate_red.png differ diff --git a/docs/media/bills-1.png b/docs/media/bills-1.png new file mode 100644 index 0000000000..aca68919ed Binary files /dev/null and b/docs/media/bills-1.png differ diff --git a/docs/media/bills-10.png b/docs/media/bills-10.png new file mode 100644 index 0000000000..1a9b1353e3 Binary files /dev/null and b/docs/media/bills-10.png differ diff --git a/docs/media/bills-11.png b/docs/media/bills-11.png new file mode 100644 index 0000000000..5e6eec9df9 Binary files /dev/null and b/docs/media/bills-11.png differ diff --git a/docs/media/bills-12.png b/docs/media/bills-12.png new file mode 100644 index 0000000000..2671a2a279 Binary files /dev/null and b/docs/media/bills-12.png differ diff --git a/docs/media/bills-13.png b/docs/media/bills-13.png new file mode 100644 index 0000000000..c6043204b2 Binary files /dev/null and b/docs/media/bills-13.png differ diff --git a/docs/media/bills-14.png b/docs/media/bills-14.png new file mode 100644 index 0000000000..9ef43d2657 Binary files /dev/null and b/docs/media/bills-14.png differ diff --git a/docs/media/bills-15.png b/docs/media/bills-15.png new file mode 100644 index 0000000000..e176d43ddf Binary files /dev/null and b/docs/media/bills-15.png differ diff --git a/docs/media/bills-16.png b/docs/media/bills-16.png new file mode 100644 index 0000000000..2b4b29f901 Binary files /dev/null and b/docs/media/bills-16.png differ diff --git a/docs/media/bills-17.png b/docs/media/bills-17.png new file mode 100644 index 0000000000..fff134b035 Binary files /dev/null and b/docs/media/bills-17.png differ diff --git a/docs/media/bills-18.png b/docs/media/bills-18.png new file mode 100644 index 0000000000..f38bec473e Binary files /dev/null and b/docs/media/bills-18.png differ diff --git a/docs/media/bills-19.png b/docs/media/bills-19.png new file mode 100644 index 0000000000..cf455f2b92 Binary files /dev/null and b/docs/media/bills-19.png differ diff --git a/docs/media/bills-2.png b/docs/media/bills-2.png new file mode 100644 index 0000000000..242ff2db11 Binary files /dev/null and b/docs/media/bills-2.png differ diff --git a/docs/media/bills-20.png b/docs/media/bills-20.png new file mode 100644 index 0000000000..ca4b84c3d0 Binary files /dev/null and b/docs/media/bills-20.png differ diff --git a/docs/media/bills-3.png b/docs/media/bills-3.png new file mode 100644 index 0000000000..ac194f860f Binary files /dev/null and b/docs/media/bills-3.png differ diff --git a/docs/media/bills-4.png b/docs/media/bills-4.png new file mode 100644 index 0000000000..74e2d7250b Binary files /dev/null and b/docs/media/bills-4.png differ diff --git a/docs/media/bills-5.png b/docs/media/bills-5.png new file mode 100644 index 0000000000..ac4c9917b2 Binary files /dev/null and b/docs/media/bills-5.png differ diff --git a/docs/media/bills-6.png b/docs/media/bills-6.png new file mode 100644 index 0000000000..4be2f89a69 Binary files /dev/null and b/docs/media/bills-6.png differ diff --git a/docs/media/bills-7.png b/docs/media/bills-7.png new file mode 100644 index 0000000000..2d7b5b0d11 Binary files /dev/null and b/docs/media/bills-7.png differ diff --git a/docs/media/bills-8.png b/docs/media/bills-8.png new file mode 100644 index 0000000000..bbcb905e7a Binary files /dev/null and b/docs/media/bills-8.png differ diff --git a/docs/media/bills-9.png b/docs/media/bills-9.png new file mode 100644 index 0000000000..edbb56605b Binary files /dev/null and b/docs/media/bills-9.png differ diff --git a/docs/media/booking-cancel-1.png b/docs/media/booking-cancel-1.png new file mode 100644 index 0000000000..767d64c89c Binary files /dev/null and b/docs/media/booking-cancel-1.png differ diff --git a/docs/media/booking-cancel-2.png b/docs/media/booking-cancel-2.png new file mode 100644 index 0000000000..3ba68d4466 Binary files /dev/null and b/docs/media/booking-cancel-2.png differ diff --git a/docs/media/booking-cancel-3.png b/docs/media/booking-cancel-3.png new file mode 100644 index 0000000000..0f3949bd35 Binary files /dev/null and b/docs/media/booking-cancel-3.png differ diff --git a/docs/media/booking-cancel-4.png b/docs/media/booking-cancel-4.png new file mode 100644 index 0000000000..0f3949bd35 Binary files /dev/null and b/docs/media/booking-cancel-4.png differ diff --git a/docs/media/booking-capture-1.png b/docs/media/booking-capture-1.png new file mode 100644 index 0000000000..5c95759673 Binary files /dev/null and b/docs/media/booking-capture-1.png differ diff --git a/docs/media/booking-capture-2.png b/docs/media/booking-capture-2.png new file mode 100644 index 0000000000..1ed25bc258 Binary files /dev/null and b/docs/media/booking-capture-2.png differ diff --git a/docs/media/booking-capture-3.png b/docs/media/booking-capture-3.png new file mode 100644 index 0000000000..2de6c8a5eb Binary files /dev/null and b/docs/media/booking-capture-3.png differ diff --git a/docs/media/booking-create-1.png b/docs/media/booking-create-1.png new file mode 100644 index 0000000000..a9aa9d4791 Binary files /dev/null and b/docs/media/booking-create-1.png differ diff --git a/docs/media/booking-create-2.png b/docs/media/booking-create-2.png new file mode 100644 index 0000000000..5942214d5a Binary files /dev/null and b/docs/media/booking-create-2.png differ diff --git a/docs/media/booking-create-3.png b/docs/media/booking-create-3.png new file mode 100644 index 0000000000..e0f0769cdd Binary files /dev/null and b/docs/media/booking-create-3.png differ diff --git a/docs/media/booking-create-4.png b/docs/media/booking-create-4.png new file mode 100644 index 0000000000..d48499b0dc Binary files /dev/null and b/docs/media/booking-create-4.png differ diff --git a/docs/media/booking-create-5.png b/docs/media/booking-create-5.png new file mode 100644 index 0000000000..ba4de889db Binary files /dev/null and b/docs/media/booking-create-5.png differ diff --git a/docs/media/booking-create-6.png b/docs/media/booking-create-6.png new file mode 100644 index 0000000000..a25176e234 Binary files /dev/null and b/docs/media/booking-create-6.png differ diff --git a/docs/media/booking-create-7.png b/docs/media/booking-create-7.png new file mode 100644 index 0000000000..dda012071a Binary files /dev/null and b/docs/media/booking-create-7.png differ diff --git a/docs/media/booking-create-8.png b/docs/media/booking-create-8.png new file mode 100644 index 0000000000..ce1de3e1db Binary files /dev/null and b/docs/media/booking-create-8.png differ diff --git a/docs/media/booking-create-9.png b/docs/media/booking-create-9.png new file mode 100644 index 0000000000..ce1de3e1db Binary files /dev/null and b/docs/media/booking-create-9.png differ diff --git a/docs/media/booking-create-bookable-1.png b/docs/media/booking-create-bookable-1.png new file mode 100644 index 0000000000..7ddded0c87 Binary files /dev/null and b/docs/media/booking-create-bookable-1.png differ diff --git a/docs/media/booking-create-bookable-2.png b/docs/media/booking-create-bookable-2.png new file mode 100644 index 0000000000..df9a3a47b7 Binary files /dev/null and b/docs/media/booking-create-bookable-2.png differ diff --git a/docs/media/booking-create-bookable-3.png b/docs/media/booking-create-bookable-3.png new file mode 100644 index 0000000000..49ed80173d Binary files /dev/null and b/docs/media/booking-create-bookable-3.png differ diff --git a/docs/media/booking-create-bookable-4.png b/docs/media/booking-create-bookable-4.png new file mode 100644 index 0000000000..6c7128d649 Binary files /dev/null and b/docs/media/booking-create-bookable-4.png differ diff --git a/docs/media/booking-create-bookable-5.png b/docs/media/booking-create-bookable-5.png new file mode 100644 index 0000000000..c501d47cf3 Binary files /dev/null and b/docs/media/booking-create-bookable-5.png differ diff --git a/docs/media/booking-create-bookable-6.png b/docs/media/booking-create-bookable-6.png new file mode 100644 index 0000000000..2261a9d6a5 Binary files /dev/null and b/docs/media/booking-create-bookable-6.png differ diff --git a/docs/media/booking-create-module-1.png b/docs/media/booking-create-module-1.png new file mode 100644 index 0000000000..a2804c8bcb Binary files /dev/null and b/docs/media/booking-create-module-1.png differ diff --git a/docs/media/booking-create-module-2.png b/docs/media/booking-create-module-2.png new file mode 100644 index 0000000000..92f093599e Binary files /dev/null and b/docs/media/booking-create-module-2.png differ diff --git a/docs/media/booking-create-module-3.png b/docs/media/booking-create-module-3.png new file mode 100644 index 0000000000..b031138983 Binary files /dev/null and b/docs/media/booking-create-module-3.png differ diff --git a/docs/media/booking-create-module-4.png b/docs/media/booking-create-module-4.png new file mode 100644 index 0000000000..32981a7e7c Binary files /dev/null and b/docs/media/booking-create-module-4.png differ diff --git a/docs/media/booking-create-resourcetype-1.png b/docs/media/booking-create-resourcetype-1.png new file mode 100644 index 0000000000..aa11630c2c Binary files /dev/null and b/docs/media/booking-create-resourcetype-1.png differ diff --git a/docs/media/booking-create-resourcetype-2.png b/docs/media/booking-create-resourcetype-2.png new file mode 100644 index 0000000000..ff517c5e87 Binary files /dev/null and b/docs/media/booking-create-resourcetype-2.png differ diff --git a/docs/media/booking-create-resourcetype-3.png b/docs/media/booking-create-resourcetype-3.png new file mode 100644 index 0000000000..d7a7e384f9 Binary files /dev/null and b/docs/media/booking-create-resourcetype-3.png differ diff --git a/docs/media/booking-create-resourcetype-4.png b/docs/media/booking-create-resourcetype-4.png new file mode 100644 index 0000000000..0f7317e495 Binary files /dev/null and b/docs/media/booking-create-resourcetype-4.png differ diff --git a/docs/media/booking-create-resourcetype-5.png b/docs/media/booking-create-resourcetype-5.png new file mode 100644 index 0000000000..784d95ad00 Binary files /dev/null and b/docs/media/booking-create-resourcetype-5.png differ diff --git a/docs/media/booking-pickup-1.png b/docs/media/booking-pickup-1.png new file mode 100644 index 0000000000..30c94517eb Binary files /dev/null and b/docs/media/booking-pickup-1.png differ diff --git a/docs/media/booking-pickup-2.png b/docs/media/booking-pickup-2.png new file mode 100644 index 0000000000..bcae061383 Binary files /dev/null and b/docs/media/booking-pickup-2.png differ diff --git a/docs/media/booking-pickup-3.png b/docs/media/booking-pickup-3.png new file mode 100644 index 0000000000..afe3857833 Binary files /dev/null and b/docs/media/booking-pickup-3.png differ diff --git a/docs/media/booking-pickup-module-1.png b/docs/media/booking-pickup-module-1.png new file mode 100644 index 0000000000..215ad7616f Binary files /dev/null and b/docs/media/booking-pickup-module-1.png differ diff --git a/docs/media/booking-pull-1.png b/docs/media/booking-pull-1.png new file mode 100644 index 0000000000..0dcdb8267c Binary files /dev/null and b/docs/media/booking-pull-1.png differ diff --git a/docs/media/booking-pull-2.png b/docs/media/booking-pull-2.png new file mode 100644 index 0000000000..a2601f7cf4 Binary files /dev/null and b/docs/media/booking-pull-2.png differ diff --git a/docs/media/booking-pull-3.png b/docs/media/booking-pull-3.png new file mode 100644 index 0000000000..a0156bea44 Binary files /dev/null and b/docs/media/booking-pull-3.png differ diff --git a/docs/media/booking-return-2.png b/docs/media/booking-return-2.png new file mode 100644 index 0000000000..503180cd91 Binary files /dev/null and b/docs/media/booking-return-2.png differ diff --git a/docs/media/booking-return-module-1.png b/docs/media/booking-return-module-1.png new file mode 100644 index 0000000000..f65b164b90 Binary files /dev/null and b/docs/media/booking-return-module-1.png differ diff --git a/docs/media/booking-return-module-2.png b/docs/media/booking-return-module-2.png new file mode 100644 index 0000000000..4c40bb6f97 Binary files /dev/null and b/docs/media/booking-return-module-2.png differ diff --git a/docs/media/booking-return-module-4.png b/docs/media/booking-return-module-4.png new file mode 100644 index 0000000000..fbbca51429 Binary files /dev/null and b/docs/media/booking-return-module-4.png differ diff --git a/docs/media/cap-wiz-cal.jpg b/docs/media/cap-wiz-cal.jpg new file mode 100644 index 0000000000..e28b592eda Binary files /dev/null and b/docs/media/cap-wiz-cal.jpg differ diff --git a/docs/media/cap-wiz-chan.jpg b/docs/media/cap-wiz-chan.jpg new file mode 100644 index 0000000000..f50eb0cf88 Binary files /dev/null and b/docs/media/cap-wiz-chan.jpg differ diff --git a/docs/media/cap-wiz-chron.jpg b/docs/media/cap-wiz-chron.jpg new file mode 100644 index 0000000000..27b955b68d Binary files /dev/null and b/docs/media/cap-wiz-chron.jpg differ diff --git a/docs/media/cap-wiz-freq.jpg b/docs/media/cap-wiz-freq.jpg new file mode 100644 index 0000000000..83b0f9dade Binary files /dev/null and b/docs/media/cap-wiz-freq.jpg differ diff --git a/docs/media/cap-wiz-num.jpg b/docs/media/cap-wiz-num.jpg new file mode 100644 index 0000000000..e1aa286dd7 Binary files /dev/null and b/docs/media/cap-wiz-num.jpg differ diff --git a/docs/media/catalogue-10.png b/docs/media/catalogue-10.png new file mode 100644 index 0000000000..41c3be1a64 Binary files /dev/null and b/docs/media/catalogue-10.png differ diff --git a/docs/media/catalogue-11.png b/docs/media/catalogue-11.png new file mode 100644 index 0000000000..d51f45bf70 Binary files /dev/null and b/docs/media/catalogue-11.png differ diff --git a/docs/media/catalogue-3.png b/docs/media/catalogue-3.png new file mode 100644 index 0000000000..f8080a9085 Binary files /dev/null and b/docs/media/catalogue-3.png differ diff --git a/docs/media/catalogue-4.png b/docs/media/catalogue-4.png new file mode 100644 index 0000000000..17352789eb Binary files /dev/null and b/docs/media/catalogue-4.png differ diff --git a/docs/media/catalogue-5.png b/docs/media/catalogue-5.png new file mode 100644 index 0000000000..2f5e5ea562 Binary files /dev/null and b/docs/media/catalogue-5.png differ diff --git a/docs/media/catalogue-6.png b/docs/media/catalogue-6.png new file mode 100644 index 0000000000..9ed436228d Binary files /dev/null and b/docs/media/catalogue-6.png differ diff --git a/docs/media/catalogue-7.png b/docs/media/catalogue-7.png new file mode 100644 index 0000000000..4aaa0c27e6 Binary files /dev/null and b/docs/media/catalogue-7.png differ diff --git a/docs/media/catalogue-8.png b/docs/media/catalogue-8.png new file mode 100644 index 0000000000..1a952ebb33 Binary files /dev/null and b/docs/media/catalogue-8.png differ diff --git a/docs/media/catalogue-9.png b/docs/media/catalogue-9.png new file mode 100644 index 0000000000..a32192628b Binary files /dev/null and b/docs/media/catalogue-9.png differ diff --git a/docs/media/caution.png b/docs/media/caution.png new file mode 100644 index 0000000000..cdc6568091 Binary files /dev/null and b/docs/media/caution.png differ diff --git a/docs/media/ccbysa.png b/docs/media/ccbysa.png new file mode 100644 index 0000000000..f0a944e0b8 Binary files /dev/null and b/docs/media/ccbysa.png differ diff --git a/docs/media/check_in_menu.png b/docs/media/check_in_menu.png new file mode 100644 index 0000000000..d04d859850 Binary files /dev/null and b/docs/media/check_in_menu.png differ diff --git a/docs/media/checkin_barcode.png b/docs/media/checkin_barcode.png new file mode 100644 index 0000000000..a7b7d1d1c4 Binary files /dev/null and b/docs/media/checkin_barcode.png differ diff --git a/docs/media/checkin_options.png b/docs/media/checkin_options.png new file mode 100644 index 0000000000..be3360f826 Binary files /dev/null and b/docs/media/checkin_options.png differ diff --git a/docs/media/checkout_item_barcode.png b/docs/media/checkout_item_barcode.png new file mode 100644 index 0000000000..c625a90315 Binary files /dev/null and b/docs/media/checkout_item_barcode.png differ diff --git a/docs/media/checkout_menu.png b/docs/media/checkout_menu.png new file mode 100644 index 0000000000..029bf36bc5 Binary files /dev/null and b/docs/media/checkout_menu.png differ diff --git a/docs/media/circulation-1.png b/docs/media/circulation-1.png new file mode 100644 index 0000000000..01d1b0748f Binary files /dev/null and b/docs/media/circulation-1.png differ diff --git a/docs/media/circulation-10.png b/docs/media/circulation-10.png new file mode 100644 index 0000000000..bc15935fc1 Binary files /dev/null and b/docs/media/circulation-10.png differ diff --git a/docs/media/circulation-11.png b/docs/media/circulation-11.png new file mode 100644 index 0000000000..9fad77c5a6 Binary files /dev/null and b/docs/media/circulation-11.png differ diff --git a/docs/media/circulation-12.png b/docs/media/circulation-12.png new file mode 100644 index 0000000000..d43881fca8 Binary files /dev/null and b/docs/media/circulation-12.png differ diff --git a/docs/media/circulation-13.png b/docs/media/circulation-13.png new file mode 100644 index 0000000000..ba6edf5a1d Binary files /dev/null and b/docs/media/circulation-13.png differ diff --git a/docs/media/circulation-14.png b/docs/media/circulation-14.png new file mode 100644 index 0000000000..1af7e6acf8 Binary files /dev/null and b/docs/media/circulation-14.png differ diff --git a/docs/media/circulation-15.png b/docs/media/circulation-15.png new file mode 100644 index 0000000000..35484a3768 Binary files /dev/null and b/docs/media/circulation-15.png differ diff --git a/docs/media/circulation-16.png b/docs/media/circulation-16.png new file mode 100644 index 0000000000..a95c5117ba Binary files /dev/null and b/docs/media/circulation-16.png differ diff --git a/docs/media/circulation-17.png b/docs/media/circulation-17.png new file mode 100644 index 0000000000..bb66c3c2aa Binary files /dev/null and b/docs/media/circulation-17.png differ diff --git a/docs/media/circulation-18.png b/docs/media/circulation-18.png new file mode 100644 index 0000000000..78b474565d Binary files /dev/null and b/docs/media/circulation-18.png differ diff --git a/docs/media/circulation-19.png b/docs/media/circulation-19.png new file mode 100644 index 0000000000..0118b0076b Binary files /dev/null and b/docs/media/circulation-19.png differ diff --git a/docs/media/circulation-2.png b/docs/media/circulation-2.png new file mode 100644 index 0000000000..077835dc64 Binary files /dev/null and b/docs/media/circulation-2.png differ diff --git a/docs/media/circulation-20.png b/docs/media/circulation-20.png new file mode 100644 index 0000000000..d1ed93616c Binary files /dev/null and b/docs/media/circulation-20.png differ diff --git a/docs/media/circulation-21.png b/docs/media/circulation-21.png new file mode 100644 index 0000000000..029c48b26d Binary files /dev/null and b/docs/media/circulation-21.png differ diff --git a/docs/media/circulation-22.png b/docs/media/circulation-22.png new file mode 100644 index 0000000000..0463348da7 Binary files /dev/null and b/docs/media/circulation-22.png differ diff --git a/docs/media/circulation-23.png b/docs/media/circulation-23.png new file mode 100644 index 0000000000..0a6f10cae3 Binary files /dev/null and b/docs/media/circulation-23.png differ diff --git a/docs/media/circulation-24.png b/docs/media/circulation-24.png new file mode 100644 index 0000000000..315125220b Binary files /dev/null and b/docs/media/circulation-24.png differ diff --git a/docs/media/circulation-25.png b/docs/media/circulation-25.png new file mode 100644 index 0000000000..afd49ff7ec Binary files /dev/null and b/docs/media/circulation-25.png differ diff --git a/docs/media/circulation-26.png b/docs/media/circulation-26.png new file mode 100644 index 0000000000..b116445602 Binary files /dev/null and b/docs/media/circulation-26.png differ diff --git a/docs/media/circulation-27.png b/docs/media/circulation-27.png new file mode 100644 index 0000000000..2f0455ad06 Binary files /dev/null and b/docs/media/circulation-27.png differ diff --git a/docs/media/circulation-28.png b/docs/media/circulation-28.png new file mode 100644 index 0000000000..ddac7ec62d Binary files /dev/null and b/docs/media/circulation-28.png differ diff --git a/docs/media/circulation-29.png b/docs/media/circulation-29.png new file mode 100644 index 0000000000..af3d586af1 Binary files /dev/null and b/docs/media/circulation-29.png differ diff --git a/docs/media/circulation-3.png b/docs/media/circulation-3.png new file mode 100644 index 0000000000..0a75f0a7ee Binary files /dev/null and b/docs/media/circulation-3.png differ diff --git a/docs/media/circulation-30.png b/docs/media/circulation-30.png new file mode 100644 index 0000000000..13830c8d6e Binary files /dev/null and b/docs/media/circulation-30.png differ diff --git a/docs/media/circulation-31.png b/docs/media/circulation-31.png new file mode 100644 index 0000000000..b2f1f1328a Binary files /dev/null and b/docs/media/circulation-31.png differ diff --git a/docs/media/circulation-32.png b/docs/media/circulation-32.png new file mode 100644 index 0000000000..1dffe813ff Binary files /dev/null and b/docs/media/circulation-32.png differ diff --git a/docs/media/circulation-33.png b/docs/media/circulation-33.png new file mode 100644 index 0000000000..367adfbfc2 Binary files /dev/null and b/docs/media/circulation-33.png differ diff --git a/docs/media/circulation-34.png b/docs/media/circulation-34.png new file mode 100644 index 0000000000..5be2e2da9d Binary files /dev/null and b/docs/media/circulation-34.png differ diff --git a/docs/media/circulation-35.png b/docs/media/circulation-35.png new file mode 100644 index 0000000000..b3b918b964 Binary files /dev/null and b/docs/media/circulation-35.png differ diff --git a/docs/media/circulation-36.png b/docs/media/circulation-36.png new file mode 100644 index 0000000000..35b1e606c1 Binary files /dev/null and b/docs/media/circulation-36.png differ diff --git a/docs/media/circulation-4.png b/docs/media/circulation-4.png new file mode 100644 index 0000000000..b92ecbcbf8 Binary files /dev/null and b/docs/media/circulation-4.png differ diff --git a/docs/media/circulation-5.png b/docs/media/circulation-5.png new file mode 100644 index 0000000000..898c871a41 Binary files /dev/null and b/docs/media/circulation-5.png differ diff --git a/docs/media/circulation-6.png b/docs/media/circulation-6.png new file mode 100644 index 0000000000..6df9eb98b4 Binary files /dev/null and b/docs/media/circulation-6.png differ diff --git a/docs/media/circulation-7.png b/docs/media/circulation-7.png new file mode 100644 index 0000000000..79987dfb7d Binary files /dev/null and b/docs/media/circulation-7.png differ diff --git a/docs/media/circulation-8.png b/docs/media/circulation-8.png new file mode 100644 index 0000000000..7c624e271d Binary files /dev/null and b/docs/media/circulation-8.png differ diff --git a/docs/media/circulation-9.png b/docs/media/circulation-9.png new file mode 100644 index 0000000000..49eae35b4e Binary files /dev/null and b/docs/media/circulation-9.png differ diff --git a/docs/media/claimed_date.png b/docs/media/claimed_date.png new file mode 100644 index 0000000000..40af3de9c2 Binary files /dev/null and b/docs/media/claimed_date.png differ diff --git a/docs/media/conj1.jpg b/docs/media/conj1.jpg new file mode 100644 index 0000000000..c515c162f8 Binary files /dev/null and b/docs/media/conj1.jpg differ diff --git a/docs/media/conj10.jpg b/docs/media/conj10.jpg new file mode 100644 index 0000000000..1365a92bd5 Binary files /dev/null and b/docs/media/conj10.jpg differ diff --git a/docs/media/conj2.jpg b/docs/media/conj2.jpg new file mode 100644 index 0000000000..d5d05ce9fa Binary files /dev/null and b/docs/media/conj2.jpg differ diff --git a/docs/media/conj3.jpg b/docs/media/conj3.jpg new file mode 100644 index 0000000000..75c8d02ff0 Binary files /dev/null and b/docs/media/conj3.jpg differ diff --git a/docs/media/conj4.jpg b/docs/media/conj4.jpg new file mode 100644 index 0000000000..9006f354fc Binary files /dev/null and b/docs/media/conj4.jpg differ diff --git a/docs/media/conj5.jpg b/docs/media/conj5.jpg new file mode 100644 index 0000000000..7e3b8f7b35 Binary files /dev/null and b/docs/media/conj5.jpg differ diff --git a/docs/media/conj6.jpg b/docs/media/conj6.jpg new file mode 100644 index 0000000000..5d407a6924 Binary files /dev/null and b/docs/media/conj6.jpg differ diff --git a/docs/media/conj7.jpg b/docs/media/conj7.jpg new file mode 100644 index 0000000000..37376fea88 Binary files /dev/null and b/docs/media/conj7.jpg differ diff --git a/docs/media/conj8.jpg b/docs/media/conj8.jpg new file mode 100644 index 0000000000..4eecf75c24 Binary files /dev/null and b/docs/media/conj8.jpg differ diff --git a/docs/media/conj9.jpg b/docs/media/conj9.jpg new file mode 100644 index 0000000000..45b5c9051b Binary files /dev/null and b/docs/media/conj9.jpg differ diff --git a/docs/media/copy_alert_message.png b/docs/media/copy_alert_message.png new file mode 100644 index 0000000000..0931d88550 Binary files /dev/null and b/docs/media/copy_alert_message.png differ diff --git a/docs/media/copy_edit_alert.png b/docs/media/copy_edit_alert.png new file mode 100644 index 0000000000..29d0527159 Binary files /dev/null and b/docs/media/copy_edit_alert.png differ diff --git a/docs/media/create-template-1.png b/docs/media/create-template-1.png new file mode 100644 index 0000000000..0358768eb8 Binary files /dev/null and b/docs/media/create-template-1.png differ diff --git a/docs/media/create-template-10.png b/docs/media/create-template-10.png new file mode 100644 index 0000000000..12deb5ce9b Binary files /dev/null and b/docs/media/create-template-10.png differ diff --git a/docs/media/create-template-11.png b/docs/media/create-template-11.png new file mode 100644 index 0000000000..003b05bc8d Binary files /dev/null and b/docs/media/create-template-11.png differ diff --git a/docs/media/create-template-12.png b/docs/media/create-template-12.png new file mode 100644 index 0000000000..fe4d999663 Binary files /dev/null and b/docs/media/create-template-12.png differ diff --git a/docs/media/create-template-13.png b/docs/media/create-template-13.png new file mode 100644 index 0000000000..0831126d09 Binary files /dev/null and b/docs/media/create-template-13.png differ diff --git a/docs/media/create-template-15.png b/docs/media/create-template-15.png new file mode 100644 index 0000000000..19734c337a Binary files /dev/null and b/docs/media/create-template-15.png differ diff --git a/docs/media/create-template-16.png b/docs/media/create-template-16.png new file mode 100644 index 0000000000..71665a0ffb Binary files /dev/null and b/docs/media/create-template-16.png differ diff --git a/docs/media/create-template-17.png b/docs/media/create-template-17.png new file mode 100644 index 0000000000..0a6308483d Binary files /dev/null and b/docs/media/create-template-17.png differ diff --git a/docs/media/create-template-19.png b/docs/media/create-template-19.png new file mode 100644 index 0000000000..a62b2825f8 Binary files /dev/null and b/docs/media/create-template-19.png differ diff --git a/docs/media/create-template-2.png b/docs/media/create-template-2.png new file mode 100644 index 0000000000..20466a6723 Binary files /dev/null and b/docs/media/create-template-2.png differ diff --git a/docs/media/create-template-20.png b/docs/media/create-template-20.png new file mode 100644 index 0000000000..d4beb2bd28 Binary files /dev/null and b/docs/media/create-template-20.png differ diff --git a/docs/media/create-template-21.png b/docs/media/create-template-21.png new file mode 100644 index 0000000000..e2cb2f9ade Binary files /dev/null and b/docs/media/create-template-21.png differ diff --git a/docs/media/create-template-22.png b/docs/media/create-template-22.png new file mode 100644 index 0000000000..b7f8532bf7 Binary files /dev/null and b/docs/media/create-template-22.png differ diff --git a/docs/media/create-template-23.png b/docs/media/create-template-23.png new file mode 100644 index 0000000000..03de846b1a Binary files /dev/null and b/docs/media/create-template-23.png differ diff --git a/docs/media/create-template-24.png b/docs/media/create-template-24.png new file mode 100644 index 0000000000..ef381f6934 Binary files /dev/null and b/docs/media/create-template-24.png differ diff --git a/docs/media/create-template-25.png b/docs/media/create-template-25.png new file mode 100644 index 0000000000..88d2a17a59 Binary files /dev/null and b/docs/media/create-template-25.png differ diff --git a/docs/media/create-template-26.png b/docs/media/create-template-26.png new file mode 100644 index 0000000000..b6816c88e2 Binary files /dev/null and b/docs/media/create-template-26.png differ diff --git a/docs/media/create-template-27.png b/docs/media/create-template-27.png new file mode 100644 index 0000000000..ac60c901a3 Binary files /dev/null and b/docs/media/create-template-27.png differ diff --git a/docs/media/create-template-28.png b/docs/media/create-template-28.png new file mode 100644 index 0000000000..69d6cf1c26 Binary files /dev/null and b/docs/media/create-template-28.png differ diff --git a/docs/media/create-template-29.png b/docs/media/create-template-29.png new file mode 100644 index 0000000000..1dcb26094f Binary files /dev/null and b/docs/media/create-template-29.png differ diff --git a/docs/media/create-template-3.png b/docs/media/create-template-3.png new file mode 100644 index 0000000000..d2bf614be4 Binary files /dev/null and b/docs/media/create-template-3.png differ diff --git a/docs/media/create-template-30.png b/docs/media/create-template-30.png new file mode 100644 index 0000000000..9421cb5f78 Binary files /dev/null and b/docs/media/create-template-30.png differ diff --git a/docs/media/create-template-31.png b/docs/media/create-template-31.png new file mode 100644 index 0000000000..3a07d05822 Binary files /dev/null and b/docs/media/create-template-31.png differ diff --git a/docs/media/create-template-32.png b/docs/media/create-template-32.png new file mode 100644 index 0000000000..3150321434 Binary files /dev/null and b/docs/media/create-template-32.png differ diff --git a/docs/media/create-template-33.png b/docs/media/create-template-33.png new file mode 100644 index 0000000000..8d2bd373c4 Binary files /dev/null and b/docs/media/create-template-33.png differ diff --git a/docs/media/create-template-34.png b/docs/media/create-template-34.png new file mode 100644 index 0000000000..8d7069357d Binary files /dev/null and b/docs/media/create-template-34.png differ diff --git a/docs/media/create-template-35.png b/docs/media/create-template-35.png new file mode 100644 index 0000000000..7bc9025d50 Binary files /dev/null and b/docs/media/create-template-35.png differ diff --git a/docs/media/create-template-4.png b/docs/media/create-template-4.png new file mode 100644 index 0000000000..b6d7201afc Binary files /dev/null and b/docs/media/create-template-4.png differ diff --git a/docs/media/create-template-5.png b/docs/media/create-template-5.png new file mode 100644 index 0000000000..d24ad3c233 Binary files /dev/null and b/docs/media/create-template-5.png differ diff --git a/docs/media/create-template-6.png b/docs/media/create-template-6.png new file mode 100644 index 0000000000..47fd843b46 Binary files /dev/null and b/docs/media/create-template-6.png differ diff --git a/docs/media/create-template-7.png b/docs/media/create-template-7.png new file mode 100644 index 0000000000..8803035b01 Binary files /dev/null and b/docs/media/create-template-7.png differ diff --git a/docs/media/create-template-8.png b/docs/media/create-template-8.png new file mode 100644 index 0000000000..8c46199336 Binary files /dev/null and b/docs/media/create-template-8.png differ diff --git a/docs/media/create-template-9.png b/docs/media/create-template-9.png new file mode 100644 index 0000000000..49fc2ef426 Binary files /dev/null and b/docs/media/create-template-9.png differ diff --git a/docs/media/due_date_display.png b/docs/media/due_date_display.png new file mode 100644 index 0000000000..48464fd008 Binary files /dev/null and b/docs/media/due_date_display.png differ diff --git a/docs/media/edit_due_date_action.png b/docs/media/edit_due_date_action.png new file mode 100644 index 0000000000..eb5fbc2577 Binary files /dev/null and b/docs/media/edit_due_date_action.png differ diff --git a/docs/media/epub_logo_color_ht39.gif b/docs/media/epub_logo_color_ht39.gif new file mode 100644 index 0000000000..337ad73fb6 Binary files /dev/null and b/docs/media/epub_logo_color_ht39.gif differ diff --git a/docs/media/evergreen_logo.gif b/docs/media/evergreen_logo.gif new file mode 100644 index 0000000000..c7c79111c5 Binary files /dev/null and b/docs/media/evergreen_logo.gif differ diff --git a/docs/media/folder-1.png b/docs/media/folder-1.png new file mode 100644 index 0000000000..0e24910efb Binary files /dev/null and b/docs/media/folder-1.png differ diff --git a/docs/media/folder-10.png b/docs/media/folder-10.png new file mode 100644 index 0000000000..7b5acd9198 Binary files /dev/null and b/docs/media/folder-10.png differ diff --git a/docs/media/folder-11.png b/docs/media/folder-11.png new file mode 100644 index 0000000000..e358551745 Binary files /dev/null and b/docs/media/folder-11.png differ diff --git a/docs/media/folder-12.png b/docs/media/folder-12.png new file mode 100644 index 0000000000..6a5f98fab8 Binary files /dev/null and b/docs/media/folder-12.png differ diff --git a/docs/media/folder-13.png b/docs/media/folder-13.png new file mode 100644 index 0000000000..62ecd43fc9 Binary files /dev/null and b/docs/media/folder-13.png differ diff --git a/docs/media/folder-14.png b/docs/media/folder-14.png new file mode 100644 index 0000000000..f7ff979d4a Binary files /dev/null and b/docs/media/folder-14.png differ diff --git a/docs/media/folder-7a.png b/docs/media/folder-7a.png new file mode 100644 index 0000000000..cadf59fd2f Binary files /dev/null and b/docs/media/folder-7a.png differ diff --git a/docs/media/generate-report-1.png b/docs/media/generate-report-1.png new file mode 100644 index 0000000000..a208d89e9e Binary files /dev/null and b/docs/media/generate-report-1.png differ diff --git a/docs/media/generate-report-10.png b/docs/media/generate-report-10.png new file mode 100644 index 0000000000..9980b92096 Binary files /dev/null and b/docs/media/generate-report-10.png differ diff --git a/docs/media/generate-report-14.png b/docs/media/generate-report-14.png new file mode 100644 index 0000000000..e6846b560a Binary files /dev/null and b/docs/media/generate-report-14.png differ diff --git a/docs/media/generate-report-2.png b/docs/media/generate-report-2.png new file mode 100644 index 0000000000..8ba8a9773d Binary files /dev/null and b/docs/media/generate-report-2.png differ diff --git a/docs/media/generate-report-3.png b/docs/media/generate-report-3.png new file mode 100644 index 0000000000..e5cdfdb3ae Binary files /dev/null and b/docs/media/generate-report-3.png differ diff --git a/docs/media/generate-report-8.png b/docs/media/generate-report-8.png new file mode 100644 index 0000000000..72a700271c Binary files /dev/null and b/docs/media/generate-report-8.png differ diff --git a/docs/media/generate-report-9.png b/docs/media/generate-report-9.png new file mode 100644 index 0000000000..5c6aa4468f Binary files /dev/null and b/docs/media/generate-report-9.png differ diff --git a/docs/media/hold-1.png b/docs/media/hold-1.png new file mode 100644 index 0000000000..18dbf6c59e Binary files /dev/null and b/docs/media/hold-1.png differ diff --git a/docs/media/hold-10.png b/docs/media/hold-10.png new file mode 100644 index 0000000000..39744442d1 Binary files /dev/null and b/docs/media/hold-10.png differ diff --git a/docs/media/hold-11.png b/docs/media/hold-11.png new file mode 100644 index 0000000000..c20be3aad1 Binary files /dev/null and b/docs/media/hold-11.png differ diff --git a/docs/media/hold-12.png b/docs/media/hold-12.png new file mode 100644 index 0000000000..012409912f Binary files /dev/null and b/docs/media/hold-12.png differ diff --git a/docs/media/hold-14.png b/docs/media/hold-14.png new file mode 100644 index 0000000000..fe211fd0e1 Binary files /dev/null and b/docs/media/hold-14.png differ diff --git a/docs/media/hold-15.png b/docs/media/hold-15.png new file mode 100644 index 0000000000..37dbaedcdf Binary files /dev/null and b/docs/media/hold-15.png differ diff --git a/docs/media/hold-16.png b/docs/media/hold-16.png new file mode 100644 index 0000000000..235b0886ae Binary files /dev/null and b/docs/media/hold-16.png differ diff --git a/docs/media/hold-17.png b/docs/media/hold-17.png new file mode 100644 index 0000000000..569a274287 Binary files /dev/null and b/docs/media/hold-17.png differ diff --git a/docs/media/hold-18.png b/docs/media/hold-18.png new file mode 100644 index 0000000000..58147bf78f Binary files /dev/null and b/docs/media/hold-18.png differ diff --git a/docs/media/hold-19.png b/docs/media/hold-19.png new file mode 100644 index 0000000000..86ffac89dd Binary files /dev/null and b/docs/media/hold-19.png differ diff --git a/docs/media/hold-2.png b/docs/media/hold-2.png new file mode 100644 index 0000000000..b9968a97c5 Binary files /dev/null and b/docs/media/hold-2.png differ diff --git a/docs/media/hold-20.png b/docs/media/hold-20.png new file mode 100644 index 0000000000..3aeb8f93db Binary files /dev/null and b/docs/media/hold-20.png differ diff --git a/docs/media/hold-21.png b/docs/media/hold-21.png new file mode 100644 index 0000000000..bb1422cee8 Binary files /dev/null and b/docs/media/hold-21.png differ diff --git a/docs/media/hold-22.png b/docs/media/hold-22.png new file mode 100644 index 0000000000..cc9050177b Binary files /dev/null and b/docs/media/hold-22.png differ diff --git a/docs/media/hold-23.png b/docs/media/hold-23.png new file mode 100644 index 0000000000..e08d9bdf27 Binary files /dev/null and b/docs/media/hold-23.png differ diff --git a/docs/media/hold-24.png b/docs/media/hold-24.png new file mode 100644 index 0000000000..69d78aa256 Binary files /dev/null and b/docs/media/hold-24.png differ diff --git a/docs/media/hold-25.png b/docs/media/hold-25.png new file mode 100644 index 0000000000..8df926061d Binary files /dev/null and b/docs/media/hold-25.png differ diff --git a/docs/media/hold-26.png b/docs/media/hold-26.png new file mode 100644 index 0000000000..73f26f1251 Binary files /dev/null and b/docs/media/hold-26.png differ diff --git a/docs/media/hold-27.png b/docs/media/hold-27.png new file mode 100644 index 0000000000..7b57b8899e Binary files /dev/null and b/docs/media/hold-27.png differ diff --git a/docs/media/hold-28.png b/docs/media/hold-28.png new file mode 100644 index 0000000000..f569003995 Binary files /dev/null and b/docs/media/hold-28.png differ diff --git a/docs/media/hold-29.png b/docs/media/hold-29.png new file mode 100644 index 0000000000..b0d265786f Binary files /dev/null and b/docs/media/hold-29.png differ diff --git a/docs/media/hold-4.png b/docs/media/hold-4.png new file mode 100644 index 0000000000..79e8a419eb Binary files /dev/null and b/docs/media/hold-4.png differ diff --git a/docs/media/hold-5.png b/docs/media/hold-5.png new file mode 100644 index 0000000000..3038e93b3d Binary files /dev/null and b/docs/media/hold-5.png differ diff --git a/docs/media/hold-6.png b/docs/media/hold-6.png new file mode 100644 index 0000000000..d57e25d6e0 Binary files /dev/null and b/docs/media/hold-6.png differ diff --git a/docs/media/hold-7.png b/docs/media/hold-7.png new file mode 100644 index 0000000000..494d5fe5cf Binary files /dev/null and b/docs/media/hold-7.png differ diff --git a/docs/media/hold-8.png b/docs/media/hold-8.png new file mode 100644 index 0000000000..780fd2a7d6 Binary files /dev/null and b/docs/media/hold-8.png differ diff --git a/docs/media/hold-9.png b/docs/media/hold-9.png new file mode 100644 index 0000000000..2b2ce2b52a Binary files /dev/null and b/docs/media/hold-9.png differ diff --git a/docs/media/holds-clearing-1.png b/docs/media/holds-clearing-1.png new file mode 100644 index 0000000000..f13d58b4dd Binary files /dev/null and b/docs/media/holds-clearing-1.png differ diff --git a/docs/media/holds-clearing-2.png b/docs/media/holds-clearing-2.png new file mode 100644 index 0000000000..0c40e2129b Binary files /dev/null and b/docs/media/holds-clearing-2.png differ diff --git a/docs/media/holds-clearing-3.png b/docs/media/holds-clearing-3.png new file mode 100644 index 0000000000..4810e851fe Binary files /dev/null and b/docs/media/holds-clearing-3.png differ diff --git a/docs/media/holds-clearing-4.png b/docs/media/holds-clearing-4.png new file mode 100644 index 0000000000..1bbc2a3ea4 Binary files /dev/null and b/docs/media/holds-clearing-4.png differ diff --git a/docs/media/holds-managing-1.png b/docs/media/holds-managing-1.png new file mode 100644 index 0000000000..298c431279 Binary files /dev/null and b/docs/media/holds-managing-1.png differ diff --git a/docs/media/holds-managing-10.png b/docs/media/holds-managing-10.png new file mode 100644 index 0000000000..fab2a8be54 Binary files /dev/null and b/docs/media/holds-managing-10.png differ diff --git a/docs/media/holds-managing-11.png b/docs/media/holds-managing-11.png new file mode 100644 index 0000000000..89beec91a0 Binary files /dev/null and b/docs/media/holds-managing-11.png differ diff --git a/docs/media/holds-managing-12.png b/docs/media/holds-managing-12.png new file mode 100644 index 0000000000..9265a57634 Binary files /dev/null and b/docs/media/holds-managing-12.png differ diff --git a/docs/media/holds-managing-13.png b/docs/media/holds-managing-13.png new file mode 100644 index 0000000000..2765f756e3 Binary files /dev/null and b/docs/media/holds-managing-13.png differ diff --git a/docs/media/holds-managing-14.png b/docs/media/holds-managing-14.png new file mode 100644 index 0000000000..ee8649480d Binary files /dev/null and b/docs/media/holds-managing-14.png differ diff --git a/docs/media/holds-managing-15.png b/docs/media/holds-managing-15.png new file mode 100644 index 0000000000..20dd0b454b Binary files /dev/null and b/docs/media/holds-managing-15.png differ diff --git a/docs/media/holds-managing-16.png b/docs/media/holds-managing-16.png new file mode 100644 index 0000000000..2db6c18230 Binary files /dev/null and b/docs/media/holds-managing-16.png differ diff --git a/docs/media/holds-managing-17.png b/docs/media/holds-managing-17.png new file mode 100644 index 0000000000..c203b51e5a Binary files /dev/null and b/docs/media/holds-managing-17.png differ diff --git a/docs/media/holds-managing-18.png b/docs/media/holds-managing-18.png new file mode 100644 index 0000000000..6e6d6d749a Binary files /dev/null and b/docs/media/holds-managing-18.png differ diff --git a/docs/media/holds-managing-19.png b/docs/media/holds-managing-19.png new file mode 100644 index 0000000000..bb14d68cff Binary files /dev/null and b/docs/media/holds-managing-19.png differ diff --git a/docs/media/holds-managing-2.png b/docs/media/holds-managing-2.png new file mode 100644 index 0000000000..4b7af26bcb Binary files /dev/null and b/docs/media/holds-managing-2.png differ diff --git a/docs/media/holds-managing-3.png b/docs/media/holds-managing-3.png new file mode 100644 index 0000000000..16ca2674f6 Binary files /dev/null and b/docs/media/holds-managing-3.png differ diff --git a/docs/media/holds-managing-4.png b/docs/media/holds-managing-4.png new file mode 100644 index 0000000000..34e758d6eb Binary files /dev/null and b/docs/media/holds-managing-4.png differ diff --git a/docs/media/holds-managing-5.png b/docs/media/holds-managing-5.png new file mode 100644 index 0000000000..96b836f3fe Binary files /dev/null and b/docs/media/holds-managing-5.png differ diff --git a/docs/media/holds-managing-6.png b/docs/media/holds-managing-6.png new file mode 100644 index 0000000000..f7ce7ebd7f Binary files /dev/null and b/docs/media/holds-managing-6.png differ diff --git a/docs/media/holds-managing-7.png b/docs/media/holds-managing-7.png new file mode 100644 index 0000000000..12f7ffef38 Binary files /dev/null and b/docs/media/holds-managing-7.png differ diff --git a/docs/media/holds-managing-8.png b/docs/media/holds-managing-8.png new file mode 100644 index 0000000000..bbbff642ba Binary files /dev/null and b/docs/media/holds-managing-8.png differ diff --git a/docs/media/holds-managing-9.png b/docs/media/holds-managing-9.png new file mode 100644 index 0000000000..4b2cc8315b Binary files /dev/null and b/docs/media/holds-managing-9.png differ diff --git a/docs/media/holds-notifications-1.png b/docs/media/holds-notifications-1.png new file mode 100644 index 0000000000..d389d5715b Binary files /dev/null and b/docs/media/holds-notifications-1.png differ diff --git a/docs/media/holds-notifications-2.png b/docs/media/holds-notifications-2.png new file mode 100644 index 0000000000..3e1eadb011 Binary files /dev/null and b/docs/media/holds-notifications-2.png differ diff --git a/docs/media/holds-notifications-3.png b/docs/media/holds-notifications-3.png new file mode 100644 index 0000000000..bfb8ee201d Binary files /dev/null and b/docs/media/holds-notifications-3.png differ diff --git a/docs/media/holds-notifications-4.png b/docs/media/holds-notifications-4.png new file mode 100644 index 0000000000..fd9201b872 Binary files /dev/null and b/docs/media/holds-notifications-4.png differ diff --git a/docs/media/holds-placing-1.png b/docs/media/holds-placing-1.png new file mode 100644 index 0000000000..5f60630e8b Binary files /dev/null and b/docs/media/holds-placing-1.png differ diff --git a/docs/media/holds-placing-10.png b/docs/media/holds-placing-10.png new file mode 100644 index 0000000000..46fe88a112 Binary files /dev/null and b/docs/media/holds-placing-10.png differ diff --git a/docs/media/holds-placing-11.png b/docs/media/holds-placing-11.png new file mode 100644 index 0000000000..cd1a10201e Binary files /dev/null and b/docs/media/holds-placing-11.png differ diff --git a/docs/media/holds-placing-2.png b/docs/media/holds-placing-2.png new file mode 100644 index 0000000000..71daec5c6c Binary files /dev/null and b/docs/media/holds-placing-2.png differ diff --git a/docs/media/holds-placing-3.png b/docs/media/holds-placing-3.png new file mode 100644 index 0000000000..16ca2674f6 Binary files /dev/null and b/docs/media/holds-placing-3.png differ diff --git a/docs/media/holds-placing-4.png b/docs/media/holds-placing-4.png new file mode 100644 index 0000000000..7b0c2e7423 Binary files /dev/null and b/docs/media/holds-placing-4.png differ diff --git a/docs/media/holds-placing-5.png b/docs/media/holds-placing-5.png new file mode 100644 index 0000000000..7ef50cb46f Binary files /dev/null and b/docs/media/holds-placing-5.png differ diff --git a/docs/media/holds-placing-6.png b/docs/media/holds-placing-6.png new file mode 100644 index 0000000000..d8e7c3d5f9 Binary files /dev/null and b/docs/media/holds-placing-6.png differ diff --git a/docs/media/holds-placing-7.png b/docs/media/holds-placing-7.png new file mode 100644 index 0000000000..aa0ec912a7 Binary files /dev/null and b/docs/media/holds-placing-7.png differ diff --git a/docs/media/holds-placing-8.png b/docs/media/holds-placing-8.png new file mode 100644 index 0000000000..c354a9d4d9 Binary files /dev/null and b/docs/media/holds-placing-8.png differ diff --git a/docs/media/holds-placing-9.png b/docs/media/holds-placing-9.png new file mode 100644 index 0000000000..41fe57efda Binary files /dev/null and b/docs/media/holds-placing-9.png differ diff --git a/docs/media/holds-pull-1.png b/docs/media/holds-pull-1.png new file mode 100644 index 0000000000..4973c579ea Binary files /dev/null and b/docs/media/holds-pull-1.png differ diff --git a/docs/media/holds-pull-2.png b/docs/media/holds-pull-2.png new file mode 100644 index 0000000000..8798d0ad1f Binary files /dev/null and b/docs/media/holds-pull-2.png differ diff --git a/docs/media/holds-pull-3.png b/docs/media/holds-pull-3.png new file mode 100644 index 0000000000..494febb84e Binary files /dev/null and b/docs/media/holds-pull-3.png differ diff --git a/docs/media/holds-pull-4.png b/docs/media/holds-pull-4.png new file mode 100644 index 0000000000..df4dde79e1 Binary files /dev/null and b/docs/media/holds-pull-4.png differ diff --git a/docs/media/holds-pull-5.png b/docs/media/holds-pull-5.png new file mode 100644 index 0000000000..05b2ea7649 Binary files /dev/null and b/docs/media/holds-pull-5.png differ diff --git a/docs/media/holds-pull-5a.png b/docs/media/holds-pull-5a.png new file mode 100644 index 0000000000..e418fb369d Binary files /dev/null and b/docs/media/holds-pull-5a.png differ diff --git a/docs/media/holds-pull-6.png b/docs/media/holds-pull-6.png new file mode 100644 index 0000000000..98fbabbef6 Binary files /dev/null and b/docs/media/holds-pull-6.png differ diff --git a/docs/media/holds-pull-7.png b/docs/media/holds-pull-7.png new file mode 100644 index 0000000000..e0a39491d7 Binary files /dev/null and b/docs/media/holds-pull-7.png differ diff --git a/docs/media/holds-pull-8.png b/docs/media/holds-pull-8.png new file mode 100644 index 0000000000..95caa42ab6 Binary files /dev/null and b/docs/media/holds-pull-8.png differ diff --git a/docs/media/holds-pull-9.png b/docs/media/holds-pull-9.png new file mode 100644 index 0000000000..17c9eb021e Binary files /dev/null and b/docs/media/holds-pull-9.png differ diff --git a/docs/media/in_house_use.png b/docs/media/in_house_use.png new file mode 100644 index 0000000000..3c15245a19 Binary files /dev/null and b/docs/media/in_house_use.png differ diff --git a/docs/media/item_status_altview.png b/docs/media/item_status_altview.png new file mode 100644 index 0000000000..5baa0ad9a0 Binary files /dev/null and b/docs/media/item_status_altview.png differ diff --git a/docs/media/item_status_barcode.png b/docs/media/item_status_barcode.png new file mode 100644 index 0000000000..10d7e21a29 Binary files /dev/null and b/docs/media/item_status_barcode.png differ diff --git a/docs/media/item_status_list_view.png b/docs/media/item_status_list_view.png new file mode 100644 index 0000000000..82b6197168 Binary files /dev/null and b/docs/media/item_status_list_view.png differ diff --git a/docs/media/item_status_menu.png b/docs/media/item_status_menu.png new file mode 100644 index 0000000000..7ecd0a61ce Binary files /dev/null and b/docs/media/item_status_menu.png differ diff --git a/docs/media/items_out_click.png b/docs/media/items_out_click.png new file mode 100644 index 0000000000..ac9542f849 Binary files /dev/null and b/docs/media/items_out_click.png differ diff --git a/docs/media/k_book_record.png b/docs/media/k_book_record.png new file mode 100644 index 0000000000..e41a886706 Binary files /dev/null and b/docs/media/k_book_record.png differ diff --git a/docs/media/last_few_circs_action.png b/docs/media/last_few_circs_action.png new file mode 100644 index 0000000000..6ccfaee033 Binary files /dev/null and b/docs/media/last_few_circs_action.png differ diff --git a/docs/media/last_few_circs_display.png b/docs/media/last_few_circs_display.png new file mode 100644 index 0000000000..0e66051d1c Binary files /dev/null and b/docs/media/last_few_circs_display.png differ diff --git a/docs/media/lost_cr_section.png b/docs/media/lost_cr_section.png new file mode 100644 index 0000000000..1a2538b96d Binary files /dev/null and b/docs/media/lost_cr_section.png differ diff --git a/docs/media/lsa-1.png b/docs/media/lsa-1.png new file mode 100644 index 0000000000..eee8707b4c Binary files /dev/null and b/docs/media/lsa-1.png differ diff --git a/docs/media/lsa-10.jpg b/docs/media/lsa-10.jpg new file mode 100644 index 0000000000..7c578e03b1 Binary files /dev/null and b/docs/media/lsa-10.jpg differ diff --git a/docs/media/lsa-11.jpg b/docs/media/lsa-11.jpg new file mode 100644 index 0000000000..4df7484298 Binary files /dev/null and b/docs/media/lsa-11.jpg differ diff --git a/docs/media/lsa-12.jpg b/docs/media/lsa-12.jpg new file mode 100644 index 0000000000..c1c550546d Binary files /dev/null and b/docs/media/lsa-12.jpg differ diff --git a/docs/media/lsa-14.jpg b/docs/media/lsa-14.jpg new file mode 100644 index 0000000000..bdf842c60a Binary files /dev/null and b/docs/media/lsa-14.jpg differ diff --git a/docs/media/lsa-16.jpg b/docs/media/lsa-16.jpg new file mode 100644 index 0000000000..90fdca61a8 Binary files /dev/null and b/docs/media/lsa-16.jpg differ diff --git a/docs/media/lsa-17.jpg b/docs/media/lsa-17.jpg new file mode 100644 index 0000000000..a08b590caf Binary files /dev/null and b/docs/media/lsa-17.jpg differ diff --git a/docs/media/lsa-18.jpg b/docs/media/lsa-18.jpg new file mode 100644 index 0000000000..a3710530e7 Binary files /dev/null and b/docs/media/lsa-18.jpg differ diff --git a/docs/media/lsa-2.jpg b/docs/media/lsa-2.jpg new file mode 100644 index 0000000000..2cdd562075 Binary files /dev/null and b/docs/media/lsa-2.jpg differ diff --git a/docs/media/lsa-22.png b/docs/media/lsa-22.png new file mode 100644 index 0000000000..b3f55dfe0f Binary files /dev/null and b/docs/media/lsa-22.png differ diff --git a/docs/media/lsa-23.jpg b/docs/media/lsa-23.jpg new file mode 100644 index 0000000000..9fbdf96ba1 Binary files /dev/null and b/docs/media/lsa-23.jpg differ diff --git a/docs/media/lsa-25.jpg b/docs/media/lsa-25.jpg new file mode 100644 index 0000000000..2cbb735295 Binary files /dev/null and b/docs/media/lsa-25.jpg differ diff --git a/docs/media/lsa-26.jpg b/docs/media/lsa-26.jpg new file mode 100644 index 0000000000..9b1575c1fd Binary files /dev/null and b/docs/media/lsa-26.jpg differ diff --git a/docs/media/lsa-27.jpg b/docs/media/lsa-27.jpg new file mode 100644 index 0000000000..36a024c049 Binary files /dev/null and b/docs/media/lsa-27.jpg differ diff --git a/docs/media/lsa-28.jpg b/docs/media/lsa-28.jpg new file mode 100644 index 0000000000..ccf0b1a705 Binary files /dev/null and b/docs/media/lsa-28.jpg differ diff --git a/docs/media/lsa-32.jpg b/docs/media/lsa-32.jpg new file mode 100644 index 0000000000..bf03d62108 Binary files /dev/null and b/docs/media/lsa-32.jpg differ diff --git a/docs/media/lsa-33.jpg b/docs/media/lsa-33.jpg new file mode 100644 index 0000000000..2a211fb686 Binary files /dev/null and b/docs/media/lsa-33.jpg differ diff --git a/docs/media/lsa-4.jpg b/docs/media/lsa-4.jpg new file mode 100644 index 0000000000..0406e4afda Binary files /dev/null and b/docs/media/lsa-4.jpg differ diff --git a/docs/media/lsa-5.jpg b/docs/media/lsa-5.jpg new file mode 100644 index 0000000000..da0e056bce Binary files /dev/null and b/docs/media/lsa-5.jpg differ diff --git a/docs/media/lsa-7.jpg b/docs/media/lsa-7.jpg new file mode 100644 index 0000000000..6544913195 Binary files /dev/null and b/docs/media/lsa-7.jpg differ diff --git a/docs/media/lsa-8.jpg b/docs/media/lsa-8.jpg new file mode 100644 index 0000000000..4de9cf445e Binary files /dev/null and b/docs/media/lsa-8.jpg differ diff --git a/docs/media/lsa-closed-mountain-1.png b/docs/media/lsa-closed-mountain-1.png new file mode 100644 index 0000000000..b7eb2c68b8 Binary files /dev/null and b/docs/media/lsa-closed-mountain-1.png differ diff --git a/docs/media/lsa-closed-mountain-2.png b/docs/media/lsa-closed-mountain-2.png new file mode 100644 index 0000000000..f0b1036d69 Binary files /dev/null and b/docs/media/lsa-closed-mountain-2.png differ diff --git a/docs/media/lsa-group-0.png b/docs/media/lsa-group-0.png new file mode 100644 index 0000000000..4d75083ac4 Binary files /dev/null and b/docs/media/lsa-group-0.png differ diff --git a/docs/media/lsa-group-1.png b/docs/media/lsa-group-1.png new file mode 100644 index 0000000000..46a0a0f832 Binary files /dev/null and b/docs/media/lsa-group-1.png differ diff --git a/docs/media/lsa-group-1a.png b/docs/media/lsa-group-1a.png new file mode 100644 index 0000000000..a5f4e93259 Binary files /dev/null and b/docs/media/lsa-group-1a.png differ diff --git a/docs/media/lsa-group-2.png b/docs/media/lsa-group-2.png new file mode 100644 index 0000000000..bd3717313e Binary files /dev/null and b/docs/media/lsa-group-2.png differ diff --git a/docs/media/lsa-group-3.png b/docs/media/lsa-group-3.png new file mode 100644 index 0000000000..328e7333a1 Binary files /dev/null and b/docs/media/lsa-group-3.png differ diff --git a/docs/media/lsa-group-4.png b/docs/media/lsa-group-4.png new file mode 100644 index 0000000000..4e378d3815 Binary files /dev/null and b/docs/media/lsa-group-4.png differ diff --git a/docs/media/lsa-group-5.png b/docs/media/lsa-group-5.png new file mode 100644 index 0000000000..53ee8edd31 Binary files /dev/null and b/docs/media/lsa-group-5.png differ diff --git a/docs/media/lsa-group-6.png b/docs/media/lsa-group-6.png new file mode 100644 index 0000000000..5a17f16547 Binary files /dev/null and b/docs/media/lsa-group-6.png differ diff --git a/docs/media/lsa-statcat-1.png b/docs/media/lsa-statcat-1.png new file mode 100644 index 0000000000..f54232ff5b Binary files /dev/null and b/docs/media/lsa-statcat-1.png differ diff --git a/docs/media/lsa-statcat-2.png b/docs/media/lsa-statcat-2.png new file mode 100644 index 0000000000..770d7a7538 Binary files /dev/null and b/docs/media/lsa-statcat-2.png differ diff --git a/docs/media/lsa-statcat-3.png b/docs/media/lsa-statcat-3.png new file mode 100644 index 0000000000..e4ec35d89b Binary files /dev/null and b/docs/media/lsa-statcat-3.png differ diff --git a/docs/media/lsa-statcat-4.png b/docs/media/lsa-statcat-4.png new file mode 100644 index 0000000000..99aa0946c1 Binary files /dev/null and b/docs/media/lsa-statcat-4.png differ diff --git a/docs/media/lsa-statcat-5.png b/docs/media/lsa-statcat-5.png new file mode 100644 index 0000000000..565d632d83 Binary files /dev/null and b/docs/media/lsa-statcat-5.png differ diff --git a/docs/media/lsa-statcat-6.png b/docs/media/lsa-statcat-6.png new file mode 100644 index 0000000000..b7bb8585a6 Binary files /dev/null and b/docs/media/lsa-statcat-6.png differ diff --git a/docs/media/lsa-statcat-7.png b/docs/media/lsa-statcat-7.png new file mode 100644 index 0000000000..964fad421e Binary files /dev/null and b/docs/media/lsa-statcat-7.png differ diff --git a/docs/media/lsa-statcat-8.png b/docs/media/lsa-statcat-8.png new file mode 100644 index 0000000000..3156964623 Binary files /dev/null and b/docs/media/lsa-statcat-8.png differ diff --git a/docs/media/main_logo.jpg b/docs/media/main_logo.jpg new file mode 100644 index 0000000000..633b7a75f9 Binary files /dev/null and b/docs/media/main_logo.jpg differ diff --git a/docs/media/mark_claims_returned.png b/docs/media/mark_claims_returned.png new file mode 100644 index 0000000000..6818ae1e42 Binary files /dev/null and b/docs/media/mark_claims_returned.png differ diff --git a/docs/media/mark_lost.png b/docs/media/mark_lost.png new file mode 100644 index 0000000000..b63df20d99 Binary files /dev/null and b/docs/media/mark_lost.png differ diff --git a/docs/media/mark_missing_damaged.png b/docs/media/mark_missing_damaged.png new file mode 100644 index 0000000000..ebb6b9ca0e Binary files /dev/null and b/docs/media/mark_missing_damaged.png differ diff --git a/docs/media/monograph_parts1.jpg b/docs/media/monograph_parts1.jpg new file mode 100644 index 0000000000..a105515e14 Binary files /dev/null and b/docs/media/monograph_parts1.jpg differ diff --git a/docs/media/monograph_parts2.jpg b/docs/media/monograph_parts2.jpg new file mode 100644 index 0000000000..20f63e3151 Binary files /dev/null and b/docs/media/monograph_parts2.jpg differ diff --git a/docs/media/monograph_parts3.jpg b/docs/media/monograph_parts3.jpg new file mode 100644 index 0000000000..f40687d941 Binary files /dev/null and b/docs/media/monograph_parts3.jpg differ diff --git a/docs/media/monograph_parts4.jpg b/docs/media/monograph_parts4.jpg new file mode 100644 index 0000000000..ae91126a28 Binary files /dev/null and b/docs/media/monograph_parts4.jpg differ diff --git a/docs/media/monograph_parts5.jpg b/docs/media/monograph_parts5.jpg new file mode 100644 index 0000000000..f4130e34af Binary files /dev/null and b/docs/media/monograph_parts5.jpg differ diff --git a/docs/media/myaccount-bookbags.png b/docs/media/myaccount-bookbags.png new file mode 100644 index 0000000000..940618fe29 Binary files /dev/null and b/docs/media/myaccount-bookbags.png differ diff --git a/docs/media/myaccount-itemrenew.png b/docs/media/myaccount-itemrenew.png new file mode 100644 index 0000000000..dcbb6760e9 Binary files /dev/null and b/docs/media/myaccount-itemrenew.png differ diff --git a/docs/media/myaccount-itemscheckedout.png b/docs/media/myaccount-itemscheckedout.png new file mode 100644 index 0000000000..4e85822bcf Binary files /dev/null and b/docs/media/myaccount-itemscheckedout.png differ diff --git a/docs/media/myaccount-itemsonhold.png b/docs/media/myaccount-itemsonhold.png new file mode 100644 index 0000000000..4b1d5e3d6b Binary files /dev/null and b/docs/media/myaccount-itemsonhold.png differ diff --git a/docs/media/myaccount-login-arrow.png b/docs/media/myaccount-login-arrow.png new file mode 100644 index 0000000000..9cdcdad299 Binary files /dev/null and b/docs/media/myaccount-login-arrow.png differ diff --git a/docs/media/myaccount-login-info.png b/docs/media/myaccount-login-info.png new file mode 100644 index 0000000000..31343612db Binary files /dev/null and b/docs/media/myaccount-login-info.png differ diff --git a/docs/media/myaccount-login.png b/docs/media/myaccount-login.png new file mode 100644 index 0000000000..180e9397a0 Binary files /dev/null and b/docs/media/myaccount-login.png differ diff --git a/docs/media/myaccount-loginpasswordupdate.png b/docs/media/myaccount-loginpasswordupdate.png new file mode 100644 index 0000000000..e29ea6661b Binary files /dev/null and b/docs/media/myaccount-loginpasswordupdate.png differ diff --git a/docs/media/myaccount-summary.png b/docs/media/myaccount-summary.png new file mode 100644 index 0000000000..1ab86b48a3 Binary files /dev/null and b/docs/media/myaccount-summary.png differ diff --git a/docs/media/note.png b/docs/media/note.png new file mode 100644 index 0000000000..198ada5be4 Binary files /dev/null and b/docs/media/note.png differ diff --git a/docs/media/offline-1.png b/docs/media/offline-1.png new file mode 100644 index 0000000000..f7cad0ccd0 Binary files /dev/null and b/docs/media/offline-1.png differ diff --git a/docs/media/offline-10.png b/docs/media/offline-10.png new file mode 100644 index 0000000000..754f007255 Binary files /dev/null and b/docs/media/offline-10.png differ diff --git a/docs/media/offline-11.png b/docs/media/offline-11.png new file mode 100644 index 0000000000..914da51de0 Binary files /dev/null and b/docs/media/offline-11.png differ diff --git a/docs/media/offline-12.png b/docs/media/offline-12.png new file mode 100644 index 0000000000..66b48cf4e7 Binary files /dev/null and b/docs/media/offline-12.png differ diff --git a/docs/media/offline-13.png b/docs/media/offline-13.png new file mode 100644 index 0000000000..fdee7dd22c Binary files /dev/null and b/docs/media/offline-13.png differ diff --git a/docs/media/offline-14.png b/docs/media/offline-14.png new file mode 100644 index 0000000000..0177657633 Binary files /dev/null and b/docs/media/offline-14.png differ diff --git a/docs/media/offline-15.png b/docs/media/offline-15.png new file mode 100644 index 0000000000..ab5c5d6b1e Binary files /dev/null and b/docs/media/offline-15.png differ diff --git a/docs/media/offline-16.png b/docs/media/offline-16.png new file mode 100644 index 0000000000..cc1e9dd5cd Binary files /dev/null and b/docs/media/offline-16.png differ diff --git a/docs/media/offline-17.png b/docs/media/offline-17.png new file mode 100644 index 0000000000..e895e6fffc Binary files /dev/null and b/docs/media/offline-17.png differ diff --git a/docs/media/offline-18.png b/docs/media/offline-18.png new file mode 100644 index 0000000000..6e1ff210fc Binary files /dev/null and b/docs/media/offline-18.png differ diff --git a/docs/media/offline-19.png b/docs/media/offline-19.png new file mode 100644 index 0000000000..6e26d49f2f Binary files /dev/null and b/docs/media/offline-19.png differ diff --git a/docs/media/offline-2.png b/docs/media/offline-2.png new file mode 100644 index 0000000000..9077658945 Binary files /dev/null and b/docs/media/offline-2.png differ diff --git a/docs/media/offline-20.png b/docs/media/offline-20.png new file mode 100644 index 0000000000..8640d72c63 Binary files /dev/null and b/docs/media/offline-20.png differ diff --git a/docs/media/offline-21.png b/docs/media/offline-21.png new file mode 100644 index 0000000000..356598ab7f Binary files /dev/null and b/docs/media/offline-21.png differ diff --git a/docs/media/offline-22.png b/docs/media/offline-22.png new file mode 100644 index 0000000000..e4b0f82893 Binary files /dev/null and b/docs/media/offline-22.png differ diff --git a/docs/media/offline-23.png b/docs/media/offline-23.png new file mode 100644 index 0000000000..d75427808d Binary files /dev/null and b/docs/media/offline-23.png differ diff --git a/docs/media/offline-24.png b/docs/media/offline-24.png new file mode 100644 index 0000000000..7e3b09094e Binary files /dev/null and b/docs/media/offline-24.png differ diff --git a/docs/media/offline-25.png b/docs/media/offline-25.png new file mode 100644 index 0000000000..bda37a6eed Binary files /dev/null and b/docs/media/offline-25.png differ diff --git a/docs/media/offline-26.png b/docs/media/offline-26.png new file mode 100644 index 0000000000..653bfb4bfd Binary files /dev/null and b/docs/media/offline-26.png differ diff --git a/docs/media/offline-27.png b/docs/media/offline-27.png new file mode 100644 index 0000000000..9c0722b793 Binary files /dev/null and b/docs/media/offline-27.png differ diff --git a/docs/media/offline-28.png b/docs/media/offline-28.png new file mode 100644 index 0000000000..9cad8d870a Binary files /dev/null and b/docs/media/offline-28.png differ diff --git a/docs/media/offline-29.png b/docs/media/offline-29.png new file mode 100644 index 0000000000..73a302c211 Binary files /dev/null and b/docs/media/offline-29.png differ diff --git a/docs/media/offline-3.png b/docs/media/offline-3.png new file mode 100644 index 0000000000..a3d644de41 Binary files /dev/null and b/docs/media/offline-3.png differ diff --git a/docs/media/offline-30.png b/docs/media/offline-30.png new file mode 100644 index 0000000000..06bbb9a111 Binary files /dev/null and b/docs/media/offline-30.png differ diff --git a/docs/media/offline-31.png b/docs/media/offline-31.png new file mode 100644 index 0000000000..6b89ac32d6 Binary files /dev/null and b/docs/media/offline-31.png differ diff --git a/docs/media/offline-32.png b/docs/media/offline-32.png new file mode 100644 index 0000000000..d26187900c Binary files /dev/null and b/docs/media/offline-32.png differ diff --git a/docs/media/offline-33.png b/docs/media/offline-33.png new file mode 100644 index 0000000000..bbf9bb16de Binary files /dev/null and b/docs/media/offline-33.png differ diff --git a/docs/media/offline-34.png b/docs/media/offline-34.png new file mode 100644 index 0000000000..eed6d76a7d Binary files /dev/null and b/docs/media/offline-34.png differ diff --git a/docs/media/offline-35.png b/docs/media/offline-35.png new file mode 100644 index 0000000000..36a3a9affe Binary files /dev/null and b/docs/media/offline-35.png differ diff --git a/docs/media/offline-36.png b/docs/media/offline-36.png new file mode 100644 index 0000000000..1274059012 Binary files /dev/null and b/docs/media/offline-36.png differ diff --git a/docs/media/offline-4.png b/docs/media/offline-4.png new file mode 100644 index 0000000000..d5e7218008 Binary files /dev/null and b/docs/media/offline-4.png differ diff --git a/docs/media/offline-5.png b/docs/media/offline-5.png new file mode 100644 index 0000000000..5641cb4e4b Binary files /dev/null and b/docs/media/offline-5.png differ diff --git a/docs/media/offline-6.png b/docs/media/offline-6.png new file mode 100644 index 0000000000..31531be097 Binary files /dev/null and b/docs/media/offline-6.png differ diff --git a/docs/media/offline-7.png b/docs/media/offline-7.png new file mode 100644 index 0000000000..7d563a46ea Binary files /dev/null and b/docs/media/offline-7.png differ diff --git a/docs/media/offline-8.png b/docs/media/offline-8.png new file mode 100644 index 0000000000..0aeeeea53b Binary files /dev/null and b/docs/media/offline-8.png differ diff --git a/docs/media/offline-9.png b/docs/media/offline-9.png new file mode 100644 index 0000000000..3f23afe3a8 Binary files /dev/null and b/docs/media/offline-9.png differ diff --git a/docs/media/overdue_checkin.png b/docs/media/overdue_checkin.png new file mode 100644 index 0000000000..3adf27d2d2 Binary files /dev/null and b/docs/media/overdue_checkin.png differ diff --git a/docs/media/passwordresetmessage.png b/docs/media/passwordresetmessage.png new file mode 100644 index 0000000000..29a9cc6f6a Binary files /dev/null and b/docs/media/passwordresetmessage.png differ diff --git a/docs/media/patron-1.png b/docs/media/patron-1.png new file mode 100644 index 0000000000..94f12126f8 Binary files /dev/null and b/docs/media/patron-1.png differ diff --git a/docs/media/patron-10.png b/docs/media/patron-10.png new file mode 100644 index 0000000000..0814ad9973 Binary files /dev/null and b/docs/media/patron-10.png differ diff --git a/docs/media/patron-11.png b/docs/media/patron-11.png new file mode 100644 index 0000000000..e2e72955c3 Binary files /dev/null and b/docs/media/patron-11.png differ diff --git a/docs/media/patron-12.png b/docs/media/patron-12.png new file mode 100644 index 0000000000..4dfb246ae2 Binary files /dev/null and b/docs/media/patron-12.png differ diff --git a/docs/media/patron-13.png b/docs/media/patron-13.png new file mode 100644 index 0000000000..5dc9cb1ba2 Binary files /dev/null and b/docs/media/patron-13.png differ diff --git a/docs/media/patron-14.png b/docs/media/patron-14.png new file mode 100644 index 0000000000..956d397751 Binary files /dev/null and b/docs/media/patron-14.png differ diff --git a/docs/media/patron-15.png b/docs/media/patron-15.png new file mode 100644 index 0000000000..8d7c4c713d Binary files /dev/null and b/docs/media/patron-15.png differ diff --git a/docs/media/patron-16.png b/docs/media/patron-16.png new file mode 100644 index 0000000000..283c6d7a05 Binary files /dev/null and b/docs/media/patron-16.png differ diff --git a/docs/media/patron-17.png b/docs/media/patron-17.png new file mode 100644 index 0000000000..f3563fad63 Binary files /dev/null and b/docs/media/patron-17.png differ diff --git a/docs/media/patron-18.png b/docs/media/patron-18.png new file mode 100644 index 0000000000..ee4ae07994 Binary files /dev/null and b/docs/media/patron-18.png differ diff --git a/docs/media/patron-19.png b/docs/media/patron-19.png new file mode 100644 index 0000000000..f69846b0f7 Binary files /dev/null and b/docs/media/patron-19.png differ diff --git a/docs/media/patron-2.png b/docs/media/patron-2.png new file mode 100644 index 0000000000..dddd820e8b Binary files /dev/null and b/docs/media/patron-2.png differ diff --git a/docs/media/patron-20.png b/docs/media/patron-20.png new file mode 100644 index 0000000000..24c4b6d8f8 Binary files /dev/null and b/docs/media/patron-20.png differ diff --git a/docs/media/patron-21.png b/docs/media/patron-21.png new file mode 100644 index 0000000000..1f5a65586f Binary files /dev/null and b/docs/media/patron-21.png differ diff --git a/docs/media/patron-22.png b/docs/media/patron-22.png new file mode 100644 index 0000000000..c2d01d8e65 Binary files /dev/null and b/docs/media/patron-22.png differ diff --git a/docs/media/patron-23.png b/docs/media/patron-23.png new file mode 100644 index 0000000000..b4f19a2fca Binary files /dev/null and b/docs/media/patron-23.png differ diff --git a/docs/media/patron-24.png b/docs/media/patron-24.png new file mode 100644 index 0000000000..7b8d7dd558 Binary files /dev/null and b/docs/media/patron-24.png differ diff --git a/docs/media/patron-25.png b/docs/media/patron-25.png new file mode 100644 index 0000000000..780716741d Binary files /dev/null and b/docs/media/patron-25.png differ diff --git a/docs/media/patron-26.png b/docs/media/patron-26.png new file mode 100644 index 0000000000..79b65e341a Binary files /dev/null and b/docs/media/patron-26.png differ diff --git a/docs/media/patron-27.png b/docs/media/patron-27.png new file mode 100644 index 0000000000..b73c9da7bb Binary files /dev/null and b/docs/media/patron-27.png differ diff --git a/docs/media/patron-28.png b/docs/media/patron-28.png new file mode 100644 index 0000000000..421855d3ee Binary files /dev/null and b/docs/media/patron-28.png differ diff --git a/docs/media/patron-29.png b/docs/media/patron-29.png new file mode 100644 index 0000000000..7b70133e9a Binary files /dev/null and b/docs/media/patron-29.png differ diff --git a/docs/media/patron-3.png b/docs/media/patron-3.png new file mode 100644 index 0000000000..24885105ae Binary files /dev/null and b/docs/media/patron-3.png differ diff --git a/docs/media/patron-30.png b/docs/media/patron-30.png new file mode 100644 index 0000000000..055b34308b Binary files /dev/null and b/docs/media/patron-30.png differ diff --git a/docs/media/patron-31.png b/docs/media/patron-31.png new file mode 100644 index 0000000000..5c3f52ed6f Binary files /dev/null and b/docs/media/patron-31.png differ diff --git a/docs/media/patron-32.png b/docs/media/patron-32.png new file mode 100644 index 0000000000..c5bcf386ca Binary files /dev/null and b/docs/media/patron-32.png differ diff --git a/docs/media/patron-3a.png b/docs/media/patron-3a.png new file mode 100644 index 0000000000..24a3c3ea52 Binary files /dev/null and b/docs/media/patron-3a.png differ diff --git a/docs/media/patron-4.png b/docs/media/patron-4.png new file mode 100644 index 0000000000..58a4992986 Binary files /dev/null and b/docs/media/patron-4.png differ diff --git a/docs/media/patron-5.png b/docs/media/patron-5.png new file mode 100644 index 0000000000..9276de00c7 Binary files /dev/null and b/docs/media/patron-5.png differ diff --git a/docs/media/patron-6.png b/docs/media/patron-6.png new file mode 100644 index 0000000000..45f459d1aa Binary files /dev/null and b/docs/media/patron-6.png differ diff --git a/docs/media/patron-7.png b/docs/media/patron-7.png new file mode 100644 index 0000000000..130ba73c72 Binary files /dev/null and b/docs/media/patron-7.png differ diff --git a/docs/media/patron-8.png b/docs/media/patron-8.png new file mode 100644 index 0000000000..c903823877 Binary files /dev/null and b/docs/media/patron-8.png differ diff --git a/docs/media/patron-9.png b/docs/media/patron-9.png new file mode 100644 index 0000000000..0370982749 Binary files /dev/null and b/docs/media/patron-9.png differ diff --git a/docs/media/patron-record-status-1.png b/docs/media/patron-record-status-1.png new file mode 100644 index 0000000000..a631541e14 Binary files /dev/null and b/docs/media/patron-record-status-1.png differ diff --git a/docs/media/patron-record-status-dark-grey.png b/docs/media/patron-record-status-dark-grey.png new file mode 100644 index 0000000000..3896fdd97b Binary files /dev/null and b/docs/media/patron-record-status-dark-grey.png differ diff --git a/docs/media/patron-record-status-green.png b/docs/media/patron-record-status-green.png new file mode 100644 index 0000000000..f50907b0b3 Binary files /dev/null and b/docs/media/patron-record-status-green.png differ diff --git a/docs/media/patron-record-status-light-grey.png b/docs/media/patron-record-status-light-grey.png new file mode 100644 index 0000000000..4c325302df Binary files /dev/null and b/docs/media/patron-record-status-light-grey.png differ diff --git a/docs/media/patron-record-status-orange.png b/docs/media/patron-record-status-orange.png new file mode 100644 index 0000000000..fdc56e13dd Binary files /dev/null and b/docs/media/patron-record-status-orange.png differ diff --git a/docs/media/patron-record-status-purple.png b/docs/media/patron-record-status-purple.png new file mode 100644 index 0000000000..6a204d6d15 Binary files /dev/null and b/docs/media/patron-record-status-purple.png differ diff --git a/docs/media/patron-record-status-red.png b/docs/media/patron-record-status-red.png new file mode 100644 index 0000000000..00d82ce50c Binary files /dev/null and b/docs/media/patron-record-status-red.png differ diff --git a/docs/media/patron-record-status-yellow.png b/docs/media/patron-record-status-yellow.png new file mode 100644 index 0000000000..c2ba407146 Binary files /dev/null and b/docs/media/patron-record-status-yellow.png differ diff --git a/docs/media/patron_summary_checkouts.jpg b/docs/media/patron_summary_checkouts.jpg new file mode 100644 index 0000000000..7b7c15e4f7 Binary files /dev/null and b/docs/media/patron_summary_checkouts.jpg differ diff --git a/docs/media/pdf_icon.gif b/docs/media/pdf_icon.gif new file mode 100644 index 0000000000..ca1ccfe4d9 Binary files /dev/null and b/docs/media/pdf_icon.gif differ diff --git a/docs/media/pre_cat_alert.png b/docs/media/pre_cat_alert.png new file mode 100644 index 0000000000..e48257229e Binary files /dev/null and b/docs/media/pre_cat_alert.png differ diff --git a/docs/media/precat.png b/docs/media/precat.png new file mode 100644 index 0000000000..9681b8e9d1 Binary files /dev/null and b/docs/media/precat.png differ diff --git a/docs/media/profile-5.png b/docs/media/profile-5.png new file mode 100644 index 0000000000..bdafbca927 Binary files /dev/null and b/docs/media/profile-5.png differ diff --git a/docs/media/profile-6.png b/docs/media/profile-6.png new file mode 100644 index 0000000000..5e3b429aee Binary files /dev/null and b/docs/media/profile-6.png differ diff --git a/docs/media/profile-7.png b/docs/media/profile-7.png new file mode 100644 index 0000000000..26fec660f1 Binary files /dev/null and b/docs/media/profile-7.png differ diff --git a/docs/media/receipt-10.jpg b/docs/media/receipt-10.jpg new file mode 100644 index 0000000000..2788ce317c Binary files /dev/null and b/docs/media/receipt-10.jpg differ diff --git a/docs/media/receipt-11.jpg b/docs/media/receipt-11.jpg new file mode 100644 index 0000000000..e259e0fb3d Binary files /dev/null and b/docs/media/receipt-11.jpg differ diff --git a/docs/media/receipt-12.jpg b/docs/media/receipt-12.jpg new file mode 100644 index 0000000000..d170ec81c3 Binary files /dev/null and b/docs/media/receipt-12.jpg differ diff --git a/docs/media/receipt-13.jpg b/docs/media/receipt-13.jpg new file mode 100644 index 0000000000..be2c6f3d15 Binary files /dev/null and b/docs/media/receipt-13.jpg differ diff --git a/docs/media/receipt-14.jpg b/docs/media/receipt-14.jpg new file mode 100644 index 0000000000..2037725267 Binary files /dev/null and b/docs/media/receipt-14.jpg differ diff --git a/docs/media/receipt-15.jpg b/docs/media/receipt-15.jpg new file mode 100644 index 0000000000..29190dcd84 Binary files /dev/null and b/docs/media/receipt-15.jpg differ diff --git a/docs/media/receipt-16.png b/docs/media/receipt-16.png new file mode 100644 index 0000000000..4407ef85cd Binary files /dev/null and b/docs/media/receipt-16.png differ diff --git a/docs/media/receipt-17.jpg b/docs/media/receipt-17.jpg new file mode 100644 index 0000000000..19a7d76aa8 Binary files /dev/null and b/docs/media/receipt-17.jpg differ diff --git a/docs/media/receipt-18.jpg b/docs/media/receipt-18.jpg new file mode 100644 index 0000000000..017d045fd5 Binary files /dev/null and b/docs/media/receipt-18.jpg differ diff --git a/docs/media/receipt-19.jpg b/docs/media/receipt-19.jpg new file mode 100644 index 0000000000..ce84686e0b Binary files /dev/null and b/docs/media/receipt-19.jpg differ diff --git a/docs/media/receipt-2.jpg b/docs/media/receipt-2.jpg new file mode 100644 index 0000000000..7d0d6f4526 Binary files /dev/null and b/docs/media/receipt-2.jpg differ diff --git a/docs/media/receipt-20.jpg b/docs/media/receipt-20.jpg new file mode 100644 index 0000000000..d83bfcddeb Binary files /dev/null and b/docs/media/receipt-20.jpg differ diff --git a/docs/media/receipt-21.jpg b/docs/media/receipt-21.jpg new file mode 100644 index 0000000000..80c7d4b49d Binary files /dev/null and b/docs/media/receipt-21.jpg differ diff --git a/docs/media/receipt-22.jpg b/docs/media/receipt-22.jpg new file mode 100644 index 0000000000..0c393679e9 Binary files /dev/null and b/docs/media/receipt-22.jpg differ diff --git a/docs/media/receipt-23.jpg b/docs/media/receipt-23.jpg new file mode 100644 index 0000000000..2fca67ec78 Binary files /dev/null and b/docs/media/receipt-23.jpg differ diff --git a/docs/media/receipt-24.jpg b/docs/media/receipt-24.jpg new file mode 100644 index 0000000000..abaf8336ea Binary files /dev/null and b/docs/media/receipt-24.jpg differ diff --git a/docs/media/receipt-3.jpg b/docs/media/receipt-3.jpg new file mode 100644 index 0000000000..f36cc405f4 Binary files /dev/null and b/docs/media/receipt-3.jpg differ diff --git a/docs/media/receipt-4.jpg b/docs/media/receipt-4.jpg new file mode 100644 index 0000000000..a69a63ebb6 Binary files /dev/null and b/docs/media/receipt-4.jpg differ diff --git a/docs/media/receipt-5.jpg b/docs/media/receipt-5.jpg new file mode 100644 index 0000000000..d73c31c5be Binary files /dev/null and b/docs/media/receipt-5.jpg differ diff --git a/docs/media/receipt-6.jpg b/docs/media/receipt-6.jpg new file mode 100644 index 0000000000..170e0205fb Binary files /dev/null and b/docs/media/receipt-6.jpg differ diff --git a/docs/media/receipt-7.jpg b/docs/media/receipt-7.jpg new file mode 100644 index 0000000000..ec59453788 Binary files /dev/null and b/docs/media/receipt-7.jpg differ diff --git a/docs/media/receipt-8.jpg b/docs/media/receipt-8.jpg new file mode 100644 index 0000000000..9c10d3331f Binary files /dev/null and b/docs/media/receipt-8.jpg differ diff --git a/docs/media/receipt-9.jpg b/docs/media/receipt-9.jpg new file mode 100644 index 0000000000..5564e9351f Binary files /dev/null and b/docs/media/receipt-9.jpg differ diff --git a/docs/media/record_in_house_action.png b/docs/media/record_in_house_action.png new file mode 100644 index 0000000000..71cfa62fb5 Binary files /dev/null and b/docs/media/record_in_house_action.png differ diff --git a/docs/media/renew_action.png b/docs/media/renew_action.png new file mode 100644 index 0000000000..d6642e2fb6 Binary files /dev/null and b/docs/media/renew_action.png differ diff --git a/docs/media/renew_item.png b/docs/media/renew_item.png new file mode 100644 index 0000000000..75a79446e5 Binary files /dev/null and b/docs/media/renew_item.png differ diff --git a/docs/media/renew_item_calendar.png b/docs/media/renew_item_calendar.png new file mode 100644 index 0000000000..d30f3dc2f6 Binary files /dev/null and b/docs/media/renew_item_calendar.png differ diff --git a/docs/media/renew_specific_date.png b/docs/media/renew_specific_date.png new file mode 100644 index 0000000000..21c30be152 Binary files /dev/null and b/docs/media/renew_specific_date.png differ diff --git a/docs/media/retrieve_patron.png b/docs/media/retrieve_patron.png new file mode 100644 index 0000000000..e5adee47ea Binary files /dev/null and b/docs/media/retrieve_patron.png differ diff --git a/docs/media/scv-crec.jpg b/docs/media/scv-crec.jpg new file mode 100644 index 0000000000..b4b3360549 Binary files /dev/null and b/docs/media/scv-crec.jpg differ diff --git a/docs/media/scv-distr.jpg b/docs/media/scv-distr.jpg new file mode 100644 index 0000000000..7ffd8ac46e Binary files /dev/null and b/docs/media/scv-distr.jpg differ diff --git a/docs/media/scv-iss.jpg b/docs/media/scv-iss.jpg new file mode 100644 index 0000000000..e56ea80560 Binary files /dev/null and b/docs/media/scv-iss.jpg differ diff --git a/docs/media/scv-rec.jpg b/docs/media/scv-rec.jpg new file mode 100644 index 0000000000..ee492a351d Binary files /dev/null and b/docs/media/scv-rec.jpg differ diff --git a/docs/media/scv-srec.jpg b/docs/media/scv-srec.jpg new file mode 100644 index 0000000000..7974ad7a6a Binary files /dev/null and b/docs/media/scv-srec.jpg differ diff --git a/docs/media/scv-sub.jpg b/docs/media/scv-sub.jpg new file mode 100644 index 0000000000..5afc9a6475 Binary files /dev/null and b/docs/media/scv-sub.jpg differ diff --git a/docs/media/server-3.png b/docs/media/server-3.png new file mode 100644 index 0000000000..f0cfb45a87 Binary files /dev/null and b/docs/media/server-3.png differ diff --git a/docs/media/server-4.png b/docs/media/server-4.png new file mode 100644 index 0000000000..e092f4798c Binary files /dev/null and b/docs/media/server-4.png differ diff --git a/docs/media/server-5.png b/docs/media/server-5.png new file mode 100644 index 0000000000..2fbea3f3de Binary files /dev/null and b/docs/media/server-5.png differ diff --git a/docs/media/server-6.png b/docs/media/server-6.png new file mode 100644 index 0000000000..05b6ed9f0e Binary files /dev/null and b/docs/media/server-6.png differ diff --git a/docs/media/shared-template-6.png b/docs/media/shared-template-6.png new file mode 100644 index 0000000000..44b75a66f0 Binary files /dev/null and b/docs/media/shared-template-6.png differ diff --git a/docs/media/shared-template-7.png b/docs/media/shared-template-7.png new file mode 100644 index 0000000000..2c52629b36 Binary files /dev/null and b/docs/media/shared-template-7.png differ diff --git a/docs/media/shared-template-9.png b/docs/media/shared-template-9.png new file mode 100644 index 0000000000..1df47250e6 Binary files /dev/null and b/docs/media/shared-template-9.png differ diff --git a/docs/media/small_logo_white.jpg b/docs/media/small_logo_white.jpg new file mode 100644 index 0000000000..e023e0357a Binary files /dev/null and b/docs/media/small_logo_white.jpg differ diff --git a/docs/media/specify_due_date1.png b/docs/media/specify_due_date1.png new file mode 100644 index 0000000000..ab8aa6c1c3 Binary files /dev/null and b/docs/media/specify_due_date1.png differ diff --git a/docs/media/specify_due_date2.png b/docs/media/specify_due_date2.png new file mode 100644 index 0000000000..71df31afc2 Binary files /dev/null and b/docs/media/specify_due_date2.png differ diff --git a/docs/media/staffclient-1.png b/docs/media/staffclient-1.png new file mode 100644 index 0000000000..3199d38741 Binary files /dev/null and b/docs/media/staffclient-1.png differ diff --git a/docs/media/staffclient-2.png b/docs/media/staffclient-2.png new file mode 100644 index 0000000000..98d168e36f Binary files /dev/null and b/docs/media/staffclient-2.png differ diff --git a/docs/media/staffclient-3.png b/docs/media/staffclient-3.png new file mode 100644 index 0000000000..f2d695d86a Binary files /dev/null and b/docs/media/staffclient-3.png differ diff --git a/docs/media/staffclient-4.png b/docs/media/staffclient-4.png new file mode 100644 index 0000000000..108afa901a Binary files /dev/null and b/docs/media/staffclient-4.png differ diff --git a/docs/media/staffclient-5.png b/docs/media/staffclient-5.png new file mode 100644 index 0000000000..9451695b11 Binary files /dev/null and b/docs/media/staffclient-5.png differ diff --git a/docs/media/staffclient-6.png b/docs/media/staffclient-6.png new file mode 100644 index 0000000000..8348e63ba7 Binary files /dev/null and b/docs/media/staffclient-6.png differ diff --git a/docs/media/staffclient-6a.png b/docs/media/staffclient-6a.png new file mode 100644 index 0000000000..02f6cef008 Binary files /dev/null and b/docs/media/staffclient-6a.png differ diff --git a/docs/media/staffclient-6b.png b/docs/media/staffclient-6b.png new file mode 100644 index 0000000000..f9ce6834a8 Binary files /dev/null and b/docs/media/staffclient-6b.png differ diff --git a/docs/media/staffclient-6c.png b/docs/media/staffclient-6c.png new file mode 100644 index 0000000000..3908102fba Binary files /dev/null and b/docs/media/staffclient-6c.png differ diff --git a/docs/media/staffclient-6d.png b/docs/media/staffclient-6d.png new file mode 100644 index 0000000000..f4c793e86d Binary files /dev/null and b/docs/media/staffclient-6d.png differ diff --git a/docs/media/staffclient-7.png b/docs/media/staffclient-7.png new file mode 100644 index 0000000000..4492a80036 Binary files /dev/null and b/docs/media/staffclient-7.png differ diff --git a/docs/media/staffclient-7a.png b/docs/media/staffclient-7a.png new file mode 100644 index 0000000000..ddc7e97266 Binary files /dev/null and b/docs/media/staffclient-7a.png differ diff --git a/docs/media/staffclient-8.png b/docs/media/staffclient-8.png new file mode 100644 index 0000000000..91154f0985 Binary files /dev/null and b/docs/media/staffclient-8.png differ diff --git a/docs/media/staffclient-9.png b/docs/media/staffclient-9.png new file mode 100644 index 0000000000..ecec7d8199 Binary files /dev/null and b/docs/media/staffclient-9.png differ diff --git a/docs/media/staffclientinstallation-proxy-putty-1.png b/docs/media/staffclientinstallation-proxy-putty-1.png new file mode 100644 index 0000000000..1558fb665c Binary files /dev/null and b/docs/media/staffclientinstallation-proxy-putty-1.png differ diff --git a/docs/media/staffclientinstallation-proxy-socks-1.png b/docs/media/staffclientinstallation-proxy-socks-1.png new file mode 100644 index 0000000000..b43192b910 Binary files /dev/null and b/docs/media/staffclientinstallation-proxy-socks-1.png differ diff --git a/docs/media/staffclientinstallation-proxy-socks-2.png b/docs/media/staffclientinstallation-proxy-socks-2.png new file mode 100644 index 0000000000..5f9088dbca Binary files /dev/null and b/docs/media/staffclientinstallation-proxy-socks-2.png differ diff --git a/docs/media/staffclientinstallation-staffclient-1.png b/docs/media/staffclientinstallation-staffclient-1.png new file mode 100644 index 0000000000..1c19db00f0 Binary files /dev/null and b/docs/media/staffclientinstallation-staffclient-1.png differ diff --git a/docs/media/staffclientinstallation-staffclient-2.png b/docs/media/staffclientinstallation-staffclient-2.png new file mode 100644 index 0000000000..a75f0565e0 Binary files /dev/null and b/docs/media/staffclientinstallation-staffclient-2.png differ diff --git a/docs/media/staffclientinstallation-staffclient-3.png b/docs/media/staffclientinstallation-staffclient-3.png new file mode 100644 index 0000000000..4627d077c0 Binary files /dev/null and b/docs/media/staffclientinstallation-staffclient-3.png differ diff --git a/docs/media/staffclientinstallation-staffclient-4.png b/docs/media/staffclientinstallation-staffclient-4.png new file mode 100644 index 0000000000..4627d077c0 Binary files /dev/null and b/docs/media/staffclientinstallation-staffclient-4.png differ diff --git a/docs/media/staffclientinstallation-staffclient-workstationnames-1.png b/docs/media/staffclientinstallation-staffclient-workstationnames-1.png new file mode 100644 index 0000000000..b219531428 Binary files /dev/null and b/docs/media/staffclientinstallation-staffclient-workstationnames-1.png differ diff --git a/docs/media/staffclientinstallation-staffclient-workstationnames-2.png b/docs/media/staffclientinstallation-staffclient-workstationnames-2.png new file mode 100644 index 0000000000..6c70b438ef Binary files /dev/null and b/docs/media/staffclientinstallation-staffclient-workstationnames-2.png differ diff --git a/docs/media/staffclientinstallation-staffclient-workstationnames-3.png b/docs/media/staffclientinstallation-staffclient-workstationnames-3.png new file mode 100644 index 0000000000..7af39674bc Binary files /dev/null and b/docs/media/staffclientinstallation-staffclient-workstationnames-3.png differ diff --git a/docs/media/staffclientinstallation-tabbed-1.png b/docs/media/staffclientinstallation-tabbed-1.png new file mode 100644 index 0000000000..d5ae3bebf7 Binary files /dev/null and b/docs/media/staffclientinstallation-tabbed-1.png differ diff --git a/docs/media/survey-1.png b/docs/media/survey-1.png new file mode 100644 index 0000000000..536f926763 Binary files /dev/null and b/docs/media/survey-1.png differ diff --git a/docs/media/survey-10.png b/docs/media/survey-10.png new file mode 100644 index 0000000000..80d5b85686 Binary files /dev/null and b/docs/media/survey-10.png differ diff --git a/docs/media/survey-2.png b/docs/media/survey-2.png new file mode 100644 index 0000000000..ba6a10fa93 Binary files /dev/null and b/docs/media/survey-2.png differ diff --git a/docs/media/survey-3.png b/docs/media/survey-3.png new file mode 100644 index 0000000000..6f0afd0a73 Binary files /dev/null and b/docs/media/survey-3.png differ diff --git a/docs/media/survey-4.png b/docs/media/survey-4.png new file mode 100644 index 0000000000..0ffc78187c Binary files /dev/null and b/docs/media/survey-4.png differ diff --git a/docs/media/survey-5.png b/docs/media/survey-5.png new file mode 100644 index 0000000000..afafdcb54a Binary files /dev/null and b/docs/media/survey-5.png differ diff --git a/docs/media/survey-6.png b/docs/media/survey-6.png new file mode 100644 index 0000000000..688d1f61f4 Binary files /dev/null and b/docs/media/survey-6.png differ diff --git a/docs/media/survey-7.png b/docs/media/survey-7.png new file mode 100644 index 0000000000..06b84fd979 Binary files /dev/null and b/docs/media/survey-7.png differ diff --git a/docs/media/survey-8.png b/docs/media/survey-8.png new file mode 100644 index 0000000000..3a37afdf53 Binary files /dev/null and b/docs/media/survey-8.png differ diff --git a/docs/media/survey-9.png b/docs/media/survey-9.png new file mode 100644 index 0000000000..896e527c94 Binary files /dev/null and b/docs/media/survey-9.png differ diff --git a/docs/media/tip.png b/docs/media/tip.png new file mode 100644 index 0000000000..eaabe82ea6 Binary files /dev/null and b/docs/media/tip.png differ diff --git a/docs/media/transit-1.png b/docs/media/transit-1.png new file mode 100644 index 0000000000..92733a0c6f Binary files /dev/null and b/docs/media/transit-1.png differ diff --git a/docs/media/transit-10.png b/docs/media/transit-10.png new file mode 100644 index 0000000000..f1c6215621 Binary files /dev/null and b/docs/media/transit-10.png differ diff --git a/docs/media/transit-2.png b/docs/media/transit-2.png new file mode 100644 index 0000000000..30681af74f Binary files /dev/null and b/docs/media/transit-2.png differ diff --git a/docs/media/transit-3.png b/docs/media/transit-3.png new file mode 100644 index 0000000000..34480f066f Binary files /dev/null and b/docs/media/transit-3.png differ diff --git a/docs/media/transit-4a.png b/docs/media/transit-4a.png new file mode 100644 index 0000000000..143bf789fc Binary files /dev/null and b/docs/media/transit-4a.png differ diff --git a/docs/media/transit-5.png b/docs/media/transit-5.png new file mode 100644 index 0000000000..ae889e24f0 Binary files /dev/null and b/docs/media/transit-5.png differ diff --git a/docs/media/transit-6.png b/docs/media/transit-6.png new file mode 100644 index 0000000000..c9ce4b118f Binary files /dev/null and b/docs/media/transit-6.png differ diff --git a/docs/media/transit-7.png b/docs/media/transit-7.png new file mode 100644 index 0000000000..8464c674ea Binary files /dev/null and b/docs/media/transit-7.png differ diff --git a/docs/media/transit-8.png b/docs/media/transit-8.png new file mode 100644 index 0000000000..ce33b5d472 Binary files /dev/null and b/docs/media/transit-8.png differ diff --git a/docs/media/transit-9.png b/docs/media/transit-9.png new file mode 100644 index 0000000000..8c84c420a3 Binary files /dev/null and b/docs/media/transit-9.png differ diff --git a/docs/media/unified_volume_copy_creator1.jpg b/docs/media/unified_volume_copy_creator1.jpg new file mode 100644 index 0000000000..a8b78d0ce4 Binary files /dev/null and b/docs/media/unified_volume_copy_creator1.jpg differ diff --git a/docs/media/unified_volume_copy_creator2.jpg b/docs/media/unified_volume_copy_creator2.jpg new file mode 100644 index 0000000000..02d6df9dd8 Binary files /dev/null and b/docs/media/unified_volume_copy_creator2.jpg differ diff --git a/docs/media/unified_volume_copy_creator3.jpg b/docs/media/unified_volume_copy_creator3.jpg new file mode 100644 index 0000000000..6a1222e586 Binary files /dev/null and b/docs/media/unified_volume_copy_creator3.jpg differ diff --git a/docs/media/unified_volume_copy_creator4.jpg b/docs/media/unified_volume_copy_creator4.jpg new file mode 100644 index 0000000000..2033608ce3 Binary files /dev/null and b/docs/media/unified_volume_copy_creator4.jpg differ diff --git a/docs/media/unified_volume_copy_creator5.jpg b/docs/media/unified_volume_copy_creator5.jpg new file mode 100644 index 0000000000..0813279181 Binary files /dev/null and b/docs/media/unified_volume_copy_creator5.jpg differ diff --git a/docs/media/unified_volume_copy_creator6.jpg b/docs/media/unified_volume_copy_creator6.jpg new file mode 100644 index 0000000000..0cdbca56c4 Binary files /dev/null and b/docs/media/unified_volume_copy_creator6.jpg differ diff --git a/docs/media/view-output-1.png b/docs/media/view-output-1.png new file mode 100644 index 0000000000..7fa0aec3a2 Binary files /dev/null and b/docs/media/view-output-1.png differ diff --git a/docs/media/view-output-2.png b/docs/media/view-output-2.png new file mode 100644 index 0000000000..b536d07234 Binary files /dev/null and b/docs/media/view-output-2.png differ diff --git a/docs/media/view-output-3.png b/docs/media/view-output-3.png new file mode 100644 index 0000000000..12756c5376 Binary files /dev/null and b/docs/media/view-output-3.png differ diff --git a/docs/media/view-output-4.png b/docs/media/view-output-4.png new file mode 100644 index 0000000000..54e364c3c9 Binary files /dev/null and b/docs/media/view-output-4.png differ diff --git a/docs/media/view-output-5.png b/docs/media/view-output-5.png new file mode 100644 index 0000000000..c4d9f61308 Binary files /dev/null and b/docs/media/view-output-5.png differ diff --git a/docs/media/warning.png b/docs/media/warning.png new file mode 100644 index 0000000000..cdc6568091 Binary files /dev/null and b/docs/media/warning.png differ diff --git a/docs/opac/my_lists.txt b/docs/opac/my_lists.txt new file mode 100644 index 0000000000..c6b848e868 --- /dev/null +++ b/docs/opac/my_lists.txt @@ -0,0 +1,63 @@ +My Lists 2.2 +------------ + +The *My Lists* feature replaces the bookbag feature that was available in versions proior to 2.2. The *My Lists* feature is a part of the Template Toolkit OPAC that is available in version 2.2. This feature enables you to create temporary and permanent lists; create and edit notes for items in lists; place holds on items in lists; and share lists via RSS feeds and CSV files. + + +*Create New Lists* + +1) Log in to your account in the OPAC. + +2) Search for titles. + +3) Choose a title to add to your list. Click *Add to My List*. + +image::media/My_Lists1.jpg[My_Lists1] + +4) Scroll up to the gray row on top of the *Search Results*. Click *View My List* + +5) Items are added to a temporary list. Your temporary list appears at the bottom of the screen. + +6) The *Actions for these items* menu on the right side of the screen demonstrates the actions that you can apply to this list. You can place holds on items in your temporary list; remove items from the list; or move selected items to a permanent list. + +To place a hold or remove items from the list, check the box adjacent to the title of the item, and select the desired function. + +To move selected items into an existing list, check the box adjacent to the title, and highlight the list in which you will store the item. + +image::media/My_Lists3.jpg[My_Lists3] + +7) If you do not want to place the item into an existing list, you can create a new list to contain the item. Enter the name of the new list, and, if desired, enter a description. + +image::media/My_Lists4.jpg[My_Lists4] + +8) Click *Submit*. + +9) The new list appears beneath the temporary list. + +10) Select the title(s) of the items that you want to add to the list, and click *Actions for these items*. Select the permanent list that you created from the drop down menu. + +image::media/My_Lists5.jpg[My_Lists5] + +11) Click *Go*. + +12) Your existing lists appear. Click on a list to view the items in the list. You can sort the items in the permanent list. You can also add, edit, and remove notes. + +13) Click *Edit* to add or edit a note. + +14). Enter desired notes, and click *Save Notes*. + +image::media/My_Lists6.jpg[My_Lists6] + +15) You can keep your list private, or you can share it. To share your list, click *Share*, and click the orange RSS icon to share through an RSS reader. You can also click *HTML View* to share your list as an HTML link. + +You can also download your list into a CSV file by clicking *Download CSV*. + +image::media/My_Lists7.jpg[My_Lists7] + + +16) When you no longer need a list, click *Delete List*. + + + + + diff --git a/docs/reports/README b/docs/reports/README new file mode 100644 index 0000000000..e69de29bb2 diff --git a/docs/root.txt b/docs/root.txt new file mode 100644 index 0000000000..5c03084abc --- /dev/null +++ b/docs/root.txt @@ -0,0 +1,320 @@ +Evergreen Documentation +======================= +Documentation Interest Group +:doctype: book +:toc: +:numbered: + +Introduction +============ + +About This Documentation +------------------------ + +This guide was produced by the Evergreen Documentation Interest Group (DIG), +consisting of numerous volunteers from many different organizations. The DIG +has drawn together, edited, and supplemented pre-existing documentation +contributed by libraries and consortia running Evergreen that were kind enough +to release their documentation into the creative commons. Please see the +<> section for a full list of authors and +contributing organizations. Just like the software it describes, this guide is +a work in progress, continually revised to meet the needs of its users, so if +you find errors or omissions, please let us know, by contacting the DIG +facilitators at docs@evergreen-ils.org. + +This guide to Evergreen is intended to meet the needs of front-line library +staff, catalogers, library administrators, system administrators, and software +developers. It is organized into Parts, Chapters, and Sections addressing key +aspects of the software, beginning with the topics of broadest interest to the +largest groups of users and progressing to some of the more specialized and +technical topics of interest to smaller numbers of users. + +Copies of this guide can be accessed in PDF and HTML formats from http://docs.evergreen-ils.org/. + +About Evergreen +--------------- + +Evergreen is an open source library automation software designed to meet the +needs of the very smallest to the very largest libraries and consortia. Through +its staff interface, it facilitates the management, cataloging, and circulation +of library materials, and through its online public access interface it helps +patrons find those materials. + +The Evergreen software is freely licensed under the GNU General Public License, +meaning that it is free to download, use, view, modify, and share. It has an +active development and user community, as well as several companies offering +migration, support, hosting, and development services. + +The community’s development requirements state that Evergreen must be: + +* Stable, even under extreme load. +* Robust, and capable of handling a high volume of transactions and simultaneous users. +* Flexible, to accommodate the varied needs of libraries. +* Secure, to protect our patrons’ privacy and data. +* User-friendly, to facilitate patron and staff use of the system. + +Evergreen, which first launched in 2006 now powers over 544 libraries of every +type – public, academic, special, school, and even tribal and home libraries – +in over a dozen countries worldwide. + +// Push titles down one level. +:leveloffset: 1 + +include::RELEASE_NOTES_2_2.txt[] + +// Return to normal title levels. +:leveloffset: 0 + +Software Installation +===================== + + +Introduction +------------ + +This part will guide you through the installation steps installation or +upgrading your Evergreen system. It is intended for system administrators. + + +include::installation/system_requirements.txt[] + +// Push titles down one level. +:leveloffset: 1 + +include::installation/server_installation.txt[] + +// Return to normal title levels. +:leveloffset: 0 + +include::installation/server_upgrade.txt[] + +include::installation/edi_setup.txt[] + +// include::staff_client_installation.txt[] +// include::org_unit_structure_initialization.txt[] +// include::loading_data.txt[] + + +System Configuration and Customization +====================================== + +Introduction +------------ + +The Evergreen system allows a free range of customizations to every aspect of +the system. Use this part of the documentation to become familiar with the tools +for configuring the system as well as customizing the OPAC and staff client. + +// include::global_system_configuration.txt[] +// include::opac_customization.txt[] + +include::admin/template_toolkit.txt[] + +include::admin/auto_suggest_search.txt[] + +include::admin/customize_staff_client.txt[] + +// include::backing_up.txt[] + + + +Using the Staff Client +====================== + + +Introduction +------------ + +This part of the documentation deals with general Staff Client usage including +logging in, navigation and shortcuts. + + +include::admin/staff_client-tab_buttons.txt[] + +include::admin/staff_client-double_clicking.txt[] + +include::admin/staff_client-sorting_columns.txt[] + +include::admin/staff_client-recent_searches.txt[] + +include::admin/staff_client-return_to_results_from_marc.txt[] + +System Administration From the Staff Client +=========================================== + +Introduction +------------ + +This part deals with the options in the Server Administration menu found in the +staff client. + +// Follow structure from staff client system admin menu. + +include::admin/acquisitions_admin.txt[] + +include::admin/authorities.txt[] + +include::admin/cn_prefixes_and_suffixes.txt[] + +include::admin/restrict_Z39.50_sources_by_perm_group.txt[] + +include::admin/booking-admin.txt[] + +include::admin/SMS_messaging.txt[] + +include::admin/user_activity_type.txt[] + + +Local Administration +==================== + +Introduction +------------ + +This part covers the options in the Local Administration menu found in the staff +client. + +// Follow structure from staff client local admin menu. + +// Push titles down one level. +:leveloffset: 1 + +include::admin/hold_driven_recalls.txt[] + +// Return to normal title levels. +:leveloffset: 0 + +include::admin/recent_staff_searches.txt[] + +include::admin/lsa-library_settings_editor.txt[] + +include::admin/lsa-statcat.txt[] + + +Acquisitions +=========== + +include::acquisitions/introduction.txt[] + +include::acquisitions/selection_lists_po.txt[] + +include::acquisitions/receive_items_from_invoice.txt[] + +include::acquisitions/vandelay_acquisitions_integration.txt[] + + +Cataloging +========== + +Introduction +------------ + +Cataloguers should use this part for understanding the cataloguing procedures +used in Evergreen. + +include::cataloging/batch_importing_MARC.txt[] + +include::cataloging/overlay_record_3950_import.txt[] + +include::cataloging/monograph_parts.txt[] + +include::cataloging/conjoined_items.txt[] + + +Serials +======= + +include::serials/A-intro.txt[] + +include::serials/B-copy_template.txt[] + +include::serials/C-subscription-SCV.txt[] + +include::serials/D-subscription-ASCV.txt[] + +include::serials/E-edit_subscriptions.txt[] + +include::serials/F-Receiving.txt[] + +include::serials/G-Special_issue.txt[] + +include::serials/H-holdings_statements.txt[] + + +Circulation +=========== + +Introduction +------------ + +Use this section for understanding the circulation procedures in the Evergreen +system. + +include::circulation/circulating_items.txt[] + +include::circulation/booking.txt[] + +Reports +======= + +Introduction +------------ + +Learn how to create and use reports in Evergreen. + +Using the Public Access Catalog +=============================== + +Introduction +------------ + +Use this part for information about searching the Evergreen public access catalog. + +include::opac/my_lists.txt[] + +Developer Resources +=================== + +Introduction +------------ + +Developers can use this part to learn more about the programming languages, +communication protocols and standards used in Evergreen. + +// Push titles down one level. +:leveloffset: 1 + +include::development/updating_translations_launchpad.txt[] + +// Return to normal title levels. +:leveloffset: 0 + +[appendix] + +include::attributions.txt[] + +include::licensing.txt[] + +Admonitions +=========== + +Images used for Admonitions +--------------------------- + +* Note + +image::media/note.png[] + +* warning + +image::media/warning.png[] + +* caution + +image::media/caution.png[] + +* tip + +image::media/tip.png[] + + diff --git a/docs/serials/A-intro.txt b/docs/serials/A-intro.txt new file mode 100644 index 0000000000..b366ac991f --- /dev/null +++ b/docs/serials/A-intro.txt @@ -0,0 +1,30 @@ +Serials +------- + +This documentation is intended for users who will be ordering subscriptions, distributing issues, and receiving issues in Evergreen. + +Serial Control View vs. Alternate Serial Control View +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Serial Control View and Alternate Serial Control View offer you two views of Serials. Both views enable you to create subscriptions, add distributions, define captions, predict future issues, and receive items. Serial Control View was designed for users who work with a smaller number of issues and was designed to accommodate workflows in academic and special libraries. Alternate Serial Control View was designed for users who receive a larger number of issues and was designed for use in public libraries. + +The views are interoperable, but because the views were designed for different purposes, some differences emerge. For example, Serial Control View enables you to create and edit serials in a single tabbed interface while Alternate Serial Control View leads you through a series of steps on multiple screens. In addition, receiving functions vary between views. Both receiving interfaces enable you to batch receive issues. However, the Serials Batch Receive interface, which is associated with Alternate Serial Control View, allows for more customization of each receiving unit while the Items tab in Serial Control View allows for greater flexibility in creating multi-issue units, such as in binding serials. + +.Serials Control View and Alternate Serials Control View Comparison +[options="header"] +|==================================================================================================== +|Function |Serials Control View |Alternate Serials Control View +|Menu Style |Menu driven |Wizard oriented +|Setting Up subscription |No calendar drop downs |Includes calendar drop down +|Setting up distributions |No copy template selection |Requires the selection of a copy template +|Creating streams |No setup required |Requires streams +|Creating captions and patterns |Wizard available |Wizard available +|Adding Starting Issue |No holdings code wizard |Includes holdings code wizard +|Generate Predictions |Make predictions |Generate predictions +|Add items for special issue |No functionality |New items on issuances tab +|==================================================================================================== + +MFHD Records +~~~~~~~~~~~~ + +MARC Format for Holdings Display (MFHD) display in the PAC in addition to holding statements generated by Evergreen from subscriptions created in the Serials Control View or the Alternate Serials Control View. The MFHDs are editable as MARC but the holdings statements generated from the control view are system generated. Multiple MFHDs can be created and are tied to Organizational Units. diff --git a/docs/serials/B-copy_template.txt b/docs/serials/B-copy_template.txt new file mode 100644 index 0000000000..3d0682e601 --- /dev/null +++ b/docs/serials/B-copy_template.txt @@ -0,0 +1,43 @@ +Copy Template for Serials +------------------------- + +A copy template enables you to specify item attributes that should be applied by default to copies of serials. You can create one copy template and apply it to multiple serials. You can also create multiple copy templates. Templates will be used in the Alternate Serial Control View or the Serial Control View. + +Create a copy template +~~~~~~~~~~~~~~~~~~~~~~ + +To create a copy template, click Admin -> Local Administration -> Copy Template Editor. + +. Enter a Name for the template. +. Select an owning library from the Owning lib drop down menu. This organization owns the copy template. A staff member with permissions at that organization can modify the copy template. The menu is populated from the organizations that you created in Admin . Server Administration . Organizational Units. +. Click the box adjacent to Circulate. If you want the item to circulate. +. Check the box adjacent to Holdable. if patrons can place holds on the item. +. Check the box adjacent to OPAC Visible. if you want patrons to be able to see the item in the OPAC after you receive it. +. Select a loan duration rule from the drop down menu. +. Select a fine level for the item from the drop down menu. +. Select a copy Location from the drop down menu. The menu is populated from the copy locations that you created in Admin . Local Administration . Copy Locations. +. Select a circ modifier from the drop down box. The menu is populated from the modifiers that you created in Admin . Server Administration . Circulation Modifiers. +. Check the box adjacent to Floating. if the item is part of a floating collection. +. Check the box adjacent to Deposit. if patrons must place a deposit on the copy before they can use it. +. Check the box adjacent to Reference. if the item is a reference item. +. If the item is in mint condition, then check the box adjacent to Mint Condition. +. Enter age protection rules in the Age Protect field. Age protection allows you to control the extent to which an item can circulate after it has been received. For example, you may want to protect new copies of a serial so that only patrons who check out the item at your branch can use it. +. Enter a message in the Alert Message field. This message will appear every time the item is checked out to a patron. +. Enter a code from the MARC fixed fields if you want to control the circulation based on the item type in the Circ as Type field. +. Enter a deposit amount if patrons must place a deposit on the copy before they can use it. +. Enter the price of the item. +. Enter the ID of the copy status in the Status field. A list of copy statuses and their IDs can be found in Admin . Server Administration . Copy Status. +. Click Save. +. Fine level and loan duration are required fields in the Copy Template Editor. + +Edit a copy template +~~~~~~~~~~~~~~~~~~~~ + +You can make changes to an existing copy template. Changes that you make to a copy template will apply to any items that you receive after you edited the template. + +. To edit a copy template, click your cursor in the row that you want to edit. The row will turn blue. +. Double-click. The copy template will appear, and you can edit the fields. +. After making changes, click Save. + +[NOTE] +From the copy template interface, you can delete copy templates that have never been used. diff --git a/docs/serials/C-subscription-SCV.txt b/docs/serials/C-subscription-SCV.txt new file mode 100644 index 0000000000..4cef1f06de --- /dev/null +++ b/docs/serials/C-subscription-SCV.txt @@ -0,0 +1,152 @@ + +Serials Control View +-------------------- + +Serial Control View is separate from the Alternate Serial Control interface. Serial Control View enables you to manage serials in a single tabbed interface. This view also enables you to bind units. Serial Control View consists of five tabs: Items, Units, Distributions, Subscriptions, and Claims. Units and Claims are not functional in 2.0. + +Create a subscription +~~~~~~~~~~~~~~~~~~~~~ +A subscription is designed to hold all information related to a single serial title. Therefore, each library is likely to have only one subscription per serial title. + +image::media/scv-sub.jpg[Subscription] + +. Click the Subscriptions link. +. Select the branch that will own the subscription. +. Right-click or click Actions for Selected Row, and click Add Subscription. +. Enter the date that the subscription begins in the start date, and click Apply. You must enter the date in YYYY-MM-DD format. +. Enter the date that the subscription ends in the end date. This field is optional. +. Enter the difference between the nominal publishing date of an issue and the date that you expect to receive your copy in the Expected Date Offset. For example, if an issue is published the first day of each month, but you receive the copy two days prior to the publication date, then enter -2 days into this field. +. When finished, click Create Subscription(s) in the bottom right corner of the screen. +. A confirmation message appears. Click OK. + +[NOTE] +You can add notes to the subscription by clicking Subscription Notes. These notes are currently viewable only in the staff client by clicking on the Subscription Notes button. + +Create a distribution +~~~~~~~~~~~~~~~~~~~~~ + +Distributions indicate the branches that should receive copies of a serial. Distributions work together with streams to indicate the number of copies that should be sent to each branch. + +image::media/scv-distr.jpg[Distribution] + +. Click the distributions link beneath the subscription. Right click or click Actions for Selected Rows, and click Add distribution. +. Apply a new label to the distribution. It may be useful to identify the branch to which you are distributing these issues in this field. This field is not publicly visible and only appears when an item is received. There are no limits on the number of characters that can be entered in this field. +. Apply a prefix to the spine label if desired. This information will display in Serial Control View when the items are received, but it does not print on the spine label in . 0. +. Apply a suffix to the spine label if desired. This information will display in Serial Control View when the items are received, but it does not print on the spine label in . 0. +. The holding library is filled in by default and is the library to which you attached the subscription. +. The Legacy Record Entry contains the MFHD records that are attached to the bib record if the owning library is identical to the distribution's holding library. A distribution can thus be an extension of an MFHD record. Select the MFHD record from the drop down menu. +. The Receive Call Number field is empty until you receive the first item. When you receive the first item, you are prompted to enter a call number. That call number will populate this drop down menu. +. The Bind Call Number field is empty until you bind the first item. When you receive the first item, you are prompted to enter a call number. That call number will populate this drop down menu. +. Receive Unit Template - The template that should be applied to copies when they are received. Select a template from the drop down menu. +. Bind Unit Template - The template that should be applied to copies when they are bound. Select a template from the drop down menu. +. When finished, click Create Distribution(s) in the bottom right corner of the screen. +. A confirmation message appears. Click OK. + +[NOTE] +You can add notes to the distribution by clicking Distribution Notes. These notes are currently viewable only in the staff client by clicking on the Distribution Notes button. + +Create Captions and Patterns +~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +. Click the captions and patterns link beneath the subscription. Right click or click Actions for Selected Rows, and click Add Caption/Pattern. +. Apply the type which can be for basic subscription, supplements, or indices +. Apply active. Only one active caption and pattern is allowed per type +. In the Pattern Code dbox, you can enter a JSON representation of the 85X tag by hand, or you can click the Pattern CodeWizard to enter the information in a user-friendly format. + +Use the Pattern Code Wizard +^^^^^^^^^^^^^^^^^^^^^^^^^^^ +The Pattern Code Wizard enables you to create the caption of the item and add its publication information. The Wizard is composed of five pages of questions. You can use the Next and Previous navigation buttons in the top corners to flip between pages. + +To add a pattern code, click Wizard. + +Page 1: Enumerations +++++++++++++++++++++ + +image::media/cap-wiz-num.jpg[Enuperation] + +. To add an enumeration, check the box adjacent to Use enumerations.. The enumerations conform to $a-$h of the 853,854, and 855 MARC tags. +. A field for the First level will appear. Enter the enumeration for the first level. A common first level enumeration is volume, or "v." +. Click Add Enumeration. +. A field for the Second level will appear. Enter the enumeration for the second level. A common first level enumeration is number, or "no." +. Enter the number of bibliographic units per next higher level. This conforms to $u in the 853, 854, and 855 MARC tags. +. Choose the enumeration scheme from the drop down menu. This conforms to $v in the 853, 854, and 855 MARC tags. ++ +[NOTE] +You can add up to six levels of enumeration. ++ +. Add Alternate Enumeration if desired. +. When you have completed the enumerations, click Next. + + +Page 2: Calendar +++++++++++++++++ + +image::media/cap-wiz-cal.jpg[Enumeration] + +. To use months, seasons, or dates in your caption, check the box adjacent to Use calendar changes. +. Identify the point in the year at which the highest level enumeration caption changes. +. In the Type drop down menu, select the points during the year at which you want the calendar to restart. +. In the Point drop down menu, select the specific time at which you would like to change the calendar +. To add another calendar change, click Add Calendar Change. There are no limits on the number of calendar changes that you can add. +. When you have finished the calendar changes, click Next. + +Page 3: Chronology +++++++++++++++++++ + +image::media/cap-wiz-chron.jpg[Chronology] + +. To add chronological units to the captions, check the box adjacent to Use chronology captions. +. Choose a chronology for the first level. If you want to display the terms such as "year" and "month" next to the chronology caption in the catlaog, then check the box beneath Display in holding field. +. To include additional levels of chronology, click Add Chronology Caption. Each level that you add must be smaller than the previous level. +. After you have completed the chronology caption, click Next. + +Page 4: Compress and Expand Captions +++++++++++++++++++++++++++++++++++++ + +image::media/cap-wiz-freq.jpg[Compress or Expand] + +. Select the appropriate option for compressing or expanding your captions in the catalog from the compressibility and expandability drop down menu. The entries in the drop down menu correspond to the indicator codes and the subfield $w in the 853 tag. Compressibility and expandability correspond to the first indicator in the 853 tag. +. Choose the appropriate caption evaluation from the drop down menu. +. Choose the frequency of your publication from the drop down menu. For irregular frequencies, you may wish to select use number of issues per year, and enter the total number of issues that you receive each year. However, in the . 0 release, recommended practice is that you use only regular frequencies. Planned development will create an additional step to aid in the creation of irregular frequencies. +. Click Next. + +Page 5: Regularity Information +++++++++++++++++++++++++++++++ + +image::media/cap-wiz-chan.jpg[Changes] + +. If needed, check box for Use specific regularity information +. Choose the appropriate information for combined, omitted or published issues +. Choose the appropriate frequency and issue +. Add additional rows as required + +Page 5: Finish Captions and Patterns +++++++++++++++++++++++++++++++++++++ + +. To complete the wizard, click Create Pattern Code. +. Return to Subscription Details. +. Confirm that the box adjacent to Active is checked. Click Save Changes. The row is now highlighted gray instead of orange. + +Creating an Issuance +~~~~~~~~~~~~~~~~~~~~ + +The Issuances function enables you to manually create an issue. Evergreen will use the initial issue that you manually create to predict future issues. + +image::media/scv-iss.jpg[Issue] + +. Click the Issuances link beneath the subscription. Right click or click Actions for Selected Rows, and click Issuance. +. Click the holdings code and click apply. Currently there is no wizard to create this code. The wizard is only available in the Alternate Serials Control View. +. Click the Caption/Pattern selecting the appropriate patternand click apply +. Click the date published and enter date information (format YYYY-MM-DD) and click apply +. Click label, enter label and click apply +. When finished, click Create Issuance(s) in the bottom right corner of the screen. +. A confirmation message appears. Click OK. + +Generate Prediction +~~~~~~~~~~~~~~~~~~~ + +. Open the Subscriptions tab. +. Right-click or click Actions for Selected Row -> Make predictions. +. A pop up box will aks you how many items you want to predict. Enter the number, and click OK. +. A confirmation message will appear. Click OK. +. Click the Issuances link to view the predicted issues. diff --git a/docs/serials/D-subscription-ASCV.txt b/docs/serials/D-subscription-ASCV.txt new file mode 100644 index 0000000000..0f0efa8d56 --- /dev/null +++ b/docs/serials/D-subscription-ASCV.txt @@ -0,0 +1,188 @@ +Alternate Serial Control View +----------------------------- + +Using the Alternate Serial Control View, you can create a subscription, a distribution, a stream, and a caption and pattern, and you can generate predictions and receive issues. To access Alternate Serial Control View, open a serials record, and click Actions for this Record >> Alternate Serial Control. This opens the Subscriptions interface + +. Create a subscription +. Create a distribution +. Create a a stream (within the distribution) +. Create a caption and pattern (or import from bibliographic or legacy serial records) +. Create at least the first issuance and generate predictions + +Creating a Subscription +~~~~~~~~~~~~~~~~~~~~~~~ + +A subscription is designed to hold all information related to a single serial title. Therefore, each library is likely to have only one subscription per serial title. + +image::media/ascv-sub.jpg[Creating a Subscription] + +. Add new subscriptions to a serials record that exists in the catalog. +. Create a subscription +. Click New Subscription. +. Select an owning library. The owning library indicates the organizational unit(s) whose staff can use this subscription. This menu is populated with the shortnames that you created for your libraries in the organizational units tree in Admin . Server Administration . Organizational Units. The rule of parental inheritance applies to this list. For example, if a system is made the owner of a subscription, then users, with appropriate permissions, at the branches within the system could also use this subscription. +. Enter the date that the subscription begins in the start date. Recommended practice is that you select the date from the drop down calendar although you can manually enter a date. Owning library and start date are required fields in the new subscription pop up box. +. Enter the date that the subscription ends in the end date. Recommended practice is to select a date from the drop down calendar, but you can manually enter a date, also. +. Enter the difference between the nominal publishing date of an issue and the date that you expect to receive your copy in the Expected Date Offset. For example, if an issue is published the first day of each month, but you receive the copy two days prior to the publication date, then enter -2 days into this field. +. Click Save. + +After you save the subscription, it will appear in a list with a hyperlinked ID number. Use the drop down menu at the top of the screen to view subscriptions at other organizations. + +Creating a Distribution +~~~~~~~~~~~~~~~~~~~~~~~ + +Distributions indicate the branches that should receive copies of a serial. Distributions work together with streams to indicate the number of copies that should be sent to each branch. + +image::media/ascv-distr.jpg[Creating a Distribution] + +. Click the Distributions tab. +. Click New Distribution. +. Enter a name for the distribution in the Label field. It may be useful to identify the branch to which you are distributing these issues in this field. This field is not publicly visible and only appears when an item is received. There are no limits on the number of characters that can be entered in this field. +. Select a holding library from the drop down menu. The holding library is the branch that will receive the copies. +. Select a copy template from the Receive Unit Template drop down menu. This menu is populated with the copy templates that you created in Copy Template Editor. ++ +[NOTE] +Label, Holding Library, and Receive Unit Template are required fields in the new distribution pop up box. ++ +. Ignore the fields, Unit Label Prefix and Unit Label Suffix. These fields are not functional in Alternate Serial Control View. +. Click Save. The distribution will appear in a list in the Distributions tab in the Subscription Details. + +Creating a Stream +~~~~~~~~~~~~~~~~~ + +Distributions work together with streams to indicate the number of copies that should be sent to each branch. Distributions identify the branches that should receive copies of a serial. Streams identify how many copies should be sent to each branch. Streams are intended for copies that are received on a recurring, even if irregular, basis. + +. Click the hyperlinked title of the distribution. The number of streams that have already been created for this distribution displays adjacent to the title. You can choose one of two ways to create a stream: New Stream or Create Many Streams. The New Stream button allows you to create one new stream and assign it a routing label. +. Click New Stream +. Enter a routing label so that the copy could be read by specific users or departments before the copy is shelved. The routing label appears during receiving and could be added to routing lists; it is not viewable by the public. Routing lists do not print from in 2.0. This field is optional. +. Click Save. ++ +[NOTE] +The "Create Many Streams button" allows you to create multiple streams at once, but it does not allow you to add a routing label when you create the stream. ++ +. Click Create Many Streams. +. Enter the number of streams that you want to create in the How many. Field. +. Click Create. + +Creating a Caption and Pattern +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +The Captions and Patterns wizard allows you to enter caption and pattern data as it is described by the 853, 854, and 855 MARC tags. These tags allow you to define how issues will be captioned, and how often the library receives issues of the serial. + +. Open the Subscription Details. +. Click the Captions and Patterns tab. +. Click Add Caption and Pattern. +. In the Type drop down box, select the MARC tag to which you would like to add data. +. In the Pattern Code drop down box, you can enter a JSON representation of the 85X tag by hand, or you can click the Wizard to enter the information in a user-friendly format. +. The Caption and Pattern that you create is Active by default, but you can deactivate a caption and pattern at a later time by unchecking the box. + + +[NOTE] +A subscription may have multiple captions and patterns listed in the subscripiton details, but only one Caption and Pattern can be active at any time. If you want to add multiple patterns, e.g. for Basic and Supplement, Click Add Caption and Pattern. + + +Use the Pattern Code Wizard +^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +The Pattern Code Wizard enables you to create the caption of the item and add its publication information. The Wizard is composed of five pages of questions. You can use the Next and Previous navigation buttons in the top corners to flip between pages. + +To add a pattern code, click Wizard. + +Page 1: Enumerations +++++++++++++++++++++ + +image::media/cap-wiz-num.jpg[Enuperation] + +. To add an enumeration, check the box adjacent to Use enumerations.. The enumerations conform to $a-$h of the 853,854, and 855 MARC tags. +. A field for the First level will appear. Enter the enumeration for the first level. A common first level enumeration is volume, or "v." +. Click Add Enumeration. +. A field for the Second level will appear. Enter the enumeration for the second level. A common first level enumeration is number, or "no." +. Enter the number of bibliographic units per next higher level. This conforms to $u in the 853, 854, and 855 MARC tags. +. Choose the enumeration scheme from the drop down menu. This conforms to $v in the 853, 854, and 855 MARC tags. ++ +[NOTE] +You can add up to six levels of enumeration. ++ +. Add Alternate Enumeration if desired. +. When you have completed the enumerations, click Next. + +Page 2: Calendar +++++++++++++++++ + +image::media/cap-wiz-cal.jpg[Enumeration] + +. To use months, seasons, or dates in your caption, check the box adjacent to Use calendar changes. +. Identify the point in the year at which the highest level enumeration caption changes. +. In the Type drop down menu, select the points during the year at which you want the calendar to restart. +. In the Point drop down menu, select the specific time at which you would like to change the calendar +. To add another calendar change, click Add Calendar Change. There are no limits on the number of calendar changes that you can add. +. When you have finished the calendar changes, click Next. + +Page 3: Chronology +++++++++++++++++++ + +image::media/cap-wiz-chron.jpg[Chronology] + +. To add chronological units to the captions, check the box adjacent to Use chronology captions. +. Choose a chronology for the first level. If you want to display the terms, "year" and "month" next to the chronology caption in the catlaog, then check the box beneath Display in holding field. +. To include additional levels of chronology, click Add Chronology Caption. Each level that you add must be smaller than the previous level. +. After you have completed the chronology caption, click Next. + +Page 4: Compress and Expand Captions +++++++++++++++++++++++++++++++++++++ + +image::media/cap-wiz-freq.jpg[Compress or Expand] + +. Select the appropriate option for compressing or expanding your captions in the catalog from the compressibility and expandability drop down menu. The entries in the drop down menu correspond to the indicator codes and the subfield $w in the 853 tag. Compressibility and expandability correspond to the first indicator in the 853 tag. +. Choose the appropriate caption evaluation from the drop down menu. +. Choose the frequency of your publication from the drop down menu. For irregular frequencies, you may wish to select use number of issues per year, and enter the total number of issues that you receive each year. However, in the . 0 release, recommended practice is that you use only regular frequencies. Planned development will create an additional step to aid in the creation of irregular frequencies. +. Click Next. + +Page 5: Regularity Information +++++++++++++++++++++++++++++++ + +image::media/cap-wiz-chan.jpg[Changes] + +. If needed, check box for Use specific regularity information +. Choose the appropriate information for combined, omitted or published issues +. Choose the appropriate frequency and issue +. Add additional rows as required + +Page 5: Finish Captions and Patterns +++++++++++++++++++++++++++++++++++++ + +. To complete the wizard, click Create Pattern Code. +. Return to Subscription Details. +. Confirm that the box adjacent to Active is checked. Click Save Changes. The row is now highlighted gray instead of orange. + +Creating an Issuance +~~~~~~~~~~~~~~~~~~~~ + +The Issuances tab enables you to manually create an issue. Evergreen will use the initial issue that you manually create to predict future issues. + +image::media/ascv-issues.jpg[Changes] + +. Click the Issuances tab in the Subscription Details. +. Click New Issuance. +. The Subscription, Creator, and Editor fields contain subscription and user IDs, respectively. These fields are disabled because Evergreen automatically fills in these fields. +. Enter a name for this issuance in the Label field. There are no limits on the number of characters that can be entered in this field. You may want to enter the month and year of the publication in hand. +. Enter the Date Published of the issuance that you are editing. Recommended practice is that you select the date from the drop down calendar although you can manually enter a date. If you are creating one manual issue before automatically predicting more issues, then this date should be the date of the most current issue before the prediction starts. +. Select a Caption/Pattern from the drop down menu. The numbers in the drop down menu correspond to the IDs of the caption/patterns that you created. +. The Holding Type appears by default and corresponds to the Type that you selected when you created the Caption/Pattern. +. In the holding code area of the New Issuance dialog, click Wizard. The Wizard enables you to add holdings information. +. Enter the volume of the item in hand in the v. field. +. Enter the number of the item in hand in the no. field. +. Enter the year of publication in the Year field. +. Enter the month of publication in the Month field if applicable. You must enter the calendar number of the month rather than the name of the month. For example, enter 12 if the item in hand was published in December. +. Enter the day of publication in the day field if applicable. +. Click Compile to generate the holdings code. + +Generate Item Predictions +~~~~~~~~~~~~~~~~~~~~~~~~~ + +After you manually create the first issue, Evergreen will predict future issuances. Use the Generate Predictions functionality to predict future issues. + +. Click Subscription Details -> Issuances -> Generate Predictions. +. Choose the length of time for which you want to predict issues. If you select the radio button to predict until end of subscription, then Evergreen will predict issues until the end date that you created when you created the subscription. See simplesect . 1 for more information. If you do not have an end date, select the radio button to predict a certain number of issuances, and enter a number in the field. +. Click Generate. +. Evergreen will predict a run of issuances and copies. The prediction will appear in a list. +. You can delete the first, manual issuance by clicking the check box adjacent to the issuance and clicking Delete Selected. diff --git a/docs/serials/E-edit_subscriptions.txt b/docs/serials/E-edit_subscriptions.txt new file mode 100644 index 0000000000..65caf8d8b2 --- /dev/null +++ b/docs/serials/E-edit_subscriptions.txt @@ -0,0 +1,19 @@ +Edit Subscriptions +------------------ +Subscriptions can be edite to change the caption and pattern and other information. + +Serials Control View +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +. To access Serial Control View, open a serials record, and click Actions for this Record >> Serial Control. This opens the Subscriptions interface +. Click the subscriptions tab +. Click on the appropriate link to edit + + +Alternate Serials Control View +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +. To access Alternate Serial Control View, open a serials record, and click Actions for this Record >> Alternate Serial Control. This opens the Subscriptions interface +. Click the hyperlinked ID number to edit the subscription. +. Click on the appropriate tab to edit the information + diff --git a/docs/serials/F-Receiving.txt b/docs/serials/F-Receiving.txt new file mode 100644 index 0000000000..656f202177 --- /dev/null +++ b/docs/serials/F-Receiving.txt @@ -0,0 +1,64 @@ +Receiving +--------- +You can receive either through the Serials Control View or in Batch Receive with the simple or advanced interface + +Serials Control View Receiving +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +image::media/scv-rec.jpg[Receiving] + +. To receive items, click the Receive radio button. In the top half of the screen, the items that have yet to be received are displayed. In the bottom half of the screen, recently received items are displayed. +. Select the branch that will receive the items from the drop down box. +. Select the issue that you want to receive. +. Select the current working unit. Click Set Current Unit, located in the lower right corner of the screen. A drop down menu will appear. + * If you want to barcode each item individually, select Auto per item. This setting is recommended for most receiving processes. + * If you want each item within a unit to share the same barcode, then select New Unit. This setting is advised for most binding processes. + * If you want the item to be received or bound into an existing item, select Recent and select the desired issue. To making a change in bound items, receive or bind the items into an already existing unit. +. Click Receive/Move Selected. +. Enter a barcode and call number if prompted to do so. +. A message confirming receipt of the item appears. Click OK. +. The screen refreshes. In the top half of the screen, the item displays a received date. In the bottom half of the screen, the item that you have just received is now at the top of the list of the received items. + +After receiving items, you can view the updated holdings in the OPAC. In this example, the legacy MFHD record and the items recently received in the serial control view display together in the MFHD statement. + +Batch Receiving +~~~~~~~~~~~~~~~ + +You can batch receive items through a simple or an advanced interface. The simple interface does not allow you to add barcodes or use the copy template. These items are also not visible in the OPAC. The advanced interface enables you to use the copy templates that you created, add barcodes, and make items OPAC visible and holdable. + +You can access both Batch Receive interfaces from two locations in the ILS. From the Subscription Details screen, you can click Batch Item Receive. You can also access these interfaces by opening the catalog record for the serial, and clicking Actions for this Record . Serials Batch Receive. + +Simple Batch Receiving +^^^^^^^^^^^^^^^^^^^^^^ +Follow these steps to receive items in batch in a simple interface. + +image::media/scv-srec.jpg[Receiving] + +. The Batch Receive interface displays issues that have not yet been received. The earliest expected issue appears at the top of the list. +. In the right lower corner, you see a check box to Create Units for Received Items. If you do not check this box, then you will receive items in simple mode. +. Click Next. +. In simple mode, the distributions that you created are displayed. They are marked received by default. If you hover over the branch name, you can view the name of the distribution and its stream. +. You can receive and add a note to each item individually, or you can perform these actions on all of the distributions and streams at once. To do so, look above the line, and enter the note that you want to apply to all copies and confirm that the box to Receive. is checked. +. Click Apply. The note should appear in the note field in each distribution. +. Then click Receive Selected Items. +. The received items are cleared from the screen. + +Advanced Batch Receiving +^^^^^^^^^^^^^^^^^^^^^^^^ +Follow these steps to receive items in batch in a simple interface. + +image::media/scv-srec.jpg[Receiving] + +. The Batch Receive interface displays issues that have not yet been received. The earliest expected issue appears at the top of the list. +. If you want to barcode each copy, display it in the catalog, and make it holdable, then check the box adjacent to Create Units for Received Items in the lower right side of the screen. +. This will allow you to utilize the copy templates and input additional information about the copy: +. Barcode - You can scan printed barcodes into the barcode field for each copy, or you can allow the system to auto-generate barcodes. To auto-generate barcodes, check the box adjacent to Auto-generate., and enter the first barcode into the barcode field in the first row of the table. Then press the Tab key. The remaining barcode fields will automatically populate with the next barcodes in sequence, including check digits. + . Circ Modifiers - The circ modifiers drop down menu is populated with the circulation modifiers that you created in Admin . Server Administration . Circulation Modifiers. If you entered a circ modifier in the copy template that you created for this subscription, then it will appear by default in the distributions. + . Call Number - Enter a call number. Any item with a barcode must also have a call number. + . Note - Add a note. There are no limits on the number of characters that can be entered in this field. The note only displays in this screen. + . Copy Location - The copy location drop down menu is populated with the copy locations that you created in Admin . Local Administration . Copy Location Editor. If you entered a copy location in the copy template that you created for this subscription, then it will appear by default in the distributions. + . Price - If you entered a price in the copy template that you created for this subscription, then it will appear by default in the distributions. You can also manually enter a price if you did not include one in the copy template. + . Receive - The boxes in the Receive Column are checked by default. Uncheck the box if you do not want to receive the item. Evergreen will retain the unreceived copies and will allow you to receive them at a later time. +. When you are ready to receive the items, click Receive Selected Items. +. The items that have been received are cleared from the Batch Receive interface. The remaining disabled item is an unreceived item. +. If the items that you received have a barcode, a copy template that was set to OPAC Visible, and are assigned a shelving location that is OPAC Visible, then you can view the received items in the catalog. Notice that the Holdings Summary has been updated to reflect the most recent addition to the holdings. diff --git a/docs/serials/G-Special_issue.txt b/docs/serials/G-Special_issue.txt new file mode 100644 index 0000000000..febf9bc7e7 --- /dev/null +++ b/docs/serials/G-Special_issue.txt @@ -0,0 +1,9 @@ +Special Issues +-------------- +Currently, Setting up the special issue can only be done through the Alternate Serials Control view. + +. Create an issuance in the Serials Control View or the Alternate Serials Control View +. In the Alternate Serials Control View, click on the name of your special issue in the list of issuances. +. Click the New Items button +. Enter the appropriate information +. The item is now ready to receive. If you complete the Date Received field and change the status to received then it will receive the issue but it won't create the associated copy record whereas if you leave it blank and receive the item through the Serials Control View or Batch Receive function you can create the Copy Record at that time. diff --git a/docs/serials/H-holdings_statements.txt b/docs/serials/H-holdings_statements.txt new file mode 100644 index 0000000000..2aa0c3babf --- /dev/null +++ b/docs/serials/H-holdings_statements.txt @@ -0,0 +1,35 @@ +Holdings +-------- + +System Generated Holdings Statement +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +As issues are received, Evergreen creates a holding statement in the OPAC based on what is set up in the Caption and Patterns of the subscription. The systems generated holdings can only be edited by changing caption and pattern information and there is no abilitiy to edit the statement as free text. + +MARC Format for Holdings Display (MFHD) +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +Evergreen users can create, edit and delete their own MFHD. + +Create an MFHD record +^^^^^^^^^^^^^^^^^^^^^ + +. Open a serial record, and in the bottom right corner above the copy information, click Add MFHD Record. You can also add the MFHD statement by clicking Actions for this Record .MFHD Holdings .Add MFHD Record. +. A message will confirm that you have created the MFHD Record. Click OK. +. Click Reload in the top left corner of the record. +. The Holdings Summary will appear. Click Edit Holdings in the right corner. +. Click Edit Record. +. The MFHD window will pop up. Enter holdings information. Click Save MFHD. +. Close the MFHD window. +. Click Reload in the top left corner of the record. The Holdings Summary will reflect the changes to the MFHD statement. + +Edit a MFHD record +^^^^^^^^^^^^^^^^^^ + +. Open a serial record, and in the Actions for this Record, click MFHD Record>>Edit MFHD Record and select the appropriate MFHD. +. Edit the MFHD +. Click Save MFHD + +Delete a MFHD Record +^^^^^^^^^^^^^^^^^^^^ + +. Open a serial record, and in the Actions for this Record, click MFHD Record>>Delete MFHD Record and select the appropriate MFHD. +. Click to confirm the deletion of the MFHD diff --git a/installation/edi_setup.txt b/installation/edi_setup.txt deleted file mode 100644 index ececa1564f..0000000000 --- a/installation/edi_setup.txt +++ /dev/null @@ -1,212 +0,0 @@ -Setting Up EDI Acquisitions ---------------------------- - -Introduction -~~~~~~~~~~~~ - -Electronic Data Interchange (EDI) is used to exchange information between -participating vendors and Evergreen. This chapter contains technical -information for installation and configuration of the components necessary -to run EDI Acquisitions for Evergreen. - -Installation -~~~~~~~~~~~~ - -Install EDI Translator -^^^^^^^^^^^^^^^^^^^^^^ - -The EDI Translator is used to convert data into EDI format. It runs -on localhost and listens on port 9191 by default. This is controlled via -the edi_webrick.cnf file located in the edi_translator directory. It should -not be necessary to edit this configuration if you install EDI Translator -on the same server used for running Action/Triggers events. - -[NOTE] -If you are running Evergreen with a multi-server configuration, make sure -to install EDI Translator on the same server used for Action/Trigger event -generation. - -.Steps for Installing - -1. As the *opensrf* user, copy the EDI Translator code found in - Open-ILS/src/edi_translator to somewhere accessible - (for example, /openils/var/edi): -+ -[source, bash] --------------------------------------------------- -cp -r Open-ILS/src/edi_translator /openils/var/edi --------------------------------------------------- -2. Navigate to where you have saved the code to begin next step: -+ -[source, bash] -------------------- -cd /openils/var/edi -------------------- -3. Next, as the *root* user (or a user with sudo rights), install the - dependencies, via "install.sh". This will perform some apt-get routines - to install the code needed for the EDI translator to function. - (Note: subversion must be installed first) -+ -[source, bash] ------------ -./install.sh ------------ -4. Now, we're ready to start "edi_webrick.bash" which is the script that calls - the "Ruby" code to translate EDI. This script needs to be started in - order for EDI to function so please take appropriate measures to ensure this - starts following reboots/upgrades/etc. As the *opensrf* user: -+ -[source, bash] ------------------ -./edi_webrick.bash ------------------ -5. You can check to see if EDI translator is running. - * Using the command "ps aux | grep edi" should show you something similar - if the script is running properly: -+ -[source, bash] ------------------------------------------------------------------------------------------- -root 30349 0.8 0.1 52620 10824 pts/0 S 13:04 0:00 ruby ./edi_webrick.rb ------------------------------------------------------------------------------------------- - * To shutdown EDI Translator you can use something like pkill (assuming - no other ruby processes are running on that server): -+ -[source, bash] ------------------------ -kill -INT $(pgrep ruby) ------------------------ - -Install EDI Scripts -^^^^^^^^^^^^^^^^^^^ - -The EDI scripts are "edi_pusher.pl" and "edi_fetcher.pl" and are used to -"push" and "fetch" EDI messages for configured EDI accounts. - -1. As the *opensrf* user, copy edi_pusher.pl and edi_fetcher.pl from - Open-ILS/src/support-scripts into /openils/bin: -+ -[source, bash] --------------------------------------------------- -cp Open-ILS/src/support-scripts/edi_pusher.pl /openils/bin -cp Open-ILS/src/support-scripts/edi_fetcher.pl /openils/bin --------------------------------------------------- -2. Setup the edi_pusher.pl and edi_fetcher.pl scripts to run as cron jobs - in order to regularly push and receive EDI messages. - * Add to the opensrf user's crontab the following entries: -+ -[source, bash] ------------------------------------------------------------------------ -10 * * * * cd /openils/bin && /usr/bin/perl ./edi_pusher.pl > /dev/null -0 1 * * * cd /openils/bin && /usr/bin/perl ./edi_fetcher.pl > /dev/null ------------------------------------------------------------------------ - * The example for edi_pusher.pl sets the script to run at - 10 minutes past the hour, every hour. - * The example for edi_fetcher.pl sets the script to run at - 1 AM every night. - -[NOTE] -You may choose to run the EDI scripts more or less frequently based on the -necessary response times from your vendors. - -Configuration -~~~~~~~~~~~~~ - -Configuring Providers -^^^^^^^^^^^^^^^^^^^^^ - -Look in Admin > Server Administration > Acquisitions > Providers - -[options="header"] -|====================================================================================== -|Column |Description/Notes -|Provider Name |A unique name to identify the provider -|Code |A unique code to identify the provider -|Owner |The org unit who will "own" the provider. -|Currency |The currency format the provider accepts -|Active |Whether or not the Provider is "active" for use -|Default Claim Policy|?? -|EDI Default |The default "EDI Account" to use (see EDI Accounts Configuration) -|Email |The email address for the provider -|Fax Phone |A fax number for the provider -|Holdings Tag |The holdings tag to be utilized (usually 852, for Evergreen) -|Phone |A phone number for the provider -|Prepayment Required |Whether or not prepayment is required -|SAN |The vendor provided, org unit specific SAN code -|URL |The vendor website -|====================================================================================== - -Configuring EDI Accounts -^^^^^^^^^^^^^^^^^^^^^^^^ - -Look in Admin > Server Administration > Acquisitions > EDI Accounts - -[options="header"] -|=============================================================================================================== -|Column |Description/Notes -|Label |A unique name to identify the provider -|Host |FTP/SFTP/SSH hostname - vendor assigned -|Username |FTP/SFTP/SSH username - vendor assigned -|Password |FTP/SFTP/SSH password - vendor assigned -|Account |Vendor assigned account number associated with your organization -|Owner |The organizational unit who owns the EDI account -|Last Activity |The date of last activity for the account -|Provider |This is a link to one of the "codes" in the "Providers" interface -|Path |The path on the vendor's server where Evergreen will send it's outgoing .epo files -|Incoming Directory |The path on the vendor's server where "incoming" .epo files are stored -|Vendor Account Number|Vendor assigned account number. -|Vendor Assigned Code |Usually a sub-account designation. Can be used with or without the Vendor Account Number. -|=============================================================================================================== - -Configuring Organizational Unit SAN code -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -Look in Admin > Server Settings > Organizational Units - -This interface allows a library to configure their SAN, alongside -their address, phone, etc. - -Troubleshooting -~~~~~~~~~~~~~~~ - -PO JEDI Template Issues -^^^^^^^^^^^^^^^^^^^^^^^ - -Some libraries may run into issues with the action/trigger (PO JEDI). -The template has to be modified to handle different vendor codes that -may be used. For instance, if you use "ingra" instead of INGRAM this -may cause a problem because they are hardcoded in the template. The -following is an example of one modification that seems to work. - -.Original template has: - -[source, bash] ----------------------------------------------------------------------------------------------------------------------------------------------- -"buyer":[ - [% IF target.provider.edi_default.vendcode && (target.provider.code == 'BT' || target.provider.name.match('(?i)^BAKER & TAYLOR')) -%] - {"id-qualifier": 91, "id":"[% target.ordering_agency.mailing_address.san _ ' ' _ target.provider.edi_default.vendcode %]"} - [%- ELSIF target.provider.edi_default.vendcode && target.provider.code == 'INGRAM' -%] - {"id":"[% target.ordering_agency.mailing_address.san %]"}, - {"id-qualifier": 91, "id":"[% target.provider.edi_default.vendcode %]"} - [%- ELSE -%] - {"id":"[% target.ordering_agency.mailing_address.san %]"} - [%- END -%] -], ----------------------------------------------------------------------------------------------------------------------------------------------- - -.Modified template has the following where it matches on provider SAN instead of code: - -[source, bash] ------------------------------------------------------------------------------------------------------------------------------------------- -"buyer":[ - [% IF target.provider.edi_default.vendcode && (target.provider.san == '1556150') -%] - {"id-qualifier": 91, "id":"[% target.ordering_agency.mailing_address.san _ ' ' _ target.provider.edi_default.vendcode %]"} - {"id-qualifier": 91, "id":"[% target.ordering_agency.mailing_address.san _ ' ' _ target.provider.edi_default.vendcode %]"} - [%- ELSIF target.provider.edi_default.vendcode && (target.provider.san == '1697978') -%] - {"id":"[% target.ordering_agency.mailing_address.san %]"}, - {"id-qualifier": 91, "id":"[% target.provider.edi_default.vendcode %]"} - [%- ELSE -%] - {"id":"[% target.ordering_agency.mailing_address.san %]"} - [%- END -%] -], ------------------------------------------------------------------------------------------------------------------------------------------- - diff --git a/installation/server_installation.txt b/installation/server_installation.txt deleted file mode 100644 index 0f52df4b14..0000000000 --- a/installation/server_installation.txt +++ /dev/null @@ -1,549 +0,0 @@ -README for Evergreen 2.2 -======================== -:toc: -:numbered: - -Preamble: referenced user accounts ----------------------------------- - -In subsequent sections, we will refer to a number of different accounts, as -follows: - - * Linux user accounts: - ** The *user* Linux account is the account that you use to log onto the - Linux system as a regular user. - ** The *root* Linux account is an account that has system administrator - privileges. On Debian and Fedora you can switch to this account from - your *user* account by issuing the `su -` command and entering the - password for the *root* account when prompted. On Ubuntu you can switch - to this account from your *user* account using the `sudo su -` command - and entering the password for your *user* account when prompted. - ** The *opensrf* Linux account is an account that you create when installing - OpenSRF. You can switch to this account from the *root* account by - issuing the `su - opensrf` command. - ** The *postgres* Linux account is created automatically when you install - the PostgreSQL database server. You can switch to this account from the - *root* account by issuing the `su - postgres` command. - * PostgreSQL user accounts: - ** The *evergreen* PostgreSQL account is a superuser account that you will - create to connect to the PostgreSQL database server. - * Evergreen administrator account: - ** The *egadmin* Evergreen account is an administrator account for - Evergreen that you will use to test connectivity and configure your - Evergreen instance. - -Preamble: Developer instructions --------------------------------- - -[NOTE] -Skip this section if you are using an official release tarball downloaded -from http://evergreen-ils.org/downloads - -Developers working directly with the source code from the Git repository, -rather than an official release tarball, must install some extra packages -and perform one step before they can proceed with the `./configure` step. - -As the *root* Linux account, install the following packages: - - * autoconf - * automake - * libtool - -As the *user* Linux account, issue the following command in the Evergreen -source directory to generate the configure script and Makefiles: - -[source, bash] ------------------------------------------------------------------------------- -autoreconf -i ------------------------------------------------------------------------------- - -After running `make install`, developers also need to install the Dojo Toolkit -set of JavaScript libraries. The appropriate version of Dojo is included -in Evergreen release tarballs. Developers should install the Dojo 1.3.3 -version of Dojo by issuing the following commands as the *opensrf* Linux -account: - -[source, bash] ------------------------------------------------------------------------------- -wget http://download.dojotoolkit.org/release-1.3.3/dojo-release-1.3.3.tar.gz -tar -C /openils/var/web/js -xzf dojo-release-1.3.3.tar.gz -cp -r /openils/var/web/js/dojo-release-1.3.3/* /openils/var/web/js/dojo/. ------------------------------------------------------------------------------- - -Installing prerequisites ------------------------- - -Evergreen has a number of prerequisite packages that must be installed -before you can successfully configure, compile, and install Evergreen. - -1. Begin by installing the most recent version of OpenSRF (2.1 or later). - You can download OpenSRF releases from http://evergreen-ils.org/opensrf.php -2. On many distributions, it is necessary to install PostgreSQL 9 from external - repositories. -+ - * On Debian Squeeze, open `/etc/apt/sources.list` in a text editor as the - *root* Linux account and add the following line: -+ -[source, bash] ------------------------------------------------------------------------------- -deb http://backports.debian.org/debian-backports squeeze-backports main contrib ------------------------------------------------------------------------------- -+ - * On Ubuntu Lucid, you can use a PPA (personal package archive), which are - package sources hosted on Launchpad. The one most commonly used by Evergreen - Community members is maintained by Martin Pitt, who also maintains the - official PostgreSQL packages for Ubuntu. As the *root* Linux account, issue - the following commands to add the PPA source: -+ -[source, bash] ------------------------------------------------------------------------------- -apt-get install python-software-properties -add-apt-repository ppa:pitti/postgresql ------------------------------------------------------------------------------- -+ - * Ubuntu Precise comes with PostgreSQL 9, so no additional steps are required. -+ - * Fedora 16 comes with PostgreSQL 9, so no additional steps are required. -+ -3. On Debian and Ubuntu, run `aptitude update` as the *root* Linux account to - retrieve the new packages from the backports repository. -4. Issue the following commands as the *root* Linux account to install - prerequisites using the `Makefile.install` prerequisite installer, - substituting `debian-squeeze`, `fedora16`, `ubuntu-lucid`, or - `ubuntu-precise` for below: -+ -[source, bash] ------------------------------------------------------------------------------- -make -f Open-ILS/src/extras/Makefile.install ------------------------------------------------------------------------------- -+ -5. Add the libdbi-libdbd libraries to the system dynamic library path by - issuing the following commands as the *root* Linux account: -+ -[NOTE] -You should skip this step if installing on Ubuntu Precise. The ubuntu-precise -target uses libdbd-pgsql from packages. -+ -.Debian / Ubuntu Lucid -[source, bash] ------------------------------------------------------------------------------- -echo "/usr/local/lib/dbd" > /etc/ld.so.conf.d/eg.conf -ldconfig ------------------------------------------------------------------------------- -+ -.Fedora -[source, bash] ------------------------------------------------------------------------------- -echo "/usr/lib64/dbd" > /etc/ld.so.conf.d/eg.conf -ldconfig ------------------------------------------------------------------------------- - -Configuration and compilation instructions ------------------------------------------- - -For the time being, we are still installing everything in the `/openils/` -directory. From the Evergreen source directory, issue the following commands as -the *user* Linux account to configure and build Evergreen: - -[source, bash] ------------------------------------------------------------------------------- -./configure --prefix=/openils --sysconfdir=/openils/conf -make ------------------------------------------------------------------------------- - -Installation instructions -------------------------- - -1. Once you have configured and compiled Evergreen, issue the following - command as the *root* Linux account to install Evergreen, build the server - portion of the staff client, and copy example configuration files to - `/openils/conf`. - Change the value of the `STAFF_CLIENT_STAMP_ID` variable to match the version - of the staff client that you will use to connect to the Evergreen server. -+ -[source, bash] ------------------------------------------------------------------------------- -make STAFF_CLIENT_STAMP_ID=rel_2_2 install ------------------------------------------------------------------------------- -+ -2. The server portion of the staff client expects `http://hostname/xul/server` - to resolve. Issue the following commands as the *root* Linux account to - create a symbolic link pointing to the `server` subdirectory of the server - portion of the staff client that we just built using the staff client ID - 'rel_name': -+ -[source, bash] ------------------------------------------------------------------------------- -cd /openils/var/web/xul -ln -sf rel_name/server server ------------------------------------------------------------------------------- - -Change ownership of the Evergreen files ---------------------------------------- - -All files in the `/openils/` directory and subdirectories must be owned by the -`opensrf` user. Issue the following command as the *root* Linux account to -change the ownership on the files: - -[source, bash] ------------------------------------------------------------------------------- -chown -R opensrf:opensrf /openils ------------------------------------------------------------------------------- - -Configure the Apache Web server -------------------------------- - -1. Use the example configuration files in `Open-ILS/examples/apache/` to -configure your Web server for the Evergreen catalog, staff client, Web -services, and administration interfaces. Issue the following commands as the -*root* Linux account: -+ -.Debian and Ubuntu -[source,bash] ------------------------------------------------------------------------------- -cp Open-ILS/examples/apache/eg.conf /etc/apache2/sites-available/ -cp Open-ILS/examples/apache/eg_vhost.conf /etc/apache2/ -cp Open-ILS/examples/apache/startup.pl /etc/apache2/ -# Now set up SSL -mkdir /etc/apache2/ssl -cd /etc/apache2/ssl ------------------------------------------------------------------------------- -+ -.Fedora -[source,bash] ------------------------------------------------------------------------------- -cp Open-ILS/examples/apache/eg.conf /etc/httpd/conf.d/ -cp Open-ILS/examples/apache/eg_vhost.conf /etc/httpd/ -cp Open-ILS/examples/apache/startup.pl /etc/httpd/ -# Now set up SSL -mkdir /etc/httpd/ssl -cd /etc/httpd/ssl ------------------------------------------------------------------------------- -+ -2. The `openssl` command cuts a new SSL key for your Apache server. For a -production server, you should purchase a signed SSL certificate, but you can -just use a self-signed certificate and accept the warnings in the staff client -and browser during testing and development. Create an SSL key for the Apache -server by issuing the following command as the *root* Linux account: -+ -[source,bash] ------------------------------------------------------------------------------- -openssl req -new -x509 -days 365 -nodes -out server.crt -keyout server.key ------------------------------------------------------------------------------- -+ -3. As the *root* Linux account, edit the `eg.conf` file that you copied into -place. - a. Replace `Allow from 10.0.0.0/8` with `Allow from all` (to enable - access to the offline upload / execute interface from any workstation on - any network - note that you must secure this for a production instance) - b. (Fedora): Change references from the non-existent `/etc/apache2/` directory - to `/etc/httpd/`. -4. Change the user for the Apache server. - * (Debian and Ubuntu): As the *root* Linux account, edit - `/etc/apache2/envvars`. Change `export APACHE_RUN_USER=www-data` to - `export APACHE_RUN_USER=opensrf`. - * (Fedora): As the *root* Linux account , edit `/etc/httpd/conf/httpd.conf`. - Change `User apache` to `User opensrf`. -5. Configure Apache with performance settings appropriate for Evergreen: - * (Debian and Ubuntu): As the *root* Linux account, edit - `/etc/apache2/apache2.conf`: - * (Fedora): As the *root* Linux account, edit `/etc/httpd/conf/httpd.conf`: - a. Change `KeepAliveTimeout` to `1`. Higher values reduce the chance of - a request timing out unexpectedly, but increase the risk of using up - all available Apache child processes. - b. 'Optional': Change `MaxKeepAliveRequests` to `100` - c. Update the prefork configuration section to suit your environment. The - following settings apply to a busy system: -+ -[source,bash] ------------------------------------------------------------------------------- - - StartServers 20 - MinSpareServers 5 - MaxSpareServers 15 - MaxClients 150 - MaxRequestsPerChild 10000 - ------------------------------------------------------------------------------- -+ -6. (Fedora): As the *root* Linux account, edit the `/etc/httpd/eg_vhost.conf` - file to change references from the non-existent `/etc/apache2/` directory - to `/etc/httpd/`. -7. (Debian and Ubuntu): As the *root* Linux account, enable the Evergreen site: -+ -[source,bash] ------------------------------------------------------------------------------- -a2dissite default # OPTIONAL: disable the default site (the "It Works" page) -a2ensite eg.conf ------------------------------------------------------------------------------- - -Configure OpenSRF for the Evergreen application ------------------------------------------------ -There are a number of example OpenSRF configuration files in `/openils/conf/` -that you can use as a template for your Evergreen installation. Issue the -following commands as the *opensrf* Linux account: - -[source, bash] ------------------------------------------------------------------------------- -cp -b /openils/conf/opensrf_core.xml.example /openils/conf/opensrf_core.xml -cp -b /openils/conf/opensrf.xml.example /openils/conf/opensrf.xml ------------------------------------------------------------------------------- - -When you installed OpenSRF, you created four Jabber users on two -separate domains and edited the `opensrf_core.xml` file accordingly. Please -refer back to the OpenSRF README and, as the *opensrf* Linux account, edit the -Evergreen version of the `opensrf_core.xml` file using the same Jabber users -and domains as you used while installing and testing OpenSRF. - -[NOTE] -The `-b` flag tells the `cp` command to create a backup version of the -destination file. The backup version of the destination file has a tilde (`~`) -appended to the file name, so if you have forgotten the Jabber users and -domains, you can retrieve the settings from the backup version of the files. - -`eg_db_config.pl`, described in the following section, sets the database -connection information in `opensrf.xml` for you. - -Creating the Evergreen database -------------------------------- - -By default, the `Makefile.install` prerequisite installer does not install -the PostgreSQL 9 database server required by every Evergreen system; -for production use, most libraries install the PostgreSQL database server on a -dedicated machine. You can install the packages required by Debian or Ubuntu Lucid -on the machine of your choice using the following commands as the *root* -Linux account: - -.(Debian and Ubuntu Lucid) Installing PostgreSQL 9.1 server packages -[source, bash] ------------------------------------------------------------------------------- -make -f Open-ILS/src/extras/Makefile.install install_pgsql_server_backport_debs_91 ------------------------------------------------------------------------------- - -.(Ubuntu Precise) Installing PostgreSQL 9.1 server packages -[source, bash] ------------------------------------------------------------------------------- -make -f Open-ILS/src/extras/Makefile.install install_pgsql_server_debs_91 ------------------------------------------------------------------------------- - -You can install the packages required by Fedora on the machine of your choice -using the following commands as the *root* Linux account: - -.(Fedora 16) Installing PostgreSQL server packages -[source, bash] ------------------------------------------------------------------------------- -make -f Open-ILS/src/extras/Makefile.install install_fedora_pgsql_server -postgresql-setup initdb ------------------------------------------------------------------------------- - -For a standalone PostgreSQL server, install the following Perl modules as the -*root* Linux account: - -.(Debian / Ubuntu) Installing additional Perl modules on a standalone PostgreSQL 9 server -[source, bash] ------------------------------------------------------------------------------- -aptitude install gcc libxml-libxml-perl libxml-libxslt-perl -cpan Business::ISBN -cpan JSON::XS -cpan Library::CallNumber::LC -cpan MARC::Record -cpan MARC::File::XML -cpan UUID::Tiny ------------------------------------------------------------------------------- - -.(Fedora 16) Installing additional Perl modules on a standalone PostgreSQL 9 server -[source, bash] ------------------------------------------------------------------------------- -yum install gcc perl-XML-LibXML perl-XML-LibXSLT perl-Business-ISBN -cpan Library::CallNumber::LC -cpan MARC::Record -cpan MARC::File::XML -cpan UUID::Tiny ------------------------------------------------------------------------------- - -You need to create a PostgreSQL superuser to create and access the database. -Issue the following command as the *postgres* Linux account to create a new -PostgreSQL superuser named `evergreen`. When prompted, enter the new user's -password: - -[source, bash] ------------------------------------------------------------------------------- -createuser -s -P evergreen ------------------------------------------------------------------------------- - -Once you have created the *evergreen* PostgreSQL account, you also need to -create the database and schema, and configure your configuration files to point -at the database server. Issue the following command as the *root* Linux account -from inside the Evergreen source directory, replacing , , -, , and with the appropriate values for your -PostgreSQL database (where and are for the *evergreen* -PostgreSQL account you just created), and replace and -with the values you want for the *egadmin* Evergreen administrator account: - -[source, bash] ------------------------------------------------------------------------------- -perl Open-ILS/src/support-scripts/eg_db_config.pl --update-config \ - --service all --create-database --create-schema --create-offline \ - --user --password --hostname --port \ - --database --admin-user --admin-pass ------------------------------------------------------------------------------- - -This creates the database and schema and configures all of the services in -your `/openils/conf/opensrf.xml` configuration file to point to that database. -It also creates the configuration files required by the Evergreen `cgi-bin` -administration scripts, and sets the user name and password for the *egadmin* -Evergreen administrator account to your requested values. - -Creating the database on a remote server -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -In a production instance of Evergreen, your PostgreSQL server should be -installed on a dedicated server. - -PostgreSQL 9.1 and later -^^^^^^^^^^^^^^^^^^^^^^^^ -To create the database instance on a remote database server running PostgreSQL -9.1 or later, simply use the `--create-database` flag on `eg_db_config.pl`. - -For PostgreSQL 9.0 -^^^^^^^^^^^^^^^^^^ -To create the database instance on a remote database server running PostgreSQL -9.0, you can either: - - * Install the PostgreSQL contrib modules on the machine on which you - are installing the Evergreen code, and use the `--create-database` - option from that machine, or - * Copy the `Open-ILS/src/sql/Pg/create_database.sql` script to your - PostgreSQL server and invoke it as the *postgres* Linux account: -+ -[source, bash] ------------------------------------------------------------------------------- -psql -vdb_name= -vcontrib_dir=`pg_config --sharedir`/contrib -f create_database.sql ------------------------------------------------------------------------------- - -Then you can issue the `eg_db_config.pl` command as above _without_ the -`--create-database` argument to create your schema and configure your -configuration files. - -Starting Evergreen ------------------- -1. As the *root* Linux account, start the `memcached` and `ejabberd` services -(if they aren't already running): -+ -[source, bash] ------------------------------------------------------------------------------- -/etc/init.d/ejabberd start -/etc/init.d/memcached start ------------------------------------------------------------------------------- -+ -2. As the *opensrf* Linux account, start Evergreen. The `-l` flag in the -following command is only necessary if you want to force Evergreen to treat the -hostname as `localhost`; if you configured `opensrf.xml` using the real -hostname of your machine as returned by `perl -ENet::Domain 'print -Net::Domain::hostfqdn() . "\n";'`, you should not use the `-l` flag. -+ -[source, bash] ------------------------------------------------------------------------------- -osrf_ctl.sh -l -a start_all ------------------------------------------------------------------------------- -+ - ** If you receive the error message `bash: osrf_ctl.sh: command not found`, - then your environment variable `PATH` does not include the `/openils/bin` - directory; this should have been set in the *opensrf* Linux account's - `.bashrc` configuration file. To manually set the `PATH` variable, edit the - configuration file `~/.bashrc` as the *opensrf* Linux account and add the - following line: -+ -[source, bash] ------------------------------------------------------------------------------- -export PATH=$PATH:/openils/bin ------------------------------------------------------------------------------- -+ -3. As the *opensrf* Linux account, generate the Web files needed by the staff - client and catalogue and update the organization unit proximity (you need to do - this the first time you start Evergreen, and after that each time you change - the library hierarchy in `config.cgi`): -+ -[source, bash] ------------------------------------------------------------------------------- -autogen.sh -u ------------------------------------------------------------------------------- -+ -4. As the *root* Linux account, restart the Apache Web server: -+ -[source, bash] ------------------------------------------------------------------------------- -/etc/init.d/apache2 restart ------------------------------------------------------------------------------- -+ -If the Apache Web server was running when you started the OpenSRF services, you -might not be able to successfully log in to the OPAC or staff client until the -Apache Web server is restarted. - -Testing connections to Evergreen --------------------------------- - -Once you have installed and started Evergreen, test your connection to -Evergreen via `srfsh`. As the *opensrf* Linux account, issue the following -commands to start `srfsh` and try to log onto the Evergreen server using the -*egadmin* Evergreen administrator user name and password that you set using the -`eg_db_config.pl` command: - -[source, bash] ------------------------------------------------------------------------------- -/openils/bin/srfsh -srfsh% login ------------------------------------------------------------------------------- - -You should see a result like: - - Received Data: "250bf1518c7527a03249858687714376" - ------------------------------------ - Request Completed Successfully - Request Time in seconds: 0.045286 - ------------------------------------ - - Received Data: { - "ilsevent":0, - "textcode":"SUCCESS", - "desc":" ", - "pid":21616, - "stacktrace":"oils_auth.c:304", - "payload":{ - "authtoken":"e5f9827cc0f93b503a1cc66bee6bdd1a", - "authtime":420 - } - - } - - ------------------------------------ - Request Completed Successfully - Request Time in seconds: 1.336568 - ------------------------------------ - -If this does not work, it's time to do some troubleshooting. - - * As the *opensrf* Linux acccount, run the `settings-tester.pl` script to see - if it finds any system configuration problems. The script is found at - `Open-ILS/src/support-scripts/settings-tester.pl` in the Evergreen source - tree. - * Follow the steps in the http://evergreen-ils.org/dokuwiki/doku.php?id=troubleshooting:checking_for_errors[troubleshooting guide]. - * If you have faithfully followed the entire set of installation steps - listed here, you are probably extremely close to a working system. - Gather your configuration files and log files and contact the - http://open-ils.org/listserv.php[Evergreen development mailing list] - for assistance before making any drastic changes to your system - configuration. - -Getting help ------------- - -Need help installing or using Evergreen? Join the mailing lists at -http://evergreen-ils.org/listserv.php or contact us on the Freenode -IRC network on the #evergreen channel. - -License -------- -This work is licensed under the Creative Commons Attribution-ShareAlike 3.0 -Unported License. To view a copy of this license, visit -http://creativecommons.org/licenses/by-sa/3.0/ or send a letter to Creative -Commons, 444 Castro Street, Suite 900, Mountain View, California, 94041, USA. diff --git a/installation/server_upgrade.txt b/installation/server_upgrade.txt deleted file mode 100644 index f8c25ff301..0000000000 --- a/installation/server_upgrade.txt +++ /dev/null @@ -1,244 +0,0 @@ -Upgrading the Evergreen Server ------------------------------- -Before upgrading, it is important to carefully plan an upgrade strategy to minimize system downtime and service interruptions. -All of the steps in this chapter are to be completed from the command line. - -Software Prerequisites: -~~~~~~~~~~~~~~~~~~~~~~~ - - * **PostgreSQL**: Version 9.1 is recommended. The minimum supported version - is 9.0. - * **Linux**: Evergreen 2.0 has been tested on Debian Squeeze (6.0), - Ubuntu Lucid Lynx (10.04) and Ubuntu Precise Pangolin (12.04). If you are - running an older version of these distributions, you may want to upgrade - before upgrading Evergreen. For instructions on upgrading these - distributions, visit the Debian or Ubuntu websites. - * **OpenSRF**: The minimum supported version of OpenSRF is 2.1.0. - -In the following instructions, you are asked to perform certain steps as either the root or opensrf user. - - * **Debian**: To become the root user, issue the `su` command and enter the password of the root user. - * **Ubuntu**: To become the root user, issue the `sudo su` command and enter the password of your current user. - -To switch from the root user to a different user, issue the `su - [user]` -command; for example, `su - opensrf`. Once you have become a non-root user, to -become the root user again simply issue the `exit` command. - -[CAUTION] -Pay attention to error output as you run these scripts. If you encounter errors -that you cannot resolve yourself through additional troubleshooting, please -report the errors to the http://evergreen-ils.org/listserv.php[Evergreen -Technical Discussion List]. - -Upgrade the Evergreen database schema -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -The upgrade of the Evergreen database schema is the lengthiest part of the -upgrade process for sites with a significant amount of production data. - -Before running the upgrade script against your production Evergreen database, -back up your database, restore it to a test server, and run the upgrade script -against the test server. This enables you to determine how long the upgrade -will take and whether any local customizations present problems for the -stock upgrade script that require further tailoring of the upgrade script. -The backup also enables you to cleanly restore your production data if -anything goes wrong during the upgrade. - -Run the following script as a user with the ability to connect to the -database server. Adjust the arguments to the `psql` command to reflect your -database server connection information: - -[source, bash] ----------------------------------------------------------- -cd /home/opensrf/Evergreen-ILS-2.1-rc1/Open-ILS/src/sql/Pg -psql -U evergreen -h localhost -f version_upgrade/2.1-2.2-upgrade-db.sql evergreen ----------------------------------------------------------- - -Upgrade the Evergreen code -~~~~~~~~~~~~~~~~~~~~~~~~~~ -The following steps guide you through a simplistic upgrade of a production -server. You must adjust these steps to accommodate your customizations such -as catalogue skins. - -. Stop Evergreen and back up your data: - .. As root, stop the Apache web server. - .. As the opensrf user, stop all Evergreen and OpenSRF services: -+ -[source, bash] ------------------------------ -osrf_ctl.sh -l -a stop_all ------------------------------ -+ - .. Back up the /openils directory. -. Upgrade OpenSRF. Download and install the latest version of OpenSRF from -the http://evergreen-ils.org/opensrf.php[OpenSRF download page]. -. As the opensrf user, download and extract Evergreen 2.2: -+ -[source, bash] ------------------------------------------------ -wget http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.2-rc1.tar.gz -tar xzf Evergreen-ILS-2.2-rc1.tar.gz ------------------------------------------------ -+ -[NOTE] -For the latest edition of Evergreen, check the http://evergreen-ils.org/downloads.php[Evergreen download page] and adjust upgrading instructions accordingly. -+ -. As the root user, install the prerequisites: -+ -[source, bash] ----------------------------------------------- -cd /home/opensrf/Evergreen-ILS-2.2-rc1 ---------------------------------------------- -+ -On the next command, replace `[distribution]` with one of these values for your -distribution of Debian or Ubuntu: - - * `debian-squeeze` for Debian Squeeze (6.0) - * `ubuntu-lucid` for Ubuntu Lucid Lynx (10.04) - * `ubuntu-precise` for Ubuntu Precise Pangolin (12.04) -+ -[source, bash] ------------------------------------------------------------- -make -f Open-ILS/src/extras/Makefile.install [distribution] ------------------------------------------------------------- -+ -. As the opensrf user, configure and compile Evergreen: -+ -[source, bash] ------------------------------------------------------------- -cd /home/opensrf/Evergreen-ILS-2.2-rc1 -./configure --prefix=/openils --sysconfdir=/openils/conf -make ------------------------------------------------------------- -+ -. As the root user, install Evergreen: -+ -[source, bash] ------------------------------------------------------------- -cd /home/opensrf/Evergreen-ILS-2.2-rc1 -make STAFF_CLIENT_STAMP_ID=rel_2_2_rc1 install ------------------------------------------------------------- -+ -. As the root user, change all files to be owned by the opensrf user and group: -+ -[source, bash] ------------------------------------------------------------- -chown -R opensrf:opensrf /openils ------------------------------------------------------------- -+ -. As the opensrf user, update the configuration files: -+ -[source, bash] ------------------------------------------------------------ -cd /home/opensrf/Evergreen-ILS-2.2-rc1 - -perl Open-ILS/src/support-scripts/eg_db_config.pl \ ---create-offline --user evergreen --password evergreen \ ---hostname localhost --port 5432 --database evergreen ----------------------------------------------------------- -+ -. As the opensrf user, update the server symlink in /openils/var/web/xul/: -+ -[source, bash] ------------------------------------------------------------ -cd /openils/var/web/xul/ -rm server -ln -s rel_2_2_rc1/server ----------------------------------------------------------- -+ -. As the opensrf user, update opensrf_core.xml and opensrf.xml by copying the - new example files (/openils/conf/opensrf_core.xml.example and - /openils/conf/opensrf.xml). -+ -[source, bash] ----------------------------------------------------------- -cp /openils/conf/opensrf_core.xml.example /openils/conf/opensrf_core.xml -cp /openils/conf/opensrf.xml.example /openils/conf/opensrf.xml ----------------------------------------------------------- -+ -[CAUTION] -Copying these configuration files will remove any customizations you have made to them. Remember to redo your customizations after copying them. -+ -. Update Apache files: -+ -[CAUTION] -Copying these Apache configuration files will remove any customizations you have made to them. Remember to redo your customizations after copying them. -For example, if you purchased an SSL certificate, you will need to edit eg.conf to point to the appropriate SSL certificate files. -+ -.. Update /etc/apache2/startup.pl by copying the example from Open-ILS/examples/apache/startup.pl. -.. Update /etc/apache2/eg_vhost.conf by copying the example from Open-ILS/examples/apache/eg_vhost.conf. -.. Update /etc/apache2/sites-available/eg.conf by copying the example from Open-ILS/ examples/apache/eg.conf. -. Update opensrf.xml with the database connection info: -+ -As the opensrf user, if you are happy with the default settings in -opensrf.xml.example, then: -+ -[source, bash] -------------------------------------------------------------------------- -cp -b /openils/conf/opensrf.xml.example /openils/conf/opensrf.xml -cd /home/opensrf/Evergreen-ILS-2.2-rc1 -perl Open-ILS/src/support-scripts/eg_db_config.pl --update-config --service all \ ---database evergreen --host localhost --user evergreen --password evergreen -------------------------------------------------------------------------- -+ -Otherwise, compare /openils/conf/opensrf.xml with /openils/conf/opensrf.xml.example and manually copy the new pieces into place in your existing opensrf.xml file - -Restart Evergreen and Test -~~~~~~~~~~~~~~~~~~~~~~~~~~ -. As the opensrf user, start all Evergreen and OpenSRF services: -+ -[source, bash] --------------------------------------------------------------- -osrf_ctl.sh -l -a start_all --------------------------------------------------------------- -+ -. As the opensrf user, run autogen to refresh the static organizational data files: -+ -[source, bash] --------------------------------------------------------------- -cd /openils/bin -../autogen.sh --------------------------------------------------------------- -+ -. Start srfsh and try logging in using your Evergreen username and password: -+ -[source, bash] --------------------------------------------------------------- -/openils/bin/srfsh -srfsh% login username password --------------------------------------------------------------- -+ -You should see a result like: -+ -[source, bash] ------------------------------------------------------- -Received Data: "250bf1518c7527a03249858687714376" - ------------------------------------ - Request Completed Successfully - Request Time in seconds: 0.045286 - ------------------------------------ - - Received Data: { - "ilsevent":0, - "textcode":"SUCCESS", - "desc":" ", - "pid":21616, - "stacktrace":"oils_auth.c:304", - "payload":{ - "authtoken":"e5f9827cc0f93b503a1cc66bee6bdd1a", - "authtime":420 - } - - } - - ------------------------------------ - Request Completed Successfully - Request Time in seconds: 1.336568 - ------------------------------------ ----------------------------------------------------------- -+ -If this does not work, it's time to do some troubleshooting. -+ -. As the root user, start the Apache web server. -+ -If you encounter errors, refer to the troubleshooting section of this documentation for tips on finding solutions and seeking further assistance -from the Evergreen community. diff --git a/installation/system_requirements.txt b/installation/system_requirements.txt deleted file mode 100644 index 765da132e2..0000000000 --- a/installation/system_requirements.txt +++ /dev/null @@ -1,32 +0,0 @@ -System Requirements -------------------- - -Server Minimum Requirements -~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -The following are the base requirements setting Evergreen up on a test server: - - * An available desktop, server or virtual image - * 1GB RAM, or more if your server also runs a graphical desktop - * Linux Operating System - * Ports 80 and 443 should be opened in your firewall for TCP connections to allow OPAC and staff client connections to the Evergreen server. - -Staff Client Requirements -~~~~~~~~~~~~~~~~~~~~~~~~~ - -Staff terminals connect to the central database using the Evergreen staff client, available for download from The Evergreen download page. -The staff client must be installed on each staff workstation and requires at minimum: - - * Windows (XP, Vista, or 7), Mac OS X, or Linux operating system - * a reliable high speed Internet connection - * 512Mb of RAM - * The staff client uses the TCP protocal on ports 80 and 443 to communicate with the Evergreen server. - -*Barcode Scanners* - -Evergreen will work with virtually any barcode scanner – if it worked with your legacy system it should work on Evergreen. - -*Printers* - -Evergreen can use any printer configured for your terminal to print receipts, check-out slips, holds lists, etc. The single exception is spine label printing, -which is still under development. Evergreen currently formats spine labels for output to a label roll printer. If you do not have a roll printer manual formatting may be required. diff --git a/licensing.txt b/licensing.txt deleted file mode 100644 index a9f2ec39d5..0000000000 --- a/licensing.txt +++ /dev/null @@ -1,13 +0,0 @@ -Licensing -========= - -Creative Commons License ------------------------- - -image::media/ccbysa.png["CC-BY-SA",link="http://creativecommons.org/licenses/by-sa/3.0/"] - -This work is licensed under a -link:http://creativecommons.org/licenses/by-sa/3.0/[Creative -Commons Attribution-ShareAlike 3.0 Unported License]. - - diff --git a/media/1.png b/media/1.png deleted file mode 100644 index 7d473430b7..0000000000 Binary files a/media/1.png and /dev/null differ diff --git a/media/10.png b/media/10.png deleted file mode 100644 index 997bbc8246..0000000000 Binary files a/media/10.png and /dev/null differ diff --git a/media/11.png b/media/11.png deleted file mode 100644 index ce47dac3f5..0000000000 Binary files a/media/11.png and /dev/null differ diff --git a/media/12.png b/media/12.png deleted file mode 100644 index 31daf4e2f2..0000000000 Binary files a/media/12.png and /dev/null differ diff --git a/media/13.png b/media/13.png deleted file mode 100644 index 14021a89c2..0000000000 Binary files a/media/13.png and /dev/null differ diff --git a/media/14.png b/media/14.png deleted file mode 100644 index 64014b75fe..0000000000 Binary files a/media/14.png and /dev/null differ diff --git a/media/15.png b/media/15.png deleted file mode 100644 index 0d65765fcf..0000000000 Binary files a/media/15.png and /dev/null differ diff --git a/media/2.png b/media/2.png deleted file mode 100644 index 5d09341b2f..0000000000 Binary files a/media/2.png and /dev/null differ diff --git a/media/3.png b/media/3.png deleted file mode 100644 index ef7b700471..0000000000 Binary files a/media/3.png and /dev/null differ diff --git a/media/4.png b/media/4.png deleted file mode 100644 index adb8364eb5..0000000000 Binary files a/media/4.png and /dev/null differ diff --git a/media/5.png b/media/5.png deleted file mode 100644 index 4d7eb46002..0000000000 Binary files a/media/5.png and /dev/null differ diff --git a/media/6.png b/media/6.png deleted file mode 100644 index 0ba694af6c..0000000000 Binary files a/media/6.png and /dev/null differ diff --git a/media/7.png b/media/7.png deleted file mode 100644 index 472e96f8ac..0000000000 Binary files a/media/7.png and /dev/null differ diff --git a/media/8.png b/media/8.png deleted file mode 100644 index 5e60973c21..0000000000 Binary files a/media/8.png and /dev/null differ diff --git a/media/9.png b/media/9.png deleted file mode 100644 index a0676d26cc..0000000000 Binary files a/media/9.png and /dev/null differ diff --git a/media/Authority_Control_Sets1.jpg b/media/Authority_Control_Sets1.jpg deleted file mode 100644 index 9ecdc58489..0000000000 Binary files a/media/Authority_Control_Sets1.jpg and /dev/null differ diff --git a/media/Authority_Control_Sets1.jpg.1 b/media/Authority_Control_Sets1.jpg.1 deleted file mode 100644 index 9ecdc58489..0000000000 Binary files a/media/Authority_Control_Sets1.jpg.1 and /dev/null differ diff --git a/media/Authority_Control_Sets2.jpg b/media/Authority_Control_Sets2.jpg deleted file mode 100644 index 4bea42d834..0000000000 Binary files a/media/Authority_Control_Sets2.jpg and /dev/null differ diff --git a/media/Authority_Control_Sets2.jpg.1 b/media/Authority_Control_Sets2.jpg.1 deleted file mode 100644 index 4bea42d834..0000000000 Binary files a/media/Authority_Control_Sets2.jpg.1 and /dev/null differ diff --git a/media/Authority_Control_Sets3.jpg b/media/Authority_Control_Sets3.jpg deleted file mode 100644 index 50beca2a86..0000000000 Binary files a/media/Authority_Control_Sets3.jpg and /dev/null differ diff --git a/media/Authority_Control_Sets3.jpg.1 b/media/Authority_Control_Sets3.jpg.1 deleted file mode 100644 index 50beca2a86..0000000000 Binary files a/media/Authority_Control_Sets3.jpg.1 and /dev/null differ diff --git a/media/Authority_Control_Sets4.jpg b/media/Authority_Control_Sets4.jpg deleted file mode 100644 index b563a56400..0000000000 Binary files a/media/Authority_Control_Sets4.jpg and /dev/null differ diff --git a/media/Authority_Control_Sets4.jpg.1 b/media/Authority_Control_Sets4.jpg.1 deleted file mode 100644 index b563a56400..0000000000 Binary files a/media/Authority_Control_Sets4.jpg.1 and /dev/null differ diff --git a/media/Authority_Control_Sets5.jpg b/media/Authority_Control_Sets5.jpg deleted file mode 100644 index a853f4b56c..0000000000 Binary files a/media/Authority_Control_Sets5.jpg and /dev/null differ diff --git a/media/Authority_Control_Sets5.jpg.1 b/media/Authority_Control_Sets5.jpg.1 deleted file mode 100644 index a853f4b56c..0000000000 Binary files a/media/Authority_Control_Sets5.jpg.1 and /dev/null differ diff --git a/media/Authority_Control_Sets6.jpg b/media/Authority_Control_Sets6.jpg deleted file mode 100644 index 646a4fa9ce..0000000000 Binary files a/media/Authority_Control_Sets6.jpg and /dev/null differ diff --git a/media/Authority_Control_Sets6.jpg.1 b/media/Authority_Control_Sets6.jpg.1 deleted file mode 100644 index 646a4fa9ce..0000000000 Binary files a/media/Authority_Control_Sets6.jpg.1 and /dev/null differ diff --git a/media/Authority_Control_Sets7.jpg b/media/Authority_Control_Sets7.jpg deleted file mode 100644 index 7f318024ee..0000000000 Binary files a/media/Authority_Control_Sets7.jpg and /dev/null differ diff --git a/media/Authority_Control_Sets7.jpg.1 b/media/Authority_Control_Sets7.jpg.1 deleted file mode 100644 index 7f318024ee..0000000000 Binary files a/media/Authority_Control_Sets7.jpg.1 and /dev/null differ diff --git a/media/Authority_Control_Sets8.jpg b/media/Authority_Control_Sets8.jpg deleted file mode 100644 index b4d776a1a1..0000000000 Binary files a/media/Authority_Control_Sets8.jpg and /dev/null differ diff --git a/media/Authority_Control_Sets8.jpg.1 b/media/Authority_Control_Sets8.jpg.1 deleted file mode 100644 index b4d776a1a1..0000000000 Binary files a/media/Authority_Control_Sets8.jpg.1 and /dev/null differ diff --git a/media/Authority_Control_Sets9.jpg b/media/Authority_Control_Sets9.jpg deleted file mode 100644 index d9d11c8ff6..0000000000 Binary files a/media/Authority_Control_Sets9.jpg and /dev/null differ diff --git a/media/Authority_Control_Sets9.jpg.1 b/media/Authority_Control_Sets9.jpg.1 deleted file mode 100644 index d9d11c8ff6..0000000000 Binary files a/media/Authority_Control_Sets9.jpg.1 and /dev/null differ diff --git a/media/Auto_Suggest_in_Catalog_Search1.jpg b/media/Auto_Suggest_in_Catalog_Search1.jpg deleted file mode 100644 index 6cbf623590..0000000000 Binary files a/media/Auto_Suggest_in_Catalog_Search1.jpg and /dev/null differ diff --git a/media/Auto_Suggest_in_Catalog_Search2.jpg b/media/Auto_Suggest_in_Catalog_Search2.jpg deleted file mode 100644 index c17abdb305..0000000000 Binary files a/media/Auto_Suggest_in_Catalog_Search2.jpg and /dev/null differ diff --git a/media/Batch_Importing_MARC_Records1.jpg b/media/Batch_Importing_MARC_Records1.jpg deleted file mode 100644 index ae0962afbb..0000000000 Binary files a/media/Batch_Importing_MARC_Records1.jpg and /dev/null differ diff --git a/media/Batch_Importing_MARC_Records10.jpg b/media/Batch_Importing_MARC_Records10.jpg deleted file mode 100644 index 089c9a1ed2..0000000000 Binary files a/media/Batch_Importing_MARC_Records10.jpg and /dev/null differ diff --git a/media/Batch_Importing_MARC_Records11.jpg b/media/Batch_Importing_MARC_Records11.jpg deleted file mode 100644 index 089c9a1ed2..0000000000 Binary files a/media/Batch_Importing_MARC_Records11.jpg and /dev/null differ diff --git a/media/Batch_Importing_MARC_Records12.jpg b/media/Batch_Importing_MARC_Records12.jpg deleted file mode 100644 index d51536e5d2..0000000000 Binary files a/media/Batch_Importing_MARC_Records12.jpg and /dev/null differ diff --git a/media/Batch_Importing_MARC_Records13.jpg b/media/Batch_Importing_MARC_Records13.jpg deleted file mode 100644 index d51536e5d2..0000000000 Binary files a/media/Batch_Importing_MARC_Records13.jpg and /dev/null differ diff --git a/media/Batch_Importing_MARC_Records14.jpg b/media/Batch_Importing_MARC_Records14.jpg deleted file mode 100644 index f192db2533..0000000000 Binary files a/media/Batch_Importing_MARC_Records14.jpg and /dev/null differ diff --git a/media/Batch_Importing_MARC_Records15.jpg b/media/Batch_Importing_MARC_Records15.jpg deleted file mode 100644 index 1413bc5c77..0000000000 Binary files a/media/Batch_Importing_MARC_Records15.jpg and /dev/null differ diff --git a/media/Batch_Importing_MARC_Records2.jpg b/media/Batch_Importing_MARC_Records2.jpg deleted file mode 100644 index b022f873ae..0000000000 Binary files a/media/Batch_Importing_MARC_Records2.jpg and /dev/null differ diff --git a/media/Batch_Importing_MARC_Records3.jpg b/media/Batch_Importing_MARC_Records3.jpg deleted file mode 100644 index 124712c72e..0000000000 Binary files a/media/Batch_Importing_MARC_Records3.jpg and /dev/null differ diff --git a/media/Batch_Importing_MARC_Records4.jpg b/media/Batch_Importing_MARC_Records4.jpg deleted file mode 100644 index 4d556a1bfb..0000000000 Binary files a/media/Batch_Importing_MARC_Records4.jpg and /dev/null differ diff --git a/media/Batch_Importing_MARC_Records5.jpg b/media/Batch_Importing_MARC_Records5.jpg deleted file mode 100644 index 3410561afa..0000000000 Binary files a/media/Batch_Importing_MARC_Records5.jpg and /dev/null differ diff --git a/media/Batch_Importing_MARC_Records6.jpg b/media/Batch_Importing_MARC_Records6.jpg deleted file mode 100644 index b0dfc8a7a1..0000000000 Binary files a/media/Batch_Importing_MARC_Records6.jpg and /dev/null differ diff --git a/media/Batch_Importing_MARC_Records7.jpg b/media/Batch_Importing_MARC_Records7.jpg deleted file mode 100644 index e26303ea81..0000000000 Binary files a/media/Batch_Importing_MARC_Records7.jpg and /dev/null differ diff --git a/media/Batch_Importing_MARC_Records8.jpg b/media/Batch_Importing_MARC_Records8.jpg deleted file mode 100644 index c8cf321bc2..0000000000 Binary files a/media/Batch_Importing_MARC_Records8.jpg and /dev/null differ diff --git a/media/Batch_Importing_MARC_Records9.jpg b/media/Batch_Importing_MARC_Records9.jpg deleted file mode 100644 index 315f5b938a..0000000000 Binary files a/media/Batch_Importing_MARC_Records9.jpg and /dev/null differ diff --git a/media/Call_Number_Prefixes_and_Suffixes_2_21.jpg b/media/Call_Number_Prefixes_and_Suffixes_2_21.jpg deleted file mode 100644 index 825b46c2f6..0000000000 Binary files a/media/Call_Number_Prefixes_and_Suffixes_2_21.jpg and /dev/null differ diff --git a/media/Call_Number_Prefixes_and_Suffixes_2_22.jpg b/media/Call_Number_Prefixes_and_Suffixes_2_22.jpg deleted file mode 100644 index 1d3f8b621b..0000000000 Binary files a/media/Call_Number_Prefixes_and_Suffixes_2_22.jpg and /dev/null differ diff --git a/media/Call_Number_Prefixes_and_Suffixes_2_22.jpg.1 b/media/Call_Number_Prefixes_and_Suffixes_2_22.jpg.1 deleted file mode 100644 index 1d3f8b621b..0000000000 Binary files a/media/Call_Number_Prefixes_and_Suffixes_2_22.jpg.1 and /dev/null differ diff --git a/media/Customizable_Toolbar1.jpg b/media/Customizable_Toolbar1.jpg deleted file mode 100644 index 5bd5f53639..0000000000 Binary files a/media/Customizable_Toolbar1.jpg and /dev/null differ diff --git a/media/Customizable_Toolbar2.jpg b/media/Customizable_Toolbar2.jpg deleted file mode 100644 index 3aed02b630..0000000000 Binary files a/media/Customizable_Toolbar2.jpg and /dev/null differ diff --git a/media/Customizable_Toolbar3.jpg b/media/Customizable_Toolbar3.jpg deleted file mode 100644 index ae4cbbf1ba..0000000000 Binary files a/media/Customizable_Toolbar3.jpg and /dev/null differ diff --git a/media/Customizable_Toolbar4.jpg b/media/Customizable_Toolbar4.jpg deleted file mode 100644 index e5c1399010..0000000000 Binary files a/media/Customizable_Toolbar4.jpg and /dev/null differ diff --git a/media/Double_Click1.jpg b/media/Double_Click1.jpg deleted file mode 100644 index 87bd0b514c..0000000000 Binary files a/media/Double_Click1.jpg and /dev/null differ diff --git a/media/Double_Click2.jpg b/media/Double_Click2.jpg deleted file mode 100644 index 0b94ba07fa..0000000000 Binary files a/media/Double_Click2.jpg and /dev/null differ diff --git a/media/Double_Click3.jpg b/media/Double_Click3.jpg deleted file mode 100644 index 0b94ba07fa..0000000000 Binary files a/media/Double_Click3.jpg and /dev/null differ diff --git a/media/My_Lists1.jpg b/media/My_Lists1.jpg deleted file mode 100644 index d0eded2bd5..0000000000 Binary files a/media/My_Lists1.jpg and /dev/null differ diff --git a/media/My_Lists3.jpg b/media/My_Lists3.jpg deleted file mode 100644 index b3fdf1fb1a..0000000000 Binary files a/media/My_Lists3.jpg and /dev/null differ diff --git a/media/My_Lists4.jpg b/media/My_Lists4.jpg deleted file mode 100644 index 97a22cb355..0000000000 Binary files a/media/My_Lists4.jpg and /dev/null differ diff --git a/media/My_Lists5.jpg b/media/My_Lists5.jpg deleted file mode 100644 index cc02d75b43..0000000000 Binary files a/media/My_Lists5.jpg and /dev/null differ diff --git a/media/My_Lists6.jpg b/media/My_Lists6.jpg deleted file mode 100644 index cb08f337a7..0000000000 Binary files a/media/My_Lists6.jpg and /dev/null differ diff --git a/media/My_Lists7.jpg b/media/My_Lists7.jpg deleted file mode 100644 index ac1645bc30..0000000000 Binary files a/media/My_Lists7.jpg and /dev/null differ diff --git a/media/New_Tab_Button1.jpg b/media/New_Tab_Button1.jpg deleted file mode 100644 index b2d261acae..0000000000 Binary files a/media/New_Tab_Button1.jpg and /dev/null differ diff --git a/media/Overlay_Existing_Record_via_Z39_50_Import1.jpg b/media/Overlay_Existing_Record_via_Z39_50_Import1.jpg deleted file mode 100644 index 33e96b56e1..0000000000 Binary files a/media/Overlay_Existing_Record_via_Z39_50_Import1.jpg and /dev/null differ diff --git a/media/Overlay_Existing_Record_via_Z39_50_Import2.jpg b/media/Overlay_Existing_Record_via_Z39_50_Import2.jpg deleted file mode 100644 index 32da4092cc..0000000000 Binary files a/media/Overlay_Existing_Record_via_Z39_50_Import2.jpg and /dev/null differ diff --git a/media/Overlay_Existing_Record_via_Z39_50_Import3.jpg b/media/Overlay_Existing_Record_via_Z39_50_Import3.jpg deleted file mode 100644 index e6b563b620..0000000000 Binary files a/media/Overlay_Existing_Record_via_Z39_50_Import3.jpg and /dev/null differ diff --git a/media/Overlay_Existing_Record_via_Z39_50_Import4.jpg b/media/Overlay_Existing_Record_via_Z39_50_Import4.jpg deleted file mode 100644 index bb6049bb87..0000000000 Binary files a/media/Overlay_Existing_Record_via_Z39_50_Import4.jpg and /dev/null differ diff --git a/media/Overlay_Existing_Record_via_Z39_50_Import5.jpg b/media/Overlay_Existing_Record_via_Z39_50_Import5.jpg deleted file mode 100644 index 96c2169d28..0000000000 Binary files a/media/Overlay_Existing_Record_via_Z39_50_Import5.jpg and /dev/null differ diff --git a/media/Overlay_Existing_Record_via_Z39_50_Import6.jpg b/media/Overlay_Existing_Record_via_Z39_50_Import6.jpg deleted file mode 100644 index 37b9a8ed15..0000000000 Binary files a/media/Overlay_Existing_Record_via_Z39_50_Import6.jpg and /dev/null differ diff --git a/media/Receive_Items_From_an_Invoice1.jpg b/media/Receive_Items_From_an_Invoice1.jpg deleted file mode 100644 index 120894cf1b..0000000000 Binary files a/media/Receive_Items_From_an_Invoice1.jpg and /dev/null differ diff --git a/media/Receive_Items_From_an_Invoice2.jpg b/media/Receive_Items_From_an_Invoice2.jpg deleted file mode 100644 index 266610b8c2..0000000000 Binary files a/media/Receive_Items_From_an_Invoice2.jpg and /dev/null differ diff --git a/media/Receive_Items_From_an_Invoice3.jpg b/media/Receive_Items_From_an_Invoice3.jpg deleted file mode 100644 index a9005da372..0000000000 Binary files a/media/Receive_Items_From_an_Invoice3.jpg and /dev/null differ diff --git a/media/Receive_Items_From_an_Invoice4.jpg b/media/Receive_Items_From_an_Invoice4.jpg deleted file mode 100644 index 60f7eb1043..0000000000 Binary files a/media/Receive_Items_From_an_Invoice4.jpg and /dev/null differ diff --git a/media/Receive_Items_From_an_Invoice5.jpg b/media/Receive_Items_From_an_Invoice5.jpg deleted file mode 100644 index bd9a45b7e5..0000000000 Binary files a/media/Receive_Items_From_an_Invoice5.jpg and /dev/null differ diff --git a/media/Receive_Items_From_an_Invoice6.jpg b/media/Receive_Items_From_an_Invoice6.jpg deleted file mode 100644 index 907f4f185e..0000000000 Binary files a/media/Receive_Items_From_an_Invoice6.jpg and /dev/null differ diff --git a/media/Receive_Items_From_an_Invoice7.jpg b/media/Receive_Items_From_an_Invoice7.jpg deleted file mode 100644 index 77785d506b..0000000000 Binary files a/media/Receive_Items_From_an_Invoice7.jpg and /dev/null differ diff --git a/media/Restrict_Z39_50_Sources_by_Permission_Group1.jpg b/media/Restrict_Z39_50_Sources_by_Permission_Group1.jpg deleted file mode 100644 index 7be1b6f554..0000000000 Binary files a/media/Restrict_Z39_50_Sources_by_Permission_Group1.jpg and /dev/null differ diff --git a/media/Restrict_Z39_50_Sources_by_Permission_Group2.jpg b/media/Restrict_Z39_50_Sources_by_Permission_Group2.jpg deleted file mode 100644 index 107f24bc0e..0000000000 Binary files a/media/Restrict_Z39_50_Sources_by_Permission_Group2.jpg and /dev/null differ diff --git a/media/Restrict_Z39_50_Sources_by_Permission_Group3.jpg b/media/Restrict_Z39_50_Sources_by_Permission_Group3.jpg deleted file mode 100644 index fd84093379..0000000000 Binary files a/media/Restrict_Z39_50_Sources_by_Permission_Group3.jpg and /dev/null differ diff --git a/media/SMS_Text_Messaging1.jpg b/media/SMS_Text_Messaging1.jpg deleted file mode 100644 index 6bbfa99e31..0000000000 Binary files a/media/SMS_Text_Messaging1.jpg and /dev/null differ diff --git a/media/SMS_Text_Messaging10.jpg b/media/SMS_Text_Messaging10.jpg deleted file mode 100644 index ec9da2715e..0000000000 Binary files a/media/SMS_Text_Messaging10.jpg and /dev/null differ diff --git a/media/SMS_Text_Messaging11.jpg b/media/SMS_Text_Messaging11.jpg deleted file mode 100644 index fea6a7098f..0000000000 Binary files a/media/SMS_Text_Messaging11.jpg and /dev/null differ diff --git a/media/SMS_Text_Messaging12.jpg b/media/SMS_Text_Messaging12.jpg deleted file mode 100644 index cf012f0ff4..0000000000 Binary files a/media/SMS_Text_Messaging12.jpg and /dev/null differ diff --git a/media/SMS_Text_Messaging13.jpg b/media/SMS_Text_Messaging13.jpg deleted file mode 100644 index 541fc26811..0000000000 Binary files a/media/SMS_Text_Messaging13.jpg and /dev/null differ diff --git a/media/SMS_Text_Messaging2.jpg b/media/SMS_Text_Messaging2.jpg deleted file mode 100644 index 81f1ba021c..0000000000 Binary files a/media/SMS_Text_Messaging2.jpg and /dev/null differ diff --git a/media/SMS_Text_Messaging3.jpg b/media/SMS_Text_Messaging3.jpg deleted file mode 100644 index f03f42e5a9..0000000000 Binary files a/media/SMS_Text_Messaging3.jpg and /dev/null differ diff --git a/media/SMS_Text_Messaging4.jpg b/media/SMS_Text_Messaging4.jpg deleted file mode 100644 index ef001919d4..0000000000 Binary files a/media/SMS_Text_Messaging4.jpg and /dev/null differ diff --git a/media/SMS_Text_Messaging5.jpg b/media/SMS_Text_Messaging5.jpg deleted file mode 100644 index 94b7913afc..0000000000 Binary files a/media/SMS_Text_Messaging5.jpg and /dev/null differ diff --git a/media/SMS_Text_Messaging6.jpg b/media/SMS_Text_Messaging6.jpg deleted file mode 100644 index e8ecc432c5..0000000000 Binary files a/media/SMS_Text_Messaging6.jpg and /dev/null differ diff --git a/media/SMS_Text_Messaging7.jpg b/media/SMS_Text_Messaging7.jpg deleted file mode 100644 index cf012f0ff4..0000000000 Binary files a/media/SMS_Text_Messaging7.jpg and /dev/null differ diff --git a/media/SMS_Text_Messaging8.jpg b/media/SMS_Text_Messaging8.jpg deleted file mode 100644 index 17fceac30b..0000000000 Binary files a/media/SMS_Text_Messaging8.jpg and /dev/null differ diff --git a/media/SMS_Text_Messaging9.jpg b/media/SMS_Text_Messaging9.jpg deleted file mode 100644 index a86fa150d5..0000000000 Binary files a/media/SMS_Text_Messaging9.jpg and /dev/null differ diff --git a/media/Saved_Catalog_Searches_2_21.jpg b/media/Saved_Catalog_Searches_2_21.jpg deleted file mode 100644 index ce22623f15..0000000000 Binary files a/media/Saved_Catalog_Searches_2_21.jpg and /dev/null differ diff --git a/media/Saved_Catalog_Searches_2_21.jpg.1 b/media/Saved_Catalog_Searches_2_21.jpg.1 deleted file mode 100644 index ce22623f15..0000000000 Binary files a/media/Saved_Catalog_Searches_2_21.jpg.1 and /dev/null differ diff --git a/media/Saved_Catalog_Searches_2_22.jpg b/media/Saved_Catalog_Searches_2_22.jpg deleted file mode 100644 index 426e3994bf..0000000000 Binary files a/media/Saved_Catalog_Searches_2_22.jpg and /dev/null differ diff --git a/media/Saved_Catalog_Searches_2_22.jpg.1 b/media/Saved_Catalog_Searches_2_22.jpg.1 deleted file mode 100644 index 426e3994bf..0000000000 Binary files a/media/Saved_Catalog_Searches_2_22.jpg.1 and /dev/null differ diff --git a/media/Search_Results1.jpg b/media/Search_Results1.jpg deleted file mode 100644 index a41532156c..0000000000 Binary files a/media/Search_Results1.jpg and /dev/null differ diff --git a/media/Sorting_Columns2.jpg b/media/Sorting_Columns2.jpg deleted file mode 100644 index 6510ea4aa7..0000000000 Binary files a/media/Sorting_Columns2.jpg and /dev/null differ diff --git a/media/Sorting_Columns3.jpg b/media/Sorting_Columns3.jpg deleted file mode 100644 index 57ba1bdfa4..0000000000 Binary files a/media/Sorting_Columns3.jpg and /dev/null differ diff --git a/media/Sorting_Columns3.jpg.1 b/media/Sorting_Columns3.jpg.1 deleted file mode 100644 index 57ba1bdfa4..0000000000 Binary files a/media/Sorting_Columns3.jpg.1 and /dev/null differ diff --git a/media/Sorting_Columns4.jpg b/media/Sorting_Columns4.jpg deleted file mode 100644 index 9d38c39241..0000000000 Binary files a/media/Sorting_Columns4.jpg and /dev/null differ diff --git a/media/Sorting_Columns5.jpg b/media/Sorting_Columns5.jpg deleted file mode 100644 index 98d573a3ee..0000000000 Binary files a/media/Sorting_Columns5.jpg and /dev/null differ diff --git a/media/Target_Pickup_Lib1.jpg b/media/Target_Pickup_Lib1.jpg deleted file mode 100644 index bbb7c01555..0000000000 Binary files a/media/Target_Pickup_Lib1.jpg and /dev/null differ diff --git a/media/Target_Pickup_Lib2.jpg b/media/Target_Pickup_Lib2.jpg deleted file mode 100644 index bbb7c01555..0000000000 Binary files a/media/Target_Pickup_Lib2.jpg and /dev/null differ diff --git a/media/User_Activity_Types1A.jpg b/media/User_Activity_Types1A.jpg deleted file mode 100644 index 69d6ab4d39..0000000000 Binary files a/media/User_Activity_Types1A.jpg and /dev/null differ diff --git a/media/User_Activity_Types2A.jpg b/media/User_Activity_Types2A.jpg deleted file mode 100644 index 63048ca1a6..0000000000 Binary files a/media/User_Activity_Types2A.jpg and /dev/null differ diff --git a/media/Vandelay_Integration_into_Acquisitions1.jpg b/media/Vandelay_Integration_into_Acquisitions1.jpg deleted file mode 100644 index 909e14e9ee..0000000000 Binary files a/media/Vandelay_Integration_into_Acquisitions1.jpg and /dev/null differ diff --git a/media/Vandelay_Integration_into_Acquisitions2.jpg b/media/Vandelay_Integration_into_Acquisitions2.jpg deleted file mode 100644 index afc195b847..0000000000 Binary files a/media/Vandelay_Integration_into_Acquisitions2.jpg and /dev/null differ diff --git a/media/Vandelay_Integration_into_Acquisitions3.jpg b/media/Vandelay_Integration_into_Acquisitions3.jpg deleted file mode 100644 index 1190fb1dd5..0000000000 Binary files a/media/Vandelay_Integration_into_Acquisitions3.jpg and /dev/null differ diff --git a/media/Vandelay_Integration_into_Acquisitions4.jpg b/media/Vandelay_Integration_into_Acquisitions4.jpg deleted file mode 100644 index 7f1c6a7135..0000000000 Binary files a/media/Vandelay_Integration_into_Acquisitions4.jpg and /dev/null differ diff --git a/media/Vandelay_Integration_into_Acquisitions5.jpg b/media/Vandelay_Integration_into_Acquisitions5.jpg deleted file mode 100644 index fd072cae6a..0000000000 Binary files a/media/Vandelay_Integration_into_Acquisitions5.jpg and /dev/null differ diff --git a/media/Vandelay_Integration_into_Acquisitions6.jpg b/media/Vandelay_Integration_into_Acquisitions6.jpg deleted file mode 100644 index 90dde3c635..0000000000 Binary files a/media/Vandelay_Integration_into_Acquisitions6.jpg and /dev/null differ diff --git a/media/acq_activate.png b/media/acq_activate.png deleted file mode 100644 index 3ee9088adc..0000000000 Binary files a/media/acq_activate.png and /dev/null differ diff --git a/media/acq_apply_claim_policy.png b/media/acq_apply_claim_policy.png deleted file mode 100644 index 6b7dd93897..0000000000 Binary files a/media/acq_apply_claim_policy.png and /dev/null differ diff --git a/media/acq_brief_record-2.png b/media/acq_brief_record-2.png deleted file mode 100644 index 264213ce31..0000000000 Binary files a/media/acq_brief_record-2.png and /dev/null differ diff --git a/media/acq_brief_record.png b/media/acq_brief_record.png deleted file mode 100644 index 25fdefe7ba..0000000000 Binary files a/media/acq_brief_record.png and /dev/null differ diff --git a/media/acq_cancel_copy.png b/media/acq_cancel_copy.png deleted file mode 100644 index 2ed7dc1651..0000000000 Binary files a/media/acq_cancel_copy.png and /dev/null differ diff --git a/media/acq_cancel_line_items.png b/media/acq_cancel_line_items.png deleted file mode 100644 index 541436346b..0000000000 Binary files a/media/acq_cancel_line_items.png and /dev/null differ diff --git a/media/acq_claim_item-2.png b/media/acq_claim_item-2.png deleted file mode 100644 index 453f02c112..0000000000 Binary files a/media/acq_claim_item-2.png and /dev/null differ diff --git a/media/acq_claim_item-3.png b/media/acq_claim_item-3.png deleted file mode 100644 index 79bbe07811..0000000000 Binary files a/media/acq_claim_item-3.png and /dev/null differ diff --git a/media/acq_claim_item-4.png b/media/acq_claim_item-4.png deleted file mode 100644 index ada7330467..0000000000 Binary files a/media/acq_claim_item-4.png and /dev/null differ diff --git a/media/acq_claim_item-5.png b/media/acq_claim_item-5.png deleted file mode 100644 index e1729e2606..0000000000 Binary files a/media/acq_claim_item-5.png and /dev/null differ diff --git a/media/acq_claim_item.png b/media/acq_claim_item.png deleted file mode 100644 index 540605f6b7..0000000000 Binary files a/media/acq_claim_item.png and /dev/null differ diff --git a/media/acq_export_list.png b/media/acq_export_list.png deleted file mode 100644 index f5c531704d..0000000000 Binary files a/media/acq_export_list.png and /dev/null differ diff --git a/media/acq_funds-2.png b/media/acq_funds-2.png deleted file mode 100644 index 259edaa3e2..0000000000 Binary files a/media/acq_funds-2.png and /dev/null differ diff --git a/media/acq_funds.png b/media/acq_funds.png deleted file mode 100644 index ad408031dc..0000000000 Binary files a/media/acq_funds.png and /dev/null differ diff --git a/media/acq_invoice_blanket.png b/media/acq_invoice_blanket.png deleted file mode 100644 index 227727ee2b..0000000000 Binary files a/media/acq_invoice_blanket.png and /dev/null differ diff --git a/media/acq_invoice_line_items.png b/media/acq_invoice_line_items.png deleted file mode 100644 index 0a572f9b4e..0000000000 Binary files a/media/acq_invoice_line_items.png and /dev/null differ diff --git a/media/acq_invoice_link.png b/media/acq_invoice_link.png deleted file mode 100644 index 6bc7c1b3dd..0000000000 Binary files a/media/acq_invoice_link.png and /dev/null differ diff --git a/media/acq_invoice_purchase_order.png b/media/acq_invoice_purchase_order.png deleted file mode 100644 index 0a572f9b4e..0000000000 Binary files a/media/acq_invoice_purchase_order.png and /dev/null differ diff --git a/media/acq_invoice_view-2.png b/media/acq_invoice_view-2.png deleted file mode 100644 index abac114908..0000000000 Binary files a/media/acq_invoice_view-2.png and /dev/null differ diff --git a/media/acq_invoice_view.png b/media/acq_invoice_view.png deleted file mode 100644 index 616380cee3..0000000000 Binary files a/media/acq_invoice_view.png and /dev/null differ diff --git a/media/acq_line_items_add_copies-2.png b/media/acq_line_items_add_copies-2.png deleted file mode 100644 index 8b1178d2cb..0000000000 Binary files a/media/acq_line_items_add_copies-2.png and /dev/null differ diff --git a/media/acq_line_items_add_copies-3.png b/media/acq_line_items_add_copies-3.png deleted file mode 100644 index ee9a6d58e2..0000000000 Binary files a/media/acq_line_items_add_copies-3.png and /dev/null differ diff --git a/media/acq_line_items_add_copies.png b/media/acq_line_items_add_copies.png deleted file mode 100644 index 699a70a93d..0000000000 Binary files a/media/acq_line_items_add_copies.png and /dev/null differ diff --git a/media/acq_line_items_add_notes.png b/media/acq_line_items_add_notes.png deleted file mode 100644 index f4e580ba94..0000000000 Binary files a/media/acq_line_items_add_notes.png and /dev/null differ diff --git a/media/acq_line_items_alerts-2.png b/media/acq_line_items_alerts-2.png deleted file mode 100644 index 7bc899c4be..0000000000 Binary files a/media/acq_line_items_alerts-2.png and /dev/null differ diff --git a/media/acq_line_items_alerts.png b/media/acq_line_items_alerts.png deleted file mode 100644 index 15003be799..0000000000 Binary files a/media/acq_line_items_alerts.png and /dev/null differ diff --git a/media/acq_line_items_link-2.png b/media/acq_line_items_link-2.png deleted file mode 100644 index d0ef1936f9..0000000000 Binary files a/media/acq_line_items_link-2.png and /dev/null differ diff --git a/media/acq_line_items_link.png b/media/acq_line_items_link.png deleted file mode 100644 index 11c1cd115b..0000000000 Binary files a/media/acq_line_items_link.png and /dev/null differ diff --git a/media/acq_line_items_update_barcodes.png b/media/acq_line_items_update_barcodes.png deleted file mode 100644 index b95368d28c..0000000000 Binary files a/media/acq_line_items_update_barcodes.png and /dev/null differ diff --git a/media/acq_line_items_view_history.png b/media/acq_line_items_view_history.png deleted file mode 100644 index b6a03abb84..0000000000 Binary files a/media/acq_line_items_view_history.png and /dev/null differ diff --git a/media/acq_line_items_worksheet.png b/media/acq_line_items_worksheet.png deleted file mode 100644 index 54e465b893..0000000000 Binary files a/media/acq_line_items_worksheet.png and /dev/null differ diff --git a/media/acq_load_records.png b/media/acq_load_records.png deleted file mode 100644 index 5b73687d73..0000000000 Binary files a/media/acq_load_records.png and /dev/null differ diff --git a/media/acq_marc_search-2.png b/media/acq_marc_search-2.png deleted file mode 100644 index a317bf0f7a..0000000000 Binary files a/media/acq_marc_search-2.png and /dev/null differ diff --git a/media/acq_marc_search.png b/media/acq_marc_search.png deleted file mode 100644 index 391ae435a2..0000000000 Binary files a/media/acq_marc_search.png and /dev/null differ diff --git a/media/acq_purchase_order_add_charges.png b/media/acq_purchase_order_add_charges.png deleted file mode 100644 index 3ee9088adc..0000000000 Binary files a/media/acq_purchase_order_add_charges.png and /dev/null differ diff --git a/media/acq_purchase_order_add_note.png b/media/acq_purchase_order_add_note.png deleted file mode 100644 index e3d9e059af..0000000000 Binary files a/media/acq_purchase_order_add_note.png and /dev/null differ diff --git a/media/acq_purchase_order_create.png b/media/acq_purchase_order_create.png deleted file mode 100644 index 71704bc09f..0000000000 Binary files a/media/acq_purchase_order_create.png and /dev/null differ diff --git a/media/acq_purchase_order_history.png b/media/acq_purchase_order_history.png deleted file mode 100644 index 8f4c5fe466..0000000000 Binary files a/media/acq_purchase_order_history.png and /dev/null differ diff --git a/media/acq_purchase_order_name.png b/media/acq_purchase_order_name.png deleted file mode 100644 index 6eaac45816..0000000000 Binary files a/media/acq_purchase_order_name.png and /dev/null differ diff --git a/media/acq_purchase_order_print.png b/media/acq_purchase_order_print.png deleted file mode 100644 index d4a14feb5c..0000000000 Binary files a/media/acq_purchase_order_print.png and /dev/null differ diff --git a/media/acq_purchase_order_split-2.png b/media/acq_purchase_order_split-2.png deleted file mode 100644 index a1fa5e3fd1..0000000000 Binary files a/media/acq_purchase_order_split-2.png and /dev/null differ diff --git a/media/acq_purchase_order_split.png b/media/acq_purchase_order_split.png deleted file mode 100644 index b47702282e..0000000000 Binary files a/media/acq_purchase_order_split.png and /dev/null differ diff --git a/media/acq_purchase_order_view-2.png b/media/acq_purchase_order_view-2.png deleted file mode 100644 index 81465c80a9..0000000000 Binary files a/media/acq_purchase_order_view-2.png and /dev/null differ diff --git a/media/acq_purchase_order_view.png b/media/acq_purchase_order_view.png deleted file mode 100644 index 2bb5c94754..0000000000 Binary files a/media/acq_purchase_order_view.png and /dev/null differ diff --git a/media/acq_search.png b/media/acq_search.png deleted file mode 100644 index 2bb5e85f5e..0000000000 Binary files a/media/acq_search.png and /dev/null differ diff --git a/media/acq_selection_clone.png b/media/acq_selection_clone.png deleted file mode 100644 index d4183b5cb1..0000000000 Binary files a/media/acq_selection_clone.png and /dev/null differ diff --git a/media/acq_selection_create.png b/media/acq_selection_create.png deleted file mode 100644 index f248d0ae9e..0000000000 Binary files a/media/acq_selection_create.png and /dev/null differ diff --git a/media/acq_selection_mark_ready-2.png b/media/acq_selection_mark_ready-2.png deleted file mode 100644 index 1452cae29d..0000000000 Binary files a/media/acq_selection_mark_ready-2.png and /dev/null differ diff --git a/media/acq_selection_mark_ready.png b/media/acq_selection_mark_ready.png deleted file mode 100644 index 3eb558659e..0000000000 Binary files a/media/acq_selection_mark_ready.png and /dev/null differ diff --git a/media/acq_selection_merge.png b/media/acq_selection_merge.png deleted file mode 100644 index e1f740c246..0000000000 Binary files a/media/acq_selection_merge.png and /dev/null differ diff --git a/media/acq_workflow.jpg b/media/acq_workflow.jpg deleted file mode 100644 index 1143cfa017..0000000000 Binary files a/media/acq_workflow.jpg and /dev/null differ diff --git a/media/add_holdings-1.png b/media/add_holdings-1.png deleted file mode 100644 index 07baaa0192..0000000000 Binary files a/media/add_holdings-1.png and /dev/null differ diff --git a/media/add_holdings-2.png b/media/add_holdings-2.png deleted file mode 100644 index 4176df14ef..0000000000 Binary files a/media/add_holdings-2.png and /dev/null differ diff --git a/media/add_holdings-3.png b/media/add_holdings-3.png deleted file mode 100644 index a847eb6afc..0000000000 Binary files a/media/add_holdings-3.png and /dev/null differ diff --git a/media/add_holdings-4.png b/media/add_holdings-4.png deleted file mode 100644 index 6359f1d0f1..0000000000 Binary files a/media/add_holdings-4.png and /dev/null differ diff --git a/media/add_holdings-5.png b/media/add_holdings-5.png deleted file mode 100644 index 3a25250aec..0000000000 Binary files a/media/add_holdings-5.png and /dev/null differ diff --git a/media/application-pdf.png b/media/application-pdf.png deleted file mode 100644 index 6fdfae9930..0000000000 Binary files a/media/application-pdf.png and /dev/null differ diff --git a/media/ascv-distr.jpg b/media/ascv-distr.jpg deleted file mode 100644 index 77c151e215..0000000000 Binary files a/media/ascv-distr.jpg and /dev/null differ diff --git a/media/ascv-issues.jpg b/media/ascv-issues.jpg deleted file mode 100644 index ab6d13c945..0000000000 Binary files a/media/ascv-issues.jpg and /dev/null differ diff --git a/media/ascv-sub.jpg b/media/ascv-sub.jpg deleted file mode 100644 index a44bdbbba6..0000000000 Binary files a/media/ascv-sub.jpg and /dev/null differ diff --git a/media/backdate_checkin.png b/media/backdate_checkin.png deleted file mode 100644 index ae0ef539f6..0000000000 Binary files a/media/backdate_checkin.png and /dev/null differ diff --git a/media/backdate_post_checkin.png b/media/backdate_post_checkin.png deleted file mode 100644 index 03b54a92cc..0000000000 Binary files a/media/backdate_post_checkin.png and /dev/null differ diff --git a/media/backdate_post_date.png b/media/backdate_post_date.png deleted file mode 100644 index 501483588c..0000000000 Binary files a/media/backdate_post_date.png and /dev/null differ diff --git a/media/backdate_red.png b/media/backdate_red.png deleted file mode 100644 index 5d7c6c9c26..0000000000 Binary files a/media/backdate_red.png and /dev/null differ diff --git a/media/bills-1.png b/media/bills-1.png deleted file mode 100644 index aca68919ed..0000000000 Binary files a/media/bills-1.png and /dev/null differ diff --git a/media/bills-10.png b/media/bills-10.png deleted file mode 100644 index 1a9b1353e3..0000000000 Binary files a/media/bills-10.png and /dev/null differ diff --git a/media/bills-11.png b/media/bills-11.png deleted file mode 100644 index 5e6eec9df9..0000000000 Binary files a/media/bills-11.png and /dev/null differ diff --git a/media/bills-12.png b/media/bills-12.png deleted file mode 100644 index 2671a2a279..0000000000 Binary files a/media/bills-12.png and /dev/null differ diff --git a/media/bills-13.png b/media/bills-13.png deleted file mode 100644 index c6043204b2..0000000000 Binary files a/media/bills-13.png and /dev/null differ diff --git a/media/bills-14.png b/media/bills-14.png deleted file mode 100644 index 9ef43d2657..0000000000 Binary files a/media/bills-14.png and /dev/null differ diff --git a/media/bills-15.png b/media/bills-15.png deleted file mode 100644 index e176d43ddf..0000000000 Binary files a/media/bills-15.png and /dev/null differ diff --git a/media/bills-16.png b/media/bills-16.png deleted file mode 100644 index 2b4b29f901..0000000000 Binary files a/media/bills-16.png and /dev/null differ diff --git a/media/bills-17.png b/media/bills-17.png deleted file mode 100644 index fff134b035..0000000000 Binary files a/media/bills-17.png and /dev/null differ diff --git a/media/bills-18.png b/media/bills-18.png deleted file mode 100644 index f38bec473e..0000000000 Binary files a/media/bills-18.png and /dev/null differ diff --git a/media/bills-19.png b/media/bills-19.png deleted file mode 100644 index cf455f2b92..0000000000 Binary files a/media/bills-19.png and /dev/null differ diff --git a/media/bills-2.png b/media/bills-2.png deleted file mode 100644 index 242ff2db11..0000000000 Binary files a/media/bills-2.png and /dev/null differ diff --git a/media/bills-20.png b/media/bills-20.png deleted file mode 100644 index ca4b84c3d0..0000000000 Binary files a/media/bills-20.png and /dev/null differ diff --git a/media/bills-3.png b/media/bills-3.png deleted file mode 100644 index ac194f860f..0000000000 Binary files a/media/bills-3.png and /dev/null differ diff --git a/media/bills-4.png b/media/bills-4.png deleted file mode 100644 index 74e2d7250b..0000000000 Binary files a/media/bills-4.png and /dev/null differ diff --git a/media/bills-5.png b/media/bills-5.png deleted file mode 100644 index ac4c9917b2..0000000000 Binary files a/media/bills-5.png and /dev/null differ diff --git a/media/bills-6.png b/media/bills-6.png deleted file mode 100644 index 4be2f89a69..0000000000 Binary files a/media/bills-6.png and /dev/null differ diff --git a/media/bills-7.png b/media/bills-7.png deleted file mode 100644 index 2d7b5b0d11..0000000000 Binary files a/media/bills-7.png and /dev/null differ diff --git a/media/bills-8.png b/media/bills-8.png deleted file mode 100644 index bbcb905e7a..0000000000 Binary files a/media/bills-8.png and /dev/null differ diff --git a/media/bills-9.png b/media/bills-9.png deleted file mode 100644 index edbb56605b..0000000000 Binary files a/media/bills-9.png and /dev/null differ diff --git a/media/booking-cancel-1.png b/media/booking-cancel-1.png deleted file mode 100644 index 767d64c89c..0000000000 Binary files a/media/booking-cancel-1.png and /dev/null differ diff --git a/media/booking-cancel-2.png b/media/booking-cancel-2.png deleted file mode 100644 index 3ba68d4466..0000000000 Binary files a/media/booking-cancel-2.png and /dev/null differ diff --git a/media/booking-cancel-3.png b/media/booking-cancel-3.png deleted file mode 100644 index 0f3949bd35..0000000000 Binary files a/media/booking-cancel-3.png and /dev/null differ diff --git a/media/booking-cancel-4.png b/media/booking-cancel-4.png deleted file mode 100644 index 0f3949bd35..0000000000 Binary files a/media/booking-cancel-4.png and /dev/null differ diff --git a/media/booking-capture-1.png b/media/booking-capture-1.png deleted file mode 100644 index 5c95759673..0000000000 Binary files a/media/booking-capture-1.png and /dev/null differ diff --git a/media/booking-capture-2.png b/media/booking-capture-2.png deleted file mode 100644 index 1ed25bc258..0000000000 Binary files a/media/booking-capture-2.png and /dev/null differ diff --git a/media/booking-capture-3.png b/media/booking-capture-3.png deleted file mode 100644 index 2de6c8a5eb..0000000000 Binary files a/media/booking-capture-3.png and /dev/null differ diff --git a/media/booking-create-1.png b/media/booking-create-1.png deleted file mode 100644 index a9aa9d4791..0000000000 Binary files a/media/booking-create-1.png and /dev/null differ diff --git a/media/booking-create-2.png b/media/booking-create-2.png deleted file mode 100644 index 5942214d5a..0000000000 Binary files a/media/booking-create-2.png and /dev/null differ diff --git a/media/booking-create-3.png b/media/booking-create-3.png deleted file mode 100644 index e0f0769cdd..0000000000 Binary files a/media/booking-create-3.png and /dev/null differ diff --git a/media/booking-create-4.png b/media/booking-create-4.png deleted file mode 100644 index d48499b0dc..0000000000 Binary files a/media/booking-create-4.png and /dev/null differ diff --git a/media/booking-create-5.png b/media/booking-create-5.png deleted file mode 100644 index ba4de889db..0000000000 Binary files a/media/booking-create-5.png and /dev/null differ diff --git a/media/booking-create-6.png b/media/booking-create-6.png deleted file mode 100644 index a25176e234..0000000000 Binary files a/media/booking-create-6.png and /dev/null differ diff --git a/media/booking-create-7.png b/media/booking-create-7.png deleted file mode 100644 index dda012071a..0000000000 Binary files a/media/booking-create-7.png and /dev/null differ diff --git a/media/booking-create-8.png b/media/booking-create-8.png deleted file mode 100644 index ce1de3e1db..0000000000 Binary files a/media/booking-create-8.png and /dev/null differ diff --git a/media/booking-create-9.png b/media/booking-create-9.png deleted file mode 100644 index ce1de3e1db..0000000000 Binary files a/media/booking-create-9.png and /dev/null differ diff --git a/media/booking-create-bookable-1.png b/media/booking-create-bookable-1.png deleted file mode 100644 index 7ddded0c87..0000000000 Binary files a/media/booking-create-bookable-1.png and /dev/null differ diff --git a/media/booking-create-bookable-2.png b/media/booking-create-bookable-2.png deleted file mode 100644 index df9a3a47b7..0000000000 Binary files a/media/booking-create-bookable-2.png and /dev/null differ diff --git a/media/booking-create-bookable-3.png b/media/booking-create-bookable-3.png deleted file mode 100644 index 49ed80173d..0000000000 Binary files a/media/booking-create-bookable-3.png and /dev/null differ diff --git a/media/booking-create-bookable-4.png b/media/booking-create-bookable-4.png deleted file mode 100644 index 6c7128d649..0000000000 Binary files a/media/booking-create-bookable-4.png and /dev/null differ diff --git a/media/booking-create-bookable-5.png b/media/booking-create-bookable-5.png deleted file mode 100644 index c501d47cf3..0000000000 Binary files a/media/booking-create-bookable-5.png and /dev/null differ diff --git a/media/booking-create-bookable-6.png b/media/booking-create-bookable-6.png deleted file mode 100644 index 2261a9d6a5..0000000000 Binary files a/media/booking-create-bookable-6.png and /dev/null differ diff --git a/media/booking-create-module-1.png b/media/booking-create-module-1.png deleted file mode 100644 index a2804c8bcb..0000000000 Binary files a/media/booking-create-module-1.png and /dev/null differ diff --git a/media/booking-create-module-2.png b/media/booking-create-module-2.png deleted file mode 100644 index 92f093599e..0000000000 Binary files a/media/booking-create-module-2.png and /dev/null differ diff --git a/media/booking-create-module-3.png b/media/booking-create-module-3.png deleted file mode 100644 index b031138983..0000000000 Binary files a/media/booking-create-module-3.png and /dev/null differ diff --git a/media/booking-create-module-4.png b/media/booking-create-module-4.png deleted file mode 100644 index 32981a7e7c..0000000000 Binary files a/media/booking-create-module-4.png and /dev/null differ diff --git a/media/booking-create-resourcetype-1.png b/media/booking-create-resourcetype-1.png deleted file mode 100644 index aa11630c2c..0000000000 Binary files a/media/booking-create-resourcetype-1.png and /dev/null differ diff --git a/media/booking-create-resourcetype-2.png b/media/booking-create-resourcetype-2.png deleted file mode 100644 index ff517c5e87..0000000000 Binary files a/media/booking-create-resourcetype-2.png and /dev/null differ diff --git a/media/booking-create-resourcetype-3.png b/media/booking-create-resourcetype-3.png deleted file mode 100644 index d7a7e384f9..0000000000 Binary files a/media/booking-create-resourcetype-3.png and /dev/null differ diff --git a/media/booking-create-resourcetype-4.png b/media/booking-create-resourcetype-4.png deleted file mode 100644 index 0f7317e495..0000000000 Binary files a/media/booking-create-resourcetype-4.png and /dev/null differ diff --git a/media/booking-create-resourcetype-5.png b/media/booking-create-resourcetype-5.png deleted file mode 100644 index 784d95ad00..0000000000 Binary files a/media/booking-create-resourcetype-5.png and /dev/null differ diff --git a/media/booking-pickup-1.png b/media/booking-pickup-1.png deleted file mode 100644 index 30c94517eb..0000000000 Binary files a/media/booking-pickup-1.png and /dev/null differ diff --git a/media/booking-pickup-2.png b/media/booking-pickup-2.png deleted file mode 100644 index bcae061383..0000000000 Binary files a/media/booking-pickup-2.png and /dev/null differ diff --git a/media/booking-pickup-3.png b/media/booking-pickup-3.png deleted file mode 100644 index afe3857833..0000000000 Binary files a/media/booking-pickup-3.png and /dev/null differ diff --git a/media/booking-pickup-module-1.png b/media/booking-pickup-module-1.png deleted file mode 100644 index 215ad7616f..0000000000 Binary files a/media/booking-pickup-module-1.png and /dev/null differ diff --git a/media/booking-pull-1.png b/media/booking-pull-1.png deleted file mode 100644 index 0dcdb8267c..0000000000 Binary files a/media/booking-pull-1.png and /dev/null differ diff --git a/media/booking-pull-2.png b/media/booking-pull-2.png deleted file mode 100644 index a2601f7cf4..0000000000 Binary files a/media/booking-pull-2.png and /dev/null differ diff --git a/media/booking-pull-3.png b/media/booking-pull-3.png deleted file mode 100644 index a0156bea44..0000000000 Binary files a/media/booking-pull-3.png and /dev/null differ diff --git a/media/booking-return-2.png b/media/booking-return-2.png deleted file mode 100644 index 503180cd91..0000000000 Binary files a/media/booking-return-2.png and /dev/null differ diff --git a/media/booking-return-module-1.png b/media/booking-return-module-1.png deleted file mode 100644 index f65b164b90..0000000000 Binary files a/media/booking-return-module-1.png and /dev/null differ diff --git a/media/booking-return-module-2.png b/media/booking-return-module-2.png deleted file mode 100644 index 4c40bb6f97..0000000000 Binary files a/media/booking-return-module-2.png and /dev/null differ diff --git a/media/booking-return-module-4.png b/media/booking-return-module-4.png deleted file mode 100644 index fbbca51429..0000000000 Binary files a/media/booking-return-module-4.png and /dev/null differ diff --git a/media/cap-wiz-cal.jpg b/media/cap-wiz-cal.jpg deleted file mode 100644 index e28b592eda..0000000000 Binary files a/media/cap-wiz-cal.jpg and /dev/null differ diff --git a/media/cap-wiz-chan.jpg b/media/cap-wiz-chan.jpg deleted file mode 100644 index f50eb0cf88..0000000000 Binary files a/media/cap-wiz-chan.jpg and /dev/null differ diff --git a/media/cap-wiz-chron.jpg b/media/cap-wiz-chron.jpg deleted file mode 100644 index 27b955b68d..0000000000 Binary files a/media/cap-wiz-chron.jpg and /dev/null differ diff --git a/media/cap-wiz-freq.jpg b/media/cap-wiz-freq.jpg deleted file mode 100644 index 83b0f9dade..0000000000 Binary files a/media/cap-wiz-freq.jpg and /dev/null differ diff --git a/media/cap-wiz-num.jpg b/media/cap-wiz-num.jpg deleted file mode 100644 index e1aa286dd7..0000000000 Binary files a/media/cap-wiz-num.jpg and /dev/null differ diff --git a/media/catalogue-10.png b/media/catalogue-10.png deleted file mode 100644 index 41c3be1a64..0000000000 Binary files a/media/catalogue-10.png and /dev/null differ diff --git a/media/catalogue-11.png b/media/catalogue-11.png deleted file mode 100644 index d51f45bf70..0000000000 Binary files a/media/catalogue-11.png and /dev/null differ diff --git a/media/catalogue-3.png b/media/catalogue-3.png deleted file mode 100644 index f8080a9085..0000000000 Binary files a/media/catalogue-3.png and /dev/null differ diff --git a/media/catalogue-4.png b/media/catalogue-4.png deleted file mode 100644 index 17352789eb..0000000000 Binary files a/media/catalogue-4.png and /dev/null differ diff --git a/media/catalogue-5.png b/media/catalogue-5.png deleted file mode 100644 index 2f5e5ea562..0000000000 Binary files a/media/catalogue-5.png and /dev/null differ diff --git a/media/catalogue-6.png b/media/catalogue-6.png deleted file mode 100644 index 9ed436228d..0000000000 Binary files a/media/catalogue-6.png and /dev/null differ diff --git a/media/catalogue-7.png b/media/catalogue-7.png deleted file mode 100644 index 4aaa0c27e6..0000000000 Binary files a/media/catalogue-7.png and /dev/null differ diff --git a/media/catalogue-8.png b/media/catalogue-8.png deleted file mode 100644 index 1a952ebb33..0000000000 Binary files a/media/catalogue-8.png and /dev/null differ diff --git a/media/catalogue-9.png b/media/catalogue-9.png deleted file mode 100644 index a32192628b..0000000000 Binary files a/media/catalogue-9.png and /dev/null differ diff --git a/media/caution.png b/media/caution.png deleted file mode 100644 index cdc6568091..0000000000 Binary files a/media/caution.png and /dev/null differ diff --git a/media/ccbysa.png b/media/ccbysa.png deleted file mode 100644 index f0a944e0b8..0000000000 Binary files a/media/ccbysa.png and /dev/null differ diff --git a/media/check_in_menu.png b/media/check_in_menu.png deleted file mode 100644 index d04d859850..0000000000 Binary files a/media/check_in_menu.png and /dev/null differ diff --git a/media/checkin_barcode.png b/media/checkin_barcode.png deleted file mode 100644 index a7b7d1d1c4..0000000000 Binary files a/media/checkin_barcode.png and /dev/null differ diff --git a/media/checkin_options.png b/media/checkin_options.png deleted file mode 100644 index be3360f826..0000000000 Binary files a/media/checkin_options.png and /dev/null differ diff --git a/media/checkout_item_barcode.png b/media/checkout_item_barcode.png deleted file mode 100644 index c625a90315..0000000000 Binary files a/media/checkout_item_barcode.png and /dev/null differ diff --git a/media/checkout_menu.png b/media/checkout_menu.png deleted file mode 100644 index 029bf36bc5..0000000000 Binary files a/media/checkout_menu.png and /dev/null differ diff --git a/media/circulation-1.png b/media/circulation-1.png deleted file mode 100644 index 01d1b0748f..0000000000 Binary files a/media/circulation-1.png and /dev/null differ diff --git a/media/circulation-10.png b/media/circulation-10.png deleted file mode 100644 index bc15935fc1..0000000000 Binary files a/media/circulation-10.png and /dev/null differ diff --git a/media/circulation-11.png b/media/circulation-11.png deleted file mode 100644 index 9fad77c5a6..0000000000 Binary files a/media/circulation-11.png and /dev/null differ diff --git a/media/circulation-12.png b/media/circulation-12.png deleted file mode 100644 index d43881fca8..0000000000 Binary files a/media/circulation-12.png and /dev/null differ diff --git a/media/circulation-13.png b/media/circulation-13.png deleted file mode 100644 index ba6edf5a1d..0000000000 Binary files a/media/circulation-13.png and /dev/null differ diff --git a/media/circulation-14.png b/media/circulation-14.png deleted file mode 100644 index 1af7e6acf8..0000000000 Binary files a/media/circulation-14.png and /dev/null differ diff --git a/media/circulation-15.png b/media/circulation-15.png deleted file mode 100644 index 35484a3768..0000000000 Binary files a/media/circulation-15.png and /dev/null differ diff --git a/media/circulation-16.png b/media/circulation-16.png deleted file mode 100644 index a95c5117ba..0000000000 Binary files a/media/circulation-16.png and /dev/null differ diff --git a/media/circulation-17.png b/media/circulation-17.png deleted file mode 100644 index bb66c3c2aa..0000000000 Binary files a/media/circulation-17.png and /dev/null differ diff --git a/media/circulation-18.png b/media/circulation-18.png deleted file mode 100644 index 78b474565d..0000000000 Binary files a/media/circulation-18.png and /dev/null differ diff --git a/media/circulation-19.png b/media/circulation-19.png deleted file mode 100644 index 0118b0076b..0000000000 Binary files a/media/circulation-19.png and /dev/null differ diff --git a/media/circulation-2.png b/media/circulation-2.png deleted file mode 100644 index 077835dc64..0000000000 Binary files a/media/circulation-2.png and /dev/null differ diff --git a/media/circulation-20.png b/media/circulation-20.png deleted file mode 100644 index d1ed93616c..0000000000 Binary files a/media/circulation-20.png and /dev/null differ diff --git a/media/circulation-21.png b/media/circulation-21.png deleted file mode 100644 index 029c48b26d..0000000000 Binary files a/media/circulation-21.png and /dev/null differ diff --git a/media/circulation-22.png b/media/circulation-22.png deleted file mode 100644 index 0463348da7..0000000000 Binary files a/media/circulation-22.png and /dev/null differ diff --git a/media/circulation-23.png b/media/circulation-23.png deleted file mode 100644 index 0a6f10cae3..0000000000 Binary files a/media/circulation-23.png and /dev/null differ diff --git a/media/circulation-24.png b/media/circulation-24.png deleted file mode 100644 index 315125220b..0000000000 Binary files a/media/circulation-24.png and /dev/null differ diff --git a/media/circulation-25.png b/media/circulation-25.png deleted file mode 100644 index afd49ff7ec..0000000000 Binary files a/media/circulation-25.png and /dev/null differ diff --git a/media/circulation-26.png b/media/circulation-26.png deleted file mode 100644 index b116445602..0000000000 Binary files a/media/circulation-26.png and /dev/null differ diff --git a/media/circulation-27.png b/media/circulation-27.png deleted file mode 100644 index 2f0455ad06..0000000000 Binary files a/media/circulation-27.png and /dev/null differ diff --git a/media/circulation-28.png b/media/circulation-28.png deleted file mode 100644 index ddac7ec62d..0000000000 Binary files a/media/circulation-28.png and /dev/null differ diff --git a/media/circulation-29.png b/media/circulation-29.png deleted file mode 100644 index af3d586af1..0000000000 Binary files a/media/circulation-29.png and /dev/null differ diff --git a/media/circulation-3.png b/media/circulation-3.png deleted file mode 100644 index 0a75f0a7ee..0000000000 Binary files a/media/circulation-3.png and /dev/null differ diff --git a/media/circulation-30.png b/media/circulation-30.png deleted file mode 100644 index 13830c8d6e..0000000000 Binary files a/media/circulation-30.png and /dev/null differ diff --git a/media/circulation-31.png b/media/circulation-31.png deleted file mode 100644 index b2f1f1328a..0000000000 Binary files a/media/circulation-31.png and /dev/null differ diff --git a/media/circulation-32.png b/media/circulation-32.png deleted file mode 100644 index 1dffe813ff..0000000000 Binary files a/media/circulation-32.png and /dev/null differ diff --git a/media/circulation-33.png b/media/circulation-33.png deleted file mode 100644 index 367adfbfc2..0000000000 Binary files a/media/circulation-33.png and /dev/null differ diff --git a/media/circulation-34.png b/media/circulation-34.png deleted file mode 100644 index 5be2e2da9d..0000000000 Binary files a/media/circulation-34.png and /dev/null differ diff --git a/media/circulation-35.png b/media/circulation-35.png deleted file mode 100644 index b3b918b964..0000000000 Binary files a/media/circulation-35.png and /dev/null differ diff --git a/media/circulation-36.png b/media/circulation-36.png deleted file mode 100644 index 35b1e606c1..0000000000 Binary files a/media/circulation-36.png and /dev/null differ diff --git a/media/circulation-4.png b/media/circulation-4.png deleted file mode 100644 index b92ecbcbf8..0000000000 Binary files a/media/circulation-4.png and /dev/null differ diff --git a/media/circulation-5.png b/media/circulation-5.png deleted file mode 100644 index 898c871a41..0000000000 Binary files a/media/circulation-5.png and /dev/null differ diff --git a/media/circulation-6.png b/media/circulation-6.png deleted file mode 100644 index 6df9eb98b4..0000000000 Binary files a/media/circulation-6.png and /dev/null differ diff --git a/media/circulation-7.png b/media/circulation-7.png deleted file mode 100644 index 79987dfb7d..0000000000 Binary files a/media/circulation-7.png and /dev/null differ diff --git a/media/circulation-8.png b/media/circulation-8.png deleted file mode 100644 index 7c624e271d..0000000000 Binary files a/media/circulation-8.png and /dev/null differ diff --git a/media/circulation-9.png b/media/circulation-9.png deleted file mode 100644 index 49eae35b4e..0000000000 Binary files a/media/circulation-9.png and /dev/null differ diff --git a/media/claimed_date.png b/media/claimed_date.png deleted file mode 100644 index 40af3de9c2..0000000000 Binary files a/media/claimed_date.png and /dev/null differ diff --git a/media/conj1.jpg b/media/conj1.jpg deleted file mode 100644 index c515c162f8..0000000000 Binary files a/media/conj1.jpg and /dev/null differ diff --git a/media/conj10.jpg b/media/conj10.jpg deleted file mode 100644 index 1365a92bd5..0000000000 Binary files a/media/conj10.jpg and /dev/null differ diff --git a/media/conj2.jpg b/media/conj2.jpg deleted file mode 100644 index d5d05ce9fa..0000000000 Binary files a/media/conj2.jpg and /dev/null differ diff --git a/media/conj3.jpg b/media/conj3.jpg deleted file mode 100644 index 75c8d02ff0..0000000000 Binary files a/media/conj3.jpg and /dev/null differ diff --git a/media/conj4.jpg b/media/conj4.jpg deleted file mode 100644 index 9006f354fc..0000000000 Binary files a/media/conj4.jpg and /dev/null differ diff --git a/media/conj5.jpg b/media/conj5.jpg deleted file mode 100644 index 7e3b8f7b35..0000000000 Binary files a/media/conj5.jpg and /dev/null differ diff --git a/media/conj6.jpg b/media/conj6.jpg deleted file mode 100644 index 5d407a6924..0000000000 Binary files a/media/conj6.jpg and /dev/null differ diff --git a/media/conj7.jpg b/media/conj7.jpg deleted file mode 100644 index 37376fea88..0000000000 Binary files a/media/conj7.jpg and /dev/null differ diff --git a/media/conj8.jpg b/media/conj8.jpg deleted file mode 100644 index 4eecf75c24..0000000000 Binary files a/media/conj8.jpg and /dev/null differ diff --git a/media/conj9.jpg b/media/conj9.jpg deleted file mode 100644 index 45b5c9051b..0000000000 Binary files a/media/conj9.jpg and /dev/null differ diff --git a/media/copy_alert_message.png b/media/copy_alert_message.png deleted file mode 100644 index 0931d88550..0000000000 Binary files a/media/copy_alert_message.png and /dev/null differ diff --git a/media/copy_edit_alert.png b/media/copy_edit_alert.png deleted file mode 100644 index 29d0527159..0000000000 Binary files a/media/copy_edit_alert.png and /dev/null differ diff --git a/media/create-template-1.png b/media/create-template-1.png deleted file mode 100644 index 0358768eb8..0000000000 Binary files a/media/create-template-1.png and /dev/null differ diff --git a/media/create-template-10.png b/media/create-template-10.png deleted file mode 100644 index 12deb5ce9b..0000000000 Binary files a/media/create-template-10.png and /dev/null differ diff --git a/media/create-template-11.png b/media/create-template-11.png deleted file mode 100644 index 003b05bc8d..0000000000 Binary files a/media/create-template-11.png and /dev/null differ diff --git a/media/create-template-12.png b/media/create-template-12.png deleted file mode 100644 index fe4d999663..0000000000 Binary files a/media/create-template-12.png and /dev/null differ diff --git a/media/create-template-13.png b/media/create-template-13.png deleted file mode 100644 index 0831126d09..0000000000 Binary files a/media/create-template-13.png and /dev/null differ diff --git a/media/create-template-15.png b/media/create-template-15.png deleted file mode 100644 index 19734c337a..0000000000 Binary files a/media/create-template-15.png and /dev/null differ diff --git a/media/create-template-16.png b/media/create-template-16.png deleted file mode 100644 index 71665a0ffb..0000000000 Binary files a/media/create-template-16.png and /dev/null differ diff --git a/media/create-template-17.png b/media/create-template-17.png deleted file mode 100644 index 0a6308483d..0000000000 Binary files a/media/create-template-17.png and /dev/null differ diff --git a/media/create-template-19.png b/media/create-template-19.png deleted file mode 100644 index a62b2825f8..0000000000 Binary files a/media/create-template-19.png and /dev/null differ diff --git a/media/create-template-2.png b/media/create-template-2.png deleted file mode 100644 index 20466a6723..0000000000 Binary files a/media/create-template-2.png and /dev/null differ diff --git a/media/create-template-20.png b/media/create-template-20.png deleted file mode 100644 index d4beb2bd28..0000000000 Binary files a/media/create-template-20.png and /dev/null differ diff --git a/media/create-template-21.png b/media/create-template-21.png deleted file mode 100644 index e2cb2f9ade..0000000000 Binary files a/media/create-template-21.png and /dev/null differ diff --git a/media/create-template-22.png b/media/create-template-22.png deleted file mode 100644 index b7f8532bf7..0000000000 Binary files a/media/create-template-22.png and /dev/null differ diff --git a/media/create-template-23.png b/media/create-template-23.png deleted file mode 100644 index 03de846b1a..0000000000 Binary files a/media/create-template-23.png and /dev/null differ diff --git a/media/create-template-24.png b/media/create-template-24.png deleted file mode 100644 index ef381f6934..0000000000 Binary files a/media/create-template-24.png and /dev/null differ diff --git a/media/create-template-25.png b/media/create-template-25.png deleted file mode 100644 index 88d2a17a59..0000000000 Binary files a/media/create-template-25.png and /dev/null differ diff --git a/media/create-template-26.png b/media/create-template-26.png deleted file mode 100644 index b6816c88e2..0000000000 Binary files a/media/create-template-26.png and /dev/null differ diff --git a/media/create-template-27.png b/media/create-template-27.png deleted file mode 100644 index ac60c901a3..0000000000 Binary files a/media/create-template-27.png and /dev/null differ diff --git a/media/create-template-28.png b/media/create-template-28.png deleted file mode 100644 index 69d6cf1c26..0000000000 Binary files a/media/create-template-28.png and /dev/null differ diff --git a/media/create-template-29.png b/media/create-template-29.png deleted file mode 100644 index 1dcb26094f..0000000000 Binary files a/media/create-template-29.png and /dev/null differ diff --git a/media/create-template-3.png b/media/create-template-3.png deleted file mode 100644 index d2bf614be4..0000000000 Binary files a/media/create-template-3.png and /dev/null differ diff --git a/media/create-template-30.png b/media/create-template-30.png deleted file mode 100644 index 9421cb5f78..0000000000 Binary files a/media/create-template-30.png and /dev/null differ diff --git a/media/create-template-31.png b/media/create-template-31.png deleted file mode 100644 index 3a07d05822..0000000000 Binary files a/media/create-template-31.png and /dev/null differ diff --git a/media/create-template-32.png b/media/create-template-32.png deleted file mode 100644 index 3150321434..0000000000 Binary files a/media/create-template-32.png and /dev/null differ diff --git a/media/create-template-33.png b/media/create-template-33.png deleted file mode 100644 index 8d2bd373c4..0000000000 Binary files a/media/create-template-33.png and /dev/null differ diff --git a/media/create-template-34.png b/media/create-template-34.png deleted file mode 100644 index 8d7069357d..0000000000 Binary files a/media/create-template-34.png and /dev/null differ diff --git a/media/create-template-35.png b/media/create-template-35.png deleted file mode 100644 index 7bc9025d50..0000000000 Binary files a/media/create-template-35.png and /dev/null differ diff --git a/media/create-template-4.png b/media/create-template-4.png deleted file mode 100644 index b6d7201afc..0000000000 Binary files a/media/create-template-4.png and /dev/null differ diff --git a/media/create-template-5.png b/media/create-template-5.png deleted file mode 100644 index d24ad3c233..0000000000 Binary files a/media/create-template-5.png and /dev/null differ diff --git a/media/create-template-6.png b/media/create-template-6.png deleted file mode 100644 index 47fd843b46..0000000000 Binary files a/media/create-template-6.png and /dev/null differ diff --git a/media/create-template-7.png b/media/create-template-7.png deleted file mode 100644 index 8803035b01..0000000000 Binary files a/media/create-template-7.png and /dev/null differ diff --git a/media/create-template-8.png b/media/create-template-8.png deleted file mode 100644 index 8c46199336..0000000000 Binary files a/media/create-template-8.png and /dev/null differ diff --git a/media/create-template-9.png b/media/create-template-9.png deleted file mode 100644 index 49fc2ef426..0000000000 Binary files a/media/create-template-9.png and /dev/null differ diff --git a/media/due_date_display.png b/media/due_date_display.png deleted file mode 100644 index 48464fd008..0000000000 Binary files a/media/due_date_display.png and /dev/null differ diff --git a/media/edit_due_date_action.png b/media/edit_due_date_action.png deleted file mode 100644 index eb5fbc2577..0000000000 Binary files a/media/edit_due_date_action.png and /dev/null differ diff --git a/media/epub_logo_color_ht39.gif b/media/epub_logo_color_ht39.gif deleted file mode 100644 index 337ad73fb6..0000000000 Binary files a/media/epub_logo_color_ht39.gif and /dev/null differ diff --git a/media/evergreen_logo.gif b/media/evergreen_logo.gif deleted file mode 100644 index c7c79111c5..0000000000 Binary files a/media/evergreen_logo.gif and /dev/null differ diff --git a/media/folder-1.png b/media/folder-1.png deleted file mode 100644 index 0e24910efb..0000000000 Binary files a/media/folder-1.png and /dev/null differ diff --git a/media/folder-10.png b/media/folder-10.png deleted file mode 100644 index 7b5acd9198..0000000000 Binary files a/media/folder-10.png and /dev/null differ diff --git a/media/folder-11.png b/media/folder-11.png deleted file mode 100644 index e358551745..0000000000 Binary files a/media/folder-11.png and /dev/null differ diff --git a/media/folder-12.png b/media/folder-12.png deleted file mode 100644 index 6a5f98fab8..0000000000 Binary files a/media/folder-12.png and /dev/null differ diff --git a/media/folder-13.png b/media/folder-13.png deleted file mode 100644 index 62ecd43fc9..0000000000 Binary files a/media/folder-13.png and /dev/null differ diff --git a/media/folder-14.png b/media/folder-14.png deleted file mode 100644 index f7ff979d4a..0000000000 Binary files a/media/folder-14.png and /dev/null differ diff --git a/media/folder-7a.png b/media/folder-7a.png deleted file mode 100644 index cadf59fd2f..0000000000 Binary files a/media/folder-7a.png and /dev/null differ diff --git a/media/generate-report-1.png b/media/generate-report-1.png deleted file mode 100644 index a208d89e9e..0000000000 Binary files a/media/generate-report-1.png and /dev/null differ diff --git a/media/generate-report-10.png b/media/generate-report-10.png deleted file mode 100644 index 9980b92096..0000000000 Binary files a/media/generate-report-10.png and /dev/null differ diff --git a/media/generate-report-14.png b/media/generate-report-14.png deleted file mode 100644 index e6846b560a..0000000000 Binary files a/media/generate-report-14.png and /dev/null differ diff --git a/media/generate-report-2.png b/media/generate-report-2.png deleted file mode 100644 index 8ba8a9773d..0000000000 Binary files a/media/generate-report-2.png and /dev/null differ diff --git a/media/generate-report-3.png b/media/generate-report-3.png deleted file mode 100644 index e5cdfdb3ae..0000000000 Binary files a/media/generate-report-3.png and /dev/null differ diff --git a/media/generate-report-8.png b/media/generate-report-8.png deleted file mode 100644 index 72a700271c..0000000000 Binary files a/media/generate-report-8.png and /dev/null differ diff --git a/media/generate-report-9.png b/media/generate-report-9.png deleted file mode 100644 index 5c6aa4468f..0000000000 Binary files a/media/generate-report-9.png and /dev/null differ diff --git a/media/hold-1.png b/media/hold-1.png deleted file mode 100644 index 18dbf6c59e..0000000000 Binary files a/media/hold-1.png and /dev/null differ diff --git a/media/hold-10.png b/media/hold-10.png deleted file mode 100644 index 39744442d1..0000000000 Binary files a/media/hold-10.png and /dev/null differ diff --git a/media/hold-11.png b/media/hold-11.png deleted file mode 100644 index c20be3aad1..0000000000 Binary files a/media/hold-11.png and /dev/null differ diff --git a/media/hold-12.png b/media/hold-12.png deleted file mode 100644 index 012409912f..0000000000 Binary files a/media/hold-12.png and /dev/null differ diff --git a/media/hold-14.png b/media/hold-14.png deleted file mode 100644 index fe211fd0e1..0000000000 Binary files a/media/hold-14.png and /dev/null differ diff --git a/media/hold-15.png b/media/hold-15.png deleted file mode 100644 index 37dbaedcdf..0000000000 Binary files a/media/hold-15.png and /dev/null differ diff --git a/media/hold-16.png b/media/hold-16.png deleted file mode 100644 index 235b0886ae..0000000000 Binary files a/media/hold-16.png and /dev/null differ diff --git a/media/hold-17.png b/media/hold-17.png deleted file mode 100644 index 569a274287..0000000000 Binary files a/media/hold-17.png and /dev/null differ diff --git a/media/hold-18.png b/media/hold-18.png deleted file mode 100644 index 58147bf78f..0000000000 Binary files a/media/hold-18.png and /dev/null differ diff --git a/media/hold-19.png b/media/hold-19.png deleted file mode 100644 index 86ffac89dd..0000000000 Binary files a/media/hold-19.png and /dev/null differ diff --git a/media/hold-2.png b/media/hold-2.png deleted file mode 100644 index b9968a97c5..0000000000 Binary files a/media/hold-2.png and /dev/null differ diff --git a/media/hold-20.png b/media/hold-20.png deleted file mode 100644 index 3aeb8f93db..0000000000 Binary files a/media/hold-20.png and /dev/null differ diff --git a/media/hold-21.png b/media/hold-21.png deleted file mode 100644 index bb1422cee8..0000000000 Binary files a/media/hold-21.png and /dev/null differ diff --git a/media/hold-22.png b/media/hold-22.png deleted file mode 100644 index cc9050177b..0000000000 Binary files a/media/hold-22.png and /dev/null differ diff --git a/media/hold-23.png b/media/hold-23.png deleted file mode 100644 index e08d9bdf27..0000000000 Binary files a/media/hold-23.png and /dev/null differ diff --git a/media/hold-24.png b/media/hold-24.png deleted file mode 100644 index 69d78aa256..0000000000 Binary files a/media/hold-24.png and /dev/null differ diff --git a/media/hold-25.png b/media/hold-25.png deleted file mode 100644 index 8df926061d..0000000000 Binary files a/media/hold-25.png and /dev/null differ diff --git a/media/hold-26.png b/media/hold-26.png deleted file mode 100644 index 73f26f1251..0000000000 Binary files a/media/hold-26.png and /dev/null differ diff --git a/media/hold-27.png b/media/hold-27.png deleted file mode 100644 index 7b57b8899e..0000000000 Binary files a/media/hold-27.png and /dev/null differ diff --git a/media/hold-28.png b/media/hold-28.png deleted file mode 100644 index f569003995..0000000000 Binary files a/media/hold-28.png and /dev/null differ diff --git a/media/hold-29.png b/media/hold-29.png deleted file mode 100644 index b0d265786f..0000000000 Binary files a/media/hold-29.png and /dev/null differ diff --git a/media/hold-4.png b/media/hold-4.png deleted file mode 100644 index 79e8a419eb..0000000000 Binary files a/media/hold-4.png and /dev/null differ diff --git a/media/hold-5.png b/media/hold-5.png deleted file mode 100644 index 3038e93b3d..0000000000 Binary files a/media/hold-5.png and /dev/null differ diff --git a/media/hold-6.png b/media/hold-6.png deleted file mode 100644 index d57e25d6e0..0000000000 Binary files a/media/hold-6.png and /dev/null differ diff --git a/media/hold-7.png b/media/hold-7.png deleted file mode 100644 index 494d5fe5cf..0000000000 Binary files a/media/hold-7.png and /dev/null differ diff --git a/media/hold-8.png b/media/hold-8.png deleted file mode 100644 index 780fd2a7d6..0000000000 Binary files a/media/hold-8.png and /dev/null differ diff --git a/media/hold-9.png b/media/hold-9.png deleted file mode 100644 index 2b2ce2b52a..0000000000 Binary files a/media/hold-9.png and /dev/null differ diff --git a/media/holds-clearing-1.png b/media/holds-clearing-1.png deleted file mode 100644 index f13d58b4dd..0000000000 Binary files a/media/holds-clearing-1.png and /dev/null differ diff --git a/media/holds-clearing-2.png b/media/holds-clearing-2.png deleted file mode 100644 index 0c40e2129b..0000000000 Binary files a/media/holds-clearing-2.png and /dev/null differ diff --git a/media/holds-clearing-3.png b/media/holds-clearing-3.png deleted file mode 100644 index 4810e851fe..0000000000 Binary files a/media/holds-clearing-3.png and /dev/null differ diff --git a/media/holds-clearing-4.png b/media/holds-clearing-4.png deleted file mode 100644 index 1bbc2a3ea4..0000000000 Binary files a/media/holds-clearing-4.png and /dev/null differ diff --git a/media/holds-managing-1.png b/media/holds-managing-1.png deleted file mode 100644 index 298c431279..0000000000 Binary files a/media/holds-managing-1.png and /dev/null differ diff --git a/media/holds-managing-10.png b/media/holds-managing-10.png deleted file mode 100644 index fab2a8be54..0000000000 Binary files a/media/holds-managing-10.png and /dev/null differ diff --git a/media/holds-managing-11.png b/media/holds-managing-11.png deleted file mode 100644 index 89beec91a0..0000000000 Binary files a/media/holds-managing-11.png and /dev/null differ diff --git a/media/holds-managing-12.png b/media/holds-managing-12.png deleted file mode 100644 index 9265a57634..0000000000 Binary files a/media/holds-managing-12.png and /dev/null differ diff --git a/media/holds-managing-13.png b/media/holds-managing-13.png deleted file mode 100644 index 2765f756e3..0000000000 Binary files a/media/holds-managing-13.png and /dev/null differ diff --git a/media/holds-managing-14.png b/media/holds-managing-14.png deleted file mode 100644 index ee8649480d..0000000000 Binary files a/media/holds-managing-14.png and /dev/null differ diff --git a/media/holds-managing-15.png b/media/holds-managing-15.png deleted file mode 100644 index 20dd0b454b..0000000000 Binary files a/media/holds-managing-15.png and /dev/null differ diff --git a/media/holds-managing-16.png b/media/holds-managing-16.png deleted file mode 100644 index 2db6c18230..0000000000 Binary files a/media/holds-managing-16.png and /dev/null differ diff --git a/media/holds-managing-17.png b/media/holds-managing-17.png deleted file mode 100644 index c203b51e5a..0000000000 Binary files a/media/holds-managing-17.png and /dev/null differ diff --git a/media/holds-managing-18.png b/media/holds-managing-18.png deleted file mode 100644 index 6e6d6d749a..0000000000 Binary files a/media/holds-managing-18.png and /dev/null differ diff --git a/media/holds-managing-19.png b/media/holds-managing-19.png deleted file mode 100644 index bb14d68cff..0000000000 Binary files a/media/holds-managing-19.png and /dev/null differ diff --git a/media/holds-managing-2.png b/media/holds-managing-2.png deleted file mode 100644 index 4b7af26bcb..0000000000 Binary files a/media/holds-managing-2.png and /dev/null differ diff --git a/media/holds-managing-3.png b/media/holds-managing-3.png deleted file mode 100644 index 16ca2674f6..0000000000 Binary files a/media/holds-managing-3.png and /dev/null differ diff --git a/media/holds-managing-4.png b/media/holds-managing-4.png deleted file mode 100644 index 34e758d6eb..0000000000 Binary files a/media/holds-managing-4.png and /dev/null differ diff --git a/media/holds-managing-5.png b/media/holds-managing-5.png deleted file mode 100644 index 96b836f3fe..0000000000 Binary files a/media/holds-managing-5.png and /dev/null differ diff --git a/media/holds-managing-6.png b/media/holds-managing-6.png deleted file mode 100644 index f7ce7ebd7f..0000000000 Binary files a/media/holds-managing-6.png and /dev/null differ diff --git a/media/holds-managing-7.png b/media/holds-managing-7.png deleted file mode 100644 index 12f7ffef38..0000000000 Binary files a/media/holds-managing-7.png and /dev/null differ diff --git a/media/holds-managing-8.png b/media/holds-managing-8.png deleted file mode 100644 index bbbff642ba..0000000000 Binary files a/media/holds-managing-8.png and /dev/null differ diff --git a/media/holds-managing-9.png b/media/holds-managing-9.png deleted file mode 100644 index 4b2cc8315b..0000000000 Binary files a/media/holds-managing-9.png and /dev/null differ diff --git a/media/holds-notifications-1.png b/media/holds-notifications-1.png deleted file mode 100644 index d389d5715b..0000000000 Binary files a/media/holds-notifications-1.png and /dev/null differ diff --git a/media/holds-notifications-2.png b/media/holds-notifications-2.png deleted file mode 100644 index 3e1eadb011..0000000000 Binary files a/media/holds-notifications-2.png and /dev/null differ diff --git a/media/holds-notifications-3.png b/media/holds-notifications-3.png deleted file mode 100644 index bfb8ee201d..0000000000 Binary files a/media/holds-notifications-3.png and /dev/null differ diff --git a/media/holds-notifications-4.png b/media/holds-notifications-4.png deleted file mode 100644 index fd9201b872..0000000000 Binary files a/media/holds-notifications-4.png and /dev/null differ diff --git a/media/holds-placing-1.png b/media/holds-placing-1.png deleted file mode 100644 index 5f60630e8b..0000000000 Binary files a/media/holds-placing-1.png and /dev/null differ diff --git a/media/holds-placing-10.png b/media/holds-placing-10.png deleted file mode 100644 index 46fe88a112..0000000000 Binary files a/media/holds-placing-10.png and /dev/null differ diff --git a/media/holds-placing-11.png b/media/holds-placing-11.png deleted file mode 100644 index cd1a10201e..0000000000 Binary files a/media/holds-placing-11.png and /dev/null differ diff --git a/media/holds-placing-2.png b/media/holds-placing-2.png deleted file mode 100644 index 71daec5c6c..0000000000 Binary files a/media/holds-placing-2.png and /dev/null differ diff --git a/media/holds-placing-3.png b/media/holds-placing-3.png deleted file mode 100644 index 16ca2674f6..0000000000 Binary files a/media/holds-placing-3.png and /dev/null differ diff --git a/media/holds-placing-4.png b/media/holds-placing-4.png deleted file mode 100644 index 7b0c2e7423..0000000000 Binary files a/media/holds-placing-4.png and /dev/null differ diff --git a/media/holds-placing-5.png b/media/holds-placing-5.png deleted file mode 100644 index 7ef50cb46f..0000000000 Binary files a/media/holds-placing-5.png and /dev/null differ diff --git a/media/holds-placing-6.png b/media/holds-placing-6.png deleted file mode 100644 index d8e7c3d5f9..0000000000 Binary files a/media/holds-placing-6.png and /dev/null differ diff --git a/media/holds-placing-7.png b/media/holds-placing-7.png deleted file mode 100644 index aa0ec912a7..0000000000 Binary files a/media/holds-placing-7.png and /dev/null differ diff --git a/media/holds-placing-8.png b/media/holds-placing-8.png deleted file mode 100644 index c354a9d4d9..0000000000 Binary files a/media/holds-placing-8.png and /dev/null differ diff --git a/media/holds-placing-9.png b/media/holds-placing-9.png deleted file mode 100644 index 41fe57efda..0000000000 Binary files a/media/holds-placing-9.png and /dev/null differ diff --git a/media/holds-pull-1.png b/media/holds-pull-1.png deleted file mode 100644 index 4973c579ea..0000000000 Binary files a/media/holds-pull-1.png and /dev/null differ diff --git a/media/holds-pull-2.png b/media/holds-pull-2.png deleted file mode 100644 index 8798d0ad1f..0000000000 Binary files a/media/holds-pull-2.png and /dev/null differ diff --git a/media/holds-pull-3.png b/media/holds-pull-3.png deleted file mode 100644 index 494febb84e..0000000000 Binary files a/media/holds-pull-3.png and /dev/null differ diff --git a/media/holds-pull-4.png b/media/holds-pull-4.png deleted file mode 100644 index df4dde79e1..0000000000 Binary files a/media/holds-pull-4.png and /dev/null differ diff --git a/media/holds-pull-5.png b/media/holds-pull-5.png deleted file mode 100644 index 05b2ea7649..0000000000 Binary files a/media/holds-pull-5.png and /dev/null differ diff --git a/media/holds-pull-5a.png b/media/holds-pull-5a.png deleted file mode 100644 index e418fb369d..0000000000 Binary files a/media/holds-pull-5a.png and /dev/null differ diff --git a/media/holds-pull-6.png b/media/holds-pull-6.png deleted file mode 100644 index 98fbabbef6..0000000000 Binary files a/media/holds-pull-6.png and /dev/null differ diff --git a/media/holds-pull-7.png b/media/holds-pull-7.png deleted file mode 100644 index e0a39491d7..0000000000 Binary files a/media/holds-pull-7.png and /dev/null differ diff --git a/media/holds-pull-8.png b/media/holds-pull-8.png deleted file mode 100644 index 95caa42ab6..0000000000 Binary files a/media/holds-pull-8.png and /dev/null differ diff --git a/media/holds-pull-9.png b/media/holds-pull-9.png deleted file mode 100644 index 17c9eb021e..0000000000 Binary files a/media/holds-pull-9.png and /dev/null differ diff --git a/media/in_house_use.png b/media/in_house_use.png deleted file mode 100644 index 3c15245a19..0000000000 Binary files a/media/in_house_use.png and /dev/null differ diff --git a/media/item_status_altview.png b/media/item_status_altview.png deleted file mode 100644 index 5baa0ad9a0..0000000000 Binary files a/media/item_status_altview.png and /dev/null differ diff --git a/media/item_status_barcode.png b/media/item_status_barcode.png deleted file mode 100644 index 10d7e21a29..0000000000 Binary files a/media/item_status_barcode.png and /dev/null differ diff --git a/media/item_status_list_view.png b/media/item_status_list_view.png deleted file mode 100644 index 82b6197168..0000000000 Binary files a/media/item_status_list_view.png and /dev/null differ diff --git a/media/item_status_menu.png b/media/item_status_menu.png deleted file mode 100644 index 7ecd0a61ce..0000000000 Binary files a/media/item_status_menu.png and /dev/null differ diff --git a/media/items_out_click.png b/media/items_out_click.png deleted file mode 100644 index ac9542f849..0000000000 Binary files a/media/items_out_click.png and /dev/null differ diff --git a/media/k_book_record.png b/media/k_book_record.png deleted file mode 100644 index e41a886706..0000000000 Binary files a/media/k_book_record.png and /dev/null differ diff --git a/media/last_few_circs_action.png b/media/last_few_circs_action.png deleted file mode 100644 index 6ccfaee033..0000000000 Binary files a/media/last_few_circs_action.png and /dev/null differ diff --git a/media/last_few_circs_display.png b/media/last_few_circs_display.png deleted file mode 100644 index 0e66051d1c..0000000000 Binary files a/media/last_few_circs_display.png and /dev/null differ diff --git a/media/lost_cr_section.png b/media/lost_cr_section.png deleted file mode 100644 index 1a2538b96d..0000000000 Binary files a/media/lost_cr_section.png and /dev/null differ diff --git a/media/lsa-1.png b/media/lsa-1.png deleted file mode 100644 index eee8707b4c..0000000000 Binary files a/media/lsa-1.png and /dev/null differ diff --git a/media/lsa-10.jpg b/media/lsa-10.jpg deleted file mode 100644 index 7c578e03b1..0000000000 Binary files a/media/lsa-10.jpg and /dev/null differ diff --git a/media/lsa-11.jpg b/media/lsa-11.jpg deleted file mode 100644 index 4df7484298..0000000000 Binary files a/media/lsa-11.jpg and /dev/null differ diff --git a/media/lsa-12.jpg b/media/lsa-12.jpg deleted file mode 100644 index c1c550546d..0000000000 Binary files a/media/lsa-12.jpg and /dev/null differ diff --git a/media/lsa-14.jpg b/media/lsa-14.jpg deleted file mode 100644 index bdf842c60a..0000000000 Binary files a/media/lsa-14.jpg and /dev/null differ diff --git a/media/lsa-16.jpg b/media/lsa-16.jpg deleted file mode 100644 index 90fdca61a8..0000000000 Binary files a/media/lsa-16.jpg and /dev/null differ diff --git a/media/lsa-17.jpg b/media/lsa-17.jpg deleted file mode 100644 index a08b590caf..0000000000 Binary files a/media/lsa-17.jpg and /dev/null differ diff --git a/media/lsa-18.jpg b/media/lsa-18.jpg deleted file mode 100644 index a3710530e7..0000000000 Binary files a/media/lsa-18.jpg and /dev/null differ diff --git a/media/lsa-2.jpg b/media/lsa-2.jpg deleted file mode 100644 index 2cdd562075..0000000000 Binary files a/media/lsa-2.jpg and /dev/null differ diff --git a/media/lsa-22.png b/media/lsa-22.png deleted file mode 100644 index b3f55dfe0f..0000000000 Binary files a/media/lsa-22.png and /dev/null differ diff --git a/media/lsa-23.jpg b/media/lsa-23.jpg deleted file mode 100644 index 9fbdf96ba1..0000000000 Binary files a/media/lsa-23.jpg and /dev/null differ diff --git a/media/lsa-25.jpg b/media/lsa-25.jpg deleted file mode 100644 index 2cbb735295..0000000000 Binary files a/media/lsa-25.jpg and /dev/null differ diff --git a/media/lsa-26.jpg b/media/lsa-26.jpg deleted file mode 100644 index 9b1575c1fd..0000000000 Binary files a/media/lsa-26.jpg and /dev/null differ diff --git a/media/lsa-27.jpg b/media/lsa-27.jpg deleted file mode 100644 index 36a024c049..0000000000 Binary files a/media/lsa-27.jpg and /dev/null differ diff --git a/media/lsa-28.jpg b/media/lsa-28.jpg deleted file mode 100644 index ccf0b1a705..0000000000 Binary files a/media/lsa-28.jpg and /dev/null differ diff --git a/media/lsa-32.jpg b/media/lsa-32.jpg deleted file mode 100644 index bf03d62108..0000000000 Binary files a/media/lsa-32.jpg and /dev/null differ diff --git a/media/lsa-33.jpg b/media/lsa-33.jpg deleted file mode 100644 index 2a211fb686..0000000000 Binary files a/media/lsa-33.jpg and /dev/null differ diff --git a/media/lsa-4.jpg b/media/lsa-4.jpg deleted file mode 100644 index 0406e4afda..0000000000 Binary files a/media/lsa-4.jpg and /dev/null differ diff --git a/media/lsa-5.jpg b/media/lsa-5.jpg deleted file mode 100644 index da0e056bce..0000000000 Binary files a/media/lsa-5.jpg and /dev/null differ diff --git a/media/lsa-7.jpg b/media/lsa-7.jpg deleted file mode 100644 index 6544913195..0000000000 Binary files a/media/lsa-7.jpg and /dev/null differ diff --git a/media/lsa-8.jpg b/media/lsa-8.jpg deleted file mode 100644 index 4de9cf445e..0000000000 Binary files a/media/lsa-8.jpg and /dev/null differ diff --git a/media/lsa-closed-mountain-1.png b/media/lsa-closed-mountain-1.png deleted file mode 100644 index b7eb2c68b8..0000000000 Binary files a/media/lsa-closed-mountain-1.png and /dev/null differ diff --git a/media/lsa-closed-mountain-2.png b/media/lsa-closed-mountain-2.png deleted file mode 100644 index f0b1036d69..0000000000 Binary files a/media/lsa-closed-mountain-2.png and /dev/null differ diff --git a/media/lsa-group-0.png b/media/lsa-group-0.png deleted file mode 100644 index 4d75083ac4..0000000000 Binary files a/media/lsa-group-0.png and /dev/null differ diff --git a/media/lsa-group-1.png b/media/lsa-group-1.png deleted file mode 100644 index 46a0a0f832..0000000000 Binary files a/media/lsa-group-1.png and /dev/null differ diff --git a/media/lsa-group-1a.png b/media/lsa-group-1a.png deleted file mode 100644 index a5f4e93259..0000000000 Binary files a/media/lsa-group-1a.png and /dev/null differ diff --git a/media/lsa-group-2.png b/media/lsa-group-2.png deleted file mode 100644 index bd3717313e..0000000000 Binary files a/media/lsa-group-2.png and /dev/null differ diff --git a/media/lsa-group-3.png b/media/lsa-group-3.png deleted file mode 100644 index 328e7333a1..0000000000 Binary files a/media/lsa-group-3.png and /dev/null differ diff --git a/media/lsa-group-4.png b/media/lsa-group-4.png deleted file mode 100644 index 4e378d3815..0000000000 Binary files a/media/lsa-group-4.png and /dev/null differ diff --git a/media/lsa-group-5.png b/media/lsa-group-5.png deleted file mode 100644 index 53ee8edd31..0000000000 Binary files a/media/lsa-group-5.png and /dev/null differ diff --git a/media/lsa-group-6.png b/media/lsa-group-6.png deleted file mode 100644 index 5a17f16547..0000000000 Binary files a/media/lsa-group-6.png and /dev/null differ diff --git a/media/lsa-statcat-1.png b/media/lsa-statcat-1.png deleted file mode 100644 index f54232ff5b..0000000000 Binary files a/media/lsa-statcat-1.png and /dev/null differ diff --git a/media/lsa-statcat-2.png b/media/lsa-statcat-2.png deleted file mode 100644 index 770d7a7538..0000000000 Binary files a/media/lsa-statcat-2.png and /dev/null differ diff --git a/media/lsa-statcat-3.png b/media/lsa-statcat-3.png deleted file mode 100644 index e4ec35d89b..0000000000 Binary files a/media/lsa-statcat-3.png and /dev/null differ diff --git a/media/lsa-statcat-4.png b/media/lsa-statcat-4.png deleted file mode 100644 index 99aa0946c1..0000000000 Binary files a/media/lsa-statcat-4.png and /dev/null differ diff --git a/media/lsa-statcat-5.png b/media/lsa-statcat-5.png deleted file mode 100644 index 565d632d83..0000000000 Binary files a/media/lsa-statcat-5.png and /dev/null differ diff --git a/media/lsa-statcat-6.png b/media/lsa-statcat-6.png deleted file mode 100644 index b7bb8585a6..0000000000 Binary files a/media/lsa-statcat-6.png and /dev/null differ diff --git a/media/lsa-statcat-7.png b/media/lsa-statcat-7.png deleted file mode 100644 index 964fad421e..0000000000 Binary files a/media/lsa-statcat-7.png and /dev/null differ diff --git a/media/lsa-statcat-8.png b/media/lsa-statcat-8.png deleted file mode 100644 index 3156964623..0000000000 Binary files a/media/lsa-statcat-8.png and /dev/null differ diff --git a/media/main_logo.jpg b/media/main_logo.jpg deleted file mode 100644 index 633b7a75f9..0000000000 Binary files a/media/main_logo.jpg and /dev/null differ diff --git a/media/mark_claims_returned.png b/media/mark_claims_returned.png deleted file mode 100644 index 6818ae1e42..0000000000 Binary files a/media/mark_claims_returned.png and /dev/null differ diff --git a/media/mark_lost.png b/media/mark_lost.png deleted file mode 100644 index b63df20d99..0000000000 Binary files a/media/mark_lost.png and /dev/null differ diff --git a/media/mark_missing_damaged.png b/media/mark_missing_damaged.png deleted file mode 100644 index ebb6b9ca0e..0000000000 Binary files a/media/mark_missing_damaged.png and /dev/null differ diff --git a/media/monograph_parts1.jpg b/media/monograph_parts1.jpg deleted file mode 100644 index a105515e14..0000000000 Binary files a/media/monograph_parts1.jpg and /dev/null differ diff --git a/media/monograph_parts2.jpg b/media/monograph_parts2.jpg deleted file mode 100644 index 20f63e3151..0000000000 Binary files a/media/monograph_parts2.jpg and /dev/null differ diff --git a/media/monograph_parts3.jpg b/media/monograph_parts3.jpg deleted file mode 100644 index f40687d941..0000000000 Binary files a/media/monograph_parts3.jpg and /dev/null differ diff --git a/media/monograph_parts4.jpg b/media/monograph_parts4.jpg deleted file mode 100644 index ae91126a28..0000000000 Binary files a/media/monograph_parts4.jpg and /dev/null differ diff --git a/media/monograph_parts5.jpg b/media/monograph_parts5.jpg deleted file mode 100644 index f4130e34af..0000000000 Binary files a/media/monograph_parts5.jpg and /dev/null differ diff --git a/media/myaccount-bookbags.png b/media/myaccount-bookbags.png deleted file mode 100644 index 940618fe29..0000000000 Binary files a/media/myaccount-bookbags.png and /dev/null differ diff --git a/media/myaccount-itemrenew.png b/media/myaccount-itemrenew.png deleted file mode 100644 index dcbb6760e9..0000000000 Binary files a/media/myaccount-itemrenew.png and /dev/null differ diff --git a/media/myaccount-itemscheckedout.png b/media/myaccount-itemscheckedout.png deleted file mode 100644 index 4e85822bcf..0000000000 Binary files a/media/myaccount-itemscheckedout.png and /dev/null differ diff --git a/media/myaccount-itemsonhold.png b/media/myaccount-itemsonhold.png deleted file mode 100644 index 4b1d5e3d6b..0000000000 Binary files a/media/myaccount-itemsonhold.png and /dev/null differ diff --git a/media/myaccount-login-arrow.png b/media/myaccount-login-arrow.png deleted file mode 100644 index 9cdcdad299..0000000000 Binary files a/media/myaccount-login-arrow.png and /dev/null differ diff --git a/media/myaccount-login-info.png b/media/myaccount-login-info.png deleted file mode 100644 index 31343612db..0000000000 Binary files a/media/myaccount-login-info.png and /dev/null differ diff --git a/media/myaccount-login.png b/media/myaccount-login.png deleted file mode 100644 index 180e9397a0..0000000000 Binary files a/media/myaccount-login.png and /dev/null differ diff --git a/media/myaccount-loginpasswordupdate.png b/media/myaccount-loginpasswordupdate.png deleted file mode 100644 index e29ea6661b..0000000000 Binary files a/media/myaccount-loginpasswordupdate.png and /dev/null differ diff --git a/media/myaccount-summary.png b/media/myaccount-summary.png deleted file mode 100644 index 1ab86b48a3..0000000000 Binary files a/media/myaccount-summary.png and /dev/null differ diff --git a/media/note.png b/media/note.png deleted file mode 100644 index 198ada5be4..0000000000 Binary files a/media/note.png and /dev/null differ diff --git a/media/offline-1.png b/media/offline-1.png deleted file mode 100644 index f7cad0ccd0..0000000000 Binary files a/media/offline-1.png and /dev/null differ diff --git a/media/offline-10.png b/media/offline-10.png deleted file mode 100644 index 754f007255..0000000000 Binary files a/media/offline-10.png and /dev/null differ diff --git a/media/offline-11.png b/media/offline-11.png deleted file mode 100644 index 914da51de0..0000000000 Binary files a/media/offline-11.png and /dev/null differ diff --git a/media/offline-12.png b/media/offline-12.png deleted file mode 100644 index 66b48cf4e7..0000000000 Binary files a/media/offline-12.png and /dev/null differ diff --git a/media/offline-13.png b/media/offline-13.png deleted file mode 100644 index fdee7dd22c..0000000000 Binary files a/media/offline-13.png and /dev/null differ diff --git a/media/offline-14.png b/media/offline-14.png deleted file mode 100644 index 0177657633..0000000000 Binary files a/media/offline-14.png and /dev/null differ diff --git a/media/offline-15.png b/media/offline-15.png deleted file mode 100644 index ab5c5d6b1e..0000000000 Binary files a/media/offline-15.png and /dev/null differ diff --git a/media/offline-16.png b/media/offline-16.png deleted file mode 100644 index cc1e9dd5cd..0000000000 Binary files a/media/offline-16.png and /dev/null differ diff --git a/media/offline-17.png b/media/offline-17.png deleted file mode 100644 index e895e6fffc..0000000000 Binary files a/media/offline-17.png and /dev/null differ diff --git a/media/offline-18.png b/media/offline-18.png deleted file mode 100644 index 6e1ff210fc..0000000000 Binary files a/media/offline-18.png and /dev/null differ diff --git a/media/offline-19.png b/media/offline-19.png deleted file mode 100644 index 6e26d49f2f..0000000000 Binary files a/media/offline-19.png and /dev/null differ diff --git a/media/offline-2.png b/media/offline-2.png deleted file mode 100644 index 9077658945..0000000000 Binary files a/media/offline-2.png and /dev/null differ diff --git a/media/offline-20.png b/media/offline-20.png deleted file mode 100644 index 8640d72c63..0000000000 Binary files a/media/offline-20.png and /dev/null differ diff --git a/media/offline-21.png b/media/offline-21.png deleted file mode 100644 index 356598ab7f..0000000000 Binary files a/media/offline-21.png and /dev/null differ diff --git a/media/offline-22.png b/media/offline-22.png deleted file mode 100644 index e4b0f82893..0000000000 Binary files a/media/offline-22.png and /dev/null differ diff --git a/media/offline-23.png b/media/offline-23.png deleted file mode 100644 index d75427808d..0000000000 Binary files a/media/offline-23.png and /dev/null differ diff --git a/media/offline-24.png b/media/offline-24.png deleted file mode 100644 index 7e3b09094e..0000000000 Binary files a/media/offline-24.png and /dev/null differ diff --git a/media/offline-25.png b/media/offline-25.png deleted file mode 100644 index bda37a6eed..0000000000 Binary files a/media/offline-25.png and /dev/null differ diff --git a/media/offline-26.png b/media/offline-26.png deleted file mode 100644 index 653bfb4bfd..0000000000 Binary files a/media/offline-26.png and /dev/null differ diff --git a/media/offline-27.png b/media/offline-27.png deleted file mode 100644 index 9c0722b793..0000000000 Binary files a/media/offline-27.png and /dev/null differ diff --git a/media/offline-28.png b/media/offline-28.png deleted file mode 100644 index 9cad8d870a..0000000000 Binary files a/media/offline-28.png and /dev/null differ diff --git a/media/offline-29.png b/media/offline-29.png deleted file mode 100644 index 73a302c211..0000000000 Binary files a/media/offline-29.png and /dev/null differ diff --git a/media/offline-3.png b/media/offline-3.png deleted file mode 100644 index a3d644de41..0000000000 Binary files a/media/offline-3.png and /dev/null differ diff --git a/media/offline-30.png b/media/offline-30.png deleted file mode 100644 index 06bbb9a111..0000000000 Binary files a/media/offline-30.png and /dev/null differ diff --git a/media/offline-31.png b/media/offline-31.png deleted file mode 100644 index 6b89ac32d6..0000000000 Binary files a/media/offline-31.png and /dev/null differ diff --git a/media/offline-32.png b/media/offline-32.png deleted file mode 100644 index d26187900c..0000000000 Binary files a/media/offline-32.png and /dev/null differ diff --git a/media/offline-33.png b/media/offline-33.png deleted file mode 100644 index bbf9bb16de..0000000000 Binary files a/media/offline-33.png and /dev/null differ diff --git a/media/offline-34.png b/media/offline-34.png deleted file mode 100644 index eed6d76a7d..0000000000 Binary files a/media/offline-34.png and /dev/null differ diff --git a/media/offline-35.png b/media/offline-35.png deleted file mode 100644 index 36a3a9affe..0000000000 Binary files a/media/offline-35.png and /dev/null differ diff --git a/media/offline-36.png b/media/offline-36.png deleted file mode 100644 index 1274059012..0000000000 Binary files a/media/offline-36.png and /dev/null differ diff --git a/media/offline-4.png b/media/offline-4.png deleted file mode 100644 index d5e7218008..0000000000 Binary files a/media/offline-4.png and /dev/null differ diff --git a/media/offline-5.png b/media/offline-5.png deleted file mode 100644 index 5641cb4e4b..0000000000 Binary files a/media/offline-5.png and /dev/null differ diff --git a/media/offline-6.png b/media/offline-6.png deleted file mode 100644 index 31531be097..0000000000 Binary files a/media/offline-6.png and /dev/null differ diff --git a/media/offline-7.png b/media/offline-7.png deleted file mode 100644 index 7d563a46ea..0000000000 Binary files a/media/offline-7.png and /dev/null differ diff --git a/media/offline-8.png b/media/offline-8.png deleted file mode 100644 index 0aeeeea53b..0000000000 Binary files a/media/offline-8.png and /dev/null differ diff --git a/media/offline-9.png b/media/offline-9.png deleted file mode 100644 index 3f23afe3a8..0000000000 Binary files a/media/offline-9.png and /dev/null differ diff --git a/media/overdue_checkin.png b/media/overdue_checkin.png deleted file mode 100644 index 3adf27d2d2..0000000000 Binary files a/media/overdue_checkin.png and /dev/null differ diff --git a/media/passwordresetmessage.png b/media/passwordresetmessage.png deleted file mode 100644 index 29a9cc6f6a..0000000000 Binary files a/media/passwordresetmessage.png and /dev/null differ diff --git a/media/patron-1.png b/media/patron-1.png deleted file mode 100644 index 94f12126f8..0000000000 Binary files a/media/patron-1.png and /dev/null differ diff --git a/media/patron-10.png b/media/patron-10.png deleted file mode 100644 index 0814ad9973..0000000000 Binary files a/media/patron-10.png and /dev/null differ diff --git a/media/patron-11.png b/media/patron-11.png deleted file mode 100644 index e2e72955c3..0000000000 Binary files a/media/patron-11.png and /dev/null differ diff --git a/media/patron-12.png b/media/patron-12.png deleted file mode 100644 index 4dfb246ae2..0000000000 Binary files a/media/patron-12.png and /dev/null differ diff --git a/media/patron-13.png b/media/patron-13.png deleted file mode 100644 index 5dc9cb1ba2..0000000000 Binary files a/media/patron-13.png and /dev/null differ diff --git a/media/patron-14.png b/media/patron-14.png deleted file mode 100644 index 956d397751..0000000000 Binary files a/media/patron-14.png and /dev/null differ diff --git a/media/patron-15.png b/media/patron-15.png deleted file mode 100644 index 8d7c4c713d..0000000000 Binary files a/media/patron-15.png and /dev/null differ diff --git a/media/patron-16.png b/media/patron-16.png deleted file mode 100644 index 283c6d7a05..0000000000 Binary files a/media/patron-16.png and /dev/null differ diff --git a/media/patron-17.png b/media/patron-17.png deleted file mode 100644 index f3563fad63..0000000000 Binary files a/media/patron-17.png and /dev/null differ diff --git a/media/patron-18.png b/media/patron-18.png deleted file mode 100644 index ee4ae07994..0000000000 Binary files a/media/patron-18.png and /dev/null differ diff --git a/media/patron-19.png b/media/patron-19.png deleted file mode 100644 index f69846b0f7..0000000000 Binary files a/media/patron-19.png and /dev/null differ diff --git a/media/patron-2.png b/media/patron-2.png deleted file mode 100644 index dddd820e8b..0000000000 Binary files a/media/patron-2.png and /dev/null differ diff --git a/media/patron-20.png b/media/patron-20.png deleted file mode 100644 index 24c4b6d8f8..0000000000 Binary files a/media/patron-20.png and /dev/null differ diff --git a/media/patron-21.png b/media/patron-21.png deleted file mode 100644 index 1f5a65586f..0000000000 Binary files a/media/patron-21.png and /dev/null differ diff --git a/media/patron-22.png b/media/patron-22.png deleted file mode 100644 index c2d01d8e65..0000000000 Binary files a/media/patron-22.png and /dev/null differ diff --git a/media/patron-23.png b/media/patron-23.png deleted file mode 100644 index b4f19a2fca..0000000000 Binary files a/media/patron-23.png and /dev/null differ diff --git a/media/patron-24.png b/media/patron-24.png deleted file mode 100644 index 7b8d7dd558..0000000000 Binary files a/media/patron-24.png and /dev/null differ diff --git a/media/patron-25.png b/media/patron-25.png deleted file mode 100644 index 780716741d..0000000000 Binary files a/media/patron-25.png and /dev/null differ diff --git a/media/patron-26.png b/media/patron-26.png deleted file mode 100644 index 79b65e341a..0000000000 Binary files a/media/patron-26.png and /dev/null differ diff --git a/media/patron-27.png b/media/patron-27.png deleted file mode 100644 index b73c9da7bb..0000000000 Binary files a/media/patron-27.png and /dev/null differ diff --git a/media/patron-28.png b/media/patron-28.png deleted file mode 100644 index 421855d3ee..0000000000 Binary files a/media/patron-28.png and /dev/null differ diff --git a/media/patron-29.png b/media/patron-29.png deleted file mode 100644 index 7b70133e9a..0000000000 Binary files a/media/patron-29.png and /dev/null differ diff --git a/media/patron-3.png b/media/patron-3.png deleted file mode 100644 index 24885105ae..0000000000 Binary files a/media/patron-3.png and /dev/null differ diff --git a/media/patron-30.png b/media/patron-30.png deleted file mode 100644 index 055b34308b..0000000000 Binary files a/media/patron-30.png and /dev/null differ diff --git a/media/patron-31.png b/media/patron-31.png deleted file mode 100644 index 5c3f52ed6f..0000000000 Binary files a/media/patron-31.png and /dev/null differ diff --git a/media/patron-32.png b/media/patron-32.png deleted file mode 100644 index c5bcf386ca..0000000000 Binary files a/media/patron-32.png and /dev/null differ diff --git a/media/patron-3a.png b/media/patron-3a.png deleted file mode 100644 index 24a3c3ea52..0000000000 Binary files a/media/patron-3a.png and /dev/null differ diff --git a/media/patron-4.png b/media/patron-4.png deleted file mode 100644 index 58a4992986..0000000000 Binary files a/media/patron-4.png and /dev/null differ diff --git a/media/patron-5.png b/media/patron-5.png deleted file mode 100644 index 9276de00c7..0000000000 Binary files a/media/patron-5.png and /dev/null differ diff --git a/media/patron-6.png b/media/patron-6.png deleted file mode 100644 index 45f459d1aa..0000000000 Binary files a/media/patron-6.png and /dev/null differ diff --git a/media/patron-7.png b/media/patron-7.png deleted file mode 100644 index 130ba73c72..0000000000 Binary files a/media/patron-7.png and /dev/null differ diff --git a/media/patron-8.png b/media/patron-8.png deleted file mode 100644 index c903823877..0000000000 Binary files a/media/patron-8.png and /dev/null differ diff --git a/media/patron-9.png b/media/patron-9.png deleted file mode 100644 index 0370982749..0000000000 Binary files a/media/patron-9.png and /dev/null differ diff --git a/media/patron-record-status-1.png b/media/patron-record-status-1.png deleted file mode 100644 index a631541e14..0000000000 Binary files a/media/patron-record-status-1.png and /dev/null differ diff --git a/media/patron-record-status-dark-grey.png b/media/patron-record-status-dark-grey.png deleted file mode 100644 index 3896fdd97b..0000000000 Binary files a/media/patron-record-status-dark-grey.png and /dev/null differ diff --git a/media/patron-record-status-green.png b/media/patron-record-status-green.png deleted file mode 100644 index f50907b0b3..0000000000 Binary files a/media/patron-record-status-green.png and /dev/null differ diff --git a/media/patron-record-status-light-grey.png b/media/patron-record-status-light-grey.png deleted file mode 100644 index 4c325302df..0000000000 Binary files a/media/patron-record-status-light-grey.png and /dev/null differ diff --git a/media/patron-record-status-orange.png b/media/patron-record-status-orange.png deleted file mode 100644 index fdc56e13dd..0000000000 Binary files a/media/patron-record-status-orange.png and /dev/null differ diff --git a/media/patron-record-status-purple.png b/media/patron-record-status-purple.png deleted file mode 100644 index 6a204d6d15..0000000000 Binary files a/media/patron-record-status-purple.png and /dev/null differ diff --git a/media/patron-record-status-red.png b/media/patron-record-status-red.png deleted file mode 100644 index 00d82ce50c..0000000000 Binary files a/media/patron-record-status-red.png and /dev/null differ diff --git a/media/patron-record-status-yellow.png b/media/patron-record-status-yellow.png deleted file mode 100644 index c2ba407146..0000000000 Binary files a/media/patron-record-status-yellow.png and /dev/null differ diff --git a/media/patron_summary_checkouts.jpg b/media/patron_summary_checkouts.jpg deleted file mode 100644 index 7b7c15e4f7..0000000000 Binary files a/media/patron_summary_checkouts.jpg and /dev/null differ diff --git a/media/pdf_icon.gif b/media/pdf_icon.gif deleted file mode 100644 index ca1ccfe4d9..0000000000 Binary files a/media/pdf_icon.gif and /dev/null differ diff --git a/media/pre_cat_alert.png b/media/pre_cat_alert.png deleted file mode 100644 index e48257229e..0000000000 Binary files a/media/pre_cat_alert.png and /dev/null differ diff --git a/media/precat.png b/media/precat.png deleted file mode 100644 index 9681b8e9d1..0000000000 Binary files a/media/precat.png and /dev/null differ diff --git a/media/profile-5.png b/media/profile-5.png deleted file mode 100644 index bdafbca927..0000000000 Binary files a/media/profile-5.png and /dev/null differ diff --git a/media/profile-6.png b/media/profile-6.png deleted file mode 100644 index 5e3b429aee..0000000000 Binary files a/media/profile-6.png and /dev/null differ diff --git a/media/profile-7.png b/media/profile-7.png deleted file mode 100644 index 26fec660f1..0000000000 Binary files a/media/profile-7.png and /dev/null differ diff --git a/media/receipt-10.jpg b/media/receipt-10.jpg deleted file mode 100644 index 2788ce317c..0000000000 Binary files a/media/receipt-10.jpg and /dev/null differ diff --git a/media/receipt-11.jpg b/media/receipt-11.jpg deleted file mode 100644 index e259e0fb3d..0000000000 Binary files a/media/receipt-11.jpg and /dev/null differ diff --git a/media/receipt-12.jpg b/media/receipt-12.jpg deleted file mode 100644 index d170ec81c3..0000000000 Binary files a/media/receipt-12.jpg and /dev/null differ diff --git a/media/receipt-13.jpg b/media/receipt-13.jpg deleted file mode 100644 index be2c6f3d15..0000000000 Binary files a/media/receipt-13.jpg and /dev/null differ diff --git a/media/receipt-14.jpg b/media/receipt-14.jpg deleted file mode 100644 index 2037725267..0000000000 Binary files a/media/receipt-14.jpg and /dev/null differ diff --git a/media/receipt-15.jpg b/media/receipt-15.jpg deleted file mode 100644 index 29190dcd84..0000000000 Binary files a/media/receipt-15.jpg and /dev/null differ diff --git a/media/receipt-16.png b/media/receipt-16.png deleted file mode 100644 index 4407ef85cd..0000000000 Binary files a/media/receipt-16.png and /dev/null differ diff --git a/media/receipt-17.jpg b/media/receipt-17.jpg deleted file mode 100644 index 19a7d76aa8..0000000000 Binary files a/media/receipt-17.jpg and /dev/null differ diff --git a/media/receipt-18.jpg b/media/receipt-18.jpg deleted file mode 100644 index 017d045fd5..0000000000 Binary files a/media/receipt-18.jpg and /dev/null differ diff --git a/media/receipt-19.jpg b/media/receipt-19.jpg deleted file mode 100644 index ce84686e0b..0000000000 Binary files a/media/receipt-19.jpg and /dev/null differ diff --git a/media/receipt-2.jpg b/media/receipt-2.jpg deleted file mode 100644 index 7d0d6f4526..0000000000 Binary files a/media/receipt-2.jpg and /dev/null differ diff --git a/media/receipt-20.jpg b/media/receipt-20.jpg deleted file mode 100644 index d83bfcddeb..0000000000 Binary files a/media/receipt-20.jpg and /dev/null differ diff --git a/media/receipt-21.jpg b/media/receipt-21.jpg deleted file mode 100644 index 80c7d4b49d..0000000000 Binary files a/media/receipt-21.jpg and /dev/null differ diff --git a/media/receipt-22.jpg b/media/receipt-22.jpg deleted file mode 100644 index 0c393679e9..0000000000 Binary files a/media/receipt-22.jpg and /dev/null differ diff --git a/media/receipt-23.jpg b/media/receipt-23.jpg deleted file mode 100644 index 2fca67ec78..0000000000 Binary files a/media/receipt-23.jpg and /dev/null differ diff --git a/media/receipt-24.jpg b/media/receipt-24.jpg deleted file mode 100644 index abaf8336ea..0000000000 Binary files a/media/receipt-24.jpg and /dev/null differ diff --git a/media/receipt-3.jpg b/media/receipt-3.jpg deleted file mode 100644 index f36cc405f4..0000000000 Binary files a/media/receipt-3.jpg and /dev/null differ diff --git a/media/receipt-4.jpg b/media/receipt-4.jpg deleted file mode 100644 index a69a63ebb6..0000000000 Binary files a/media/receipt-4.jpg and /dev/null differ diff --git a/media/receipt-5.jpg b/media/receipt-5.jpg deleted file mode 100644 index d73c31c5be..0000000000 Binary files a/media/receipt-5.jpg and /dev/null differ diff --git a/media/receipt-6.jpg b/media/receipt-6.jpg deleted file mode 100644 index 170e0205fb..0000000000 Binary files a/media/receipt-6.jpg and /dev/null differ diff --git a/media/receipt-7.jpg b/media/receipt-7.jpg deleted file mode 100644 index ec59453788..0000000000 Binary files a/media/receipt-7.jpg and /dev/null differ diff --git a/media/receipt-8.jpg b/media/receipt-8.jpg deleted file mode 100644 index 9c10d3331f..0000000000 Binary files a/media/receipt-8.jpg and /dev/null differ diff --git a/media/receipt-9.jpg b/media/receipt-9.jpg deleted file mode 100644 index 5564e9351f..0000000000 Binary files a/media/receipt-9.jpg and /dev/null differ diff --git a/media/record_in_house_action.png b/media/record_in_house_action.png deleted file mode 100644 index 71cfa62fb5..0000000000 Binary files a/media/record_in_house_action.png and /dev/null differ diff --git a/media/renew_action.png b/media/renew_action.png deleted file mode 100644 index d6642e2fb6..0000000000 Binary files a/media/renew_action.png and /dev/null differ diff --git a/media/renew_item.png b/media/renew_item.png deleted file mode 100644 index 75a79446e5..0000000000 Binary files a/media/renew_item.png and /dev/null differ diff --git a/media/renew_item_calendar.png b/media/renew_item_calendar.png deleted file mode 100644 index d30f3dc2f6..0000000000 Binary files a/media/renew_item_calendar.png and /dev/null differ diff --git a/media/renew_specific_date.png b/media/renew_specific_date.png deleted file mode 100644 index 21c30be152..0000000000 Binary files a/media/renew_specific_date.png and /dev/null differ diff --git a/media/retrieve_patron.png b/media/retrieve_patron.png deleted file mode 100644 index e5adee47ea..0000000000 Binary files a/media/retrieve_patron.png and /dev/null differ diff --git a/media/scv-crec.jpg b/media/scv-crec.jpg deleted file mode 100644 index b4b3360549..0000000000 Binary files a/media/scv-crec.jpg and /dev/null differ diff --git a/media/scv-distr.jpg b/media/scv-distr.jpg deleted file mode 100644 index 7ffd8ac46e..0000000000 Binary files a/media/scv-distr.jpg and /dev/null differ diff --git a/media/scv-iss.jpg b/media/scv-iss.jpg deleted file mode 100644 index e56ea80560..0000000000 Binary files a/media/scv-iss.jpg and /dev/null differ diff --git a/media/scv-rec.jpg b/media/scv-rec.jpg deleted file mode 100644 index ee492a351d..0000000000 Binary files a/media/scv-rec.jpg and /dev/null differ diff --git a/media/scv-srec.jpg b/media/scv-srec.jpg deleted file mode 100644 index 7974ad7a6a..0000000000 Binary files a/media/scv-srec.jpg and /dev/null differ diff --git a/media/scv-sub.jpg b/media/scv-sub.jpg deleted file mode 100644 index 5afc9a6475..0000000000 Binary files a/media/scv-sub.jpg and /dev/null differ diff --git a/media/server-3.png b/media/server-3.png deleted file mode 100644 index f0cfb45a87..0000000000 Binary files a/media/server-3.png and /dev/null differ diff --git a/media/server-4.png b/media/server-4.png deleted file mode 100644 index e092f4798c..0000000000 Binary files a/media/server-4.png and /dev/null differ diff --git a/media/server-5.png b/media/server-5.png deleted file mode 100644 index 2fbea3f3de..0000000000 Binary files a/media/server-5.png and /dev/null differ diff --git a/media/server-6.png b/media/server-6.png deleted file mode 100644 index 05b6ed9f0e..0000000000 Binary files a/media/server-6.png and /dev/null differ diff --git a/media/shared-template-6.png b/media/shared-template-6.png deleted file mode 100644 index 44b75a66f0..0000000000 Binary files a/media/shared-template-6.png and /dev/null differ diff --git a/media/shared-template-7.png b/media/shared-template-7.png deleted file mode 100644 index 2c52629b36..0000000000 Binary files a/media/shared-template-7.png and /dev/null differ diff --git a/media/shared-template-9.png b/media/shared-template-9.png deleted file mode 100644 index 1df47250e6..0000000000 Binary files a/media/shared-template-9.png and /dev/null differ diff --git a/media/small_logo_white.jpg b/media/small_logo_white.jpg deleted file mode 100644 index e023e0357a..0000000000 Binary files a/media/small_logo_white.jpg and /dev/null differ diff --git a/media/specify_due_date1.png b/media/specify_due_date1.png deleted file mode 100644 index ab8aa6c1c3..0000000000 Binary files a/media/specify_due_date1.png and /dev/null differ diff --git a/media/specify_due_date2.png b/media/specify_due_date2.png deleted file mode 100644 index 71df31afc2..0000000000 Binary files a/media/specify_due_date2.png and /dev/null differ diff --git a/media/staffclient-1.png b/media/staffclient-1.png deleted file mode 100644 index 3199d38741..0000000000 Binary files a/media/staffclient-1.png and /dev/null differ diff --git a/media/staffclient-2.png b/media/staffclient-2.png deleted file mode 100644 index 98d168e36f..0000000000 Binary files a/media/staffclient-2.png and /dev/null differ diff --git a/media/staffclient-3.png b/media/staffclient-3.png deleted file mode 100644 index f2d695d86a..0000000000 Binary files a/media/staffclient-3.png and /dev/null differ diff --git a/media/staffclient-4.png b/media/staffclient-4.png deleted file mode 100644 index 108afa901a..0000000000 Binary files a/media/staffclient-4.png and /dev/null differ diff --git a/media/staffclient-5.png b/media/staffclient-5.png deleted file mode 100644 index 9451695b11..0000000000 Binary files a/media/staffclient-5.png and /dev/null differ diff --git a/media/staffclient-6.png b/media/staffclient-6.png deleted file mode 100644 index 8348e63ba7..0000000000 Binary files a/media/staffclient-6.png and /dev/null differ diff --git a/media/staffclient-6a.png b/media/staffclient-6a.png deleted file mode 100644 index 02f6cef008..0000000000 Binary files a/media/staffclient-6a.png and /dev/null differ diff --git a/media/staffclient-6b.png b/media/staffclient-6b.png deleted file mode 100644 index f9ce6834a8..0000000000 Binary files a/media/staffclient-6b.png and /dev/null differ diff --git a/media/staffclient-6c.png b/media/staffclient-6c.png deleted file mode 100644 index 3908102fba..0000000000 Binary files a/media/staffclient-6c.png and /dev/null differ diff --git a/media/staffclient-6d.png b/media/staffclient-6d.png deleted file mode 100644 index f4c793e86d..0000000000 Binary files a/media/staffclient-6d.png and /dev/null differ diff --git a/media/staffclient-7.png b/media/staffclient-7.png deleted file mode 100644 index 4492a80036..0000000000 Binary files a/media/staffclient-7.png and /dev/null differ diff --git a/media/staffclient-7a.png b/media/staffclient-7a.png deleted file mode 100644 index ddc7e97266..0000000000 Binary files a/media/staffclient-7a.png and /dev/null differ diff --git a/media/staffclient-8.png b/media/staffclient-8.png deleted file mode 100644 index 91154f0985..0000000000 Binary files a/media/staffclient-8.png and /dev/null differ diff --git a/media/staffclient-9.png b/media/staffclient-9.png deleted file mode 100644 index ecec7d8199..0000000000 Binary files a/media/staffclient-9.png and /dev/null differ diff --git a/media/staffclientinstallation-proxy-putty-1.png b/media/staffclientinstallation-proxy-putty-1.png deleted file mode 100644 index 1558fb665c..0000000000 Binary files a/media/staffclientinstallation-proxy-putty-1.png and /dev/null differ diff --git a/media/staffclientinstallation-proxy-socks-1.png b/media/staffclientinstallation-proxy-socks-1.png deleted file mode 100644 index b43192b910..0000000000 Binary files a/media/staffclientinstallation-proxy-socks-1.png and /dev/null differ diff --git a/media/staffclientinstallation-proxy-socks-2.png b/media/staffclientinstallation-proxy-socks-2.png deleted file mode 100644 index 5f9088dbca..0000000000 Binary files a/media/staffclientinstallation-proxy-socks-2.png and /dev/null differ diff --git a/media/staffclientinstallation-staffclient-1.png b/media/staffclientinstallation-staffclient-1.png deleted file mode 100644 index 1c19db00f0..0000000000 Binary files a/media/staffclientinstallation-staffclient-1.png and /dev/null differ diff --git a/media/staffclientinstallation-staffclient-2.png b/media/staffclientinstallation-staffclient-2.png deleted file mode 100644 index a75f0565e0..0000000000 Binary files a/media/staffclientinstallation-staffclient-2.png and /dev/null differ diff --git a/media/staffclientinstallation-staffclient-3.png b/media/staffclientinstallation-staffclient-3.png deleted file mode 100644 index 4627d077c0..0000000000 Binary files a/media/staffclientinstallation-staffclient-3.png and /dev/null differ diff --git a/media/staffclientinstallation-staffclient-4.png b/media/staffclientinstallation-staffclient-4.png deleted file mode 100644 index 4627d077c0..0000000000 Binary files a/media/staffclientinstallation-staffclient-4.png and /dev/null differ diff --git a/media/staffclientinstallation-staffclient-workstationnames-1.png b/media/staffclientinstallation-staffclient-workstationnames-1.png deleted file mode 100644 index b219531428..0000000000 Binary files a/media/staffclientinstallation-staffclient-workstationnames-1.png and /dev/null differ diff --git a/media/staffclientinstallation-staffclient-workstationnames-2.png b/media/staffclientinstallation-staffclient-workstationnames-2.png deleted file mode 100644 index 6c70b438ef..0000000000 Binary files a/media/staffclientinstallation-staffclient-workstationnames-2.png and /dev/null differ diff --git a/media/staffclientinstallation-staffclient-workstationnames-3.png b/media/staffclientinstallation-staffclient-workstationnames-3.png deleted file mode 100644 index 7af39674bc..0000000000 Binary files a/media/staffclientinstallation-staffclient-workstationnames-3.png and /dev/null differ diff --git a/media/staffclientinstallation-tabbed-1.png b/media/staffclientinstallation-tabbed-1.png deleted file mode 100644 index d5ae3bebf7..0000000000 Binary files a/media/staffclientinstallation-tabbed-1.png and /dev/null differ diff --git a/media/survey-1.png b/media/survey-1.png deleted file mode 100644 index 536f926763..0000000000 Binary files a/media/survey-1.png and /dev/null differ diff --git a/media/survey-10.png b/media/survey-10.png deleted file mode 100644 index 80d5b85686..0000000000 Binary files a/media/survey-10.png and /dev/null differ diff --git a/media/survey-2.png b/media/survey-2.png deleted file mode 100644 index ba6a10fa93..0000000000 Binary files a/media/survey-2.png and /dev/null differ diff --git a/media/survey-3.png b/media/survey-3.png deleted file mode 100644 index 6f0afd0a73..0000000000 Binary files a/media/survey-3.png and /dev/null differ diff --git a/media/survey-4.png b/media/survey-4.png deleted file mode 100644 index 0ffc78187c..0000000000 Binary files a/media/survey-4.png and /dev/null differ diff --git a/media/survey-5.png b/media/survey-5.png deleted file mode 100644 index afafdcb54a..0000000000 Binary files a/media/survey-5.png and /dev/null differ diff --git a/media/survey-6.png b/media/survey-6.png deleted file mode 100644 index 688d1f61f4..0000000000 Binary files a/media/survey-6.png and /dev/null differ diff --git a/media/survey-7.png b/media/survey-7.png deleted file mode 100644 index 06b84fd979..0000000000 Binary files a/media/survey-7.png and /dev/null differ diff --git a/media/survey-8.png b/media/survey-8.png deleted file mode 100644 index 3a37afdf53..0000000000 Binary files a/media/survey-8.png and /dev/null differ diff --git a/media/survey-9.png b/media/survey-9.png deleted file mode 100644 index 896e527c94..0000000000 Binary files a/media/survey-9.png and /dev/null differ diff --git a/media/tip.png b/media/tip.png deleted file mode 100644 index eaabe82ea6..0000000000 Binary files a/media/tip.png and /dev/null differ diff --git a/media/transit-1.png b/media/transit-1.png deleted file mode 100644 index 92733a0c6f..0000000000 Binary files a/media/transit-1.png and /dev/null differ diff --git a/media/transit-10.png b/media/transit-10.png deleted file mode 100644 index f1c6215621..0000000000 Binary files a/media/transit-10.png and /dev/null differ diff --git a/media/transit-2.png b/media/transit-2.png deleted file mode 100644 index 30681af74f..0000000000 Binary files a/media/transit-2.png and /dev/null differ diff --git a/media/transit-3.png b/media/transit-3.png deleted file mode 100644 index 34480f066f..0000000000 Binary files a/media/transit-3.png and /dev/null differ diff --git a/media/transit-4a.png b/media/transit-4a.png deleted file mode 100644 index 143bf789fc..0000000000 Binary files a/media/transit-4a.png and /dev/null differ diff --git a/media/transit-5.png b/media/transit-5.png deleted file mode 100644 index ae889e24f0..0000000000 Binary files a/media/transit-5.png and /dev/null differ diff --git a/media/transit-6.png b/media/transit-6.png deleted file mode 100644 index c9ce4b118f..0000000000 Binary files a/media/transit-6.png and /dev/null differ diff --git a/media/transit-7.png b/media/transit-7.png deleted file mode 100644 index 8464c674ea..0000000000 Binary files a/media/transit-7.png and /dev/null differ diff --git a/media/transit-8.png b/media/transit-8.png deleted file mode 100644 index ce33b5d472..0000000000 Binary files a/media/transit-8.png and /dev/null differ diff --git a/media/transit-9.png b/media/transit-9.png deleted file mode 100644 index 8c84c420a3..0000000000 Binary files a/media/transit-9.png and /dev/null differ diff --git a/media/unified_volume_copy_creator1.jpg b/media/unified_volume_copy_creator1.jpg deleted file mode 100644 index a8b78d0ce4..0000000000 Binary files a/media/unified_volume_copy_creator1.jpg and /dev/null differ diff --git a/media/unified_volume_copy_creator2.jpg b/media/unified_volume_copy_creator2.jpg deleted file mode 100644 index 02d6df9dd8..0000000000 Binary files a/media/unified_volume_copy_creator2.jpg and /dev/null differ diff --git a/media/unified_volume_copy_creator3.jpg b/media/unified_volume_copy_creator3.jpg deleted file mode 100644 index 6a1222e586..0000000000 Binary files a/media/unified_volume_copy_creator3.jpg and /dev/null differ diff --git a/media/unified_volume_copy_creator4.jpg b/media/unified_volume_copy_creator4.jpg deleted file mode 100644 index 2033608ce3..0000000000 Binary files a/media/unified_volume_copy_creator4.jpg and /dev/null differ diff --git a/media/unified_volume_copy_creator5.jpg b/media/unified_volume_copy_creator5.jpg deleted file mode 100644 index 0813279181..0000000000 Binary files a/media/unified_volume_copy_creator5.jpg and /dev/null differ diff --git a/media/unified_volume_copy_creator6.jpg b/media/unified_volume_copy_creator6.jpg deleted file mode 100644 index 0cdbca56c4..0000000000 Binary files a/media/unified_volume_copy_creator6.jpg and /dev/null differ diff --git a/media/view-output-1.png b/media/view-output-1.png deleted file mode 100644 index 7fa0aec3a2..0000000000 Binary files a/media/view-output-1.png and /dev/null differ diff --git a/media/view-output-2.png b/media/view-output-2.png deleted file mode 100644 index b536d07234..0000000000 Binary files a/media/view-output-2.png and /dev/null differ diff --git a/media/view-output-3.png b/media/view-output-3.png deleted file mode 100644 index 12756c5376..0000000000 Binary files a/media/view-output-3.png and /dev/null differ diff --git a/media/view-output-4.png b/media/view-output-4.png deleted file mode 100644 index 54e364c3c9..0000000000 Binary files a/media/view-output-4.png and /dev/null differ diff --git a/media/view-output-5.png b/media/view-output-5.png deleted file mode 100644 index c4d9f61308..0000000000 Binary files a/media/view-output-5.png and /dev/null differ diff --git a/media/warning.png b/media/warning.png deleted file mode 100644 index cdc6568091..0000000000 Binary files a/media/warning.png and /dev/null differ diff --git a/opac/my_lists.txt b/opac/my_lists.txt deleted file mode 100644 index c6b848e868..0000000000 --- a/opac/my_lists.txt +++ /dev/null @@ -1,63 +0,0 @@ -My Lists 2.2 ------------- - -The *My Lists* feature replaces the bookbag feature that was available in versions proior to 2.2. The *My Lists* feature is a part of the Template Toolkit OPAC that is available in version 2.2. This feature enables you to create temporary and permanent lists; create and edit notes for items in lists; place holds on items in lists; and share lists via RSS feeds and CSV files. - - -*Create New Lists* - -1) Log in to your account in the OPAC. - -2) Search for titles. - -3) Choose a title to add to your list. Click *Add to My List*. - -image::media/My_Lists1.jpg[My_Lists1] - -4) Scroll up to the gray row on top of the *Search Results*. Click *View My List* - -5) Items are added to a temporary list. Your temporary list appears at the bottom of the screen. - -6) The *Actions for these items* menu on the right side of the screen demonstrates the actions that you can apply to this list. You can place holds on items in your temporary list; remove items from the list; or move selected items to a permanent list. - -To place a hold or remove items from the list, check the box adjacent to the title of the item, and select the desired function. - -To move selected items into an existing list, check the box adjacent to the title, and highlight the list in which you will store the item. - -image::media/My_Lists3.jpg[My_Lists3] - -7) If you do not want to place the item into an existing list, you can create a new list to contain the item. Enter the name of the new list, and, if desired, enter a description. - -image::media/My_Lists4.jpg[My_Lists4] - -8) Click *Submit*. - -9) The new list appears beneath the temporary list. - -10) Select the title(s) of the items that you want to add to the list, and click *Actions for these items*. Select the permanent list that you created from the drop down menu. - -image::media/My_Lists5.jpg[My_Lists5] - -11) Click *Go*. - -12) Your existing lists appear. Click on a list to view the items in the list. You can sort the items in the permanent list. You can also add, edit, and remove notes. - -13) Click *Edit* to add or edit a note. - -14). Enter desired notes, and click *Save Notes*. - -image::media/My_Lists6.jpg[My_Lists6] - -15) You can keep your list private, or you can share it. To share your list, click *Share*, and click the orange RSS icon to share through an RSS reader. You can also click *HTML View* to share your list as an HTML link. - -You can also download your list into a CSV file by clicking *Download CSV*. - -image::media/My_Lists7.jpg[My_Lists7] - - -16) When you no longer need a list, click *Delete List*. - - - - - diff --git a/release_notes.txt b/release_notes.txt deleted file mode 100644 index e382742875..0000000000 --- a/release_notes.txt +++ /dev/null @@ -1,611 +0,0 @@ -Release notes -============= -:toc: -:numbered: - -Upgrade notes -------------- - -Z39.50 Server Definitions -~~~~~~~~~~~~~~~~~~~~~~~ -Z39.50 server target definitions have been removed from the sample -`opensrf.xml.example` file. To migrate existing settings from your -`opensrf.xml` configuration file to the database, peform the -following steps: - - 1. First, set up your custom Z39.50 sources in the database. For - each entry in `z3950/services`, map the following XML paths to the - corresponding `config.z3950_source` table column as follows: -+ - ** `z3950/services/` = name - ** `///name` = label - ** `///host` = host - ** `///port` = port - ** `///db` = db - ** `///record_format` = record_format - ** `///transmission_format` = transmission_format -+ - 2. Then, for each attribute defined in the `` element for - a given service, map the following XML paths to the corresponding - `config.z3950_attr` table column as follows: -+ - ** `z3950/services/` = source - ** `///attrs/` = name - ** `///attrs//code` = code - ** `///attrs//format` = format -+ - 3. After adding the new Z39.50 sources and corresponding attributes, - you will need to log out of the staff client and log back into the - staff client to retrieve the new entry values. If a given Z39.50 - server does not work for a given attribute, pay attention to the - `truncation` column for the attribute. - - -New features ------------- - -Administration -~~~~~~~~~~~~ - -Custom Org Unit Trees -^^^^^^^^^^^^^^^^^^^^^ -Evergreen enables you to create an organizational tree that describes the -systems, branches, or other units that comprise your organization. By default, -the org unit tree that appears to patrons in the OPAC is identical to the one -that appears to users of the staff client. Using this feature, you can condense -or re-order the organizational tree into a simpler structure for patrons using -the OPAC while maintaining the complex organizational tree that is available to -users of the staff client. - -As a further enhancement, you can hide a parental org unit yet still make its -child org units visible in the OPAC. In previous versions of Evergreen, child -org units inherited the visibility setting of their parents. - -Documentation for this feature is available in the Book of Evergreen at -http://docs.evergreen-ils.org/2.2/ - -Fine Accrual on Closed Dates -^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -By default, fines accrue only on dates that the library is open. This feature -enables you to charge patrons fines on dates the library is closed. Fines -accrue during scheduled closings as well as during normal weekly closed dates. - -Documentation for this feature is available in the Book of Evergreen at -http://docs.evergreen-ils.org/2.2/ - -Target Copies for Holds at Closed Libraries -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -By default, when a patron places a hold on a title, the hold targeter will -search for copies to fill the hold only at circulating libraries that are open. -Copies at closed libraries are not targeted to fill holds. When turned on, this -feature enables Evergreen to target copies that have closed circulating -libraries to fill holds. Two new org unit settings control this feature. - -Documentation for this feature is available in the Book of Evergreen at -http://docs.evergreen-ils.org/2.2/ - -OPAC -~~~~ - -Template Toolkit OPAC (_TPAC_) -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -The basic catalog has been replaced by the Template Toolkit OPAC (_TPAC_). -Compared to the traditional catalog (_JSPAC_), TPAC uses far fewer network -calls for each page, resulting in faster loading pages. TPAC is built on the -http://template-toolkit.org[Template Toolkit] language to enable simple but -powerful customization, and supports integrated `gettext`-based translation -for strings--including placeholders and quantities--for better -internationalization support. - -The next feature release of Evergreen will make TPAC the primary catalog -and deprecate the use of the JSPAC. - -Auto Suggest in Catalog Search -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -The -http://docs.evergreen-ils.org/2.2/_auto_suggest_in_catalog_search_2.html[auto -suggest feature] suggests the completion of search terms as the user enters his -query. By default, the user will see ten suggestions although this -number is configurable at the database level. Scroll through suggestions with -your mouse, or use the arrow keys to scroll through the suggestions. Select a -suggestion to view records that are linked to this suggestion. - -This feature is not turned on by default. You must turn it on in the Admin -module. - -Copy Location Groups -^^^^^^^^^^^^^^^^^^^^ -This feature allows staff to create and name sets of copy locations to use as -a search filter in the catalog. OPAC-visible groups will display within the -library selector in the template toolkit OPAC. When a user selects a group -and performs a search, the set of results will be limited to records that have -copies in one of the copy locations within the group. Groups can live at any -level of the library hierarchy and may include copy locations from any parent -org unit or child org unit. - -For advanced users, this change includes a new Query Parser filter called -location_groups(). - -My Lists -^^^^^^^^ -The My Lists feature replaces the bookbag feature that was available in -versions proior to 2.2. This feature enables you to create temporary and -permanent lists; create and edit notes for items in lists; place holds on items -in lists; and share lists via RSS feeds and CSV files. - -Documentation for this feature is available in the Book of Evergreen at -http://docs.evergreen-ils.org/2.2/ - -SMS Text Messaging -^^^^^^^^^^^^^^^^^^ -The SMS Text Messaging feature enables users to receive hold notices via text -message. Users can opt-in to this hold notification as their default setting -for all holds, or they can receive specific hold notifications via text -message. Users can also send call numbers and copy locations via text message. - -Documentation for this feature is available in the Book of Evergreen at -http://docs.evergreen-ils.org/2.2/ - -New Patron Preferences -^^^^^^^^^^^^^^^^^^^^^^^ -Users will now have the ability to designate the following preferences in the -Template Toolkit catalog (_TPAC_): - -* A preferred search location. Unlike the default search library in JSPAC, this - setting will also control which copies display first in search results and - record detail screens. -* A preferred pickup location. -* The ability to keep a history of checked out items. -* The ability to keep a history of holds. - -Credit Card Payment via Public Catalog -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -Patrons can now use credit cards to pay fines and bills in *My Account* of the -TPAC. - -Record Detail Print and E-mail Actions -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -Implements Print and Email actions as links below the *Add to List* link -in the TPAC record detail page. - -Identify Previously-Checked-Out Items in Search Results -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -When a user is logged into the TPAC and performs a search, this feature -indicates in the results set when any of the result items were ever checked -out by the logged-in user. Items will only be tagged when the related org -setting is enabled and the user has opted in to circ history tracking. - -Patron Management -~~~~~~~~~~~~~~~~~ - -Patron Statistical Category Enhancements -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -The following enhancements have been added to patron statistical categories: - - * categories can be marked as 'required' (must be filled out when a patron is - registered) - * categories can be marked to allow or disallow user-created entries - * an entry for a given category and org unit can be marked as the default - entry. It will be automatically selected in the new patron registration - screen. - -User Settings Available from Patron Editor -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -Staff can now access and update user settings, like notification prefererences -and default pickup library, in the patron editor. - -Mark Patron E-mail or Phone as Invalid -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -Staff can mark a patron's email address or phone number as invalid in the -patron editor. The system will clear the email (or phone) field from -`actor.usr`, and [both optionally, per OU setting]: - - . create a corresponding standing penalty against the user, for staff to - notice next time they bring up said patron in the staff client; - . create a patron note. Related penalties (but not notes) will be cleared - whenever that patron's email address or phone number is updated again. - -Address Alert in Patron Registration -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -Support for comparing user addresses to alert addresses. When an address is -found, the address in question is styled (the header row turns red) and the -configured alert message is shown along the top-right, where other warnings -appear. - -Circulation -~~~~~~~~~~~ - -Telephony Improvements -^^^^^^^^^^^^^^^^^^^^^^ -Enhancements to notifications by telephony, including: - -* A feature that allows an Evergreen system to roll over failed notifcations - into new ones with a different notification method. -* Holiday awareness. System administrators can, via `cron`, schedule the - `set_pbx_holidays` script on an Evergreen system to periodically update - the PBX's table of holidays, based on a given org unit's closed date ranges. -* Smart retry. In certain situations, if you put too many callfiles into - Asterisk's spool at once, Asterisk will try to make too many calls at - once, and all such calls just fail. That is what the allocator is meant to - prevent. Smart retry is about moving calls that have been tried once, and will - be retried again later due to resulting in a busy signal or other problem, out - of the spool to make room for other calls that could be made in the meantime. - -Circulation Limit Groups & Limit Sets -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -The new *Circulation Limit Groups* interface found in the *Server -administration* menu can be thought of as _tags_ the system places on -circulations so that it can find them later. The *Limit Sets* interface found -in the *Local administration* menu defines rules for limiting the number of -active circulations a patron may have based on Circulation Modifiers and Limit -Groups. These new features support the following options: - -* Setting circ limits for circulations that have no circ modifiers. This is - useful for systems with circulation rules based on something other than - circulation modifiers (for example, *MARC type*) or for grouping items - that may have different circulation modifiers so that, for example, you - can count every video, regardless of circulation modifiers. -* The ability to set limits for a single library's items, regardless of - the checkout library. - -New Checkin Modifiers -^^^^^^^^^^^^^^^^^^^^^ -The following modifiers have been added to the check-in interface: - -* *Clear Shelf-Expired Holds*. When checking in something on the hold shelf, - run a 'Clear Shelf Process' for the specific copy ID at that library to - auto-clear any Shelf-Expired holds. -* *Retarget Local Holds*. When checking in 'in process' items that are owned by - the library, attempt to find a local hold to retarget. This is intended to - help with proper targeting of newly-cataloged items. -* *Retarget All Statuses*. Similar to 'Retarget Local Holds', this modifier will - attempt to find a local hold to retarget, regardless of the status of the - item being checked in. This modifier must be used in conjunction with the - 'Retarget Local Holds' modifier. -* *Capture Local Holds as Transits*. With this checkin modifier, any local holds - will be given an 'in transit' status instead of 'holds shelf'. The intent is - to stop the system from sending holds notifications before the item is ready - to be placed on the holds shelf. Possible use cases include Automated - Materials Handling(AMH) checkins, in which items may be sitting in a bin for a - while before landing on the holds shelf, and checkins done on closed days. - -Copy Location Alerts -^^^^^^^^^^^^^^^^^^^^ -This enhancement adds a new 'checkin_alert' column to copy locations. If true -(defaults to false), then a routing alert is generated at reshelving time for -the location. This is intended for special locations, such as 'Display', that -may require special handling, or that temporarily contain items that are not -normally in that location. - -Age Hold Protection Based on a Copy's Active Date -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -* Adds a 'Sets copy active' column to the 'Copy Statuses' interface to identify - statuses that indicate a copy is active and ready for checkout. The first - time a copy is set to one of these statuses, the system adds an 'active date' - for the copy, which can be used for reporting. -* Provides a new library setting for age hold protection to be based on the - copy's active date instead of its create date. - -Option to Place Holds on Age Protected Items -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -Allow choice of placing hold despite age protection. This alters the backend to -watch when so much as one copy failed only due to age protection. In JSPAC, an -alternate confirm message is shown. In TPAC, the failure message is changed -and override is always allowed for the hold in question. - -Force and Cataloging Recall Holds -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -Creates two new types of copy-level holds, *Force* and *Cataloging Recall*, -that cut in front of all other holds and ignore hold rules. For cataloging -recall holds, the copy's status changes to 'cataloging' when it reaches its -destination. - -Archiving Statistical Categories and Circulation-Time Copy Locations -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -Circulation-time copy locations are now archived with circulations (aged or active). - -Using the *Statistical Categories Editor*, staff can also designate statistical -categories (patron and copy) to archive with circulations. - -Browse Holds Shelf Interface Displays Canceled Holds -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -Holds that are canceled after they are placed on the holds shelf will continue -to display in this interface and will also display in the 'shelf-expired holds' -view. - -Acquisitions -~~~~~~~~~~~~ - -Vandelay Integration into Acquisitions -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -The Acquisitions Load MARC Order Record interface enables you to add MARC -records to selection lists and purchase orders and upload the records into the -catalog. The Vandelay interface enables you to create specific match points -between incoming MARC records and exisiting catalog records. Combining these -two features enables you to track on order MARC records through the -Acquisitions interface and to utilize the record matching mechanisms available -in Vandelay when importing acquisitions records. - -Documentation for this feature is available in the Book of Evergreen at -http://docs.evergreen-ils.org/2.2/ - -Receive Items from an Invoice -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -This feature enables users to receive items from an invoice. Staff can receive -individual copies, or they can receive items in batch. - -Documentation for this feature is available in the Book of Evergreen at -http://docs.evergreen-ils.org/2.2/ - -Lineitem and Copy Actions Accessible from More Interfaces -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -Users can now access lineitem actions (for example, receive, unreceive, update -barcodes, new invoice) from the acquisitions lineitem search results and -selection list interfaces. Also available on these interfaces is a link to copy -details where users can take receive actions (receive, unreceive, cancel) on -individual copies. - -Improved Displays for Provider and Fund Administration Pages -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -This enhancement provides improved support for viewing the provider and fund -administation pages. It also allows staff to use filters to find providers and -funds. - -Cataloging -~~~~~~~~~~ - -Authority Control Sets -^^^^^^^^^^^^^^^^^^^^^^ -The tags and subfields that display in authority records in Evergreen are -proscribed by control sets. The Library of Congress control set is the default -control set in all versions of Evergreen. However, in Evergreen release 2.2, -you can create customized control sets for authority records, and you can -define thesauri and authority fields for these control sets. - -Patrons and staff can browse authorities in the JSPAC. The following fields are -browsable by default: author, series, subject, title, and topic. You can add -custom browse axes in addition to these default fields. - -Documentation for this feature is available in the Book of Evergreen at -http://docs.evergreen-ils.org/2.2/ - -Batch Importing MARC Records -^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -The MARC Batch Import interface features improved matching of records and -managing of your import queue. In version 2.2, you can specify match points -between incoming and existing records to better detect matching records and -prevent record duplication. You can also create quality controls to ensure that -incoming matching records are superior in quality to existing catalog records. - -You also have new options for managing your queue. You can apply filters to -your queue, and you can generate a list of import errors. You can also print -your queue, email your queue, or export your queue as a CSV file. - -Documentation for this feature is available in the Book of Evergreen at -http://docs.evergreen-ils.org/2.2/ - -Hide Fields in Copy Editor -^^^^^^^^^^^^^^^^^^^^^^^^^^ -You can customize the *Copy Editor* for staff by hiding fields in the *Copy -Editor* that are not relevant for workflows at particular org units. Descendant -org units inherit the settings of their parents. - -Documentation for this feature is available in the Book of Evergreen at -http://docs.evergreen-ils.org/2.2/ - -Prevent Bibliographic Records from Having Attached Copies -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -To enable libraries to designate specific sets of records as only for use as -electronic resources, it is possible to configure a bibliographic source such -that physical copies or MFHD records may not be attached to records from that -source. The `config.bib_source` table now includes a new Boolean column, -`can_have_copies`, that controls this behavior. If `can_have_copies` for a -given bibliographic source is `TRUE`, then the staff client will prevent a -cataloger from adding volumes or MFHD records to records belonging to that -source. - -Documentation for this feature is available in the Book of Evergreen at -http://docs.evergreen-ils.org/2.2/ - -Overlay Existing Catalog Record via Z39.50 Import -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -You can replace an existing catalog record with a record obtained through a -Z39.50 search. No new permissions or administrative settings are needed to use -this feature. - -Documentation for this feature is available in the Book of Evergreen at -http://docs.evergreen-ils.org/2.2/ - -Restrict Z39.50 Sources by Permission Group -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -You can use a permission to restrict users' access to Z39.50 servers. You can -apply a permission to the Z39.50 servers to restrict access to that server, and -then assign that permission to users or groups so that they can access the -restricted servers. - -Documentation for this feature is available in the Book of Evergreen at -http://docs.evergreen-ils.org/2.2/ - -Switch Copy Location Name and Library Short Name in Copy Editor -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -By default, the copy editor shows the library shortname ('BR1' or 'CONS') -followed by the copy location name ('Stacks', 'Reference'). A new workstation -setting, under *Admin -> Workstation Administration -> Copy Editor: Copy -Location Name First*, enables staff to change the display so that the copy -location name is displayed first, followed by the library shortname. This may -be particularly useful for libraries that have defined one set of copy -locations at the consortial level and want to enable quick keyboard navigation -to copy locations by typing just the first letters of the copy location. - -Documentation for this feature is available in the Book of Evergreen at -http://docs.evergreen-ils.org/2.2/ - -User Activity Types -~~~~~~~~~~~~~~~~~~~ -The User Activity Types feature enables you to specify the user activity that -you want to record in the database. You can use this feature for reporting -purposes. This function will also display a last activity date in a user's -account. Currently, this feature only tracks user authentication. - -Documentation for this feature is available in the Book of Evergreen at -http://docs.evergreen-ils.org/2.2/ - -Authentication Proxy -~~~~~~~~~~~~~~~~~~ -To support integration of Evergreen with organizational authentication systems, -and to reduce the proliferation of user names and passwords, Evergreen offers -a new service called `open-ils.auth_proxy`. If you enable the service, -`open-ils.auth_proxy` supports different authentication mechanisms -that implement the `authenticate` method. You can define a chain of these -authentication mechanisms to be tried in order within the `` -element of the `opensrf.xml` configuration file, with the option of falling -back to the `native` mode that uses Evergreen's internal method of password -authentication. - -This service only provides authentication; there is no support for automatic -provisioning of accounts. To authenticate against any authentication system, -the user account must first be defined within the Evergreen system, and -authentication will be based on the user name as it exists in Evergreen. - -A sample authentication mechanism for LDAP is provided in -`Open-ILS::Application::AuthProxy::LDAP_AUTH`, and corresponding sample -attributes can be found in `opensrf.xml.example`. - -Auditor Tables -~~~~~~~~~~~~~~ -This enhancement adds user and workstation IDs to the auditor tables. It also -adds/changes auditor functions to allow for setting, getting, and clearing -auditor information, as well as adding a couple of utility functions for -updating auditors after changes to their origin columns. - -Reports -~~~~~~~ - -New Views for Reporting Sources -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -To support the creation of collection development reports, the following -reporting sources have been added: - - * 'Last Circulation or Creation Date' is a source that offers the copy ID, - the last circulation date or creation date, and the last circulation date - * 'Hold/Copy Ratio per Bib and Pickup Library' is a source that calculates - the number of holds per copy per bibliographic record, with granularity - by pickup library. - - -Staff Client Navigation -~~~~~~~~~~~~~~~~~~~~~~~ - -Customizable Toolbar -^^^^^^^^^^^^^^^^^^^^ -By default, two toolbars are available in the staff client: circulation and -cataloging. This feature enables you to customize toolbars in the staff client. -You can add buttons that will enable quick access to a variety of features. -You can create toolbars for specific org unit(s), workstation(s), or login(s). - -Documentation for this feature is available in the Book of Evergreen at -http://docs.evergreen-ils.org/2.2/ - -Double Clicking in the Staff Client -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -You can search for a patron's record, and double click on a result to access -that record. You can double click on an item in the *Holdings Maintenance* -screen to access copy information. The item is linked to the *Volume/Copy -Creator*, if you turned it on in the staff client's org unit settings. If you -did not turn on the *Volume/Copy Creator*, then the item links to the *Item -Attributes*. - -Documentation for this feature is available in the Book of Evergreen at -http://docs.evergreen-ils.org/2.2/ - -Recent Staff Searches -^^^^^^^^^^^^^^^^^^^^^ -You can view your recent searches as you perform them in the staff client. By -default, staff can view their recent searches, although the number is -configurable. This feature is only available through the staff client; it is -not available to patrons in the OPAC. - -Documentation for this feature is available in the Book of Evergreen at -http://docs.evergreen-ils.org/2.2/ - -Return to Search Results from MARC Record -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -This feature enables you to return to your title search results directly from -any view of the MARC record, including the *OPAC View*, *MARC Record*, *MARC -Edit*, and *Holdings Maintenance* views. You can use this feature to page -through records in the *MARC Record View* or *Edit* interfaces. You do not have -to return to the *OPAC View* to access title results. - -Documentation for this feature is available in the Book of Evergreen at -http://docs.evergreen-ils.org/2.2/ - -Sorting Columns -^^^^^^^^^^^^^^^ -This feature enables you to sort by multiple display columns so that you can -find easily the information that you need on a screen. You can sort display -columns on any screen that is built on a grid, such as the *Check In* screen or -the *On Shelf Pull List*. - -You can also sort the columns on the following *Administration* screens: - - * Circulation Policies - * Hold Policies - * Circulation Limit Sets - * Barcode Completion - * Acquisitions User Request List - * Vandelay Import Errors - -You can sort items in an ascending or descending order, and you can prioritize -the order in which columns will sort. - -Documentation for this feature is available in the Book of Evergreen at -http://docs.evergreen-ils.org/2.2/ - -Tab Button -^^^^^^^^^^ -This feature enables you to add a new tab to the Evergreen staff client by -clicking the *+* sign adjacent to the tab that you currently have opened. As in -previous versions, you can also add new tabs by clicking *File -> New Tab*, or -use the hotkey, *Ctrl+T*. - -Documentation for this feature is available in the Book of Evergreen at -http://docs.evergreen-ils.org/2.2/ - -Close All Tabs Shortcut -^^^^^^^^^^^^^^^^^^^^^^^ -You can use *CTRL+Click* on the close tab (*X*) button to close all tabs. - -Independent Column Configurations and Receipt Templates for Different Hold List Interfaces -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -Previously, all hold list interfaces shared the same column picker settings and -receipt templates. This enhancement creates independent settings for the -following interfaces: - -* Actions for this Record -> View Holds -* Patron Display -> Holds -* Circulation -> Browse Hold Shelf -* Circulation -> Pull List for Hold Requests - -Line Number Columns -^^^^^^^^^^^^^^^^^^^ -List displays in the staff client now have a non-sortable line number column -which displays the ordinal position of each row in the list. The first row in -such a list will always have a value of 1 in the ordinal column, no matter how -the list is sorted. There is no special handling for paged interfaces; the -first row on any given page still gets an ordinal value of 1. - -Auto-Login -^^^^^^^^^^ -Supports auto-login in the staff client by adding three new command line -parameters: - -* `-ILSuser`: user name to log in with -* `-ILSpassword`: password to use -* `-ILShost`: hostname to use - -License -------- -This work is licensed under the Creative Commons Attribution-ShareAlike 3.0 -Unported License. To view a copy of this license, visit -http://creativecommons.org/licenses/by-sa/3.0/ or send a letter to Creative -Commons, 444 Castro Street, Suite 900, Mountain View, California, 94041, USA. diff --git a/reports/README b/reports/README deleted file mode 100644 index e69de29bb2..0000000000 diff --git a/root.txt b/root.txt deleted file mode 100644 index 3a39c650b9..0000000000 --- a/root.txt +++ /dev/null @@ -1,320 +0,0 @@ -Evergreen Documentation -======================= -Documentation Interest Group -:doctype: book -:toc: -:numbered: - -Introduction -============ - -About This Documentation ------------------------- - -This guide was produced by the Evergreen Documentation Interest Group (DIG), -consisting of numerous volunteers from many different organizations. The DIG -has drawn together, edited, and supplemented pre-existing documentation -contributed by libraries and consortia running Evergreen that were kind enough -to release their documentation into the creative commons. Please see the -<> section for a full list of authors and -contributing organizations. Just like the software it describes, this guide is -a work in progress, continually revised to meet the needs of its users, so if -you find errors or omissions, please let us know, by contacting the DIG -facilitators at docs@evergreen-ils.org. - -This guide to Evergreen is intended to meet the needs of front-line library -staff, catalogers, library administrators, system administrators, and software -developers. It is organized into Parts, Chapters, and Sections addressing key -aspects of the software, beginning with the topics of broadest interest to the -largest groups of users and progressing to some of the more specialized and -technical topics of interest to smaller numbers of users. - -Copies of this guide can be accessed in PDF and HTML formats from http://docs.evergreen-ils.org/. - -About Evergreen ---------------- - -Evergreen is an open source library automation software designed to meet the -needs of the very smallest to the very largest libraries and consortia. Through -its staff interface, it facilitates the management, cataloging, and circulation -of library materials, and through its online public access interface it helps -patrons find those materials. - -The Evergreen software is freely licensed under the GNU General Public License, -meaning that it is free to download, use, view, modify, and share. It has an -active development and user community, as well as several companies offering -migration, support, hosting, and development services. - -The community’s development requirements state that Evergreen must be: - -* Stable, even under extreme load. -* Robust, and capable of handling a high volume of transactions and simultaneous users. -* Flexible, to accommodate the varied needs of libraries. -* Secure, to protect our patrons’ privacy and data. -* User-friendly, to facilitate patron and staff use of the system. - -Evergreen, which first launched in 2006 now powers over 544 libraries of every -type – public, academic, special, school, and even tribal and home libraries – -in over a dozen countries worldwide. - -// Push titles down one level. -:leveloffset: 1 - -include::release_notes.txt[] - -// Return to normal title levels. -:leveloffset: 0 - -Software Installation -===================== - - -Introduction ------------- - -This part will guide you through the installation steps installation or -upgrading your Evergreen system. It is intended for system administrators. - - -include::installation/system_requirements.txt[] - -// Push titles down one level. -:leveloffset: 1 - -include::installation/server_installation.txt[] - -// Return to normal title levels. -:leveloffset: 0 - -include::installation/server_upgrade.txt[] - -include::installation/edi_setup.txt[] - -// include::staff_client_installation.txt[] -// include::org_unit_structure_initialization.txt[] -// include::loading_data.txt[] - - -System Configuration and Customization -====================================== - -Introduction ------------- - -The Evergreen system allows a free range of customizations to every aspect of -the system. Use this part of the documentation to become familiar with the tools -for configuring the system as well as customizing the OPAC and staff client. - -// include::global_system_configuration.txt[] -// include::opac_customization.txt[] - -include::admin/template_toolkit.txt[] - -include::admin/auto_suggest_search.txt[] - -include::admin/customize_staff_client.txt[] - -// include::backing_up.txt[] - - - -Using the Staff Client -====================== - - -Introduction ------------- - -This part of the documentation deals with general Staff Client usage including -logging in, navigation and shortcuts. - - -include::admin/staff_client-tab_buttons.txt[] - -include::admin/staff_client-double_clicking.txt[] - -include::admin/staff_client-sorting_columns.txt[] - -include::admin/staff_client-recent_searches.txt[] - -include::admin/staff_client-return_to_results_from_marc.txt[] - -System Administration From the Staff Client -=========================================== - -Introduction ------------- - -This part deals with the options in the Server Administration menu found in the -staff client. - -// Follow structure from staff client system admin menu. - -include::admin/acquisitions_admin.txt[] - -include::admin/authorities.txt[] - -include::admin/cn_prefixes_and_suffixes.txt[] - -include::admin/restrict_Z39.50_sources_by_perm_group.txt[] - -include::admin/booking-admin.txt[] - -include::admin/SMS_messaging.txt[] - -include::admin/user_activity_type.txt[] - - -Local Administration -==================== - -Introduction ------------- - -This part covers the options in the Local Administration menu found in the staff -client. - -// Follow structure from staff client local admin menu. - -// Push titles down one level. -:leveloffset: 1 - -include::admin/hold_driven_recalls.txt[] - -// Return to normal title levels. -:leveloffset: 0 - -include::admin/recent_staff_searches.txt[] - -include::admin/lsa-library_settings_editor.txt[] - -include::admin/lsa-statcat.txt[] - - -Acquisitions -=========== - -include::acquisitions/introduction.txt[] - -include::acquisitions/selection_lists_po.txt[] - -include::acquisitions/receive_items_from_invoice.txt[] - -include::acquisitions/vandelay_acquisitions_integration.txt[] - - -Cataloging -========== - -Introduction ------------- - -Cataloguers should use this part for understanding the cataloguing procedures -used in Evergreen. - -include::cataloging/batch_importing_MARC.txt[] - -include::cataloging/overlay_record_3950_import.txt[] - -include::cataloging/monograph_parts.txt[] - -include::cataloging/conjoined_items.txt[] - - -Serials -======= - -include::serials/A-intro.txt[] - -include::serials/B-copy_template.txt[] - -include::serials/C-subscription-SCV.txt[] - -include::serials/D-subscription-ASCV.txt[] - -include::serials/E-edit_subscriptions.txt[] - -include::serials/F-Receiving.txt[] - -include::serials/G-Special_issue.txt[] - -include::serials/H-holdings_statements.txt[] - - -Circulation -=========== - -Introduction ------------- - -Use this section for understanding the circulation procedures in the Evergreen -system. - -include::circulation/circulating_items.txt[] - -include::circulation/booking.txt[] - -Reports -======= - -Introduction ------------- - -Learn how to create and use reports in Evergreen. - -Using the Public Access Catalog -=============================== - -Introduction ------------- - -Use this part for information about searching the Evergreen public access catalog. - -include::opac/my_lists.txt[] - -Developer Resources -=================== - -Introduction ------------- - -Developers can use this part to learn more about the programming languages, -communication protocols and standards used in Evergreen. - -// Push titles down one level. -:leveloffset: 1 - -include::development/updating_translations_launchpad.txt[] - -// Return to normal title levels. -:leveloffset: 0 - -[appendix] - -include::attributions.txt[] - -include::licensing.txt[] - -Admonitions -=========== - -Images used for Admonitions ---------------------------- - -* Note - -image::media/note.png[] - -* warning - -image::media/warning.png[] - -* caution - -image::media/caution.png[] - -* tip - -image::media/tip.png[] - - diff --git a/serials/A-intro.txt b/serials/A-intro.txt deleted file mode 100644 index b366ac991f..0000000000 --- a/serials/A-intro.txt +++ /dev/null @@ -1,30 +0,0 @@ -Serials -------- - -This documentation is intended for users who will be ordering subscriptions, distributing issues, and receiving issues in Evergreen. - -Serial Control View vs. Alternate Serial Control View -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -Serial Control View and Alternate Serial Control View offer you two views of Serials. Both views enable you to create subscriptions, add distributions, define captions, predict future issues, and receive items. Serial Control View was designed for users who work with a smaller number of issues and was designed to accommodate workflows in academic and special libraries. Alternate Serial Control View was designed for users who receive a larger number of issues and was designed for use in public libraries. - -The views are interoperable, but because the views were designed for different purposes, some differences emerge. For example, Serial Control View enables you to create and edit serials in a single tabbed interface while Alternate Serial Control View leads you through a series of steps on multiple screens. In addition, receiving functions vary between views. Both receiving interfaces enable you to batch receive issues. However, the Serials Batch Receive interface, which is associated with Alternate Serial Control View, allows for more customization of each receiving unit while the Items tab in Serial Control View allows for greater flexibility in creating multi-issue units, such as in binding serials. - -.Serials Control View and Alternate Serials Control View Comparison -[options="header"] -|==================================================================================================== -|Function |Serials Control View |Alternate Serials Control View -|Menu Style |Menu driven |Wizard oriented -|Setting Up subscription |No calendar drop downs |Includes calendar drop down -|Setting up distributions |No copy template selection |Requires the selection of a copy template -|Creating streams |No setup required |Requires streams -|Creating captions and patterns |Wizard available |Wizard available -|Adding Starting Issue |No holdings code wizard |Includes holdings code wizard -|Generate Predictions |Make predictions |Generate predictions -|Add items for special issue |No functionality |New items on issuances tab -|==================================================================================================== - -MFHD Records -~~~~~~~~~~~~ - -MARC Format for Holdings Display (MFHD) display in the PAC in addition to holding statements generated by Evergreen from subscriptions created in the Serials Control View or the Alternate Serials Control View. The MFHDs are editable as MARC but the holdings statements generated from the control view are system generated. Multiple MFHDs can be created and are tied to Organizational Units. diff --git a/serials/B-copy_template.txt b/serials/B-copy_template.txt deleted file mode 100644 index 3d0682e601..0000000000 --- a/serials/B-copy_template.txt +++ /dev/null @@ -1,43 +0,0 @@ -Copy Template for Serials -------------------------- - -A copy template enables you to specify item attributes that should be applied by default to copies of serials. You can create one copy template and apply it to multiple serials. You can also create multiple copy templates. Templates will be used in the Alternate Serial Control View or the Serial Control View. - -Create a copy template -~~~~~~~~~~~~~~~~~~~~~~ - -To create a copy template, click Admin -> Local Administration -> Copy Template Editor. - -. Enter a Name for the template. -. Select an owning library from the Owning lib drop down menu. This organization owns the copy template. A staff member with permissions at that organization can modify the copy template. The menu is populated from the organizations that you created in Admin . Server Administration . Organizational Units. -. Click the box adjacent to Circulate. If you want the item to circulate. -. Check the box adjacent to Holdable. if patrons can place holds on the item. -. Check the box adjacent to OPAC Visible. if you want patrons to be able to see the item in the OPAC after you receive it. -. Select a loan duration rule from the drop down menu. -. Select a fine level for the item from the drop down menu. -. Select a copy Location from the drop down menu. The menu is populated from the copy locations that you created in Admin . Local Administration . Copy Locations. -. Select a circ modifier from the drop down box. The menu is populated from the modifiers that you created in Admin . Server Administration . Circulation Modifiers. -. Check the box adjacent to Floating. if the item is part of a floating collection. -. Check the box adjacent to Deposit. if patrons must place a deposit on the copy before they can use it. -. Check the box adjacent to Reference. if the item is a reference item. -. If the item is in mint condition, then check the box adjacent to Mint Condition. -. Enter age protection rules in the Age Protect field. Age protection allows you to control the extent to which an item can circulate after it has been received. For example, you may want to protect new copies of a serial so that only patrons who check out the item at your branch can use it. -. Enter a message in the Alert Message field. This message will appear every time the item is checked out to a patron. -. Enter a code from the MARC fixed fields if you want to control the circulation based on the item type in the Circ as Type field. -. Enter a deposit amount if patrons must place a deposit on the copy before they can use it. -. Enter the price of the item. -. Enter the ID of the copy status in the Status field. A list of copy statuses and their IDs can be found in Admin . Server Administration . Copy Status. -. Click Save. -. Fine level and loan duration are required fields in the Copy Template Editor. - -Edit a copy template -~~~~~~~~~~~~~~~~~~~~ - -You can make changes to an existing copy template. Changes that you make to a copy template will apply to any items that you receive after you edited the template. - -. To edit a copy template, click your cursor in the row that you want to edit. The row will turn blue. -. Double-click. The copy template will appear, and you can edit the fields. -. After making changes, click Save. - -[NOTE] -From the copy template interface, you can delete copy templates that have never been used. diff --git a/serials/C-subscription-SCV.txt b/serials/C-subscription-SCV.txt deleted file mode 100644 index 4cef1f06de..0000000000 --- a/serials/C-subscription-SCV.txt +++ /dev/null @@ -1,152 +0,0 @@ - -Serials Control View --------------------- - -Serial Control View is separate from the Alternate Serial Control interface. Serial Control View enables you to manage serials in a single tabbed interface. This view also enables you to bind units. Serial Control View consists of five tabs: Items, Units, Distributions, Subscriptions, and Claims. Units and Claims are not functional in 2.0. - -Create a subscription -~~~~~~~~~~~~~~~~~~~~~ -A subscription is designed to hold all information related to a single serial title. Therefore, each library is likely to have only one subscription per serial title. - -image::media/scv-sub.jpg[Subscription] - -. Click the Subscriptions link. -. Select the branch that will own the subscription. -. Right-click or click Actions for Selected Row, and click Add Subscription. -. Enter the date that the subscription begins in the start date, and click Apply. You must enter the date in YYYY-MM-DD format. -. Enter the date that the subscription ends in the end date. This field is optional. -. Enter the difference between the nominal publishing date of an issue and the date that you expect to receive your copy in the Expected Date Offset. For example, if an issue is published the first day of each month, but you receive the copy two days prior to the publication date, then enter -2 days into this field. -. When finished, click Create Subscription(s) in the bottom right corner of the screen. -. A confirmation message appears. Click OK. - -[NOTE] -You can add notes to the subscription by clicking Subscription Notes. These notes are currently viewable only in the staff client by clicking on the Subscription Notes button. - -Create a distribution -~~~~~~~~~~~~~~~~~~~~~ - -Distributions indicate the branches that should receive copies of a serial. Distributions work together with streams to indicate the number of copies that should be sent to each branch. - -image::media/scv-distr.jpg[Distribution] - -. Click the distributions link beneath the subscription. Right click or click Actions for Selected Rows, and click Add distribution. -. Apply a new label to the distribution. It may be useful to identify the branch to which you are distributing these issues in this field. This field is not publicly visible and only appears when an item is received. There are no limits on the number of characters that can be entered in this field. -. Apply a prefix to the spine label if desired. This information will display in Serial Control View when the items are received, but it does not print on the spine label in . 0. -. Apply a suffix to the spine label if desired. This information will display in Serial Control View when the items are received, but it does not print on the spine label in . 0. -. The holding library is filled in by default and is the library to which you attached the subscription. -. The Legacy Record Entry contains the MFHD records that are attached to the bib record if the owning library is identical to the distribution's holding library. A distribution can thus be an extension of an MFHD record. Select the MFHD record from the drop down menu. -. The Receive Call Number field is empty until you receive the first item. When you receive the first item, you are prompted to enter a call number. That call number will populate this drop down menu. -. The Bind Call Number field is empty until you bind the first item. When you receive the first item, you are prompted to enter a call number. That call number will populate this drop down menu. -. Receive Unit Template - The template that should be applied to copies when they are received. Select a template from the drop down menu. -. Bind Unit Template - The template that should be applied to copies when they are bound. Select a template from the drop down menu. -. When finished, click Create Distribution(s) in the bottom right corner of the screen. -. A confirmation message appears. Click OK. - -[NOTE] -You can add notes to the distribution by clicking Distribution Notes. These notes are currently viewable only in the staff client by clicking on the Distribution Notes button. - -Create Captions and Patterns -~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -. Click the captions and patterns link beneath the subscription. Right click or click Actions for Selected Rows, and click Add Caption/Pattern. -. Apply the type which can be for basic subscription, supplements, or indices -. Apply active. Only one active caption and pattern is allowed per type -. In the Pattern Code dbox, you can enter a JSON representation of the 85X tag by hand, or you can click the Pattern CodeWizard to enter the information in a user-friendly format. - -Use the Pattern Code Wizard -^^^^^^^^^^^^^^^^^^^^^^^^^^^ -The Pattern Code Wizard enables you to create the caption of the item and add its publication information. The Wizard is composed of five pages of questions. You can use the Next and Previous navigation buttons in the top corners to flip between pages. - -To add a pattern code, click Wizard. - -Page 1: Enumerations -++++++++++++++++++++ - -image::media/cap-wiz-num.jpg[Enuperation] - -. To add an enumeration, check the box adjacent to Use enumerations.. The enumerations conform to $a-$h of the 853,854, and 855 MARC tags. -. A field for the First level will appear. Enter the enumeration for the first level. A common first level enumeration is volume, or "v." -. Click Add Enumeration. -. A field for the Second level will appear. Enter the enumeration for the second level. A common first level enumeration is number, or "no." -. Enter the number of bibliographic units per next higher level. This conforms to $u in the 853, 854, and 855 MARC tags. -. Choose the enumeration scheme from the drop down menu. This conforms to $v in the 853, 854, and 855 MARC tags. -+ -[NOTE] -You can add up to six levels of enumeration. -+ -. Add Alternate Enumeration if desired. -. When you have completed the enumerations, click Next. - - -Page 2: Calendar -++++++++++++++++ - -image::media/cap-wiz-cal.jpg[Enumeration] - -. To use months, seasons, or dates in your caption, check the box adjacent to Use calendar changes. -. Identify the point in the year at which the highest level enumeration caption changes. -. In the Type drop down menu, select the points during the year at which you want the calendar to restart. -. In the Point drop down menu, select the specific time at which you would like to change the calendar -. To add another calendar change, click Add Calendar Change. There are no limits on the number of calendar changes that you can add. -. When you have finished the calendar changes, click Next. - -Page 3: Chronology -++++++++++++++++++ - -image::media/cap-wiz-chron.jpg[Chronology] - -. To add chronological units to the captions, check the box adjacent to Use chronology captions. -. Choose a chronology for the first level. If you want to display the terms such as "year" and "month" next to the chronology caption in the catlaog, then check the box beneath Display in holding field. -. To include additional levels of chronology, click Add Chronology Caption. Each level that you add must be smaller than the previous level. -. After you have completed the chronology caption, click Next. - -Page 4: Compress and Expand Captions -++++++++++++++++++++++++++++++++++++ - -image::media/cap-wiz-freq.jpg[Compress or Expand] - -. Select the appropriate option for compressing or expanding your captions in the catalog from the compressibility and expandability drop down menu. The entries in the drop down menu correspond to the indicator codes and the subfield $w in the 853 tag. Compressibility and expandability correspond to the first indicator in the 853 tag. -. Choose the appropriate caption evaluation from the drop down menu. -. Choose the frequency of your publication from the drop down menu. For irregular frequencies, you may wish to select use number of issues per year, and enter the total number of issues that you receive each year. However, in the . 0 release, recommended practice is that you use only regular frequencies. Planned development will create an additional step to aid in the creation of irregular frequencies. -. Click Next. - -Page 5: Regularity Information -++++++++++++++++++++++++++++++ - -image::media/cap-wiz-chan.jpg[Changes] - -. If needed, check box for Use specific regularity information -. Choose the appropriate information for combined, omitted or published issues -. Choose the appropriate frequency and issue -. Add additional rows as required - -Page 5: Finish Captions and Patterns -++++++++++++++++++++++++++++++++++++ - -. To complete the wizard, click Create Pattern Code. -. Return to Subscription Details. -. Confirm that the box adjacent to Active is checked. Click Save Changes. The row is now highlighted gray instead of orange. - -Creating an Issuance -~~~~~~~~~~~~~~~~~~~~ - -The Issuances function enables you to manually create an issue. Evergreen will use the initial issue that you manually create to predict future issues. - -image::media/scv-iss.jpg[Issue] - -. Click the Issuances link beneath the subscription. Right click or click Actions for Selected Rows, and click Issuance. -. Click the holdings code and click apply. Currently there is no wizard to create this code. The wizard is only available in the Alternate Serials Control View. -. Click the Caption/Pattern selecting the appropriate patternand click apply -. Click the date published and enter date information (format YYYY-MM-DD) and click apply -. Click label, enter label and click apply -. When finished, click Create Issuance(s) in the bottom right corner of the screen. -. A confirmation message appears. Click OK. - -Generate Prediction -~~~~~~~~~~~~~~~~~~~ - -. Open the Subscriptions tab. -. Right-click or click Actions for Selected Row -> Make predictions. -. A pop up box will aks you how many items you want to predict. Enter the number, and click OK. -. A confirmation message will appear. Click OK. -. Click the Issuances link to view the predicted issues. diff --git a/serials/D-subscription-ASCV.txt b/serials/D-subscription-ASCV.txt deleted file mode 100644 index 0f0efa8d56..0000000000 --- a/serials/D-subscription-ASCV.txt +++ /dev/null @@ -1,188 +0,0 @@ -Alternate Serial Control View ------------------------------ - -Using the Alternate Serial Control View, you can create a subscription, a distribution, a stream, and a caption and pattern, and you can generate predictions and receive issues. To access Alternate Serial Control View, open a serials record, and click Actions for this Record >> Alternate Serial Control. This opens the Subscriptions interface - -. Create a subscription -. Create a distribution -. Create a a stream (within the distribution) -. Create a caption and pattern (or import from bibliographic or legacy serial records) -. Create at least the first issuance and generate predictions - -Creating a Subscription -~~~~~~~~~~~~~~~~~~~~~~~ - -A subscription is designed to hold all information related to a single serial title. Therefore, each library is likely to have only one subscription per serial title. - -image::media/ascv-sub.jpg[Creating a Subscription] - -. Add new subscriptions to a serials record that exists in the catalog. -. Create a subscription -. Click New Subscription. -. Select an owning library. The owning library indicates the organizational unit(s) whose staff can use this subscription. This menu is populated with the shortnames that you created for your libraries in the organizational units tree in Admin . Server Administration . Organizational Units. The rule of parental inheritance applies to this list. For example, if a system is made the owner of a subscription, then users, with appropriate permissions, at the branches within the system could also use this subscription. -. Enter the date that the subscription begins in the start date. Recommended practice is that you select the date from the drop down calendar although you can manually enter a date. Owning library and start date are required fields in the new subscription pop up box. -. Enter the date that the subscription ends in the end date. Recommended practice is to select a date from the drop down calendar, but you can manually enter a date, also. -. Enter the difference between the nominal publishing date of an issue and the date that you expect to receive your copy in the Expected Date Offset. For example, if an issue is published the first day of each month, but you receive the copy two days prior to the publication date, then enter -2 days into this field. -. Click Save. - -After you save the subscription, it will appear in a list with a hyperlinked ID number. Use the drop down menu at the top of the screen to view subscriptions at other organizations. - -Creating a Distribution -~~~~~~~~~~~~~~~~~~~~~~~ - -Distributions indicate the branches that should receive copies of a serial. Distributions work together with streams to indicate the number of copies that should be sent to each branch. - -image::media/ascv-distr.jpg[Creating a Distribution] - -. Click the Distributions tab. -. Click New Distribution. -. Enter a name for the distribution in the Label field. It may be useful to identify the branch to which you are distributing these issues in this field. This field is not publicly visible and only appears when an item is received. There are no limits on the number of characters that can be entered in this field. -. Select a holding library from the drop down menu. The holding library is the branch that will receive the copies. -. Select a copy template from the Receive Unit Template drop down menu. This menu is populated with the copy templates that you created in Copy Template Editor. -+ -[NOTE] -Label, Holding Library, and Receive Unit Template are required fields in the new distribution pop up box. -+ -. Ignore the fields, Unit Label Prefix and Unit Label Suffix. These fields are not functional in Alternate Serial Control View. -. Click Save. The distribution will appear in a list in the Distributions tab in the Subscription Details. - -Creating a Stream -~~~~~~~~~~~~~~~~~ - -Distributions work together with streams to indicate the number of copies that should be sent to each branch. Distributions identify the branches that should receive copies of a serial. Streams identify how many copies should be sent to each branch. Streams are intended for copies that are received on a recurring, even if irregular, basis. - -. Click the hyperlinked title of the distribution. The number of streams that have already been created for this distribution displays adjacent to the title. You can choose one of two ways to create a stream: New Stream or Create Many Streams. The New Stream button allows you to create one new stream and assign it a routing label. -. Click New Stream -. Enter a routing label so that the copy could be read by specific users or departments before the copy is shelved. The routing label appears during receiving and could be added to routing lists; it is not viewable by the public. Routing lists do not print from in 2.0. This field is optional. -. Click Save. -+ -[NOTE] -The "Create Many Streams button" allows you to create multiple streams at once, but it does not allow you to add a routing label when you create the stream. -+ -. Click Create Many Streams. -. Enter the number of streams that you want to create in the How many. Field. -. Click Create. - -Creating a Caption and Pattern -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -The Captions and Patterns wizard allows you to enter caption and pattern data as it is described by the 853, 854, and 855 MARC tags. These tags allow you to define how issues will be captioned, and how often the library receives issues of the serial. - -. Open the Subscription Details. -. Click the Captions and Patterns tab. -. Click Add Caption and Pattern. -. In the Type drop down box, select the MARC tag to which you would like to add data. -. In the Pattern Code drop down box, you can enter a JSON representation of the 85X tag by hand, or you can click the Wizard to enter the information in a user-friendly format. -. The Caption and Pattern that you create is Active by default, but you can deactivate a caption and pattern at a later time by unchecking the box. - - -[NOTE] -A subscription may have multiple captions and patterns listed in the subscripiton details, but only one Caption and Pattern can be active at any time. If you want to add multiple patterns, e.g. for Basic and Supplement, Click Add Caption and Pattern. - - -Use the Pattern Code Wizard -^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -The Pattern Code Wizard enables you to create the caption of the item and add its publication information. The Wizard is composed of five pages of questions. You can use the Next and Previous navigation buttons in the top corners to flip between pages. - -To add a pattern code, click Wizard. - -Page 1: Enumerations -++++++++++++++++++++ - -image::media/cap-wiz-num.jpg[Enuperation] - -. To add an enumeration, check the box adjacent to Use enumerations.. The enumerations conform to $a-$h of the 853,854, and 855 MARC tags. -. A field for the First level will appear. Enter the enumeration for the first level. A common first level enumeration is volume, or "v." -. Click Add Enumeration. -. A field for the Second level will appear. Enter the enumeration for the second level. A common first level enumeration is number, or "no." -. Enter the number of bibliographic units per next higher level. This conforms to $u in the 853, 854, and 855 MARC tags. -. Choose the enumeration scheme from the drop down menu. This conforms to $v in the 853, 854, and 855 MARC tags. -+ -[NOTE] -You can add up to six levels of enumeration. -+ -. Add Alternate Enumeration if desired. -. When you have completed the enumerations, click Next. - -Page 2: Calendar -++++++++++++++++ - -image::media/cap-wiz-cal.jpg[Enumeration] - -. To use months, seasons, or dates in your caption, check the box adjacent to Use calendar changes. -. Identify the point in the year at which the highest level enumeration caption changes. -. In the Type drop down menu, select the points during the year at which you want the calendar to restart. -. In the Point drop down menu, select the specific time at which you would like to change the calendar -. To add another calendar change, click Add Calendar Change. There are no limits on the number of calendar changes that you can add. -. When you have finished the calendar changes, click Next. - -Page 3: Chronology -++++++++++++++++++ - -image::media/cap-wiz-chron.jpg[Chronology] - -. To add chronological units to the captions, check the box adjacent to Use chronology captions. -. Choose a chronology for the first level. If you want to display the terms, "year" and "month" next to the chronology caption in the catlaog, then check the box beneath Display in holding field. -. To include additional levels of chronology, click Add Chronology Caption. Each level that you add must be smaller than the previous level. -. After you have completed the chronology caption, click Next. - -Page 4: Compress and Expand Captions -++++++++++++++++++++++++++++++++++++ - -image::media/cap-wiz-freq.jpg[Compress or Expand] - -. Select the appropriate option for compressing or expanding your captions in the catalog from the compressibility and expandability drop down menu. The entries in the drop down menu correspond to the indicator codes and the subfield $w in the 853 tag. Compressibility and expandability correspond to the first indicator in the 853 tag. -. Choose the appropriate caption evaluation from the drop down menu. -. Choose the frequency of your publication from the drop down menu. For irregular frequencies, you may wish to select use number of issues per year, and enter the total number of issues that you receive each year. However, in the . 0 release, recommended practice is that you use only regular frequencies. Planned development will create an additional step to aid in the creation of irregular frequencies. -. Click Next. - -Page 5: Regularity Information -++++++++++++++++++++++++++++++ - -image::media/cap-wiz-chan.jpg[Changes] - -. If needed, check box for Use specific regularity information -. Choose the appropriate information for combined, omitted or published issues -. Choose the appropriate frequency and issue -. Add additional rows as required - -Page 5: Finish Captions and Patterns -++++++++++++++++++++++++++++++++++++ - -. To complete the wizard, click Create Pattern Code. -. Return to Subscription Details. -. Confirm that the box adjacent to Active is checked. Click Save Changes. The row is now highlighted gray instead of orange. - -Creating an Issuance -~~~~~~~~~~~~~~~~~~~~ - -The Issuances tab enables you to manually create an issue. Evergreen will use the initial issue that you manually create to predict future issues. - -image::media/ascv-issues.jpg[Changes] - -. Click the Issuances tab in the Subscription Details. -. Click New Issuance. -. The Subscription, Creator, and Editor fields contain subscription and user IDs, respectively. These fields are disabled because Evergreen automatically fills in these fields. -. Enter a name for this issuance in the Label field. There are no limits on the number of characters that can be entered in this field. You may want to enter the month and year of the publication in hand. -. Enter the Date Published of the issuance that you are editing. Recommended practice is that you select the date from the drop down calendar although you can manually enter a date. If you are creating one manual issue before automatically predicting more issues, then this date should be the date of the most current issue before the prediction starts. -. Select a Caption/Pattern from the drop down menu. The numbers in the drop down menu correspond to the IDs of the caption/patterns that you created. -. The Holding Type appears by default and corresponds to the Type that you selected when you created the Caption/Pattern. -. In the holding code area of the New Issuance dialog, click Wizard. The Wizard enables you to add holdings information. -. Enter the volume of the item in hand in the v. field. -. Enter the number of the item in hand in the no. field. -. Enter the year of publication in the Year field. -. Enter the month of publication in the Month field if applicable. You must enter the calendar number of the month rather than the name of the month. For example, enter 12 if the item in hand was published in December. -. Enter the day of publication in the day field if applicable. -. Click Compile to generate the holdings code. - -Generate Item Predictions -~~~~~~~~~~~~~~~~~~~~~~~~~ - -After you manually create the first issue, Evergreen will predict future issuances. Use the Generate Predictions functionality to predict future issues. - -. Click Subscription Details -> Issuances -> Generate Predictions. -. Choose the length of time for which you want to predict issues. If you select the radio button to predict until end of subscription, then Evergreen will predict issues until the end date that you created when you created the subscription. See simplesect . 1 for more information. If you do not have an end date, select the radio button to predict a certain number of issuances, and enter a number in the field. -. Click Generate. -. Evergreen will predict a run of issuances and copies. The prediction will appear in a list. -. You can delete the first, manual issuance by clicking the check box adjacent to the issuance and clicking Delete Selected. diff --git a/serials/E-edit_subscriptions.txt b/serials/E-edit_subscriptions.txt deleted file mode 100644 index 65caf8d8b2..0000000000 --- a/serials/E-edit_subscriptions.txt +++ /dev/null @@ -1,19 +0,0 @@ -Edit Subscriptions ------------------- -Subscriptions can be edite to change the caption and pattern and other information. - -Serials Control View -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -. To access Serial Control View, open a serials record, and click Actions for this Record >> Serial Control. This opens the Subscriptions interface -. Click the subscriptions tab -. Click on the appropriate link to edit - - -Alternate Serials Control View -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -. To access Alternate Serial Control View, open a serials record, and click Actions for this Record >> Alternate Serial Control. This opens the Subscriptions interface -. Click the hyperlinked ID number to edit the subscription. -. Click on the appropriate tab to edit the information - diff --git a/serials/F-Receiving.txt b/serials/F-Receiving.txt deleted file mode 100644 index 656f202177..0000000000 --- a/serials/F-Receiving.txt +++ /dev/null @@ -1,64 +0,0 @@ -Receiving ---------- -You can receive either through the Serials Control View or in Batch Receive with the simple or advanced interface - -Serials Control View Receiving -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -image::media/scv-rec.jpg[Receiving] - -. To receive items, click the Receive radio button. In the top half of the screen, the items that have yet to be received are displayed. In the bottom half of the screen, recently received items are displayed. -. Select the branch that will receive the items from the drop down box. -. Select the issue that you want to receive. -. Select the current working unit. Click Set Current Unit, located in the lower right corner of the screen. A drop down menu will appear. - * If you want to barcode each item individually, select Auto per item. This setting is recommended for most receiving processes. - * If you want each item within a unit to share the same barcode, then select New Unit. This setting is advised for most binding processes. - * If you want the item to be received or bound into an existing item, select Recent and select the desired issue. To making a change in bound items, receive or bind the items into an already existing unit. -. Click Receive/Move Selected. -. Enter a barcode and call number if prompted to do so. -. A message confirming receipt of the item appears. Click OK. -. The screen refreshes. In the top half of the screen, the item displays a received date. In the bottom half of the screen, the item that you have just received is now at the top of the list of the received items. - -After receiving items, you can view the updated holdings in the OPAC. In this example, the legacy MFHD record and the items recently received in the serial control view display together in the MFHD statement. - -Batch Receiving -~~~~~~~~~~~~~~~ - -You can batch receive items through a simple or an advanced interface. The simple interface does not allow you to add barcodes or use the copy template. These items are also not visible in the OPAC. The advanced interface enables you to use the copy templates that you created, add barcodes, and make items OPAC visible and holdable. - -You can access both Batch Receive interfaces from two locations in the ILS. From the Subscription Details screen, you can click Batch Item Receive. You can also access these interfaces by opening the catalog record for the serial, and clicking Actions for this Record . Serials Batch Receive. - -Simple Batch Receiving -^^^^^^^^^^^^^^^^^^^^^^ -Follow these steps to receive items in batch in a simple interface. - -image::media/scv-srec.jpg[Receiving] - -. The Batch Receive interface displays issues that have not yet been received. The earliest expected issue appears at the top of the list. -. In the right lower corner, you see a check box to Create Units for Received Items. If you do not check this box, then you will receive items in simple mode. -. Click Next. -. In simple mode, the distributions that you created are displayed. They are marked received by default. If you hover over the branch name, you can view the name of the distribution and its stream. -. You can receive and add a note to each item individually, or you can perform these actions on all of the distributions and streams at once. To do so, look above the line, and enter the note that you want to apply to all copies and confirm that the box to Receive. is checked. -. Click Apply. The note should appear in the note field in each distribution. -. Then click Receive Selected Items. -. The received items are cleared from the screen. - -Advanced Batch Receiving -^^^^^^^^^^^^^^^^^^^^^^^^ -Follow these steps to receive items in batch in a simple interface. - -image::media/scv-srec.jpg[Receiving] - -. The Batch Receive interface displays issues that have not yet been received. The earliest expected issue appears at the top of the list. -. If you want to barcode each copy, display it in the catalog, and make it holdable, then check the box adjacent to Create Units for Received Items in the lower right side of the screen. -. This will allow you to utilize the copy templates and input additional information about the copy: -. Barcode - You can scan printed barcodes into the barcode field for each copy, or you can allow the system to auto-generate barcodes. To auto-generate barcodes, check the box adjacent to Auto-generate., and enter the first barcode into the barcode field in the first row of the table. Then press the Tab key. The remaining barcode fields will automatically populate with the next barcodes in sequence, including check digits. - . Circ Modifiers - The circ modifiers drop down menu is populated with the circulation modifiers that you created in Admin . Server Administration . Circulation Modifiers. If you entered a circ modifier in the copy template that you created for this subscription, then it will appear by default in the distributions. - . Call Number - Enter a call number. Any item with a barcode must also have a call number. - . Note - Add a note. There are no limits on the number of characters that can be entered in this field. The note only displays in this screen. - . Copy Location - The copy location drop down menu is populated with the copy locations that you created in Admin . Local Administration . Copy Location Editor. If you entered a copy location in the copy template that you created for this subscription, then it will appear by default in the distributions. - . Price - If you entered a price in the copy template that you created for this subscription, then it will appear by default in the distributions. You can also manually enter a price if you did not include one in the copy template. - . Receive - The boxes in the Receive Column are checked by default. Uncheck the box if you do not want to receive the item. Evergreen will retain the unreceived copies and will allow you to receive them at a later time. -. When you are ready to receive the items, click Receive Selected Items. -. The items that have been received are cleared from the Batch Receive interface. The remaining disabled item is an unreceived item. -. If the items that you received have a barcode, a copy template that was set to OPAC Visible, and are assigned a shelving location that is OPAC Visible, then you can view the received items in the catalog. Notice that the Holdings Summary has been updated to reflect the most recent addition to the holdings. diff --git a/serials/G-Special_issue.txt b/serials/G-Special_issue.txt deleted file mode 100644 index febf9bc7e7..0000000000 --- a/serials/G-Special_issue.txt +++ /dev/null @@ -1,9 +0,0 @@ -Special Issues --------------- -Currently, Setting up the special issue can only be done through the Alternate Serials Control view. - -. Create an issuance in the Serials Control View or the Alternate Serials Control View -. In the Alternate Serials Control View, click on the name of your special issue in the list of issuances. -. Click the New Items button -. Enter the appropriate information -. The item is now ready to receive. If you complete the Date Received field and change the status to received then it will receive the issue but it won't create the associated copy record whereas if you leave it blank and receive the item through the Serials Control View or Batch Receive function you can create the Copy Record at that time. diff --git a/serials/H-holdings_statements.txt b/serials/H-holdings_statements.txt deleted file mode 100644 index 2aa0c3babf..0000000000 --- a/serials/H-holdings_statements.txt +++ /dev/null @@ -1,35 +0,0 @@ -Holdings --------- - -System Generated Holdings Statement -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -As issues are received, Evergreen creates a holding statement in the OPAC based on what is set up in the Caption and Patterns of the subscription. The systems generated holdings can only be edited by changing caption and pattern information and there is no abilitiy to edit the statement as free text. - -MARC Format for Holdings Display (MFHD) -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -Evergreen users can create, edit and delete their own MFHD. - -Create an MFHD record -^^^^^^^^^^^^^^^^^^^^^ - -. Open a serial record, and in the bottom right corner above the copy information, click Add MFHD Record. You can also add the MFHD statement by clicking Actions for this Record .MFHD Holdings .Add MFHD Record. -. A message will confirm that you have created the MFHD Record. Click OK. -. Click Reload in the top left corner of the record. -. The Holdings Summary will appear. Click Edit Holdings in the right corner. -. Click Edit Record. -. The MFHD window will pop up. Enter holdings information. Click Save MFHD. -. Close the MFHD window. -. Click Reload in the top left corner of the record. The Holdings Summary will reflect the changes to the MFHD statement. - -Edit a MFHD record -^^^^^^^^^^^^^^^^^^ - -. Open a serial record, and in the Actions for this Record, click MFHD Record>>Edit MFHD Record and select the appropriate MFHD. -. Edit the MFHD -. Click Save MFHD - -Delete a MFHD Record -^^^^^^^^^^^^^^^^^^^^ - -. Open a serial record, and in the Actions for this Record, click MFHD Record>>Delete MFHD Record and select the appropriate MFHD. -. Click to confirm the deletion of the MFHD