# US 10,482,077 B2 · System and method for asynchronous update of a search index > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,482,077 B2 - Document ID: US10482077B2 - Status: Granted - Kind: B2 - Application number: 15/238,222 - Filed: 2016-08-16 - Published: 2017-07-13 - Granted: 2019-11-19 - Earliest claimed: 2016-01-07 - Assignees: International Business Machines Corporation - Applicants: International Business Machines Corporation - Inventors: Alexander Gavrin; Raymond T. Jones; Paulo H. Paulin; Jorge A. Senger; Maksim Vinokurov - Web page: https://patentgrep.com/patent/US10482077B2 ## CPC - G06F 16/2322: {using timestamps} - G06F 16/162: {Delete operations (erasing in storage systems G06F3/0652)} - G06F 16/31: Indexing; Data structures therefor; Storage structures - G06F 16/3331: Query processing - G06F 16/93: Document management systems - G06F 16/986: {Document structures and storage, e.g. HTML extensions} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A method for maintaining a document database and search index includes the steps of: (i) receiving a plurality of document action requests including one or more of a create document action request, a refresh document action request, a refreshfull document action request, an update document action request, or a delete document action request; (ii) creating a timestamp for each of the plurality of received document action requests; (iii) querying the document action requests to determine which are associated with a first document action request type; (iv) processing any of the document action requests of the first document action request type, where the document action requests are processed according to their associated timestamp; and (v) updating the search index using the updated document database. ## Claims ### Claim 1 A method for maintaining a graphical user interface (GUI), the method comprising the steps of: receiving a plurality of document action requests, wherein the plurality of document action requests comprise at least one of a create document action request, an update document action request, or a delete document action request; associating a timestamp with each of the plurality of received document action requests; querying the document action requests to determine which are associated with a first document action request type; processing any of the document action requests of the first document action request type, wherein the document action requests are processed according to their associated timestamp; and updating the graphical user interface (GUI) using an updated document database. ### Claim 2 (depends on 1) The method of claim 1, further comprising the steps of: querying the document action requests to determine which are associated with a second document action request type; and processing any of the document action requests of the second document action request type, wherein the document action requests are processed according to their associated timestamp; wherein the document action requests of the second document action request type are processed only if the document action requests of the first document action request type have been processed. ### Claim 3 (depends on 2) The method of claim 2, further comprising the steps of: querying the document action requests to determine which are associated with a third document action request type; and processing any of the document action requests of the third document action request type, wherein the document action requests are processed according to their associated timestamp; wherein the document action requests of the third document action request type are processed only if the document action requests of the second document action request type have been processed. ### Claim 4 (depends on 3) The method of claim 3, wherein create document action requests are processed first, update document action requests are processed second, and delete document action requests are processed last. ### Claim 5 (depends on 1) The method of claim 1, wherein said graphical user interface (GUI) is based on document content, taxonomy data, and one or more metadata fields from the document database. ### Claim 6 (depends on 1) The method of claim 1, further comprising the step of creating a database record for each document action request, wherein the database record comprises document data and document metadata. ### Claim 7 (depends on 1) The method of claim 1, wherein each type of document action request is processed by a different sub-process, and further wherein each sub-process is associated with a time that the sub-processed last processed a document action request. ### Claim 8 (depends on 7) The method of claim 7, wherein the time that the sub-processed last processed a document action request is stored. ### Claim 9 (depends on 7) The method of claim 7, wherein each sub-process is associated with a predetermined processing time threshold. ### Claim 10 (depends on 7) The method of claim 7, further comprising the step of terminating a sub-process if the predetermined processing time threshold is exceeded. ### Claim 11 An SSoR system, the system comprising: a document database comprising a plurality of documents; a graphical user interface (GUI); and a processor in communication with the document database and the graphical user interface (GUI), the processor configured to: (i) receive a plurality of document action requests, the plurality of document action requests comprising at least one of a create document action request, an update document action request, or a delete document action request; (ii) associate a timestamp with each of the plurality of received document action requests; (iii) query the document action requests to determine which are associated with a first document action request type; (iv) process any of the document action requests of the first document action request type, wherein the document action requests are processed according to their associated timestamp; and (v) update the graphical user interface (GUI) using an updated document database. ### Claim 12 (depends on 11) The system of claim 11, wherein the processor is further configured to: (i) query the document action requests to determine which are associated with a second document action request type; and (ii) process any of the document action requests of the second document action request type, wherein the document action requests are processed according to their associated timestamp, wherein the document action requests of the second document action request type are processed only if the document action requests of the first document action request type have been processed. ### Claim 13 (depends on 12) The system of claim 12, wherein the processor is further configured to: (i) query the document action requests to determine which are associated with a third document action request type; and (ii) process any of the document action requests of the third document action request type, wherein the document action requests are processed according to their associated timestamp, wherein the document action requests of the third document action request type are processed only if the document action requests of the second document action request type have been processed. ### Claim 14 (depends on 13) The system of claim 13, wherein create document action requests are processed first, update document action requests are processed second, and delete document action requests are processed last. ### Claim 15 (depends on 12) The system of claim 12, wherein the processor is further configured to create a database record for each document action request, wherein the database record comprises document data and document metadata. ### Claim 16 (depends on 11) The system of claim 11, wherein each type of document action request is processed by a different sub-process, and further wherein each sub-process is associated with a time that the sub-processed last processed a document action request. ### Claim 17 (depends on 16) The system of claim 16, wherein the time that the sub-processed last processed a document action request is stored. ### Claim 18 (depends on 16) The system of claim 16, wherein each sub-process is associated with a predetermined processing time threshold. ### Claim 19 (depends on 18) The system of claim 18, wherein the processor is further configured to terminate a sub-process if the predetermined processing time threshold is exceeded. ### Claim 20 A method for maintaining a graphical user interface (GUI), the method comprising the steps of: receiving a plurality of document action requests; associating a timestamp with each of the plurality of received document action requests; querying the document action requests to determine which are associated with a first document action request type; processing any of the document action requests of the first document action request type, wherein the document action requests are processed in the order of their associated timestamp, with earlier document action requests of the first document action request type being processed first; and updating the graphical user interface (GUI) using an updated document database.