EVAL_DATA

Owned by Former user (Deleted)
Last updated: Sept 11, 2009Version comment
3 min read

XML documents defining EVALSYS entities must include one and only one EVAL_DATA element at the top level.

The EVAL_DATA element may contain other elements. There are eight types of elements that may occur at the top level within the EVAL_DATA element. They are:

The EVAL_DATA element may contain zero or one of each of these elements. They should appear in the order shown above. If you look at the definitions of the types for each of these elements, you will find that each of the top-level elements within an EVAL_DATA element may contain one or more elements. Details about each of these elements can be found in the pages about the element types above.

The EVAL_DATA element is defined as follows:

<xsd:element name="EVAL_DATA">
		<xsd:annotation>
			<xsd:documentation xml:lang="en">
				<p>The outer element in an XML file describing evaluation data is "eval_data".
					Within the "eval_data" element, one or more sets of elements may be defined, and
					within each set, one or more elements may be defined. If more than one of the
					top-level elements is being defined within the "eval_data" element, they should
					be listed in a particular order so references to other entities loaded in the
					same XML file will not lead to errors. The order is:</p>
				<ul>
					<li>eval_scales</li>
					<li>eval_items</li>
					<li>eval_item_groups</li>
					<li>eval_templates</li>
					<li>eval_templateitems</li>
					<li>eval_email_templates</li>
					<li>eval_evaluations</li>
					<li>eval_assign_groups</li>
				</ul>

				<p> UMICH changes: none </p>
			</xsd:documentation>
		</xsd:annotation>

		<xsd:complexType>
			<xsd:sequence>
				<xsd:element name="EVAL_SCALES" type="eval_scales" minOccurs="0">
					<xsd:annotation>
						<xsd:documentation xml:lang="en">
							<p>This element is a container for one or more "eval_scale"
								elements.</p>
							<p> UMICH changes: none </p>
						</xsd:documentation>
					</xsd:annotation>
				</xsd:element>
				<xsd:element name="EVAL_ITEM_GROUPS" type="eval_item_groups" minOccurs="0"> </xsd:element>
				<xsd:element name="EVAL_ITEMS" type="eval_items" minOccurs="0">
					<xsd:annotation>
						<xsd:documentation xml:lang="en">
							<p>This element is a container for one or more "eval_item" elements. </p>
							<p> UMICH changes: This element is new but is not required. Since
								Michigan does not use eval_item_groups, no change is required. </p>
						</xsd:documentation>
					</xsd:annotation>
				</xsd:element>
				<xsd:element name="EVAL_TEMPLATES" type="eval_templates" minOccurs="0">
					<xsd:annotation>
						<xsd:documentation xml:lang="en">
							<p>This element is a container for one or more "eval_template"
								elements.</p>
							<p> UMICH changes: none </p>
						</xsd:documentation>
					</xsd:annotation>
				</xsd:element>
				<xsd:element name="EVAL_TEMPLATEITEMS" type="eval_templateitems" minOccurs="0">
					<xsd:annotation>
						<xsd:documentation xml:lang="en">This element is a container for one or more
							"eval_templateitem" elements.</xsd:documentation>
						<xsd:documentation xml:lang="en"> UMICH changes: none </xsd:documentation>
					</xsd:annotation>
				</xsd:element>
				<xsd:element name="EVAL_EMAIL_TEMPLATES" type="eval_email_templates" minOccurs="0">
					<xsd:annotation>
						<xsd:documentation xml:lang="en">This element is a container for one or more
							"eval_email_template" elements.</xsd:documentation>
						<xsd:documentation xml:lang="en"> UMICH changes: none </xsd:documentation>
					</xsd:annotation>
				</xsd:element>
				<xsd:element name="EVAL_EVALUATIONS" type="eval_evaluations" minOccurs="0">
					<xsd:annotation>
						<xsd:documentation xml:lang="en">This element is a container for one or more
							"eval_evaluation" elements.</xsd:documentation>
						<xsd:documentation xml:lang="en"> UMICH changes: none </xsd:documentation>
					</xsd:annotation>
				</xsd:element>
				<xsd:element name="EVAL_ASSIGN_GROUPS" type="eval_assign_groups" minOccurs="0">
					<xsd:annotation>
						<xsd:documentation xml:lang="en">This element is a container for one or more
							"eval_assign_group" elements.</xsd:documentation>
						<xsd:documentation xml:lang="en"> UMICH changes: none </xsd:documentation>
					</xsd:annotation>
				</xsd:element>
			</xsd:sequence>
			<xsd:attribute name="update_policy" use="optional">
				<xsd:annotation>
					<xsd:documentation xml:lang="en">
						<p> Acceptable values for the optional "duplicate_eid_policy" attribute of
							the "EVAL_DATA" element are "reject", "replace" and "cascade". The
							default is "reject". The value of this attribute determines the policy
							that will apply to import of elements whose EID duplicates the EID of an
							existing element of the same class. </p>
						<p> A value of "reject" indicates that attempts to import a duplicate
							element will be rejected. No changes will be made to the existing
							element, and no new element will be created. An error will be reported
							(TODO: how will the error be reported?) </p>
						<p> A value of "replace" indicates that attempts to import an element with
							an EID that is already in use for elements of that type will result in
							updates of the existing entity in the system. The existing values of all
							properties and attributes of the object, as well as any elements
							contained by it, will be removed and replaced with values supplied in
							the newly imported element. If the element is an eval_template or
							eval_templateitem, no changes will be made to any existing
							eval_evaluation or eval_item that were previously created based on the
							previous values of the element. </p>
						<p> A value of "cascade" indicates that attempts to import an element with
							an EID that is already in use for elements of that type will result in
							updates of the existing entity in the system and the changes in the
							element's properties and any contained elements will be cascaded to any
							elements that were previously created based on earlier values for the
							element. </p>
					</xsd:documentation>
				</xsd:annotation>
			</xsd:attribute>

		</xsd:complexType>
	</xsd:element>