• CiTO updates #3: third paper in the collection and updated Scholia patch

    Last week the third paper got published in the Citation Typing Ontology Collection and this weekend I finished adding the citation annotations to Wikidata.
  • CiTO updates #2: annotation migration to Wikidata and first Scholia patch

    During the time of the editorial about the Journal of Cheminformatics Citation Typing Ontology (CiTO) Pilot I already worked out a model to add CiTO annotation in Wikidata. It looks like this for the first research article with annotation:
  • SARS-CoV-2, COVID-19, and Open Science

    WP4846 that I started on March 16. It will see a massive overhaul in the next weeks. Voices are getting stronger over how important Open Science is. Insiders have known the advantages for decades. We also know the issues in the transition, but the transition has been steady. Contributing to Open Science is simple: there are plenty of project where you can contribute without jeopardizing your own research (funding or prestige). Myself, my small contributions have been done without funding too. But I needed to do something. I have been mostly self-quarantined since March 6, with only very few exception. And I’m so done with it. Like so many other people. It won’t stop me wearing masks when I go shopping (etc).
  • Bioclipse git experiences #2: Create patches for individual plugins/features

    This is a series of two posts repeating some content I wrote up back in the Bioclipse days (see also this Scholia page). They both deal with something we were facing: restructuring of version control repositories, while actually keeping the history. For example, you may want to copy or move code from one repository to another. A second use case can be a file that must be removed (there are valid reasons for that). Because these posts are based on Bioclipse work, there will be some specific terminology, but the approach I regularly apply in other situations.
  • Bioclipse git experiences #1: Strip away unwanted plugins

    This is a series of two posts repeating some content I wrote up back in the Bioclipse days (see also this Scholia page). They both deal with something we were facing: restructuring of version control repositories, while actually keeping the history. For example, you may want to copy or move code from one repository to another. A second use case can be a file that must be removed (there are valid reasons for that). Because these posts are based on Bioclipse work, there will be some specific terminology, but the approach I regularly apply in other situations.
  • What metabolites are found in which species? Nanopublications from Wikidata

    In December I reported about Groovy code to create nanopublications . This has been running for some time now, extracting nanopubs that assert that some metabolite is found in some species. I send the resulting nanopubs to Tobias Kuhn , to populate his Growing Resource of Provenance-Centric Scientific Linked Data (doi:10.1109/eScience.2018.00024, PDF).
  • Creating nanopublications with Groovy

    Yesterday, I struggled some with creating nanopublications with Groovy. My first attempt was an utter failure, but then I discovered Thomas Kuhn’s NanopubCreator and it was downhill from there.