Processing a content item with regard to an event

• US 9,535,911 B2
• Filed: 06/27/2008
• Issued: 01/03/2017
• Est. Priority Date: 06/29/2007
• Status: Active Grant

• Current Assignee: Pulsepoint Incorporated (Pulsepoint Holdings LLC)
• Original Assignee: Pulsepoint Incorporated (Pulsepoint Holdings LLC)
• Inventors: Tareen, Amra Q., Sood, Sanjay C., Birnbaum, Lawrence A., Hammond, Kristian J., Sundelof, Erik
• Primary Examiner(s): VU, BAI DUC
• Application Number:
  US12/215,701
• Publication Number:
  US 20090019013A1
• Time in Patent Office: 3,112 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 16/219 Managing data history or versioning querying versioned data G06F16/2474; querying temporal data G06F16/2477
• CPC Class Codes: G06F 16/38 Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
• CPC Class Codes: G06F 16/40 of multimedia data, e.g. slideshows comprising image and additional audio data retrieval of still image data G06F16/50; retrieval of audio data G06F16/60; retrieval of video data G06F16/70
• CPC Class Codes: G06F 16/489 using time information
• CPC Class Codes: G06F 16/9537 Spatial or temporal dependent retrieval, e.g. spatiotemporal queries
• CPC Class Codes: G06Q 10/00 Administration; Management

Abstract

Aggregating a content item with an event is disclosed. An event is created based on a user-provided or a feed sourced content item. The user-provided or feed sourced content item is aggregated with the event. The user-provided or feed sourced content item is identified using a query to one or more repositories.

Claims

1. A method, comprising the steps of:

by computer, analyzing information contained in a content item to ascertain an event that is subject of the content item, and a time and geographic location of the event, the content item received from one or more streams of content, the stream(s) presenting content items relating to events including events that occur for the first time in the stream(s);

by computer, evaluating whether the event ascertained from the content item is currently stored in an event repository of stored events, the event repository designed to store user submitted events and feed-sourced events, and to index content items under respective events to which the content items relate, and designed to permit retrieval of stored content items indexed by event;

when the evaluation determines that the ascertained event is not in the event repository, automatically as a consequence of the determination that the ascertained event does not exist in the event repository, by computer;

creating a new event in the event repository corresponding to the ascertained event, and indexing the content item under the newly-created event;

generating a query based on the ascertained event ascertained from the content item;

issuing the query via one or more internet search engines to locate additional content items relating to the ascertained event; and

aggregating into the event in the event repository the additional content items returned in response to the query, indexed under the ascertained event.

2. The method according to claim 1, further comprising:

evaluating received feed sourced events to ascertain whether the feed sourced events relate to events previously stored in the event repository, and if so, by computer aggregating content items indexed under the feed source event.

3. The method according to claim 2, further comprising the step of:

based on the content item being aggregated with a pre-existing event in the event repository, revising a location, a category, a title, a summary, or a combination thereof for the pre-existing event.

4. The method according to claim 1, further comprising the step of:

building a context model for the content item using tags, title, summary, and user contributed textual information of the content item, wherein the query is generated using the context model.

5. The method according to claim 1, further comprising the step of:

querying an event repository using user generated text and tags associated with the content item.

6. The method according to claim 1, further comprising the step of:

aggregating additional content items indexed under the new repository event by;

creating a set of queries relating to the new event; and

submitting the set of queries to one or more online sources, one or more repositories, or a combination thereof.

7. The method according to claim 6, further comprising the steps of:

receiving the additional content items from one or more online sources, one or more repositories, or a combination thereof addressed by the issued query; and

filtering and ordering the additional content items based on relevance to the ascertained event.

8. The method of claim 1, further comprising the step of:

by computer, analyzing metadata associated with the content item to ascertain an event that is subject of the content item, and a time and geographic location of the event.

9. The method of claim 1, wherein:

the event repository is organized in two or more subrepositories, the subrepositories corresponding to two or more classes of event.

10. The method of claim 1, wherein:

the event repository is organized in two or more subrepositories, the subrepositories corresponding to two or more classes of content.

11. The method of claim 1, further comprising the step of:

the content item is an event specification from a user, directly identifying the event by name, time, and location, as a request to include the event into the repository and to index content items associated with the event.

12. The method of claim 11, further comprising the step of:

evaluating a reputation of the user to determine how to index the event into the repository and to query for content relating to the event.

13. The method of claim 1, further comprising the step of:

based on the ascertained event and content item, formulating a second query for events related to the ascertained event;

issuing the second query to the event repository.

14. The method of claim 1, further comprising the step of:

on receipt of a subsequent content item, ascertaining a subsequent event of the subsequent content item, and determining that the ascertained subsequent event is in the event repository, automatically issuing a query via one or more internet search engines to locate additional content items relating to the ascertained event to update the indexed content indexed under the repository event.

15. A system for associating a content item with an event, comprising:

at least one processor; and

at least one non-transitory computer readable medium storing instructions executable by the at least one processor to;

when a content item is received over a computer network, analyze the content item to ascertain an event that is subject of the content item, and a time and geographic location of the ascertained event;

evaluate whether the event ascertained from the content item comprises a new event or relates to an existing event stored in an event repository of stored events, the event repository designed to store user submitted events and feed-sourced events, and to index content items under respective events to which the content items relate, and designed to permit retrieval of stored content items indexed by event;

when the evaluation determines that the ascertained event is not in the event repository, automatically as a consequence of the determination that the ascertained event does not exist in the event repository;

create a new event in the event repository corresponding to the ascertained event, and to index the content item under the newly-created event;

generate a query based on the ascertained event ascertained from the content item;

issue the query via one or more internet search engines to locate additional content items relating to the ascertained event; and

aggregate into the newly-created repository event additional content returned in response to the query, indexed under the repository event.

16. The system of claim 15, wherein the instructions are further programmed to cause the processor to:

evaluate feed sourced events to ascertain whether the feed sourced events relate to events previously stored in the event repository, and if so, aggregate content items indexed under the matching feed source event.

17. The system of claim 16, wherein the instructions are further programmed to cause the processor to:

based on the content item being aggregated with a pre-existing event in the event repository, revise a location, a category, a title, a summary, or a combination thereof for the pre-existing event.

18. The system of claim 15, wherein the instructions are further programmed to cause the processor to:

build a context model for the content item using tags, title, summary, and user contributed textual information of the content item, wherein the query is generated using the context model.

19. The system of claim 15, wherein the instructions are further programmed to cause the processor to:

query an event repository using user generated text and tags associated with the content item.

20. The system of claim 15, wherein the instructions are further programmed to cause the processor to:

aggregate additional content items indexed under the new repository event by;

create a set of queries relating to the new event; and

submit the set of queries to one or more online sources, one or more repositories, or a combination thereof.

21. The system of claim 20, wherein the instructions are further programmed to cause the processor to:

receive the additional content items from one or more online sources, one or more repositories, or a combination thereof addressed by the issued query; and

filter and order the additional content items based on relevance to the ascertained event.

22. The system of claim 15, the instructions being further programmed to cause the processor to:

analyze metadata associated with the content item to ascertain an event that is subject of the content item, and a time and geographic location of the event.

23. The system of claim 15, wherein:

the event repository is organized in two or more subrepositories, the subrepositories corresponding to two or more classes of event.

24. The system of claim 15, wherein:

the event repository is organized in two or more subrepositories, the subrepositories corresponding to two or more classes of content.

25. The system of claim 15, wherein:

the content item is an event specification from a user, directly identifying the event by name, time, and location, as a request to include the event into the repository and to index content items associated with the event.

26. The system of claim 25, the instructions being further programmed to cause the processor to:

evaluate a reputation of the user to determine how to index the event into the repository and to query for content relating to the event.

27. The system of claim 15, the instructions being further programmed to cause the processor to:

based on the ascertained event and content item, formulate a second query for events related to the ascertained event;

issue the second query to the event repository.

28. A non-transitory computer readable medium storing instructions translatable by at least one processor to perform:

analyze information contained in a content item to ascertain an event that is subject of the content item, and a time and geographic location of the event;

evaluate whether the event ascertained from the content item is currently stored in an event repository of stored events, the event repository designed to store user submitted events and feed sourced events, and to index content items under respective events to which the content items relate, and designed to permit retrieval of stored content items indexed by event;

when the evaluation determines that the ascertained event is not found in the event repository, automatically as a consequence of the determination that the ascertained event does not exist in the event repository to;

create a new event in the event repository corresponding to the ascertained event, and to index the content item under the newly-created event;

generate a query based on the ascertained event ascertained from the content item;

issue the query via one or more internet search engines to locate additional content items relating to the ascertained event; and

aggregate into the event in the event repository the additional content items returned in response to the query, indexed under the ascertained event.

29. The computer program product of claim 28, wherein the instructions are further programmed to cause the processor to:

evaluate feed sourced events to ascertain whether the feed sourced events relate to events previously stored in the event repository, and if so, aggregate content items indexed under the matching feed source event.

30. The computer program product of claim 29, wherein the instructions are further programmed to cause the processor to:

based on the content item being aggregated with a pre-existing event in the event repository, revising a location, a category, a title, a summary, or a combination thereof for the pre-existing event.

31. The computer program product of claim 28, wherein the instructions are further programmed to cause the processor to:

build a context model for the content item using tags, title, summary, and user contributed textual information of the content item, wherein the query is generated using the context model.

32. The computer program product of claim 28, wherein the instructions are further programmed to cause the processor to:

aggregate additional content items indexed under the new repository event by;

create a set of queries relating to the new event; and

submit the set of queries to one or more online sources, one or more repositories, or a combination thereof.

33. The computer program product of claim 32, wherein the instructions are further programmed to cause the processor to:

receive the additional content items from one or more online sources, one or more repositories, or a combination thereof addressed by the issued query; and

filter and order the additional content items based on relevance to the ascertained event.