13-6 Oracle Fusion Middleware Administrators Guide for Universal Records Management
13.3 XSD Data Transfer
XSD schemas can be used to manage records, folders, and content to comply with the DoD 5015.2 specification. Exporting and importing data using a format defined as XSD
format XML Schema Definition conforms with standard transfer schema defaults.
The information must be mapped before proceeding with exporting or importing. After the correct mapping is in the place, data can be imported and used in Oracle
URM. It can then later be transferred as needed to NARA or another system using the XSD schema for that site.
13.3.1 Important Considerations Before Exporting
Two considerations should be evaluated before beginning the import and export process:
■
Special Handling of choice Elements on page 13-6
■
Required Fields on Import on page 13-6
■
Target Namespace and Qualified Locals on page 13-6
13.3.1.1 Special Handling of choice Elements
The choice element type allows only one of the elements contained in the selected group to be present within a containing element. This differs from an option list in
which one field can have multiple possible values.
A document whose data is being exported can only contain a value in one of the fields contained in the xs:choice group. This restriction determines which field to use
when the XML file is generated for output. If more than one of the fields in the choice group contain a value, an error occurs and the export cannot finish because of
ambiguity as to which field should be used.
The following example shows this type of choice list. In this example, an employee can be only one of the three types of employees full-time, part-time, or
contractor. So only one of the three corresponding fields can be contained in the choice
element. xs:complexType name=employee
xs:choice xs:element ref=full-time
xs:element ref=part-time xs:element ref=contractor
xs:choice xs:complexType
13.3.1.2 Required Fields on Import
If your server has required fields, all of those fields must have a value set in order to perform an import. Mapping the required fields to an XML node provides the value.
However, if any of the required fields are not mapped, a profile must be created that sets these values on import. If this is not done, the import fails.
13.3.1.3 Target Namespace and Qualified Locals
Explicitly declare a target namespace in the .xsd file and also specify that locally defined elements and locally defined attributes are qualified. The target namespace is
specified by the targetNamespace attribute.
Archiving and Transfering Information 13-7
Local elements and attributes can be qualified globally by using the elementFormDefault
and attributeFormDefault attributes on the schema element. They can be specified separately for each local declaration using the form
attribute. Attribute values can be set to unqualified or qualified, to indicate if locally declared elements and attributes must be unqualified.
13.3.2 Configuring XSD for Importing and Exporting
