| Element Name | Include |
|---|---|
| Parent Elements | MetaDataVersion |
| Element XPath(s) | /ODM/Study/MetaDataVersion/Include |
| Element Textual Value | None |
| Attributes | StudyOID, MetaDataVerionOID, href |
|---|---|
| Child Elements | None |
Attributes
| Jira | ||||||
|---|---|---|---|---|---|---|
|
...
Contained in:
...
A reference to a prior metadata version. This version must be present earlier in the same ODM file or in a previous file in the series. See the PriorFileOID attribute of the ODM element.
| Usage/Business Rules |
|
|---|
|
...
|
The href attribute allows to provide the location (as a URL) to the ODM where the to-be-included elements can be retrieved from, in the case that the combination of the referenced study and metadataversion is not present in the same file. The reference can be to a file, e.g. "file:///d:/MyStudies/MyStudy/PriorVersionODM.xml" or e.g. be an API call, like "https://www.MyCompany.com/MyStudies?StudyOID=MyStudy&MetaDataVersionOID=MV.001".
In the following example, question "I.003" has been added to the ItemGroup "IG.001" by adding an ItemRef element to the ItemGroupDef. The new version of the ItemGroupDef now contains only one of the Aliases, and the other Alias defined in MetaDataVersion "MDV.001" has been removed. This same mechanism is used to remove ItemRefs from an ItemGroupDef, or to re-order them.
| Code Block |
|---|
<Study OID="S.001">
<MetaDataVersion OID="MDV.001" Name="First Metadata version">
<ItemGroupDef OID="IG.001" Name="First ItemGroup">
<ItemRef ItemOID="I.001" Mandatory="Yes" OrderNumber="1"/>
<ItemRef ItemOID="I.002" Mandatory="Yes" OrderNumber="2"/>
<Alias Context="Context1" Name="IG1"/>
<Alias Context="Context2" Name="FIRST"/>
</ItemGroupDef>
</MetaDataVersion>
<MetaDataVersion OID="MDV.002" Name="Second Metadata version">
<Include StudyOID="S.001" MetaDataVersionOID="MDV.001"/>
<ItemGroupDef OID="IG.001" Name="First ItemGroup (modified)">
<ItemRef ItemOID="I.001" Mandatory="Yes" OrderNumber="1"/>
<ItemRef ItemOID="I.003" Mandatory="Yes" OrderNumber="2"/>
<ItemRef ItemOID="I.002" Mandatory="Yes" OrderNumber="3"/>
<Alias Context="Context1" Name="IG1"/>
</ItemGroupDef>
</MetaDataVersion>
</Study> |
...
|
...
|
...
|
...
|
...
Note: By placing this information in a subelement of MetaDataVersion (rather than in attributes) we allow for future evolution of this capability. For example, it might be useful to allow inclusion of two common metadata dictionaries, or to add new common metadata into a previous study-specific metadata version.
...