sage releases -> DOI number?

105 views
Skip to first unread message

Harald Schilly

unread,
Apr 22, 2015, 6:15:59 PM4/22/15
to sage-release
Has there ever been someone thinking about getting a DOI number for
Sage releases, to make them citable? At least, this page
https://guides.github.com/activities/citable-code/
seems like being an explanation how we could get a citable DOI number
for the sage releases. At least, that's how I understand it.

-- Harald

Volker Braun

unread,
Apr 22, 2015, 7:36:55 PM4/22/15
to sage-r...@googlegroups.com
Sounds good to me. The github integration is probably the easiest way to go about it (instead of uploading tarballs by hand etc).

Emmanuel Charpentier

unread,
Apr 23, 2015, 12:47:12 AM4/23/15
to sage-r...@googlegroups.com
Excellent idea. FYI: the R core team obtained an ISBN for R, making it citable as a book. Not nicely retrievable viadoi:, though.

Pros and contras of each solution ?

HTH,

--
Emmanuel Charpentier

Harald Schilly

unread,
Apr 23, 2015, 5:08:52 AM4/23/15
to sage-release
On Thu, Apr 23, 2015 at 6:47 AM, Emmanuel Charpentier
<emanuel.c...@gmail.com> wrote:
> the R core team obtained an ISBN for R, making it citable as a book.

htey have a nonprofit organization running in the background, which
does among other things also publish a "proper" journal. once we can
pull our resources together and also have a SageMath NPO, we should
definitely do that, too.

>
> Pros and contras of each solution ?

Well, we can do all of those solutions, or even more. Digital data is
happy with being copied around :-)

The benefit with this is, that there is a specific citable release,
which is also archived (supported with funds from EU projects, which
do manage this). that's in my eyes a far better situation than a
general "this version X" without any additional authority.

If nobody objects, I can pull the necessary strings to get this DOI
for the latest sagemath release. Or lets see, if it is really so easy
as it seems ;-)

-- h

Niles Johnson

unread,
Apr 23, 2015, 6:25:02 AM4/23/15
to sage-release

I think the DOI is a great idea!


--
You received this message because you are subscribed to the Google Groups "sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.
To post to this group, send email to sage-r...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Harald Schilly

unread,
Apr 23, 2015, 6:37:00 AM4/23/15
to sage-release
ok, then I'll do it, and I think I've also figured out how to set the
Authorname to "SageMath Developers" instead of claiming that all this
is my own work :-p

Harald Schilly

unread,
Apr 23, 2015, 7:19:45 AM4/23/15
to sage-r...@googlegroups.com
So, here it is:


LaTeX:

@misc{w_a_stein_et_al_2015_17093,
  author       = {W. A. Stein et al.}
  title        = {SageMath 6.6},
  month        = apr,
  year         = 2015,
  doi          = {10.5281/zenodo.17093},
  url          = {http://dx.doi.org/10.5281/zenodo.17093}
}


Markdown code for the README.md

[![DOI](https://zenodo.org/badge/doi/10.5281/zenodo.17093.svg)](http://dx.doi.org/10.5281/zenodo.17093)
It's "just" the Sage library. I saw that it is possible to attach a file on GitHub to a release, then the whole source code tarball would there (I guess). But either way, I think it's a neat thing to have ;-)

-- Harald

William Stein

unread,
Apr 23, 2015, 7:37:38 AM4/23/15
to sage-r...@googlegroups.com


On Thursday, April 23, 2015, Harald Schilly <harald....@gmail.com> wrote:
So, here it is:


LaTeX:

@misc{w_a_stein_et_al_2015_17093,
  author       = {W. A. Stein et al.}
  title        = {SageMath 6.6},
  month        = apr,
  year         = 2015,
  doi          = {10.5281/zenodo.17093},
  url          = {http://dx.doi.org/10.5281/zenodo.17093}
}


Markdown code for the README.md

[![DOI](https://zenodo.org/badge/doi/10.5281/zenodo.17093.svg)](http://dx.doi.org/10.5281/zenodo.17093)
It's "just" the Sage library. I saw that it is possible to attach a file on GitHub to a release, then the whole source code tarball would there (I guess). But either way, I think it's a neat thing to have ;-)

-- Harald



On Thursday, April 23, 2015 at 12:37:00 PM UTC+2, Harald Schilly wrote:
ok, then I'll do it, and I think I've also figured out how to set the
Authorname to "SageMath Developers" instead of claiming that all this
is my own work :-p   
 
 

Maybe it is time to change it to not say my name explicitly either.  The example you list above says me et al rather than the sage developers. 
 

--
You received this message because you are subscribed to the Google Groups "sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.
To post to this group, send email to sage-r...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.


--
Sent from my massive iPhone 6 plus.

Harald Schilly

unread,
Apr 23, 2015, 8:12:15 AM4/23/15
to sage-release
On Thu, Apr 23, 2015 at 1:37 PM, William Stein <wst...@gmail.com> wrote:
> Maybe it is time to change it to not say my name explicitly either. The
> example you list above says me et al rather than the sage developers.
>

Hi, I can change the autor field any time, I just did copy it from the
wiki page for now. I did also change it to "Sage Mathematical Software
System", and not just "SageMath".

updated: http://dx.doi.org/10.5281/zenodo.17093

-- harald

Emmanuel Charpentier

unread,
Apr 23, 2015, 3:47:16 PM4/23/15
to sage-r...@googlegroups.com
Le jeudi 23 avril 2015 13:19:45 UTC+2, Harald Schilly a écrit :
So, here it is:


LaTeX:

@misc{w_a_stein_et_al_2015_17093,
  author       = {W. A. Stein et al.}
  title        = {SageMath 6.6},
  month        = apr,
  year         = 2015,
  doi          = {10.5281/zenodo.17093},
  url          = {http://dx.doi.org/10.5281/zenodo.17093}
}


Markdown code for the README.md

It's "just" the Sage library. I saw that it is possible to attach a file on GitHub to a release, then the whole source release tarball would there (I guess). But either way, I think it's a neat thing to have ;-)

Hmmm... Since (one of the) purpose(s) of a DOI is to enhance reproductibility, the only reasonable attachment would be the whole tarball. (Or, more precisely, this tarball + any standard  package tarball installed in upstream/ : I got bitten by the requirement of the "new" (i. e. git-managed) tarball, that needs to download various source tarballs during compilation : you can't just grab the tarball and get offline... I had to jury-rig something to keem open the damn "corporate-style" proxy that always closes at the most inconvenient moment.)

Other pros : that would constitute a "standard of reference" for Sage's evolution. Easy "citability" might enhance citations.

Contras : Large tarball, that might getr frowned upon by the host repositories. Nice way to stuff sci-hub and pals :-)...

Any way : even without the tarball, a DOI is a great idea. The ISBN is also worth pursuing, IMHO...

HTH,

--
Emmanuel Charpentier
 

Harald Schilly

unread,
Apr 23, 2015, 4:24:09 PM4/23/15
to sage-release
On Thu, Apr 23, 2015 at 9:47 PM, Emmanuel Charpentier
<emanuel.c...@gmail.com> wrote:
> Since (one of the) purpose(s) of a DOI is to enhance reproductibility ...

So, just two tiny comments by me:

1. There are hashsums inside the sage release for the standard
packages, which are part of the git repository and hence the "root
hash" of all this does indeed reference content based hash references
to those packages. Therefore, the reproducibility is in some sense
given … it's just that all those packages are maybe not available.
(Put differently: it's not the case that just arbitrary packages are
pulled when compiling Sage from that release)

2. I don't know much about this zenodo service, but I'm wondering if
there are somewhere hashsums for the zip files available, or even
better: a cryptographic signature for the hash of this. For me, it
looks like as if the zip-file they serve can change at any time and
there is no way to see this.

In any case, yes, I think it's a nice service to have SageMath listed
there and there are also those "community aspects" when scientific
data and tools are pulled together in a service.

-- harald

Daniel Krenn

unread,
Apr 24, 2015, 3:38:12 AM4/24/15
to sage-r...@googlegroups.com
Am 2015-04-23 um 13:37 schrieb William Stein:
> On Thursday, April 23, 2015, Harald Schilly <harald....@gmail.com
> <mailto:harald....@gmail.com>> wrote:
> LaTeX:
>
> @misc{w_a_stein_et_al_2015_17093,
> author = {W. A. Stein et al.}
> title = {SageMath 6.6},
> month = apr,
> year = 2015,
> doi = {10.5281/zenodo.17093},
> url = {http://dx.doi.org/10.5281/zenodo.17093}
> }
> Maybe it is time to change it to not say my name explicitly either. The
> example you list above says me et al rather than the sage developers.

Am 2015-04-23 um 14:11 schrieb Harald Schilly:
> Hi, I can change the autor field any time, I just did copy it from the
> wiki page for now. I did also change it to "Sage Mathematical Software
> System", and not just "SageMath".

Isn't "SageMath Mathematical Software System 6.6" an even better title,
since it contains "SageMath", which should occur "everywhere"?


And, the wiki page

http://wiki.sagemath.org/Publications_using_SAGE

should be updated:

@manual{sagemath,
Key = {SageMath},
Author = {SageMath Developers},
Organization = {The Sage Development Team},
Title = {{S}age{M}ath {M}athematical {S}oftware {S}ystem
({V}ersion x.y.z)},
note = {{\tt http://www.sagemath.org}},
Year = {YYYY},
}

Several things (inconsistencies; similarities to previous bib-entry)
should be dicussed:

- We have an "Author" and an "Organization" field; both sound similar,
but are somehow different; ideas how to handle this?

- "SageMath Mathematical Software System" (like in doi) vs. "SageMath
Mathemathics Software System" (like in old bib-entry + (Sage->SageMath))

- Version Number: "...System 6.6" (doi) vs. "...System (Version 6.6)"
(old bib-entry)


Best wishes

Daniel

Jeroen Demeyer

unread,
Apr 24, 2015, 4:30:40 AM4/24/15
to sage-r...@googlegroups.com
On 2015-04-23 21:47, Emmanuel Charpentier wrote:
> Or, more precisely, this tarball + any standard package
> tarball installed in upstream/
The Sage source tarball should contain all tarballs for standard
packages in upstream/. If this is not the case, that's a bug.

Jeroen.

Luiz Roberto Meier

unread,
Apr 24, 2015, 4:35:06 AM4/24/15
to sage-r...@googlegroups.com
The new feature, oops, bug is the show() command in 6.6 . Simply don't render correctly the output. The same command and examples still working in version 6.5. I've used a fresh Ubuntu and Fedora latest installation.



Jeroen.

--
You received this message because you are subscribed to the Google Groups "sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.
To post to this group, send email to sage-r...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.



--
Luiz Roberto Meier

[...] The energy released by the loss of one phosphate is equivalent to heating the enzyme up to 7,000 degrees Fahrenheit. (ATP --> ADP)
--

Harald Schilly

unread,
Apr 24, 2015, 4:43:39 AM4/24/15
to sage-release
On Fri, Apr 24, 2015 at 9:38 AM, Daniel Krenn <kr...@aon.at> wrote:
> Isn't "SageMath Mathematical Software System 6.6" an even better title,
> since it contains "SageMath", which should occur "everywhere"?

Back in that re-naming thread, I did argue that the duplicate "Math
Math" in the long title is a bit silly. One time is enough, and hence
the short for is a run-together of the long form.

>
>
> And, the wiki page
>
> http://wiki.sagemath.org/Publications_using_SAGE
>
> should be updated:

yes, it should. I also don't know how to call the authors: "SageMath
Developers", "... Authors", "... Group", "... Team", ... ?

-- h

Harald Schilly

unread,
Apr 24, 2015, 4:44:23 AM4/24/15
to sage-release
On Fri, Apr 24, 2015 at 10:30 AM, Jeroen Demeyer <jdem...@cage.ugent.be> wrote:
> The Sage source tarball should contain all tarballs for standard packages in
> upstream/. If this is not the case, that's a bug.

yes, but this isn't the sage source tarball, hence the ambiguity.

-- h

Nathann Cohen

unread,
Apr 24, 2015, 5:21:21 AM4/24/15
to sage-release
> The new feature, oops, bug is the show() command in 6.6 . Simply don't
> render correctly the output. The same command and examples still working in
> version 6.5. I've used a fresh Ubuntu and Fedora latest installation.

A related discussion on #18289:
http://trac.sagemath.org/ticket/18289

Nathann

leif

unread,
Apr 24, 2015, 5:27:49 AM4/24/15
to sage-r...@googlegroups.com
Task force.


-leif

Nathann Cohen

unread,
Apr 24, 2015, 5:28:43 AM4/24/15
to sage-release
> Task force.

"The Sage guys"

Nathann
Reply all
Reply to author
Forward
0 new messages