Rationalize the Columns used within Zingg

[navinrathore]

Z Columns Zingg uses the few internal columns to store internal and intermediate data

Describe the solution you'd like As of now, things work fine as expected. However, it is prudent to revisit the same that are used in different phases or different steps in product lifecycle.

Additional context Some of the points that need to be considered

• What columns should be part of written records (Marked/unmarked) data
• Exported data to be used as training samples
• externally training supplied samples
• Match output
• Use in different phases e.g Match vs link
• Columns of stop words file