I have created a simple Zotero translator that creates a markdown link to your Zotero Item when quick copying (drag and dropping) the item into obsidian.
I use Zotfile plugin to put all my files in Zotero to one folder in dropbox to sync between computers ( I have over 5gb pdfs, so this is more than free Zotero account allows to synce )
Then I use this plugin from post above Zotero best practices to link the item from Zotero to Obsidian database;
I can’t argue with that! My only point is that moving and relocating things in Zotero is a painful process, and for most people Zotfile will do a much better job. I’m sorry that’s not the case for you!
I don’t know what you’re referring to. Using Zotfile it’s possible to create some structure based on the wildcards it supports, and it’s possible to add some of the metadata in the filenames. It might not work for your particular use case, given that you’re using it for things other than references and other types of files, but it is also not impossible.
Having said that, there are indeed limitations (not possible to organize folders based on collections) and yes, if Zotero eventually dies, that collection “classification” will die with it.
My strategy for that is encoding everything with citekeys: I have a bib file for my entire library, so I know what the citekey is with respect to the paper. My naming convention for my notes usually includes the citekey (or links or references it). Because the export with mdnotes, I now also have information about the collections in my notes. And because my Zotfile-generated folders also have the citekey, I’m not too worried about not being able to find stuff.
Can you elaborate a bit more about this strategy? I am still exploring the ideal strategy for how to organize my small library of pdfs. So I am interested in other people’s way of doing things
Can you briefly expand a bit more on your system? My issue with typical folder hierarchy is that it kinda forces a file to only have 1 direct parent (i.e. the folder) or ancestry (i.e. the folder path)
Sometimes you come across a pdf or some document and it hits on several topics e.g. maybe an article may be related to topic A, B, and C. And also relevant to your projects X, Y, and Z.
Before Zotero and Obsidian, I wonder whether I should have a storage hierarchy independent of the topics and projects or I should simply duplicate the PDFs and put the copies in the relevant topic and project folders.
Now, I am thinking of just having a flat folder hierarchy to store the PDFs and yet remain accessible to Zotero and/or Zotfile. Then perhaps using @argentum plugin for mdnotes create a md reference to that PDF. Then the individual markdown notes for topic A, B, C, and projects X, Y, Z, all have links to the md note of that PDF.
So your experience may help me decide one way or another. Or perhaps even another completely different way of organizing
I store sources in a physical archive like way, starting with the largest entity and narrowing down to the date and name of the document.
i.e. : Repositiory of original/type of archive/main name of source/date and name of sub-source/document name/
Do you also create a canonical md file pointing to a paper in PDF format?
I suppose you store your PDFs this way
PDF in Sources/Documents/PDFs/YYYY/YYYY-MM/YYYY-MM-DD/Zotero-name-of-the-paper.pdf
Then in the Zotero, you do a Attach Link to File right?
I changed the renaming rule to include the citekey, instead of making it a subfolder. This means that my file will be renamed <citekey>-<title of paper> (you can see the example at the very top):
What this means is that for a paper by John Doe, published in 2020 at the conference of Cool Zotero Settings (CZS), I’ll get a citekey like this: doe2020czs.
I’m using the citekey as title setting in mdnotes, so the filenames of all the files exported from include doe2020czs. I can then search my harddrive for doe2020czs, and all the files related to this paper will show up. In Obsidian, I try to follow the same naming convention.
This is just the way it works for me, but Zotfile offers a lot of flexibility depending on the wildcards that you use and work for you.
From the screenshot itself, I’m not sure what could be wrong. Sorry, I’m not on MacOS so I can’t really help you debug there since I don’t have much experience with what works there. Not sure what PDF viewer you are using to annotate, but Foxit reader messes it up in Linux. My suggestions would be:
