Date(s) - 26/03/2014 - 28/03/2014
RWTH Aachen University
Category(ies) No Categories
RWTH hosted the first integration meeting, referred to as the “Aachen Integration Meeting”, in March 2014. The purpose of this meeting was to gather the whole consortium in order to reach the project to the same vision and same integration plan for the second year. This meeting last for three successive days and the main agenda was circulating in two main strands: Integration and Theory Camp. Regarding integration, different sessions and categories were considered such as: data integration, service integration, user interface integration, development process integration, data integration, and external tool integration. Moreover there were sessions about the sustainability scenarios in which contributes to the longevity of the project. In theory camp sessions big ideas and theories which also help to the sustainability and improvement of the project were hold.
The results of the Aachen Integration Meeting can be categorized as follows:
- As for the data integration, common data model was proposed and therefore a file based cloud storage was agreed as a big data management source. Moreover, cloud video transcoder also was adopted as a service for i5 cloud data storage. In which it can be used for transforming videos to work with different kinds of devices. Hence cloud video transcoder and cloud storage support layers services to save and transform their data to various codecs
- As for service integration, there were sessions for Open ID Connect and layers adapter. Open ID Connect was proposed as a seamless authentication and authorization approach for all of the layers applications. In other words, it supports single user and password for all of the services. Layers adapter was discussed as the communication entry point that all of request and responses should go through it. To put this another way, it plays as a single entry points for all layers services.
- Regarding user interface integration, layers Java script library for client side user integration, accessible and responsive web design was explored and acquired.
- With regard to development process integration, licensing policy session was hold and it was agreed that all the partners use permissive licensing policy for the modules existing in Github. Furthermore, using JIRA for issue tracking and Jenkins for nightly built and continuous integration was adopted and discussed.
- For continuous evaluation and monitoring of the services and project users, two services so called MobSOS and NOSE Dashboard was proposed in order to be used for future evaluation and monitoring in the project. MobSOS was agreed to be integrated into the Layers integration architecture as means for formative evaluation of Layers artifacts (tools, services). NOSE Dashboard was adopted to be used to increase awareness of what is going on within project and support community requirements.
- Last but not least, there were separate sessions on external tools integration. As for this, services should be integrated with Intradoc247, Gephi and yFiles. Gephi and yFiles are some open source and powerful visualization tools which can support the services for the visualization of different parameters and output.