IIIF Manifest error

[jaimemears]

"IIF Manifest Error" and “Error loading the work collection”

We know based on LC developer response that in order to correct these loading issues we'd have to " code to deal with the possibility of a 500 response and catch, retry, and notify the user etc"

We also should handle LOC IIIF manifest itself (not just the Collection reference) failing, and still pass through info from the local manifest.

[adamjarling]

So currently if there's an error loading the manifest from LOC's servers, the UI is just relaying that error message to the user. We could do one of 2 things:

1. Update the text on the error message to make it more user-friendly, or
2. Suppress the error message entirely, since some of the metadata will still load (from local Manifests)

Let me know what you'd prefer @jaimemears @CourtneyMcClellan ?

[CourtneyMcClellan]

I would say option 2, suppress the error message. Jaime, let us know if you feel differently.

…

On Fri, May 14, 2021 at 7:30 AM Adam J. Arling ***@***.***> wrote: So currently if there's an error loading the manifest from LOC's servers, the UI is just relaying that error message to the user. We could do one of 2 things: 1. Update the text on the error message to make it more user-friendly, or 2. Suppress the error message entirely, since some of the metadata will still load (from local Manifests) Let me know what you'd prefer @jaimemears <https://github.com/jaimemears> @CourtneyMcClellan <https://github.com/CourtneyMcClellan> ? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#127 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASOHXDHNE4RKPG3D7RA5SWLTNUCUHANCNFSM4425VO5Q> .

[adamjarling]

@jaimemears If you want to confirm this, I'll hide the errors (in the UI but still let them flow through to the browser console for help in debugging for your devs).