@andupaz great comments. I am just giving ideas here, not making any decisions, but I absolutely agree with your comments. From my point of view, this would be the ideal end result of the integration:
- Logseq has a way to cite Zotero items
- Cite by searching for name etc.
- Cite selected items in Zotero
- go to Zotero window, select all the items desired, then run command
- this is useful to cite e.g. a bunch of related items in Zotero
- Cite last n items added to Zotero
- this will speed up things a lot, if I add 3 articles to Zotero via the connector, I can immediately add them to Logseq (where probably most of the work will be done), without doing a 2nd search.
- Once the articles have been added to Logseq, their functioning is independent of Zotero
- The only coupling back into the Zotero-world is via zotero://select links
- pdf files are directly linked (i.e. not via a webserver through Zotero)
- This means, if Zotero is removed at this point, everything will continue to work
- If the local Zotero-api ever stops working, we can switch the citing mechanism to a .bib file based system
- The link Zotero → Logseq is done by adding linked items to Zotero
- Every time an item is cited in Logseq, it calls the Zotero to add a linked attachment to the markdown file
- If Zotero goes down, this feature will fail, but it is no big deal. There could be a routine to create the links after the fact once the Zotero issues have been fixed.
Does that make sense from your point of view?