Re: [release planning] Enable Zenodo before 7.8.6 and 8.0.0
Vaclav Petras <[email protected]> Mon, 31 May 2021 15:25:16 -0400
| Newsgroups | gmane.comp.gis.grass.devel |
|---|---|
| Message-ID | <CABo5uVu9uOFKw0cxCWcdjr+7KYXMPL1PwgwDbHQwqHF9VyJKnw@mail.gmail.com> |
--===============5812379419563888453== Content-Type: multipart/alternative; boundary="00000000000068411305c3a5300c" --00000000000068411305c3a5300c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Dear all, Zenodo-GitHub link is enabled. There is nothing to see or customize on Zenodo.org until a release happens. It is important that every release is a GitHub release rather than just a tag, but other than that, it will work automatically. I won't be creating .zenodo.json right away, but will probably wait until 7.8.6 or 8.0.alpha happens to see how good or bad the metadata is. Then we will see what priority to assign to creating .zenodo.json. Best, Vaclav On Mon, May 24, 2021 at 9:06 PM Vaclav Petras <[email protected]> wrote: > Thanks everyone for the support. > > I was able to identify some potential issues. Namely, the auto-generated > metadata on Zenodo does not seem to be that great and that includes basic > things like title and license. How an author list will look is hard to sa= y > without trying, but it is promised to be sensible. It seems that a lot of > projects just solve this using a .zenodo.json configuration file which > includes this info, e.g. a full author list. > > Although these metadata issues are certainly visible, a DOI will be > generated and usable by itself in any case. Additionally, metadata can be > edited manually after the publishing/release. Finally, having .zenodo.jso= n > is doable (probably through CITATION.cff which would be good to have > anyway). Thus, I don't see this as a blocker, just as something to resolv= e > on the way. > > On Mon, May 24, 2021 at 1:27 PM Stefan Blumentrath < > [email protected]> wrote: > > >> There is already a GRASS GIS community on Zenodo, managed by Pietro. >> >> There are way more GRASS related records in zenodo than registered in >> that community. Wound probably be useful to register relevant entries in= a >> GRASS community... >> > > There seems to be exactly n-1 GRASS-related records not in the community > (where n is all the GRASS-related records). Are we looking at the same on= e? > > https://zenodo.org/communities/grass/ > > >> >> Would it be an option to develop the community in that direction, Pietro= ? >> If others too think that's useful ... >> >> Cheers >> Stefan >> ------------------------------ >> *From:* grass-dev <[email protected]> on behalf of >> Veronica Andreo <[email protected]> >> *Sent:* Monday, May 24, 2021 1:48:21 PM >> *To:* Moritz Lennert <[email protected]> >> *Cc:* grass-dev <[email protected]>; Peter L=C3=B6we < >> [email protected]> >> *Subject:* Re: [GRASS-dev] [release planning] Enable Zenodo before 7.8.6 >> and 8.0.0 >> >> +1 from my side too >> >> El lun., 24 may. 2021 03:23, Moritz Lennert <[email protected]= e> >> escribi=C3=B3: >> >> Clear +1 from me. >> >> Moritz >> >> Le 24 mai 2021 03:08:06 GMT+01:00, Vaclav Petras <[email protected]> >> a =C3=A9crit : >> >> Hi all, >> >> Let's enable the Zenodo link before 7.8.6 and 8.0(.0?) releases to get >> DOIs and Zenodo records. >> >> Solving the whole DOI linking and Zenodo archiving for the old versions >> may be complex [1], but enabling the link between GitHub and Zenodo is >> trivial (one click) and every newly created GitHub release (we do those) >> will be automatically registered and receive DOI. >> >> Zenodo uses a system of DOI versions and a main DOI (Concept DOI). >> Whether it is an ideal system, that's a question, but it is currently th= e >> expected one since it is the same for everything on Zenodo. It is used >> automatically when using the GitHub-Zenodo integration. >> >> It seems I have the permissions to enable it for GRASS GIS. The one who >> enables that becomes a maintainer of it. I'm fine with that, but I won't= be >> uploading any older versions. The maintainer can be changed later by >> contacting Zenodo support [2]. >> >> Although there are things to figure out in terms of next steps, I don't >> see much risk in enabling it. There are no choices available in the setu= p >> or in terms of alternatives. DOI and some kind of registration are expec= ted >> more and more. >> >> Thoughts? >> >> Vaclav >> >> [1] https://grasswiki.osgeo.org/wiki/GitHub-Zenodo_linkage >> <https://eur01.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fgra= sswiki.osgeo.org%2Fwiki%2FGitHub-Zenodo_linkage&data=3D04%7C01%7C%7Cfba8a69= fdf764573335708d91ea9dec9%7C6cef373021314901831055b3abf02c73%7C0%7C0%7C6375= 74537213313936%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIi= LCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3DhCfCxTMHSG5PluYrYfies7ZWg9F3h= CSM%2B1aC8WzgD4E%3D&reserved=3D0> >> [2] https://github.com/zenodo/zenodo/issues/826 >> <https://eur01.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fgit= hub.com%2Fzenodo%2Fzenodo%2Fissues%2F826&data=3D04%7C01%7C%7Cfba8a69fdf7645= 73335708d91ea9dec9%7C6cef373021314901831055b3abf02c73%7C0%7C0%7C63757453721= 3313936%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI= 6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3DSHGhq70btcEWoFgXiip%2FKVGKfKAy3K8B1p= en%2BjIG13Q%3D&reserved=3D0> >> >> _______________________________________________ >> grass-dev mailing list >> [email protected] >> https://lists.osgeo.org/mailman/listinfo/grass-dev >> <https://eur01.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Flis= ts.osgeo.org%2Fmailman%2Flistinfo%2Fgrass-dev&data=3D04%7C01%7C%7Cfba8a69fd= f764573335708d91ea9dec9%7C6cef373021314901831055b3abf02c73%7C0%7C0%7C637574= 537213323931%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLC= JBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3D1Bk3qlRhlR5jphU%2BlBob9UyY%2BxS= tFXFXS%2FREBYn5JVk%3D&reserved=3D0> >> >> _______________________________________________ >> grass-dev mailing list >> [email protected] >> https://lists.osgeo.org/mailman/listinfo/grass-dev >> > --00000000000068411305c3a5300c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr">Dear all,</div><div dir=3D"ltr"><br></div= ><div dir=3D"ltr">Zenodo-GitHub link is enabled. There is nothing to see or= customize on Zenodo.org until a release happens. It is important that ever= y release is a GitHub release rather than just a tag, but other than that, = it will work automatically.<br></div><div dir=3D"ltr"><br></div><div dir=3D= "ltr">I won't be creating .zenodo.json right away, but will probably wa= it until 7.8.6 or 8.0.alpha happens to see how good or bad the metadata is.= Then we will see what priority to assign to creating .zenodo.json.</div><d= iv><br></div><div>Best,<br></div><div>Vaclav<br></div></div><br><div class= =3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, May 24, 2021= at 9:06 PM Vaclav Petras <<a href=3D"mailto:[email protected]">wenze= [email protected]</a>> wrote:<br></div><blockquote class=3D"gmail_quote" s= tyle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pad= ding-left:1ex"><div dir=3D"ltr"><div>Thanks everyone for the support. </div= ><div><br></div><div>I was able to identify some potential issues. Namely, = the auto-generated metadata on Zenodo does not seem to be that great and th= at includes basic things like title and license. How an author list will lo= ok is hard to say without trying, but it is promised to be sensible. It see= ms that a lot of projects just solve this using a .zenodo.json configuratio= n file which includes this info, e.g. a full author list.</div><div><br></d= iv><div>Although these metadata issues are certainly visible, a DOI will be= generated and usable by itself in any case. Additionally, metadata can be = edited manually after the publishing/release. Finally, having .zenodo.json = is doable (probably through CITATION.cff which would be good to have anyway= ). Thus, I don't see this as a blocker, just as something to resolve on= the way.</div><div><br></div><div class=3D"gmail_quote"><div dir=3D"ltr" c= lass=3D"gmail_attr">On Mon, May 24, 2021 at 1:27 PM Stefan Blumentrath <= <a href=3D"mailto:[email protected]" target=3D"_blank">Stefan.Blum= [email protected]</a>> wrote:<br></div><div>=C2=A0</div><blockquote class= =3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg= b(204,204,204);padding-left:1ex"><div> <div style=3D"color:rgb(33,33,33);background-color:rgb(255,255,255)" dir=3D= "auto"> </div> <div style=3D"color:rgb(33,33,33);background-color:rgb(255,255,255)" dir=3D= "auto"> There is already a GRASS GIS community on Zenodo, managed by Pietro.</div> <div style=3D"color:rgb(33,33,33);background-color:rgb(255,255,255)" dir=3D= "auto"> <br> </div> <div style=3D"color:rgb(33,33,33);background-color:rgb(255,255,255)" dir=3D= "auto"> There are way more GRASS related records in zenodo than registered in that = community. Wound probably be useful to register relevant entries in a GRASS= community...</div></div></blockquote><div><br></div><div>There seems to be= exactly n-1 GRASS-related records not in the community (where n is all the= GRASS-related records). Are we looking at the same one?<br></div><div><br>= </div><div><a href=3D"https://zenodo.org/communities/grass/" target=3D"_bla= nk">https://zenodo.org/communities/grass/</a></div><div>=C2=A0</div><blockq= uote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1p= x solid rgb(204,204,204);padding-left:1ex"><div> <div style=3D"color:rgb(33,33,33);background-color:rgb(255,255,255)" dir=3D= "auto"> <br> </div> <div style=3D"color:rgb(33,33,33);background-color:rgb(255,255,255)" dir=3D= "auto"> Would it be an option to develop the community in that direction, Pietro? I= f others too think that's useful ...</div> <div style=3D"color:rgb(33,33,33);background-color:rgb(255,255,255)" dir=3D= "auto"> <br> </div> <div style=3D"color:rgb(33,33,33);background-color:rgb(255,255,255)" dir=3D= "auto"> Cheers=C2=A0</div> <div style=3D"color:rgb(33,33,33);background-color:rgb(255,255,255)" dir=3D= "auto"> Stefan</div> <hr style=3D"display:inline-block;width:98%"> <div id=3D"gmail-m_-8826051041913863186gmail-m_8215046019207934969divRplyFw= dMsg" dir=3D"ltr"><font style=3D"font-size:11pt" face=3D"Calibri, sans-seri= f" color=3D"#000000"><b>From:</b> grass-dev <<a href=3D"mailto:grass-dev= [email protected]" target=3D"_blank">[email protected]= rg</a>> on behalf of Veronica Andreo <<a href=3D"mailto:veroandreo@gm= ail.com" target=3D"_blank">[email protected]</a>><br> <b>Sent:</b> Monday, May 24, 2021 1:48:21 PM<br> <b>To:</b> Moritz Lennert <<a href=3D"mailto:[email protected]= e" target=3D"_blank">[email protected]</a>><br> <b>Cc:</b> grass-dev <<a href=3D"mailto:[email protected]" targe= t=3D"_blank">[email protected]</a>>; Peter L=C3=B6we <<a href= =3D"mailto:[email protected]" target=3D"_blank">[email protected]</a>>= <br> <b>Subject:</b> Re: [GRASS-dev] [release planning] Enable Zenodo before 7.8= .6 and 8.0.0</font> <div>=C2=A0</div> </div> <div> <div dir=3D"auto">+1 from my side too</div> <br> <div> <div dir=3D"ltr">El lun., 24 may. 2021 03:23, Moritz Lennert <<a href=3D= "mailto:[email protected]" target=3D"_blank">[email protected]= online.be</a>> escribi=C3=B3:<br> </div> <blockquote style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204= ,204,204);padding-left:1ex"> <div>Clear +1 from me. <br> <br> Moritz<br> <br> <div>Le 24 mai 2021 03:08:06 GMT+01:00, Vaclav Petras <<a href=3D"mailto= :[email protected]" rel=3D"noreferrer" target=3D"_blank">wenzeslaus@gmai= l.com</a>> a =C3=A9crit=C2=A0: <blockquote style=3D"margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204= ,204,204);padding-left:1ex"> <div dir=3D"ltr"> <div>Hi all,<br> </div> <div><br> </div> <div>Let's enable the Zenodo link before 7.8.6 and 8.0(.0?) releases to= get DOIs and Zenodo records.<br> </div> <div><br> </div> <div>Solving the whole DOI linking and Zenodo archiving for the old version= s may be complex [1], but enabling the link between GitHub and Zenodo is tr= ivial (one click) and every newly created GitHub release (we do those) will= be automatically registered and receive DOI.</div> <div><br> </div> <div>Zenodo uses a system of DOI versions and a main DOI (Concept DOI). Whe= ther it is an ideal system, that's a question, but it is currently the = expected one since it is the same for everything on Zenodo. It is used auto= matically when using the GitHub-Zenodo integration.</div> <div><br> </div> <div>It seems I have the permissions to enable it for GRASS GIS. The one wh= o enables that becomes a maintainer of it. I'm fine with that, but I wo= n't be uploading any older versions. The <span>maintainer</span> can be changed later by contacting Zenodo support [= 2].<br> </div> <div><br> </div> <div>Although there are things to figure out in terms of next steps, I don&= #39;t see much risk in enabling it. There are no choices available in the s= etup or in terms of alternatives. DOI and some kind of registration are exp= ected more and more.<br> </div> <div><br> </div> <div>Thoughts?</div> <div><br> </div> <div>Vaclav<br> </div> <div><br> </div> <div>[1] <a href=3D"https://eur01.safelinks.protection.outlook.com/?url=3Dh= ttps%3A%2F%2Fgrasswiki.osgeo.org%2Fwiki%2FGitHub-Zenodo_linkage&data=3D= 04%7C01%7C%7Cfba8a69fdf764573335708d91ea9dec9%7C6cef373021314901831055b3abf= 02c73%7C0%7C0%7C637574537213313936%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAw= MDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3DhCfCx= TMHSG5PluYrYfies7ZWg9F3hCSM%2B1aC8WzgD4E%3D&reserved=3D0" rel=3D"norefe= rrer" target=3D"_blank"> https://grasswiki.osgeo.org/wiki/GitHub-Zenodo_linkage</a></div> <div>[2] <a href=3D"https://eur01.safelinks.protection.outlook.com/?url=3Dh= ttps%3A%2F%2Fgithub.com%2Fzenodo%2Fzenodo%2Fissues%2F826&data=3D04%7C01= %7C%7Cfba8a69fdf764573335708d91ea9dec9%7C6cef373021314901831055b3abf02c73%7= C0%7C0%7C637574537213313936%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJ= QIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3DSHGhq70btcEW= oFgXiip%2FKVGKfKAy3K8B1pen%2BjIG13Q%3D&reserved=3D0" rel=3D"noreferrer"= target=3D"_blank"> https://github.com/zenodo/zenodo/issues/826</a></div> </div> </blockquote> </div> </div> _______________________________________________<br> grass-dev mailing list<br> <a href=3D"mailto:[email protected]" rel=3D"noreferrer" target=3D"_= blank">[email protected]</a><br> <a href=3D"https://eur01.safelinks.protection.outlook.com/?url=3Dhttps%3A%2= F%2Flists.osgeo.org%2Fmailman%2Flistinfo%2Fgrass-dev&data=3D04%7C01%7C%= 7Cfba8a69fdf764573335708d91ea9dec9%7C6cef373021314901831055b3abf02c73%7C0%7= C0%7C637574537213323931%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjo= iV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3D1Bk3qlRhlR5jphU%= 2BlBob9UyY%2BxStFXFXS%2FREBYn5JVk%3D&reserved=3D0" rel=3D"noreferrer no= referrer" target=3D"_blank">https://lists.osgeo.org/mailman/listinfo/grass-= dev</a><br> </blockquote> </div> </div> </div> _______________________________________________<br> grass-dev mailing list<br> <a href=3D"mailto:[email protected]" target=3D"_blank">grass-dev@li= sts.osgeo.org</a><br> <a href=3D"https://lists.osgeo.org/mailman/listinfo/grass-dev" rel=3D"noref= errer" target=3D"_blank">https://lists.osgeo.org/mailman/listinfo/grass-dev= </a><br> </blockquote></div></div> </blockquote></div> --00000000000068411305c3a5300c-- --===============5812379419563888453== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ grass-dev mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/grass-dev --===============5812379419563888453==--