IP Library Granted Patent US 10,915,584
Granted Patent B2
US 10,915,584 · App. 14/861,100 · Granted Feb 9, 2021

Event-related document generation

Inventors: Tsung-Hsiang Chang (San Bruno, CA); Christina Cacioppo (San Francisco, CA); Ryhan Hassan (San Francisco, CA); Phillip Cohen (San Francisco, CA)
Assignee: DROPBOX, INC.
G06F16/93G06Q10/1095H04L67/02
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,915,584
App. No.
14/861,100
Granted
Feb 9, 2021
Kind
B2
Abstract

A computer-implemented method, system, and non-transitory computer-readable medium may provide event attendees of a network-accessible calendar with a way to generate collaborative notes for a meeting related to an event. In some embodiments, a calendar entry in a network-accessible calendar may be identified. The calendar entry may correspond to an event and may identify the event attendees. A collaborative document that capable of receiving modifications to the event from the event attendees may be created. The event attendees may further be provided access to the collaborative document.

Claims (62)

1. A computer-implemented method comprising:

accessing a network-accessible calendar, maintained by a productivity management system via one or more application programming interfaces (APIs) maintained by the productivity management system;

identifying a calendar entry in the network-accessible calendar, the calendar entry comprising information associated therewith that includes at least an event and event attendees by gathering productivity information via the one or more APIs, the productivity information comprising information related to one or more calendar entries in the network-accessible calendar;

responsive to identifying the calendar entry, automatically creating for the event, via the one or more APIs, a collaborative document;

interfacing with an external computing system to obtain identities of event attendees, wherein each event attendee is associated with an account managed by the productivity management system;

suggesting that a subset of event attendees that have accepted an invite to the event receive access to the collaborative document;

responsive to receiving approval of the suggestion, storing the collaborative document in a shared location, accessible to the subset of event attendees, associated with the account managed by the productivity management system, based on the obtained identities;

prompting the productivity management system to modify the calendar entry to include an actionable link that provides access to the collaborative document in the shared location; and

providing access to the collaborative document responsive to an event attendee of the subset of event attendees selecting the actionable link;

in response to the event attendee selecting the actionable link, presenting the collaborative document to the event attendee, the collaborative document compatible with an external document editing application, without prompting the event attendee to separately open the external document editing application.

2. The computer-implemented method of claim 1 , wherein the link is a Uniform Resource Locator (URL) to the collaborative document.

3. The computer-implemented method of claim 1 , wherein the collaborative document is configured to be collaboratively edited by multiple digital devices at a particular time.

4. The computer-implemented method of claim 1 , further comprising:

monitoring the collaborative document for changes; and

notifying at least some of the event attendees of the changes.

5. The computer-implemented method of claim 1 , further comprising restricting write access to the collaborative document after an end time of the event.

6. The computer-implemented method of claim 1 , further comprising modifying the collaborative document using a title of the calendar entry.

7. The computer-implemented method of claim 1 , further comprising suggesting boilerplate content for the collaborative document based on the calendar entry.

8. The computer-implemented method of claim 7 , further comprising receiving instructions to accept or to deny the boilerplate content.

9. The computer-implemented method of claim 1 , further comprising providing, by a document editor application, to at least one of the event attendees a first prompt to invoke the collaborative document.

10. The computer-implemented method of claim 9 , further comprising providing, by the document editor application, an ordered list of prompts wherein an order of the first prompt in the ordered list of prompts changes as a time and date of the event approaches.

11. A system comprising:

one or more processors; and

a memory storing instructions that, when executed by the one or more processors, cause the one or more processors to:

access a network-accessible calendar, maintained by a productivity management system via one or more application programming interfaces (APIs) maintained by the productivity management system;

identify a calendar entry in the network-accessible calendar by gathering productivity information via the one or more APIs, the productivity information comprising information related to one or more calendar entries in the network-accessible calendar, the calendar entry corresponding to an event and identifying user accounts for the network-accessible calendar, each of the user accounts associated with one or more event attendees, the calendar entry including information regarding the event;

responsive to identifying the calendar entry, automatically create for the event, via the one or more APIs, a collaborative document;

interface with an external computing system to obtain identities of event attendees, wherein each event attendee is associated with an account managed by the productivity management system;

suggest that a subset of event attendees that have accepted an invite to the event receive access to the collaborative document;

populate the collaborative document with the information regarding the event from the calendar entry the information regarding the event being provided through one or more APIs between the network-accessible calendar and the system;

responsive to receiving approval of the suggestion, store the collaborative document in a shared location, accessible to the subset of event attendees, associated with the account managed by the productivity management system, based on the obtained identities;

prompt the productivity management system to modify the calendar entry to include an actionable link that provides access to the collaborative document in the shared location; and

provide access to the collaborative document responsive to an event attendee of the subset of event attendees selecting the actionable link;

in response to the event attendee selecting the actionable link, presenting the collaborative document to the event attendee, the collaborative document compatible with an external document editing application, without prompting the event attendee to separately open the external document editing application.

12. The system of claim 11 , wherein the link is a Uniform Resource Locator (URL) to the collaborative document.

13. The system of claim 11 , wherein the collaborative document is configured to be collaboratively edited by multiple digital devices at a particular time.

14. The system of claim 11 , wherein the instructions further cause the one or more processors to:

monitor the collaborative document for changes; and

notify at least some of the event attendees of the changes.

15. The system of claim 11 , wherein the instructions further cause the one or more processors to restrict write access to the collaborative document after an end time of the event.

16. The system of claim 11 , wherein the instructions further cause the one or more processors to modify the collaborative document using a title of the calendar entry.

17. The system of claim 11 , wherein the instructions further cause the one or more processors to store the collaborative document in a network-accessible content management system.

18. The system of claim 11 , wherein the instructions further cause the one or more processors to suggest boilerplate content for the collaborative document based on the calendar entry.

19. The system of claim 18 , wherein the instructions further cause the one or more processors to receive instructions to accept or to deny the boilerplate content.

20. The system of claim 11 , wherein the instructions further cause the one or more processors to: provide, by a document editor application, to at least one of the event attendees a first prompt to invoke the collaborative document.

21. The system of claim 20 , wherein the instructions further cause the one or more processors to: provide, by the document editor application, an ordered list of prompts wherein an order of the first prompt in the ordered list of prompts changes as a time and date of the event approaches.

22. A non-transitory computer readable medium comprising executable instructions, the instructions executable by one or more processors to perform a method, the method comprising:

accessing a network-accessible calendar, maintained by a productivity management system via one or more application programming interfaces (APIs) maintained by the productivity management system;

identifying a calendar entry in the network-accessible calendar, the calendar entry comprising information associated therewith that includes at least an event and event attendees by gathering productivity information via the one or more APIs, the productivity information comprising information related to one or more calendar entries in the network-accessible calendar;

responsive to identifying the calendar entry, automatically creating for the event, via the one or more APIs, a collaborative document without actions of multiple users associated with an account managed by the productivity management system;

interfacing with an external computing system to obtain identities of event attendees, wherein each event attendee is associated with an account managed by the productivity management system;

suggesting that a subset of event attendees that have accepted an invite to the event receive access to the collaborative document;

responsive to receiving approval of the suggestion, storing the collaborative document in a shared location, accessible to the subset of event attendees, associated with the account managed by the productivity management system, based on the obtained identities;

prompting the productivity management system to modify the calendar entry to include an actionable link that provides access to the collaborative document in the shared location; and

providing access to the collaborative document responsive to an event attendee of the subset of event attendees selecting the actionable link;

in response to the event attendee selecting the actionable link, presenting the collaborative document to the event attendee, the collaborative document compatible with an external document editing application, without prompting the event attendee to separately open the external document editing application.

23. The computer-implemented method of claim 1 , wherein interfacing with the external computing system to obtain the identities of the event attendees, wherein each event attendee is associated with the account managed by the productivity management system comprises:

identifying the identities of the event attendees based on a common domain associated with each event attendee.

24. The computer-implemented method of claim 1 , wherein interfacing with the external computing system to obtain the identities of the event attendees, wherein each event attendee is associated with the account managed by the productivity management system comprises:

identifying the identities of the event attendees based on each event attendee being a member of a group to which a creator of the calendar entry is a member.

25. The computer-implemented method of claim 1 , wherein interfacing with the external computing system to obtain the identities of the event attendees, wherein each event attendee is associated with the account managed by the productivity management system comprises:

identifying the identities of the event attendees based on prior participation in past events involving similar subject matter to the calendar entry.

Assignments (6)
RELEASE OF SECURITY INTEREST Recorded Dec 13, 2024
From: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
To: DROPBOX, INC.
Reel/Frame 069635/0332 →
SECURITY INTEREST Recorded Dec 12, 2024
From: DROPBOX, INC.
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 069604/0611 →
RELEASE OF SECURITY INTEREST Recorded Dec 12, 2024
From: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
To: DROPBOX, INC.
Reel/Frame 069613/0744 →
PATENT SECURITY AGREEMENT Recorded Mar 10, 2021
From: DROPBOX, INC.
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 055670/0219 →
SECURITY INTEREST Recorded Apr 14, 2017
From: DROPBOX, INC.
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 042254/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 24, 2017
From: CHANG, TSUNG-HSIANG; CACIOPPO, CHRISTINA; HASSAN, RYHAN; COHEN, PHILLIP
To: DROPBOX, INC.
Reel/Frame 041067/0980 →
Continuity (1)
Related Publication 20170083871A1 · Mar 23, 2017
Cited By (1)
US 12,718,204