Proposal in progress

BusinessProcessPostCondition

A BusinessProcess precondition or postcondition is a dataset. The dataset has a position in the DataStore, SQL that describes it, rejectionCriteria against which its adequacy may be tested and an optional annotation that describes its provenance.

BusinessProcessPrecondition

A BusinessProcess precondition or postcondition is a dataset. The dataset has a position in the DataStore, SQL that describes it, rejectionCriteria against which its adequacy may be tested and an optional annotation that describes its provenance.

MetadataDrivenAction

Whereas ComputationActions are used in statistical packages like SPSS, Stata, SAS and R to perform data management and data transformations, MetadataDrivenActions are used by ETL (Extract Transform Load) platforms along with ComputationActions.

In ETLs the user is presented with a menu of MetadataDrivenActions that are captured here in an external controlled vocabulary.

In ETLs users enter into a dialog with the platform through which they customize the MetadataDrivenAction. The user writes no code. The dialog is saved.

BusinessProcessIndicator

Allows for the identification of the BusinessProcess specifically as a member and optionally provides an index for the member within an ordered array.

DataPipeline

A DataPipeline is a single traversal of the Generic Longitudinal Business Model (GLBPM) and/or the Generic Statistical Business process Model (GSBPM) in the course of a study where a study is either one off or a wave in a StudySeries.

BusinessProcess

BusinessProcesses are GLBPM and/or GSBPM steps and/or sub-steps. BusinessProcesses participate in a DataPipeline by virtue of their preconditions and postconditions.

A BusinessProcess differs from a WorkflowStep by virtue of its granularity. Higher level operations are the subject of BusinessProcesses. A BusinessProcess has a WorkflowStepSequence through which these higher levels operations may optionally be decomposed into WorkflowSteps.

UnitDataRecord

Gives a UnitDataRecord structure to a Logical Record. UnitDataRecord structures a LogicalRecord as either a SimpleCollection or a StructuredCollection of Instance Variables.

The UnitDataRecord also organizes Instance Variables in a Viewpoint. The Viewpoint assigns roles to Instance Variables. In any one Viewpoint UnitDataRecord Instance variables play one of three roles: identifier, measure or attribute. The same UnitDataRecord may have many Viewpoints.

InstanceVariableRelation

Defines the relationship between 2 or more InstanceVariables or, alternatively, defines a relationship that interleaves concepts and InstanceVariables.

Recall that an InstanceVariable is a type of Concept so, when the members of the relationship are two or more InstanceVariables, in this instance the source and target(s) as concepts are in fact placeholders for InstanceVariables.

ClassificationItemIndicator

A ClassificationItemIndicator realizes and extends a MemberIndicator which provides a Classification Item with an index indicating order and a level reference providing the level location of the Classification Item within a hierarchical structure.

GeographicUnitClassification

Describes the classification of specific geographic units into a classification system. As a subtype of Code List it can be used directly for the description of a value domain.

Pages

Subscribe to RSS - Proposal in progress