Document registry system

• US 8,620,911 B2
• Filed: 04/29/2010
• Issued: 12/31/2013
• Est. Priority Date: 04/29/2010
• Status: Expired due to Fees

• Current Assignee: Micro Focus LLC (Open Text Corporation)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Simske, Steven J., Coughlan, Chris, Jacobsen, Mark, Keyes, Mick, Moloney, Gary
• Primary Examiner(s): VO, TRUONG V
• Application Number:
  US13/634,764
• Publication Number:
  US 20130036127A1
• Time in Patent Office: 1,342 Days
• Field of Search: 707/728
• US Class Current: 707/728
• CPC Class Codes: G06F 16/33 Querying
• CPC Class Codes: G06F 16/93 Document management systems
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Abstract

A document registry system (10) includes a registry database (20) with a specific task sub-database (22) and an analytics-supporting general task sub-database (24). The sub-databases (22, 24) include i) pre-existing fields configured to store, respectively, specific task-related and analytics-related document data received from one or more of a plurality of sources (S1, S2, S3, S4) or from a source (NS1, NS2) other than the plurality of sources (S1, S2, S3, S4), and ii) de novo fields configured tote generated as a result of, respectively, a specific task query and a general task query and configured to store, respectively, specific task-related and general task-related document data received from source(s) (NS1, NS2) other than the plurality of sources (S1, S2, S3, S4). A query mapping engine (26) is configured to receive a request entry, map the request entry into a query, and actively collect data based upon the query. Data is collected from the specific task sub-database (22) or the analytics-supporting general task sub-database (24), and from the source(s) (NS1, NS2) other than the plurality of sources (S1, S2, S3, S4).

Claims

1. A document registry system (10), comprising:

a registry database (20), including;

a specific task sub-database (22), including;

pre-existing fields configured to store specific task-related document data received from one or more of a plurality of sources (S1, S2, S3, S4 or from a source other than the plurality of sources (NS1, NS2); and

de novo fields configured to be generated as a result of a general task query and configured to store specific task-related document data received from the source other than the plurality of sources (NS1, NS2);

an analytics-supporting general task sub-database (24), including;

pre-existing fields configured to store general task-related document data received from one or more of the plurality of sources (S1, S2, S3, S4) or at least a second source other than the plurality of sources (NS1, NS2); and

de novo fields configured to be generated as a result of a general task query and configured to store general task-related document data received from the source or the second source other than the plurality of sources (NS1 NS2); and

a query mapping engine (26) configured to receive a request entry, map the request entry into a query, and actively collect data based upon the query from the specific task sub-database (22) or the analytics-supporting general task sub-database (24), and from the source or the it least a second source other than the plurality of sources (NS1, NS2).

2. The document registry system (10) as defined in claim 1, further comprising an anonymity or obfuscation engine (30) in operative communication with the registry database (20), the anonymity or obfuscation engine (30) configured to anonymize or obfuscate the collected data.

3. The document registry system (10) as defined in claim 1, further comprising a filter (32) in operative communication with the registry database (20), the filter (32) configured to at least one of process, categorize, or classify the collected data.

4. The document registry system (10) as defined in claim 1, further comprising:

a computing device (14) configured to transmit the request entry; and

a cloud computing network (12) configured to be accessible by the computing device (14) and configured to provide an access point (34) into a workflow management system (18) include the query mapping engine (26).

5. The document registry system (10) as defiled in claim 4 wherein the cloud computing network (12) is further configured to publicly post information based upon a general security love.

6. The document registry system (10) as defined in claim 4, wherein the cloud computing network (12) is further configured to post information based upon predetermined levels of discretization of access control.

7. The document registry system (10) as defined in claim 1, further comprising a computing device (16) configured to:

i) receive the collected data; and

ii) generate output, based upon the collected data, for one of a plurality of document-based workflows, the output affecting a condition of the one of the plurality of document-based workflows upstream, downstream, or at point at which the request entry is received.

8. The document registry system (10) as defined in claim 7 wherein the computing device (16) is configured to generate the output by at least one of:

i) generating and populating the de nova fields of the specific task sub-database (22) or the analytics-supporting general task sub-database (24) based upon the collected data;

ii) depopulating or deleting the pre-existing fields of the specific task sub-database (22) or the analytics-supporting general task sub-database (24) based upon the collected data;

or

iii) repopulating the pre-existing fields of the specific task sub-database (22) or the analytics-supporting general task sub-database (24) based upon the collected data.

9. The document registry system (10) as defined in claim 7, further comprising the plurality of sources (S1, S2, S3, S4), each of which subscribes to a workflow management system (18) and participates in at least one of the plurality of document-based workflows, and wherein the computing device (16) is further configured to automate at least, one of a process, a response, or an action related to a particular node of the at least one of the plurality of document-based workflows upstream, downstream or at the point at which the request entry is received.

10. The document registry system (10) as defined in claim 1, further comprising a hierarchy of the data in the registry database (20), the hierarchy being based upon a query semantics tag assigned to at least one of the plurality of sources (S1, S2, S3, S4) or a document-based workflow after the query is performed.

11. The document registry system (10) as defined in claim 1, further comprising:

a source of the entry request; and

data access rules associated with the source of the entry request;

wherein the query mapping engine (26) is configured to map the query based upon the data access rules.

12. A method operating on a cloud computing network (12) for responding to a request entry, the cloud computing network (12) having instructions stored thereon, the instructions being executable to perform the steps of:

receiving the request entry for information related to at least one document-based workflow;

identifying an originator of the request entry;

determining information access rules for the identified originator;

mapping the request entry into a query, based upon the information access rules, for i) either a specific task sub-database (22) or an analytics-supporting general task sub-database (24) of a registry database (20) and ii) at least one source (NS1, NS2) other than a source (S1, S2, S3, S4) that subscribes to the registry database (20);

actively collecting data based upon the query from the specific task sub-database (22) or the analytics-supporting general task sub-database (24), and from the at least one source (NS1, NS2) other than the source (S1, S2, S3, S4) that subscribes to the registry database (20);

running the mapped query; and

at least one of;

i) repopulating a pre-existing field of the specific task sub-database (22) based upon data received from the running of the mapped query;

or

ii) depopulating or deleting a pre-existing field of the specific task sub-database (22) based upon data received from the running of the mapped query;

or

iii) creating at least one de novo field in the specific task sub-database (22); and

populating the at least one de novo field with data retrieved from the running of the mapped query.

13. The method as defined in claim 12, further comprising:

determining that the request entry pertains to a specific instantiation of the at least one document-based workflow;

running the mapped query on the specific task sub-database (22) and on the at least one source (NS1, NS2) other than the source (S1, S2, S3, S4) that subscribes to the registry database (20); and

at least one of;

i) repopulating a pre-existing field of the specific task sub-database (22) based upon data received from the running of the mapped query;

or

ii) depopulating or deleting a pre-existing field of the specific task sub database (22) based upon data received from the running of the mapped query;

or

iii) creating at least one de novo field in the specific task sub database (22); and

populating the at least one de novo field with data retrieved from the running of the mapped query.

14. The method as defined in claim 12, further comprising:

determining that the request entry pertains to a general inquiry regarding the at least one document-based workflow;

running the mapped query on the analytics-supporting general task sub-database (24) and on the at least one source (NS1, NS2) other than the source (S1, S2, S3, S4) that subscribes to the registry database (20);

at least one of;

i) repopulating a pre-existing field of the analytics-supporting general task sub-database (24) based upon data received from the running of the mapped query;

or

depopulating or deleting a pre-existing field of the analytics-supporting general task sub-database (24) based upon data received from the running of the mapped query;

or

iii) creating at least one de novo field in the analytics-supporting general task sub-database (24); and

populating the at least one de novo field with data retrieved from the running of the mapped query.

15. The method as defined in claim 12, further comprising generating output, based upon the collected data, for one of a plurality of document-based workflows in the registry database (20), the output affecting a condition of the one of the plurality of document-based workflows upstream, downstream, or at a point at which the request entry is received.

16. A non-transitory computer-readable storage medium storing instructions that, when executed by a processor-based system, cause the processor-based system to perform a method for responding to a request entry, comprising:

receiving the request entry for information related to at least one document-based workflow;

identifying an originator of the request entry;

determining information access rules for the identified originator;

mapping the request entry into a query, based upon the information access rules, for i) either a specific task sub-database (22) or an analytics-supporting general task sub-database (24) of a registry database (20) and ii) at least one source (NS1, NS2) other than a source (S1, S2, S3, S4) that subscribes to the registry database (20);

actively collecting data based upon the query from the specific task sub-database (22) or the analytics-supporting general task sub-database (24), and from the at least one source (NS1, NS2) other than the source (S1, S2, S3, S4) that subscribes to the registry database (20);

running the mapped query; and

at least one of;

i) repopulating a pre-existing field of the specific task sub-database (22) based upon data received from the running of the mapped query;

or

ii) depopulating or deleting a pre-existing field of the specific task sub-database (22) based upon data received from the running of the mapped query;

or

iii) creating at least one de novo field in the specific task sub-database (22); and

populating the at least one de novo field with data retrieved from the running of the mapped query.

17. The computer-readable medium of claim 16, the method further comprising:

determining that the request entry pertains to a specific instantiation of the at least one document-based workflow;

running the mapped query on the specific task sub-database (22) and on the at least one source (NS1, NS2) other than the source (S1, S2, S3, S4) that subscribes to the registry database (20); and

at least one of;

i) repopulating a pre-existing field of the specific task sub-database (22) based upon data received from the running of the mapped query;

or

ii) depopulating or deleting a pre-existing field of the specific task sub-database (22) based upon data received from the running of the mapped query;

or

iii) creating at least one de novo field in the specific task sub-database (22); and

populating the at least one de novo field with data retrieved from the running of the mapped query.

18. The computer-readable medium of claim 16, the method further comprising:

determining that the request entry pertains to a general inquiry regarding the at least one document-based workflow;

running the mapped query on the analytics-supporting general task sub-database (24) and on the at least one source (NS1, NS2) other than the source (S1, S2, S3, S4) that subscribes to the registry database (20);

at least one of;

i) repopulating a pre-existing field of the analytics-supporting general task sub-database (24) based upon data received from the running of the mapped query;

or

ii) depopulating or deleting a pre-existing field of the analytics-supporting general task sub-database (24) based upon data received from the running of the mapped query;

or

iii) creating at least one de novo field in the analytics-supporting general task sub-database (24); and

populating the at least one de novo field with data retrieved from the running of the mapped query.

19. The computer-readable medium of claim 16, the method further comprising generating output, based upon the collected data, for one of a plurality of document-based workflows in the registry database (20), the output affecting a condition of the one of the plurality of document-based workflows upstream, downstream, or at a point at which the request entry is received.