Maybe not the only one. As you mentioned above, there are already some plugins using bib file to communicate with Zotero. So they are all local-only I think. But sorry I lack the experience to make any specific suggestion because I didn’t try them myself.
FYI, Zotero recently released a local web API for Zotero 7. Since it follows the web api, should Logseq just be able to easily switch to using the local endpoints? I have never made a feature request before, so I’d appreciate guidance on how to go about doing that. Or making a PR.
Thanks for sharing. I am still using this solution and works perfectly. But maybe this zotero release could improve something in the plugin workflow? Or maybe it is a solution by it self?? I do not know… @hkgnp since you are working on another solution, could you explain what would be the advantages or benefits in comparison with existing solutions? I am quite interested
One benefit would be that the user would not need to install the Zotserver plugin for a Logseq plugin to communicate with, so it’d be easier to use. (You had to install Zotserver to use the plugin you mentioned, right?) In fact, Zotserver isn’t supporting Zotero 7 so far (since it’s redundant), so using Zotero’s own local API is likely the way going forward.
Super exciting! I am having trouble installing it though. I downloaded the zip file from the release page, extracted it, and used “Load unpacked plugin” in Logseq. I got the plugin’s icon to show up, but there’s no setting in the plugins setting page :(. The custom commands also didn’t show up. Do you know if I have to do something else?
Also, curious how you ended up bypassing the CORS restriction. I saw you used the “x-zotero-connector-api-version” and “zotero-allowed-request” like I did. Do you know if that’s what we’re supposed to do? Did you find any source on that?
By the server code did you mean this file? If so, I can see that the headers in questions are checked, but there’s no comment explaining what they are, so I wasn’t 100% sure. Also, doesn’t having “zotero-allowed-request” kinda make the CORS protection pointless? Since a website can just issue a request to localhost and include that header to bypass CORS anyway, right?