Replies: 5 comments
-
When you embed an image to a note, Zotero will encode it to base64 to display. I’m not pretty sure how this works but it is possible to happen when there are too many images in a note. Besides, Zotero has a note length limit for syncing, we’d better not make them too long. About export a template result directly, I am refactor the code for two path syncing and we will use a different backend to process md/note conversions in the future. We could expect it to be possible. |
Beta Was this translation helpful? Give feedback.
-
Besides, the more I dive deeper into the Zotero note in richtext, the more shortcomings and limitations I find with it. Maybe in a further future, we could migrate to a pure md note system. |
Beta Was this translation helpful? Give feedback.
-
Thanks. This is a slightly separate question but it's effectively a workaround for this issue so I hope ok to tag it on here. Specifically, it's fantastic I can export the notes+images, but I would ideally also export the tags and parent itemkey (in an ideal world as a yaml header, but I can reformat for that myself). I can't see the template in the template editor. Is it possible to edit the export-template in better notes? If not, a slightly kludgey approach, in the |
Beta Was this translation helpful? Give feedback.
-
With the new export backend, the tags are automatically added to the YAML header. The memory bug (haven't tested it, suppose it is a bug) may not be solved as it's not a common use case and is hard to track. If no updates, I'll close this issue. If you think this thread would be helpful to others, converting it to a discussion would be better. Thanks for the feedback! |
Beta Was this translation helpful? Give feedback.
-
@windingwind thanks! The YAML header on the notes is fantastic, and seems a great workaround. I think this is likely to be useful to others, so may be good to convert to a discussion (or/and, to link to the closed issue from the template that compiles from tags). Thanks again |
Beta Was this translation helpful? Give feedback.
-
Describe the bug
On running a template I'm getting a 'not enough memory resources are available to process this command' error, with a failed to encode base64 data (this is a template with annotation images).
To Reproduce
Steps to reproduce the behavior:
I tried running the template in blocks of ~50 items a time, and this definitely helped, but I guess the first blocks are still live links so perhaps that has an impact on memory (I'll try unlinking them maybe, or run the chunks in multiple separate notes).
Desktop (please complete the following information):
Additional context
I wonder if it would be possible to do something like 'send template to export', to run a template that writes an external file?
Alternatively, whether the 'export' function could be modified in some ways to make use of some of the benefits of better notes, e.g., at the moment they don't include tags or parent item metadata, but these could be included (ideally as yaml headers), and then users can work with an external note taking tool.
Beta Was this translation helpful? Give feedback.
All reactions