US 8,620,911 B2 · Document registry system

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).

Claims19

Dependent claims

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).

8 more elements

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.

12 more elements

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.

12 more elements

Dependencies are inferred from the claim text.

Document registry system

Life of this patent

Document registry system

Life of this patent

Abstract

Claims19