Provide filtering options to gooseberry make ?

[ngirard]

I've started this discussion rather than an issue, because I should perhaps adapt my workflow to Gooseberry rather than the opposite here.

The filtering options to search and view and the proposed workflow make all perfect sense to me, until I try and bring my new annotations to my Obsidian vault.

I feel the need to digest my annotations from within Obsidian iteratively, i.e. dealing with them by chunks. For this, I would associate a tag to each research I'm performing, so that when working on a topic T, the related annotations are all tagged T -- or whatever equivalent.

So at that stage, I'd expect to be able to generate markdown files only for today's annotations, or for the topical tags related to my current work (like T in this discussion), instead of regenerating the whole stuff.

But perhaps I'm approaching it the wrong way ?

[ngirard]

(Loosely) related: #86.

[Ninjani]

This is actually something I've been thinking of implementing - I have the same issue, and I've been trying to get around it by using different hypothesis groups for different topics, but it's annoying to have to change the group in the sidebar constantly. The filters themselves are quite easy to implement - my main blocker is the index file. Would this file only contain the links generated by the current make run (easy), or will it need to have links based on all annotations (not hard to implement but would mean querying for all annotations on each run anyway)?

[ngirard]

Another thing, which concerns both "publishing to others" and "digesting via Obsidian" workflow.

Once gooseberry make <query> is done, I wish I would tag the concerned annotations, so that I can distinguish the annotations that went through a workflow from the other ones, and only search the latter ones later.

For tagging these annotations with e.g. a done tag, I could use gooseberry tag <query> -- done, but it feels like gooseberry make could gain a dedicated options, such as --then-tag done. Not indispensable, though.

But then, for searching the annotations that aren't tagged done, I'm unsure whether it's currently possible using the --tags option. Reading the CLI help suggests it's not.

[ngirard]

Could you perhaps make an issue for this? Should be an easy fix.

Sure ! Done in #93.

[ngirard]

Would the fix detailed in #54 work for this?

Sure, that's Good Enough ® ! Thanks !

[Ninjani]

But then, for searching the annotations that aren't tagged done, I'm unsure whether it's currently possible using the --tags option. Reading the CLI help suggests it's not.

No, not right now but I'll add this to #92. Will think a bit more about adding the tag option to make though, since it feels like the export won't actually reflect the annotations (since the exported markdown won't have the done tag but the annotations will)

Sure ! Done in #93.

Thanks!

[ngirard]

No, not right now but I'll add this to #92.

Great, thanks !

Will think a bit more about adding the tag option to make though, since it feels like the export won't actually reflect the annotations (since the exported markdown won't have the done tag but the annotations will)

Sure. Designing a good CLI is a process. Better take your time than doing it quick & dirty.

[Ninjani]

Done in v0.9.0!