This proposal outlines an extension to the Patron Validation API to include an optional serviceName parameter. When provided, this value will be recorded in the Integrated Library System (ILS) transaction log, allowing us to track which service initiates each patron validation request.

Currently, the ILS transaction log records patron validations without capturing which service initiated the request. This lack of context makes it difficult to analyze traffic from third-party services (e.g., OverDrive, Hoopla) or internal applications, troubleshoot validation spikes, and make informed decisions about service contracts and resource allocation.

The proposed solution is to modify the Patron Validation API to accept an optional serviceName parameter. If the serviceName is included, the API will pass it to the ILS for logging. If omitted, the validation will proceed as normal to ensure full backward compatibility with existing integrations.

Benefits
Enhanced Analytics: Generate reports on service usage to inform vendor negotiations and collection development.
Improved Troubleshooting: Quickly identify the source of performance issues or high traffic to reduce resolution time.

Data-Driven Decisions: Use service usage patterns to guide technology investments and integrations.

Backward Compatibility: The optional parameter ensures existing applications continue to function without modification.