Jonnyp

Hi all, I have tried this new multilevel tagging feature out and it works great. It is useful to contract long strings of tags into a single tag and helps to make the tagging facet nice and tidy. Good work team! JP

Markjrouse, for discovery we use Intella as a processing engine. We ingest the data and run date filters and search terms to identify items that are respondent to the search criteria. When it comes to review we provide a load file to our lawyers to review for privilege and relevance. Once the review is complete the lawyers produce a dataset from their review tool (Summation is used in NZ) with the privileged material removed or redacted to the over party. Our discovery rules in NZ required us to produce PDF files to the other party. This can be done relatively easily in Summation where redactions are "burned in" on the PDF files. Your situation is a bit different to ours. If you are required to provide native emails with any privileged attachments removed, I can only see this being a manual process unfortunately. How do other tools deal with this type of situation? I cant say I have heard of any discovery tools that will remove selected attachments from native emails. JP

Hi markjrouse and Administrator, I have completed some testing on this issue. I have base the testing on the following assumptions: The export dataset is made up of an email message with 4 attachments (word, excel, PDF etc) That the export dataset is being exported as a load file The load file contains native documents and images The load file should contain the email and only 3 of the attachments Process: I located an email that had 4 attachments and tagged all items into a tag named 'Dataset'. I selected 1 of the attachments and tagged this attachment as 'Exclude'. I searched on the Dataset tag which returned the email and 4 attachments. I also ran an exclude search on the Exclude tag and the 1 attachment in the Exclude tag was removed from the items in the Details pane. I created a load file from the email and 3 attachments remaining in the Details pane. Output: The load file created correctly and contained 1 email message and 3 attachments in the 'Natives' folder. Similarly images for the email and 3 attachments were created. Findings: As you would expect, there were no native files for the attachment that was excluded. This is the case because when creating a load file, only the selected item in the Details pane are included in the load file. I have to mention that the native email actually contains all 4 attachments within it. This is something I was not aware of and poses an issue if markjrouse wants to remove one of the attachments of an email for privilege purposes. The only work around I can think of at this stage is to not include native documents when creating the load file. This will leave you with images for the email and only the 3 attachments. Discussion: In my view, this is a tricky issue to fix. What should be included in discovery will depend on your discovery and disclosure laws/rules and I would certainly leave this up to the lawyers. If Vound add functionally to remove 1 attachment from a native email, that email is no longer the same as the original email, would this cause another problem? It is possible that there are other consequence involved in removing attachments. JP

Hi Markjrouse, creating load files from search results is not as easy as it sounds. I have seen people make mistakes when selecting the data for load files. One mistake I've seen is when load files are created from direct searches only which, as you know, do not include all family items (In NZ the discovery rules state that all family items need to be included with any relevant items). I have also seen load files where all children items are returned and included. This causes all embedded items to be added as individual items in the load file. This can really blow out the number of unnecessary tiff images that are produced for the load file (1 PDF file can result in100s of tiff files) and also the time to create the load file. The over populated load file will produce a separate line for each item in the review system which is not ideal. After the searching phase is complete, care must be taken when selecting the documents for the load file so that you don't miss anything and that you don't end up with a whole lot of junk files in the load file. This is how we select these files and exclude the embedded items. Show all of the top parent items from the search results (some items in the search results may already be top level items). Using the top level items and all of the search hit items, we show all of the children and tag them. We do not select 'show direct children' as relevant files could be several levels deep (i.e. a word doc in a zip file that is attached to an email which is in another zip file). This step helps to identify all pure parent items. To locate the pure parent items, run a search on the search results and parent items and also run an exclude search on the children tag. This will display only the pure parent items. Tag these pure parents and dedup as the client does not want to review duplicates. Show all children items for the pure parent items and tag them. Now we need to 'clean' the child item tag. We want all email attachments and anything that is in the body of an email (i.e. screen shots that have been pasted in an email etc) Show the children tag and sort by the URI field. The first thing you can remove from this tag are all image files that are marked 'PDF:Aperture' in the URI column. We will have the original PDF so we don't need all of these bits and pieces. This will remove a large percentage of embedded items. Do the same for WORD:Aperture, POWERPOINT:Aperture, OPENXML:Aperture etc. Make sure you don't remove the items in ZIP:Aperture or MSG:Aperture. The MSG:Aperture will include all of the linkedin and twitter logos that we don't want however, there could be screen shots in the body of emails that are relevant and we don't want to get rid of these. Clear the search and search again on the children tag. In facets, view by 'type' then 'image'. Now view in thumbnail view and manually remove items that are clearly 'junk' images. This should clean up most of the embedded items. Regards Jon