Error Handling

[thehabes]

It does not seem like the newberry has quite the same level of error handling. What things do we need to make sure are handled gracefully? Various common things I can think of are

• There is no manifest object, or a 500 was returned while trying to get it
• The manifest object is entirely invalid
• There is no user detected in the session
• There are no image on the canvases
• There are no lines on the canvas
• The annotations (transcription lines) do not have #xywh selectors or invalid ones
• The height and/or width of a canvas is 0
• The image on the canvas could not be resolved (some 4XX or 5XX error)
• A CRUD do the annotation store returned 4XX or 5XX (annotation store cannot be reached)
• There is no message for manifests that take upwards of 5 minutes to load
• Other various javascript or HTML client errors that result in an endless spinny

[thehabes]

@cubap says: Make a broad ajax error that returns a general statement (for type 500's). Then we don't have to handle the things individually. Maybe separate out parsing CRUD errors vs. page loading errors, but keep things generalized.

[thehabes]

I have optmized this for the newberry code.