IMP section in the INI file - Brainware for Transcripts - 24.1 - 24.1 - Ready - Brainware - external - Brainware/Brainware-for-Transcripts/24.1/Brainware-for-Transcripts-User-Guide/Configure-Brainware-for-Transcripts/INI-File-Configurations/IMP-section-in-the-INI-file - 2024-10-28

Brainware for Transcripts User Guide
Platform
Brainware
Product
Brainware for Transcripts
Release
24.1
License

This section contains settings revolving around document import, specifically the mapping of values contained within the image filename to fields in Intelligent Capture. This provides a simple means to pass data to Brainware for Transcripts from an upstream system.

Filename components are separated by an underscore, such as COMPONENT1.tif, COMPONENT1_COMPONENT2.tif, COMPONENT1_COMPONENT2_COMPONENT3.tif, and so on.

The values provided in the following IMP_VL components are included within the filename.

  • IMP_VL_URN=COMPONENT3

  • IMP_VL_BatchName=

  • IMP_VL_ScanDate=

  • IMP_VL_PriorityFlag=

  • IMP_VL_TranscriptType=

  • IMP_VL_DestinationArchive=

  • IMP_VL_InputSource=

  • IMP_VL_ClientID=

  • IMP_VL_LocationID=

  • IMP_VL_ApplicantID=COMPONENT1

  • IMP_VL_SiteID=

  • IMP_VL_InstitutionID=COMPONENT2

For example, IMP_VL_ScanDate=COMPONENT1 for the 12022008_1234_123456.tif file inserts 12022008 into the ScanDate field in Intelligent Capture.

Brainware for Transcripts also enables you to pre-define documents, based on the transcript type, using standardized auto-indexing values in the document filename. The auto-indexing configurations are as follows:

  • IMP_VL_CollegeTranscriptType=C

  • IMP_VL_HighSchoolTranscriptType=H

  • IMP_VL_MilitaryTranscriptType=M

In order to use this feature, you must first configure the TranscriptType field in the IMP section of the INI file. This enhancement eliminates any chances of classification errors by the automated classification process. Based on the indexes you provide in the filename of the document, the post-classification process re-classifies erroneously classified documents to the correct category.

For example, if the Auto-Index is College and the resulting classification is not college, then the classification will be set to College.If the Auto-Index is High School and the resulting classification is not High School, then the classification will be set to School.If the Auto-Index is Military and the resulting classification is not one of the supported military classes, then the classification will be set to Joint Services.

The following settings are available.

Parameter Type Description
URN Freetext This is the document unique reference number.
BatchName Freetext This is the document batch name.
ScanDate Freetext This is the document scan date.
PriorityFlag Freetext This is the document priority flag.
TranscriptType Freetext This is the document transcript type.
Note: You can use the auto-index feature to pre-classify college, high-school and military documents only if you have configured this field.
DestinationArchive Freetext This is the document destination archive.
InputSource Freetext This is the document input source, such as SCAN, EDI, and EMAIL.
ClientID Freetext This is the document client ID.

In a multi-client project, this value must be mapped. If not, the configuration set associated with client zero is used.
LocationID Freetext This is the document Location ID.

This field can be used to hold the operation location ID that is relevant for the document. For example, the ID of a shared service center.

The value contained within the filename is written into the Visibility reporting tables for that particular document to enable location level reporting.
ApplicantID Freetext This is the ApplicantID that can be pre-linked to a transcript before processing through BFT. This allows you to continue the transcripts receipt process while not stopping the documents in Verifier based on the ApplicantID ASE results.

  • If ApplicantID is mapped, the value mapped must exist in the ASE pool data.

  • If the mapped value does not exist in the ASE pool, or the component is not in the filename, the ApplicantID is extracted normally.
SiteID Freetext This is the applicant site ID assigned to the transcript if pre-linking is used with the implementation and a site ID is assigned to the applicant pool.

Mapping of applicant SiteID is not required if the implementation does not include an applicant SiteID.
InstitutionID Freetext This is the InstitutionID that can be pre-linked to a transcript before processing through BFT. This allows you to continue the transcripts receipt process while not stopping the documents in Verifier based on the InstitutionID ASE results.

  • If InstitutionID is mapped, the value mapped must exist in the ASE pool data.

  • If the mapped value does not exist in the ASE pool, or the component is not in the filename, the InstitutionID is extracted normally.
InstSiteID Freetext This is the InstSiteID assigned to the transcript if pre-linking is used with the implementation and a site ID is assigned to the institution pool.

Mapping of InstSiteID is not required if the implementation does not include InstSiteID.
ComponentSeperator Freetext This is the character used to segment the components of the document filename, for example, underscore (_).
Note: An underscore character “_” is the default component separator assigned in the INI file.
PriorityFlagYes Freetext This is the value that denotes a positive setting for the priority flag.
DateFormat Freetext This is the format of a date contained within the document filename. Options are DDMMYYYY, MMDDYYYY or YYYYMNDD.