Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Alex last won the day on February 3 2017

Alex had the most liked content!

Profile Information

  • Gender
    Not Telling

Alex's Achievements


Newbie (1/14)



  1. Hello, In the Content Analysis facet panel, create new category with a regular expression for your pattern ("New" button) Execute content analysis for this category on the selected items ("Process->Content Analysis..." in the context menu) Right-click the category name in the CA facet and select "Export values...". You can export the values list either into plain-text CSV or Excel format.
  2. "baxter (article OR paper)"~20 AND "jason (article OR paper)"~20 A nearest one I can think of.
  3. Hello, Matches of the wildcard searches like this are highlighted. If you think if it doesn't work in your case, I suggest to open a support ticket with detailed information about this issue.
  4. Hello, To find these words in a sequence, a phrase pattern should be used: "(tr?s OR 3) (porcento OR percento) (jos? OR paulo)" Note that I omitted the clause with the singe % character, because it cannot be searched alone. Can you please elaborate a bit on what "click on Highlight hits" means? Intella UI does not have a button or other element named like this. The hits are highlighted automatically in the Previewer window when a keyword search result is opened.
  5. Hi, You can take a look at the regular expression-based Content Analysis feature that allows to search for complex patterns like in your case. The regular search does not support proximity searches with phrases and word distances. Only single terms and character distances are allowed: "Pace Slow"~20 ("Pace" and "Slow" within 20 characters in the extracted text)
  6. Either way. The search scope (text or metadata) is defined by selected search options only and does not depend on the syntax. Yes, regular expressions should be enclosed between forward slashes: otherwise, they are parsed just like normal query strings. It should be noted that regex syntax support in the regular search is experimental and there are few known limitations related with it. For instance, only patterns for individual words are supported, so sentence or phrase search is not possible there. Regex search in the Content Analysis is a different story: it is more powerful, but as it was pointed out, works only on the full text. I think, Jon's reply was about this type of search.
  7. Hello, Metadata values should be searchable if the respective search options are turned on (the "Options" button under the search bar). Regex search function in the Content Analysis ("custom categories") works only for full text of items (not metadata). If you think this is not working properly, feel free to open a support ticket on https://support.vound-software.com. Please attach the screenshots to illustrate the issue. Thanks!
  8. PDF's may contain photocopies or scanned images of documents. In this case, they need to be OCRed in order to be searchable in Intella. Please note that if embedded ABBYY FineReader method is used, all foreign languages must be selected on the configuration page of the OCR wizard. For PDF documents containing a parseable text, non-English language should not be a problem. Otherwise, we suggest to open a support ticket and attach few examples of problematic PDFs.
  9. Hello, MD5 value of an email message can be defined as a hash of an exported EML file. From the forensic point of view, this provides the most accurate identification of message duplicates, as it is computed for all MIME fields (unlike Message Hashes).
  10. Unfortunately, it will not work. The AND operator has no meaning within the phrase and proximity searches.
  11. Dear users, Recently our support service received a number of complaints about Intella started to crash after updating the GeForce driver. As it turned out, the problem was the driver version, not compatible with Java applications. If your Intella installation is affected by this issue, it is highly recommended to download and install the 378.57 driver hot fix provided by NVIDIA: http://nvidia.custhelp.com/app/answers/detail/a_id/4378/
  12. Hans, This is a good idea to have an option to export the search history to a KW list file. We will consider this in feature planning for future versions, In the current version, it's possible to extract a list of all used keywords manually from "case.prefs" file located in "prefs" subfolder of the case. The entry to search in this file is "SearchHistory". The keywords in the list are separated by special "_." character sequences, which need to be removed and replaced by line breaks. Thanks!
  13. Hello Buldawg, You can use the Content Analysis facet that contains all Credit Cards and Social Security numbers found in this case. These values are extracted automatically during indexing, there is no need to run the Content Analysis process to identify them. The values can be exported to a CSV file using "Export values" option in the context menu. Hope this helps.
  • Create New...