Patent classifications
G06F16/2291
AUTOMATED INQUIRY ANALYSIS
An inquiry analysis system and method are disclosed. An inquiry analysis system includes a computer configured to receive an electronic communication from a user, the electronic communication comprising an inquiry associated with an article of interest. The inquiry analysis system determines one or more measures including a first result of a first trained model based on one or more content elements of the inquiry, a second result of a second trained model based on one or more sentiment elements of the inquiry, and a valuation divergence model result based on a comparison of the inquiry with a reference value associated with the article of interest. The inquiry analysis system calculates and outputs a composite interest prediction which predicts a level of interest of the user associated with the respective article of interest.
METHOD AND APPARATUS FOR ACTIVE LEARNING BASED CALL CATEGORIZATION
A method and apparatus for active learning based call categorization include a method for categorizing a call automatically. The method includes generating a plurality of first scores corresponding to a plurality of first parameter candidates and a plurality of second scores corresponding to a plurality of second parameter candidates, based on at least one of a transcript of a call between a customer and an agent, or a CRM data associated with the call. The method further includes determining at least one first parameter from the plurality of first parameter candidates based on the plurality of first scores, and determining at least one second parameter from the plurality of second parameter candidates based on the plurality of second scores.
TRACKING OBJECT DEPENDENCY INFORMATION IN A CLOUD SYSTEM
Aspects of the present disclosure address systems, methods, and devices for tracking object dependencies in a cloud database system. An object dependency created between a referencing object and a referenced object is detected. Based on detecting the object dependency, a dependency record is generated. The dependency record includes dependency information describing the object dependency between the reference object and the referenced object. The dependency record is stored in a database of dependency records.
Single table multi-schema data store in a key value store
A system of creating a multi-schema data store of a key-value store may include a computing device. The system may receive a query to search for data from the multi-schema data store, wherein a first portion of the data corresponds to a first schema and a second portion of the data corresponds to one or more other schemas, the first and second portions of the data being stored in the multi-schema data store in interleaved format, wherein the query comprises a unique identifier associated with the data. The system may parse one or more entries of the multi-schema data store in a sequential order until a first entry is found that corresponds to the unique identifier, without assuming a hierarchy between schemas in the multi-schema data store. The system may compare the query to one or more proximate entries of the multi-schema data store.
USING DYNAMIC DATA STRUCTURES FOR STORING DATA OBJECTS
A technique for dynamic data structure usage for storing data objects is described. In one example of the present disclosure, a system can receive a data object and properties associated with the data object. The system can determine, based on at least one of the properties and pre-defined rules for data objects and corresponding object types, an object type of the data object and a first data structure for storing the data object that is different from a second data structure currently storing data objects in the memory. The system can output a command for causing the first data structure to store the data object in the memory.
Systems and methods for providing custom objects for a multi-tenant platform with microservices architecture
A multi-tenant system, comprises a main storage system including: a monolithic database storing global records associated with global objects, each global object including global fields common for all tenants; a monolithic application configured to process a particular global record storage request by instructing the monolithic database to store particular global field values of the particular global record for a particular tenant, and to process a particular global record fetch request by instructing the monolithic database to retrieve the one or more particular global field values; a custom object storage system including: a custom object database configured to store custom records associated with one or more custom objects, each custom object including one or more custom fields for a tenant; a custom object record service configured to process a particular custom record storage request by instructing the custom object database to store one or more particular custom field values for the tenant, and to process a particular custom record fetch request by instructing the custom object database to retrieve the one or more particular custom field values; and a query engine configured to receive a query, fetch relevant global records from the monolithic database, fetch relevant custom records from the custom object database, and generate a query response.
AUTOMATICALLY GENERATING EVENTS
Disclosed herein are system, method, and computer program product embodiments for automatically generating events. In some embodiments, a server receives a request to subscribe to an event type for an application. The server identifies an entity in a data model corresponding to the event type. The entity is associated with application data of the application. Furthermore, the server subscribes to receive alerts associated with any change to the entity in the data model. The server receives an alert indicating a change to the entity in the data model. The alert includes the change to the entity. Moreover, the server generates an event corresponding to the event type based on the change to the entity and transmits the event to an event infrastructure.
User augmented indexing and ranking of data
The application relates to a method for creating a user-augmented index, including: receiving information identifying data, a first user-created category and a first user-designated value from the first user. The data, the first user-created category, and the first user-designated value are associated together in a data entry in the user-augmented index. A second user-created category and a second user-designated value are received from the second user. The second user-created category and the second user-designated value are also associated with the data entry in the user-augmented index. The application further relates to ranking one or more related data entries in response to a query of a user-augmented index.
FILE ANALYTICS SYSTEMS AND METHODS INCLUDING RECEIVING AND PROCESSING FILE SYSTEM EVENT DATA IN ORDER
Examples of file analytics systems are described that may obtain event data from a virtualized file server. The event data may be aggregated and/or filtered to provide metrics. The file analytics system may obtain event data from the virtualized file server. The file analytics system may process multiple streams of event data in parallel by separating messages corresponding to the event data message topic into multiple partition pipelines. To avoid processing events related to a particular file out of chronological order, the analytics tool may distribute events for the particular file to the same message topic partition pipeline.
Electronic note management via a connected entity graph
Electronic note management via a connected entity graph. In one embodiment, for example, a method for searching for electronic notes via a connected entity graph comprises the steps of: receiving selection of a beginning entity; receiving selection of a linking parameter; receiving selection of a target entity type; searching a connected entity graph, comprising at least one electronic note entity, starting at the beginning entity, for any target entities, of the target entity type, and within a predetermined search depth, that have a first degree connection in the connected entity graph with the beginning entity that satisfies the linking parameter or that have a first degree connection with one of the other target entities that satisfies the linking parameter; and displaying in a graphical user interface a search result comprising nodes and edges, each of the nodes representing the beginning entity or one of the target entities and each of the edges connecting two of the nodes and representing a first degree connection in the connected entity graph between the two entities represented by the two nodes connected by the edge.