# US 10,372,769 B2 · Displaying results, in an analytics visualization dashboard, of federated searches across repositories using as inputs attributes of the analytics visualization dashboard

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

- Number: US 10,372,769 B2
- Document ID: US10372769B2
- Status: Granted
- Kind: B2
- Application number: 15/090,091
- Filed: 2016-04-04
- Published: 2017-10-05
- Granted: 2019-08-06
- Earliest claimed: 2016-04-04
- Assignees: Entit Software LLC
- Applicants: Hewlett Packard Enterprise Development LP
- Inventors: Ashok Chandnani; Kevin E. Matthews; Kirk Alan Kaufman
- Web page: https://patentgrep.com/patent/US10372769B2

## CPC

- G06F 16/256: {in federated or virtual databases}
- G06F 16/24: Querying
- G06F 16/81: Indexing, e.g. XML tags; Data structures therefor; Storage structures
- 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

Examples receive an input indicating a Graphical User Interface (GUI) selection of an attribute displayed in an analytics visualization dashboard, where the selected attribute is associated with a search term. Some examples perform a federated search across a plurality of repositories using the search term and through a content web service. Some examples obtain results of the federated search performed in the repositories, the results being content metadata associated to the search term, the content metadata relating to contents stored in the repositories and the content metadata including links to the contents. Some examples display the content metadata in the analytics visualization dashboard and provide access, through the links, to the contents associated with the displayed content metadata.

## Claims

### Claim 1

A method comprising:
receiving, by a computing platform, an input indicating a Graphical User Interface (GUI) selection of an attribute displayed in an analytics visualization dashboard, wherein the selected attribute is associated with a search term;
performing, by the computing platform, a federated search across a plurality of repositories using the search term and through a content web service, wherein the federated search includes a specific search for each repository that is based on a search configuration for each repository type, and wherein the search configuration includes search field definitions that specify metadata fields to be searched against the search term and a limit on a number of results retrieved;
forwarding at least one search configuration for the plurality of repositories to the content web service;
obtaining, by the computing platform, results of the federated search performed in the plurality of repositories, wherein the results are content metadata associated to the search term, the content metadata relating to contents stored in the plurality of repositories, and the content metadata further comprising links to the contents;
sending the at least one search configuration for the plurality of repositories to the analytics visualization dashboard for display; and
displaying the at least one search configuration for the plurality of repositories and the content metadata in the analytics visualization dashboard and providing access, through the links in the analytics visualization dashboard, to the contents associated with the displayed content metadata.

### Claim 2 (depends on 1)

The method of claim 1, wherein the results provided are content metadata comprising the search term associated to the attribute.

### Claim 3 (depends on 1)

The method of claim 1, wherein content metadata is metadata in XML format.

### Claim 4 (depends on 3)

The method of claim 3, wherein providing results of the federated search comprises parsing the XML metadata in an in-memory table.

### Claim 5 (depends on 1)

The method of claim 1, wherein the content metadata displayed in the analytics visualization dashboard at least comprises a source repository name, a content title, a thumbnail Uniform Resource Locator (URL) and a content URL.

### Claim 6 (depends on 1)

The method of claim 1, wherein the federated search across the plurality of repositories is performed by a web service invoker scripted in the analytics visualization dashboard, and wherein the web service invoker is to generate Representational State Transfer (Rest) Application Programming Interface (API) calls to the content web service to perform the federated search in the plurality of repositories.

### Claim 7 (depends on 1)

The method of claim 1, wherein the results of the federated search are provided by the repositories to the content web service as a Java Script Object Notation (JSON) object.

### Claim 8

An article comprising at least one non-transitory machine readable storage medium comprising instructions executable by a processor resource of a computing platform to:
receive an input indicating a Graphical User Interface (GUI) selection of an attribute displayed in an analytics visualization dashboard, wherein the selected attribute is associated with a search term;
receive a search configuration for each repository of a plurality of repositories, wherein each search configuration defines at least one metadata field within the repository to be searched against the search term and a limit on a number of results retrieved;
perform a federated search across the plurality of repositories using the search term and through a content web service, wherein the federated search includes a specific search based on the search configuration for each repository of the plurality of repositories;
forward at least one search configuration for the plurality of repositories to the content web service;
obtain results of the federated search performed in the plurality of repositories, wherein the results are content metadata associated to the search term, the content metadata relating to contents stored in the plurality of repositories and the content metadata further comprising links to the contents;
send the at least one search configuration for the plurality of repositories to the analytics visualization dashboard for display; and
display the at least one search configuration for the plurality of repositories and the content metadata in the analytics visualization dashboard and provide access, through the links in the analytics visualization dashboard, to the contents associated with the displayed content metadata.

### Claim 9 (depends on 8)

The article of claim 8, wherein the results are content metadata in XML, format that at least comprise a source repository identifier, a title, a thumbnail URL and a content URL.

### Claim 10 (depends on 8)

The article of claim 8, wherein the instructions to perform a federated search across the plurality of repositories comprise instructions to generate Representational State Transfer (Rest) Application Programming Interface (API) calls to the content web service to perform the federated search in the plurality of repositories.

### Claim 11 (depends on 9)

The article of claim 9, wherein the instructions to obtain results of the federated search comprise instructions to parse the XML metadata in an in-memory table.

### Claim 12

A system comprising:
a display device to display an analytics visualization dashboard showing a plurality of attributes; and
a computing platform to:
receive an input indicating a Graphical User Interface (GUI) selection of one of the attributes displayed in the analytics visualization dashboard, wherein the selected attribute is associated with a search term;
perform a federated search across a plurality of repositories using the search term and through a content web service;
obtain results of the federated search performed in the repositories, wherein the results are content metadata associated to the search term, the content metadata relating to contents stored in the repositories and the content metadata further comprising links to the contents;
generate search configurations for each one of the plurality of repositories, wherein each search configuration defines at least one metadata field within the repository to be searched against the search term and a limit on a number of results retrieved;
forward at least one search configuration for the plurality of repositories to the content web service; and
send the at least one search configuration for the plurality of repositories to the analytics visualization dashboard for display; and
wherein a dashboard engine is further to utilize the display device to display the at least one search configuration for the plurality of repositories and the content metadata in the analytics visualization dashboard and provide access, through the links in the analytics visualization dashboard, to the contents associated with the displayed content metadata.

### Claim 13 (depends on 12)

The system of claim 12, wherein the computing platform comprises an in-memory table to store the content metadata results of the federated search, the results being previously parsed.

### Claim 14 (depends on 12)

The system of claim 12, wherein the analytics visualization dashboard comprises a web service invoker to generate Representational State Transfer (Rest) Application Programming Interface (API) calls to the content web service to perform the federated search in the plurality of repositories.
