Documentation Center

Using the S1000D Upload Content tool

To upload S1000D and other content from the file system into your Contenta S1000D CSDB, use the S1000D Upload Content tool. This topic provides information you need before running this tool.

Use the S1000D Upload Content tool to upload the following items into the Contenta S1000D CSDB:
  • DMs
  • PMs
  • SCPMs
  • graphics
  • Word
  • Excel
  • PowerPoint
  • CSS
  • JS
  • ZIP

You can upload all of these types of content into a configuration in the CSDB hierarchy, or directly into a project for work in progress.

You can also upload S1000D Issue 1.6–1.9 SGML DMs into your CSDB. File extensions can be .sgm or .sgml. SGML DMs are converted to XML before being uploaded to the CSDB.

How content is stored in the CSDB

Contenta S1000D stores uploaded content in different folders based on the content's SNS or file type, as explained in How Content is Organized in Contenta S1000D in the Contenta S1000D documentation. If your database contains multiple configurations that contain S1000D content, and users do not have access to all configurations, you must upload any data modules and graphics that are shared across projects/programs into a shared configuration that is on all users' Contenta desktops. Each module, graphic, Word, Excel, PowerPoint, and ZIP file may exist only in one place in the database, and users may access only data in the configurations on their respective desktops. Data that is frequently shared includes Business Rules (BREX), Applicability (ACT, PCT, CCT) and Common Information Repository (CIR) data modules, as well as some graphics.

Schema support

Contenta S1000D supports the flat schema and the master schema in namespace URLs. Flat schemas are supported out of the box. See Supported Schemas for details.

Uploading XML content

The S1000D Upload Content tool validates that content specified to be uploaded consists of well-formed XML before uploading it. Optionally, the tool can also validate whether content complies with the applicable S1000D schema. You can elect whether well-formed content that fails the schema validation is uploaded.

While the tool is running, it displays the number of files that were successfully uploaded, skipped by choice, or failed to upload. Click one of the corresponding View log links to launch a window displaying the name and status of such files. The status information includes the file name, type, and issue number. S1000D Upload Content determines the S1000D Issue by checking the xsi:noNamespaceSchemaLocation attribute of the <dmodule>, <pm> or <scormContentPackage> tag. In addition, if you selected Local Upload to upload files from your client machine, the Upload Status section of the user interface includes the number of files not transferred to the server. Clicking the View log link corresponding to the Total not Transferred to Server total launches a window displaying the name of each file not transferred and the reason it was not transferred. When the upload is complete, if the upload of any files failed or was skipped, a Download files link becomes active, allowing you to download a .zip file containing the files that were not uploaded.

To upload files through your Web browser, you must have a version of the Java Runtime Environment (JRE) installed that is listed in the Contenta S1000D Platform Requirements.

Character entity support

The S1000D Upload Content tool may run into problems resolving character entities because it cannot access the s1000d.org web site. If so, configure S1000D Upload Content to look locally for entities by creating an S1000D_Catalog.prop file on the Contenta Web server, as explained in Configuring the Upload Content Tool to Use Local Entities.

Multi-language support

If multi-language support is enabled in AppData settings, Contenta S1000D allows you to upload content (DMs, PMs, and SCPMs) in multiple languages to a configuration or program/project. When you upload an object in a language other than the source language of the database, it is placed in a container one level down in the hierarchy from the source language version of the object. This container is labeled with a language-country combination derived from the values assigned to the object's languageIsoCode and countryIsoCode attributes, separated by a hyphen. For example, a DM in French would be uploaded to a folder labeled FR-FR. If the appropriate container does not exist before the object is uploaded, the tool creates it.

To enable multi-language support at the configuration or program/project level, the supportMultipleLanguages AppData setting must be set to yes. In addition, the sourceLanguageCountryCode AppData setting must be set to the appropriate language-country combination for the source language. The default value is EN-US, which denotes United States English. The applicable language-country combination is appended to the name of any module in a language other than the source language. The source language-country combination is appended to the names of objects in the source language only if the includeLanguageCountryCodeInSourceObjectNames AppData setting is set to yes.

For further information about enabling multi-language support, see Modifying AppData settings after installing or upgrading Contenta S1000D.

Uploading graphics

When uploading ICNs or other graphics, note the following:
  • Contenta S1000D does not support hyphens or dashes in the Standard Numbering System (SNS) field in the ICN. So, for example, ICN-SDLC-AN20000-N-61331-00002-A-01-1.jpg is a supported ICN file name structure, but ICN-SDLC-A-N2-00-00-N-61331-00002-A-01-1.jpg is not.
  • CAGE code-based ICN codes such as ICN-78286-00027-A01-01.tif are supported for uploading.
  • The Contenta S1000D database cannot contain two ICNs or other graphics if both have the same file name, but different file extensions. This is the case when the graphics have different formats (for example, photo1.bmp and photo1.cgm). This restriction results in the following S1000D Upload Content behavior.
    • If you try to upload a graphic while a graphic with the same name but a different file extension already exists, S1000D Upload Content displays an error message and prevents the upload.
    • If you try to upload two new graphics simultaneously from a list that have the same name but different file extensions, S1000D Upload Content uploads the first graphic but displays an error message for the second graphic and prevents its upload.

Uploading other types of files

When uploading Word, Excel, PowerPoint, and ZIP files, note the following:
  • Files with either .doc or .docx extensions will be uploaded into Word objects.

    The MIME Type property for .docx is set to application/vnd.openxmlformats-officedocument.wordprocessingml.document

    The MIME Type property for.doc is set to application/msword

  • Files with either .ppt or .pptx extensions will be uploaded into PowerPoint objects.

    The MIME Type property for .pptx is set to application/vnd.openxmlformats-officedocument.presentationml.presentation

    The MIME Type property for .ppt is set to application/vnd.ms-powerpoint

  • Files with either .xls or .xlsx extensions will be uploaded into Excel objects.

    The MIME Type property for .xlsx is set to application/vnd.openxmlformats-officedocument.spreadsheetml.sheet

    The MIME Type property for .xls is set to application/vnd.ms-excel

  • Files with a.zip extension will be uploaded into ZIP objects.

    The MIME Type property for .zip is set to application/zip

  • If you upload a file named abc.doc it will be uploaded into a Word object named abc. If you subsequently start to upload a file named abc.docx, Upload Content will recognize that the abc Word object already exists in the CSDB. If you have permission to overwrite existing data, you can specify to upload this object by checking the box in the first column.