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
All Stanford manifests have this error, and apparently, items behind Auth are dependent upon this mismatch. So non-compliant @ids are a feature, not a bug, at Stanford.
I suppose the only recourse is to reduce the allmaps validation level, since there doesn't seem to be interest in fixing this. From what I'm told, fixing it breaks these manifests in Mirador.
The text was updated successfully, but these errors were encountered:
The manifest link (https://rosetta.slv.vic.gov.au:2083/iiif/2/IE7116075:FL21458813.jpg) forwards on to the info.json link so the info.json is correct. I think the fix would be to update the manifest but I'm not sure its invalid IIIF as after following the redirects it does deliver the correct IIIF info.json.
Here is map manifest, not behind Auth:
Here is a manifest behind Auth:
https://purl.stanford.edu/bd117rc5047/iiif/manifest
All Stanford manifests have this error, and apparently, items behind Auth are dependent upon this mismatch. So non-compliant @ids are a feature, not a bug, at Stanford.
I suppose the only recourse is to reduce the allmaps validation level, since there doesn't seem to be interest in fixing this. From what I'm told, fixing it breaks these manifests in Mirador.
The text was updated successfully, but these errors were encountered: