For this purpose, the user must have deployed the **SchemaTIFF** component.  This component is provided as a simple Docker image, but users can deploy it as a Python script. A proper Python requirements file is provided. In this description, we will use *some directory* as a reference to any given place in the user’s file system, for the sake of simplicity.

#### Actions
- The user saves images in some directory
- The user configures Converter by providing environmental variables
- The user decides which conversion steps should be performed (decide between format conversion, manifest generation, or both)
- Manifests and converted files are being saved to the directories pointed out during the configuration step

Documentation: https://gitlab.pcss.pl/dl-team/atrium/iiif/converter

For this part, the user has to have IIIF-enabled files, e.g. those generated in the previous step. Those files are converted images and corresponding manifests. Manifests have to be served by some file server like NGINX. Images have to be saved to a directory accessible by **Cantaloupe** that will be deployed.

#### Steps
- User deploys an HTTP server to serve manifests 
- The user checks if manifests are accessible and if the address of the HTTP server is the same as the one in the generated manifests
- The user configures compose so directory with images will be attached to the proper mount in the **Cantaloupe** container
- The user runs compose and checks if images are served properly

Documentation: https://gitlab.pcss.pl/dl-team/atrium/iiif/iiif-server

The last part is to access images. Once the user has accessible IIIF images and manifests, it can handle the deployment of **Altamira** component.

#### Steps
- User deploys image obtained from repository
- Sometimes it might be necessary to modify nwb.config.js (allowedHosts) and rebuild the image, due to CORS. Providing value 0.0.0.0 does not always work

Documentation: https://gitlab.pcss.pl/dl-team/atrium/iiif/mirador/mirador-dev

Piotr Tylczyński

Aleksandra Nowak

Konrad Pawlikowski

#### Introduction 

The purpose of this workflow is to provide a way to create and serve files in IIIF-compatible (International Image Interoperability Framework) format, which:

- Increase interoperability by standardizing access, as it is open source and widely implemented 

- Enhance delivery time by sending to the end-user only the required parts of the image

- Increase scalability as IIIF is ground-designed to handle large volumes of data

The main goal of this workflow is to streamline the creation process of IIIF-enabled resources. The entire procedure should be as simple as possible. Moreover, saved data should be accessible at will by any user having a proper resource link.

#### Workflow Goals
 
- Enable users to save images (in a given subset of formats) that will be properly converted and saved to the IIIF Server
- Enable users to access saved images at will by IIIF Viewer

#### Workflow implementation
Full documentation available [here](https://gitlab.pcss.pl/dl-team/atrium/iiif/project-files/-/blob/main/README.md)


Edit actor

Other URLs relevant to the resource, e.g. ORCID, etc.

URL, ideally landing page, of the resource.

Person/group/body who helped create the resource.

Should be concise and raise interest in the entry. Allows <Link>Markdown</Link> content.

Other URLs relevant to the resource, e.g. code, DOI, etc.

Upload media

URL pointing to info about the access policy.

The activities you can do with the resource. See <Link></Link>.

Name of the conference where paper was given.

Describes the discipline covered by resource. See <Link></Link>.

Locations where the Resource is offered. See <Link></Link>.

URL to helpdesk for incidents & user requests.

Audience targeted by the resource. See <Link></Link>.

A particular published issue of a journal.

Concept or term related to MP entry. See <Link></Link>.

Language(s) in which a resource is available. See <Link></Link>.

Select license pertaining to resource. See <Link></Link>. If license is unknown, use the "Terms of use" property field to describe the usage terms.

Status of the Resource life-cycle. See <Link></Link>.

Mode of use for the resource. See <Link></Link>.

File format of the linked resource. See <Link></Link>.

Page #s of a resource, separate by commas.

Refine the resource's nature and function. See <Link></Link>.

Links to non-MP materials that are relevant.

Info about performance levels provider expected to deliver.

Standard used by the resource. See <Link></Link>.

Technology Readiness Level of the Resource. See <Link></Link>.

Resource user manual and documentation URL.

Version of the tool or service that is linked.

The volume of a journal or multivolume book.

Edit source

Name

If you are having trouble with the sign in process, please <ContactLink>contact the SSH Open Marketplace team</ContactLink>.

If you are having trouble with the sign up process, please <ContactLink>contact the SSH Open Marketplace team</ContactLink>.

IIIF Enablement and Visualization Workflow Using Altamira Viewer and Cantaloupe for Image Repositories

Introduction

Workflow Goals

Workflow implementation

Related items(2)

Workflow for Annotating and Comparing IIIF resources using Altamira

Altamira Viewer @ ADS

Workflow steps(3)

1 Saving Images (SchemaTIFF)

2 Serving Images (Cantaloupe)

3 Accessing images (Altamira)