Data Repository Ownership Lineage Using User Linkage Data
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional methods fail to accurately identify data repository ownership, especially in large data systems with a large and frequently changing user set, leading to inaccuracies and outdated ownership information.
Innovation Solution
A computer-implemented method that identifies data repository ownership by processing metadata and system access data, utilizing a user linkage database to retrieve up-to-date ownership information, and employing scanning processes to determine prominent or single owners.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If conventional methods are used to identify data repository ownership, then the process is simple, but the accuracy of ownership identification deteriorates in large data systems with frequently changing user sets
Solution Approach 1:
The ownership identification process is segmented into multiple distinct phases: initial system access data analysis, scanning process execution for detailed file-level access information collection, user linkage database querying, and prominence determination. This segmentation allows each phase to focus on specific tasks, improving overall accuracy while managing complexity through structured decomposition of the identification workflow.
Solution Approach 2:
The system performs preliminary actions by first collecting and analyzing system access data before executing the full scanning process. The patent implements preliminary filtering and analysis of available access information to determine whether a full scan is necessary, and preliminarily identifies prominent users from partial data before comprehensive verification. This preliminary action reduces unnecessary full scans and improves efficiency.
2Reliability
If system access data is processed to identify owners, then up-to-date ownership information can be obtained, but the processing time increases
Solution Approach 1:
The system applies partial action by scanning only the necessary portion of data repository access information rather than processing all possible data. The scanning process is configured to collect sufficient access information to identify prominent users without exhaustively analyzing every file and user interaction history. This partial scanning approach obtains reliable ownership information while minimizing processing time.
Solution Approach 2:
The system implements feedback mechanisms where the results from initial system access data analysis inform whether a full scanning process is required. The patent uses feedback from preliminary owner identification attempts to determine if additional scanning is necessary, and uses feedback from the scanning process to verify and refine ownership conclusions. This feedback loop ensures reliability while avoiding unnecessary processing steps.
3Measurement precision
If a scanning process is executed to identify prominent access users, then accurate ownership can be determined, but the computational resources required increase
Solution Approach 1:
The scanning process applies local quality by focusing computational resources on analyzing access patterns for specific files and users that are most relevant to ownership determination. Rather than uniformly processing all data with the same intensity, the system identifies and concentrates scanning efforts on critical access information that most strongly indicates prominent users, thereby improving accuracy while reducing overall computational resource consumption.
Data Source
AI summary
Embodiments of the present disclosure provide for improved identification of ownership and/or ownership lineage for a data repository, such as a shared file drive. Ownership data and/or ownership lineage data is identified based on data associated with the data repository itself and/or file data objects stored thereon in conjunction with data from a user linkage database. In this regard, accurate identification of a particular owner or owner(s) of a data repository may be determined from the data repository, and the user linkage database may serve additional details of such owner(s), linkages to other user(s) and/or group(s) of users embodying owner(s), and/or the like. Identified ownership data and/or ownership lineage data may be used for a myriad of additional processes, such as to notify users, determine what data repositories to perform detailed, efficient scans of based on group membership of the owner of said data repositories, or the like.


