ROLE OF THIS DELIVERABLE IN THE PROJECT. This deliverable presents the overall architecture for the definition, construction, deployment and experiencing of the GLP, aligned with the design specifications developed in Work Package 3 (D3.3 Learning Environment System Specification and D3.5 Game Design Document) by both game designers and pedagogical experts. It has been prepared following specific guidelines described in the DoA and has been structured as a key hub of contributions from all partners, in turn providing flexible examples of usage scenarios to be implemented, tested and refined within the pilots in Work Packages 5 and 6.
ROLE OF THIS DELIVERABLE IN THE PROJECT. This deliverable provides results of how the project’s goals for dissemination and business communication activities have been achieved in the first 18 months of the project. This document is also an evaluation on how the project is progressing during the first half ot the project and what open issues about the dissemination (e.g. specific stakeholders not being reached) and what corrective actions should be taken to address those issues in the following 18 months.
ROLE OF THIS DELIVERABLE IN THE PROJECT. This deliverable presents the Visual Identity Guidelines (VIG), the main sections and functionalities of the project website and the key Communication/ Promotion Materials that underpin the distinctiveness of the project and construct sustainable mechanisms to support dissemination activities during and beyond the life of the project. The objective of the VIG is to provide a unified, meaningful project brand that complies with the quality, and the innovative impact of Beaconing. The Communication/Promotion Materials were constructed in accordance with these VIG. The Beaconing website is one of the key elements for the dissemination and identity of the project. At consortium level, the private section of the project website aims to enhance internal communication among partners through wiki and discussion pages, scheduling of events, as well as uploads of project deliverables. The public sections of the website coupled with a strong presence in well-established social media channels, provides partners with mechanisms that increase the visibility, the impact of the project outcomes, and consolidate the project brand.
ROLE OF THIS DELIVERABLE IN THE PROJECT. This deliverable contributes to the work of work packages (WP) WP5 and WP6: As the BEACONING platform and the pilots are testing the software, we handle and process different kinds of sensitive data – partially of minors – it is vital for project members to know how to treat them correctly and securely. Also, developers need to know how the new GDPR influences their work and what must be considered within BEACONING. Therefore, this document defines the ethical guidelines and new consent form templates for the pilots and describes how data and consent shall be handled by the software internally in terms of the new GDPR.
ROLE OF THIS DELIVERABLE IN THE PROJECT. This deliverable is the first of two on user requirements and provides input to WP 4 as well as task 3. 4 and 3.5.
ROLE OF THIS DELIVERABLE IN THE PROJECT. This deliverable provides the Dissemination and Communication plan for the BEACONING project. It represents a shared vision of how the project’s goals and results will be communicated to different stakeholders and target audiences, and it serves as a reference for all partners in their involvement in dissemination and communication activities. This document will also serve as a plan to evaluate how the project is progressing along the execution of the project and to identify early both best practices that should be generalized or open issues about the dissemination (e.g. specific stakeholders not being reached) and what corrective actions should be taken to address those issues.
ROLE OF THIS DELIVERABLE IN THE PROJECT. This deliverable displays a repository of existing technologies, learning environments, content, infrastructure and their currently used technologies to give a better insight of the project’s starting point. It presents the basis for further development. It lists all components we can re-use as asset, product or service, saves time and resources to reach our goals as fast and easily as possible. The document is complimentary to the outcome of the end users’ requirements (D3.1) and the lessons plans (D3.3), as they together provide an overview of what we can re-use, adapt and what we have to build or extend. Therefore, these three deliverables are the basis for the further development in task 3.4 and 3.5 as well as in WP 4.
ROLE OF THIS DELIVERABLE IN THE PROJECT. The Beaconing interface integrates the relevant components and allows the user to fully interact and navigate around the system. The back-end interface controls how the system communicates internally, and to the external requests. This deliverable places the focus specifically on the front end interfaces. The progress of the project going forward relies heavily on the work presented in this deliverable. The interface plays a key role in the small and large-scale pilots, allowing the users to test the platform properly and get the platform to perform the functions they require.
ROLE OF THIS DELIVERABLE IN THE PROJECT. This deliverable describes a reference implementation of the client component, which will be provided as an open source code package. It includes a technical implementation of the required backend services, delivered as an open source code package2. Additionally, this deliverable describes how to integrate analytics in a game, provides a full analytics manual for developers and teachers (including API usage) and provides a complete example collection model for a particular XXX and its visualization configuration.
ROLE OF THIS DELIVERABLE IN THE PROJECT. While the software is still under final developments, it appears in more detail which data BEACONING handles and collects, and this document is updated regularly throughout the project. This deliverable contributes to the work of all work packages. This document sets the guidelines for ethics, as well as for handling data of all kinds. This includes how data is treated within the software architecture, but also how to proceed and secure data outside the BEACONING Platform, e.g. questionnaire results. Therefore, this deliverable is necessary to ensure that all partners comply with the agreements. The ethical part of this document is mostly relevant for WP5 and WP6, which focus on the small and large-scale pilots. This deliverable will be updated once more at the end of the project, in month 36.
