Abstract: A method executes at a computing device having one or more processors and memory. The device identifies a set of objects for a data visualization platform, each object in the set of objects representing a database, a data source, a table, a data field, a user, a visualization worksheet, or a calculated field. The device generates a data model from the set of objects. Each object of the set of objects is represented as a node in the data model and each directed edge in the data model identifies a relationship between a pair of objects. The device generates one or more shortcuts in the data model according to object types of the objects in the set of objects. Each shortcut represents a relationship, between a respective pair of objects, not represented by a directed edge. Then the device stores the data model, including the generated shortcuts, in the memory.

Abstract: Embodiments are directed to managing a data model that includes data objects associated with layers of the data model may be provided. A lineage model that includes lineage objects that has one or more lineage objects associated with a layer may be provided. A lineage object associated with a layer may be activated. A first portion data objects may be determined based on the activated lineage object. An anchor object may be determined from the first portion of data objects. A search of the data model may be employed to provide dependency information based on a position of the anchor data object in the data model. A second portion of data objects may be determined based on the dependency information. A report that includes a list of the second portion of data objects, the dependency information, or the like, may be provided.

Abstract: Embodiments are directed to managing data. A data model that includes data type nodes and relationship edges may be provided. Other data types and other data type relationships may be provided and included in the data model. If a portion of the nodes in the data model may be downstream of leaf nodes in the graphlet: the data model may be traversed to visit the downstream nodes; shortcut edges may be generated to each downstream node associated with shortcut nodes. If a second portion of the nodes in the data model may be upstream of the leaf nodes: the data model may be traversed upwards from the leaf nodes; other shortcut edges may be generated to each node visited in the upwards traversal associated with shortcut nodes.

Abstract: Embodiments are directed to managing data. A data model that includes data types, data type relationships, shortcuts may be provided. In response to a query for determining a directed path in the data model for a shortcut further actions may be performed including: determining candidate nodes and traversal edges based on the data model, a target data type, and a source data type; generating a tree based on the candidate nodes and the traversal edges; removing leaf nodes of the tree that are not the target data type; removing duplicate branches of the tree that correspond to duplicate traversal edges; determining the directed path in the data model connecting the source data type to the target data type based on the remaining candidate nodes and traversal edges; and generating a response to the query based on the directed path.

Abstract: Embodiments are directed to managing data using a network computers. A hierarchy model that includes edges that represent dependency relationships between fields may be generated. In response to a query for determining values of metadata associated with an anchor field performing further actions, including: traversing the hierarchy model upwards from the anchor field based on the query, and in response to visiting field nodes in the hierarchy model, collecting the values of the metadata that correspond to the visited field node and terminating the traversal based on a type of the query; in response to visiting a calculation node, terminating the traversal of the hierarchy model associated with the visited calculation node; and in response to visiting a flow node that is dependent on two or more other nodes, terminating the traversal of the hierarchy model. The collected metadata may be provided in a response to the query.

Abstract: Embodiments are directed to managing a data model that includes data objects associated with layers of the data model may be provided. A lineage model that includes lineage objects that has one or more lineage objects associated with a layer may be provided. A lineage object associated with a layer may be activated. A first portion data objects may be determined based on the activated lineage object. An anchor object may be determined from the first portion of data objects. A search of the data model may be employed to provide dependency information based on a position of the anchor data object in the data model. A second portion of data objects may be determined based on the dependency information. A report that includes a list of the second portion of data objects, the dependency information, or the like, may be provided.

Abstract: Embodiments are directed to managing a data model that includes data objects associated with layers of the data model may be provided. A lineage model that includes lineage objects that has one or more lineage objects associated with a layer may be provided. A lineage object associated with a layer may be activated. A first portion data objects may be determined based on the activated lineage object. An anchor object may be determined from the first portion of data objects. A search of the data model may be employed to provide dependency information based on a position of the anchor data object in the data model. A second portion of data objects may be determined based on the dependency information. A report that includes a list of the second portion of data objects, the dependency information, or the like, may be provided.

Abstract: Embodiments are directed to managing a data model that includes data objects associated with layers of the data model may be provided. A lineage model that includes lineage objects that has one or more lineage objects associated with a layer may be provided. A lineage object associated with a layer may be activated. A first portion data objects may be determined based on the activated lineage object. An anchor object may be determined from the first portion of data objects. A search of the data model may be employed to provide dependency information based on a position of the anchor data object in the data model. A second portion of data objects may be determined based on the dependency information. A report that includes a list of the second portion of data objects, the dependency information, or the like, may be provided.