Abstract: Provided is a system and method for processing Compliance Data Subject Requests (DSRs) across a network by providing an executable planning model that contains a DSR domain description language, a DSR action description language, DSR problem templates, and predetermined logical, temporal, and dependency constraints. The DSR domain description language includes domains, with each domain including a domain name, and an object hierarchy representing various objects and their inter-relationship within each domain. The DSR action description language includes at least DELETE, REMOVE, OBFUSCATE, and ENCRYPT actions. The DSR problem templates each correspond to an operation that operates upon a compliance object within one of the domains, using at least one of the DSR actions. An instance of DSR processing may comprise receiving from a user DSR that includes a user object on which DSR processing is required and automatically processing the user DSR by executing the executable planning model.
Abstract: A system receives a plurality of knowledge objects (KOs). The system receives repository structure definition information, the repository structure definition information specifying one or more repository structure definitions that define respective structures for the one or more data repositories. The system groups the plurality of KOs based on the name, type, and tag attributes of the KOs, and storage paths of the underlying unit of structured, semi-structured, and unstructured data at the one or more data repositories corresponding to the KOs to generate a number of groups of KOs. For each group in the groups of KOs, the system determines a count of KOs in the group. The system generates multiple mapping structures with M to N relationships between the groups of KOs to the one or more repository structure definitions, the mapping relationship including the count of associated KOs.
Abstract: Provided is a system and method for processing Compliance Data Subject Requests (DSRs) across a network by providing an executable planning model that contains a DSR domain description language, a DSR action description language, DSR problem templates, and predetermined logical, temporal, and dependency constraints. The DSR domain description language includes domains, with each domain including a domain name, and an object hierarchy representing various objects and their inter-relationship within each domain. The DSR action description language includes at least DELETE, REMOVE, OBFUSCATE, and ENCRYPT actions. The DSR problem templates each correspond to an operation that operates upon a compliance object within one of the domains, using at least one of the DSR actions. An instance of DSR processing may comprise receiving from a user DSR that includes a user object on which DSR processing is required and automatically processing the user DSR by executing the executable planning model.