Campaign Lifecycle Management

This is where administrative users:

start new campaigns.
Campaigns are founded on questionnaire specifications and suites of associated parameters configurations. This is the interactive process where specifications are chosen, parameter suites defined, and other facets of the campaign model provided (identifiers, descriptions, timestamps, lifecycle state, etc.).
Overall, this process acquires all the information required to generate campaign populations.
populate campaigns.
This is a generative process that uses questionnaire specifications and parameter suites to beget families of (empty) questionnaires. The process also marks the start of individual questionnaire lifecycles.
Population is inherently a bulk process and as such raises common expectations: report on completion status and resilience to individual failures. Single runs with specific parameter configurations may be required to reprocess individual failures from bulk runs, or to support previewing. Equally of value is the ability to resume population and apply it to questionnaires that have not successfully completed in previous runs.
The process subsume a loading process for each element of the population and the subsequent enforcement of dynamic exclusion constraints on questionnaire selections. Because of selection loading, existing statistics are a key input of campaign population.
The process also subsumes a resolution process whereby selection coordinates are replaced by localised names, such as will be rendered in published forms. Because of coordinate resolution, reference data is also a key input of campaign population.
close campaigns.
This an action that marks the completion of the data collection process, typically because the entire questionnaire population has been submitted and ingested in the working system.
disseminate campaigns.
Campaigns have visibility within the insitution. Starting and closing campaigns are events that can be triggered through network APIs.
Similarly, the current status of compaigns - including the lifecycle state of each member of its population - can be reported through network APIs.
Collectively, the APIs represent the interface of the system towards institution-wide process or workflow management solutions.

PreviousSpecification Lifecycle Management NextQuestionnaire Lifecycle Management

Last updated 6 years ago

This is where administrative users:

start new campaigns.
Campaigns are founded on questionnaire specifications and suites of associated parameters configurations. This is the interactive process where specifications are chosen, parameter suites defined, and other facets of the campaign model provided (identifiers, descriptions, timestamps, lifecycle state, etc.).
Overall, this process acquires all the information required to generate campaign populations.
populate campaigns.
This is a generative process that uses questionnaire specifications and parameter suites to beget families of (empty) questionnaires. The process also marks the start of individual questionnaire lifecycles.
Population is inherently a bulk process and as such raises common expectations: report on completion status and resilience to individual failures. Single runs with specific parameter configurations may be required to reprocess individual failures from bulk runs, or to support previewing. Equally of value is the ability to resume population and apply it to questionnaires that have not successfully completed in previous runs.
The process subsume a loading process for each element of the population and the subsequent enforcement of dynamic exclusion constraints on questionnaire selections. Because of selection loading, existing statistics are a key input of campaign population.
The process also subsumes a resolution process whereby selection coordinates are replaced by localised names, such as will be rendered in published forms. Because of coordinate resolution, reference data is also a key input of campaign population.
close campaigns.
This an action that marks the completion of the data collection process, typically because the entire questionnaire population has been submitted and ingested in the working system.
disseminate campaigns.
Campaigns have visibility within the insitution. Starting and closing campaigns are events that can be triggered through network APIs.
Similarly, the current status of compaigns - including the lifecycle state of each member of its population - can be reported through network APIs.
Collectively, the APIs represent the interface of the system towards institution-wide process or workflow management solutions.