I'm writing with a question about the IIIF manifest for Princeton MS 9. The manifest works perfectly in a IIIF viewer (like Universal Viewer on your collection page) yet it produces some kind of error loading into a specialized manuscript collation modeling tool, VisColl. I opened a ticket for this issue with the VisColl developers and will wait to hear what they say.
If possible, can the team that manages IIIF manifests at Princeton take a look the manifest structure? All the manifests for Princeton's rare books cannot be loaded into VisColl's web tool, called VCEditor. A IIIF manifest inspector tool flags these three points about the manifest JSON:
• URL does not have correct access-control-allow-origin header: got "", expected *
• The remote server did not use the requested gzip transfer compression, which will slow access. (Content-Encoding: )
• WARNING: Setting non-standard field 'rendering' on resource of type 'sc:Manifest'
Request from Matthew Westerby, at the National Gallery of Art via Roel.
I'm writing with a question about the IIIF manifest for Princeton MS 9. The manifest works perfectly in a IIIF viewer (like Universal Viewer on your collection page) yet it produces some kind of error loading into a specialized manuscript collation modeling tool, VisColl. I opened a ticket for this issue with the VisColl developers and will wait to hear what they say. If possible, can the team that manages IIIF manifests at Princeton take a look the manifest structure? All the manifests for Princeton's rare books cannot be loaded into VisColl's web tool, called VCEditor. A IIIF manifest inspector tool flags these three points about the manifest JSON: • URL does not have correct access-control-allow-origin header: got "", expected * • The remote server did not use the requested gzip transfer compression, which will slow access. (Content-Encoding: ) • WARNING: Setting non-standard field 'rendering' on resource of type 'sc:Manifest'
Request from Matthew Westerby, at the National Gallery of Art via Roel.