github-actions[bot]
commented
3 weeks ago Hello @m-walters,
@retorquere is ready to assist you with Better BibTeX. In order to do so efficiently, a debug log is generally required. The information it containst is key to him understanding, replicating, and resolving your issue. If you have shared a D<number> log, those go to the Zotero team, @retorquere cannot access those.
Here’s how you can share your debug log:
- If your issue involves specific references, citekey generation, or exports, right-click on the relevant item(s) and select "Better BibTeX -> Submit Better BibTeX debug log" from the menu.
- For issues where items do not play a role, follow these steps:
- Restart Zotero with debugging enabled (Help -> Debug Output Logging -> Restart with logging enabled).
- Reproduce the problem.
- Choose "Send Better BibTeX debug report..." from the help menu.
After these steps, you will receive debug ID displayed in red. Please share this ID with @retorquere in this issue thread. If your query is about an export, include both the actually exported result and your expected/desired outcome.
Sharing your debug log gives @retorquere a view of your Better BibTeX configuration and the elements contributing to the issue. This helps him address your concerns more efficiently.
Thank you.
PS: If the Debug Log menu is not available, or if it fails to send the debug log, you can use the option under “Help” > “Send debug log to file.io”.
m-walters
retorquere
Debug log ID
none
What happened?
I'm pretty new to this utility, but already I've encountered something that I think many others might appreciate. I have a bib export for my Obsidian use. And I have a new one for my manuscript. For my manuscript, I don't need that as many bib fields (don't need the
urldatedate accessed, etc.), but for Obsidian I like more details.It would be handy to be able to create different exporting templates/profiles to fit different contexts.