Jump to content

Ipro_TannerComes

IPRO Employee
  • Posts

    59
  • Joined

  • Days Won

    4

Everything posted by Ipro_TannerComes

  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.
  16. 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.
  17. I came across an interesting issue on an install today. I was installing Eclipse, and I would get a 403 error whenever I browsed to it, even from the web machine. I verified that my service account had permission to C:\Program Files\Ipro Tech\Web and that only Anonymous Authentication was enabled in IIS. Searching the logs, I found the specific error was 403 with a substatus of 14. I googled this to find that enabling Directory Browsing would fix it. So I tried this, but now I could see all the files in C:\Program Files\Ipro Tech\Web\EclipseWeb. I clicked on the Eclipse.xbap and it downloaded and ran. But obviously this wasn't the fix - you don't want users seeing what's in that directory. So I disabled Directory Browsing and realized that the Default Document probably wasn't configured. In IIS, I selected the Default Document option and as I suspected, "eclipse.xbap" was not in the list. I added this entry and tried again, and just like that I was able to access Eclipse.
  18. I came across an interesting issue on an install today. I was installing Eclipse, and I would get a 403 error whenever I browsed to it, even from the web machine. I verified that my service account had permission to C:\Program Files\Ipro Tech\Web and that only Anonymous Authentication was enabled in IIS. Searching the logs, I found the specific error was 403 with a substatus of 14. I googled this to find that enabling Directory Browsing would fix it. So I tried this, but now I could see all the files in C:\Program Files\Ipro Tech\Web\EclipseWeb. I clicked on the Eclipse.xbap and it downloaded and ran. But obviously this wasn't the fix - you don't want users seeing what's in that directory. So I disabled Directory Browsing and realized that the Default Document probably wasn't configured. In IIS, I selected the Default Document option and as I suspected, "eclipse.xbap" was not in the list. I added this entry and tried again, and just like that I was able to access Eclipse.
  19. I've received a call here or there where a user got a new machine and installed Eclipse SE and the buttons were missing text, or there were other strange display issues. One such call came from @Lori Bregenzer and she helped me figure out a way to work around this: 1. Right-click on the desktop. Choose "Display Settings", or go to Control Panel -> appearance and Personalization -> Display 2. Locate the Change the size of all items section. 3. Change the size to Smaller - 100% 4. Restart the PC to apply the changes universally.
  20. I've received a call here or there where a user got a new machine and installed Eclipse SE and the buttons were missing text, or there were other strange display issues. One such call came from @Lori Bregenzer and she helped me figure out a way to work around this: 1. Right-click on the desktop. Choose "Display Settings", or go to Control Panel -> appearance and Personalization -> Display 2. Locate the Change the size of all items section. 3. Change the size to Smaller - 100% 4. Restart the PC to apply the changes universally.
  21. I've received a call here or there where a user got a new machine and installed Eclipse SE and the buttons were missing text, or there were other strange display issues. One such call came from @Lori Bregenzer and she helped me figure out a way to work around this: 1. Right-click on the desktop. Choose "Display Settings", or go to Control Panel -> appearance and Personalization -> Display 2. Locate the Change the size of all items section. 3. Change the size to Smaller - 100% 4. Restart the PC to apply the changes universally.
  22. Hi Stephen, A few questions that might help us to figure out what's wrong here: 1 - Does the data show up this way in the Eclipse Web interface? 2- What is the data type of the field? You can find this in Eclipse Admin -> Case Management -> Database Fields 3- Are you opening the dat file in Notepad, or a different program? If so, which? Thank you, Tanner Comes Technical Support Engineer
  23. Hi Stephen, A few questions that might help us to figure out what's wrong here: 1 - Does the data show up this way in the Eclipse Web interface? 2- What is the data type of the field? You can find this in Eclipse Admin -> Case Management -> Database Fields 3- Are you opening the dat file in Notepad, or a different program? If so, which? Thank you, Tanner Comes Technical Support Engineer
  24. Hi Stephen, A few questions that might help us to figure out what's wrong here: 1 - Does the data show up this way in the Eclipse Web interface? 2- What is the data type of the field? You can find this in Eclipse Admin -> Case Management -> Database Fields 3- Are you opening the dat file in Notepad, or a different program? If so, which? Thank you, Tanner Comes Technical Support Engineer
  25. If you need to populate a page count field as part of a production requirement, and this data isn't already in your Eclipse case, you can use the below query to populate a page count field. Keep the following in mind when using this query: 1. It's best to back up a database prior to running any DML queries against it. 2. This query should be run against the case database. 3. Populate the name of the field as it appears in the case in the first DECLARE statement. 4. This query will update the specified Page Count field and the Has Image field based on information it finds in the DocumentPages field. 5. The query will fail if the specified Page Count field is either not found in the case, or is not a WholeNumber field. /**************************************************************************** Update Page Count and HasImage for a case. Use: Run against your case Database. Enter the field name between the quotes of the @PageCountFieldName variable. If the field does not exist, or is not a WholeNumber value, the query will fail and provide instructions to continue. Author: TComes@Iprotech 05 12 2017 ******************************************************************************/ DECLARE @PageCountFieldName nvarchar(20) = '' --Enter the field name here. DECLARE @PageCountDBFieldName nvarchar(20) DECLARE @PageCount NVARCHAR(7) DECLARE @DocID INT DECLARE @SQL NVARCHAR(MAX), @HasImageSQL NVARCHAR(MAX) DECLARE @HasImageField NVARCHAR(20) = (SELECT ColumnName from vFieldDefinition where systemfieldtype = 25) SET NOCOUNT ON IF NOT EXISTS(SELECT TOP 1 1 FROM vFieldDefinition WHERE FieldName = @PageCountFieldName) THROW 50001, 'The specified field does not exist. Please ensure you''ve typed the field name exactly as it appears in the case and try again.', 1 ELSE IF ((SELECT TOP 1 FieldDataType FROM vFieldDefinition WHERE FieldName = @PageCountFieldName) <> 2) THROW 50001, 'The specified field exists, however it is not of WholeNumber type. Please choose a different field or correct the field.', 1 SET @PageCountDBFieldName = (SELECT TOP 1 ColumnName FROM vFieldDefinition WHERE FieldName = @PageCountFieldName) IF OBJECT_ID('tempdb..##docs') IS NOT NULL DROP TABLE ##docs CREATE TABLE ##docs ( DocID INT ) INSERT INTO ##docs SELECT Docid from vDocumentFields WHILE EXISTS (SELECT TOP 1 1 FROM ##docs) BEGIN SET @DocID = (SELECT TOP 1 DocID FROM ##docs) SET @PageCount = (SELECT COUNT(*) FROM DocumentPages WHERE DocID = @DocId) SET @HasImageSQL = 'UPDATE vDocumentFields SET ' + @HasImageField + ' = ' + CAST(IIF(@PageCount < 1, 0, 1) AS NVARCHAR) + ' WHERE DocID = ' + CAST(@DocID AS NVARCHAR) IF @PageCount = 0 SET @PageCount = ' ' SET @SQL = 'UPDATE vDocumentFields SET ' + @PageCountDBFieldName + ' = ' + CAST(IIF(@PageCount = ' ', '''''', @PageCount) AS NVARCHAR) + ' WHERE DocID = ' + CAST(@DocID AS NVARCHAR) EXEC(@SQL) EXEC(@HasImageSQL) PRINT 'Doc ID ' + CAST(@DocID AS NVARCHAR)+ ' has ' + CAST(IIF(@PageCount = ' ', 0, @PageCount) AS NVARCHAR) + ' pages.' DELETE FROM ##docs WHERE DocID = CAST(@DocID AS NVARCHAR) END
×
×
  • Create New...