How Preferred Funds and Locations Affect the Selection List Process

To limit the funds and locations available to staff during the selection list process, you must have the Initialize scope to funds and Initialize scope to locations Acquisitions options enabled.

By using the Preferred Funds and Preferred Locations settings, you can create a list of permissible funds and locations that are linked to a user's login. These settings affect editing only in the Selection List tab and in the Web Works Selection Lists product. Editing is affected in the following two ways.

While adding copies to orders during the selection lists process, a user who tries to enter a fund or location is shown a limited list based on the entries made in the Preferred Funds and Preferred Locations settings. The user can only enter funds and locations that appear in these settings lists.

This feature is particularly useful in multi-branch libraries that want to prevent a selector in one branch from editing an entry from another branch. Users are permitted to edit an existing entry only under either of the following circumstances.

  • Both the fund and location are in the user's authorized list.
  • One element (fund or location) has a value in the user's authorized list, and the other element has no value.

The system uses a different color to flag selections that cannot be edited based on the Preferred Locations and Preferred Funds settings for that user.

Using the Preferred Funds or Preferred Locations Settings Separately

Sierra allows you define the Preferred Locations and Preferred Funds settings separately, and does not require the use of both simultaneously. In this case, the system uses the one setting which you have defined to determine whether a user can edit that entry. If the fund or location either has no value or is included in the user's authorized list, then the user will have permission to edit.