BEACONING Open Data Architecture Sample Clauses

BEACONING Open Data Architecture. International Side‌ Figure 7 shows that tools or web pages used by game developers, BEACONING participants, or external researchers, only work with BEACONING IDs, they have no access to local LMS IDs. Special local needs (country/organization/purpose) can be catered for by a dedicated web services proxy. BEACONING Web services proxy BEACONING BEACONING Vault Database 4 ETHICS‌ In Deliverable 1.7 it was mentioned that all ethical and privacy regulations of the participating countries will be respected and will conform to the current legislation and regulations in the countries where the research takes place, to European legislation, as well as International conventions and declarations. To ensure this transparency, our consortium members have provided their pilot specific ethical aspects according to their country specific rules and regulations. In order to receive formal consent from the parents and/or guardians, the consortium has decided to use template of forms adapted to the national regulations (see D1.7), when there will be debrief session between the BEACONING platform personnel, the participants, their parents and/or guardians. The pilot specific needs are as follows:

BEACONING Open Data Architecture. School Side‌ As it can be seen in Figure 6, games or web pages used by students and teachers get personal data either directly from the LMS services or from a local BEACONING server managed by local authorities (school, district, region, country, etc.). Only the local server and local app know how to associate a BEACONING ID with a local LMS ID. The International BEACONING databases never hold personal identification data. BEACONING IDs (de-personalized) LMS LMS IDs (personal) BEACONING Database BEACONING Vault