Researchers and scientists are entering a new age of development, yet are still using antiquated methods of data collection. The norm of students and researchers is a simple notebook where one manually inputs their data findings, hypotheses and procedures. Irreproducibility of protocol alone causes 3 billion dollars of losses in the life science and the R&D industry, not to mention the hours of time wasted trying to reproduce and validate data, only to get something different than expected. Over the years, I have worked in laboratories, researching in optics, biotechnology, and electrochemistry. Data redundancy and irreproducible results were definitely a problem in all three cases, and it always boiled down to how we We are developing a platform that aims to patch the gaps in research and data management, and helping groups collaborate with others for reproducibility of their research.

Source on the reproducibility issue:

What it does

Accumulab is an artificially intelligent system made to record coherent and reproducible data in a consolidated dashboard that utilizes next generation speech recognition and adaptive capabilities based on research needs. The lab notebook for the 21st century, Accumulab will extensively utilize Google Cloud's Natural Language Processor API to incorporate voice recognition to record verbal notes instead of handwritten. A real-time Progressive Web Application that will decrease the time spent writing and searching, and increase time spent collaborating with your fellow researchers. The integration of AI into our platform to create a hands-free data collection system automatically sets us apart from the electronic laboratory notebooks currently on the market, all of which rely on manual data entry. We are also taking another step above the competition with the creation of a collaboration platform to connect like-minded researchers together.

How I built it

The plan to build the Accumulab prototype was to use web application frameworks, specifically with MERN stack technologies in addition to other developer services as needed such as Google Natural Language processor. I used Marvel to design the prototype. My overall plan for development was as followed:

A) Design & Planning 1) Add/Remove/Edit User Experience and User Interface 2) Wireframe new designs and features 3) Render wireframes using Marvel

B) Development 1) Deploy designs into code 2) Using Agile methodologies' software development life cycle 3) Using React on front end 4) NodeJS and Express on back end 5) MongoDB for database 6) GitHub and Git for source control management 7) Slack and Trello for project management

C) Release 1)Send latest iteration to the public

D) Feedback 1) Find bugs 2) Conduct end-user surveys

E) Go back to Design & Planning for next iteration

Challenges I ran into

For the weekend, I aimed to accomplish Part A of my plan, which was the design and planning. This was successful as I started off with hand-drawn UI mockups, improved on it by thinking about what features are needed, and then rendering it in Marvel. I also wanted to make headway into Part B, which was development. From there, this was the biggest challenge of the weekend. My team and I are not too well-versed in Javascript and React, making development time stretch out the entire duration of the hackathon. Thus, many of the rendered wireframes were not deployed into code.

Accomplishments that I'm proud of

Despite the setback from coding, I am proud that my team appreciated the dream I have for Accumulab, and are willing to put in the time and effort towards development. We are all eager to learn, so I have no doubt that the prototype can be developed. In a short span of time, we had all come together and have accomplished solid work as a team.

What I learned

In this hackathon, I relearned a lesson I've experienced in the lab countless times: no matter how well you initially plan, you always need to take into account of the many bumps in the round when executing your plan. Translating your wireframes to code is no simple task. With all the elements one works with, there are countless chances of bugs that can arise. That's why its important for us to realize that in a hackathon, it is not always about who can hack away the most in a certain amount of time, but for developing critical skills such as being able to work under pressure, being able to gauge a situation, knowing when to move on, etc.

What's next for Accumulab

Accumulab is extremely feasible compared to other projects. Developing it from a technical standpoint until launch can cost as cheap as $0 because we aren't using technologies out of the ordinary besides the one already extensively used in the developer community. The technologies we are using have been used successfully in applications such as Google Productivity Suite or Instagram or slack. We have all the resources to develop this product because of how open source works, and how many companies provide free services for developers. Github for example provides free repository hosting, Mongolabs for example provides free database hosting, Firebase or GitHub Pages provides free website hosting, etc. The only technical drawbacks to developing Accumulab is not really technical at all: we just need time to develop this application.

The number of potential users for Accumulab is relatively scalable from a few dozen to a few thousand over a period of time. The STEM field is greatly involving, with multiple initiatives put into place to surge research and teaching. As such, the time to aid the STEM initiative is now, as we can see the influx of research work being planned and conducted for years to come. My team and I come from a primarily STEM background, each of us with years of experience in our relevant fields. For me, the problem we are tackling is not only personal, but something I witnessed happen with my colleagues. As such, our drive to improve research is not just a venture or a weekend project, but a personal mission.

Built With

Share this project: