Work package 4: System architecture and design

Objectives: The EuDML system will enable seamless access to the DML resources distributed through the heterogeneous repositories of the partners and other potential content contributors. The system will primarily consist of an access portal, harvesting and indexing infrastructure and a resource’s identifier resolver.
The primary objective of this WP is to design the architecture and to create technical specifications of the system and its interfaces upon which the core components will be implemented within WP5–6, and additional toolset components within WP7–11.
EuDML is a project with relevant technological challenges, but its main purpose is not to invent new technology. Many solutions that are required in EUDML already exist, so in many areas new developments will not be required; however, a careful design and evaluation of the alternatives has to be carried out.
Also, in order to assure a proper follow-up, the evolving environment needs to be considered, which implies that EuDML should not be conceived as a solution taking into consideration only its own specific functional requirements, but also other important requirements for interoperability.
All of this motivates this WP, which will work as a central point in the coordination of all the technical work to be done in the project.
Finally, it is important to stress the need to perform this work in two iterations. The purpose of the first iteration is to provide to the project the architecture of reference and a design able to support the immediate development. But one must expect that new opportunities, requirements and challenges might emerge, making it fundamental to provide a proper mechanism to react to these situations, avoiding a negative crystallization of the architecture too early phase in the project. In this sense we are not proposing to drive the project on the basis of a pure Agile Design and Modelling, but we’ll follow an adequate methodology inspired by those principles and properly adapted to the requirements of an EC co-funded project.

  • Deliverable 4.1 – EuDML global system functional specification Definition of the main global functional specification of the EuDML system, based both on the Architecture of Processes and Architecture of Information.
  • Deliverable 4.2 – EuDML global system functional specification and design Description of the overall architecture and the key components of the EuDML software system. Together with its complementary appendix, it is intended as the general reference document for development purposes. The concise document is focused on the main concepts of the EuDML architecture only. More detailed descriptions of individual services and other components are provided in the companion document “Deliverable 4.2 – EuDML global system functional specification and design – Appendix”.
  • Deliverable 4.2 – EuDML global system functional specification
    and design – Appendix
    It complements “Deliverable 4.2 – EuDML global system functional specification and design” by describing in detail the key components and services of the EuDML software system. It is intended as the general reference document for development purposes. Therefore, it is expected that the document is going to be continuously updated to reflect the evolution of the system.
  • Deliverable 4.4 – The EuDML Information Life Cycle Process This document describes the basic information entities and their lifecycle within the EuDML.
  • Deliverable 4.3 – EuDML global system functional specification and design – Revision The document describes the EuDML architecture as a service oriented, document centric system. The system is divided into three main components: web interface – which provides user interface and REST services, backend – which provides services and REPOX – which is responsible for harvesting data from data providers and serving contents of the system over the OAI-PMH protocol. Components communicate using HTTP-invoke protocol (encapsulated by Spring Remoting).