Launch phase I of the publishing process, export the files
When you publish, files are exported to the server and prepared for the publishing in the requested format. There are several steps to this process.
When you click publish:
- Missing translations are exported in case of supplied fallback language for topics, maps, images, and library topics. If not supplied, an error object is exported instead.
- Variables are resolved.
- The topics and maps are filtered to match the context of the publication.
- The background process is triggered for an export of the publication to $\InfoShare\Data\publishingservice\Data\DataExports. The following graphic represents the folder structures used during publishing.
The export of publication is done on the server. The process includes:
- Determination of which versions to export (baseline report).
- Exporting of the data in blocks (50 items) to the file system.
- Validation and building the report file.
- Identification of differences with previous version if requested.
- Save of the job specification file.
- Filtering of conditional text.
- DTD System IDs are resolved.
- Variables are resolved.
The following items are exported:- All referenced objects are exported together with their metadata.
- Versions are selected according to the baseline (or autocomplete mode).
- Language(s) that are request (and possible fallback).
- Required image resolution as specified on the chosen OutputFormat (or fallback resolution).
- OutputFormat metadata.
- An export report.
- A job ticket.
- An event data xml file.
Example: Event Log, EXPORTFORPUBLICATION
For additional information about an event, click on the event. In the graphic below, the second event was clicked (highlighted in blue). The information below the grey bar shows additional information about that event.