Managing data objects for graph-based data structures
Various embodiments provide methods, systems, apparatus, computer program products, and/or the like for managing, ingesting, monitoring, updating, and/or extracting/retrieving information/data associated with an electronic record (ER) stored in an ER data store and/or accessing information/data from the ER data store.
1. A computer-implemented method performed by one or more computing devices, the computer-implemented method comprising:
receiving, by one or more processors of the one or more computing devices via one or more communications interfaces of the one or more computing devices, a plurality of messages; and
responsive to at least one of (a) an incoming message volume satisfying an incoming message volume threshold or (b) a resource availability satisfying a resource availability threshold, dynamically changing, by the one or more processors, a form of data processing used by the one or more computing devices from real-time data processing or near real-time data processing to deferred data processing, wherein the deferred data processing comprises:
(i) storing, by the one or more processors, a plurality of respective data objects generated for the plurality of messages in a first data store for the deferred data processing, wherein each data object is identifiable by an entity identifier and is deferred for processing until a user interaction event associated with the entity identifier is detected,
(ii) detecting, by the one or more processors, a user interaction event,
(iii) responsive to detecting the user interaction event, receiving, by the one or more processors, the plurality of respective data objects from the first data store,
(iv) initiating, by the one or more processors, the deferred data processing for the plurality of respective data objects, and
(v) storing, by the one or more processors, data from the plurality of respective data objects in a second data store and in association with the entity identifier.
2. The computer-implemented method of claim 1 , wherein (a) the user interaction event authenticates a user via an interface through which the user has access to data stored in association with a user profile corresponding to the entity identifier and (b) the user is an owner corresponding to the entity identifier.
3. The computer-implemented method of claim 1 , wherein (a) the user interaction event authenticates a user via an interface through which the user has access to data stored in association with a user profile corresponding to the entity identifier and (b) the user has a relationship defined within a graph-based domain ontology with an entity that is an owner corresponding to the entity identifier.
4. The computer-implemented method of claim 3 , wherein detecting the user interaction event comprises:
determining that the user has been authenticated via the interface;
identifying one or more relationships in which the user is a participant based at least in part on the entity identifier corresponding to the user; and
determining, based at least in part on the one or more relationships, that the user has access to data corresponding to the entity identifier.
5. The computer-implemented method of claim 4 , wherein the one or more relationships are identified based at least in part on a graph data structure of the graph-based domain ontology.
6. The computer-implemented method of claim 1 , wherein the user interaction event is detected based at least in part on historical behavior of one or more users having access to data corresponding to the entity identifier.
7. The computer-implemented method of claim 1 , further comprising, responsive to at least one of (a) the incoming message volume no longer satisfying the incoming message volume threshold or (b) the resource availability no longer satisfying the resource availability threshold, dynamically changing the form of data processing used by the one or more computing devices from deferred data processing to real-time data processing or near real-time data processing.
8. A system comprising memory and one or more processors, the one or more processors configured to:
receive, by one or more communication interfaces of the system, a plurality of messages; and
responsive to at least one of (a) an incoming message volume satisfying an incoming message volume threshold or (b) a resource availability satisfying a resource availability threshold, dynamically change a form of data processing used by the system from real-time data processing or near real-time data processing to deferred data processing, wherein the deferred data processing comprises:
(i) store a plurality of respective data objects generated for the plurality of messages in a first data store for the deferred data processing, wherein each data object is identifiable by an entity identifier and is deferred for processing until a user interaction event associated with the entity identifier is detected,
(ii) detect a user interaction event,
(iii) responsive to detecting the user interaction event, receive the plurality of respective data objects from the first data store, and
(iv) store data from the plurality of respective data objects in a second data store and in association with the entity identifier.
9. The system of claim 8 , wherein (a) the user interaction event authenticates a user via an interface through which the user has access to data stored in association with a user profile corresponding to the entity identifier and (b) the user is an owner corresponding to the entity identifier.
10. The system of claim 8 , wherein (a) the user interaction event authenticates a user via an interface through which the user has access to data stored in association with a user profile corresponding to the entity identifier and (b) the user has a relationship defined within a graph-based domain ontology with an entity that is an owner corresponding to the entity identifier.
11. The system of claim 10 , wherein detecting the user interaction event comprises:
determining that the user has been authenticated via the interface;
identifying one or more relationships in which the user is a participant based at least in part on the entity identifier corresponding to the user; and
determining, based at least in part on the one or more relationships, that the user has access to data corresponding to the entity identifier.
12. The system of claim 11 , wherein the one or more relationships are identified based at least in part on a graph data structure of the graph-based domain ontology.
13. The system of claim 8 , wherein the user interaction event is detected based at least in part on historical behavior of one or more users having access to data corresponding to the entity identifier.
14. The system of claim 8 , wherein the one or more processors are further configured to, responsive to at least one of (a) the incoming message volume no longer satisfying the incoming message volume threshold or (b) the resource availability no longer satisfying the resource availability threshold, dynamically changing the form of data processing used by the system from deferred data processing to real-time data processing or near real-time data processing.
15. One or more non-transitory computer-readable storage media including instructions that, when executed by one or more processors, cause the one or more processors to:
receive, by one or more communications interfaces of one or more computing devices, a plurality of messages; and
responsive to at least one of (a) an incoming message volume satisfying an incoming message volume threshold or (b) a resource availability satisfying a resource availability threshold, dynamically change a form of data processing used by the one or more computing devices from real-time data processing or near real-time data processing to deferred data processing, wherein the deferred data processing comprises:
(i) store a plurality of respective data objects generated for the plurality of messages in a first data store for the deferred data processing, wherein each data object is identifiable by an entity identifier and is deferred for processing until a user interaction event associated with the entity identifier is detected,
(ii) detect a user interaction event,
(iii) responsive to detecting the user interaction event, receive the plurality of respective data objects from the first data store, and
(iv) store data from the plurality of respective data objects in a second data store and in association with the entity identifier.
16. The one or more non-transitory computer-readable storage media of claim 15 , wherein (a) the user interaction event authenticates a user via an interface through which the user has access to data stored in association with a user profile corresponding to the entity identifier and (b) the user is an owner corresponding to the entity identifier.
17. The one or more non-transitory computer-readable storage media of claim 15 , wherein (a) the user interaction event authenticates a user via an interface through which the user has access to data stored in association with a user profile corresponding to the entity identifier and (b) the user has a relationship defined within a graph-based domain ontology with an entity that is an owner corresponding to the entity identifier.
18. The one or more non-transitory computer-readable storage media of claim 17 , wherein detecting the user interaction event comprises:
determining that the user has been authenticated via the interface;
identifying one or more relationships in which the user is a participant based at least in part on the entity identifier corresponding to the user; and
determining, based at least in part on the one or more relationships, that the user has access to data corresponding to the entity identifier.
19. The one or more non-transitory computer-readable storage media of claim 15 , wherein the user interaction event is detected based at least in part on historical behavior of one or more users having access to data corresponding to the entity identifier.
20. The one or more non-transitory computer-readable storage media of claim 15 , wherein the one or more processors are further configured to, responsive to at least one of (a) the incoming message volume no longer satisfying the incoming message volume threshold or (b) the resource availability no longer satisfying the resource availability threshold, dynamically changing the form of data processing used by the one or more computing devices from deferred data processing to real-time data processing or near real-time data processing.