This endpoint is available at /iiif/1.
Cantaloupe implements version 1.1 of this API, for compatibility with all 1.x clients. Compliance level is dynamically computed and declared on a per-processor basis. Most processors are "Level 2"-compliant.
tile_width
and tile_height
endpoint.iiif.min_tile_size
configuration key, or the full image dimensions.endpoint.iiif.min_tile_size
.formats
qualities
profile
This endpoint can be enabled or disabled by setting endpoint.iiif.1.enabled
to true
or false
in the configuration file.
This endpoint is available at /iiif/2.
Cantaloupe implements version 2.0 of this API, for compatibility with all 2.0 clients. Compliance level is dynamically computed and declared on a per-processor basis. Most processors are "Level 2"-compliant.
sizes
endpoint.iiif.2.restrict_to_sizes
configuration option.)tiles
width
and height
will be the smallest of the native tile dimensions, the value of the endpoint.iiif.min_tile_size
configuration key, or the full image dimensions.endpoint.iiif.min_tile_size
.profile/formats
profile/qualities
profile/supports
service
Cantaloupe supports an optional service profile in information responses. The delegate script merely needs to implement the get_iiif2_service()
method. An example implementation of the Physical Dimensions service follows:
module Cantaloupe
##
# @param identifier [String] Image identifier
# @return [Hash] that will be transformed to JSON and appended to a
# `service` key in information responses
#
def self.get_iiif2_service(identifier)
# Obviously, some of this info would be retrieved dynamically from a
# database or what have you. This is just an example.
{
'@context' => 'http://iiif.io/api/image/2/context.json',
'profile' => 'http://iiif.io/api/annex/services/physdim/1/context.json',
'physicalScale' => 0.85,
'physicalUnits' => 'cm'
}
end
end
This endpoint can be enabled or disabled by setting endpoint.iiif.2.enabled
to true
or false
in the configuration file.