Creating a Splitting Map

Demo:

V_DS_837I_4010_ContentSplit1 in the Scripts directory of Instream
Content_Based_Split_Setup.ini in the DemoData directory of Instream

The purpose of this step is to specify the literal values that cause a split and to tell Docsplitter the filename for the split data.

Add a [Content Splitting Map] section to a setup file (see Setup File). List each custom split point and a corresponding filename:

FilenameEnd=Splitdata|Splitdata|…

You can define any number of files, each corresponding to one line in the [Content Splitting Map] section of the setup file. Fewer lines in this section will result in faster performance.

Example Content Splitting Map

[Content Splitting Map]
Anderson=111111111
BTownDamascus=222222222|444444444
Edwards.EDI=555555555

Anderson=111111111 specifies:

With this command-line
parameter …

Output files for data 111111111
will be …

-oi specified Provider_Invalid.txt

Provider_InvalidAnderson.txt

-ov specified  Provider_Valid.txt

Provider_ValidAnderson.txt

BTownDamascus=222222222|444444444 specifies:

With this command-line
parameter …

Output files for data 222222222 and 444444444 will be …

-oi specified Provider_Invalid.txt

Provider_InvalidBTownDamascus.txt

-ov specified  Provider_Valid.txt

Provider_ValidBTownDamascus.txt

Edwards.EDI=555555555 specifies:

With this command-line parameter …

Output files for data 555555555 will be …

-oi specified Provider_Invalid.txt

Provider_InvalidEdwards.EDI

-ov specified  Provider_Valid.txt

Provider_InvalidEdwards.EDI

Spaces in the Content Splitting Map

If your content data contains leading or trailing spaces, set up the lines this way in the content splitting map:

Anderson=111111111  |

Vertical bar after the trailing spaces

BTownDamascus=|  222222222|444444444

Vertical bar before the leading spaces