Google Calendar API accepts bad data!

Eric PughApril 11, 2007

If you’ve been reading my posts lately, you’ve noticed lots of posts about parsing working with Time and Dates in Ruby. This has been because my hobby project has been to write a Ruby tool for synchronizing my Apple iCal calendar to my Google Calendar.

This project is published on RubyForge as Novo, and is finally nearing a 0.1 release.

As I’ve been working on flushing out a lot of the bugs, I’ve learned quite a bit about the GData API. And one of the things I’ve noticed is that you can create bad data in their system via the REST API pretty easily. My code had a bug where it wasn’t converting Time’s properly when inserting events into gCal, so I managed to put the same event in twice, once without start and end times, and once with! Unfortunately I can’t delete the bad entry through the Google Calendar interface. It shows up in searches, but not in the listing:

GCal Bad Data

Because of a couple of bad calendar entries that I created during development, I’ve add an ignore option so that the bad entries can be permanently ignored.

As I get closer to the Novo 0.1 release I’ll post more about the tool

More blog articles:

Let's do a project together!

We provide tailored search, discovery and personalization solutions using Solr and Elasticsearch. Learn more about our service offerings