Skip to content
Tx Platform
Config String Builder { id="config" }

Config String Builder🔗︎

This feature is deprecated and not available for new use.

The Parser is highly configurable to meet your needs, but by default, is configured to parse in a way that meets most users' needs. The SaaS service is stateless allowing the Parser to be configured completely differently for each transaction.

Parser Output Settings🔗︎

Stripping Out Reported Data from Jobs🔗︎

By default, the Positions/Description field includes the descriptive text that is related to a particular Position, but not including the portion which contains the title, company, location and date. If you want the Description field to have all of the text associated with a position, including the parsed data points, then set this option to false.

See below that the default behavior strips this text from the “Description” node:

Technical Difference        October 2004 - Current
Director of Web Applications Development

While this works well for most resumes, it can cause problems with some resumes that do not have all the data points together. Some data may be buried far away from other data, or at the end of the description, and in such cases, more data will be stripped out than expected, leaving an incomplete Description.

Strip Parsed Data🔗︎

OutputFormat.StripParsedDataFromPositionHistoryDescription = true - Default Value

"EmploymentHistory": {
    "Positions": [
        {
        "Id": "POS-1",
        "IsCurrent": true,
        ...,
        "Description": "• Add new technology to website to manage leads, increase response time and provide pertinent information to new customers. • Convert current HRIS from VB to ASP to create complete web based solution.\r\n• Added custom encryption coding to SQL and ASP web applications. • Designed custom applicant tracking ASP program for large client. • Designed customer support application to receive requests/files from clients, divert to appropriate support staff, and track issue from open to resolve.",
        }
    ]
}  
Include Parsed Data🔗︎

OutputFormat.StripParsedDataFromPositionHistoryDescription = false

"EmploymentHistory": {
    "Positions": [
        {
        "Id": "POS-1",
        "IsCurrent": true,
        ...,
        "Description": "Technical Difference Solana Beach, California\tOctober 2004 - Current Director of Web Applications Development • Add new technology to website to manage leads, increase response time and provide pertinent information to new customers. • Convert current HRIS from VB to ASP to create complete web based solution. • Added custom encryption coding to SQL and ASP web applications. • Designed custom applicant tracking ASP program for large client. • Designed customer support application to receive requests/files from clients, divert to appropriate support staff, and track issue from open to resolve.",
        }
    ]
} 

Reformat Position Description🔗︎

By default, the Position/Description element retains as much of the original formatting as possible. For example:

• Add new technology to website to manage leads, increase response time and provide pertinent information to new customers.
• Convert current HRIS from VB to ASP to create complete web based solution.
• Added custom encryption coding to SQL and ASP web applications.
• Designed custom applicant tracking ASP program for large client.
• Designed customer support application to receive requests/files from clients, divert to appropriate support staff, and track issue from open to resolve.

When this settings is enabled (OutputFormat.ReformatPositionHistoryDescription = True) the Parser will remove blank lines, split long paragraphs into separate lines, and other reformatting techniques intended to place each achievement on a separate line. Example:

Add new technology to website to manage leads, increase response time and provide pertinent information to new customers.

Convert current HRIS from VB to ASP to create complete web based solution.

Added custom encryption coding to SQL and ASP web applications.

Designed custom applicant tracking ASP program for large client.

Designed customer support application to receive requests/files from clients, divert to appropriate support staff, and track issue from open to resolve.

Create Bullets🔗︎

When OutputFormat.CreateBullets = true in the config string, the output will include a "bullet" based interpretation of the Description text in which each significant sentence/line/paragraph is reported as a separate element. This can be useful when transforming the output into a standard resume document format and you want each major point to be a bullet.

The Type attribute of each Bullet is one of the following values:

  • creativeTerm: Bullet text contains one of the phrases from the CREATIVE_ACTION_WORDS data list (such as “implemented”, “initiated”, and “developer on”).
  • sentence: This is the default when the type is not creativeTerm.

Here is an example of the output with this feature turned on:

"Positions": [
    {
        "Id": "POS-1",
        ...,
        "Bullets": [
            {
                "Type": "creativeTerm",
                "Text": "Managed email marketing campaigns to attract new sales and retain customers"
            },
            {
                "Type": "sentence",
                "Text": "Add new technology to website to manage leads, increase response time and provide pertinent information to new customers"
            },
            {
                "Type": "sentence",
                "Text": "Convert current HRIS from VB to ASP to create complete web based solution"
            },
            {
                "Type": "sentence",
                "Text": "Added custom encryption coding to SQL and ASP web applications"
            },
            {
                "Type": "creativeTerm",
                "Text": "Designed custom applicant tracking ASP program for large client"
            },
            {
                "Type": "creativeTerm",
                "Text": "Designed customer support application to receive requests/files from clients, divert to appropriate support staff, and track issue from open to resolve"
            }
        ]
    }
]

Normalize Regions🔗︎

By default, the Parser reports the Region as it was detected in the document. When this setting is turned on ( OutputFormat.NormalizeRegions = True), the parser normalizes Region values to the standard postal abbreviations. For example, 'Texas' to 'TX'. This setting currently only applies to US states and Canadian provinces.

Prefer Shorter Position Titles🔗︎

By default, this setting is turned off and the parser reports position titles exactly as they are found in the document. When true (OutputFormat.PreferShorterPositionTitles = True), titles may be truncated if the additional phrase does not include Job words. For example, VICE PRESIDENT, INFORMATION SYSTEMS would be reported as just VICE PRESIDENT if this switch is set to true.

Additional Settings🔗︎

Languages & Locales🔗︎

The Parser includes a language and locale analyzer that is able to accurately detect all supported Parser languages and can detect and set most supported locales based on an analysis of language, phone numbers, and email addresses. It is NEVER necessary or advisable to manually override the Parser's language detection, and it is rarely advisable to override the Parser's locale detection.

For a listing of languages and regions supported, you can refer to technical specs.

So, when might it be advisable to override the default locale detection? In some cases, you may be certain that you are parsing a CV from a particular locale and you want to ensure that the Parser "knows" about that locale even if the CV does not have any information on it that would readily tell it that it is from that locale (for example, if the CV contains no contact info).

Here is an example: if you are processing CVs in or from Australia, Australia uses a four-digit postal code. You may desire to set Culture.DefaultCountryCode = AU in the config string. This will give better results on a few Australian CVs that lack enough contact info for the Parser to detect that the CV contains Australian locale data. HOWEVER, a side effect is that, when that switch is "on" and a non-Australian CV is parsed, the Parser may erroneously report Australian contact info rather than the correct locale's contact info. For instance:

John Smith
Suite 404
3017 Sydney
Dallas, TX 75225

This is actually a USA address, and will possibly be reported by the Parser as being an address in postal code 3017 in Sydney, Australia rather than at 3017 Sydney Street in Dallas, Texas, USA in postal code 75225.

Our general recommendation is that only the following locale switches are advisable to set "on", and then only when the CV is almost certain to contain that locale’s data:

  • Set Culture.DefaultCountryCode = IN if you are parsing in India
  • Set Culture.DefaultCountryCode = AU if parsing in Australia or New Zealand (you can use either AU or NZ) and you have Australian or New Zealand locale CVs
  • Set Culture.DefaultCountryCode = ZA if you are parsing in South Africa

Again, setting these switches assumes that you really have a CV flow that is almost completely from those regions.