If I had all the books I’ve read in Logseq, I could just go to the relevant tag page to see everything tagged with a given tag, or use Logseq queries to retrieve lists certain types of things (e.g. Keeping lists of book recommendations by subject/tag. This is already duplicated with my use of Zotero. Keeping track of books (and other things) that I have read. I’ve already moved this to Logseq with item-type::book and status::want-to-read properties. Keeping a list of books that I want to read. Once I configured it, all I have to do is go through and create an entry for each book that I have notes for in Zotero, and it pulls everything right across, including the notes. This does mean that the Logseq page for each book will duplicate some information that will also be in Zotero, which isn’t ideal, and so if I didn’t care about real references and citations, I could just ditch Zotero, but I do, so I won’t.įor getting data in from Zotero, it turns out that Logseq’s built-in Zotero integration works just fine. Now with just about everything else in Logseq, it makes sense to keep using Zotero as a reference, citation and bibliography manager and move my page-by-page research notes into Logseq. Zotero was really not a great place because I don’t spend any time ‘in’ Zotero. In that past, whether I kept these research notes in Scrivener or Zotero, they were separate and unlinked from my other notes. As I noted in my last update on writing tools, I often take detailed notes on books that I read so that I can search and reference them later.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |