Jump to content

Krista Schmidt

Moderators
  • Posts

    193
  • Joined

  • Days Won

    4

Krista Schmidt last won the day on April 28 2017

Krista Schmidt had the most liked content!

Krista Schmidt's Achievements

Enthusiast

Enthusiast (6/14)

30

Reputation

  1. Q: Can the Password Handling list in eCapture Case Settings be used to break protected files in a Streaming Discovery job? A: The Password Handling list will be utilized during the initial Streaming Discovery job. The passwords in the list will be attempted when the job is initially run to attempt to break passwords on archive files (zip, rar, etc…) as well as PDF and Office file types. If a password is not available for item level documents during the initial Streaming Discovery job, the documents (and their families) will be pushed into review as protected files. Q: After my Streaming Discovery job has finished, can I enter a password into the list and re-queue any password protected files? A: While password handling is a big focus for the ADD Processing team, after the initial Streaming Discovery job is completed, the password list currently can only be used to apply to re-queued archive files (ZIP, RAR, etc...). Passwords entered after the initial Streaming Discovery job has completed will not be applied during a re-queue of protected PDF or Office file types or containers. For non-archive containers, if a password is received after the initial Streaming Discovery job is completed, container (node) level files would have to be un-protected before being re-queued or submitted as a new job. In this case, Ipro generally recommends that users leave the errored container and create a separate job for the new un-protected container. This will maintain process proof and users can then enter notes of the process followed and the job name for the new file. Document (Item) level protected files could be resolved using the eCapture QC application to enter the password and push any additional data to Review. Q: If we do not have the password for a protected item level document, what results can we expect with the file in review? A: For password protected files, the processing system is generally able to extract all file system metadata. For certain files which are only partially protected, IE one tab in an Excel file has a password, we are able to get the majority if not all of the metadata from the file and even some of the text. If the file is saved in ‘Protected View’, the entire file contents may be extracted, but it may still be marked as protected. The results appearing in review will all be dependent upon the level of protection in the file itself.
  2. Q: Can the Password Handling list in eCapture Case Settings be used to break protected files in a Streaming Discovery job? A: The Password Handling list will be utilized during the initial Streaming Discovery job. The passwords in the list will be attempted when the job is initially run to attempt to break passwords on archive files (zip, rar, etc…) as well as PDF and Office file types. If a password is not available for item level documents during the initial Streaming Discovery job, the documents (and their families) will be pushed into review as protected files. Q: After my Streaming Discovery job has finished, can I enter a password into the list and re-queue any password protected files? A: While password handling is a big focus for the ADD Processing team, after the initial Streaming Discovery job is completed, the password list currently can only be used to apply to re-queued archive files (ZIP, RAR, etc...). Passwords entered after the initial Streaming Discovery job has completed will not be applied during a re-queue of protected PDF or Office file types or containers. For non-archive containers, if a password is received after the initial Streaming Discovery job is completed, container (node) level files would have to be un-protected before being re-queued or submitted as a new job. In this case, Ipro generally recommends that users leave the errored container and create a separate job for the new un-protected container. This will maintain process proof and users can then enter notes of the process followed and the job name for the new file. Document (Item) level protected files could be resolved using the eCapture QC application to enter the password and push any additional data to Review. Q: If we do not have the password for a protected item level document, what results can we expect with the file in review? A: For password protected files, the processing system is generally able to extract all file system metadata. For certain files which are only partially protected, IE one tab in an Excel file has a password, we are able to get the majority if not all of the metadata from the file and even some of the text. If the file is saved in ‘Protected View’, the entire file contents may be extracted, but it may still be marked as protected. The results appearing in review will all be dependent upon the level of protection in the file itself.
  3. Q: When the Publish Errors button is clicked, what is happening? Which files are then published that were originally held back? A: After the streaming discovery job is completed and the user has decided that no other exceptions can be resolved, they click on the Publish Errors button. Publish Errors will generate one final export job of all remaining error families which can be pushed to review. This would include the documents extracted from partially extracted containers, as well as document families which resulted in a Detect Container or Read Email Fields error. Example: A PST file is extracted that results in many emails, but contains a folder that was unable to be extracted. The PST would be identified as a node level error and all files extracted from the PST will be held back during initial processing. If a user is able to resolve the folder issue and re-queue the container successfully, then the results will be pushed to review automatically. If nothing is done to the container, when the user Publishes Errors, the successfully extracted documents and their families would be pushed to review. An MSG file was discovered with two attachments but resulted in a ‘Read Email Fields’ exception and the whole family was held back. When the user Publishes Errors, the MSG and its family will be promoted to review. Q: How can I resolve errors for containers or items which were not promoted to review? A: Errors encountered during processing would generally be resolved outside of the ADD Processing engine. Once the issue has been resolved, the exception can be re-queued using the ‘Modify Streaming Discovery Job’ button to resubmit the file for potential additional extraction. Keep in mind, users will want to review and resolve the file at the discovery location, not necessarily the original source location. Review the error report to find the location of the file with the error. Example: A Password protected PST file is identified. If a password has been provided, a user could un-protect the PST file and re-queue the exception. A PST file had issues extracting all content. The user could run a repair utility such as ScanPST on the PST. This may or may not repair the file and has the potential to change metadata for content, but it is utilized generally through approval from the end client. The container could then be re-queued. Q: How can the eCapture QC application be used with my Streaming Discovery job? A: Once a streaming discovery job has completed, it can be loaded in QC to review the results. Generally, it would be used to review exception flags. Users can then attempt to determine what might have caused the error and utilize the different reprocessing options such as forcing the document to use Stellent to process in order to attempt to get additional information from the file. If the documents were loaded directly to Eclipse, the results from a successfully reprocessed file in eCapture QC will automatically be updated in Eclipse, similar to the Enterprise Imaging function today. Successfully reprocessed files could result in additional metadata or text being loaded to Eclipse. Q: When an item level exception document is sent to Eclipse using the Publish Errors option, what can we expect the document to look like in Eclipse? A: Documents published to Eclipse will be flagged in the System QC Flags (Ipro Eclipse Template Field Name) field with ‘Streaming Discovery Errors Forced Through Export’. Documents in these families which did not have an issue will appear as normal. Documents which caused the family to be held back will also be flagged as an exception and will most likely only contain file system metadata depending on the error.
  4. Q: When the Publish Errors button is clicked, what is happening? Which files are then published that were originally held back? A: After the streaming discovery job is completed and the user has decided that no other exceptions can be resolved, they click on the Publish Errors button. Publish Errors will generate one final export job of all remaining error families which can be pushed to review. This would include the documents extracted from partially extracted containers, as well as document families which resulted in a Detect Container or Read Email Fields error. Example: A PST file is extracted that results in many emails, but contains a folder that was unable to be extracted. The PST would be identified as a node level error and all files extracted from the PST will be held back during initial processing. If a user is able to resolve the folder issue and re-queue the container successfully, then the results will be pushed to review automatically. If nothing is done to the container, when the user Publishes Errors, the successfully extracted documents and their families would be pushed to review. An MSG file was discovered with two attachments but resulted in a ‘Read Email Fields’ exception and the whole family was held back. When the user Publishes Errors, the MSG and its family will be promoted to review. Q: How can I resolve errors for containers or items which were not promoted to review? A: Errors encountered during processing would generally be resolved outside of the ADD Processing engine. Once the issue has been resolved, the exception can be re-queued using the ‘Modify Streaming Discovery Job’ button to resubmit the file for potential additional extraction. Keep in mind, users will want to review and resolve the file at the discovery location, not necessarily the original source location. Review the error report to find the location of the file with the error. Example: A Password protected PST file is identified. If a password has been provided, a user could un-protect the PST file and re-queue the exception. A PST file had issues extracting all content. The user could run a repair utility such as ScanPST on the PST. This may or may not repair the file and has the potential to change metadata for content, but it is utilized generally through approval from the end client. The container could then be re-queued. Q: How can the eCapture QC application be used with my Streaming Discovery job? A: Once a streaming discovery job has completed, it can be loaded in QC to review the results. Generally, it would be used to review exception flags. Users can then attempt to determine what might have caused the error and utilize the different reprocessing options such as forcing the document to use Stellent to process in order to attempt to get additional information from the file. If the documents were loaded directly to Eclipse, the results from a successfully reprocessed file in eCapture QC will automatically be updated in Eclipse, similar to the Enterprise Imaging function today. Successfully reprocessed files could result in additional metadata or text being loaded to Eclipse. Q: When an item level exception document is sent to Eclipse using the Publish Errors option, what can we expect the document to look like in Eclipse? A: Documents published to Eclipse will be flagged in the System QC Flags (Ipro Eclipse Template Field Name) field with ‘Streaming Discovery Errors Forced Through Export’. Documents in these families which did not have an issue will appear as normal. Documents which caused the family to be held back will also be flagged as an exception and will most likely only contain file system metadata depending on the error.
  5. While exploring some different options and some questions which have come up recently, I wanted to put together a Q&A to help assist with some common processing questions that we often receive. Q: With standard eCapture Discovery and Data Extract jobs, there is a Task Retry option for Data Extraction which can be configured to retry files multiple times before failing them as an exception, is this the case with Streaming Discovery jobs as well and does the same value apply? A: While this is the case for standard eCapture processing, for Streaming Discovery jobs, when a file fails processing, it will automatically fall back to standard eCapture Data Extraction to attempt the file. If the file does fall back to standard eCapture Data Extraction, at that point it will use the configured number of retries set for standard Data Extraction. Q: During the Streaming Discovery job, what types of errors are held back from being exported or pushed to Review during initial processing? A: During Streaming Discovery, Node level exceptions will cause the exception file and any corresponding family to be held back from being pushed to review. These Node level exceptions could be partially discovered containers, or containers which were unable to be discovered at all. Item level exceptions will be automatically pushed to review with the exception of ‘Detect Container’ errors and ‘Read Email Fields’ exceptions (as well as their families). As a general rule, any errors that result in files not being discovered or being discovered improperly will hold the files back. Examples: A PST file is extracted that results in many emails, but contains a folder that was unable to be extracted. The PST would be identified as a node level error and all files extracted from the PST will be held back during initial processing. If a user is able to resolve the folder issue and re-queue the container successfully, then all files will be pushed to review automatically. If nothing is done to the container, when the user Publishes Errors, the successfully extracted documents and their families would be pushed to review. A corrupt PST file is encountered and streaming discovery is unable to extract anything from it. The PST would be identified as a node level exception and no files will be pushed to review. If nothing is done to the container, when the user Publishes Errors, nothing will be pushed to review. A ZIP file is processed and some loose files are successfully processed but the ZIP file also contains an encrypted PST. The ZIP file is successfully extracted and the loose files are pushed to review. The PST is marked as a Node Level exception Q: What does the ‘Detect Container’ exception mean? A: The Detect Container error generally indicates that the processing engine believes the file is a container of some kind, but it wasn’t able to extract any children from it. Re-queuing these types of errors may be able to resolve the exception. Q: What does the ‘Read Email Fields’ exception mean? A: This exception generally means the processing engine was unable to extract one or more values that it is using for hash generation and therefore the document fails hash generation. This could potentially result in extra files being delivered if the missing fields resulted in the file not being de-duplicated. Re-queuing these types of errors may be able to resolve the exception. Q: What is the best way to review exception messages for my job? A: While the eCapture Controller UI will provide you with an error message for the selected error, reviewing the Detailed Error Report is the best way to get the exact error message resulting from the exception.
  6. While exploring some different options and some questions which have come up recently, I wanted to put together a Q&A to help assist with some common processing questions that we often receive. Q: With standard eCapture Discovery and Data Extract jobs, there is a Task Retry option for Data Extraction which can be configured to retry files multiple times before failing them as an exception, is this the case with Streaming Discovery jobs as well and does the same value apply? A: While this is the case for standard eCapture processing, for Streaming Discovery jobs, when a file fails processing, it will automatically fall back to standard eCapture Data Extraction to attempt the file. If the file does fall back to standard eCapture Data Extraction, at that point it will use the configured number of retries set for standard Data Extraction. Q: During the Streaming Discovery job, what types of errors are held back from being exported or pushed to Review during initial processing? A: During Streaming Discovery, Node level exceptions will cause the exception file and any corresponding family to be held back from being pushed to review. These Node level exceptions could be partially discovered containers, or containers which were unable to be discovered at all. Item level exceptions will be automatically pushed to review with the exception of ‘Detect Container’ errors and ‘Read Email Fields’ exceptions (as well as their families). As a general rule, any errors that result in files not being discovered or being discovered improperly will hold the files back. Examples: A PST file is extracted that results in many emails, but contains a folder that was unable to be extracted. The PST would be identified as a node level error and all files extracted from the PST will be held back during initial processing. If a user is able to resolve the folder issue and re-queue the container successfully, then all files will be pushed to review automatically. If nothing is done to the container, when the user Publishes Errors, the successfully extracted documents and their families would be pushed to review. A corrupt PST file is encountered and streaming discovery is unable to extract anything from it. The PST would be identified as a node level exception and no files will be pushed to review. If nothing is done to the container, when the user Publishes Errors, nothing will be pushed to review. A ZIP file is processed and some loose files are successfully processed but the ZIP file also contains an encrypted PST. The ZIP file is successfully extracted and the loose files are pushed to review. The PST is marked as a Node Level exception Q: What does the ‘Detect Container’ exception mean? A: The Detect Container error generally indicates that the processing engine believes the file is a container of some kind, but it wasn’t able to extract any children from it. Re-queuing these types of errors may be able to resolve the exception. Q: What does the ‘Read Email Fields’ exception mean? A: This exception generally means the processing engine was unable to extract one or more values that it is using for hash generation and therefore the document fails hash generation. This could potentially result in extra files being delivered if the missing fields resulted in the file not being de-duplicated. Re-queuing these types of errors may be able to resolve the exception. Q: What is the best way to review exception messages for my job? A: While the eCapture Controller UI will provide you with an error message for the selected error, reviewing the Detailed Error Report is the best way to get the exact error message resulting from the exception.
  7. The ADD Web case creation process makes creating ADD cases so much easier. With the built-in Ipro templates, some more experienced users who have created their own templates have been asking how they can switch out the default Ipro templates to use their own files by default. We are working to improve the template management process but in the meantime, you can replace the template Processing and Export Series INI files as well as the Review case CSE default file. Please be cautious about doing this and ensure that your new template files work as expected prior to replacing them!! The default files that the ADD Web case creation process uses are stored on the web server at the following location: C:\Program Files\Ipro Tech\Web\ADDServices\App_Data At that location you will see the three template files that ADD Web uses to create cases. To replace the files, make sure you use the exact same file names as the existing template files and feel free to copy or rename the existing ones in the event you would need to reference them at a later time.
  8. The ADD Web case creation process makes creating ADD cases so much easier. With the built-in Ipro templates, some more experienced users who have created their own templates have been asking how they can switch out the default Ipro templates to use their own files by default. We are working to improve the template management process but in the meantime, you can replace the template Processing and Export Series INI files as well as the Review case CSE default file. Please be cautious about doing this and ensure that your new template files work as expected prior to replacing them!! The default files that the ADD Web case creation process uses are stored on the web server at the following location: C:\Program Files\Ipro Tech\Web\ADDServices\App_Data At that location you will see the three template files that ADD Web uses to create cases. To replace the files, make sure you use the exact same file names as the existing template files and feel free to copy or rename the existing ones in the event you would need to reference them at a later time.
  9. The ADD Web case creation process makes creating ADD cases so much easier. With the built-in Ipro templates, some more experienced users who have created their own templates have been asking how they can switch out the default Ipro templates to use their own files by default. We are working to improve the template management process but in the meantime, you can replace the template Processing and Export Series INI files as well as the Review case CSE default file. Please be cautious about doing this and ensure that your new template files work as expected prior to replacing them!! The default files that the ADD Web case creation process uses are stored on the web server at the following location: C:\Program Files\Ipro Tech\Web\ADDServices\App_Data At that location you will see the three template files that ADD Web uses to create cases. To replace the files, make sure you use the exact same file names as the existing template files and feel free to copy or rename the existing ones in the event you would need to reference them at a later time.
  10. Hi! A screen shot of your settings might help, but when you selected your re-numbering for you files, did you select both Document and Page level numbering? If you would like the Page ID's to be sequential, as in, Empirical_00008441 followed by Empirical_00008442, you just want to set the Page level numbering. I have attached a screenshot in case that helps. Also, you can preview the imagekey at the bottom of the page if you aren't sure if you have it set up properly.
  11. Hi! A screen shot of your settings might help, but when you selected your re-numbering for you files, did you select both Document and Page level numbering? If you would like the Page ID's to be sequential, as in, Empirical_00008441 followed by Empirical_00008442, you just want to set the Page level numbering. I have attached a screenshot in case that helps. Also, you can preview the imagekey at the bottom of the page if you aren't sure if you have it set up properly.
  12. Hi! A screen shot of your settings might help, but when you selected your re-numbering for you files, did you select both Document and Page level numbering? If you would like the Page ID's to be sequential, as in, Empirical_00008441 followed by Empirical_00008442, you just want to set the Page level numbering. I have attached a screenshot in case that helps. Also, you can preview the imagekey at the bottom of the page if you aren't sure if you have it set up properly.
  13. Hi! A screen shot of your settings might help, but when you selected your re-numbering for you files, did you select both Document and Page level numbering? If you would like the Page ID's to be sequential, as in, Empirical_00008441 followed by Empirical_00008442, you just want to set the Page level numbering. I have attached a screenshot in case that helps. Also, you can preview the imagekey at the bottom of the page if you aren't sure if you have it set up properly.
  14. Hi! A screen shot of your settings might help, but when you selected your re-numbering for you files, did you select both Document and Page level numbering? If you would like the Page ID's to be sequential, as in, Empirical_00008441 followed by Empirical_00008442, you just want to set the Page level numbering. I have attached a screenshot in case that helps. Also, you can preview the imagekey at the bottom of the page if you aren't sure if you have it set up properly.
  15. Hi! A screen shot of your settings might help, but when you selected your re-numbering for you files, did you select both Document and Page level numbering? If you would like the Page ID's to be sequential, as in, Empirical_00008441 followed by Empirical_00008442, you just want to set the Page level numbering. I have attached a screenshot in case that helps. Also, you can preview the imagekey at the bottom of the page if you aren't sure if you have it set up properly.
×
×
  • Create New...