Unable to work with a url-escaped image identifier when there is no identifier field

[hashimmm]

In the case where the @id received from an image information (info.json) request contains a url-escaped image identifier component, and there is no identifier field, for example:
"@id": "scheme://host:port/prefix/url%20escaped%2Fidentifier"

Mirador seems to incorrectly specify the tilesUrl for OpenSeaDragon (even though simply creating an OpenSeaDragon viewer separately and specifying the info request url as tilesUrl will work). Mirador displays thumbnails for the given image just fine, there's only an issue when prepping info for OSD.

According to the image API specification the identifier field shouldn't be required.

This can be fixed by changing json.identifier = matches[2]; to json.identifier = decodeURIComponent(matches[2]); in getImageHostUrl in iiif.js.

[azaroth42]

+1

On Thu, Jul 17, 2014 at 12:17 AM, Hashim Muqtadir [email protected]
wrote:

In the case where the @id received from an image information (info.json)
request contains a url-escaped image identifier component, and there is no
identifier field, for example:
"@id": "scheme://host:port/prefix/url%20escaped%2Fidentifier"

Mirador seems to incorrectly specify the tilesUrl for OpenSeaDragon (even
though simply creating an OpenSeaDragon viewer separately and specifying
the info request url as tilesUrl will work). Mirador displays thumbnails
for the given image just fine, there's only an issue when prepping info for
OSD.

According to the image API specification
http://www-sul.stanford.edu/iiif/image-api/1.1/#info the identifier
field shouldn't be required.

This can be fixed by changing json.identifier = matches[2]; to json.identifier
= decodeURIComponent(matches[2]); in getImageHostUrl in iiif.js.

—
Reply to this email directly or view it on GitHub
ProjectMirador/mirador#135.

Rob Sanderson
Technology Collaboration Facilitator
Digital Library Systems and Services
Stanford, CA 94305