Problem as seen on user end: When uploading items to a Mise project, upload works well and items can be used in a Mise workspace. However, support for redisplaying those items in other IIIF contexts (external Mirador, for instance) appears problematic. IIIF drag-and-drop, and IIIF manifest, both fail to load the items in external platforms.
Further investigation shows a malformed body id at line 15 of the test manifest
This situation holds for all uploaded items in this project
As an aside, I also note that the manifest id does not conform to requirements and is likely not valid as well - see https://iiif.io/api/presentation/3.0/#id and compare with "id":"3da9bae0-01b4-45f6-8578-282a83b8b787" in the sample manifest referred to above.
blalbrit
commented
3 years ago
Problem as seen on user end: When uploading items to a Mise project, upload works well and items can be used in a Mise workspace. However, support for redisplaying those items in other IIIF contexts (external Mirador, for instance) appears problematic. IIIF drag-and-drop, and IIIF manifest, both fail to load the items in external platforms.
Examples:
Using this workspace: https://mise.stanford.edu/projects/bb1a8a9c-eb3e-41d3-8b4c-722c7d72744e/resources
the resource list appears correct, but manifests are not valid
For instance: this manifest (https://mise.stanford.edu/projects/bb1a8a9c-eb3e-41d3-8b4c-722c7d72744e/resources/7455c8ac-adb4-44f1-adc1-533a7d4c7030) does not validate in the IIIF prezi validator (https://iiif.io/api/presentation/validator/service/)
Further investigation shows a malformed body id at line 15 of the test manifest
This situation holds for all uploaded items in this project
As an aside, I also note that the manifest id does not conform to requirements and is likely not valid as well - see https://iiif.io/api/presentation/3.0/#id and compare with
"id":"3da9bae0-01b4-45f6-8578-282a83b8b787"in the sample manifest referred to above.