IP Library › Granted Patent US 11,907,237
Granted Patent B2
US 11,907,237 · App. 18/153,332 · Granted Feb 20, 2024

Gathering and contributing content across diverse sources

Inventors: Joshua E. Decker (Redmond, WA); Sean Michael Sperte (Kirkland, WA); Timothy R. Shimotakahara (Bellevue, WA)
Assignee: Tagboard, Inc.
G06F16/2471G06F16/24573G06F16/252G06F16/285G06F16/951G06F16/9535
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 11,907,237
App. No.
18/153,332
Granted
Feb 20, 2024
Kind
B2
Abstract

A content unification system is described herein that aligns related content from various sources into one unified stream. The system leverages tagging (e.g., hashtags or other added metadata associated with content) to filter and connect related content across sites, formats, and sources. One component of the system is a user-friendly and customizable “dash board” view of the various topics, called a “tagboard”. Tagboards can be quickly and easily created by users and can be embedded on any website. Users can interact with various content sources such as blogs, forums, or services without leaving the tagboard they are viewing. The content unification system provides users the tools to make the web efficient, increase user interaction, and increase the signal to noise ratio. The system also allows site owners and publishers to monetize their traffic better by directing advertisements to their content in real time.

Claims (44)

1. A computer-implemented method in a content unification system to cause data from network accessible resources to be redisplayed in a uniform visual fashion, the method comprising:

automatically retrieving, via an application programming interface (API), data from a network accessible resource, the retrieved data having a retrieved format and including content related to a particular data classification;

identifying the particular data classification associated with the retrieved data;

normalizing the retrieved data to allow the retrieved data to be displayed in a different format from the retrieved format;

generating metadata associated with the retrieved data, the metadata including an identification of a source of the retrieved data and the particular data classification associated with the retrieved data;

storing the data and associated metadata in a data store for subsequent retrieval;

receiving criteria from a user specifying which stored data is to be redisplayed;

identifying stored data which satisfies the received user criteria;

accessing a rendering template having a specified format for redisplaying stored data in a uniform visual fashion;

formatting the stored data in the format specified by the rendering template; and

providing the formatted data to a site to allow data satisfying the received user criteria to be displayed in an embedded fashion on the site, wherein the embedded data is displayed in a uniform visual fashion different from the retrieved format;

wherein the preceding steps are performed by at least one processor.

2. The computer-implemented method of claim 1 , wherein normalizing the data comprises removing information from the data that affects redisplay of the data.

3. The computer-implemented method of claim 2 , wherein the removed information is hypertext markup language (HTML), cascading style sheets (CSS), or other formatting instructions.

4. The computer-implemented method of claim 2 , wherein normalizing the data further comprises removing words or truncating content.

5. The computer-implemented method of claim 1 , wherein the generated metadata further includes a time period associated with the data or a timestamp associated with the data.

6. The computer-implemented method of claim 1 , wherein the generated metadata further includes a geographical location associated with the data or an author associated with the data.

7. The computer-implemented method of claim 1 , wherein the particular data classification is a hashtag.

8. The computer-implemented method of claim 1 , wherein the rendering template prepares data for display on a television, mobile computing device, or web browser.

9. The computer-implemented method of claim 1 , wherein the rendering template further retrieves and displays media with the stored data.

10. The computer-implemented method of claim 9 , wherein the media includes photos, video, embedded files, or other types of content.

11. The computer-implemented method of claim 1 , wherein the site is a web site, a kiosk, or other information display.

12. A non-transitory computer-readable medium having computer-executable instructions stored thereon that, in response to execution by one or more processors of a content unification system, cause the content unification system to perform actions to cause data from network accessible resources to be redisplayed in a uniform visual fashion, the actions comprising:

automatically retrieving, via an application programming interface (API), data from a network accessible resource, the retrieved data having a retrieved format and including content related to a particular data classification;

identifying the particular data classification associated with the retrieved data;

normalizing the retrieved data to allow the retrieved data to be displayed in a different format from the retrieved format;

generating metadata associated with the retrieved data, the metadata including an identification of a source of the retrieved data and the particular data classification associated with the retrieved data;

storing the data and associated metadata in a data store for subsequent retrieval;

receiving criteria from a user specifying which stored data is to be redisplayed;

identifying stored data which satisfies the received user criteria;

accessing a rendering template having a specified format for redisplaying stored data in a uniform visual fashion;

formatting the stored data in the format specified by the rendering template; and

providing the formatted data to a site to allow data satisfying the received user criteria to be displayed in an embedded fashion on the site, wherein the embedded data is displayed in a uniform visual fashion different from the retrieved format;

wherein the preceding steps are performed by at least one processor.

13. The non-transitory computer-readable medium of claim 12 , wherein normalizing the data comprises removing information from the data that affects redisplay of the data.

14. The non-transitory computer-readable medium of claim 2 , wherein the removed information is hypertext markup language (HTML), cascading style sheets (CSS), or other formatting instructions.

15. The non-transitory computer-readable medium of claim 2 , wherein normalizing that data further comprises removing words or truncating content.

16. The non-transitory computer-readable medium of claim 1 , wherein the generated metadata further includes a time period associated with the data or a timestamp associated with the data.

17. The non-transitory computer-readable medium of claim 1 , wherein the generated metadata further includes a geographical location associated with the data or an author associated with the data.

18. The non-transitory computer-readable medium of claim 1 , wherein the particular data classification is a hashtag.

19. The non-transitory computer-readable medium of claim 1 , wherein the rendering template prepares data for display on a television, mobile computing device, or web browser.

20. The non-transitory computer-readable medium of claim 1 , wherein the rendering template further retrieves and displays media with the stored data.

21. The non-transitory computer-readable medium of claim 9 , wherein the media includes photos, video, embedded files, or other types of content.

22. The non-transitory computer-readable medium of claim 1 , wherein the site is a web site, a kiosk, or other information display.

Continuity (7)
Continuation 17117084 · Dec 9, 2020
Continuation 15696104 · Sep 5, 2017
Continuation 15206159 · Jul 8, 2016
Continuation 14849440 · Sep 9, 2015
Continuation 13837829 · Mar 15, 2013
Provisional Application 61613411 · Mar 20, 2012
Related Publication 20230237062A1 · Jul 27, 2023