Yes, that is correct.
The way the updating works at the moment is that the code keeps the existing note (if this exists), over-writes everything above the “## Notes” (in the next version) or “## Extracted Annotations” (in the existing version). Basically everything above is over-written, everything below is updated. A more flexible structure like the one you outlined (with some metadata at the top and some at the bottom) would be desirable but to implement it I will need to rethink how the updating of the note works.
I’m adding the feature to allow importing comments stored in Zotero, and it will be part of the next version.
The way the updating works at the moment is that the code keeps the existing note (if this exists), over-writes everything above the “## Notes” (in the next version) or “## Extracted Annotations” (in the existing version). Basically everything above is over-written, everything below is updated.
In case I am not the only one that got confused by the updating process, this would be a great way to summarise it in the readme on github.
I’m adding the feature to allow importing comments stored in Zotero, and it will be part of the next version.
Great!
I cannot replicate the issue (it behaves as planned on my end). Could you open an issue on GitHub and export from Zotero the json with one or more sources that are not behaving as planned?
on zotero select the source you are trying to export → right click → export item → create Better BibTex Json with only that source. No need to send the entire bibliography
I set import path for json file which exported from Zotero, and export path correctly( i suppose every setting is OK /LoL),but it does not work,the plug in is the latest version.
I really love this project - thank you. I am starting to heavily use this plugin now
how can I pay you?
also can you show me where to find a copy of the “admonition” template in markdown with the placeholders it uses so I can tweak it to make my own custom template?
also (I am new) can Dataview query/tabulate the metadata section, or do I need to duplicate some of the fields in the top YAML section for Dataview to work?
Hi @stpag, do you have an idea of when you will release the new version of your plugin this week? It’s to know more or less so that I do not change my workflow too much until the new update
The admonition template is currently stored here.
You would have to remove the quotation marks, the “+” and replace \n with a new line. I will upload a md file next.
Dataview accepts both values in the yaml or inline fields (Data Annotation - Dataview). You can either add a yaml to your template or simply tweak the template so that it accepts inline fields (e.g. author:: {{author}}
I have introduced quite a lot of changes (see changelog) so I want to do a bit more testing before I release it. Probably towards the end of the week. But none of the changes are breaking changes.
only add non-overlapping sentences (“Save Entire Note”)
Will this make it possible to only update the notes section? and have a a separate manual summary section or added metadata section (not one filled in by zotero, but one filled in manually, for example to set the type of study::, a quick summary::, etc, with inline datafield)
Yes, it will allow you to place a marker (e.g. a heading) to specify the beginning and the end of the section that will not be over-written.
And it will be possible to have a separate manual summary section that will not be overwritten (if placed below the marker)
another very important question for the community - I have created a custom template I am happy with - if I update your plugin by overwriting the folder with your new content, will it wipe my custom template/settings?
Somehow in the back of my mind I thought that spaces and non-alphanumeric characters were not allowed in the name of a note. I have corrected this in the version that I will release later this week
