A method of processing a query to a database from a query source is provided, comprising: receiving the query, the query in a first format supported by the query source; inputting the query into a first neural network; outputting, by the first neural network, the query in a second format, wherein the second format is a format supported by the database; receiving, from the database, a response to the query, the response in the second format; inputting the response to the query into a second neural network; outputting, by the second neural network, the response to the query in the first format; wherein each neural network is trained by inputting a first plurality of pairs of semi-structured data, each pair of semi-structured data comprising a sample query or response in the first format and the sample query or response in the second format.

A system and related method for change management at login. The method includes constructing an administratively prescribed target data store as a function of received administrative input prescribing a target feature and target feature-state, and related messages to push to a user upon occurrences of target feature mismatches and matches. Login information, including a username identifier, service provider identifier, and current use time-stamp are received for a user. A historical data store is queried to obtain a user status that associates the username identifier and the service provider identifier with a previously used feature, feature-state and a previous use time-stamp. The target data store is queried for the service provider. Determinations are made as to whether previous feature use matches target feature use. Messages are displayed responsive thereto.

Computer implemented methods for storing ad hoc relations between previously unrelated database objects assigned to different database structures using an electronic computing device are presented, the methods including: causing the electronic computing device to define at least three database structures: structure A, structure B and structure C, where each of the at least three database structures each includes a number of objects, where there exists at least one relation between objects of structure A and objects of structure B, and where there exists at least one relation between objects of structure B and objects of structure C; filtering data of structure A; accessing structure B using a first selected relation between structure A and structure B; storing information about filtering of structure A and information on a first selected path between structure A and structure B; filtering results obtained from structure B.

A system and related method for change management at login. The method includes constructing an administratively prescribed target data store as a function of received administrative input prescribing a target feature and target feature-state, and related messages to push to a user upon occurrences of target feature mismatches and matches. Login information, including a username identifier, service provider identifier, and current use time-stamp are received for a user. A historical data store is queried to obtain a user status that associates the username identifier and the service provider identifier with a previously used feature, feature-state and a previous use time-stamp. The target data store is queried for the service provider. Determinations are made as to whether previous feature use matches target feature use. Messages are displayed responsive thereto.

The invention is a system for integrating data sets organized in one organization type with data sets organized in a second organization type so that data queries submitted to be processed in the manner of the first organization type can be translated into queries usable by the data set in the second data organization type and the results returned to satisfy the first query.

Well operation information arranged in the extensible markup language format may be converted into a cloud-native format. The converted information may be provided to a cloud-native application to facilitate operation of the well.

Systems, devices, methods, and interfaces generally for use with database management systems (DBMSs) and DBMS interfaces (i.e. user interfaces, input interfaces, search interfaces, operating interfaces, etc.). In some aspects, the systems, devices, methods, and interfaces include using artificial intelligence (i.e. machine learning and/or anticipation functionalities, etc.) to learn a user's use of a DBMS or DBMS interface, store this “knowledge” in a knowledgebase, and anticipate the user's future operating intentions. In other aspects, the systems, devices, methods, and interfaces include disassembling user or other input into various types of portions (i.e. text, numbers, etc.) and determining one or more instructions for performing operations on a DBMS or DBMS interface based on the various types of portions. In further aspects, the systems, devices, methods, and interfaces include associative DBMS command construction. Other systems, devices, methods, interfaces, and features are also disclosed.

Systems and methods for sharing information between distributed computer systems connected to one or more data networks. In particular, a replication system implements methodologies for sharing database information between computer systems where the databases use different classification schemes for information access control.

Systems and methods for sharing information between distributed computer systems connected to one or more data networks. In particular, a replication system implements methodologies for sharing database information between computer systems where the databases use different classification schemes for information access control.

In various embodiments, a process for dynamic endpoint generation includes using a stored endpoint definition expressed in a declarative language to dynamically generate an endpoint comprising a representational state transfer (REST) interface. The process includes providing access to a locally-stored database via the endpoint and REST interface.