User Standing Map Wizard

Configuration and Policies > Circulation Configuration Wizards > User Standing Map Wizard

User Standing Map Wizard

The User Standing Map policy provides libraries with the ability to control the library privileges allowed when a user is assigned a specific status (user standing). The user’s library privileges can be assigned to specific combinations of commands/user standings (status)/interface types.

For example, typically a user with a BLOCKED status may not renew material without an override from the WorkFlows client or from e-Library. However, if you configure a User Standing Map policy to allow users with a BLOCKED status to renew without an override in e-Library, when a BLOCKED users logs into the My Account feature in e-Library, he or she will be able to renew material without an override (though, any renewal done in the WorkFlows client for the same user would still require an override).

This policy affects the following circulation functions:

•

Checkouts

•

Renewals

•

Placing holds

•

Placing blanket holds

•

Cancel holds

•

Suspending holds

•

Paying bills

As with the circulation map and other map policies, the order of the map lines is important. The user standing map is read by SirsiDynix Symphony from the bottom up, where the library privileges are evaluated against the lowest lines in the map first. See Policy Operations for Map Policies.

The User Standing Map Wizard honors any existing circulation thresholds and patron override scenarios defined in the library’s policies. (For example, the renew limit override policy threshold will still display regardless of the User Standing Map policy settings.) Please consider these existing policies when creating the user standing map lines.

For examples of how this map policy can be configured, see FAQs: User Standing Map Policy Scenarios.

From the List Policies window, you can create, display, modify, copy, or remove the User Standing Map policies. Click Close to exit the wizard.

Attributes

The User Standing Map wizard displays the following attributes.

Name

This attribute uniquely identifies a specific User Standing Map policy. This name is ten characters or less, and may not include spaces or punctuation, except for dash (-), underscore (_), and dollar sign ($). Additionally, the pipe character (|) may not be used.

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.

Command

This attribute lists that circulation command(s) controlled by this map line. From the drop-down list, select one of the following: All, Blanket Hold, Checkout Item, Pay Bills, Place Hold, Remove Hold, Renew, or Suspend Holds. If you select All or leave this field blank, all commands are controlled by this map line.

User Standing

This attribute lists the User Standing policies controlled by this map line. The user standings are defined in the User Standing Policy Wizard which includes standard user statuses (such as BLOCKED or OK) as well as custom user statuses created by the library. Use the Policy List gadget to select user statuses.

Interface

This attribute lists the SirsiDynix Symphony client interfaces affected by this map line. Use the Policy List gadget to select client interfaces. The following are available values and possible usage scenarios for the client interfaces:

Value	Usage scenario
All	Applies to all client interfaces
NCIP	Applies to NCIP client
Pocket Circ	Applies to PocketCirc client
SIP2	Applies to SIP2
Staff Web	Applies to the Staff Web Client interface
UNKNOWN	Used when client interface is UNKNOWN
Webcat	Applies to e-Library (OPAC) interface
Web Services	Applies to Web Services interface
Web Services DS	Applies to Discovery Services interface (Enterprise, Portfolio)
Web Services Mobile	Applies to BookMyne interface
WorkFlows	Applies to Java WorkFlows Client interface

Action

This attribute includes the action allowed by this command/user standing/client type combination. Actions include:

•

Allow – Permits the command/user standing/client type combination.

•

Allow Override – Permits the command/user standing/client type combination, but requires an override.

•

Deny – Denies the command/user standing/client type combination.

If this field is blank, the default action is Allow.

If you assign the “Allow Override” action to a client interface that does not normally allow overrides (e-Library, for example), the command will not be allowed and will be treated as “Deny.”