Exception codes for when R5 reports are no longer available

In recent weeks the Code Team has been talking about which error code is the best one to use when publishers stop offering Release 5 reports. Some publishers have already stopped offering R5, and more R5 services will be shut down over the coming months. This is what the Code Team recommends for those publishers.

If you are no longer offering them, then you need to deliver the following Exception when libraries request R5 reports

{
   "Code": 3031
   "Severity": "Error"
   "Message": "Usage Not Ready for Requested Dates"
   "Data": "[Publisher] has transitioned to R5.1. No R5 reports are available for periods from [YYYY-MM] onwards. See [registry record] for details."
}

Remember that R5.1 doesn’t use Severity, so you shouldn’t be including that information if you need to deliver an Exception for R5.1.

More information about errors and exceptions

We’ve published a couple of other posts about handling errors and exceptions recently. You can find them at:

• Managing empty reports
• Harvesting multiple reports