Abstract: Examples disclosed herein relate to item identifier assignment. For example, a processor may create a mass serialization scheme to provide a list of item identifiers to allow a subset of the identifiers to be knocked out. Each item identifier may associated with multiple containers, and each container may include two item identifiers relating to the sequence of item identifiers included within the container.

Abstract: A system includes a plurality of sources that subscribe to, and another source that is unaffiliated with, a workflow management system. The system further includes a registry database that has pre-existing fields that are configured to store data received from one or more of the sources or from the other source, and de novo fields that are configured to be generated as a result of a data collection event and are configured to store data received from one or more of the sources or from the other source. An engine is configured to actively collect data from the sources and from the other source. The system further includes a dynamically updatable user interface that is operatively connected to the registry database. The dynamically updatable user interface is configurable or re-configurable for a particular one of the plurality of sources in response to the data collection event.

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.

Abstract: An information tracking system includes a plurality of sources (S1, S2, S3, S4) that subscribe to, and another source (NS1, NS2) that is unaffiliated with, a workflow management system (18). The information tracking system (10) further includes a registry database (20) that has pre-existing fields that are configured to store data received from one or more of the sources (S1, S2, S3, S4) or from the other source (NS1, NS2), and de novo fields that are configured to be generated as a result of a data collection event and are configured to store data received from one or more of the sources (S1, S2, S3, S4) or from the other source (NS1, NS2). An engine (26) is configured to actively collect data from the sources (S1, S2, S3, S4) and from the other source (NS1, NS2). The system (10) further includes a dynamically updatable user interface (UI) that is operatively connected to the registry database (20).

Abstract: An information tracking system (10) includes a plurality of sources (S1, S2, S3, S4) that subscribe to a workflow management system (10), a sensor network (NS1, NS2) that is unaffiliated with the workflow management. System (10), a registry database (20) and an engine (26). The registry database (20) includes pre-existing fields configured to store data received from one or more of the plurality of sources (S1, S2, S3, S4) or from the sensor network (NS1, NS2) and de novo fields configured to be generated as a result of a sensor data collection event and configured to store sensor data received from one or more of the plurality of sources (S1, S2, S3, S4) or from the sensor network (NS1, NS2). The engine (26) is configured to actively collect sensor data from the plurality of sources (S1, S2, S3, S4) and from the sensor network (NS1, NS2).

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.