Thank you for this fantastic plugin! It is an essential addition to Joplin for writing and processing them further for scientific publications.
I have several suggestions to improve the plugin. (But please keep in mind that I am not a programmer. Therefore, I do not know if my proposals are easy, difficult to implement, or feasible.)
- Using standardized short references from the CSL file
Instead of inserting the BibTex Code, I suggest using the short reference as it is defined as the standard way to reference literature in the CSL file.
For instance: Instead of using @arnold_humanities_2016, please use (Arnold & Tilton, 2016).
The proper complete reference for this example in APA 7th ed. is already displayed correctly in Joplin under "References" in the Rich Text Editor (Thank you!):
Arnold, T., & Tilton, L. (2016). Humanities Data in R: Exploring Networks, Geospatial Data, Images, and Text (Softcover reprint of the original 1st ed. 2015 Edition). Springer.
- Link to the complete reference in the note, not to Google Scholar
Again this is the standard way of writing a scientific paper. It would be nice to have a backlink from the complete reference, but I do not know if this is feasible.
- Allow for localization
If I am writing some articles in German, I would like to have "Literatur" or "Bibliografie" as the header in the Rich Text editor instead of "References". Maybe the best way would be to have a preference setting for the content of this header.
- Help users to find their BibTex and CSL files with file dialog windows
Maybe it would be helpful to copy this file under the Joplin User Profile folder so that Joplin would synchronize it?
Hopefully, you have time (and pleasure) to consider these suggestions.
Added 2022-07-28
I want to add some new thoughts I came up with:
-
My suggestions in the previous post are related to the Markdown Viewer (not the Editor). But even though they have no relevance, if you are going to export your notes for a professional (latex-based) publishing tool.
-
In that case, the only important thing is the BibTeX Code that should work in the publishing software so that the reference manager of the publishing tool could get into contact with the bibliographic data.
-
The ideal solution would be a complete integration of Zotero with Joplin, requiring writing a Zotero plugin. I think in the long run, this is the way to go!
In the meanwhile, I suggest the following workaround using the BibTeX Plugin of Joplin:
-
Download the Better BibTeX Plugin for Zotero as @ocns has already suggested and use for the export the option "Keep updated". (See image)
-
Check the format of the BibTeX Code your publishing tool is using. (Often, professional tools use the [Pandoc Syntax].)(Pandoc - Pandoc User’s Guide). In my case (RStudio/RMarkdown), it is the syntax author (in lower case) + year.
-
Set the Better BibTeX configuration to meet the same syntax when exporting references for the Joplin BibTeX plugin. You can find the Better BibTeX syntax here.
See the screenshot:
