Define-XML and ryze

ryze supports define xml 2 1 and previous versions of define xml and you can import and export define xml in different versions since the formatting can change between versions, there are some properties to consider when working with define external standards see docid\ g7sbrmfxwcbbg1mp6rai2 origins origins in the ryze ui are designed to support the latest version of define xml since there are differences with the formatting of define xml 2 0 and 2 1 for example, when editing an origin in ryze; if you select type collected and source investigator , then the exported define 2 0 origin is displayed as “crf” importing and exporting define 2 0 when adding an origin to an asset, (such as a variable or value), you should follow cdisc guidance for the expected type and source , see the https //www cdisc org/standards/data exchange/define xml the following tables show how ryze handles origin definitions on import and export import origin properties are displayed differently in the ryze user interface the following table shows how these properties are displayed after importing to ryze export the following table shows how ryze properties are converted to define 2 0 on export !=vendor if source is not equal to “vendor" "derived" origins define xml 2 1 guidance means that when you set an origin as “derived” you must also create or associate a method asset class and subclass you can add a subclass to a class property, subclasses allow you to provide a more descriptive classification of the datasets subclasses are free text fields and you can add more than one subclass has no data the “ has no data '' property can be set on assets, such as variables, where no data is present when “ has no data ” is checked, a warning is displayed that the user should have a comment on the corresponding asset to explain why once you create or associate a comment, the warning is removed