johnbjr

We're having a series of events around the USA this summer. We've got the events described in a Trumba calendar, and use the Trumba information in various ways throughout our Web site. Now, we've come up with the idea that we'd like to provide a map interface to the summer series of events. In other words, visitors to our site would see a map of the US with the location of each event "pinned." Using Google Maps APIs, we can embed a Google map in our Web page, have the location of each event appear as a "pin" on the map, and then have the event description appear when someone clicks on the pin. The event description comes courtesy of XML that we generate out of a separate database that contains lat/long coordinates and event details. I would really love to eliminate the need for this separate database that we have to maintain in addition to the Trumba calendar entries for this event. The closest I can get today is by using the RSS/Atom feed from Trumba. However, if I define custom fields such as latitude and longitude, they won't appear in the RSS feed unless they're "public" fields, but I don't really want this data to appear on the Trumba event descriptions, because it is not very understandable to the average calendar viewer. Is there something I'm overlooking, or some way of manipulating the RSS feed that I've missed? Better yet, perhaps is Trumba working on some kind of API that would provide data more directly to Google?

I would like to publish a Trumba calendar to my organization's Intranet. My idea is that this internal calendar would have events from our public (Internet) events calendar, as well as additional internal-only events. I know I can use secure URLs and mix-ins to accomplish this (mixing events from public calendars into the Intranet calendars I will also create). But, I'm wondering if it's possible to have certain event fields attached to public events that don't display on public calendars, but that I could display on my Intranet calendars? For example, it would be great to have an "Internal Notes" field that contained many details about an event that we get asked via telephone all the time, but that would clutter up the public events calendar (parking info, meal choices, dress code, and so on). I would not publish this field to the event descriptions on the public calendars, but I would publish this field to the event descriptions on the Intranet calendars. That way, our customer service folks could use the Intranet calendar as a knowledge base about our events, yet we'd maintain the efficiency of having just the one Trumba calendar database.