Inspiration
We observed that in our field alone the number of cross-disciplinary opportunities was immense, from application of AI in medical imaging, to developing CAD software used in architectural design and engineering, to the creation of modern games that often require the combined efforts of artists, writers, modellers and game developers. Yet, reflecting on own experience, it seemed that formal opportunities for collaboration with other students in medicine, architecture, engineering, arts and so on were relatively rare. The desire to promote multidisciplinary in student approaches to education (e.g., research), personal projects (e.g., startups) and competitions (e.g., hackathons) towards the end of pursuing innovation, diversity and excellence served to be the inspiration for our proposed product, “Collabeeration”.
What it does
Taking notes from its namesake mascot, the bee, Collabeeration facilitates teams working together thus allowing for the “cross-pollination” of ideas, i.e., multidisciplinary approaches to projects and problems. As a platform built for students, alumni, teaching staff and relevant organisations, Collabeerate allows users to list and apply to openings for well-defined projects requiring specific roles. In one instance, one could conceive of an artist looking to collaborate with a student familiar in robotics to achieve some artistic exploration similar to “Heterobota” by Agnieszka Pilat, recently exhibited in the NGV. Such a student would write a detailed listing on Collabeerate, detailing the name of the project, required skills, estimated commitment, deadlines and so on. A compatible student, in this case one with familiarity with robotics, would input they details in the search bar or if they already had an account would be shown relevant results including the aforementioned listing. Applying would then direct users to a simple messaging system within the website.
How we built it
HTML, CSS, JS, JSON
Challenges we ran into
A feature we tried to implement was a “Generate summary” button which would call an LLM API to summarize a detailed brief input by the user. We found difficulty in implementing the API due to the underlying framework we chose to build the website with. This is certainly a lesson we will carry forward, hopefully through committing more time to planning key features before beginning to build the project we can avoid similar issues in the future.
Accomplishments that we're proud of
For most of us this our first hackathon so producing a relatively finished design was great!
What we learned
Hackathons are hard!
What's next for Collabeerate
Given the time constraints, many of the features shown in the wireframes were not achieved, so following through with this and continuing to iterate seems to be the path forward.
Log in or sign up for Devpost to join the conversation.