Thanks, Josh. I don't think we are hitting the rate limit, since it claims to be IP based, and requests from the same IP with a different UA string work fine, while our regular access has been down for days. We have also experienced recently that LoC blocks requests with an "LWP" UA string, so this is apparently becoming more common as a basic means to block scripted harvesters/attacks.
As for the more direct cover link, I'd be curious to see whether it follows the same "FRBR"-ish logic allowed in the volumes API. It seems like we may have gone down that road before, but switched to the volumes API to increase the odds of finding some cover, even if for a different edition, but maybe I am remembering something else (Google books API, etc.).
Thanks, Josh. I don't think we are hitting the rate limit, since it claims to be IP based, and requests from the same IP with a different UA string work fine, while our regular access has been down for days. We have also experienced recently that LoC blocks requests with an "LWP" UA string, so this is apparently becoming more common as a basic means to block scripted harvesters/attacks.
As for the more direct cover link, I'd be curious to see whether it follows the same "FRBR"-ish logic allowed in the volumes API. It seems like we may have gone down that road before, but switched to the volumes API to increase the odds of finding some cover, even if for a different edition, but maybe I am remembering something else (Google books API, etc.).