Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Mateusz Kuzak
    @mkuzak
    @sbliven Unfortunately, I don't have an answer to that, and we did have some discussion around it at the cofest. I'm asking around, more knowledgable people. Hopefully, we'll find the answer for you. BTW, there is very useful page about making software citable in the eSCience Center software guide https://guide.esciencecenter.nl/citable_software/making_software_citable.html
    Emmy Tsang
    @emmyft
    Hi @sbliven, I think CodeCite / some variation of it is going to continue at the eLife Innovation Sprint – we also have someone from the FORCE11 software citation implementation group... we could try and loop you in remotely if it's helpful, and if you're available? (Sep 4–5)
    Mateusz Kuzak
    @mkuzak
    yes, the team will definitely continue at the sprint :) and the more the merrier :)
    Spencer Bliven
    @sbliven
    Thanks for the responses. @emmyft, I would be interested if there's an opportunity for remote participation!
    Did you solve the chicken-and-egg problem of pre-registering for a zenodo DOI before the release? Writing the CFF once is straightforward, but I'm still uncertain about how to integrate it into our release process.
    Yo Yehudi
    @yochannah
    I think we had the idea of scripting a PR back to the original repo to add the DOI details after the DOI was created - my brain is getting foggy though
    but a PR means you can review it before merging the content - automated feels a little hairy
    Emmy Tsang
    @emmyft

    I think we had the idea of scripting a PR back to the original repo to add the DOI details after the DOI was created - my brain is getting foggy though

    yep that was the idea I believe... exactly because the automated usually doesn't do a good job

    Spencer Bliven
    @sbliven
    But then the CITATION.cff file for a release uses the DOI for the previous release?
    I guess if you want to include the commit hash, for instance, there's no way to get that until after making the commit.
    Emmy Tsang
    @emmyft

    I'm reading our notes from CoFest (https://github.com/SoftDev4Research/codecite/blob/master/BOSC_cofest2019_log.md): Extend zenodo to pull good cff data, make the artifact deposit, and then zenodo says “we suggest you update your cff to include this DOI - download the new file here.

    yes- so if you update your CFF, technically it's not the same "release" anymore... I believe we didn't think about that :p

    Mateusz Kuzak
    @mkuzak
    you can also use a concept DOI provided by zenodo, that does not change and will always point to the lastest version
    Spencer Bliven
    @sbliven
    I will look into adding a maven hook for prereservation
    Yo Yehudi
    @yochannah
    I am incredibly happy to see work from CoFest still being carried on :+1:
    Emmy Tsang
    @emmyft
    @sbliven i'll keep you updated regarding remote participation at the eLife Sprint - we can't stream the whole thing, but there're definitely options for remote contributions via some combinations of Github + slack /gitter + VC within groups (: anyone else who happens to read this and wants to do join remote, let me know!
    Spencer Bliven
    @sbliven
    Sounds good. I created a first draft BioJava CFF biojava/biojava#846
    Nomi Harris
    @nlharris

    I am incredibly happy to see work from CoFest still being carried on :+1:

    Same!

    Peter Cock
    @peterjc
    Ah, the chicken and egg problem with a DOI in a CFF file needing to be committed, but only getting a Zenodo DOI after doing the commit, was troubling me too.
    And like @sbliven, for Biopython currently it would be easier to have just a non-version specific paper's DOI, but I didn't see how to do that.
    Michael R. Crusoe
    @mr-c
    @peterjc You saw the comments about from Mateusz about reserving a DOI from Zenodo? Also, you can use the unversioned "parent" DOI from Zenodo
    Peter Cock
    @peterjc
    That sounds promising, hopefully Spencer can work this out for BioJava, and I can follow their example ;)
    Michael R. Crusoe
    @mr-c
    Also see https://twitter.com/stdruskat/status/1166609224593547264 @peterjc @mkuzak @sbliven @yochannah
    Mateusz Kuzak
    @mkuzak
    that looks good :)
    Monica Munoz-Torres
    @monicacecilia
    You guyyyyys, I just want to say that ever since BOSC 2019 brought Nicky Mulder to my field of view, I haven’t stopped catching eye of her awesomeness. I’m listening to another talk from her right now, about her work with the team at H3Africa https://h3africa.org/
    :raised_hands:
    Tony Yang
    @tonyyzy
    Some recordings of talks are available on ISCB's youtube channel now!
    Raony Guimaraes
    @raonyguimaraes
    @tonyyzy awesome!
    Some videos are private, maybe the presenter didn't sign the documents?
    Monica Munoz-Torres
    @monicacecilia
    You are correct, Tony. If the presenter has not given consent, the video will show up as private. :(
    Yo Yehudi
    @yochannah
    (so if you're reading this chat and you want to share your video, make sure you have signed consent to share it :D )
    Nomi Harris
    @nlharris
    @khokamp emailed all the authors yesterday asking them to sign the consent form if they’d like to to share the video of their talk.
    Spencer Bliven
    @sbliven
    I hope the #eLifeSprint today and tomorrow goes well, @emmyft! I haven't had a chance to add the zenodo API to our release process yet. I'll be interested to hear if the sprint has any suggestions for making that process easier!
    Spencer Bliven
    @sbliven
    Here's a potential funding opportunity for open source projects: https://chanzuckerberg.com/rfa/essential-open-source-software-for-science/
    Bob Hanson
    @BobHanson
    Thank you, Spencer!