-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Encourage use of CSL-JSON #387
Comments
Yes, I fully agree. This is also an issue I have considered for How do you want to encourage the use of JSON? It seems this would be an issue for the manual, no? |
For example by including an example "references.json" instead of "references.bib" in the template |
That's what I also had in mind. Unfortunately, it seems like the |
Thanks for chiming in, Daniel. A quick thought: While CSL-JSON is preferred over BibTeX because it's not lossy, BibTeX is far more widely used and available. I fear that if we use CSL-JSON in the example, which is one of the first things a new user will look at, it may be off-putting. I know Zotero allows CSL-JSON export, but I think other commonly used reference managers (e.g., Citavi, Papers, Endnote) do/may not. But I would be happy to add a comment to the YAML that encourages use of JSON. We should definitely mention this in the manual, though. Marius, I think you are right. The references that we generate for the used R packages are only available in Bib(La)TeX-format, so we would need to convert them somehow. |
As can be seen in this pull request, it is best to use CSL-JSON compared to BibTeX. Does this also apply to
papaja
, and should we also encourage usage of CSL-JSON in the documentation and the template? Better CSL-JSON is provided by the Better BibTeX Zotero PluginThe text was updated successfully, but these errors were encountered: