Request limit configuration is currently extremely limited:

• It applies across the whole instutition
• It is a single limit which can't be distinguished for different material types, items or kinds of requests
• It is linked only the user group of the patron.

We propose that request limit config should match loan limit config and allow for other variables:

• Application to a specific library
• Limit by item policy, location, material type, user group, statistical category and job category.

An additional improvement would be to allow some link up between request limits and loan limits. They are particularly problematic for remote storage integrations where users can keep requesting items even when their loan limit has been reached.