What’s New In Transact 4.5?
Machine Learning | Machine Learning Classification and Extraction Roles
In previous versions of Transact, the administrator managed permissions for machine learning classification and machine learning extraction using a single configuration on the Document Types screen. The required roles were selected from the column “Roles of Machine Learning” and were applied to both machine learning classification and extraction.
In Ephesoft Transact v188.8.131.52, machine learning classification and extraction are handled separately. Two columns called “Classification Roles” and “Extraction Roles” have been added to the Document Types screen. Now, the administrator can separately assign the roles to perform machine learning classification and machine learning extraction. This feature is available in both Windows and Linux environments.
Roles selected for a Batch Class on the Batch Class Management screen are inherited by the Document Types added under this Batch Class. You can then edit the default roles populated for Classification and Extraction as required on the Document Types screen.
Note: When the Batch Class is copied, all the roles defined at the Batch Class level and the Document Type level will be copied as well.
When the Batch Class is exported, all the information about defined roles will be exported as well.
When the Batch Class is imported, you can select whether to import it with or without defined roles using the checkbox “Roles” in the Import Batch Class popup window. If you select this checkbox, the Batch Class will be imported along with the roles. In this case, Batch Class roles will be inherited by the Document Types as well. If you leave the checkbox unselected, the Batch Class will be imported without roles.
In the case of Document Type, the assigned roles for Classification and Extraction are also copied, imported, and exported.
To assign roles for machine learning classification and extraction, the administrator will make the following configurations:
- Create a Batch Class and select required Roles from the Roles dropdown on the Batch Class Management screen.
- Navigate to the Extraction module, add the MACHINE_LEARNING_BASED_EXTRACTON plugin and turn on the Machine Learning Based Extraction Switch.
- Navigate to the Document Types screen and create a new Document Type. The Classification and Extraction Roles fields are automatically populated with the Roles assigned at the Batch Class level on the Batch Class Management screen.
- Change Classification and Extraction Roles as required.
Now, let us consider several scenarios where:
- Different Roles are assigned for machine learning classification and extraction
- The same Roles are assigned for machine learning classification and extraction
- Roles are assigned at the Document Type level, but no roles are assigned at the Batch Class level
1. Different Roles assigned for machine learning classification and extraction
Suppose there are three Roles configured in the application (Role1, Role2, and Role3) and the administrator assigns only Role1 and Role2 at the Batch Class level.
In this case, the user with Role3 won’t be able to see the Batch Class or the batch instances of that Batch Class unless there is a custom script running which gives him permission to work with a specific batch or Batch Class.
Let’s suppose the administrator has assigned Role1 for classification and Role2 for extraction at the Document Type level.
In this case, the user with Role2 will not be able to perform classification and the user with Role1 will not be able to perform validation. However, both the users can view the batch instance in the Review and Validate states.
Note that all the users assigned at the Batch Class level can upload the batch and only the user with permission “classification/extraction” can perform the operation. This is completely dependent on the roles.
Based on the above configurations, let us now log in as an operator with Role1 and Role2 and verify the results.
Log in as the user with Role1 and upload a batch.
Select the Batch Class and upload the batch by clicking on the Select Files hyperlink.
Click on the Start Batch button to initiate the batch processing workflow.
Go to the Batch List. The uploaded batch instance will appear in the Review state if the classification is not performed properly.
Note: If the classification is executed properly, the batch instance will directly go into the Validation state. The batch instance will be stuck on the validation screen if you have applied Force Review or if any of the index fields are not extracted properly.
If the classification is not performed properly, the user with Role1 must perform machine learning to re-learn the documents.
Select the Document Type for which you want to process the document.
Click on Learn Files from the More dropdown.
Assign First, Middle or Last Pages (if required) and click on the Learn Files button to confirm the machine learning.
The document is re-learned and if the user processes the same document again, the document will be classified into the defined Document Type.
Suppose this batch also requires machine learning extraction as some of the index fields are not extracted properly. In this case, the status of the batch changes to Ready for Validation and now the user can see it in the Validation section of the Batch List screen.
If the user with Role1 tries to proceed with extraction, he will see the message “Machine Learning of a document is not allowed for Current User” as he has the permission to do only machine learning classification of the document.
Now, log in as a user with Role 2 and navigate to the Batch List screen. The batch instance created by the user with Role1 is now ready for validation.
Proceed to the Validation screen and perform machine learning extraction.
If required, machine learning can be used for table extraction as well.
Click on the Validate button and confirm that validation has been completed.
The index fields are re-learned and the batch is processed. If the user processes the same document again, the values will be successfully extracted.
If the user with Role2 tries to do machine learning classification for any batch instance of this Batch Class, he will be able to proceed to the Review screen. However, his ability to classify the document will be restricted per the rules set up at the Document Type level. When he clicks on the Review button, he will receive the message “Machine Learning of a document is not allowed for Current User”.
This way, the administrator can assign roles separately for machine learning classification and extraction at the Document Type level.
2. Same Roles assigned for machine learning classification and extraction
Let’s assume that the administrator assigns the same roles (Role1 and Role2) for both operations – machine learning classification and extraction.
In this case, both users will be able to perform machine learning classification and extraction.
3. Roles assigned at the Document Type level, but no roles assigned at the Batch Class level
Suppose the administrator does not assign any role for a Batch Class on the Batch Class Management screen.
However, at the Document Type level he assigns Role1 and Role2 for both classification and extraction.
In this case, when users with Role1 and Role2 try to upload a batch on the Upload Batch screen, they will not see that particular Batch Class (in our example, it is BCF – ML_roles) in the dropdown list in the top panel. They will only see Batch Classes that have been assigned to them at the Batch Class Management screen.
Users with Role1 and Role2 will also not be able to work with batch instances created under this Batch Class and will not see them on the Batch List screen, unless a custom script is deployed giving them permission to perform machine learning for a particular batch.