Closed adamjarling closed 6 years ago
@mcwhitaker Should the type be "Image" instead of "dcTypes:Image"? That's what I'm seeing in the 3.0 docs: http://prezi3.iiif.io/api/presentation/3.0/#thumbnail. Or is the 3.0 spec wrong on this point?
@cjcolvar I don't know the answer to your question and I can't get to the prezi 3 documentation right now (site must be having problems).
I see many manifests with dcTypes, but they are prezi 2. We have not explicitly talked about that change in the A/V meetings, but there have been other community calls where prezi 3 has been discussed, so you may be right. But without having access to the documentation, I can't tell.
@mcwhitaker @cjcolvar Are you both able to open this link? ( http://prezi3.iiif.io/api/presentation/3.0/#thumbnail ) For past 2 days I cannot open it for some reason.
This site can’t be reached
prezi3.iiif.io’s server DNS address could not be found.
Search Google for prezi 3 iiif io api presentation
ERR_NAME_NOT_RESOLVED
@mcwhitaker Quick question on: http://dlib.indiana.edu/iiif_av/lunchroom_manners/lunchroom_manners_v4.json
Here structures
is not at the root of the Manifest, but nested in a canvases
array element. Is this valid? I'm trying to follow the Object model here (http://iiif.io/api/presentation/2.1/#b-summary-of-metadata-requirements), to see what's legal where, in order to keep the parser logic from ballooning. Not sure if those tables at the bottom are just for Presentation API 2.0, or if they carry over to 3.0..., or quite possibly I'm just reading them wrong:)
@adamjarling From what I can tell from the prezi 3 spec that manifest is invalid. canvases
should be items
and structures
should be at the root.
@adamjarling good catch! I have fixed it. It was a problem when adding ] and }...
plus the canvas->items change from v2 to v3
@mcwhitaker @davidschober @joncameron @cjcolvar
Note this currently only works for the specific instance of thumbnails present in: http://dlib.indiana.edu/iiif_av/lunchroom_manners/lunchroom_manners_v4.json
And to get it work at: https://avalonmediasystem.github.io/avalon-iiif-player/build/, the manifest file will need to be updated so any http://
are replaced with https://
@cjcolvar has added the /manifest URI option to mallorn, and I'm working now on updating the parsing to handle those generated manifests (ie. https://mallorn.dlib.indiana.edu/media_objects/0c483j54d/manifest). There will be pretty big (and better) changes for the parser, especially if the Mallorn manifests are more in line with what Avalon will provide. Perhaps we'll have a better idea after the next few days out here.
The takeaway here (perhaps there's a better place to note this than in this ticket), is that I'm working on updating the parsing functionality, and the MEJS player integration, so it's more in line with what we'll actually use in an Avalon production setting.
@adamjarling I have changed http to https on the v4 manifest. I get a "Manifest URL Error - error" when I try it in the player.
Description
Add support in the IIIF player / parser for
thumbnail
property. Example manifest created by @mcwhitaker here: http://dlib.indiana.edu/iiif_av/lunchroom_manners/lunchroom_manners_v4.jsonTasks
thumbnail
value if it exists from a manifest canvas object.@davidschober @joncameron FYI adding this to the sprint.