Added automatic builds
Each day a ZIP-file is created via cron.
The builds consist of XMI, XSD, DocBook, PDF and graphs in dot, svg and png.
Added basic validation for names
installed module for validation, some rules for object and package names have been defined.
Added help for creating and managing the model
Guidelines for naming and propeties.
Added stage-tagging for objects
Re-arranged "Status" and added field for Stage, filter added on objects page.
Changes for Datatype
Datatype taxonomy is replaced by a datatype content type, to create a new one go to /node/add/datatype. You can specify basic documentation of the datatype and specify enumerated values. A datatype must be placed in a package.



The Sampling View covers the methodology and process for obtaining a sample from a described sample frame. It provides descriptive information of the methodologies used, design of the sample, algorithms to support the processing of the sample, goals, sample frames used, and guidance on the use of the resulting sample (for defining weights, limitations, etc.). This includes the use of the Workflows which can define the process of creating simple or complex samples on a step-by-step basis. Can be used as metadata to drive sample selection.


A BusinessProcess precondition or post condition which describes the condition which must be met to begin (pre) or exit (post) a process. It may include a specified 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.


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.


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


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.


BusinessProcesses could be Generic Longitudinal Business Process Model (GLBPM) and/or Generic Statistical Business Process Model (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.


BusinessWorkflow was introduced to provide Workflow with an upper model that could be used to describe traversals of the Generic Longitudinal Business Process Model (GLBPM) and/or the Generic Statistical Business Process Model (GSBPM) either in a one off study or in a wave that is part of a StudySeries.


Gives a UnitDataRecord structure to a Logical Record. UnitDataRecord structures a LogicalRecord as either a SimpleCollection or a StructuredCollection (InstanceVariableRelationStructure) of instance variables.

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


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.


Subscribe to DDI Moving Forward RSS