Closed justinlittman closed 5 years ago
How should we handle this?
This is an error on their end, correct? If so, I think we can anticipate many of these in the future. Many collections/records will go off line. Would it make sense to pass a message to the client like "Image not found. The url may have changed or may no longer be available." or something like that? @anarchivist I think you should weigh in on this as well.
It looks to me like they put up a capcha on their API to prevent robots (read "us") from using the API.
So, a couple things:
primaryImage
or primaryImageSmall
here. This object is interesting because primaryImageSmall
is actually larger than primaryImage
results in:
where
http://www.metmuseum.org/api/Collection/additionalImages?crdId=321385
resolves to: