Hands-on GitHub Actions (Getting Started with GitHub Actions Workflows)

Following the CDK and JChemPaint Primary, Bioclipe moved to Git just after the 2.0.0 release.

This module includes a script to collect all the pull requests and issues for a GitHub organization. The resulting data includes date created, date closed, date closed, title, and number of comments. The script outputs both a JSON and CSV file. This script is written with the support of GitHub copilot. To run this, you need to add the organization of interest, your Personal Access Token (from your GitHub account settings) and ensure you have the dependencies (curl and jq).

I spent last Friday and Saturday at ( Research in the 21st Century: Data, Analytics and Impact , hashtag #ReCon_15) in Edinburgh. Friday 19th was conference day, followed by a hackday at CodeBase. There's a Storify archive of the tweets so you can get a sense of the meeting. Sitting in the audience a few things struck me. No identifier wars, DOIs have won and are everywhere.

BioPerl has migrated to git and GitHub!

Ein Großteil an Code wird von Entwicklern ohne Lizenz ins Netz gestellt, etwa bei Github. Das birgt bereits Probleme, doch dahinter steckt eine weitere Entwicklung: Auch Copyleft-Modelle wie das der GPL setzen ein starkes Urheberrecht voraus. Beides ist für viele Entwickler zu unflexibel und damit nicht mehr attraktiv, so Armin Ronacher.

Here's another example of a Darwin Core Archive that is "broken" such that GBIF is missing some information. GBIF data set A checklist to the wasps of Peru (Hymenoptera, Aculeata) comes from Pensoft, and corresponds to the paper:As with the previous example GBIF says there are 0 georeferenced records in this dataset. This is odd, because the ZooKeys page for this article lists three supplementary files, including KML files for Google Earth.