Zotero to CiteDrive
CiteDrive creates a public (shareable) API for .bib files. It would be cool if I could connect Zotero to CiteDrive and "push" some collections to be replicated as CiteDrive projects, which I could then share with my colleagues. This sounds like an interesting Zotero Extension idea, but perhaps something which could be considered for Zotero cloud solution?
References: CiteDrive https://www.citedrive.com/docs/quick-start/
References: CiteDrive https://www.citedrive.com/docs/quick-start/
If there's a specific feature you want in Zotero, you'd have to say what it is.
------
title: "My cool paper"
author: John Doe
bibliography: https://api.citedrive.com/bib/e11efd6c-8176-45d5-9491-69fbcaa12ac3/references.bib?x=eyJpZCI6ICJlMTFlZmQ2Yy04MTc2LTQ1ZDUtOTQ5MS02OWZiY2FhMTJhYzMiLCAidXNlciI6ICIyNzM1IiwgInNpZ25hdHVyZSI6ICJiYWQ0NmE4YzYyOGNkZGM0NDgxY2FhYmExNzQ1MGQ4MGUxYTNhMGE2ZDFiNjJjZjZhOGM3MjA3MmYzNjQ1OTQ0In0=/bibliography.bib
--------
The body of the document
As I said, it may not be of core interest to Zotero team to modify the API, so I thought someone might be interested to develop an extension, which would push part of my library to CiteDrive to be then exposed via the URL.
But I don't quite understand the use case. This seems significantly worse than just putting the BBT (or R-Studio) -generated references.bib or references.json file in box/Dropbox/Drive/github and linking to that? Going through citedrive involves two APIs and Citedrive reconstitutes the bibtex, as I understand it, so lots of potential for things to break.
If someone wanted to develop something, though, the natural place would be on the Citedrive end of things: OAuth with the Zotero API and pull in whatever content you specify.
For something like a share link to a specific collection in an otherwise private library, that doesn't exist, but it's something we've long generally planned to add. And that's my point about the framing here — if there's something you want Zotero to do, you should just ask for it.
But as adamsmith says, just using a BBT-generated file is a much more common approach here.
> just putting the BBT (or R-Studio) -generated references.bib or references.json file in box/Dropbox/Drive/github and linking to that
This seems to be the DIY citedrive solution I should look into. I don't like making my entire library public. I also would like the file to be updateable, as I develop the draft. So automatic generation via RBBT and subsequent uploading to the cloud service seems to be a plausible solution. Thank you all for your tolerance to my misguided question.