Indexed text extraction for external use

[milcent-CVM]

Is there a way to access the text database (SOLR, I believe) to extract text and metadata for external use?

[lfcnassif]

Generally the indexed text is not stored to reduce the case disk usage, it is computed again on demand by UI. Exceptions are OCR and transcription results, since computing them again is a costly operation.

About metadata (and text), it can be obtained (or computed) using the web api (not tested for a long time, maybe it will be deprecated and removed in the future) or python scripts:

• https://github.com/sepinf-inc/IPED/wiki/Web-API
• Using Python to extract IPED case data #875

[lfcnassif]

so DO NOT REMOVE IT 💯 !

Would you be able to help us maintain the feature for all future IPED versions?

[milcent-CVM]

Thanks @wladimirleite . I will try java 11. I thought iped > 4 did not need the system java, but I guess the webapi may be different.

[milcent-CVM]

@lfcnassif I think I told you before, unfortunately I´m not a java guy...
However, if I manage to get the Jnius Java-Python interface (#875) going, I think I might be able to expose it as a Python plugin using FastAPI, maybe even with the possibility of running it from a docker container.

[wladimirleite]

@milcent-CVM, you can use IPED's embedded JRE too.
When running IPED in Windows, iped.exe will find the embedded JRE, but when you use "java -jar" (which you need for using the web API), you need to specify IPED JRE path (something like "jre\bin\java -jar") or add it to the PATH.

[milcent-CVM]

Great tip @wladimirleite , thank you!

It Works!!

So, just to clarify and help anyone else in the same situation (on Windows and with version 4.x), call the java executable from the iped distribution itself. If you are inside the lib folder, which contains the iped-webapi.jar:
..\jre\bin\java -jar .\iped-webapi.jar --sources=[JSON_FILE_WITH_CASES_INFO]
Thanks again!

[paulobreim]

@milcent-CVM including parameters for java. example:
iped.exe -Xms30G -Xmx30G -profile forensic -o i:\xxx -d "h:\image1.dd" -d "h:\image2.dd"

[milcent-CVM]

No, no, @paulobreim, the parameters you mentioned are for indexing, right? The issue here is running an ALREADY INDEXED material in API mode.

[paulobreim]

Sorry