Our next Community Call, on March 27th, aims to help people learn about using rOpenSci’s R packages to access and analyze taxonomy and biodiversity data, and to recognize the breadth and depth of their applications. We also aim to learn from the discussion how we might improve these tools. Presentations will start with an introduction to the topic and details on some specific packages and we’ll hear from several people about their “use cases in the wild”....
Citations are a crucial piece of scholarly work. They hold metadata on each scholarly work, including what people were involved, what year the work was published, where it was published, and more. The links between citations facilitate insight into many questions about scholarly work.
Citations come in many different formats including BibTex, RIS, JATS, and many more. This is not to be confused with citation styles such as APA vs. MLA and so on.
...Introduction
stats19
is a new R package enabling access to and working with
Great Britain’s official road traffic casualty database,
STATS19.
We started the package in late 2018 following three main motivations:
stplanr
being split-out
into two separate packages:
cyclestreets
and
stats19
.We have a wider motivation: we want the roads to be safer. By making data on the nature of road crashes more publicly accessible to inform policy, we hope this package saves lives.
...The ssh package provides a native ssh client for R. You can connect to a remote server over SSH to transfer files via SCP, setup a secure tunnel, or run a command or script on the host while streaming stdout and stderr directly to the client. The intro vignette provides a brief introduction.
This week version 0.4 has been released, so you can install it directly from CRAN:
install.packages("ssh")
The NEWS file shows that this is mostly a bugfix release:
...We tend to know a good open source research software project when we see it: The code is well-documented, users contribute back to the project, the software is licensed and citable, and the community interacts and co-produces in a healthy, productive fashion. The academic literature 1 and community discourse 2 around research software development offer insight into how to promote the technical best-practices needed to produce some of these project attributes; however, the management of non-technical, social components of software projects are less visible and therefore less often discussed in best-practice pieces. In a recent community call, I discussed some of these components through the lens of my research on open source research software project governance....