News

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 http://www1.unece.org/stat/platform/display/DDI4/Tracking+Progress

New objects for Simple Instruments

New objects to enter the simple instrument view

SimpleInstrument

The purpose of Simple Instrument is to describe the data collection instrument and procedures involved in fielding a simple survey questionnaire.

ItemSequence

Describes the types of sequences that can be used for a set of items.

SpecificSequence

Describes the ordering of items when not otherwise indicated. There are a set number of values for ItemSequenceType, but also a provision for describing an alternate ordering using a command language.

ShapeCoded

Specifies a type of geometric shape for the purpose of determining the required information needed to render the object.

PointFormat

Provides an enumerated list of valid point format types for capturing a coordinate point.

BaseObjects

The package is a holding place for objects that are widely used but are not treated as properties; primarily identifiable types. A decision on the status and location of these objects needs to be made.

pInstrumentControl

InstrumentControl references a PhysicalInstrument. InstrumentControl assists in protocol representation. More specifically InstrumentControl facilitates the representation of an instrument order within a StudyUnit. [please clear this up. I fear this may not be an object. Either way the definition is not very clear. ]

StudyUnitControl

StudyUnitControl references a StudyUnitType. StudyUnitControl enables the representation of a research protocol at the StudyUnit level. [If the only purpose of the object is to carry a StudyUnit, it should be seriously considered for melting with another object. Modeling rules state that any object needs to have a reality of its own. Carrying another object is not a reality. If I misunderstood, please clarify the description instead]

Pages

Subscribe to DDI Moving Forward RSS