Microsoft Technology Licensing, LLC

Adobe, Inc.

Mark Wade Heninger

Christina Storm

Sandhya Vankamamidi

Jung-Chen Hung

Amir Netz

Giovanni Moises Della-Libera

Kevin Grealish

David John Nettleton

Andrew James Peacock

Michael Justin Flasko

Chiu Ying Cheung

Cheryl Couris

Sonia P Carlson

Paula M Bach

Christian Liensberger

Chairy Chiu Ying Cheung

Paul Bryan Anastasopoulos

Arijit Chatterjee

Arno Gourdol

Andrew C Ng

James Eldon Tillinghast

Smitha Bhat Bharadwaj

Christopher Smith

Alan Jinsoo Yu

A system displays summaries of relationships of a selected data asset with other data assets at a limited number of levels upstream and downstream from the selected data asset in rows above and below the selected data asset. In each row, data assets are arranged in order of usage, with most used data asset displayed directly above or below the selected data asset. The user views grandparent-level data assets of a parent-level data asset that is directly above the selected data asset. The system includes a carousal feature to further navigate the lineage data upstream or downstream. By selecting a new data asset in the parent row, the user can view grandparent-level data assets of the newly selected data asset. The user can view multiple upstream or downstream levels arranged in respective rows displayed above or below the selected data asset. The system can analyze data from any application.

Systems and methods for dynamically rendering data lineage

A computing device including a user input device. The computing device may further include memory storing a file tree that includes a plurality of files arranged in a hierarchical structure having a plurality of nodes. The computing device may further include at least one processor configured to receive, via the user input device, a scoping selection of one or more nodes of the plurality of nodes. The scoping selection may indicate a respective display status for each of the one or more nodes. The processor may generate a scoped view of the file tree in which for each selected node, whether that selected node is displayed or hidden in the scoped view is determined based at least on the respective display status indicated for that selected node by the scoping selection. The processor may output the scoped view to a display for display in a graphical user interface (GUI).

Scoped view of file tree

Organizations may comprise a variety of resources that are assigned to various organizational units, and allocated for various projects or tasks. A user who wishes to understand the organizational structure of the resources may examine information sources, such as resource manifests and resource access logs, and interpret such information with the user's knowledge of the organization, but may fail to achieve a comprehensive, accurate, and up-to-date understanding of the organization. Instead, interactions among users and resources may be monitored to infer organizational structure; assignment of resources to organizational units; relationships among resources; and usages arising within such resource relationships. Based on such inferences, an interactive visual map may be automatically generated that depicts the arrangement of the organization and the interrelationships of the resources. A user may interact with the visualized resources, such as changing the time range or level of detail, or selecting resources to view usage information.

Inference-based visual map of organizational structure and resource usage

Job execution can be scheduled and monitored. Execution of a job results in generation of one or more data slices, which can be consumed as input by one or more related jobs. Data slices can be presented in an interactive view. Selection of a data slice in the view can trigger automatic identification of related data slices based on dependencies between data slices. Each data slice can also include and be presented with a status indicating the availability of corresponding data, such as pending, ready, or failed. Furthermore, selection of a data slice that failed to generate successfully can trigger identification of related data slices that failed or are predicted to fail to generate successfully.

Job scheduling and monitoring in a distributed computing environment

A view of data transformation jobs can be presented by way of a user interface. Related jobs can subsequently be identified automatically after a job is selected based on data dependencies between jobs. Execution status can also be determined and presented such that successful and failed execution of jobs, for example, can be differentiated. Furthermore, selection of a job run that failed to execute successfully can trigger identification of related jobs runs that failed or are predicted to fail to execute successfully.

User interface for a display screen

Growing community of inventors

Preston, WA, United States of America

Mark Wade Heninger