Jump to content

wmfiske

Members
  • Content Count

    9
  • Joined

  • Last visited

Community Reputation

0 Neutral

About wmfiske

  • Rank
    Newbie

Profile Information

  • Gender
    Not Telling
  1. I have the same question on how this can be done if a reviewer is using Connect. I can do this type of limitation to the keyword list if I use Intella Viewer or Intella Pro. However, in my case, I have a need for this to happen with the reviewer using Connect.
  2. I am using 1.9.1 to read a CSV load file and it will not read the file properly when it comes to the Extracted Text field. A sample Extracted Text field is "Images\001\001\00000001.txt" During the Validation step, it says it cannot read the file. The example above shows [path]\Images00100100000001.txt The backslashes in the CSV file are not being read and shows it as one long string.
  3. When I use Preview Item (CTRL+O), I can enter either an Item ID number or a URI. If I want to identify a series of Item ID's, I can add those Item ID's items to a single text file and import that list via the Item ID Lists facet. Can you expand the Item ID Lists facet to include a text file containing URI's?
  4. [disregard - wrong forum]
  5. I would like to open a community discussion on OCR settings and programs as I have been doing some performance testing recently. There are two versions of ABBYY that I have been testing: FineReader Corporate (4 core) and Recognition Server (RS v4). My first assumption was that RS v4 would be faster since it is 4-5x the cost of the 4-core Corporate version. I was using an unlimited core version and I liked the idea that I could export/import files directly from Intella v1.9. In one test, I sent 100 non-searchable PDF files to RS using the Intella interface. I preconfigured a workflo
  6. Does Intella calculate the total expanded size of data? I know that I can export the table to a CSV list with each entry and sum the size. That export takes some time.
  7. Igor, The recovery of deleted items is exactly what took the longest. It took a total of 9 hours to process the entire 30 GB OST file. According to the log, 7 hours was used to process deleted items.
  8. The OST file was created by Outlook 2010.
  9. I am currently running ver 1.9 and indexing a 30 GB OST file. Intella was cranking along just fine for the first 80 minutes. Then it reduced to a minimal processing mode. The Index New Data window shows no new activity. However, through Resource Monitor, I can see that Java is reading the OST file, but it appears to be extremely slow in contrast. Is there a way to determine exactly what is going on? I am running it on a Windows 7 box (i7-5930 3.5 GHz with 64GB RAM) with evidence on one drive and temp on a 512 GB M.2 card. This is my second test on this OST file. When I
×
×
  • Create New...