Abstract: Tubing anchor catchers that include a mandrel having a first end portion and a second end portion, each end portion having threading with multiple starts, a first cone, a second cone, and a slip that is at least partially disposed between the first cone and the second cone. The first cone and second cone are coupled to the mandrel via the threading with multiple starts such that when the mandrel is rotated in a first direction with respect to at least one of the first cone and the second cone, the at least one of the first cone and the second cone is configured to move to reduce a distance between the first cone and the second cone to force the slip to move laterally from the tubing anchor catcher. Furthermore, the slip engages with a well bore or casing following between less than six rotations of the mandrel.

Abstract: A system and method for the centralized management of distributed intermittently connected runtime platforms. The method may include creating an artifact store pre-loaded with a set of utilities, libraries, and artifacts necessary to perform initial infrastructure creation in a local environment, creating an instance infrastructure for a central management system, and creating two or more availability zones, wherein each availability zone includes a private subnet and a public subnet. The method may further include transferring state data necessary to perform infrastructure as code (IaC) automation from the local environment to the artifact store.

Abstract: A system for efficient query execution over ontology-based databases and related methods are disclosed. The system is programmed to receive an ontology query from a user account against an ontology having access controls, and transform the ontology query into a set of database queries, including a set of exact aggregations or joins. The system is programmed to then estimate how much data processing is to be performed in executing the set of exact aggregations or joins, considering how much data in the ontology can be accessed by the user account under the access controls. Upon determining that the estimated amount of data processing exceeds a threshold, the system is programmed to route the set of exact aggregations or joins to a set of nodes optimized for large-scale data processing.

Abstract: A system for query execution planning over ontology-based databases and related methods are disclosed. The system is programmed to receive an ontology query from a user account against an ontology having access controls, and transform the ontology query into a set of database queries, including a plurality of joins. The system is programmed to compute the amounts of data processing associated with executing the plurality of joins in different orders on a sample of the databases representing the ontology, considering how much data in the ontology can be accessed by the user account under the access controls, and determine an execution plan corresponding to a preferred amount of data processing. Furthermore, the system is programmed to execute the set of database queries on the databases according to the execution plan, and transmit a reply to the ontology query to the user device based on a result of the execution.

Abstract: Systems and methods generate a first security node hash identifier by performing a first hash operation, such as a one-way hash, on a first data resource identifier associated with a first data resource, such as a data set, produced by a data resource platform. The systems and methods generate a dependent second security node hash identifier by performing a second hash operation on a second data resource identifier associated with a dependent second data resource produced by the data resource platform and on the first security node hash identifier, receive an access request for access to the dependent second data resource; and in response to the access request, grant permission to access the dependent second data resource to a user associated with the access request based on the dependent second security node hash identifier.

Abstract: A system for providing a unified query interface across multiple ontology-based databases and related methods are disclosed. The system is programmed to receive calls to an application programming interface for querying an ontology, where ontology data is represented in different databases respectively in different forms. For each function being called, system is programmed to select a database from the different databases based on the function type and each ontology entity type being processed by the function. The system is further programmed to retrieve data from each selected database, merge the retrieval results as appropriate, and transform the final result to ontology data in response to the calls.

Abstract: A distributed, transactional database uses timestamps, such as logical clock values, for entry versioning and transaction management in the database. To write to the database, a service requests a timestamp to be inserted into the database with a new version of data. During a backup procedure, a cleanup process is paused, issuing new timestamps is paused, and a backup timestamp is generated, which results in an effective backup copy. During a restore of a backup, a snapshot of the database is loaded and any entries older than the backup timestamp are deleted, which ensures that a consistent restore has occurred.

Abstract: Systems, methods, and non-transitory computer readable media are provided for recursively searching a plurality of workspaces of the system for linked data associated with the seed data, initiating an endpoint process for each the seed data and the linked data, and, upon completion of the search, delete the seed data and the linked data identified based at least in part on the endpoint process. The process may be automatically repeated at a predetermined time interval to identify and remove future data that is stored in the plurality of datasets.

Abstract: A system for balancing query execution against ontology-based databases among multiple user accounts and related methods are disclosed. The system is programmed to receive database queries transformed from ontology queries from user accounts. The system is further programmed to manage execution of the database queries to enable fair utilization of computing resources among the user accounts, based on tracked usage of computing resources of each user account or estimated costs of pending database queries considering access controls associated with the ontology. Managing execution of the database queries comprises preempting a complex database query for another database query associated with a user account having a current top priority in query execution.

Abstract: A method comprises receiving a set of data source updates for one or more datasets from data sources; receiving one or more sets of user edits to an ontology; transforming the set of data source updates to a list of updates to the ontology based on a mapping between the one or more datasets and a plurality of ontology entity types; merging the list of updates with the one or more sets of user edits into a merged dataset; and resolving conflicts in the merged dataset by prioritizing a user edit over a data source update, comprising: determining that a current user edit to a first ontology entity of a first ontology entity type is to create the first ontology entity and no earlier user edit to the first ontology entity was to delete the first ontology entity; and disregarding any later data source update to the first ontology entity.

Abstract: A system for query execution planning over ontology-based databases and related methods are disclosed. The system is programmed to receive an ontology query from a user account against an ontology having access controls, and transform the ontology query into a set of database queries, including a plurality of joins. The system is programmed to compute the amounts of data processing associated with executing the plurality of joins in different orders on a sample of the databases representing the ontology, considering how much data in the ontology can be accessed by the user account under the access controls, and determine an execution plan corresponding to a preferred amount of data processing. Furthermore, the system is programmed to execute the set of database queries on the databases according to the execution plan, and transmit a reply to the ontology query to the user device based on a result of the execution.

Abstract: A system for efficient query execution over ontology-based databases and related methods are disclosed. The system is programmed to receive an ontology query from a user account against an ontology having access controls, and transform the ontology query into a set of database queries, including a set of exact aggregations or joins. The system is programmed to then estimate how much data processing is to be performed in executing the set of exact aggregations or joins, considering how much data in the ontology can be accessed by the user account under the access controls. Upon determining that the estimated amount of data processing exceeds a threshold, the system is programmed to route the set of exact aggregations or joins to a set of nodes optimized for large-scale data processing.

Abstract: A method comprises receiving a set of data source updates for datasets; transforming the set of data source updates to a list of updates to an ontology, the ontology including a definition for each ontology entity type that include one or more properties, obtaining a first transformation mapping columns of a first dataset to a first set of properties of a certain ontology entity type; obtaining a second transformation mapping columns of a second dataset to a second set of properties of the certain ontology entity type; obtaining a specific security policy that applies to the first set of properties based on a first set of permissions controlling access to rows of the first dataset; obtaining a particular security policy that applies to the second set of properties based on a second set of permissions controlling access to rows of the second dataset.

Abstract: In some examples, systems and methods for managing access control to one or more resources are provided. An example method includes receiving a permission request for a user to access the one or more resources, generating an access request based at least in part on the permission request, notifying one or more reviewers to review the access request, receiving an indication of the access request being approved, and automatically granting permission to the user to access the one or more resources.

Abstract: In some examples, systems and methods for managing task approvals are provided. An example method includes receiving a task identifier for a task that is requested to be approved, and one or more subtasks decomposed from the task, and generating a task request including a task request identifier. In some examples, the task request is associated with the task, the task request identifier corresponds to the task identifier, and each subtask of the one or more subtasks of the task corresponds to one or more approval policies. In some examples, the method further includes: determining, for each subtask of the one or more subtasks of the task, whether the one or more approval policies are satisfied, in response to determining that, for each subtask of the one or more subtasks of the task, the one or more approval policies are satisfied, approving the task, and outputting an indication of the approval.

Abstract: A system for providing a unified query interface across multiple ontology-based databases and related methods are disclosed. The system is programmed to receive calls to an application programming interface for querying an ontology, where ontology data is represented in different databases respectively in different forms. For each function being called, system is programmed to select a database from the different databases based on the function type and each ontology entity type being processed by the function. The system is further programmed to retrieve data from each selected database, merge the retrieval results as appropriate, and transform the final result to ontology data in response to the calls.

Abstract: A system for managing versioning of ontology data represented in multiple forms respectively in multiple databases and related methods are disclosed. The system is programmed to determine which changes to the ontology are to be incorporated into a new version of specific ontology data. In response to a write request to write a latest version of specific ontology data, the system is programmed to start representing the latest version in the multiple databases according to a first predetermined strategy. In response to a read request to read a latest version, the system is programmed to return a particular version from at least one of the multiple databases according to a second predetermined strategy.

Abstract: A distributed, transactional database uses timestamps, such as logical clock values, for entry versioning and transaction management in the database. To write to the database, a service requests a timestamp to be inserted into the database with a new version of data. During a backup procedure, a cleanup process is paused, issuing new timestamps is paused, and a backup timestamp is generated, which results in an effective backup copy. During a restore of a backup, a snapshot of the database is loaded and any entries older than the backup timestamp are deleted, which ensures that a consistent restore has occurred.

Abstract: Systems, methods, and non-transitory computer readable media are provided for recursively searching a plurality of workspaces of the system for linked data associated with the seed data, initiating an endpoint process for each the seed data and the linked data, and, upon completion of the search, delete the seed data and the linked data identified based at least in part on the endpoint process. The process may be automatically repeated at a predetermined time interval to identify and remove future data that is stored in the plurality of datasets.

Abstract: A system for resolving conflicts between data source updates and user edits to an ontology before applying the resulting changes to the ontology and related methods are disclosed. The system is programmed to receive data source updates from data sources and transform the data source updates to updates to ontology data. The system is also programmed to receive edits to ontology data from user accounts. The system is programmed to review these updates or edits to the ontology and resolve conflicts according to a predetermined strategy, such as prioritizing a user edit over a data source update. The resulting changes are incorporated to one or more databases where representations of the ontology data are stored.