Jump to content

Michael Hadder

Escalation Engineer
  • Posts

    48
  • Joined

  • Days Won

    3

Everything posted by Michael Hadder

  1. Trial Director 6 can accept a large range of files, but I am intrigued that a MP4 files didn't work, as these are supported. How are you trying to use the MP4 and where specifically is it failing to play properly?
  2. Can you elaborate more on what you mean by Dynamic De-duplication and how it differs from standard deduplication?
  3. The recent TrialDirector Update is a patch for a Windows Update coming this Spring, and contained no bug fixes or feature enhancements. It is just designed to be compatible with Windows Operating Systems after this update. This does not mean that we aren't working on improving TrialDirector, just that we wanted to get a quick patch out to prevent issues with Windows 10 and Trial Director in the coming months.
  4. If you are ever in the situation where you need to pause a job for some reason, then you should know the possible impact this could create with deduplication. In general, pausing a job will not impact anything with the job, but this can change depending on other jobs that are running or will be run. Here is an example of something that can happen: We start a job called Job A. Then we pause Job A and start another job (Job B) in the same custodian. We are de-duplicating at the custodian level. Let's say Job A has processed 10 files before it was paused, one of those files was found in Job B > Job B will list the item as a duplicate of the item in Job A. Let's let Job B finish and unpause Job A and let it finish The last item in Job A was a duplicate of an item in Job B > Job A will deduplicate it out, keeping the item from Job B In this case both jobs have an item that was deduplicated from the other. Whichever job discovers the item first will be the reference, and all other jobs will mark their items as duplicates, even if one job finishes before the other or if a job is paused. Let's go over another scenario: Let's start Job A and let it get though the same 10 documents again, then pause it Now we will start Job B and let it finish. One of Job B's items is a duplicate of one of the items in Job A that is done with processing, and gets deduplicated Now we delete Job A. What happens to the item in Job B? It still is marked as a duplicate, and will still be deduplicated. Now we are in a problem where an item is getting marked as a duplicate despite the original job being deleted. Normally if we delete Job A before starting Job B, this wouldn't cause a problem, but because the jobs were active at the same time, the jobs are now "linked" by their duplicate items, and deleting one job means potentially re-running the other.
  5. From time to time we get requests on assisting with moving an authorization server. There are many reasons why someone might want to do this, but if you forget to do some small steps, it will result in having to call Ipro Support to clear everything for you before you can reauthorize. This also affects moving serial numbers for Classic products between machines as well. So to help make things easier the next time you need to move your authorization, here is how to do it without needing to call in. Online Authorizations On the ORIGINAL authorization machine, open the Ipro Auth Manager. Note for eScan-IT and Copy+ this can be accessed manually by going to the install location Click on Authorization Management > Remote Management > Deactivate Install the Ipro Auth Manager on your NEW authorization machine and input your ClientID and Serial number from the other machine. If it is already installed, click on Authorization Management > Remote Management > Activate Ensure your get a Valid status in your Auth Manager Offline Authorizations Install the Ipro Auth Manager on your NEW authorization machine and input your ClientID and Serial number from the other machine. Open the Ipro Auth Manager on the NEW machine Click on Authorization Management > DAT Management > Export Save the DAT file somewhere on your computer Email CSR@Iprotech.com with that DAT file and request for it to be authorized. You should receive a new DAT file from them Go back to the Ipro Auth Manager and click Authorization Management > DAT Management > Import Select the new DAT file you received from CSR@iprotech.com Ensure you see the Valid status in your Auth Manager For dongle users, the only thing to remember is to move the dongle from the old machine to the new machine. If you for whatever reason can no longer access the Ipro Auth Manager from the ORIGINAL machine and you are using an online authorization, please contact Ipro Technical Support to have us clear your account manually on our end so you can reauthorize on the new machine.
  6. From time to time we get requests on assisting with moving an authorization server. There are many reasons why someone might want to do this, but if you forget to do some small steps, it will result in having to call Ipro Support to clear everything for you before you can reauthorize. This also affects moving serial numbers for Classic products between machines as well. So to help make things easier the next time you need to move your authorization, here is how to do it without needing to call in. Online Authorizations On the ORIGINAL authorization machine, open the Ipro Auth Manager. Note for eScan-IT and Copy+ this can be accessed manually by going to the install location Click on Authorization Management > Remote Management > Deactivate Install the Ipro Auth Manager on your NEW authorization machine and input your ClientID and Serial number from the other machine. If it is already installed, click on Authorization Management > Remote Management > Activate Ensure your get a Valid status in your Auth Manager [ATTACH=CONFIG]n2686[/ATTACH] Offline Authorizations Install the Ipro Auth Manager on your NEW authorization machine and input your ClientID and Serial number from the other machine. Open the Ipro Auth Manager on the NEW machine Click on Authorization Management > DAT Management > Export Save the DAT file somewhere on your computer Email CSR@Iprotech.com with that DAT file and request for it to be authorized. You should receive a new DAT file from them Go back to the Ipro Auth Manager and click Authorization Management > DAT Management > Import Select the new DAT file you received from CSR@iprotech.com Ensure you see the Valid status in your Auth Manager [ATTACH=CONFIG]n2685[/ATTACH] For dongle users, the only thing to remember is to move the dongle from the old machine to the new machine. If you for whatever reason can no longer access the Ipro Auth Manager from the ORIGINAL machine and you are using an online authorization, please contact Ipro Technical Support to have us clear your account manually on our end so you can reauthorize on the new machine.
  7. From time to time we get requests on assisting with moving an authorization server. There are many reasons why someone might want to do this, but if you forget to do some small steps, it will result in having to call Ipro Support to clear everything for you before you can reauthorize. This also affects moving serial numbers for Classic products between machines as well. So to help make things easier the next time you need to move your authorization, here is how to do it without needing to call in. Online Authorizations On the ORIGINAL authorization machine, open the Ipro Auth Manager. Note for eScan-IT and Copy+ this can be accessed manually by going to the install location Click on Authorization Management > Remote Management > Deactivate Install the Ipro Auth Manager on your NEW authorization machine and input your ClientID and Serial number from the other machine. If it is already installed, click on Authorization Management > Remote Management > Activate Ensure your get a Valid status in your Auth Manager [ATTACH=CONFIG]n2686[/ATTACH] Offline Authorizations Install the Ipro Auth Manager on your NEW authorization machine and input your ClientID and Serial number from the other machine. Open the Ipro Auth Manager on the NEW machine Click on Authorization Management > DAT Management > Export Save the DAT file somewhere on your computer Email CSR@Iprotech.com with that DAT file and request for it to be authorized. You should receive a new DAT file from them Go back to the Ipro Auth Manager and click Authorization Management > DAT Management > Import Select the new DAT file you received from CSR@iprotech.com Ensure you see the Valid status in your Auth Manager [ATTACH=CONFIG]n2685[/ATTACH] For dongle users, the only thing to remember is to move the dongle from the old machine to the new machine. If you for whatever reason can no longer access the Ipro Auth Manager from the ORIGINAL machine and you are using an online authorization, please contact Ipro Technical Support to have us clear your account manually on our end so you can reauthorize on the new machine.
  8. The official list of files that eScan-IT supports can be found starting on page 256 of the latest eScan-IT user guide, which I will attach to this post. Note that given the option, we always recommend to process files through eCapture when given the choice between eCapture and eScan-IT.
  9. The official list of files that eScan-IT supports can be found starting on page 256 of the latest eScan-IT user guide, which I will attach to this post. Note that given the option, we always recommend to process files through eCapture when given the choice between eCapture and eScan-IT. Ipro eScan-IT 2017.0.3 User Guide.pdf
  10. I was working with a client earlier today who wanted to do some post processing in Copy+. Specifically they wanted to add in document boundaries to split up documents and folders. Normally the method you would use to apply boundaries would be to use the Display Bindings button, but this only applies to the next scanned document and not the document you currently are looking at. To apply a new boundary to the document of your choice, first you must ensure that the page you want to apply it to is a loose document or staple document. [ATTACH=CONFIG]n2197[/ATTACH] Bindings cannot be applied to images marked as pages. Then you will want to click on the modify button while Image is selected. It should look like this: [ATTACH=CONFIG]n2195[/ATTACH] You should see the following screen: [ATTACH=CONFIG]n2196[/ATTACH] If you see another screen, then you are not looking at the first page of a document or it is not set to be the first page of a document. From this menu click on bindings and you will be able to apply the bindings you would like!
  11. I was working with a client earlier today who wanted to do some post processing in Copy+. Specifically they wanted to add in document boundaries to split up documents and folders. Normally the method you would use to apply boundaries would be to use the Display Bindings button, but this only applies to the next scanned document and not the document you currently are looking at. To apply a new boundary to the document of your choice, first you must ensure that the page you want to apply it to is a loose document or staple document. Bindings cannot be applied to images marked as pages. Then you will want to click on the modify button while Image is selected. It should look like this: You should see the following screen: If you see another screen, then you are not looking at the first page of a document or it is not set to be the first page of a document. From this menu click on bindings and you will be able to apply the bindings you would like!
  12. If you ever run into an issue where you try to run a production or export only to have Eclipse tell you "there was an error starting the job" there are a few things to check. 1. Ensure that the Ipro Integration Service is running on the eCapture machine that is hosting it (usually the main controller machine and Queue Manager machine, but double check environmental documentation to be sure). This service is what bridges Eclipse and eCapture, and is essential for running productions and exports our of Eclipse. 2. Check the Controller and Queue Manager logs. One of them will most likely report another error message that should help identify why staging has failed. 3. If the service is running and eCapture is not reporting any errors, then try recycling the Application pools for both ADD and Eclipse in IIS. To confirm that this works you will need to re-create the job or make a copy of it, but this can sometimes prevent the issue as well. As always the best place for getting error messages for production is going to be the eCapture logs, but sometimes the error can be picked up in the ReviewAdmin.ExceptionLog in the Eclipse Config database in SQL as well. Make sure to check them both to help pinpoint the exact error that is causing staging to fail. Note that these jobs will need to be removed manually from SQL afterwards, or can be ignored.
  13. If you ever run into an issue where you try to run a production or export only to have Eclipse tell you "there was an error starting the job" there are a few things to check. 1. Ensure that the Ipro Integration Service is running on the eCapture machine that is hosting it (usually the main controller machine and Queue Manager machine, but double check environmental documentation to be sure). This service is what bridges Eclipse and eCapture, and is essential for running productions and exports our of Eclipse. 2. Check the Controller and Queue Manager logs. One of them will most likely report another error message that should help identify why staging has failed. 3. If the service is running and eCapture is not reporting any errors, then try recycling the Application pools for both ADD and Eclipse in IIS. To confirm that this works you will need to re-create the job or make a copy of it, but this can sometimes prevent the issue as well. As always the best place for getting error messages for production is going to be the eCapture logs, but sometimes the error can be picked up in the ReviewAdmin.ExceptionLog in the Eclipse Config database in SQL as well. Make sure to check them both to help pinpoint the exact error that is causing staging to fail. Note that these jobs will need to be removed manually from SQL afterwards, or can be ignored.
  14. Have you ever needed to know how many pages are in a subset of documents and didn't want to add them all up one at a time? Well there is a feature in Eclipse SE Desktop that can do this for you! If you run a search on the documents you are looking for and go to print one of it's images, you can select to calculate the page count from all documents by selecting the All Documents radio button and clicking on the Calculate Page Count button!
  15. Have you ever needed to know how many pages are in a subset of documents and didn't want to add them all up one at a time? Well there is a feature in Eclipse SE Desktop that can do this for you! If you run a search on the documents you are looking for and go to print one of it's images, you can select to calculate the page count from all documents by selecting the All Documents radio button and clicking on the Calculate Page Count button!
  16. Have you ever needed to know how many pages are in a subset of documents and didn't want to add them all up one at a time? Well there is a feature in Eclipse SE Desktop that can do this for you! If you run a search on the documents you are looking for and go to print one of it's images, you can select to calculate the page count from all documents by selecting the All Documents radio button and clicking on the Calculate Page Count button!
  17. Ever have problems opening your case in Eclipse SE and cannot seem to figure out why? Here is a quick guide on how to check out if the case data directory is set properly! 1. Go to Eclipse SE Administrator 2. Click on Client/Case Management > Case Management 3. Select your Client ID and select the case 4. If you get an error that says "Could not open case MainIndex. Case Database directory does not exist" then the data directory is wrong. If you don't get this message and the case loads, then make sure the system directory is set properly on the Desktop user's machine (Config button when logging in) 5. Click OK > Modify Case > try to reach the path listed under Data Directory. If Windows File Explorer cannot find it, then the path is wrong. 6. Remove sections of the path until it works to narrow down your search on where to check for the correct path This can happen sometimes when people are moving the system directory around between locations or when trying to organize the System Directory manually.
  18. Ever have problems opening your case in Eclipse SE and cannot seem to figure out why? Here is a quick guide on how to check out if the case data directory is set properly! 1. Go to Eclipse SE Administrator 2. Click on Client/Case Management > Case Management 3. Select your Client ID and select the case 4. If you get an error that says "Could not open case MainIndex. Case Database directory does not exist" then the data directory is wrong. If you don't get this message and the case loads, then make sure the system directory is set properly on the Desktop user's machine (Config button when logging in) 5. Click OK > Modify Case > try to reach the path listed under Data Directory. If Windows File Explorer cannot find it, then the path is wrong. 6. Remove sections of the path until it works to narrow down your search on where to check for the correct path This can happen sometimes when people are moving the system directory around between locations or when trying to organize the System Directory manually.
  19. Ever have problems opening your case in Eclipse SE and cannot seem to figure out why? Here is a quick guide on how to check out if the case data directory is set properly! 1. Go to Eclipse SE Administrator 2. Click on Client/Case Management > Case Management 3. Select your Client ID and select the case 4. If you get an error that says "Could not open case MainIndex. Case Database directory does not exist" then the data directory is wrong. If you don't get this message and the case loads, then make sure the system directory is set properly on the Desktop user's machine (Config button when logging in) 5. Click OK > Modify Case > try to reach the path listed under Data Directory. If Windows File Explorer cannot find it, then the path is wrong. 6. Remove sections of the path until it works to narrow down your search on where to check for the correct path This can happen sometimes when people are moving the system directory around between locations or when trying to organize the System Directory manually.
  20. While working with Persistent Highlighting there are some key things to know regarding how to write out your terms to get the results you are looking for. Below are some important notes to remember when formatting your list of terms: 1. Persistent Highlighting is looking for an exact match. If the word is spelled differently in a document, then it will not highlight. Also only the provided variation of the word will be highlighted. 2. Persistent Highlighting does not highlight partial words. If your term is found in the middle of a larger word, then it will not be highlighted be default. 3. Asterisk (*) is the only supported wildcard. Using this character means that there might be other letters associated with the word, but will stop looking once it encounters white space. 4. Persistent Highlighting can highlight a phrase of words. To do this just make sure the whole phrase is on a single line. Using quotes will also force the search to find the quotes in the extracted text and may not find what you are looking for. 5. Persistent Highlighting does NOT use dtSearch to find the word, but DOES return the count of words. If you ever see the counts being incorrect, then rebuilding your dtSearch index should resolve that. However it is possible to use Persistent Highlighting without the dtSearch index for highlighting the terms. Here are some examples to better illustrate some of these points. They are broken into the term that is being searched, then an example of something that would be highlighted, and finally something that would not be highlighted or would only be partially highlighted. Term | "Example of what would highlight" | "Example of what won't highlight" 1. Example | "example" | "exemple" -- spelling mistakes or alternative spellings are not highlighted 2. part | "PART" | "impartial" -- partial words without *s will not work 3. *part* | "impartial" | "party people" -- while party would highlight, the whole phrase would not highlight 4. This is a phrase | "This is a phrase" | "This is a different phrase" -- If the whole phrase is located anywhere in the case it will be highlighted, but only if it matches exactly (or you are using the * wildcard correctly)
  21. While working with Persistent Highlighting there are some key things to know regarding how to write out your terms to get the results you are looking for. Below are some important notes to remember when formatting your list of terms: 1. Persistent Highlighting is looking for an exact match. If the word is spelled differently in a document, then it will not highlight. Also only the provided variation of the word will be highlighted. 2. Persistent Highlighting does not highlight partial words. If your term is found in the middle of a larger word, then it will not be highlighted be default. 3. Asterisk (*) is the only supported wildcard. Using this character means that there might be other letters associated with the word, but will stop looking once it encounters white space. 4. Persistent Highlighting can highlight a phrase of words. To do this just make sure the whole phrase is on a single line. Using quotes will also force the search to find the quotes in the extracted text and may not find what you are looking for. 5. Persistent Highlighting does NOT use dtSearch to find the word, but DOES return the count of words. If you ever see the counts being incorrect, then rebuilding your dtSearch index should resolve that. However it is possible to use Persistent Highlighting without the dtSearch index for highlighting the terms. Here are some examples to better illustrate some of these points. They are broken into the term that is being searched, then an example of something that would be highlighted, and finally something that would not be highlighted or would only be partially highlighted. Term | "Example of what would highlight" | "Example of what won't highlight" 1. Example | "example" | "exemple" -- spelling mistakes or alternative spellings are not highlighted 2. part | "PART" | "impartial" -- partial words without *s will not work 3. *part* | "impartial" | "party people" -- while party would highlight, the whole phrase would not highlight 4. This is a phrase | "This is a phrase" | "This is a different phrase" -- If the whole phrase is located anywhere in the case it will be highlighted, but only if it matches exactly (or you are using the * wildcard correctly)
  22. While working with Persistent Highlighting there are some key things to know regarding how to write out your terms to get the results you are looking for. Below are some important notes to remember when formatting your list of terms: 1. Persistent Highlighting is looking for an exact match. If the word is spelled differently in a document, then it will not highlight. Also only the provided variation of the word will be highlighted. 2. Persistent Highlighting does not highlight partial words. If your term is found in the middle of a larger word, then it will not be highlighted be default. 3. Asterisk (*) is the only supported wildcard. Using this character means that there might be other letters associated with the word, but will stop looking once it encounters white space. 4. Persistent Highlighting can highlight a phrase of words. To do this just make sure the whole phrase is on a single line. Using quotes will also force the search to find the quotes in the extracted text and may not find what you are looking for. 5. Persistent Highlighting does NOT use dtSearch to find the word, but DOES return the count of words. If you ever see the counts being incorrect, then rebuilding your dtSearch index should resolve that. However it is possible to use Persistent Highlighting without the dtSearch index for highlighting the terms. Here are some examples to better illustrate some of these points. They are broken into the term that is being searched, then an example of something that would be highlighted, and finally something that would not be highlighted or would only be partially highlighted. Term | "Example of what would highlight" | "Example of what won't highlight" 1. Example | "example" | "exemple" -- spelling mistakes or alternative spellings are not highlighted 2. part | "PART" | "impartial" -- partial words without *s will not work 3. *part* | "impartial" | "party people" -- while party would highlight, the whole phrase would not highlight 4. This is a phrase | "This is a phrase" | "This is a different phrase" -- If the whole phrase is located anywhere in the case it will be highlighted, but only if it matches exactly (or you are using the * wildcard correctly)
  23. Hi everyone, When I was looking into Eclipse SE I noticed that when I was sorting on a multi-value field that the results were not what I expected. After digging around I was able to find out how Eclipse SE handles sorting multi-values fields, and I think this can be very useful for everyone to know! So let's say we have five files with the following information: BEGDOC Values | Multi-Value Field Information 0001 | A;C 0002 | B;C;A 0003 | D;A 0004 | A;Z 0005 | Z;A Now before I go any further it is worth mentioning that in Eclipse SE Administrator you can set multi-value fields to auto-sort the values, which will make the Multi-Value field information field look identical for the first three, as well as making the last two identical as well. When you sort the second column using the "Sort Ascending" option it will keep everything in the same order. This is because the sort looks for the value that would appear first in alphabetical order in the field and uses that to sort on other documents. This means that even though the first value for the second file is a B, it will appear with the A's because the value the sort pulls is A. If we sort using the "Sort Descending" option instead, the list will return the documents in the following order: BEGDOC Values | Multi-Value Field Information 0005 | A;Z 0004 | Z;A 0003 | D;A 0001 | A;C 0002 | B;C;A These results are because it pulls the "lowest" value in alphabetical order and sorts on that. In the event of a match, it sorts based on BEGDOC instead. Lastly, since sorting this way only reads one value, the BEGDOC value is used if the value that is returned matches another. For example, let's say you have three files and their field information is as follows: BEGDOC Values | Multi-Value Field Information 0001 | A;C 0002 | A;B 0003 | A When you use the Sort Ascending option these files will appear as is. This is because the sort only takes one value from the field. I hope this is useful to anyone trying to sort on a multi-value field!
  24. Hi everyone, When I was looking into Eclipse SE I noticed that when I was sorting on a multi-value field that the results were not what I expected. After digging around I was able to find out how Eclipse SE handles sorting multi-values fields, and I think this can be very useful for everyone to know! So let's say we have five files with the following information: BEGDOC Values | Multi-Value Field Information 0001 | A;C 0002 | B;C;A 0003 | D;A 0004 | A;Z 0005 | Z;A Now before I go any further it is worth mentioning that in Eclipse SE Administrator you can set multi-value fields to auto-sort the values, which will make the Multi-Value field information field look identical for the first three, as well as making the last two identical as well. When you sort the second column using the "Sort Ascending" option it will keep everything in the same order. This is because the sort looks for the value that would appear first in alphabetical order in the field and uses that to sort on other documents. This means that even though the first value for the second file is a B, it will appear with the A's because the value the sort pulls is A. If we sort using the "Sort Descending" option instead, the list will return the documents in the following order: BEGDOC Values | Multi-Value Field Information 0005 | A;Z 0004 | Z;A 0003 | D;A 0001 | A;C 0002 | B;C;A These results are because it pulls the "lowest" value in alphabetical order and sorts on that. In the event of a match, it sorts based on BEGDOC instead. Lastly, since sorting this way only reads one value, the BEGDOC value is used if the value that is returned matches another. For example, let's say you have three files and their field information is as follows: BEGDOC Values | Multi-Value Field Information 0001 | A;C 0002 | A;B 0003 | A When you use the Sort Ascending option these files will appear as is. This is because the sort only takes one value from the field. I hope this is useful to anyone trying to sort on a multi-value field!
  25. Hi everyone, When I was looking into Eclipse SE I noticed that when I was sorting on a multi-value field that the results were not what I expected. After digging around I was able to find out how Eclipse SE handles sorting multi-values fields, and I think this can be very useful for everyone to know! So let's say we have five files with the following information: BEGDOC Values | Multi-Value Field Information 0001 | A;C 0002 | B;C;A 0003 | D;A 0004 | A;Z 0005 | Z;A Now before I go any further it is worth mentioning that in Eclipse SE Administrator you can set multi-value fields to auto-sort the values, which will make the Multi-Value field information field look identical for the first three, as well as making the last two identical as well. When you sort the second column using the "Sort Ascending" option it will keep everything in the same order. This is because the sort looks for the value that would appear first in alphabetical order in the field and uses that to sort on other documents. This means that even though the first value for the second file is a B, it will appear with the A's because the value the sort pulls is A. If we sort using the "Sort Descending" option instead, the list will return the documents in the following order: BEGDOC Values | Multi-Value Field Information 0005 | A;Z 0004 | Z;A 0003 | D;A 0001 | A;C 0002 | B;C;A These results are because it pulls the "lowest" value in alphabetical order and sorts on that. In the event of a match, it sorts based on BEGDOC instead. Lastly, since sorting this way only reads one value, the BEGDOC value is used if the value that is returned matches another. For example, let's say you have three files and their field information is as follows: BEGDOC Values | Multi-Value Field Information 0001 | A;C 0002 | A;B 0003 | A When you use the Sort Ascending option these files will appear as is. This is because the sort only takes one value from the field. I hope this is useful to anyone trying to sort on a multi-value field!
×
×
  • Create New...