Datalets / dribdat
Open source hackathon platform
The future of [human, innovative] work is enhanced and complemented with technologies that support our learning, focus and collaboration - without distracting us from our goals.
This is an open Hackathon. The stakes are high, the competition is ready. You will be measured, your progress tracked, your creativity analysed & compared. Think you have what it takes? Ready, steady, go!
DRIBDAT (Driven By Data) was created specially for the IoT Hackathon. It works as a website and project board for running exciting, productive Hackathons..with an Impact Factor. You can set up a website with details of your event, link and embed a community platform. The requirement of this project was to create a tool to help organizers run a more professional event, and for team members to quickly (re)publish presentable documentation about their idea.
"Data-driven hackathons" are supported with social features (like the Event Dashboard) to track the activity levels, gauge progress and send signals that may boost the success of the projects themselves. The signals that each project generates are tracked in the background, and are extensible. Currently these are used to assign 'completeness points' and allow users of the platform to send each other 'KUDOS', but this system could be extended to do much more.
At the hackathon, we looked into smartphone and Arduino-compatible pulse sensors that can be used to trigger an automatic signal depending on the users' heart rates (HR). These may be correlated to the relative performance of the teams working on projects, for example to notify participants of fatigue, or send encouragement when they are operating at peak efficiency (e.g., see Correlating Heart Rate Variability with Mental Fatigue).
Another idea is to use OpenCV-based computer vision to detect movement - a camera embedded in the workspace of a given team could estimate and relay relative activity levels. In order to test this further, we would need to provision a cloud-based messaging platform (such as VerneMQ) to accept HTTP PUTs from the devices and channel them to the DRIBDAT API, in addition to finishing device support for some of these experimental features.
We hope you have enjoyed using this tool - please leave any feedback here and/or using the Issues link at the bottom of every page.