Skip to content
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

no doi in bibliography #9

Open
pdebuyl opened this issue Jul 9, 2020 · 16 comments
Open

no doi in bibliography #9

pdebuyl opened this issue Jul 9, 2020 · 16 comments

Comments

@pdebuyl
Copy link
Member

pdebuyl commented Jul 9, 2020

Hi @rougier

I notice that there is no DOI in the article's bibliography.

I usually make sure that all references have a clickable DOI, which is also useful to verify the references.

Changing "doi = false" to "doi = true" in rescience.cls 's biber settings fixes it. Should I do that?

@rougier
Copy link
Member

rougier commented Jul 10, 2020

It's on purpose in order to make the title clickable. This redirects you to the paper using the doi.

@pdebuyl
Copy link
Member Author

pdebuyl commented Jul 10, 2020

I am preparing ReScience C 6, 1, #11 and the titles are not clickable. The papers that have a "url" or a "eprint" filed display a clickable url, the ones with "only" a doi cannot be clicked.

I use debian with texlive 2018.

@rougier
Copy link
Member

rougier commented Jul 10, 2020

Can you give me a link to the repo?

@pdebuyl
Copy link
Member Author

pdebuyl commented Jul 10, 2020

ReScience/submissions#41

@pdebuyl
Copy link
Member Author

pdebuyl commented Jul 10, 2020

I also took the most recent versions of yaml-to-latex.py rescience.cls from the template repo

@pdebuyl
Copy link
Member Author

pdebuyl commented Jul 13, 2020

From https://tex.stackexchange.com/a/23843/71116

This seems to do it:

\newbibmacro{string+doi}[1]{%                                                                                                                      
  \iffieldundef{doi}{#1}{\href{http://dx.doi.org/\thefield{doi}}{#1}}}                                                                             
\DeclareFieldFormat{title}{\usebibmacro{string+doi}{\mkbibemph{#1}}}                                                                               
\DeclareFieldFormat[article]{title}{\usebibmacro{string+doi}{\mkbibquote{#1}}}                                                                     

@broukema
Copy link

broukema commented Jul 13, 2020

I would prefer \ref{https://oadoi.org/\thefield{doi}{#1}} rather than \ref{http://dx.doi.org/\thefield{doi}{#1}} - the https://oadoi.org domain chooses open-access versions of an article, preferring publisher versions (gold open access) if possible, otherwise preprints (green open access), and only falls back to the paywalled version if nothing open-access (gold or green) is available.

It's also better to use https systematically rather than http: a small step towards privacy mainly implemented on a mass scale thanks to Ed Snowden.

This is another long-term issue about open access, so I don't expect unanimity on this suggestion for the official version. For example, I haven't checked how long the oadoi.org domain name and service can be reasonably expected to be sustained.

Meta-level comment: It's highly positive that public discussion between author(s) and editor(s) exists for this journal, in contrast to conventional journals, where an author or an editor can give an unreasonable request or answer and only a tiny handful of people have any opportunity at all to judge the validity of the arguments and any decisions taken.

@rougier
Copy link
Member

rougier commented Jul 16, 2020

I didn't know about the oadoi.org service and we could probably use it instead of the regular dx.doi.org. Since there might be future problem if the site is down, maybe we can have the actual DOI to be printed in the reference but with a link to the oadoi service. If the service is down in the future, at least people can use the plain doi ( Imean, without having to exract it from the url). @broukema Can you make a PR (in the articles repo) ?

We also need to find a way to update the template on GitHub and overleaf automatically.

@pdebuyl
Copy link
Member Author

pdebuyl commented Jul 17, 2020

@rougier in the last paper you edited, the links are missing as well (Upshall & Shifman). Would you like a PR for the snippet above?

@broukema
Copy link

hi @rougier, @pdebuyl

@rougier I don't quite follow PR (pull request?). I assume you meant for me to update my article with these changes - so here's commit d4cc1fc
broukema/RBG08_rep@d4cc1fc
https://codeberg.org/boud/RBG08/commit/d4cc1fc97ab4e38e4b798fc2b0e4ed8c0e60a478

@rougier
Copy link
Member

rougier commented Jul 23, 2020

@broukema Sorry, I was not clear. Yes, PR mesn Pull Request. And I was taliking about changing the ReScience template (not only yours) such that future submission make use of the alternate source for findnig DOI. But now I realized this might ned some work for making the DOI apparent in the bibliography. I'll need to investigate.

@pdebuyl
Copy link
Member Author

pdebuyl commented Jul 23, 2020

@rougier have a look at @broukema 's paper https://zenodo.org/record/3956058 it has visible doi's.

You can cherry-pick the commit broukema/RBG08_rep@d4cc1fc that contains the modification to rescience.cls

@rougier
Copy link
Member

rougier commented Jul 28, 2020

Oh great, this is definitely something we can re-use for the official template. @broukema, care to make a PR?

@broukema
Copy link

@rougier Done.

BTW, adding the 03 and 04 tags over at ReScience/submissions#41 might help convince the ArXiv moderators that my paper is accepted and published. That's probably not the only criterion they're thinking about, but it may help.

@rougier
Copy link
Member

rougier commented Aug 3, 2020

You mean you had problems with ArXiV when you submitted ? Tell me if I can help.

@broukema
Copy link

broukema commented Aug 3, 2020

@rougier - I'll answer over at ReScience/submissions#41 to keep the discussion focussed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants