As a user, I would like to have the ability to automatically download COUNTER reports by using the eUsage application's harvester scheduling process, even if the service is busy at the provider and the COUNTER reports are not available until later.
Use Case / Example
Sometimes the endpoints for requesting COUNTER reports from the provider are very busy. The service is then too busy to execute the incoming request from the harvester.
The services return a response with the CoP exception code 1010 for each requested report to inform the client about the server status. The client must then retry the request after a reasonable time.
Example of a response where requested reports received the information on CoP 1010:
Concept
If the response from the providers endpoint is that the service is busy (exception code 1010):
UI: Mark the requested report with Orange/exclamation mark (no change)
Backend: Attempt to retrieve the requested report again after a few hours without counting up the failed attempts.
See also CoP Handling Errors and Exceptions:
Acceptance criterias (UAT)
As a user, I can download COUNTER reports automatically through the eUsage application's harvester scheduling process, even if the service endpoint is busy from the provider and the COUNTER reports are not available until later.
Description
As a user, I would like to have the ability to automatically download COUNTER reports by using the eUsage application's harvester scheduling process, even if the service is busy at the provider and the COUNTER reports are not available until later.
Use Case / Example
Sometimes the endpoints for requesting COUNTER reports from the provider are very busy. The service is then too busy to execute the incoming request from the harvester.
The services return a response with the CoP exception code 1010 for each requested report to inform the client about the server status. The client must then retry the request after a reasonable time.
Example of a response where requested reports received the information on CoP 1010:
Concept
If the response from the providers endpoint is that the service is busy (exception code 1010):
UI: Mark the requested report with Orange/exclamation mark (no change)
Backend: Attempt to retrieve the requested report again after a few hours without counting up the failed attempts.
See also CoP Handling Errors and Exceptions:
Acceptance criterias (UAT)
As a user, I can download COUNTER reports automatically through the eUsage application's harvester scheduling process, even if the service endpoint is busy from the provider and the COUNTER reports are not available until later.