Adjust request limit logic so that photoduplication requests do not count against request limit.
Requests submitted for photoduplication go to Awaiting Request Processing | Awaiting Order Processing initially. Because the requests hit Awaiting Request Processing, photoduplication requests currently count against a patron's request limit until they are moved into a photoduplication queue.
Sites should have the option to choose whether photoduplication requests count against a patron's limit.
Anne Marie Lyons commented
The University of Washington would also like this feature.
Hillel Arnold commented
This may be a separate idea, but we'd actually like to be able to set a limit on photoduplication requests distinct from a limit on reading room requests. If request limits had an awareness of the request type (in addition to queues) that would be the first step to solving that problem (and would also address this issue).
Susan McElrath commented
Despite having a routing rule that moves requests from Awaiting Request Processing, which is counted towards request limits to Awaiting Duplication, which is not, some of our users are still hitting the request limit. Chris Youngblood asked if these users were trying to submit large orders from a finding aid that tried to create a bunch of separate requests at once. We think this might be the case. Chris wondered whether "the routing rule might not have been fast enough in routing the requests as they were created."
Genie Powell commented
The impact of this may be minimized since photoduplication queues are not counted in request limits by default.