Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Stian Soiland-Reyes
    @stain
    @tonyyzy I had that issue two years ago, then you could not update f1000 uploads under poster or slides, unlike the paper uploads
    Do moan at them! Zenodo always permits New Version (with new DOI), you shouldn't be forced to do a fresh deposit
    Stian Soiland-Reyes
    @stain
    Btw, the BOSC "proceedings" linked to from https://www.open-bio.org/events/bosc/schedule/ are on Google Drive, which feels quite temporary. Could you post the PDF to Zenodo so it has a more long term storage? (Perhaps the same for previous years proceedings)
    Nitesh Turaga
    @nturaga
    Wh
    Nomi Harris
    @nlharris
    @stain Thanks for reminding me—I did intend to put the proceedings somewhere more permanent (I put it in gdrive for ease of updating while it was still in development). Zenodo is a good idea (I was going to put it on GitHub).
    Stian Soiland-Reyes
    @stain
    thanks, @nlharris! :)
    Stian Soiland-Reyes
    @stain
    @nlharris another moan.. (sorry) - why F1000 for posters and slides? It's quite awkward and too rigid to use compared to Zenodo. See thread https://twitter.com/soilandreyes/status/1154724309862162432
    Hilmar Lapp
    @hlapp
    F1000 gives us a channel that pulls together all BOSC content, including the meeting report. It's also integrated with the ISCB community channel there.
    Nomi Harris
    @nlharris
    Yes, I think it was ISCB that initially led us to F1000? They have also been BOSC sponsors several times (which doesn’t bind us to them, of course, but it is a factor to consider). However, if F1000 is not serving the needs of our presenters (I saw your complaints about it on Twitter), we may reconsider.
    Honestly, I’m not sure whether Zenodo existed yet (or maybe we just weren’t aware of it) back when we chose F1000 (several years ago).
    Michael R. Crusoe
    @mr-c
    :+1: for Zenodo!
    Peter Cock
    @peterjc
    @stain @nomi We could put the BOSC proceeding on our GitHub as in previous years (along side the individual abstracts too) https://github.com/OBF/bosc_materials/tree/master/
    Nomi Harris
    @nlharris
    Looks like I in fact already added it there 11 days ago
    Tony Yang
    @tonyyzy
    Finally got my slides and poster on F1000! How do I add them to the BOSC collection? slides: https://doi.org/10.7490/f1000research.1117144.1, poster: https://doi.org/10.7490/f1000research.1117143.1
    Nomi Harris
    @nlharris
    I know you can submit slides and posters to the BOSC collection by going to https://f1000research.com/collections/bosc?selectedDomain=slides. What I’m not sure about is how to move things to the BOSC collection once they’ve been added.
    Tony Yang
    @tonyyzy
    BTW, I got an email from ISCB that I can deposit poster to the community journal but I didn't select ISMB when I published them...I guess it's too late now?
    Nomi Harris
    @nlharris
    What is the “community journal”? Can you forward that email to bosc@open-bio.org so we can take a look?
    Tony Yang
    @tonyyzy
    @nlharris it's the ISCB community journal on F1000. https://f1000research.com/gateways/iscb or "Gateway" as they call it
    Peter Cock
    @peterjc
    F1000 will ensure all the BOSC 2019 content via https://f1000research.com/collections/bosc will also appear on https://f1000research.com/gateways/iscb (they use a tagging system, look at 2017 and you'll see how it will look).
    Conversely, we will be checking for missing BOSC slides and posters. If they are only on https://f1000research.com/gateways/iscb then we'll ask F1000 to tag them to appear in https://f1000research.com/collections/bosc too.
    Where people have used FigShare etc instead, we'll probably fall back on links from the complete schedule as done in previous years - although the main OBF/BOSC website is in a bit of flux so the URLs may change but with a direction. Have a look at https://www.open-bio.org/wiki/BOSC_2017_Schedule or https://www.open-bio.org/wiki/BOSC_2016_Schedule for example.
    Spencer Bliven
    @sbliven
    Anyone still lurking here from the citation file format community? I'm trying to write a CFF for BioJava but I'm not sure how to proceed
    Basically, we want people to cite the most recent paper for all versions. CFF seems to be for a specific software version?
    I should have taken the chance at the CoFest to discuss this with the CodeCite group
    Yo Yehudi
    @yochannah
    I wonder if @sdruskat checks gitter?
    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: