Systems and methods for selectively storing event data

• US 9,672,232 B1
• Filed: 09/13/2012
• Issued: 06/06/2017
• Est. Priority Date: 03/31/2004
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Lawrence, Stephen R., Auerbach, David Benjamin, Khan, Omar Habib
• Primary Examiner(s): DAYE, CHELCIE L
• Application Number:
  US13/613,193
• Time in Patent Office: 1,727 Days
• Field of Search: 707741, 709203
• CPC Class Codes: G06F 16/2228 Indexing structures
• CPC Class Codes: G06F 16/951 Indexing; Web crawling techniques

Abstract

Methods and systems are provided for selectively storing event data. In one described method, an event associated with an article is captured. The captured event can comprise event data. The method further comprises evaluating the event for satisfaction of a criterion. If the event satisfies the criterion, it is indexed.

Claims

1. A computer-implemented method comprising the following operations performed by at least one processor:

capturing an event associated with an article, wherein the event comprises activity associated with the article on a client device or a client application;

generating event data associated with the event, the event data including at least one of article content, a title of the article, metadata associated with the article, a link to the article, a time of the event, a date of the event, and an image of the article;

determining whether the event is indexable, the determination responsive to the event data satisfying at least one criterion, the at least one criterion comprising an event capture criterion related to characteristics associated with capturing the event; and

indexing the event responsive to a determination that the event is indexable, wherein the indexing comprises;

determining an event capture frequency;

portioning the event data for the event determined to be indexable into a first portion and a second portion based, at least in part, on the determined event capture frequency;

storing the first portion of the event data within a data store; and

excluding the second portion of the event data from the data store; and

wherein for a first event indexed by a first indexing at a first time and for a second event indexed by a second indexing at a second time, the first portion and the second portion for partitioning the event data for the first indexing is reapportioned and different from the first portion and the second portion for partitioning the event data for the second indexing, and wherein the first event and the second event are of the same type.

2. The method of claim 1, wherein determining whether the event is indexable comprises capturing only part of the event data with the criterion.

3. The method of claim 1, wherein the article comprises a search result and the second portion of the event data comprises a search term, the search result generated in response to the search term.

4. The method of claim 1, wherein the first portion of the event data comprises meta data associated with the article.

5. The method of claim 1, wherein the first portion of the event data comprises an image in the article content.

6. The method of claim 1, wherein the first portion of the event data comprises an audio file in the article content.

7. The method of claim 1, wherein the first portion of the event data comprises text in the article content.

8. The method of claim 1, wherein the second portion of the event data comprises meta data associated with the article.

9. The method of claim 1, further comprising portioning the article content into the first portion and the second portion.

10. The method of claim 1, further comprising requesting a user input indicating whether the portioning of the article content is acceptable to the user.

11. The method of claim 1, further comprising reapportioning at least one of the first and second portions of the event data based, at least in part, on at least one of the total amount of event data stored in the data store, the determined event capture frequency, and an amount of remaining capacity of the data store.

12. A non-transitory computer-readable storage medium containing program code executable by at least processor to perform the following operations:

capturing an event associated an article, wherein the event comprises activity associated with the article on a client device or a client application;

generating event data associated with the event, the event data including at least one of article content, a title of the article, metadata associated with the article, a link to the article, a time of the event, a date of the event, and an image of the article;

determining whether the event is indexable, the determination responsive to the event data satisfying at least one criterion, the at least one criterion comprising an event capture criterion related to characteristics associated with capturing the event; and

indexing the event responsive to a determination that the event is indexable, wherein the indexing comprises;

determining an event capture frequency;

portioning the event data for the event determined to be indexable into a first portion and a second portion based, at least in part, on the determined event capture frequency;

storing the first portion of the event data within a data store; and

excluding the second portion of the event data from the data store; and

wherein for a first event indexed by a first indexing at a first time and for a second event indexed by a second indexing at a second time, the first portion and the second portion for partitioning the event data for the first indexing is reapportioned and different from the first portion and the second portion for partitioning the event data for the second indexing, and wherein the first event and the second event are of the same type.

14. The computer-readable medium of claim 12, wherein the program code further configures the at least one processor to perform operations including comparing only a part of the event data with the criterion.

15. The computer-readable medium of claim 12, wherein the program code further configures the at least processor to perform operations comprising reapportioning at least one of the first and second portions of the event data based, at least in part, on at least one of the total amount of event data stored in the data store, the determined event capture frequency, and an amount of remaining capacity of the data store.

13. A non-transitory computer-readable storage medium containing program code executable by at least processor to perform the following operations:

capturing an event associated an article, wherein the event comprises activity associated with the article on a client device or a client application;

generating event data associated with the event, the event data including at least one of article content, a title of the article, metadata associated with the article, a link to the article, a time of the event, a date of the event, and an image of the article;

determining whether the event is indexable responsive to the event data satisfying at least one criterion, the at least one criterion comprising an event capture criterion related to characteristics associated with capturing the event;

determining an event capture frequency; and

indexing the event responsive to a determination that the event is indexable, wherein the indexing comprises;

portioning the event data into a first portion and a second portion based, at least in part, on the determined event capture frequency;

storing the first portion of the event data within a data store; and

excluding the second portion of the event data from the data store;

wherein the program code further configures the at least processor to perform operations comprising;

creating a related event object related to the event, wherein the related event object comprises a set of one or more related events;

storing the related event object at a first location within the data store;

storing a first portion of the event data at a second location within the data store; and

providing a pointer between the related event object and the one or more related events.

16. A computer system comprising:

at least one processor for executing program code; and

a non-transitory computer-readable storage medium containing program code executable by the at least one processor to perform operations comprising;

capturing an event associated an article, wherein the event comprises activity associated with the article on a client device or a client application;

generating event data associated with the event, the event data including at least one of article content, a title of the article, metadata associated with the article, a link to the article, a time of the event, a date of the event, and an image of the article;

determining whether the event is indexable, the determination responsive to the event data satisfying at least one criterion, the at least one criterion comprising an event capture criterion related to characteristics associated with capturing the event; and

indexing the event responsive to a determination that the event is indexable, wherein the indexing comprises;

determining an event capture frequency;

portioning the event data for the event determined to be indexable into a first portion and a second portion based, at least in part, on the determined event capture frequency;

storing the first portion of the event data within a data store; and

excluding the second portion of the event data from the data store; and

wherein for a first event indexed by a first indexing at a first time and for a second event indexed by a second indexing at a second time, the first portion and the second portion for partitioning the event data for the first indexing is reapportioned and different from the first portion and the second portion for partitioning the event data for the second indexing, and wherein the first event and the second event are of the same type.

18. The computer system of claim 16, wherein the article comprises an email.

17. A computer system comprising:

at least one processor for executing program code; and

a non-transitory computer-readable storage medium containing program code executable by the at least one processor to perform operations comprising;

capturing an event associated an article, wherein the event comprises activity associated with the article on a client device or a client application;

generating event data associated with the event, the event data including at least one of article content, a title of the article, metadata associated with the article, a link to the article, a time of the event, a date of the event, and an image of the article;

determining whether the event is indexable responsive to the event data satisfying at least one criterion, the at least one criterion comprising an event capture criterion related to characteristics associated with capturing the event;

determining an event capture frequency; and

indexing the event responsive to a determination that the event is indexable, wherein the indexing comprises;

portioning the event data into a first portion and a second portion based, at least in part, on the determined event capture frequency;

storing the first portion of the event data within a data store; and

excluding the second portion of the event data from the data store;

wherein the program code further configures the at least one processor to perform operations comprising;

creating a related event object related to the event, wherein the related event object comprises a set of one or more related events;

storing the related event object at a first location within the data store;

storing a first portion of the event data at a second location within the data store; and

providing a pointer between the related event object and the one or more related events.