Platform-agnostic data storage and retrieval in a multiplatform computing environment
View Patent ↗A data storage system instantiates a graph data structure to store platform-agnostic atomic data units of organization-owned content in a multiplatform computing environment. Each atomic data unit can be accessed by any platform in the multiplatform computing environment and may be included in or referenced by any document, object, or other platform-specific data structure.
1 . A method for storing platform-agnostic data and constructing platform-specific documents in a multi-platform computing environment, the method comprising:
receiving a request to display a platform-specific document object in a frontend of a respective documentation tool of the multi-platform computing environment, the platform-specific document object identified by an identifier;
in response to the request, querying a platform-specific datastore with the identifier to retrieve a set of atomic data units that define content of the platform-specific document object, the atomic data units accessible to both of the documentation tool of the multi-platform computing environment and an issue tracking tool of the multi-platform computing environment, wherein at least one atomic data unit of the set of atomic data units defines content of a platform-specific issue tracking data of the issue tracking tool;
querying a platform-agnostic graph data store to retrieve each atomic data unit defining the platform-specific document and at least one transformation node associated with the platform-specific document object;
constructing, for the documentation tool of the multi-platform computing environment, the platform-specific document object from the retrieved atomic data units, the construction comprising an execution of the at least one transformation node with respect to at least one atomic data unit of the set of atomic data units; and
causing the platform-specific document object to be rendered as a graphical user interface element in the frontend of the documentation tool of the multi-platform computing environment.
2 . The method of claim 1 , wherein constructing the platform-specific document comprises performing a transform defined by the transformation node to a data attribute of a respective first atomic data unit of the retrieved atomic data units.
3 . The method of claim 2 , wherein the transform comprises formatting or modifying text content of the respective first atomic data unit.
4 . The method of claim 2 , wherein the transform comprises modifying media content of the respective first atomic data unit.
5 . The method of claim 2 , wherein the transform comprises pivoting tabular data content of the respective first atomic data unit.
6 . The method of claim 2 , wherein the transform comprises filtering tabular data content of the respective first atomic data unit.
7 . The method of claim 2 , wherein the transform comprises extracting, calculating, or generating a metadata value from data content of the respective first atomic data unit.
8 . The method of claim 2 , wherein the transform comprises generating a visual representation of tabular data content of the respective first atomic data unit.
9 . The method of claim 1 , wherein querying the platform-agnostic graph data store includes, in response to the query, authenticating a permission to access at least one of the atomic data unit nodes associated with the platform-specific document.
10 . The method of claim 1 , wherein retrieving each atomic data unit node includes traversing the platform-agnostic graph data store to retrieve one or more interconnected atomic data units associated with each atomic data unit.
11 . A data management system for storing and retrieving platform-agnostic data in a multi-platform computing environment, the data management system comprising:
a platform-agnostic object store of a host service that includes one or more servers;
a processor allocation to instantiate an instance of a documentation tool controller on the one or more servers of the host service, the documentation tool controller configured to:
receive a platform-specific object request from a frontend providing client-side functionality of the documentation tool;
query a platform-specific data store for a platform-specific object map corresponding to a platform-specific object indicated by the platform-specific object request;
receive the platform-specific object map identifying, by reference:
a set of atomic data units that define content of the platform-specific object, each atomic data unit node of the set of atomic data units stored in the platform-agnostic object store, the set of atomic data units object accessible to both of the documentation tool controller of the multi-platform computing environment and a issue tracking tool controller of the multi-platform computing environment, wherein at least one atomic data unit of the set of atomic data units defines content of a platform-specific issue tracking data of the issue tracking tool;
retrieve the set of atomic data units from the platform-agnostic object store and at least one transformation node associated with the platform-specific object;
constructing a platform-specific object from the retrieved set of atomic data units, the construction comprising an execution of the at least one transformation node with respect to at least one atomic data unit of the set of atomic data units; and
cause display, within a graphical user interface of the frontend, of the platform-specific object.
12 . The data management system of claim 11 , wherein the platform-specific object map identifies, by reference, an object type of the platform-specific object.
13 . The data management system of claim 11 , wherein the at least one transformation node, when executed:
modifies text content of the at least one atomic data unit;
formats data content of the at least one atomic data unit;
filters tabular data content of the at least one atomic data unit; or
generates a visualization of tabular data content of the at least one atomic data unit.
14 . The data management system of claim 13 , wherein the at least one transformation node is executed by the documentation tool controller.
15 . The data management system of claim 13 , wherein the at least one transformation node is executed by the frontend.
16 . The data management system of claim 13 , wherein a first stage of the at least one transformation node is executed by the documentation tool controller and a second stage of the at least one transformation node is executed by the frontend.
17 . The data management system of claim 11 , wherein the processor allocation to instantiate the instance of the documentation tool controller is further configured to:
in response to the request, authenticate a permission to access at least one of the atomic data unit nodes associated with the platform-specific object.
18 . The data management system of claim 11 , wherein the processor allocation to instantiate the instance of the documentation tool controller is further configured to:
traverse a platform-agnostic graph data store to retrieve one or more interconnected atomic data units associated with each atomic data unit.