Messages de Rogue Scholar

language

Last week, the ScholCommLab welcomed some smiling new faces to Vancouver. On Friday, Nov 9, attendees of ASIS&T’s 2018 Annual Meeting joined us from Dusseldorf, Detroit, Ottawa, and beyond for a quick lab tour, some dinner and conversation, and one very crowded, very happy selfie. At the conference, speakers and attendees from around the globe met in Vancouver to discuss the latest advances in information science.

Join us for the next Open Science Beers YVR Thursday, March 14, 2019 6 PM – 9 PM The Emerald (555 Gore Ave) About Open Science Beers YVR During last year’s FORCE11 conference, the idea was born to recreate Montreal’s popular Open Science Beers event right here in our very own Vancouver. Now, that idea has become a reality. Each month, we’re bringing together friends of Open Science* for a casual evening of drinks and conversation.

While many people groan at the thought of participating in a group ice breaker activity, we’ve gotten consistent feedback from people who have been to recent rOpenSci unconferences. We’ve had lots of requests for a detailed description of how we do it. This post shares our recipe, including a script you can adapt, a reflection on its success, examples of how others have used it, and some tips to remember.

rOpenSci’s software engineer / postdoc Jeroen Ooms will explain what images are, under the hood, and showcase several rOpenSci packages that form a modern toolkit for working with images in R, including opencv, av, tesseract, magick and pdftools. 🕘 Thursday, November 15, 2018, 10-11AM PST; 7-8PM CET (find your timezone) ☎️ Find all details for joining the call on our Community Calls page.Everyone is welcome.

Taking place from Oct 11 to 12 in Montreal, QC, FORCE 2018 is a multi-disciplinary conference dedicated to creating a more open future for scholarly communications. This year, the conference will bring together a diverse mix of publishers, librarians, students, and policy makers—as well as several members of the ScholCommLab!

Do you have code that accompanies a research project or manuscript? How do you review and archive that code before you submit a paper? Our next Community Call will present different perspectives on this hot topic, with plenty of time for Q&A.What’s the culture of the group around feedback and code collaboration?What are the use cases?What are some practices that can adopted?