T6.1: Design platform architecture and elicitation of technical requirements, and ECCCH (Lead: CTL; Contributors: All; [M07-M12]) – T6.1 will define MusicSphere’s architecture and high-level representation of all subsystems to be integrated into an interoperable platform. The architecture will form the essential theoretical scheme based on which, MusicSphere will build the appropriate interfaces with databases, define common data formats for subsystem interfaces, and exchange information between software and hardware components. The architecture design will offer recommendations on the high-level design of the subsystems. Novel concepts of operations will be elaborated to narrate the process to be followed in implementing the MusicSphere platform. The architectural layout of the MusicSphere subsystem interactions will be further validated by the feedback obtained through participatory approach and co-design methodologies. This approach will facilitate the adoption of the technologies and will ensure the conformation of a system addressing the real needs of the end-users (i.e. site managers, public authorities, etc.). The architecture will comply with relevant industrial standards for software and hardware integration supported by ISO/TC 184/SC 5 (Interoperability, integration, and architectures for enterprise systems and automation applications). The architecture will be in full alignment with the guidelines of the ECCCH infrastructure and recommendations (see T2.2). The architecture will incorporate a series of security measures ensuring data protection (see T1.5) and ethical guidelines (see T1.4). (Output: D6.1).

T6.2: Backend infrastructure, security, and basic integration (Lead: CTL; Contributors: -; [M09-M18]) – T6.2 will deploy a 2-Tier data workflow model infrastructure that will include: a Big Data capability and microservices set up with Docker, Jenkins and Kubernetes orchestration as needed, and Data Ops for data exploitation. The Data Ops will entail: i) connectors via REST APIs for MusicSphere interfaces for raw data gathering; ii) development of data wrangling/data munging algorithms for transforming and structuring data from raw data form into a unified format (e.g., XML, JSON); iii) development of data cleaning algorithms for filtering of unwanted characters; iv) data enrichment for merging third-party data from external authoritative sources; v) Data validation routines for ensuring data quality and peculiar unexpected data-value violations; vi) Publication of Data process to a data middleware stack via APIs or Message Brokers (e.g. Kafka) that will be consumed from other MusicSphere tools. The entire data deriving from the projects’ gathering activities will be pre-processed and stored to the Data Middleware Stack (DMS) with security on-transfer and on-storage. The MusicSphere Open API will be developed, with data anonymization methods that will guarantee privacy via k-anonymity and l-diversity algorithms. A layered architecture will be implemented where its layers will be determined by the tier onto which the software operates. (Output: D6.2).