# US 11,907,237 B2 · Gathering and contributing content across diverse sources

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 11,907,237 B2
- Document ID: US11907237B2
- Status: Granted
- Kind: B2
- Application number: 18/153,332
- Filed: 2023-01-11
- Published: 2023-07-27
- Granted: 2024-02-20
- Earliest claimed: 2012-03-20
- Assignees: Tagboard, Inc.
- Applicants: Tagboard, Inc.
- Inventors: Joshua E. Decker; Sean Michael Sperte; Timothy R. Shimotakahara
- Web page: https://patentgrep.com/patent/US11907237B2

## CPC

- G06F 16/2471: {Distributed queries}
- G06F 16/24573: {using data annotations, e.g. user-defined metadata}
- G06F 16/252: {between a Database Management System and a front-end application}
- G06F 16/285: {Clustering or classification}
- G06F 16/951: Indexing; Web crawling techniques
- G06F 16/9535: Search customisation based on user profiles and personalisation
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## 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

### Claim 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.

### Claim 2 (depends on 1)

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

### Claim 3 (depends on 2)

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

### Claim 4 (depends on 2)

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

### Claim 5 (depends on 1)

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.

### Claim 6 (depends on 1)

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.

### Claim 7 (depends on 1)

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

### Claim 8 (depends on 1)

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

### Claim 9 (depends on 1)

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

### Claim 10 (depends on 9)

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

### Claim 11 (depends on 1)

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

### Claim 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.

### Claim 13 (depends on 12)

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.

### Claim 14 (depends on 2)

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.

### Claim 15 (depends on 2)

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

### Claim 16 (depends on 1)

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.

### Claim 17 (depends on 1)

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.

### Claim 18 (depends on 1)

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

### Claim 19 (depends on 1)

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.

### Claim 20 (depends on 1)

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

### Claim 21 (depends on 9)

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

### Claim 22 (depends on 1)

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