Add user Activity Types documentation from Sally/ESI. Thanks!
authorrsoulliere <robert.soulliere@mohawkcollege.ca>
Sat, 12 May 2012 17:56:34 +0000 (13:56 -0400)
committerrsoulliere <robert.soulliere@mohawkcollege.ca>
Sat, 12 May 2012 17:56:34 +0000 (13:56 -0400)
admin/user_activity_type.txt [new file with mode: 0644]
media/User_Activity_Types1A.jpg [new file with mode: 0644]
media/User_Activity_Types2A.jpg [new file with mode: 0644]
root.txt

diff --git a/admin/user_activity_type.txt b/admin/user_activity_type.txt
new file mode 100644 (file)
index 0000000..979f479
--- /dev/null
@@ -0,0 +1,32 @@
+User Activity Types\r
+-------------------\r
+\r
+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.\r
+\r
+Enabling this Feature\r
+~~~~~~~~~~~~~~~~~~~~~\r
+\r
+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.\r
+\r
+The *Label* is a free text field that enables you to describe the activity that you are tracking.\r
+\r
+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.\r
+\r
+The *Event Type* describes the type of activity that Evergreen is tracking.  Currently, this feature only tracks user authentication.  \r
+\r
+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.\r
+\r
+The *Enabled* field allows you to specify which types of user activity that you would like to track.\r
+\r
+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*.\r
+\r
+image::media/User_Activity_Types1A.jpg[User_Activity_Types1A]\r
+\r
+\r
+Using this Feature\r
+~~~~~~~~~~~~~~~~~~\r
+\r
+The last activty date for user logins appears in the patron's summary.\r
+\r
+image::media/User_Activity_Types2A.jpg[User_Activity_Types2A]\r
\r
diff --git a/media/User_Activity_Types1A.jpg b/media/User_Activity_Types1A.jpg
new file mode 100644 (file)
index 0000000..69d6ab4
Binary files /dev/null and b/media/User_Activity_Types1A.jpg differ
diff --git a/media/User_Activity_Types2A.jpg b/media/User_Activity_Types2A.jpg
new file mode 100644 (file)
index 0000000..63048ca
Binary files /dev/null and b/media/User_Activity_Types2A.jpg differ
index 6b26177..88a41e3 100644 (file)
--- a/root.txt
+++ b/root.txt
@@ -124,6 +124,9 @@ include::admin/booking-admin.txt[]
 \r
 include::admin/SMS_messaging.txt[]\r
 \r
+include::admin/user_activity_type.txt[]\r
+\r
+\r
 Local Administration\r
 ====================\r
 \r