Patent classifications
G06F16/211
Systems and Methods for Using Machine Learning Models to Automatically Identify and Compensate for Recurring Charges
Disclosed embodiments may include a method and system for automated incremental payments. The system may identify recurring charges from historical account data. Based on the recurring charges and an incremental period, the system may calculate an incremental amount and expected amount. At each iteration of the incremental period, the incremental amount may be assigned to a savings bucket. The value of the savings bucket may be subtracted from an actual account balance to calculate a reduced account balance. The system may generate and transmit a graphical user interface to a user device showing the reduced account balance. The system may receive current data containing a charge that corresponds to the recurring charges. The system may reduce the value of the savings bucket by the amount of the current data charge. If the current data charge is different from the expected amount, the system may adjust the incremental amount accordingly.
RELATIONSHIP BUILDER TO RELATE DATA ACROSS MULTIPLE ENTITIES/NODES
A method for implementing a relationship builder to relate data across multiple entities of a database system, comprising the steps of: providing a set of data sets across multiple entities in the database system, wherein an entity comprises a set of structured data or a set of semi-structured data; identifying a set of relationships across the set of datasets without any prior schema knowledge of the set of data sets; testing and discarding relationships et of relationships across the set of datasets that are detected as a negative; referring a set of remaining relationships which have not been discarded as a set of tested possible relationships; validating the set of tested possible relationships by applying an initial filtering algorithms to remove any false positives comprising a distilled relation; and determining a set of tested possible relationships as comprising a set of true relationships applying a set of graph algorithms.
Building data platform with a distributed digital twin
A method including receiving, by one or more processing circuits, building data, generating, by the one or more processing circuits, a first digital twin based on the building data, wherein a first system stores the first digital twin and a second system stores a second digital twin generated based on the building data, where the first digital twin includes a relationship that forms a connection between the first digital twin and the second digital twin by linking a first entity of the first entities of the first digital twin and a second entity of the second entities of the second digital twin, and performing, by the one or more processing circuits, one or more operations based on at least one of the first digital twin, the second digital twin, or the relationship that forms the connection between the first digital twin and the second digital twin.
GENERATING USER INTERFACE ELEMENTS BASED ON DATA SCHEMA FILES
Methods and systems for improved generation of user interfaces based on data schemas are provided. In one embodiment, a method is provided that includes receiving a data schema file and identifying a data schema within the data schema file. The data schema file may identify valid data for a computing service, such as an API. The data schema may be provided to a validation service, which may test whether a plurality of sentinel values comply with the data schema. An error message may be received from the validation service and a user interface element may be selected based on the error message. The user interface element may be added to the user interface.
SCHEMA VALIDATION WITH SUPPORT FOR ORDERING
Computer-readable media, methods, and systems are disclosed for validating data associated with schemas. A user defines the object model of at least one asset and a first schema is generated in accordance with the defined object model, and a unique fingerprint is generated. Data is collected from one or more devices in accordance with the object model. The collected data is serialized, and a second schema is generated. The second schema is ordered in accordance with the first schema and a unique fingerprint is generated. The fingerprint of the first schema is compared to the fingerprint of the second schema to provide an efficient review process for determining whether the schemas are equal, and the associated data may be validated. A fingerprint cache may be updated with fingerprints associated with a plurality of schemas, as well as version history of each schema, to provide an efficient review process.
Putative ontology generating method and apparatus
Apparatus for generating a putative ontology from a data structure associated with a data store, the apparatus including an electronic processing device that generates a putative ontology by determining at least one concept table in the data structure, determining at least one validated attribute within the at least one concept table, determining at least one selected attribute value from the at least one validated attribute and generating at least one ontology class using the at least one attribute value.
Systems and methods for multi-file check-in
A content management system provides a mechanism for multi-file check-in features useful for content management. The content management system provides a way for users to check in multiple files in a single action. The system allows users to either select assets (e.g., files) or drag and drop multiple assets to be checked in. The assets being checked in are automatically matched with checked out assets, and once matched, unlocked.
METHODS AND SYSTEMS FOR STORING DATA IN A DATABASE
A method comprising, by a processor and memory circuitry, obtaining a plurality of data comprising one or more groups of data, obtaining a data structure usable to determine, for at least a first data type and a second data type, a given data type which is adapted to represent at least both data of the first and second data types for their storage, for at least one given group of data which comprises one or more subsets of data S.sub.1 to S.sub.N: for each subset of data S.sub.1 to S.sub.N, determining a data type which is adapted to represent said subset of data for its storage, and using the given data type of each subset of data S.sub.1 to S.sub.N and the data structure to determine a common data type which is adapted to represent data belonging to subsets of data S.sub.1 to S.sub.N for their storage.
SYSTEM EVENT ANALYSIS AND DATA MANAGEMENT
Techniques are provided for analyzing events incoming through a message broker and configuring a database schema for storing the events based on the analysis. The analysis is performed on all the attributes of the incoming events with reference to a primary identifier of an event source. The analysis determines the characteristics of the attributes, which facilitates development of the database schema with availability, accuracy, existence, and other factors of various attributes. Analysis is supported for various formats of events, such as AVRO, XML, complex JSON, etc. In some examples, the attributes of interest for database schema generation can be provided via a configuration for the respective databases including relational, time-series, analytical, graph, etc. Also, if a given database supports direct ingestion of data through the message broker, then the ingestion specification can be generated.
In-memory database for multi-tenancy
An in-memory database server hosting a tenant of a multi-tenant software architecture can receive a definition of a custom data field that is unique to an organization having isolated access to the tenant. The custom data field can extend a standard table defined by central metadata stored at a system tenant of the multi-tenant software architecture. Tenant private metadata that includes the definition can be stored in memory accessible only to the tenant. A tenant-dependent table that includes the custom data field can be formed, for example by retrieving central metadata defining the standard table from the system tenant and adding the custom data field using the definition. The tenant-dependent table can be presented for access via a database client at the organization. Related systems, articles of manufacture, and computer-implemented methods are disclosed.