[CHANGE] consider JSONL output to the console

[ross-spencer]

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

The current workflow requires export of data to tsv and then parsing of those files in a rather undynamic way, e.g. one might open them in LibreOffice and then analyze them there. There may be ways to make the workflow more ergonomic for users adept with the command line.

Describe the solution you'd like
A clear and concise description of what you want to happen.

Offer an export to JSONL via the session ID so that it can be piped to a file or straight to JQ.

JSONL is a good format for this as there are different schemas for directory/file/exif/session and so on. JQ is also adept at handling JSONL enabling querying and remapping into other JSON schemas if required.

Connected to #138 this would give the user a streamlined scan -> export -> analyze with JQ workflow.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

As the tool matures other export formats may also be desirable but JSON feels too static with the heterogeneous schema currently being made use of. That being said, making it easy to extend options in future would be a good approach.

[steffenfritz]

That is indeed a question I have been asking myself for a long time. Thanks for the input! JSONL looks interesting. Can this also be transferred well to visualization tools, e.g. Kibana/Open Dashboard? I think that would be an exciting path for analysts.

[ross-spencer]

Can this also be transferred well to visualization tools, e.g. Kibana/Open Dashboard?

I believe it can because Kibana (at least) will often be working on line by line input, e.g. logs. That being said, those two tools are gaps I need to fill in my knowledge.

If I can find capacity again in the coming weeks I'll also try and take a look.