TriDK XML Setup
The TriDK XML Setup tool can be used to modify the underlying database structure. It is under extreme caution and understanding of the Content Manager architecture that this tool should be used.
Before the TriDK XML Setup Tool was created, partners and system administrators had to make a change request to SDL if they wanted to customize the metadata model. SDL would then create SQL scripts that were executed for the database needing customization. The TriDK XML Setup Tool allows partners and system administrators to add, update, or remove customer specific metadata without interaction with Content Manager.
The active server pages (ASPs) that build the user interface still must be manually edited to synchronize them with the updated database organization. For example, if a field is added at the logical level of an illustration, this field has to be added to the ASP file.
Precautions
The functionality of TriDK XML Setup is very powerful and incorrect use can lead to irreparable damage to the database, therefore it is necessary for you to be familiar with Content Manager, its configuration and the underlying relational database before using the TriDK XML Setup tool. It is recommended to take a number of precautions in order to reduce the risk of data loss.
Content Manager architecture
The TriDK XML Setup tool directly interacts with the TriDK Data Layer. This is done by a command line tool which converts a database independent input XML file into a database dependent SQL scripts that are executed on the database.
Metadata
Metadata are a cornerstone of Content Manager and the following division can be made:
- Metadata required by Content Manager such as: ID, Status, Title, Author.
- Metadata required by TriDK such as: creationdate, cardtype, language.
- Customer specific metadata such as: TranslationDueDate, ManualType, DepartmentName which are used to customize the Content Manager application for a specific customer.