
Workaround When Presentation API v2 Manifests Cannot Be Displayed in Mirador 3
Overview When loading a Presentation API v2 manifest file like the following into Mirador 3, a display error occurred. https://gist.githubusercontent.com/nakamura196/42fb6bca6a9fa137234c334cb313fc58/raw/4188ebccb7406ff5132331a4fecc4ace8bdd7ebc/ng.json Below is the display in Mirador 3. I investigated the cause and workaround, and am sharing the findings here. Cause The following error message was displayed. Despite providing IIIF v2 input, it appeared to be interpreted as v3. Error: A IIIF v3 localized property value must have an array as the value for a given language. at PropertyValue.ts:126:20 at Array.map (<anonymous>) at t.parse (PropertyValue.ts:123:29) at t.getLabel (ManifestResource.ts:35:28) at canvases.js:162:12 at index.js:67:25 at h (defaultMemoize.js:123:20) at index.js:81:40 at h (defaultMemoize.js:123:20) at Function.mapToProps (OpenSeadragonViewer.js:39:12) This appeared to occur when the canvas label was written in object format, as shown below: ...











