[open-ils-commits] [GIT] Evergreen ILS branch rel_2_4 updated. 06f89fb208a22be29deeae99f7fcc0e824be97d7

[Evergreen Git]

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  06f89fb208a22be29deeae99f7fcc0e824be97d7 (commit)
       via  3ed0711fb276d2a1c5a9a84fae062cfd0ae8f0eb (commit)
      from  b895fdf27a2a0e9f621f7f96a05a30ceb78cb5b2 (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 06f89fb208a22be29deeae99f7fcc0e824be97d7
Merge: 3ed0711 b895fdf
Author: Angela Kilsdonk <akilsdonk at esilibrary.com>
Date:   Fri Aug 9 11:24:06 2013 -0400

    Merge branch 'rel_2_4' of git.evergreen-ils.org:Evergreen into rel_2_4


commit 3ed0711fb276d2a1c5a9a84fae062cfd0ae8f0eb
Author: Angela Kilsdonk <akilsdonk at esilibrary.com>
Date:   Fri Aug 9 10:31:34 2013 -0400

    Documentation for storing Z39.50 credentials.  Added to existing file on Z39.50 permissions.
    
    Signed-off-by: Angela Kilsdonk <akilsdonk at esilibrary.com>

diff --git a/docs/admin/restrict_Z39.50_sources_by_perm_group.txt b/docs/admin/restrict_Z39.50_sources_by_perm_group.txt
index c9667ba..8ee4761 100644
--- a/docs/admin/restrict_Z39.50_sources_by_perm_group.txt
+++ b/docs/admin/restrict_Z39.50_sources_by_perm_group.txt
@@ -1,10 +1,13 @@
+Z39.50 Servers
+--------------
+
 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.
 
@@ -27,7 +30,7 @@ image::media/Restrict_Z39_50_Sources_by_Permission_Group1.jpg[]
 
 
 Restrict Z39.50 Sources by Permission Group
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 1) Click *Admin -> Server Administration -> Z39.50 Servers*
 
@@ -47,3 +50,18 @@ 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.
+
+
+Storing Z39.50 Server Credentials
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Staff have the option to apply Z39.50 login credentials to each Z39.50 server at different levels of the organizational unit hierarchy.  Credentials can be set at the library branch or system level, or for an entire consortium.  When credentials are set for a Z39.50 server, searches of the Z39.50 server will use the stored credentials.  If a staff member provides alternate credentials in the Z39.50 search interface, the supplied credentials will override the stored ones.  Staff have the ability to apply new credentials or clear existing ones in this interface.  For security purposes, it is not possible for staff to retrieve or report on passwords.
+
+
+To set up stored credentials for a Z39.50 server:
+. Go to *Admin -> Server Administration -> Z39.50 Servers*.
+. Select a *Z39.50 Source* by clicking on the hyperlinked source name.  This will take you the Z39.50 Attributes for the source.
+. At the top of the screen, select the *org unit* for which you would like to configure the credentials.  
+. Enter the *Username* and *Password*, and click *Apply Credentials*.  
+
+image::media/storing_z3950_credentials.JPG[Storing Z39.50 Credentials]
diff --git a/docs/media/storing_z3950_credentials.JPG b/docs/media/storing_z3950_credentials.JPG
new file mode 100644
index 0000000..fadaa9a
Binary files /dev/null and b/docs/media/storing_z3950_credentials.JPG differ

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

Summary of changes:
 .../restrict_Z39.50_sources_by_perm_group.txt      |   24 +++++++++++++++++--
 docs/media/storing_z3950_credentials.JPG           |  Bin 0 -> 105109 bytes
 2 files changed, 21 insertions(+), 3 deletions(-)
 create mode 100644 docs/media/storing_z3950_credentials.JPG


hooks/post-receive
-- 
Evergreen ILS