Finding parsed data in output #2029
-
Hello all, As part of my computer science master thesis I am examining the output of IPED. I was, however, not able to discover the results of parsing files in the output of IPED. I did of course find the CSV file listing all the discovered files, but I have not been, for example, able to find a file containing data about emails, such as their sender and receiver and topic. I do expect this data to be somewhere, since the IPED user interface also seems to show it in the screenshots on the Github page. I have executed the tool using Docker on an image that contains a wealth of different files. Thanks very much in advance! If I need to provide some more information, please let me know. Kind regards, Luuk van Campen |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
Hi @luukvancampen! Not sure if I fully understand your question, but in the "regular usage" of IPED, all parsed/extracted/generated information is avaliable through the analysis GUI. It is possible to select some items (or all of them), and export their properties to a CSV file. In that case, all visible columns will be included in the CSV. And you can select the visible columns to include the properties you are interested in. Text extracted from the items will not be exported using this procedure, only properties. Another option would be using the WebAPI. |
Beta Was this translation helpful? Give feedback.
-
Hi @luukvancampen. IPED stores parsed data in a structured way into a Lucene index. To access its contents without dealing with low level Lucene API, you can use the Web API (https://github.com/sepinf-inc/IPED/wiki/Web-API) suggested by @wladimirleite or use a python-java bridge like #875 (this uses old IPED v3 API, I'll update the examples to IPED v4 API when I return back from vacation in mid January). |
Beta Was this translation helpful? Give feedback.
-
Hello! Thank you very much! |
Beta Was this translation helpful? Give feedback.
Hi @luukvancampen. IPED stores parsed data in a structured way into a Lucene index. To access its contents without dealing with low level Lucene API, you can use the Web API (https://github.com/sepinf-inc/IPED/wiki/Web-API) suggested by @wladimirleite or use a python-java bridge like #875 (this uses old IPED v3 API, I'll update the examples to IPED v4 API when I return back from vacation in mid January).