I understand Zotero is going to be dropped from LogSeq DB edition as a built-in feature; this makes me pretty sad, especially since there doesn’t appear to be a commitment to even continuing support through an official plugin . Is this because there is already a reliable community-supported plugin that will support DB? Otherwise, it’s difficult to understand why such a useful feature would be left out.
Even after finding the section addressing Zotero in the unofficial DB FAQ, I feel this change is significant enough to warrant its own dedicated discussion rather than being tucked away in an FAQ. The community’s response (or lack thereof) could also provide valuable insight.
Is Zotero integration not widely used by other users? I personally rely on it extensively—how about others? Even with fantastic community developers like benjypng stepping in, it’s a bit disheartening to see what was, in my opinion, a prominently advertised built-in feature like Zotero integration become deprioritized.
I agree that Zotero integration is pretty essential for scholarly work with LogSeq. But I also understand that the dev team is under pressure to simplify the codebase, given the scale of the rewrite of the codebase.
It looks like benjypng hasn’t replied yet to the question of will he continue to develop the local Zotero plugin for the DB version. But @Flan’s message above implies that maybe that is happening? (Edited my original post to add that according to the unofficial DB version FAQ, benjypng will indeed update the plugin. That’s great news!) Any other efforts at implementing Zotero support for the DB version?
The zotero integration as a first party citizen or something close to it was a killer feature why I was able to choose logseq over obsidian. Though everyday I have to use it I envy the obsidian world for their two way sync of notes.
there’s also this repository which seems to be an alternative to the one from benjypng: GitHub - e-zz/logseq-pdf-extract: Import Zotero into Logseq, extract text or area Highlights into block.
I haven’t tried either, but the latter from e-zz looks a bit more planning ahead.But I would love this or something similar to become a plugin with official support (including testing and fixing for every new version).
. Is this because there is already a reliable community-supported plugin that will support DB? Otherwise, it’s difficult to understand why such a useful feature would be left out.