Abstract: A method may include a obtaining a first data model instance comprising an identifier string and. a set of attributes associated with a set of attribute name strings. The method may include obtaining an ontology graph that includes a first label, a second label, and an association between them. The method may include using a prediction model to select the first label based on the first data model instance and determining the second label based on the relationship. The method may include determining a selected set of labels that includes the first label and the second label to associate with the first data model instance. The method may include associating the selected set of labels with the first data model instance in a dataset that includes a plurality of records, where each record is associated with a different data model instance.

Abstract: A method includes receiving a data capture event affecting personal data of a user stored in at least one storage device of a computing system and mapped in a privacy graph database. Personal data of the user may be identified in the data capture event and classified into the data categories. In response to the data capture event, a mapping of user-centric nodes associated with the at least one user associated with other users in the privacy graph database is automatically updated using the classified personal data in the data capture event. A request by a requester for personal data of at least one specific user stored in the at least one storage device is received. The privacy graph database is queried to provide the requested personal data and locations of the requested personal data of the at least one specific user in the request stored in the computing system.

Abstract: A method may include a obtaining a first data model instance comprising an identifier string and a set of attributes associated with a set of attribute name strings. The method may include obtaining an ontology graph that includes a first label, a second label, and an association between them. The method may include using a prediction model to select the first label based on the first data model instance and determining the second label based on the relationship. The method may include determining a selected set of labels that includes the first label and the second label to associate with the first data model instance. The method may include associating the selected set of labels with the first data model instance in a dataset that includes a plurality of records, where each record is associated with a different data model instance.

Abstract: In some implementations, a system may receive inventory data associated with a data storage system. The inventory data identifies file paths for objects stored in the data storage system. The system may detect patterns in prefixes of the file paths using one or more trained machine learning models. The system may normalize the prefixes of the file paths based on the patterns detected in the prefixes. The system may detect datasets of the objects stored in the data storage system based on the normalized prefixes. The system may compare prefixes associated with the detected datasets with prefixes associated with a set of registered datasets that are registered with a metadata repository. The system may determine, based on comparing the prefixes associated with the detected datasets and the prefixes associated with the set of registered datasets, a respective registration classification for each detected dataset.

Abstract: A device may log update information associated with an operation, wherein the update information identifies one or more changes made to the dataset during the operation and a source of the operation. The device may identify, based on identification information associated with the dataset, a lineage record identifier associated with the dataset. The device may generate a lineage record associated with the operation, wherein the lineage record includes the lineage record identifier and the update information. The device may send a request for validation to an authorized node to validate the lineage record, wherein the authorized node is authorized to access the dataset. The device may store, based on the lineage record being validated by the authorized node, the lineage record in a distributed ledger, wherein the distributed ledger is accessible to a plurality of nodes to enable the plurality of nodes to access the update information.

Abstract: A device may log update information associated with an operation, wherein the update information identifies one or more changes made to the dataset during the operation and a source of the operation. The device may identify, based on identification information associated with the dataset, a lineage record identifier associated with the dataset. The device may generate a lineage record associated with the operation, wherein the lineage record includes the lineage record identifier and the update information. The device may send a request for validation to an authorized node to validate the lineage record, wherein the authorized node is authorized to access the dataset. The device may store, based on the lineage record being validated by the authorized node, the lineage record in a distributed ledger, wherein the distributed ledger is accessible to a plurality of nodes to enable the plurality of nodes to access the update information.

Abstract: A method includes receiving a data capture event affecting personal data of a user stored in at least one storage device of a computing system and mapped in a privacy graph database. Personal data of the user may be identified in the data capture event and classified into the data categories. In response to the data capture event, a mapping of user-centric nodes associated with the at least one user associated with other users in the privacy graph database is automatically updated using the classified personal data in the data capture event. A request by a requester for personal data of at least one specific user stored in the at least one storage device is received. The privacy graph database is queried to provide the requested personal data and locations of the requested personal data of the at least one specific user in the request stored in the computing system.

Abstract: A method includes receiving a data capture event affecting personal data of a user stored in at least one storage device of a computing system and mapped in a privacy graph database. Personal data of the user may be identified in the data capture event and classified into the data categories. In response to the data capture event, a mapping of user-centric nodes associated with the at least one user associated with other users in the privacy graph database is automatically updated using the classified personal data in the data capture event. A request by a requester for personal data of at least one specific user stored in the at least one storage device is received. The privacy graph database is queried to provide the requested personal data and locations of the requested personal data of the at least one specific user in the request stored in the computing system.

Abstract: A method may include a obtaining a first data model instance comprising an identifier string and. a set of attributes associated with a set of attribute name strings. The method may include obtaining an ontology graph that includes a first label, a second label, and an association between them. The method may include using a prediction model to select the first label based on the first data model instance and determining the second label based on the relationship. The method may include determining a selected set of labels that includes the first label and the second label to associate with the first data model instance. The method may include associating the selected set of labels with the first data model instance in a dataset that includes a plurality of records, where each record is associated with a different data model instance.

Abstract: A method includes receiving a data capture event affecting personal data of a user stored in at least one storage device of a computing system and mapped in a privacy graph database. Personal data of the user may be identified in the data capture event and classified into the data categories. In response to the data capture event, a mapping of user-centric nodes associated with the at least one user associated with other users in the privacy graph database is automatically updated using the classified personal data in the data capture event. A request by a requester for personal data of at least one specific user stored in the at least one storage device is received. The privacy graph database is queried to provide the requested personal data and locations of the requested personal data of the at least one specific user in the request stored in the computing system.

Abstract: A device may log update information associated with an operation, wherein the update information identifies one or more changes made to the dataset during the operation and a source of the operation. The device may identify, based on identification information associated with the dataset, a lineage record identifier associated with the dataset. The device may generate a lineage record associated with the operation, wherein the lineage record includes the lineage record identifier and the update information. The device may send a request for validation to an authorized node to validate the lineage record, wherein the authorized node is authorized to access the dataset. The device may store, based on the lineage record being validated by the authorized node, the lineage record in a distributed ledger, wherein the distributed ledger is accessible to a plurality of nodes to enable the plurality of nodes to access the update information.

Abstract: A method includes receiving a data capture event affecting personal data of a user stored in at least one storage device of a computing system and mapped in a privacy graph database. Personal data of the user may be identified in the data capture event and classified into the data categories. In response to the data capture event, a mapping of user-centric nodes associated with the at least one user associated with other users in the privacy graph database is automatically updated using the classified personal data in the data capture event. A request by a requester for personal data of at least one specific user stored in the at least one storage device is received. The privacy graph database is queried to provide the requested personal data and locations of the requested personal data of the at least one specific user in the request stored in the computing system.

Abstract: A device may log update information associated with an operation, wherein the update information identifies one or more changes made to the dataset during the operation and a source of the operation. The device may identify, based on identification information associated with the dataset, a lineage record identifier associated with the dataset. The device may generate a lineage record associated with the operation, wherein the lineage record includes the lineage record identifier and the update information. The device may send a request for validation to an authorized node to validate the lineage record, wherein the authorized node is authorized to access the dataset. The device may store, based on the lineage record being validated by the authorized node, the lineage record in a distributed ledger, wherein the distributed ledger is accessible to a plurality of nodes to enable the plurality of nodes to access the update information.