Modifying ArticleReach Paging

ArticleReach paging can be configured to:

• Assign paging priority and paging groups to participating sites.
• Enable your site's patrons to request items that are locally available.
• Prevent your patrons' requests from paging at specific sites.
• Manage paged requests that cannot be filled.
• Manage requests that cannot be paged.
• Manage usage thresholds.
• Require a matching year in requests for holdings at your site.
• Use the presence of year data when determining paging list order.

Assigning Paging Priority and Paging Groups

Your ArticleReach System can assign priority and group values that help balance the paging load among participating sites. They system can be configured to page articles at:

• sites with higher priority levels before paging them at sites with lower priority levels
• sites within the requesting site's group before paging them at sites in other paging groups

To enable this feature, your Central System Administrator must provide Innovative with the following values for each participating site:

Priority	A number between 0 and 99 designating the site's priority in ArticleReach paging. The higher the value, the more likely that the site's items will be selected (for example, a site with a "25" priority displays in the paging list before a site with a "5" priority, if there are other paging order considerations). The default value is "0".
Group Number	A number between 0 and 99 that designates the site's group in ArticleReach paging. The default value is "0".

Enabling ArticleReach Requests for Locally Available Items

After matching a submitted request to a bibliographic record, ArticleReach determines whether the requested article is locally available to the patron. A requested article is considered locally available if the publication year in the request matches a year for which the patron's site has holdings.

Your library can control whether or not your patrons can request locally available items based on central P TYPE. For example, the system can be configured to enable only faculty (that is, only patrons with the central P TYPE of "Faculty") to request locally available articles.

Depending on the requesting patron's central P TYPE, the system acts as follows:

• If a patron's P TYPE can request locally available articles, the system creates a paging list that typically includes your site as the first potential lender. (The order of sites on the paging list can also be affected by additional conditions, such as year matching or paging group and/or priority.)
• If a patron's P TYPE cannot request locally available articles, the system automatically cancels the request and notifies the patron of the cancellation. The reason for this cancellation displays as "This article is available at your local library" in the patron notification message and in the Pickup Location/Delivery Information field of the ArticleReach requests display in WebPAC.

Note that if the ArticleReach Request Form displays the ForceSameSite check box, your patrons can force the system to page locally available items at your site, regardless of whether your site has enabled requesting for locally available holdings for the patron's central P TYPE. If the patron checks the ForceSameSite check box on the request form, the system creates a paging list with your site as the first potential lender.

Preventing ArticleReach Requests from Paging at Specific Sites

By default, the system creates a paging list using all sites that have appropriate holdings. Your site can specify a site (or sites) that the system excludes from any paging lists created for your patrons' requests.

Requiring a Matching Year in ArticleReach Requests

By default, the system matches an article request to holdings at your site based on the ISSN of the serial in which the article was published. Your site can require that the year entered by the patron in the article request matches a year for which your site has holdings. If you require a matching year in article requests, the system does not page a request without matching year information at your site.

Using Holdings Year Data When Determining Paging List Order

ArticleReach can consider the presence or absence of year data as a criterion for determining the position of your site in paging lists:

• If your site does not have year data in holdings statements and the system uses holdings year data as a criterion in determining paging list order, a request is more likely to page at a site with year data in its holdings statements before it pages at your site.
• If your site does not have year data in holdings statements and the system does not use holdings year data as a criterion in determining paging list order, the request is equally likely to page at your site as at a site with year data in its holdings statements.

Note that, although the presence or absence of year data functions as a primary criterion in determining paging list order, other criteria (such as site priority or paging group) are also considered in determining the order of sites in a paging list.