Jump to content

Ipro_TannerComes

IPRO Employee
  • Posts

    59
  • Joined

  • Days Won

    4

Ipro_TannerComes last won the day on August 3 2017

Ipro_TannerComes had the most liked content!

About Ipro_TannerComes

  • Birthday 09/01/1992

Ipro_TannerComes's Achievements

Enthusiast

Enthusiast (6/14)

40

Reputation

  1. Hi GDufrense, A document will only exist within one cluster at a time. Each document is added to the cluster that it fits best depending on the concepts in the document. Thanks, Tanner
  2. As a note, this will be located in the Eclipse Web config, which is located at C:\Program Files\Ipro Tech\Web\EclipseWeb
  3. Hi Cristia, If the name of the file you're ingesting is in a standard begdoc format (ie ABC00000001) then the recommendation is to use the filename as the begdoc. Unfortunately there is no way for Eclipse SE to determine a document's begdoc or a page's image key based on endorsements, as it would rely on OCR, which can be inaccurate.
  4. Hi Cristia, If the name of the file you're ingesting is in a standard begdoc format (ie ABC00000001) then the recommendation is to use the filename as the begdoc. Unfortunately there is no way for Eclipse SE to determine a document's begdoc or a page's image key based on endorsements, as it would rely on OCR, which can be inaccurate.
  5. Hi Cristia, If the name of the file you're ingesting is in a standard begdoc format (ie ABC00000001) then the recommendation is to use the filename as the begdoc. Unfortunately there is no way for Eclipse SE to determine a document's begdoc or a page's image key based on endorsements, as it would rely on OCR, which can be inaccurate.
  6. Say you already had a set of documents reviewed, but you want to implement the TAR process. But at the same time, you don't want to lose all that valuable review work product. Here's a workflow to accommodate this situation: Run the training round as normal. You may encounter some already-reviewed documents in this pass, but just tag them as normal. Check the training batch(es) in, and build categories. Collect the training round reports. Tag the documents that have already been reviewed with the TAR_Responsive, TAR_Not Responsive, and TAR_Do Not Use As Example tags as appropriate. Rebuild your categories at this point. Continue with the validation rounds as normal.
  7. Say you already had a set of documents reviewed, but you want to implement the TAR process. But at the same time, you don't want to lose all that valuable review work product. Here's a workflow to accommodate this situation: Run the training round as normal. You may encounter some already-reviewed documents in this pass, but just tag them as normal. Check the training batch(es) in, and build categories. Collect the training round reports. Tag the documents that have already been reviewed with the TAR_Responsive, TAR_Not Responsive, and TAR_Do Not Use As Example tags as appropriate. Rebuild your categories at this point. Continue with the validation rounds as normal.
  8. Say you already had a set of documents reviewed, but you want to implement the TAR process. But at the same time, you don't want to lose all that valuable review work product. Here's a workflow to accommodate this situation: Run the training round as normal. You may encounter some already-reviewed documents in this pass, but just tag them as normal. Check the training batch(es) in, and build categories. Collect the training round reports. Tag the documents that have already been reviewed with the TAR_Responsive, TAR_Not Responsive, and TAR_Do Not Use As Example tags as appropriate. Rebuild your categories at this point. Continue with the validation rounds as normal.
  9. That's good info Jeff! Just one thing I'd like to add- if you change your transcript, make sure to have a back up first!
  10. That's good info Jeff! Just one thing I'd like to add- if you change your transcript, make sure to have a back up first!
  11. Hey Vaibhav, This was on 2017.3.3. I think it was specific to the environment I was installing, as I've been able to install to other environments without this issue.
  12. Hey Vaibhav, This was on 2017.3.3. I think it was specific to the environment I was installing, as I've been able to install to other environments without this issue.
  13. I ran into this one on a new install today. I set up the client's Relativity Integration service and verified the connections were successful. When I ran a streaming export to Relativity, the export just kinda went on forever. I found out that the Relativity Desktop Client needs to be launched by the account running the Relativity Integration Service prior to running an export. There's some initialization that happens on first-launch, so if that doesn't happen, then the export won't load into Relativity.
  14. I ran into this one on a new install today. I set up the client's Relativity Integration service and verified the connections were successful. When I ran a streaming export to Relativity, the export just kinda went on forever. I found out that the Relativity Desktop Client needs to be launched by the account running the Relativity Integration Service prior to running an export. There's some initialization that happens on first-launch, so if that doesn't happen, then the export won't load into Relativity.
  15. Good info, Michael. To add onto it - it's important that documents with the same prefixes have the same zero-padding width for their numbering in order to avoid pages ending up in the wrong documents or documents ending up in the wrong sort order.
×
×
  • Create New...