Importing Data
Data can be imported into the product’s information structure. The imported data must match the Model Identification Code and System Difference Code of the product information structure.
The import file is a standard zip file that contains all the appropriate information element files. The information elements from the zip file are downloaded into the appropriate sections of the product information structure automatically. This is based on the data module code or ICN of the information element.
|
|
If your import file contained a publication module, then the publication module is added to the information structure under a new Publication Modules node. A publication structure is also created under the product for each publication module.
|
1. In the Navigator, select the Folders item under your product.
The Folders view is displayed.
2. Select > from the Actions pull-down menu.
The New Document dialog box is displayed.
3. Select Import From Compressed File from the Type pull-down list.
4. In the Primary Content Source section, click Browse and select the required Import zip file.
5. Click Finish
The information elements from the zip file are downloaded into the appropriate sections of the product information structure.
|
|
All imported objects (data modules and entities) are imported at a workflow state of Imported.
To integrate the imported objects into the current system workflow, they need to be explicitly assigned. To do this, select the objects and choose the Assign to Workflow option from the context menu.
When the assignment task is complete, a message box indicates completion. Click OK to close the message. The objects’ workflow state is changed to Issued.
|
Importing Data from Earlier Projects
If you are importing data from earlier Arbortext Aerospace & Defense 4.x products, you must ensure that all the data modules reference the schema URL location. Use the schema URL location rather than a local or network location. For example:
<dmodule xsi:noNamespaceSchemaLocation="http://www.s1000d.org/S1000D_4-0-1/ xml_schema_flat/proced.xsd" ...
rather than:
<dmodule xsi:noNamespaceSchemaLocation="C:/dtds/S1000D_4-0-1/ xml_schema_flat/proced.xsd" ...
|
|
If your data modules contain local or network reference, you need to use a text editor to search for, and replace, all the local or network location references with the URL location, before attempting to import the data.
|
Validation of Data During Import
Data is validated on import into a product’s information structure. Warnings and errors are listed in an HTML report provided in the Validation folder in the Reports table for the product.
Sample information that may be provided by a validation report:
• Deleted data modules (Issue Type Deleted)
• Publications that reference deleted data modules
• Inclusion of a model/CAGE ICN not permitted for the product (error — will prevent the import)
• ACT/CCT containing data module level applicability (warning —will be ignored or changed, for example the ACT/CCT will not have applicability statements once imported)
• Invalid XML content
You can generate debug information about a content import. For more information, see
Troubleshoot a Content Import.
