Open TheCedarPrince opened 1 year ago
This relates to an interesting idea I had based on my note system - building the bibliography based on linked documents that are mirrors of Zotero data. (That‘s how I build bibliography references in my vault - using links to notes which are named after their BetterBibTex keys).
Interesting @SevorisDoe ! Why do you do that? Could you explain more?
But yea, I used to have this functionality set up for my notes at one point but it was not as robust as I can make it now. I’ll sketch out the full requirements for hacking here shortly. Planning to get to this sometime today to draft a couple prototypes on a new branch.
So basically, when I reference things from Zotero, I use a plugin to build a local Markdown note mirror of the Zotero entry in my notes workspace. I then reference that Markdown file. The advantage is that I have a link (which gets properly parsed by all the various other markdonw notes tools) and I have a single point of truth in my notes about the Zotero entry. I can also quote-transclude any highlights I have made in PDFs. So overall it is just a very powerful way to fully intregrate things.
The result is that you have this mutliple-note ontology: A note referencing a Zotero entry contains a wikilink with say [[2023ANeatCitation]]
as the link. If you want to interpret that forward into a citation embedding in the NoteMate sense, you can use the format of the link or the location of the note (it rests in a Zotero folder) to know what info you have to query from Zotero to then build a human-readable citation string.
That is a special kind of multiple-note ontology, where another note contains the information for a literature citation used by another note.
A different ontology may be my ZK system, where I have fleeting, permanent, literature (my own words, so distinct from highlight extracts) and creation notes as the big information carriers in the synthesis sense. If we say, parse out creation notes of a specific type to NoteMate, we might interpret the linked fleeting notes as inspirations and pull them into the NoteMate output.
I am sure other multiple-note formats can be envisioned. One more idea I can name right now is that some user approves workspace content for publication by creating and filling out a "garden pot" note that contains title and sumary and what other note(s) to pull form for the note body (in the process strippint out intra-workspace information that may be before and after the content you want to publish) and then NoteMate interprets the ontology thusly to create one output note .
One note should be able to be pulled from a knowledge base and then turned into a single note which recursively pulls linked notes from within the original document into a single document. This should not be too hard to make but needs a bit of checking and some dedicated development. Ideally, the functionality should have a recursive depth limit. Then, the table of contents should be created in the final document dependent on that.