The migration process imports validated existing documents into SCHEMA ST4 in order to quickly populate and take advantage of the content management system. RTF data and formatted Word or Framemaker files can be imported without difficulties. Scriptor first checks the prerequisites: Are the formats consistent or do the source documents need preparatory work?
If an automated import is not possible, manual import remains an option. Modular structures are used to maximise the degree of reuse. All text and graphic modules (resources) are identified during the migration by metadata so that they are available for all future publications.
Migrating master data
Migration is the automated or manual transfer of texts and graphics into SCHEMA ST4’s information and resource pools. The structures that have been created must be maintained and the modules must be assigned metadata to make them discoverable. This is the actual core of the migration, and is often supplemented by additional authoring services. The simplest service is to create a project to obtain a publication corresponding to the source document.
More far-reaching are the restructuring and reformulating of content (e.g. using variables to replace product names to maintain product-independent documentation). Depending on the existing template structures in SCHEMA ST4, the contents of the modules may have to be re-sorted and more finely granulated. New company standards, spellings or content changes and additions in the course of product updates can also lead to revisions within the scope of a data migration.
Migrating translations
The migration of translated text makes sense when the normal export of master data and subsequent translation is out of the question. The translations are usually copied manually into the structures of the master data project. The language-specific settings are then made in SCHEMA ST4. This is a quick, straightforward solution for transferring validated data.
Migrating master data
Migration is the automated or manual transfer of texts and graphics into SCHEMA ST4’s information and resource pools. The structures that have been created must be maintained and the modules must be assigned metadata to make them discoverable. This is the actual core of the migration, and is often supplemented by additional authoring services. The simplest service is to create a project to obtain a publication corresponding to the source document.
More far-reaching are the restructuring and reformulating of content (e.g. using variables to replace product names to maintain product-independent documentation). Depending on the existing template structures in SCHEMA ST4, the contents of the modules may have to be re-sorted and more finely granulated. New company standards, spellings or content changes and additions in the course of product updates can also lead to revisions within the scope of a data migration.
Migrating translations
The migration of translated text makes sense when the normal export of master data and subsequent translation is out of the question. The translations are usually copied manually into the structures of the master data project. The language-specific settings are then made in SCHEMA ST4. This is a quick, straightforward solution for transferring validated data.
Scriptor highlights
- Migrating data into existing structures
- Migrating and creating structures
- Migrating and publishing on our customers
Scriptor highlights
- Migrating data into existing structures
- Migrating and creating structures
- Migrating and publishing on our customers
Your advantages
- Fill your system
- Transfer existing text instead of authoring
- Reuse after migration
- Revise the contents after migration
Your advantages
- Fill your system
- Transfer existing text instead of authoring
- Reuse after migration
- Revise the contents after migration
Address
Scriptor
Dokumentations Service GmbH
Krackser Strasse 12c
33659 Bielefeld
Germany
Tel: +49 521 950220
Fax: +49 521 9502225
e-mail: info@scriptor.de
Contact
Heike Hettwer
+ 49 521 950220