Deliverable 4.7 Workflows and Transcoding

This document discusses the way in which we implemented workflow and transcoding services in the Archipel demonstration platform.
First, we will be outlining the overall architecture of the platform. By using a service oriented approach and adhering to the principles of separation of concerns we manage to create a solid yet flexible design. In this architecture, single components or complete layers of functionality can be swapped out and replaced with a different implementation if needed.
Secondly, we will discuss the main layers in the context of workflows and transcoding. The Enterprise Service Bus (or ESB) implementation provides a level of abstraction and decoupling between the individual services. We show how the workflows are employing feedback loops to interact with the services in the landscape, and zoom in to the level of individual services.
Finally, we give an overview of the services integrated in the workflows. These services can be divided into three categories: harvesting services, discussed in deliverable 4.2, dissemination services, partly discussed in deliverable 4.3, and preservation services. These preservation services guarantee the integrity and interpretability of the preserved content. In this section the transcoding services are also discussed. These services play a crucial role in the preservation process, because they will migrate the file formats of the harvested content to interpretable file formats for dissemination and preservation purposes.