[open-ils-commits] [GIT] Evergreen ILS branch rel_2_4 updated. 48afaf0538ec7abf7057428c46a3c74f3ad3427c

Evergreen Git git at git.evergreen-ils.org
Wed May 29 16:15:16 EDT 2013


This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Evergreen ILS".

The branch, rel_2_4 has been updated
       via  48afaf0538ec7abf7057428c46a3c74f3ad3427c (commit)
       via  dda048cf3811e00b17211aabca56792e091538e9 (commit)
       via  7a95cdd7d1a1b1ccd63f681d1fb97d8af194fabe (commit)
      from  4f409cf9870f833c3328bfb9d071d09198fb69a2 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 48afaf0538ec7abf7057428c46a3c74f3ad3427c
Author: Angela Kilsdonk <akilsdonk at esilibrary.com>
Date:   Wed May 29 15:44:56 2013 -0400

    Documentation for Best Hold Selection Sort Order
    
    Signed-off-by: Angela Kilsdonk <akilsdonk at esilibrary.com>

diff --git a/docs/admin/Best_Hold_Selection_Sort_Order.txt b/docs/admin/Best_Hold_Selection_Sort_Order.txt
new file mode 100644
index 0000000..c525116
--- /dev/null
+++ b/docs/admin/Best_Hold_Selection_Sort_Order.txt
@@ -0,0 +1,60 @@
+Best-Hold Selection Sort Order
+------------------------------
+
+Best-Hold Selection Sort Order allows libraries to configure customized rules for Evergreen to use to select the best hold to fill at opportunistic capture.  When a copy is captured for a hold upon check-in, Evergreen evaluates the holds in the system that the item could fill.  Evergreen uses a set of rules, or a Best-Hold Selection Sort Order, to determine the best hold to fill with the item.  In previous version of Evergreen, there were two sets of rules for Evergreen to use to determine the best hold to fulfill: Traditional and FIFO (First In, First Out).  Traditional uses Org Unit Proximity to identify the nearest hold to fill.  FIFO follows a strict order of first-in, first-out rules.  This feature allows new, custom Best-Hold Selection Sort Orders to be created.  Existing Best-Hold Selection Sort Orders can also be modified.
+
+
+Preconfigured Best-Hold Orders
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Evergreen comes with six preconfigured Best-Hold Selection Sort Orders to choose from:
+
+* Traditional
+* Traditional with Holds-go-home
+* Traditional with Holds-always-go-home
+* FIFO
+* FIFO with Holds-go-home
+* FIFO with Holds-always-go-home
+
+The Holds-go-home and Holds-always-go-home options allow libraries to determine how long they want to allow items to transit outside of the item’s home library, before it must return to its home library to fulfill any holds that are to be picked up there.  Libraries can set this time limit in the library setting *Holds: Max foreign-circulation time*.  The Library Settings Editor can be found under *Admin -> Local Administration -> Library Settings Editor*.  
+
+Create a New Best-Hold Selection Sort Order
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+To create a new Best-Hold Selection Sort Order, go to *Admin -> Server Administration -> Best-Hold Selection Sort Order*.  
+
+. Click *Create New*.
+. Assign your Best-Hold Selection Sort Order a *Name*.
+. Next, use the *Move Up* and *Move Down* buttons to arrange the fields in the order that you would like Evergreen to check when looking for the best hold to fill with a copy at opportunistic capture.
+. Click *Save Changes* to create your custom Best-Hold Selection Sort Order.  
+
+image::media/best_hold_sort_order1.jpg[Best-Hold Selection Sort Order]
+
+
+Edit an Existing Best-Hold Selection Sort Order
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+To edit an existing Best-Hold Selection Sort Order, go to *Admin -> Server Administration -> Best-Hold Selection Sort Order*.  
+
+. Click *Edit Existing*.
+. Choose the Best-Hold Selection Sort Order that you would like to edit from the drop down menu.
+. Next, use the *Move Up* and *Move Down* buttons to arrange the fields in the new order that you would like Evergreen to check when looking for the best hold to fill with a copy at opportunistic capture.
+. Click *Save Changes* to save your edits.  
+
+Choosing the Best-Hold Selection Sort Order
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+The Best-Hold Selection Sort Order can be set for an Org Unit in the *Library Settings Editor*.  
+
+To select the Best-Hold Selection Sort Order that your Org Unit will use:
+
+. Go to *Admin -> Local Administration -> Library Settings Editor*.  
+. Locate the setting *Holds: Best-hold selection sort order*, and click *Edit*.
+. Choose the *Context* org unit for this setting.
+. Select the Best-hold selection sort order, or *Value*, from the drop down menu.
+. Click *Update Setting*. 
+
+image::media/best_hold_sort_order2.jpg[Library Settings Editor]
+
+
+Permissions to use this Feature
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+To administer the custom Best-Hold Selection Sort Order interface, you need the following permission:
+
+* ADMIN_HOLD_CAPTURE_SORT
\ No newline at end of file
diff --git a/docs/media/best_hold_sort_order1.jpg b/docs/media/best_hold_sort_order1.jpg
new file mode 100644
index 0000000..6aba665
Binary files /dev/null and b/docs/media/best_hold_sort_order1.jpg differ
diff --git a/docs/media/best_hold_sort_order2.jpg b/docs/media/best_hold_sort_order2.jpg
new file mode 100644
index 0000000..d8e22d6
Binary files /dev/null and b/docs/media/best_hold_sort_order2.jpg differ
diff --git a/docs/root.txt b/docs/root.txt
index 46eaebe..c3215d0 100644
--- a/docs/root.txt
+++ b/docs/root.txt
@@ -180,6 +180,8 @@ include::admin/acquisitions_admin.txt[]
 
 include::admin/authorities.txt[]
 
+include::admin/Best_Hold_Selection_Sort_Order.txt[]
+
 include::admin/cn_prefixes_and_suffixes.txt[]
 
 include::admin/circulation_limit_groups.txt[]

commit dda048cf3811e00b17211aabca56792e091538e9
Author: Angela Kilsdonk <akilsdonk at esilibrary.com>
Date:   Wed May 29 15:40:19 2013 -0400

    Updated root
    
    Signed-off-by: Angela Kilsdonk <akilsdonk at esilibrary.com>

diff --git a/docs/root.txt b/docs/root.txt
index 4130f09..46eaebe 100644
--- a/docs/root.txt
+++ b/docs/root.txt
@@ -1,4 +1,4 @@
-Evergreen Documentation
+Evergreen Documentation
 =======================
 Documentation Interest Group
 :doctype: book
@@ -188,6 +188,8 @@ include::admin/restrict_Z39.50_sources_by_perm_group.txt[]
 
 include::admin/booking-admin.txt[]
 
+include::admin/Org_Unit_Proximity_Adjustments.txt[]
+
 include::admin/permissions.txt[]
 
 include::admin/SMS_messaging.txt[]

commit 7a95cdd7d1a1b1ccd63f681d1fb97d8af194fabe
Author: akilsdonk <akilsdonk at esilibrary.com>
Date:   Wed May 29 14:59:48 2013 -0400

    Org Unit Proximity Adjustment documentation
    
    Signed-off-by: akilsdonk <akilsdonk at esilibrary.com>

diff --git a/docs/admin/Org_Unit_Proximity_Adjustments.txt b/docs/admin/Org_Unit_Proximity_Adjustments.txt
new file mode 100644
index 0000000..11e235a
--- /dev/null
+++ b/docs/admin/Org_Unit_Proximity_Adjustments.txt
@@ -0,0 +1,44 @@
+Org Unit Proximity Adustments
+-----------------------------
+
+Org Unit Proximity Adustments
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Org Unit Proximity Adjustments allow libraries to indicate lending preferences for holds between libraries in an Evergreen consortium.  When a hold is placed in Evergreen, the hold targeter looks for copies that can fill the hold.  One factor that the hold targeter uses to choose the best copy to fill the hold is the distance, or proximity, between the capturing library and the pickup library for the request.  The proximity is based on the number of steps through the org tree that it takes to get from one org unit to another.    
+
+image::media/Org_Unit_Prox_Adj1.PNG[Org Unit Proximity]
+Org Unit Proximity between BR1 and BR4 = 4
+
+Org Unit Proximity Adjustments allow libraries to customize the distances between org units, which provides more control over which libraries are looked at when targeting copies to fill a hold.  Evergreen can also be configured to take Org Unit Proximity Adjustments into account during opportunistic capture through the creation of a custom Best-Hold Selection Sort Order.  See documentation <here> for more information on Best-Hold Selection Sort Order. 
+ 
+An Org Unit Proximity Adjustment can be created to tell Evergreen which libraries to look at first for copies to fill a hold or which library to look at last.  This may be useful for accounting for true transit costs or physical distances between libraries.  It can also be used to identify libraries that have special lending agreements or preferences.  Org Unit Proximity Adjustments can be created for all holds between two org units, or they can be created for holds on specific Copy Locations and Circulation Modifiers.  
+ 
+Absolute and Relative Adjustments
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Two types of proximity adjustments can be created in Evergreen: Absolute adjustments and Relative adjustments.  
+
+Absolute proximity adjustments allow you to replace the default proximity distance between two org units.  An absolute adjustment could be made to tell the hold targeter to look at a specific library or library system first to find an item to fill a hold, before looking elsewhere in the consortium.  
+ 
+Relative proximity adjustments allows the proximity between org units to be treated as closer or farther from one another than the default distance.  A relative proximity adjustment could be used to identify a library that has limited hours or slow transit times to tell the hold targeter to look at that library last for copies to fill a hold.  
+
+Create an Org Unit Proximity Adjustment
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+.To create an Org Unit Proximity Adjustment between two libraries:
+. In the Admin menu choose *Server Administration -> Org Unit Proximity Adjustments*.
+. Click *New OU Proximity Adjustment*.
+. Choose an *Item Circ Lib* from the drop down menu.  
+. Choose a *Hold Request Lib* from the drop down menu.
+. If this proximity adjustment applies to a specific copy location, select the appropriate *Copy Location*  from the drop down menu.
+. If this proximity adjustment applies to a specific material type, select the appropriate *Circ Modifier* from the drop down menu.
+. If this is an Absolute proximity adjustment, check the box next to *Absolute adjustment?*  If you leave the box blank, a relative proximity adjustment will be applied.
+. Enter the *Proximity Adjustment* between the *Item Circulating Library* and the *Request Library*.
+. Click *Save*.
+
+image::media/03/Org_Unit_Prox_Adj2.PNG[Org Unit Proximity Adjustment]
+
+This will create a one-way proximity adjustment between Org Units.  In this example this adjustment will apply to items requested at by a patron BR4 and filled at BR1.  To create the reciprocal proximity adjustment, for items requested at BR1 and filled at BR4, create a second proximity adjustment between the two Org Units.
+
+Permissions to use this Feature
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+To create Org Unit Proximity Adjustments, you will need the following permission:
+
+* ADMIN_PROXIMITY_ADJUSTMENT
\ No newline at end of file
diff --git a/docs/media/Org_Unit_Prox_Adj1.PNG b/docs/media/Org_Unit_Prox_Adj1.PNG
new file mode 100644
index 0000000..25e3377
Binary files /dev/null and b/docs/media/Org_Unit_Prox_Adj1.PNG differ
diff --git a/docs/media/Org_Unit_Prox_Adj2.PNG b/docs/media/Org_Unit_Prox_Adj2.PNG
new file mode 100644
index 0000000..9ccf7e5
Binary files /dev/null and b/docs/media/Org_Unit_Prox_Adj2.PNG differ

-----------------------------------------------------------------------

Summary of changes:
 docs/admin/Best_Hold_Selection_Sort_Order.txt |   60 +++++++++++++++++++++++++
 docs/admin/Org_Unit_Proximity_Adjustments.txt |   44 ++++++++++++++++++
 docs/media/Org_Unit_Prox_Adj1.PNG             |  Bin 0 -> 12836 bytes
 docs/media/Org_Unit_Prox_Adj2.PNG             |  Bin 0 -> 27714 bytes
 docs/media/best_hold_sort_order1.jpg          |  Bin 0 -> 68796 bytes
 docs/media/best_hold_sort_order2.jpg          |  Bin 0 -> 312206 bytes
 docs/root.txt                                 |    6 ++-
 7 files changed, 109 insertions(+), 1 deletions(-)
 create mode 100644 docs/admin/Best_Hold_Selection_Sort_Order.txt
 create mode 100644 docs/admin/Org_Unit_Proximity_Adjustments.txt
 create mode 100644 docs/media/Org_Unit_Prox_Adj1.PNG
 create mode 100644 docs/media/Org_Unit_Prox_Adj2.PNG
 create mode 100644 docs/media/best_hold_sort_order1.jpg
 create mode 100644 docs/media/best_hold_sort_order2.jpg


hooks/post-receive
-- 
Evergreen ILS


More information about the open-ils-commits mailing list