• State Suggested Answer
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 139 subscribers
  • Views 4152 views
  • Users 0 members are here
Options
Related

Content Importer configuration file for TD14

Naoki Hirai

The file 'Trisoft.ContentImporter.config' exists in the AppData folder for each user. There are some processing parameters in this file. I'd like to know about the 'validateReferences' parameter. The default setting is as follows:

  <validateReferences>Error</validateReferences>

I think by this default setting, if Content Importer detects link error in maps or topics, those files would not be imported. Is this correct?

In addition, are there any alternative settings for the 'validateReferences' parameter?

If there are alternative settings, please let us know those alternatives with the outcomes.

Kind regards,

Naoki
Rate translation
×
Suggest better translation
×
Parents
  • 0

    Hi Naoki,

    In general you are right. The idea is to avoid "garbage in" because that in turn usually results in issues and essentially "garbage out". Main idea is described on TD14SP1 - Preparing DITA content for conversion and import

    Slightly more technical, engineering sometimes adds flags to allow debugging situations or bypassing certain issues. The configuration permutations that make sense for the wider audience are typically documented and in turn tested.

    Your flag is not documented on TD14SP1 - Trisoft.ContentImporter.config which makes me believe it is an engineering edge case. Looking at the value "Error", I can imagine that there would be a "Warning" or "Info" flavor. Then again that is a technical prediction, the main question is: Why would you need this to behave differently, because there could be side effects if you lower the incoming data quality?

    Hope this helps,
    Best wishes,
    Dave
  • 0 in reply to Dave De Meyer

    Hi Dave,

    I interested in this parameter because:

    In our company, we sometime duplicate a publication after translating it. Because the content of the document varies depending on the product destination and it's difficult to manage those differences completely by using conditions and variables. In this case, though we duplicate maps and topics, same illustrations are used by duplicated topics. To achieve this importing scenario, we need to import topics that refer to illustrations using GUID. However, Standard import of Content Importer refuses topics that have broken links in the file system.

    Kind regards,

    Naoki
Reply
  • 0 in reply to Dave De Meyer

    Hi Dave,

    I interested in this parameter because:

    In our company, we sometime duplicate a publication after translating it. Because the content of the document varies depending on the product destination and it's difficult to manage those differences completely by using conditions and variables. In this case, though we duplicate maps and topics, same illustrations are used by duplicated topics. To achieve this importing scenario, we need to import topics that refer to illustrations using GUID. However, Standard import of Content Importer refuses topics that have broken links in the file system.

    Kind regards,

    Naoki
Children
No Data