You can reuse ODM-formatted study design metadata that is exported from a third-party application. Consider the following if you are importing metadata in ODM format into the Central Designer application to use in the creation of InForm studies or libraries.
All common StudyEventDefs in an ODM import file are consolidated into a single common visit after import. The forms defined for the common visits in the ODM import file appear in the single common visit in the Central Designer application.
The CommonVisit definition for the common visit that appears in the Central Designer application contains a LongTitle and ShortTitle, which are populated by the Description and Name defined in the first common StudyEventDef in the ODM import file.
The Central Designer application does not support ODM file chaining. The ODM specification allows files to be chained together through the FileOID and PriorFileOID attributes. File chaining is primarily used in Transactional ODM, but can also be used in Snapshot ODM to break up study metadata into multiple files that are chained together. Transactional ODM uses file chaining to create a final end state of a study upon import completion. Because the Central Designer application does not support file chaining, if you import Transactional ODM, an error occurs.
Note: You cannot import InForm metadata that you extracted from the InForm Adapter application with a Transactional file type. You must specify Snapshot as the file type parameter when you export data from the InForm Adapter application. For more information see the InForm Adapter User Guide.
Note: Any study event, with or without an OrderNumber attribute, is assigned a sequence number of zero if its predecessor in the workflow has a type of Scheduled.
The following localized study objects can be imported:
For example, during the import, to create a StudyEventOID, the Central Designer application:
In addition, within an ODM import file, ODM allows the reuse of RefNames if the RefName is for a different type of study object. However, the Central Designer application requires unique RefNames for all study objects in a study, and for all study objects in an import file. To enforce the uniqueness of RefNames in the import file, the Central Designer application adds prefixes to the imported study object RefNames according to the study object type.
If an ODM import file contains study objects with the same RefName, the Central Designer application uses the following logic:
Note: If you import multiple ODM files, and duplicate RefNames exist between the files, the Central Designer application allows you to import the study objects. You must resolve RefName conflicts after import in order to validate the study.
The Central Designer application applies the following prefixes for study objects with duplicate RefNames within an ODM import file.
Prefixes for CSML objects
CSML object type | Prefix |
---|---|
StudyDesign | SD_ |
StudyEvent | SE_ |
DataView (from the FormDef definition in the ODM import file) | DF_ |
DataView (from the ItemGroupDef definition in the ODM import file) | DI_ |
IntegerVariable, FloatVariable, DateTimeVariable, or TextVariable | VR_ |
CodeList | CL_ |
CodeListItem | CI_ |
Copyright © 2013 Oracle and/or its affiliates. All rights reserved. |
---|