User Standing Policy WizardUser Standing Policy WizardThe User Standing policy allows the creation of locally-defined custom user status policies for use in user records. It also allows the modification of the messages that display for the delivered User Standing policies of OK, COLLECTION, DELINQUENT, BLOCKED and BARRED.
You may only change the Description and the Message attributes for the delivered User Standing policies (OK, COLLECTION, DELINQUENT, BLOCKED, and BARRED). The Name, Delinquency Type, and Auto-replace attributes can not be modified. The delivered User Standing policies cannot be removed.
Attributes
The User Standing policy displays the following attributes.
| • | Name |
| • | Description |
| • | Message |
| • | Delinquency Type |
| • | Auto-Replace |
This attribute uniquely identifies a specific User Standing policy. When the user status is displayed in SirsiDynix Symphony, the text specified in this attribute displays. The policy name is ten characters or less, and may not include spaces or punctuation, except for dash (-), underscore (_), and dollar sign ($). Additionally, the pipe character ( | ) cannot be used.
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.
This specifies the message that will display when a circulation transaction causes the user’s status to be displayed or changed. This message will display in the WorkFlows client and, by default, in the e-Library when the patron clicks My Account. Because the message can display to patrons, be careful when creating the message. (You can change the display of the User Status in the e-Library by modifying an environment variable.)
The message may be up to 60 characters in length.
Each locally-defined user status has one of four delinquency types: OK, DELINQUENT, BLOCKED, or BARRED. The behavior of circulation transactions is determined by the delinquency type.
| • | OK – The user has full library privileges as defined in the policy file. |
| • | COLLECTION – The user has been sent to collections. An override code is required to check out items to a user in collections. |
| • | DELINQUENT – The user has unpaid bills or overdue items. Delinquent users can still check out items and have all the other privileges of OK users, but the workstation operator will be warned that the user is delinquent. |
| • | BLOCKED – The user has unpaid bills, accrued fines, and/or a number of overdue items that reach certain thresholds defined in the policy file. An override code is required to check out items to a blocked user. |
| • | BARRED – The user cannot checkout items. A user cannot be automatically barred or unbarred. This status must be set or removed manually by a workstation operator with special privileges. |
In circulation transactions that test a user’s status, the Delinquency Type attribute of the corresponding User Standing policy is checked to see if any special action should occur, such as a message is to display, an override is required, or the transaction should be blocked. If a message is to display, the message defined in the policy’s Message attribute displays.
Indicates whether this custom user status should be replaced by delivered user statuses when a circulation transaction updates the user status, or when the Update User Delinquency Status report runs.
| • | REPLACE_ALWAYS – If a user’s status is changed manually to this custom user status, the custom user status will always be replaced with a delivered user status (when applicable) by a transaction or the report. |
| • | REPLACE_NEVER – If a user’s status is changed manually to this custom user status, the custom user status will never be replaced with a delivered user status by a transaction or the report. |
| • | REPLACE_RAISE_ONLY – If a user’s status is changed manually to this custom user status, the custom user status will only be replaced with a delivered user status by a transaction or the report if the projected delivered user status is more restrictive that the custom user status. If the projected delivered user status is equal to or less restrictive that the custom user status, the custom user status is not replaced. |
| • | REPLACE_REPORT – The user's status is set or updated by the debt collection reports when a user qualifies for collection agency. The status may also be cleared by the report when a user no longer has outstanding bills or has paid all bills. This type is only used by debt collection reports. |
Example User Standing Policies
The following are examples of User Standing policies.
For example, the library might create a NEEDS_ID Custom User Status.
The library wants to create a custom user status for patrons who have not presented IDs when they registered. The library defines a NEEDS_ID user status that will have the BLOCKED delinquency type. The NEEDS_ID User Standing policy is defined as follows.
|
Name |
NEEDS_ID |
|
Description |
Status when the user does not have ID at registration. |
|
Message |
Please make the patron present an ID before allowing checkout. |
|
Delinquency Type |
BLOCKED |
|
Auto-replace |
REPLACE_NEVER |
The following example illustrates creating a User Standing Policy for the LIBCOUNCIL Custom User Status.
The library wants to define a custom user status for members of the Library Council Board such that they will always have full library privileges, and their user accounts will never be affected by overdue items or bills. The library decides to create a LIBCOUNCIL user status that will always have the OK delinquency type. This status is not to be changed by any circulation transactions or when the Update User Delinquency Status report runs. The LIBCOUNCIL User Standing policy is created as follows.
|
Name |
LIBCOUNCIL |
|
Description |
Library Council Board Member |
|
Message |
LIBCOUNCIL - Patron is a Library Council Board Member |
|
Delinquency Type |
OK |
|
Auto-replace |
REPLACE_NEVER |
Related topics
© 2006, 2014 SirsiDynix