Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integrate with Google Calendar API #42

Open
shubhpatel108 opened this issue Mar 12, 2016 · 3 comments
Open

Integrate with Google Calendar API #42

shubhpatel108 opened this issue Mar 12, 2016 · 3 comments
Labels
Milestone

Comments

@shubhpatel108
Copy link
Collaborator

No description provided.

@shubhpatel108
Copy link
Collaborator Author

One use case is covered in #78

@paulinahaduong
Copy link
Collaborator

Potentially could address #28 with invites through gcal instead.

@shubhpatel108
Copy link
Collaborator Author

shubhpatel108 commented Aug 7, 2016

Integration architecture:
gcal integration - book-a-nook

Scenarios:

  1. Every Google user have a calendar list where he can add personal calendars as well as other public/permitted calendars. In our case, every Nook will have its own calendar, primarily attached to the Admin who created the nook, i.e. this calendar will be added to his/her GC list. Other admins may or may not add this calendar to their GC list. If possible, we can have the calendar detachable from the owner too.
  2. Many admins can add a nook’s calendar to their calendar list as shown in the diagram.
  3. As an admin could be associated with many locations, he/she can add calendars of nooks related to other locations too.
  4. For a confirmed Event1, the requestor User1 will able to add it to its personal Google calendar. This will be done on demand, for every reservation separately. We can have a common sync functionality too.
  5. A confirmed Event2 is created by User1 but is not added to his own personal calendar. However when he invites User2 (using Google Contacts APIs), the latter accept it and Event2 gets added to his/her calendar. This is an incremental goal and can be implemented only if time permits.
  6. Delete the GC event if the status is changed back from confirmed to any other. This is because the GC events are always assumed to be confirmed.
  7. A user can opt for pre-event alerts (emails, pop-ups and SMS) from Google.
  8. Update the GC event information like title and description when an event is updated on our app.

quoted from my GSoC '16 proposal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants