-
Update existing Create endpoint to support creating IIIF Collections
part 1:
https://deploy-preview-3--dlcs-docs.netlify.app/api-doc/iiif#example-create-a-iiif-collection-within-a-storage-collection…
-
For scanned maps we serve a version 3 manifest at a path like v3/manifest. For audio we just serve v3 manifests from the original path.
Should we choose one of these two approaches over the other?
Ar…
-
For audiobooks, or other media with multiple parts, like this manifest:
https://iiif.archive.org/iiif/3/beowulf_te_librivox/manifest.json
It would be useful to have the IIIF property `behaviour` s…
-
See https://iiif.io/api/presentation/3.0/#behavior
This should be overrideable via config.
-
All the examples at https://mirador-download-plugin.netlify.app/ use IIIF presentation level 2 examples. Manifests using IIIF level 3 instead don't work - the plugin loads but no actual page gets show…
-
## Description
Avalon currently writes `http://www.w3.org/ns/anno.jsonld` into the @context of all IIIF manifests. Running the IIIF validator against our manifests, the error "Top level @context is no…
-
First of all, I want to say how much I appreciate that you’ve introduced the concept of Linked Open Usable Data (LOUD) in your course. It’s an important and valuable topic. Having extensively [studied…
-
This is higher up the to-do list than dockerizing, as once the spec is done, this is the main blocker for the migration.
-
For description see
- https://developer.mozilla.org/en-US/docs/Web/HTTP/Content_negotiation
- https://iiif.io/api/presentation/3.0/#63-responses
On a property-by-property basis you will need to …
-
The IIIF specifications use warning blocks (marked `{: .warning}` in the source) which appear with a red bar and background, e.g. the "Incompatibility Warning" in https://iiif.io/api/presentation/3.0/…