How four girls conspired to take down CAESAR

Someone once said, “we should totally just stab Caesar.” Our school’s student account system, CAESAR, is the official course registration tool and is also the source of several frustrations for students. So my peers and I committed an infamy. We dared to totally take a stab at CAESAR.

Each quarter, Knight Lab encourages its student fellows to think of how best to develop skills specific to our personal interests and needs. In the past, I’ve been stuck thinking in terms of “I need to learn Python; let me do a data project.” This quarter, I adopted the reverse approach by thinking of existing problems in the community and thinking of how solutions to those problems might also help me learn the technologies I need.

And CAESAR is a real problem that my community wants to fix. It’s been at the core of hackathons like the student government’s RedesigNU last year. As it exists right now, CAESAR has a search engine that is comprehensive but not browse-friendly because the process is one-directional. For example, users are unable to press the back button without resetting the entire search, which results in juggling three different browsers just to make course selection a little less painful.

Then there are the CTECs -- the only formal documentation of what previous students thought of each class or instructor. Unfortunately, among the anonymous comments and unhelpful “he smells” notes, credibility is hard to screen for. So we instead defer to putting up screenshots of our class schedules on Facebook to get insight about classes our friends have taken as well. We also do it because we want to experience a little camaraderie of having to suffer through the same computer science requirement, and we know misery loves company.

But surely, someone’s already come up with a solution to this?

Nope. There’s been a slew of “Brutus” projects that Northwestern students have built to enhance the usability of CAESAR, like CourseDJ and Course Connect, but not one platform has captured the social aspect of choosing courses while improving the search flow (and thus browsing experience) at the same time.

So Nicole Zhu, Mallory Busch, Ashley Wu, and I built Romaine.

When we had established our objective and proposed a solution, the learning part came naturally. Over the course of a few months, my initial (and vague) objective of learning how to interact with databases soon became two-fold, three-fold, then five. I didn’t even realize how much my skills were growing until my team and I reached a point where we could finally reflect on how close we were to having a tangible product. We had:

  • Made calls to the Northwestern Course Data API to produce a JSON file using Python
  • Learned how to interact with and make queries to Parse, a backend service on the cloud
  • Discovered that we had somehow ideated a join table in Parse without any prior knowledge of relational databases
  • Figured out how Facebook integration works using its login and graph API
  • Blinged out our style factor with some SASSy CSS
  • Adopted efficient frameworks and deployment tools like Middleman, Ruby on Rails, and Heroku


Amidst all the super awesome hacking/breaking/theorizing we were doing, we also learned from each other. Because my team members and I varied in terms of skill and background, we were able to grow in all aspects of bringing a product to life. Mallory got hip with the lingo of A/B testing, user interface design, and other product-orientated thinking; Ashley, the only Windows-based person in our group, learned to use Vagrant so development would be consistent across all operating systems; and Nicole and I finally, finally learned how to resolve merge conflicts. But for each and every one of these steps, everyone was either actively teaching or learning, so that involvement was consistent.

In the end, Romaine is not a journalism project. Python isn’t a journalism skill. Neither is using Parse, JavaScript or Facebook APIs -- until you find the right application for them. Romaine introduced us to technologies we might otherwise use in newsroom development and taught us to be aware of our audience throughout the design process.

Of course, building a new empire in CAESAR’s place takes time. For now, Romaine remains beta. Lettuce hope it grows more useful over time.

(I will not apologize for the Mean Girls reference and the puns. I have no shame.)

 

About the author

Suyeon Son

Undergraduate Fellow

Latest Posts

  • Building a Community for VR and AR Storytelling

    In 2016 we founded the Device Lab to provide a hub for the exploration of AR/VR storytelling on campus. In addition to providing access to these technologies for Medill and the wider Northwestern community, we’ve also pursued a wide variety of research and experimental content development projects. We’ve built WebVR timelines of feminist history and looked into the inner workings of ambisonic audio. We’ve built virtual coral reefs and prototyped an AR experience setting interviews...

    Continue Reading

  • A Brief Introduction to NewsgamesCan video games be used to tell the news?

    When the Financial Times released The Uber Game in 2017, the game immediately gained widespread popularity with more than 360,000 visits, rising up the ranks as the paper’s most popular interactive piece of the year. David Blood, the game’s lead developer, said that the average time spent on the page was about 20 minutes, which was substantially longer than what most Financial Times interactives tend to receive, according to Blood. The Uber Game was so successful that the Financial...

    Continue Reading

  • With the 25th CAR Conference upon us, let’s recall the first oneWhen the Web was young, data journalism pioneers gathered in Raleigh

    For a few days in October 1993, if you were interested in journalism and technology, Raleigh, North Carolina was the place you had to be. The first Computer-Assisted Reporting Conference offered by Investigative Reporters & Editors brought more than 400 journalists to Raleigh for 3½ days of panels, demos and hands-on lessons in how to use computers to find stories in data. That seminal event will be commemorated this week at the 25th CAR Conference, which...

    Continue Reading

  • Prototyping Augmented Reality

    Something that really frustrates me is that, while I’m excited about the potential AR has for storytelling, I don’t feel like I have really great AR experiences that I can point people to. We know that AR is great for taking a selfie with a Pikachu and it’s pretty good at measuring spaces (as long as your room is really well lit and your phone is fully charged) but beyond that, we’re really still figuring...

    Continue Reading

  • Capturing the Soundfield: Recording Ambisonics for VR

    When building experiences in virtual reality we’re confronted with the challenge of mimicking how sounds hit us in the real world from all directions. One useful tool for us to attempt this mimicry is called a soundfield microphone. We tested one of these microphones to explore how audio plays into building immersive experiences for virtual reality. Approaching ambisonics with the soundfield microphone has become popular in development for VR particularly for 360 videos. With it,...

    Continue Reading

  • Audience Engagement and Onboarding with Hearken Auditing the News Resurrecting History for VR Civic Engagement with City Bureau Automated Fact Checking Conversational Interface for News Creative Co-Author Crowdsourcing for Journalism Environmental Reporting with Sensors Augmented Reality Visualizations Exploring Data Visualization in VR Fact Flow Storytelling with GIFs Historical Census Data Information Spaces in AR/VR Contrasting Forms Of Interactive 3D Storytelling Interactive Audio Juxtapose Legislator Tracker Storytelling with Augmented Reality Music Magazine Navigating Virtual Reality Open Data Reporter Oscillations Personalize My Story Photo Bingo Photojournalism in 3D for VR and Beyond Podcast Discoverability Privacy Mirror Projection Mapping ProPublica Illinois Rethinking Election Coverage SensorGrid API and Dashboard Sidebar Smarter News Exploring Software Defined Radio Story for You Storyline: Charts that tell stories. Storytelling Layers on 360 Video Talking to Data Visual Recipes Watch Me Work Writing and Designing for Chatbots
  • Prototyping Spatial Audio for Movement Art

    One of Oscillations’ technical goals for this quarter’s Knight Lab Studio class was an exploration of spatial audio. Spatial audio is sound that exists in three dimensions. It is a perfect complement to 360 video, because sound sources can be localized to certain parts of the video. Oscillations is especially interested in using spatial audio to enhance the neuroscientific principles of audiovisual synchrony that they aim to emphasize in their productions. Existing work in spatial......

    Continue Reading

Storytelling Tools

We build easy-to-use tools that can help you tell better stories.

View More