You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the API attempts to "validate" IIIF by serializing and deserializing a collection, which can help strip out unwanted fields. However, this process is slow and not truly validating the IIIF as this can lead to collections being served that aren't valid - ie missing "id" or "@context". I think for now we should ensure that all collections and manifests saved to s3 always have id + context
This ticket is to improve this behaviour
The text was updated successfully, but these errors were encountered:
Currently, the API attempts to "validate" IIIF by serializing and deserializing a collection, which can help strip out unwanted fields. However, this process is slow and not truly validating the IIIF as this can lead to collections being served that aren't valid - ie missing "id" or "@context". I think for now we should ensure that all collections and manifests saved to s3 always have id + context
This ticket is to improve this behaviour
The text was updated successfully, but these errors were encountered: