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.


This extends the WorkflowStepSequence allowing for a graph structuring of WorkflowSteps. It adds a WorkflowStepRelationStructure which describes the order of Workflow steps in StructuredWorkflowSteps that has multiple entry points and/or multiple exit points and/or, alternatively, a WorkflowStep can have multiple predecessors and/or multiple successors.


In the context of data management a WorkflowStepRelationStructure describes a network of data transformations and data products. Like all RelationStructures, a WorkflowStepRelationStructure is a Directed Acyclic Graph (DAG). A forward looking WorkflowStepRelationStructure describes the succession of data transformations and data products. A backward looking WorkflowStepRelationStructure describes the antecedents of one or a combination of data transformations and/or data products.


Describes structured relations between WorkflowSteps




A BusinessProcess precondition or post condition which describes the condition which must be met to begin (pre) or exit (post) a process. It may use a specified LogicalRecord. The Logical Record has SQL that describes it, rejectionCriteria against which its adequacy may be tested and an optional annotation that describes its provenance.


MetadataDrivenActions are Acts in which their logic is defined by validation and transformation rules expressed in some standard rule language.


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.


The BusinessWorkflow Package covers the description of business processes and traversals of business models like Generic Longitudinal Business Process Model (GLBPM) and/or the Generic Statistical Business Process Model (GSBPM), on a higher level than Workflow. It describes records rather than variables and is primarily based on the ETL (Extract, Transform, and Load) use case.


Subscribe to DDI Moving Forward RSS