Skip to content

Output column names (CLI+docs) + ergonomics of matchprintf #231

@ross-spencer

Description

@ross-spencer

I might be missing something, but right now, the only documentation we have of column names output by FIDO is:

fido/fido/fido.py

Lines 803 to 804 in 33789ab

parser.add_argument('-matchprintf', metavar='FORMATSTRING', default=None, help='format string (Python style) to use on match. See nomatchprintf, README.txt.')
parser.add_argument('-nomatchprintf', metavar='FORMATSTRING', default=None, help='format string (Python style) to use if no match. See README.txt')

Previously I am guessing it was in the KB wiki: https://github.com/openpreserve/fido?tab=readme-ov-file#installation but I believe a long-term issue exists where this can't be accessed any more.

In terms of features, I wonder if a user friendly set of columns could be output? (if this can't be output already), i.e. CSV header.

We could also add this to the docs.

I can see looking around one or two folks use matchprintf, e.g. fido -matchprintf "%(info.mimetype)s,%(info.time)s,%(info.puid)s\n" filename to truncate data in rows. It's quite complex to setup though, I wonder if there's a way the ergonomics of this can be improved? (or if there already exists a conf file that might help take some of the pain away on every invocation)?

Lots of questions sorry! (I think I've had to work this out a few times in the past but haven't committed to writing an issue before now and should have saved my previous notes).

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions