Last Activity Date Rule Wizard
Last Activity Date Rule policies control which actions result in an update to the Last Activity Date attribute of a user record. The way in which Last Activity Date rules affect or don't affect a given user is defined by the Last Activity Date Rule attribute in the user's associated User Profile policy. For more information, see User Profile Wizard.
Attributes
The Last Activity Date Rule wizard displays the following attributes:
Name
This attribute uniquely identifies a specific Last Activity Date Rule policy. This name is ten characters or less, and may not include spaces, the pipe character ( | ), or punctuation characters. However, dash (-), underscore (_), and dollar sign ($) are permitted.
Description
This attribute provides more information about the policy and its use by the library. The description may be up to 60 characters in length. Although the Description attribute may contain spaces and punctuation, the pipe character ( | ) cannot be used.
Checking Out an Item
This attribute specifies that checking out an item should update the Last Activity Date of the user receiving the checkout.
Checking In an Item
This attribute specifies that checking in an item should update the Last Activity Date of the user who had checked out the item.
Renewing an Item
This attribute specifies that renewing an item should update the Last Activity Date of the user receiving the renewal.
Placing a Hold
This attribute specifies that placing a hold on an item should update the Last Activity Date of the user obtaining the hold.
Removing a Hold
This attribute specifies that removing a hold from a user record should update the Last Activity Date of the user whose hold is removed.
Editing a Hold
This attribute specifies that editing a user's hold should update the Last Activity Date of that user. When this attribute is enabled, you can specify the scenarios under which the user's last activity date changes:
|
•
|
Only within patron clients—SirsiDynix Symphony only updates the user's Last Activity Date if the user edits a hold using a patron client (such as, for example, SirsiDynix e-Library or BLUEcloud PAC). |
|
•
|
Only within staff clients—SirsiDynix Symphony only updates the user's Last Activity Date if a library staff user edits the user's hold using a staff client (such as, for example, WorkFlows or SirsiDynix SymphonyWeb). |
|
•
|
Both—SirsiDynix Symphony updates the user's Last Activity Date when the hold is edited regardless of which client is used to do so. |
Marking an Item Lost
This attribute specifies that marking an item as lost should update the Last Activity Date of the user who had the item checked out when the item was marked as lost.
Billing a User
This attribute specifies that receiving a bill should update the Last Activity Date of the user being billed.
Paying a Bill
This attribute specifies that paying a bill should update the Last Activity Date of the user paying the bill.
Creating a User
This attribute specifies that creating a user should update the Last Activity Date of the user record being created.
Creating a Request
This attribute specifies that creating a request for an item should update the Last Activity Date of the user making the request.
Editing a Request
This attribute specifies that editing a request for an item should update the Last Activity Date of the user who had made the request.
Editing Address Information
This attribute specifies that editing a user's address should update the Last Activity Date of that user. When this attribute is enabled, you can specify the scenarios under which the user's last activity date changes:
|
•
|
Only within patron clients—SirsiDynix Symphony only updates the user's Last Activity Date if the user edits an address using a patron client (such as, for example, BLUEcloud PAC or SirsiDynix Enterprise). |
Note: Because SirsiDynix e-Library doesn't allow a patron to edit their address data directly, the Last Activity Date doesn't update when a patron submits an address change request using e-Library.
|
•
|
Only within staff clients—SirsiDynix Symphony only updates the user's Last Activity Date if a library staff user edits a user address using a staff client (such as, for example, WorkFlows or SirsiDynix SymphonyWeb). |
|
•
|
Both—SirsiDynix Symphony updates the user's Last Activity Date when the hold is edited regardless of which client is used to do so. |
Related topics
User Configuration Wizards