# US 12,007,959 B2 · Apparatuses, methods, and computer-program products for generating and updating object types across multiple schemas > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,007,959 B2 - Document ID: US12007959B2 - Status: Granted - Kind: B2 - Application number: 17/657,491 - Filed: 2022-03-31 - Published: 2023-10-05 - Granted: 2024-06-11 - Earliest claimed: 2022-03-31 - Assignees: Atlassian Pty Ltd.; Atlassian US, Inc. - Applicants: Atlassian Pty Ltd.; Atlassian US, Inc. - Inventors: Jeremey Llewellyn Barrett; Ola Melin; Michael Johannes Ruflin - Web page: https://patentgrep.com/patent/US12007959B2 ## CPC - G06F 16/211: {Schema design and management} - G06F 16/289: {Object oriented databases} - G06F 16/219: {Managing data history or versioning (querying versioned data G06F16/2474; querying temporal data G06F16/2477)} - G06F 16/2264: {Multidimensional index structures} - G06F 16/9024: {Graphs; Linked lists (G06F16/9027 takes precedence)} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract Various embodiments of the present disclosure provide for generating, updating, and/or otherwise managing an assent management system and its associated objects. An example embodiment is configured for accessing an asset management repository comprising a plurality of object type identifier nodes and a plurality of object attribute identifier nodes configured in a directed graph structure; receiving an object query comprising a selected object type identifier; traversing the directed graph structure to return a selected object type schema comprising an object attribute identifier node subset associated with the selected object type identifier; and outputting a selected object type interface component based on the selected object type schema for rendering to the object types registry interface. ## Claims ### Claim 1 An apparatus configured to manage an object types registry interface of an asset management system, the apparatus comprising at least one processor and at least one memory, the at least one memory having computer-coded instructions therein, wherein the computer-coded instructions are configured to, in execution with the at least one processor, cause the apparatus to: access an asset management repository comprising a plurality of object type identifier nodes and a plurality of object attribute identifier nodes configured in a directed graph structure; receive an object query comprising a selected object type identifier; traverse the directed graph structure to return a selected object type schema comprising an object attribute identifier node subset associated with the selected object type identifier; and output a selected object type interface component based on the selected object type schema for rendering to an object types registry interface. ### Claim 2 (depends on 1) The apparatus of claim 1, the computer-coded instructions are further configured to cause the apparatus to: receive a second attribute creation request, the second attribute creation request comprising a second plurality of object attribute identifier nodes in association with the plurality of object type identifier nodes to be configured in the directed graph structure. ### Claim 3 (depends on 2) The apparatus of claim 2, wherein the second plurality of object attribute identifier nodes comprises at least a second object attribute identifier node configured to generate a second object type schema with an object type identifier node of the plurality of object type identifier nodes. ### Claim 4 (depends on 3) The apparatus of claim 3, the computer-coded instructions are further configured to cause the apparatus to: generate an association between an object type schema and the second object type schema, wherein the object type schema is associated with the selected object type schema. ### Claim 5 (depends on 4) The apparatus of claim 4, wherein the association between the object type schema and the second object type schema comprises an updated object version identifier associated with the object type identifier node of the second object type schema. ### Claim 6 (depends on 1) The apparatus of claim 1, wherein the plurality of object attribute identifier nodes configured in a directed graph structure comprise a plurality of object version identifiers nodes associated with a plurality of version types for an object type of the object type identifier node. ### Claim 7 (depends on 6) The apparatus of claim 6, the computer-coded instructions are further configured to cause the apparatus to: generate an object version type schema comprising at least the object type identifier node and the plurality of object version identifier nodes based on a plurality of shared object attribute identifier nodes, wherein each object version identifier node of the plurality of object version identifier nodes comprises at least one of a plurality of incident identifiers or a plurality of change identifiers. ### Claim 8 (depends on 7) The apparatus of claim 7, the computer-coded instructions are further configured to cause the apparatus to: receive an object version query comprising the selected object type identifier; traverse the directed graph structure to return the object version type schema comprising at least an object version identifier node subset associated with the selected object type identifier; and output a selected object version type interface component based on the object version identifier node subset for rendering to the object types registry interface. ### Claim 9 A computer-implemented method for managing an object types registry interface of an asset management system, the computer-implemented method comprising: accessing an asset management repository comprising a plurality of object type identifier nodes and a plurality of object attribute identifier nodes configured in a directed graph structure; receiving an object query comprising a selected object type identifier; traversing the directed graph structure to return a selected object type schema comprising an object attribute identifier node subset associated with the selected object type identifier; and outputting a selected object type interface component based on the selected object type schema for rendering to an object types registry interface. ### Claim 10 (depends on 9) The computer-implemented method of claim 9, further comprising receiving a second attribute creation request, the second attribute creation request comprising a second plurality of attribute identifier nodes in association with the plurality of object type identifier nodes to be configured in the directed graph structure. ### Claim 11 (depends on 10) The computer-implemented method of claim 10, wherein the second plurality of attribute identifier nodes comprises at least a second attribute identifier node configured to generate a second object type schema with an object type identifier node of the plurality of object type identifier nodes. ### Claim 12 (depends on 11) The computer-implemented method of claim 11, further comprising generating an association between an object type schema and the second object type schema, wherein the object type schema is associated with the selected object type schema. ### Claim 13 (depends on 12) The computer-implemented method of claim 12, wherein the association between the object type schema and the second object type schema comprises an updated object version identifier associated with the object type identifier node of the second object type schema. ### Claim 14 (depends on 9) The computer-implemented method of claim 9, wherein the plurality of object attribute identifier nodes configured in a directed graph structure comprise a plurality of object version identifiers nodes associated with a plurality of version types for an object type of the object type identifier node. ### Claim 15 (depends on 14) The computer-implemented method of claim 14, further comprising generating an object version type schema comprising at least the object type identifier node and the plurality of object version identifier nodes based on a plurality of shared object attribute identifier nodes, wherein each object version identifier node of the plurality of object version identifier nodes comprises at least one of a plurality of incident identifiers or a plurality of change identifiers. ### Claim 16 (depends on 15) The computer-implemented method of claim 15, further comprising: receiving an object version query comprising the selected object type identifier; traversing the directed graph structure to return the object version type schema comprising at least an object version identifier node subset associated with the selected object type identifier; and outputting a selected object version type interface component based on the object version identifier node subset for rendering to the object types registry interface. ### Claim 17 A computer-program product comprising at least one non-transitory computer-readable storage medium having computer-readable program code thereon that, in execution with at least one process, configures the computer-program product for: accessing an asset management repository comprising a plurality of object type identifier nodes and a plurality of object attribute identifier nodes configured in a directed graph structure; receiving an object query comprising a selected object type identifier; traversing the directed graph structure to return a selected object type schema comprising an object attribute identifier node subset associated with the selected object type identifier; and outputting a selected object type interface component based on the selected object type schema for rendering to an object types registry interface. ### Claim 18 (depends on 17) The computer-program product of claim 17, wherein the computer-readable program code is further configured for: receiving a second attribute creation request, the second attribute creation request comprising a second plurality of attribute identifier nodes in association with the plurality of object type identifier nodes to be configured in the directed graph structure. ### Claim 19 (depends on 18) The computer-program product of claim 18, wherein the second plurality of attribute identifier nodes comprises at least a second attribute identifier node configured to generate a second object type schema with an object type identifier node of the object type identifier nodes. ### Claim 20 (depends on 19) The computer-program product of claim 19, wherein the computer-readable program code is further configured for: generating an association between an object type schema and the second object type schema, wherein the object type schema is associated with the selected object type schema. ### Claim 21 (depends on 20) The computer-program product of claim 20, wherein the association between the object type schema and the second object type schema comprises an updated object version identifier associated with the object type identifier node of the second object type schema. ### Claim 22 (depends on 17) The computer-program product of claim 17, wherein the plurality of object attribute identifier nodes configured in a directed graph structure comprise a plurality of object version identifiers nodes associated with a plurality of version types for an object type of the object type identifier node. ### Claim 23 (depends on 22) The computer-program product of claim 22, wherein the computer-readable program code is further configured for: generating an object version type schema comprising at least the object type identifier node and the plurality of object version identifier nodes based on a plurality of shared object attribute identifier nodes, wherein each object version identifier node of the plurality of object version identifier nodes comprises at least one of a plurality of incident identifiers or a plurality of change identifiers. ### Claim 24 (depends on 23) The computer-program product of claim 23, wherein the computer-readable program code is further configured for: receiving an object version query comprising the selected object type identifier; traversing the directed graph structure to return the object version type schema comprising at least an object version identifier node subset associated with the selected object type identifier; and outputting a selected object version type interface component based on the object version identifier node subset for rendering to the object types registry interface.