News

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.

Welcome to the development platform for the next generation of DDI

The DDI Alliance is building a new model-based specification, for more information on the background to this see, the process and what we hope to achieve see the DDI Alliance website at http://www.ddialliance.org/ddi-moving-forward-process.

A site to hold discussions and further ongoing discussion is at https://ddi-alliance.atlassian.net/wiki/pages/viewpage.action?pageId=491703

DesignOverview

High level, descriptive, human informative, design statement The design may be used to specify how a process will be performed in general. This would most commonly be used in a Codebook along with an AlgorithmOverview and a MethodologyOverview. The design informs a specific or implemented process as to its general parameters. Supports specification of any realization of Goal.

AlgorithmOverview

High level, descriptive, human informative, algorithm statement used to describe the overall methodology. This would most commonly be used in a Codebook along with a MethodologyOverview and a DesignOverview.The underlying properties of the algorithm or method rather than the specifics of any particular implementation. In short a description of the method in its simplest and most general representation.

MethodologyOverview

High level, descriptive, human informative methodology statement used to describe the overall methodology, identify related design, algorithm, and process information. A methodology is normally informed by earlier research and clarifies how earlier research methods were incorporated into the current work.
This would most commonly be used in a Codebook along with an AlgorithmOverview and a DesignOverview. Note that Process may be described in more detail than a high level overview.

MethodologyOverviewPackage

Descriptive Methodology provides the basic means of describing in methodology in a descriptive, or human informative, terms rather than machine actionable content. Where available, specific use realizations of the Methodology Pattern should be created and/or use. All of these support general description as well as machine actionable description and may contain additional, defined metadata related to the specialized use.

RankingResponseDomain

A response domain capturing a ranking response which supports a "ranking" or "Ordering" of provided categories.
Note: This item still must be modeled and is incomplete at this time.

ScaleResponseDomain

A response domain capturing a scaled response, such as a Likert scale.
Note: This item still must be modeled and is incomplete at this time.

BooleanResponseDomain

A response domain capturing a binary response, such as selected/unselected or checked/unchecked or true/false.

CodeListResponseDomain

A response domain capturing a coded response (where both codes and their related category value are displayed) for a question. This response domain allows the single selection of one coded response.

NumericResponseDomain

A response domain capturing a numeric response (the intent is to analyze the response as a number) for a question.

Pages

Subscribe to DDI Moving Forward - google cloud RSS