Change doi to oadoi in CSL
I am trying to tweak a citation style to output oaDOIs rather than simple DOIs. I have changed
text variable="DOI" prefix="https://doi.org/"/
to
text variable="DOI" prefix="https://oadoi.org/"/
in the relevant style. The output in Word shows https://oadoi.org/10.1093/ecco-jcc/jjx002.517 but only links the actual DOI portion, and still links that through doi.org (ie in this example the link from 10.1093/ecco-jcc/jjx002.517 leads to http://doi.org/10.1093/ecco-jcc/jjx002.517). How can I fix this?
text variable="DOI" prefix="https://doi.org/"/
to
text variable="DOI" prefix="https://oadoi.org/"/
in the relevant style. The output in Word shows https://oadoi.org/10.1093/ecco-jcc/jjx002.517 but only links the actual DOI portion, and still links that through doi.org (ie in this example the link from 10.1093/ecco-jcc/jjx002.517 leads to http://doi.org/10.1093/ecco-jcc/jjx002.517). How can I fix this?
So I'm not too keen on adding this. I didn't realize citeproc had a hard-wired hyperlink for the DOI now, though?
https?://.+
, but not doi.org. This is going to be rare, but I could see other cases e.g. where people want to specifically route through the CNKI DOI service. Not sure if those warrant a change or if that's getting too in-the-weeds.Does citeproc-js do anything for other URLs generated using a prefix? E.g. when I do
<text variable="PMCID" prefix="https://www.ncbi.nlm.nih.gov/pmc/articles/"/>
what does it do?On CKNI etc, is the domain of a DOI implicit in the number? If so, we could do something with that. Otherwise, forcing a single domain on everything is a risky heuristic. Splintering standards are a real headache. Bah, humbug.
Happy for guidance on what IDs to add to the family and other tweaks!