Jump to content

Allowed Password Protected Percentage


Diego Iannitelli

Recommended Posts

With archives, the files in the archive are password-protected, not the archive itself. You can have 3 protected and 7 unprotected files in the archive. eCapture/Streaming would be able to get the unprotected files out. If eCapture failed in all cases if it couldn’t get any files out, you’d never be able to process the 7 files we could get out. Hence the need for a fudge factor.

 

Our fudge factor is the Allowed Password Protected Percentage setting. We calculate the percentage of documents we couldn’t get and compare it to the setting. In the above example, 3 of 10 documents failed for a failure percentage of 30%. If the allowed setting is 25%, we’ll fail the node and not process any of the contents. If the allowed setting is 50% we won’t fail the node and continue to process the 7 files we could get.

 

When you set the allowed percentage to 100%, you’re telling eCapture/Streaming to never fail any archive nodes because we couldn’t extract any of the files due to them being password-protected.

Link to comment
Share on other sites

With archives, the files in the archive are password-protected, not the archive itself. You can have 3 protected and 7 unprotected files in the archive. eCapture/Streaming would be able to get the unprotected files out. If eCapture failed in all cases if it couldn’t get any files out, you’d never be able to process the 7 files we could get out. Hence the need for a fudge factor.

 

Our fudge factor is the Allowed Password Protected Percentage setting. We calculate the percentage of documents we couldn’t get and compare it to the setting. In the above example, 3 of 10 documents failed for a failure percentage of 30%. If the allowed setting is 25%, we’ll fail the node and not process any of the contents. If the allowed setting is 50% we won’t fail the node and continue to process the 7 files we could get.

 

When you set the allowed percentage to 100%, you’re telling eCapture/Streaming to never fail any archive nodes because we couldn’t extract any of the files due to them being password-protected.

Link to comment
Share on other sites

With archives, the files in the archive are password-protected, not the archive itself. You can have 3 protected and 7 unprotected files in the archive. eCapture/Streaming would be able to get the unprotected files out. If eCapture failed in all cases if it couldn’t get any files out, you’d never be able to process the 7 files we could get out. Hence the need for a fudge factor.

 

Our fudge factor is the Allowed Password Protected Percentage setting. We calculate the percentage of documents we couldn’t get and compare it to the setting. In the above example, 3 of 10 documents failed for a failure percentage of 30%. If the allowed setting is 25%, we’ll fail the node and not process any of the contents. If the allowed setting is 50% we won’t fail the node and continue to process the 7 files we could get.

 

When you set the allowed percentage to 100%, you’re telling eCapture/Streaming to never fail any archive nodes because we couldn’t extract any of the files due to them being password-protected.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...