jcoyne

Hi Cristiaan, This makes sense now. I've just tested it with 16 CPU cores (rather than the production 8) and it makes very little difference. It appears that the code for the conversion will not use all of the available CPU cycles The pre caching idea would be great. Ideally as a background process based on a certain Flags/Tags when connect is up and running. I say that because you may have 100,000 office documents of which 1500 may be responsive to search terms - it would only be these 1500 which you would pre-cache ready for the linear review, the rest can wait for the conversion but I would not want to add too many hours to the initial index caching the whole 100,000. Happy to test this if you have a pre-production?

I've noticed that the native preview tab in connect 1.8 (this includes both .2 & .4) is slower to display the document that it was with 1.7.x Its fine previewing PDF's as these are not converted server side, put word/excel and powerpoint documents when being converted from native to pdf as not as quick as before. The server platform is the same, the case is the same, just connect is now on 1.8 - the users of the case commented that they used to be able to review documents and tag in the preview pane with documents loading is <1sec - now the same process takes about 2-3seconds with the "loading native previewer" message displayed. I've monitored the connect server and I can see the java process utilizing CPU cycles, but these are well balanced acrossed the 8 cores and dont raise the server above 22-25% for about 2-3 seconds. It would be a better user expereince if it used 75% for 1 second and I think this is the profile that we saw in 1.7. Has the preview engine (which converts office documents to PDF) in connect 1.8 been changed? and can I tune it to speed up the process. Best regards, Jason

Hi Guys, We are just about to start a case where a significant number of the documents are in Mandarin as well as English. This will include Electronic documents and about 27000 sheets of paper which we plan to OCR to text overlaid images held within a PDF format. We are going to be provided with two sets of search terms, one English the other which is stated to be Simplified Chinese. Is any of the above likely to cause Intella and problems and/or do we need to configure our systems differently to handle the search and review (planned to be Team for Indexing then Connect 1.8.2 for the review)? Any help or advice would be appreciated.

Hi Guys, We really need your help on how we can facilitate the removal of some data from Intella. The background is that we are hosting the edisclosure for one of the parties in a 6 party litigation, over the course of the last couple of months we have exchanged many rounds (3 rounds x 6 parties) of document disclosure and really exercised the import/export by load file functionality and all is working well. Now - one of the other parties has inadvertently disclosed some privileged material and we have loaded it into intella, the other parties have loaded it into their respective systems (3 x clearwell, relativity and Recommind). We are now faced with a request to remove the offending material, the other parties are confirming that they have deleted the material, but I'm not going to be able to make the same statement. I'm aware that I can tag and then restrict access but I've started these discussions and it will not be good enough. I cant (practically) rebuild the case without the offending material as the number of load files all of different formats etc would be weeks worth of work. I can however remove the native files from the directory, therefore the previewing will error gracefully, but I'm still left with the text of the documents in the "contents" tab. Is there any chance, even if its at database level, that I can zero out the contents tab - This will allow me to comply with what is likely to be a court order ? Intella is really holding it own in this litigation with other parties slow and expensive mega systems - I don't want to fall nearing the home straight. Hope you can assist? Best regards, Jason Coyne

Thank you Chaps - both worked well .

The Parent ID is available in the export to relativity load file, I have used "RECORD_ID_GROUP_BEGIN" in the load file to link the email bodies and attachments together. You can also open a relativity load file "Export.dat" in excel as a delimited file and then save it as an xls

I'm searching for a Mr Bradly-Jones in intella but "Bradly-Jones" even when in quotes treats the search as Bradly AND Jones. After looking at the manual I've also tried Bradly\-Jones and Bradly?Jones but all seem to return the two names separately. These are in both email addresses and documents Any ideas? Best Regards, Jason

Hi Chaps, I love the functionality of Intella but have sleepless nights about the indexing process. I'm generally a bit disappointed that Intella does not use more of the available power of the machine to index quicker. I'm currently conducting the indexing on a dual processor (total 8 cores) with 28 GB RAM and a 512GB SSD for the intella database and 4TB spindle drive for the source files (mix of pst's and general office files). Intella never gets more than 30-50% of the system utilisation and never maxes out the RAM / IO / CPU and I seem to think there must be a way to improve the speed and get it to use more power. I've experimented with the settings in the ini files, but I don't really notice much difference. Has anyone got any recommendations of where to move the memory tuning setting to? or anything else within the system that make the indexing process quicker? Best regards, Jason Coyne.

Great News! The workflow you suggest sounds reasonable. I think only content is required to be redacted, I cant currently perceive (for my purpose) meta data would need redaction. I have been using the Adobe XI redaction and that works well (certainly worth looking at for ideas). It would be good if you can search for text and globally replace with a redaction mark, say redact all "Ms Lizza Wong" Make sure the redactions are 'burnt in' I saw some redaction last month that were floating blocks of colour that if you scrolled up and down fast enough you could cause lag and see the text underneath. Its bound to be asked - when is the ETA of this feature? Best regards

is this available in 1.7.2 ? or in a future version

Ok I understand so, I do the redactions afterwards once I have selected the documents of interest and exported them. No problem

I was looking for a way to Annotate and/or redact a document within intella. I have located the above but it appears it is functionality greyed out? Is there anything that I need to do. what is the link to annotations designed to do? Best regards, Jason

I'd like to be a beta tester please