FAQs: User Standing Map Policy Scenarios
| • | Why use the User Standing Map policy? |
| • | Example 1: Creating allowances for BLOCKED users |
| • | Example 2: Creating further restrictions for DELINQUENT users |
Why use the User Standing Map policy?
Previously, when a patron had a BLOCKED delinquency type in SirsiDynix Symphony, the patron could not check out, renew, or place holds on materials without a staff member providing an override in all client interfaces (including WorkFlows, e-Library, self-check systems, and more). This presented a problem for libraries, because the blocked status did not take into account the context in which the patron was attempting to use the library. For instance, if the patron reached an overdue threshold, he would be blocked. But, if the patron saw that he was blocked in the e-Library My Account page and wanted to renew items to avoid more overdue fines, he was prevented from performing this action.
The User Standing Map wizard provides libraries with the ability to control the library privileges allowed in different SirsiDynix Symphony clients for users assigned a specific status.
By creating specific command combinations of user standing (status), interface, and action, libraries can control a user’s library privileges for checkout, renewal, paying bills, and placing and suspending holds. The library also controls which SirsiDynix Symphony client (WorkFlows, SirsiDynix e-Library, self-check, etc.) will extend or deny these privileges.
The following two examples will help illustrate how the User Standing Map wizard can be used.
Example 1: Creating allowances for BLOCKED users
If the library wants to allow users with a BLOCKED status (and BLOCKED delinquency type) to renew material in e-Library and at the Self Check machine (with all other functions working as expected when dealing with a BLOCKED user), the library would configure the User Standing Map policy as follows:
|
Field |
Value |
|
Name |
BLCKEDREN |
|
Command |
Renew |
|
User Standing |
BLOCKED |
|
Interface |
Webcat, SIP2 |
|
Action |
Allow |
Users with a BLOCKED status would then be allowed to renew material online through e-Library without an override. BLOCKED users would also be allowed to renew material from a Self Check machine without an override. Configuring the User Standing Map policy in this would allow users to renew overdue material in order to prevent the overdue fine from continuing to accrue. However, it is important to note that BLOCKED users would not be allowed to checkout new material without a staff override, nor would they be able to place a hold in e-Library.
Example 2: Creating further restrictions for DELINQUENT users
Libraries can also use the User Standing Policy wizard to create custom user statuses that can then be applied in User Standing Map policies (for details, see User Standing Policy Wizard). For example, suppose that a library creates a custom user status called STOPPED, with a DELINQUENT delinquency type. If the library wanted to use the STOPPED status to force a patron to go to the circulation desk for checkouts, holds, and renewals, the library would configure the User Standing Map policy as follows:
|
Field |
Value |
|
Name |
RENSTOP |
|
Command |
Renew |
|
User Standing |
STOPPED |
|
Interface |
Webcat, SIP2 |
|
Action |
Deny |
|
Field |
Value |
|
Name |
CHKOUTSTOP |
|
Command |
Checkout |
|
User Standing |
STOPPED |
|
Interface |
Webcat, SIP2 |
|
Action |
Deny |
|
Field |
Value |
|
Name |
HOLDSTOP |
|
Command |
Place Hold |
|
User Standing |
STOPPED |
|
Interface |
Webcat, SIP2 |
|
Action |
Deny |
Users with a STOPPED status would then have to go to the circulation desk to checkout, renew, or place holds on material. They would not be allowed to renew material online through e-Library or from self check. STOPPED users would also not be allowed to place holds using e-Library.
Related topics