Last week, our team lead, Alex, presented a summary of our project progress so far. He presented some of the more technical aspects associated with software development (such as version control and site deployment) and the tools we’re using to make that happen (git, Jenkins, etc).
What went well?
Essentially, we’ve doing well for the semester and are now at the point where we can dive into the code and make some changes happen! Everything is set up with Django and Jenkins so that the website is built nightly and hosted live on here.
The current eyeData homepage!
As such, changes to the project are as simple as git pull, commit, push. We still have the bullk of the work left to do, but I’m sure we’ll figure it out soon enough!
What was challenging?
The most challenging aspect for this week has been getting the team to work together. Now that we’ve started diving into the code, we’re having each member specialize on a certian aspect of the project: UI, data analysis, graph plotting, etc. As such, we’re getting to the point where each member is the expert in his/her area, so making larger changes requires closer collaboration than before. This has proved to be a challenge, but with definitive goals, we will overcome it!
What’s up next?
We’re planning to use the resources at the Berkman Center to learn about what visualizations are useful for social science research. Not every social scientists is going to need the same type of graphs ; we want our product to be intuitive and intelligent, so we need to learn more about what’s actually in use out there in the wild.
We’ll also want to learn what languages/libraries are used most frequently by social scientists. While we’re focused more heavily on data visualization, at some point in the process, we’d like to provide the social scientists with access to the manipulations performed on the data. Knowing what background knowledge they have will be helpful for us
We had Raman Prasad, our resident expert on python, mapping, and many other things, volunteer to provide a helping hand in setting everything up! He’s been asked to give us a Python back-end to interface with the DataVerse API.
Each person in the team made a short presentation on what we expect to see from our eyeData project! The presentations went quite well!
Here’s a quick snapshot of our UI Presentation, highlighting some key ideas (inspired by CS50 Courses)
What went well
The presentations went quite well – each team member contributed great idea to the project and raised questions the presenter hadn’t yet considered. The process of figuring out how the UI would be laid out went incredibly well 🙂
What was challenging
The scope analysis of this project is the most challenging so far! Do we want to focus on just survey data and DataVerse, or should we begin considering handling more general sets. Another challenging aspect of the work will be the collaboration – how will we divide the work and make sure that each team member can be kept up to data? Our plan is to use GitHub for version control and bug reports!
What’s up next
Up next, we have our Scope Doc! This is a document which will incorporate most of our ideas and list out the tools and resources we plan to use for our project. It will help us get organized before we dive into coding! We plan to have this prepared for our next meeting, during which we will dive into each aspect in detail and begin assigning parts to each team member! Here’s a quick snapshot of what we have so far!
Go team eyeData! Wait to hear more from us next week!