I recently found logseq and it seems to fit my needs quite nicely. However, there is the only drawback that it seems to not work that great if you already have a lot of information stored in JabRef.
A usecase for me would be literature search, where I find it easier to collect thoughts in logseq than it is in JabRef. I found the
logseq-citation-plugin which allows me to load a bib file and link to files, but unfortunately, the new format for the file entry does not really work with that plugin - but maybe that could be fixed on either side: I already created a bugreport for the plugin, but I wonder if it is possible to configure Jabref to write simply the filepath and not the description and filetype?
Any ways, I wonder if someone here is using JabRef in combination with logseq and might want to give me some more ideas what workflows work and how it can be configured?
I’m using logseq now for a month and I still like it. I also tried obsidian, but personally I like logseq a bit more - I think everything works a bit more fluent for me there.
The bibtex integration works, but there are a few things that do not work that well:
- If you link the library to the folder the plugin requires, the plugin can no longer automatically re-index the library, when the bibtex file changes.
- The plugin has a weird search field and you can, for example, not search for the citation key
- I have not figured out how to link the files - it is possible, I have manually tried it - but from the plugin it does not work, because jabref stores more information than just the file path
Some thoughts, or ideas that could solve some of these problems:
- an export option in jabref would be nice, to automatically store the library on-save somewhere else too
- this export option should also allow to overwrite or normalize certain fields, such as the filename field (an option to export there the absolute path without the metadata would be nice)
Would be nice to hear some thoughts of other logseq+jabref users!
I tried, but at that time relative paths did not work, so you’d have to copy all files into the assets/ folder. Similar to this issue: Relative path for Zotero data directory - Feature Requests - Logseq
Yes, I have the same issue. Relative paths do not work and it looks like all trailing path components like
.. are stripped from the path.
I found out you can circumvent this, by using something like this:
![does not work file path](file://../../papers/files/MyPaper.pdf) # gives an error :(
![hacky file path](file://assets/../../papers/files/MyPaper.pdf) # weird that this works...
I have the following structure on my disk:
\--- references.bib # JabRef library
\--- (all PDF files)
\--- ... # All other logseq stuff
But unfortunately, I have not figured out how to automatically link the file path from the citation plugin, as the Jabref metadata in the
files field interferes with the path as noted above…
That path issue is a shame. Otherwise Logseq is an amazing program.
Are you also using this plugin? GitHub - sawhney17/logseq-citation-manager
I think this is what I tried, but there is also direct Zotero integration, but it only works with the Zotero web server. Comprehensive Zotero Plugin - Plugins - Logseq
The plugin above was designed to work with Zotero exported .bib files, are they not the same as Jabref bib files?
Yes, that’s the one I’m using too.
I opened a feature request on github as well: parse JabRef file entries · Issue #44 · sawhney17/logseq-citation-manager · GitHub
I guess the bibtex formats are not different between zotero and jabref, but the difference is in the