Data Entry/ Data Indexing
Before indexing, we analyze the source input and the required fields. Accordingly, we design the indexing program for each project by extensive use of field validations including table.lookups, formulas, and data-type restrictions as the case may be. For example, this includes standard or custom check-digit formulas, city, state and zip code lookups from Postal Code tables, as well as any type of customer-specific data. This enables us in creation of indexes using one or more columns of a database table, providing the basis for both random look ups and efficient access of the ordered records.
The disk space required to store these index files is typically less than that required by the table (since indexes usually contain only the key-fields according to which the table is to be arranged, and all the other details are excluded from the table).This also enhances our ability to store indexes in the memory for a table whose data is too large to store in memory.
Forms Processing:
At PATELiinfo, data processing is done from various kinds of forms including examination forms, legal forms, questionnaires etc. It is done manually if the text is hand-written and via certain tools for printed text to automate the process. The output is indexed to generate a XSL or CSV file as the case may be. We have processed various forms like:
- Invoices
- Payroll
- Inventory Control
- Share Application
- Fixed Coupon Analysis
- Voter’s ID cards
- Survey and Market Research Data
- Medicals bills
- Insurance claims
- Bank account forms
- Challans
- Questionnaires
- University internship forms
- Schedule enumeration forms
- Shipping documents
- Examinations Processing
- Legal forms
- Patent rights form
- Government forms
Certain Quality Measures that we incorporate in our processes are:
| QA/ QC measures | Description |
| On-screen comparison of converted/ processed data from 2 different production pipes | Different production teams are used to process the same input data. QA staff is fed with the input data & the 2 different outputs to compare on-screen & take a decision. Many-a-times, specific tools are developed to provide comfortable simultaneous viewing options for the input & 2 outputs. |
| Printed proof-reading of sourced documents & processed output | If the conversion process permits, the input document & the processed output are printed on separate sets of paper. QA staff then ticks off the entire data character by character with notes on updation due to errors if any. Updation staff completes the process by modifying the output file where needed. |
| Use of software tools to check the integrity of the processed data | We have an in-house software team providing support in developing comparison, logic interdependency checking & data checksum tools which reads the output data & reveals any errors or inconsistency as per the logic programmed. These tools are particularly helpful checking metadata & the structure of such databases where different cells have a logical interdependency. |