Methods and systems for connecting data with non-standardized schemas in connected graph data exchanges

1. A system for connecting data with non-standardized schemas in connected graph data exchanges, comprising:

cloud-based memory configured to:

store a first data structure for user profile data, wherein the first data structure comprises a first attribute for a connected graph data exchange database, and wherein the first data structure corresponds to a first node in the connected graph data exchange database, wherein the connected graph data exchange database relates data items in a data store to a collection of nodes and edges, wherein nodes, in the collection of nodes, represent data items in the data store, and wherein the edges represent relationships between the nodes; and

store a second data structure for a standardized data structure, wherein the second data structure comprises a second attribute for a standardized data structure;

cloud-based control circuitry configured to:

receive a first user request to generate a custom data structure for the user profile data, wherein the custom data structure comprises relationships between attributes of the user profile data and data exchange assets in the connected graph data exchange database, and wherein the custom data structure comprises a plurality of fields;

retrieve the first data structure for the user profile data;

retrieve the second data structure for the standardized data structure;

determine that the first attribute and the second attribute correspond;

generate reference data that maps the first attribute to the second attribute in response to determining that the first attribute and the second attribute correspond, wherein the reference data represents an edge in the connected graph data exchange database connecting a third node corresponding to the first attribute and a fourth node corresponding to the second attribute;

generate a custom attribute for including in the custom data structure based on the reference data; and

populate the custom data structure with the custom attribute, wherein the custom attribute represents a value of a field of the plurality of fields;

receive a second user request to update the second data structure; and

update the reference data in response to receiving the second user request; and

cloud-based input/output circuitry configured to:

generate for display, on a user interface, a notification based on updating the reference data.

2. A method for connecting data with non-standardized schemas in connected graph data exchanges, comprising:

receiving, via a user interface, a first user request to generate a custom data structure for user profile data, wherein the custom data structure comprises relationships between attributes of the user profile data and data exchange assets in a connected graph data exchange database, wherein the connected graph data exchange database relates data items in a data store to a collection of nodes and edges, wherein nodes, in the collection of nodes, represent data items in the data store, and wherein the edges represent relationships between the nodes;

retrieving a first data structure for the user profile data, wherein the first data structure comprises a first attribute for the connected graph data exchange database, and wherein the first data structure corresponds to a first node in the connected graph data exchange database;

retrieving a second data structure for a standardized data structure, wherein the second data structure comprises a second attribute for the connected graph data exchange database, and wherein the second data structure corresponds to a second node in the connected graph data exchange database;

determining that the first attribute and the second attribute correspond;

in response to determining that the first attribute and the second attribute correspond, generating reference data that maps the first attribute to the second attribute;

generating a custom attribute for including in the custom data structure based on the reference data;

populating the custom data structure with the custom attribute;

receiving, via the user interface, a second user request to update the second data structure in response to receiving the second user request, updating the reference data; and

generating for display, on a user interface, a notification based on updating the reference data.

3. The method of claim 2 , wherein the first attribute describes a first type of user identifier, and wherein the second attribute describes a second type of user identifier, and wherein the reference data maps the first type of user identifier to the second type of user identifier.

4. The method of claim 2 , wherein the first attribute describes a first type of user setting, and wherein the second attribute describes a second type of user setting, and wherein the reference data maps the first type of user setting to the second type of user setting.

5. The method of claim 2 , further comprising:

receiving, via the user interface, a third user request to update the user profile data; and

in response to receiving the second user request, retrieving the custom data structure.

6. The method of claim 2 , further comprising:

in response to receiving the first user request to generate the custom data structure, determining that the custom data structure comprises the first data structure and the second data structure; and

in response to determining that the custom data structure comprises the first data structure and the second data structure, accessing:

a first remote issue link to a first server housing the first data structure; and

a second remote issue link to a second server housing the first data structure.

7. The method of claim 2 , wherein generating the reference data further comprises:

determining the first attribute;

determining the second attribute; and

determining a rule set for automatically mapping the first attribute to the second attribute.

8. The method of claim 2 , further comprising:

retrieving first content from the first attribute;

retrieving second content from the second attribute;

determining a semantic closeness between the first content and the second content;

comparing the semantic closeness to a threshold semantic closeness;

determining that the first content and the second content correspond based on the semantic closeness equaling or exceeding the threshold semantic closeness; and

determining that the first attribute and the second attribute correspond based on the semantic closeness equaling or exceeding the threshold semantic closeness.

9. The method of claim 2 , further comprising:

retrieving first content from the first attribute;

determining a keyword in the first content;

comparing the keyword to a list of keywords corresponding to the second attribute; and

determining that the first attribute and the second attribute correspond based on comparing the keyword to the list of keywords corresponding to the second attribute.

10. The method of claim 2 , further comprising:

receiving a user edit to the reference data; and

storing the edited reference data in the custom data structure.

11. A non-transitory, computer-readable medium comprising instructions that, when executed by one or more processors, cause operations comprising:

receiving, via a user interface, a first user request to generate a custom data structure for user profile data, wherein the custom data structure comprises relationships between attributes of the user profile data and data exchange assets in a connected graph data exchange database, wherein the connected graph data exchange database relates data items in a data store to a collection of nodes and edges, wherein nodes, in the collection of nodes, represent data items in the data store, and wherein the edges represent relationships between the nodes;

retrieving a first data structure for the user profile data, wherein the first data structure comprises a first attribute for the connected graph data exchange database, and wherein the first data structure corresponds to a first node in the connected graph data exchange database;

retrieving a second data structure for a standardized data structure, wherein the second data structure comprises a second attribute for the connected graph data exchange database, and wherein the second data structure corresponds to a second node in the connected graph data exchange database;

determining that the first attribute and the second attribute correspond;

in response to determining that the first attribute and the second attribute correspond, generating reference data that maps the first attribute to the second attribute;

generating a custom attribute for including in the custom data structure based on the reference data;

populating the custom data structure with the custom attribute;

receiving, via the user interface, a second user request to update the second data structure in response to receiving the second user request, updating the reference data; and

generating for display, on a user interface, a notification based on updating the reference data.

12. The non-transitory, computer-readable medium of claim 11 , wherein the first attribute describes a first type of user identifier, and wherein the second attribute describes a second type of user identifier, and wherein the reference data maps the first type of user identifier to the second type of user identifier.

13. The non-transitory, computer-readable medium of claim 11 , wherein the instructions further cause operations comprising:

receiving, via the user interface, a third user request to update the user profile data; and

in response to receiving the second user request, retrieving the custom data structure.

14. The non-transitory, computer-readable medium of claim 11 , wherein the instructions further cause operations comprising:

in response to receiving the first user request to generate the custom data structure, determining that the custom data structure comprises the first data structure and the second data structure; and

in response to determining that the custom data structure comprises the first data structure and the second data structure, accessing:

a first remote issue link to a first server housing the first data structure; and

a second remote issue link to a second server housing the first data structure.

15. The non-transitory, computer-readable medium of claim 11 , wherein generating the reference data further comprises:

determining the first attribute;

determining the second attribute; and

determining a rule set for automatically mapping the first attribute to the second attribute.

16. The non-transitory, computer-readable medium of claim 11 , wherein the instructions further cause operations comprising:

retrieving first content from the first attribute;

retrieving second content from the second attribute;

determining a semantic closeness between the first content and the second content;

comparing the semantic closeness to a threshold semantic closeness;

determining that the first content and the second content correspond based on the semantic closeness equaling or exceeding the threshold semantic closeness; and

determining that the first attribute and the second attribute correspond based on the semantic closeness equaling or exceeding the threshold semantic closeness.

17. The non-transitory, computer-readable medium of claim 11 , wherein the instructions further cause operations comprising:

retrieving first content from the first attribute;

determining a keyword in the first content;

comparing the keyword to a list of keywords corresponding to the second attribute; and

determining that the first attribute and the second attribute correspond based on comparing the keyword to the list of keywords corresponding to the second attribute.

18. The non-transitory, computer-readable medium of claim 11 , wherein the instructions further cause operations comprising:

receiving a user edit to the reference data; and

storing the edited reference data in the custom data structure.