Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Each citation is added to a formatted JSON file when it is first seen. After this it stays the same. This means you can fix the citation data by hand by just editing the JSON file. You should include the JSON file in your version control. An example is here [1]

Of course this might not be as comfortable as a GUI editor like Zotero, but I think I still prefer doing some small tweaks to a JSON file vs. the problems I've had in the past with Zotero exporting. The auto-export didn't always work consistently, and Zotero has many features that I don't need at all that make the whole thing more complex and fragile. Even collections are somewhat confusing to work with - I've often added citations to the wrong collection because it always adds to the currently open one, and then had to spend time to find it again. You also can't know which references are actually used and which aren't.

And I pretty much always gave up as soon as someone else needs to work on the same paper, which then leads to managing the .bib file by hand anyways.

[1]: https://github.com/phiresky/pandoc-url2cite/blob/master/exam...



FTR, Direct ink to raw `Source README.md`[0] is correct, but direct link to `Result README.pdf`[1] should be corrected.

Should be: https://raw.githubusercontent.com/phiresky/pandoc-url2cite/m...

[0] https://raw.githubusercontent.com/phiresky/pandoc-url2cite/m...

[1] https://github.com/phiresky/pandoc-url2cite/blob/master/READ...


Thanks for this. Just a quick follow-up: if I use the same reference in different papers, do I need to make those changes we were discussing on each per-paper json file, or is there a way to do them once and for all?


Well, you can use the same json file for multiple documents.

By default it will be stored in the directory from which pandoc is invoked, but you can also change that by setting `url2cite-cache: filename` in the markdown frontmatter or in the pandoc invocation: `pandoc -M url2cite-cache=../bla.json --filter ...`.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: