Okay, thanks for the clarification Lane!  This isn't a huge thing, and
I'm sure you guys have plenty of other things to add, but will either
editing the author or adding other authors ever be possible?

On Jun 5, 2:16 pm, "Lane LiaBraaten (Google)" <[EMAIL PROTECTED]>
wrote:
> Hi rachnr,
>
> When creating events, the Calendar API will automatically set the
> author to be the user that is currently authenticated.  If user1
> creates an event on user2's calendar, then user1 will appear as the
> author of the event.  For your example of a central calendar, when
> people submit an event they will be the author, but all the events
> pulled from the database will have the account that the database uses
> to authenticate as the author.
>
> Sorry for the confusion in the docs and sample code.  You can't
> currently add authors to events.  I'll remove the inappropriate
> example.
>
> Cheers,
> Lane
>
> On Jun 5, 7:34 am, rachnr <[EMAIL PROTECTED]> wrote:
>
> > Can someone from Google address this?  Shouldyoube able to set the
> > author or add authors?  If not, why does the documentation imply 
> > thatyoucan?  Also, if not, I think this is an important feature to add.
> > It seems like it would be helpful when populating other people's
> > calendars to be able to show who submitted the events.  In our case,
> > we want a Google calendar that the users on our domain can subscribe
> > to that gets populated from our existing event database system.  I
> > don't want the author to be the calendar owner because this is a
> > central calendar that other people submit to.  Please advise if there
> > is a method to change the author.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Calendar Data API" group.
To post to this group, send email to 
[email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/google-calendar-help-dataapi?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to