Overview of S1000D Upload
To upload S1000D codes and content from the file system into your Contenta S1000D CSDB, use the S1000D Upload tool. This topic provides information that you need to know before running the Upload tool.
- DMs
- PMs
- SCPMs
- graphics
- DMRLs (CSV files)
- Word
- Excel
- PowerPoint
- 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, except for DMRLs, which can only be uploaded into a configuration.
File too large to upload: FILENAMEwhere FILENAME is the name of the file you are attempting to upload.
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. 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' desktops in Contenta. Each module, graphic, Word, Excel, PowerPoint, and ZIP file may only exist in one place in the database, and users may only access data in the configurations that are on their 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.
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 SX-US, which denotes Simplified Technical English (ASD-STE100) (recommended in S1000D Issues 4.1 and later for English language content), and the United States. 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 in the Configuring SDL Contenta S1000D section of the Installing and Upgrading SDL Contenta S1000D documentation.
To upload files through your Web browser, you must have a version of the Java Runtime Environment (JRE) installed that is listed in the SDL Contenta S1000D Platform Requirements.
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.
xsi:noNamespaceSchemaLocation attribute of the <dmodule>, <pm> or <scormContentPackage> tag. If the version cannot be determined from this attribute, S1000D Upload displays:
S1000D Version: ?? After the well-formed check, it displays the following error message and prevents the module from being uploaded into the CSDB:
Version not found
Missing or invalid xsi:noNamespaceSchemaLocation attribute
S1000D Upload may run into problems resolving character entities because it cannot access the s1000d.org Web site. If so, configure S1000D Upload to look locally for entities by creating an S1000D_Catalog.prop file on the Contenta Web server, as explained in Configuring the Upload Tool to Use Local Entities.
SDL 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.jpgis a supported ICN file name structure, butICN-SDLC-A-N2-00-00-N-61331-00002-A-01-1.jpgis not.CAGE code-based ICN codes such as ICN-78286-00027-A01-01.tif are supported for uploading.
The SDL 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 behavior:
- If you try to upload a graphic while a graphic with the same name but a different file extension already exists, S1000D Upload 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 uploads the first graphic but displays an error message for the second graphic and prevents its upload.
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 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.
- The file name must start with the prefix
DRML_ - The file extension must be
.csv - Any leading zeroes must not have been stripped from the codes in the file.