<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Open Science on The Carpentries</title><link>https://deploy-preview-705--carpentries-website.netlify.app/blog/tag/open-science/</link><description>Recent content in Open Science on The Carpentries</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 20 Nov 2024 10:51:28 -0500</lastBuildDate><atom:link href="https://deploy-preview-705--carpentries-website.netlify.app/blog/tag/open-science/index.xml" rel="self" type="application/rss+xml"/><item><title>Opportunities and Challenges in Localisation: The Carpentries Perspective</title><link>https://deploy-preview-705--carpentries-website.netlify.app/blog/2023/10/carpentries-opportunities-and-challenges-in-localisation/</link><pubDate>Thu, 12 Oct 2023 00:00:00 +0000</pubDate><guid>https://deploy-preview-705--carpentries-website.netlify.app/blog/2023/10/carpentries-opportunities-and-challenges-in-localisation/</guid><description>&lt;p>&lt;em>In the realm of open science, the power of collective knowledge is magnified when it&amp;rsquo;s accessible to all, irrespective of geographical or linguistic boundaries. Localisation, in this context, is not just about translating scientific content, but about adapting research, methodologies, and data to resonate with diverse cultural and regional nuances. This series of blog posts, Opportunities and Challenges in Localisation, will dig into the world of localisation from the vantage point of various open science communities of practice. Representatives from these communities will share their unique efforts in championing localisation, the opportunities they&amp;rsquo;ve unearthed, the challenges they&amp;rsquo;ve grappled with, and pathways for you, the reader, to engage and collaborate. Join us in this exploration, as we underscore the importance of localisation in making open science truly inclusive, bridging knowledge gaps, and fostering a global community of collaborative inquiry. If your organisation also has localisation efforts, and would like to share your story on a future blog post in this series, please do so following these &lt;a href="https://docs.google.com/document/d/1LzjftRnD-BYZ-Xmg-UUkBfi5qKm0qi144BrVNeGS_WQ/edit#heading=h.foq8jruhiryr">formatting and template guidelines&lt;/a> and send your contribution to &lt;a href="mailto:balmarzouq@turing.ac.uk">balmarzouq@turing.ac.uk&lt;/a>.&lt;/em>&lt;/p></description></item><item><title>Lessons for Librarians in Open Science Principles and Methods</title><link>https://deploy-preview-705--carpentries-website.netlify.app/blog/2022/12/cfp-imls-ucla-open-science-library/</link><pubDate>Sat, 17 Dec 2022 00:00:00 +0000</pubDate><guid>https://deploy-preview-705--carpentries-website.netlify.app/blog/2022/12/cfp-imls-ucla-open-science-library/</guid><description>&lt;p>The UCLA Library is pleased to announce a &lt;a href="https://ucla-imls-open-sci.info/">call for proposals&lt;/a> for
&lt;a href="https://www.imls.gov/grants/awarded/re-252335-ols-22">Lessons for Librarians in Open Science Principles and Methods&lt;/a>, a two-year (2023-2024) project
funded by the Institute of Museum and Library Service (IMLS) to incentivize lesson authors to develop and refine seven lessons each year through
two-year sequential summer workshops. This initial call is for lesson proposals to form the project&amp;rsquo;s first-year cohort (2023).&lt;/p>
&lt;p>The project seeks to support continued skills development for librarians in open science by creating a librarian-focused curriculum. Led by the UCLA
Library Data Science Center, the project will award each recipient (individual or group) with $5,000 for developing an open science lesson. Authors
will design and refine lessons through summer workshops utilizing the &lt;a href="https://cdh.carpentries.org/">Carpentries Curriculum Development guidelines&lt;/a> and
the &lt;a href="https://carpentries.github.io/lesson-development-training/">Collaborative Lesson Development Training program&lt;/a> as frameworks for curriculum
development. The program was designed by a &lt;a href="https://ucla-imls-open-sci.info/#team">team at UCLA&lt;/a>, including the chair of the Library Carpentry
Curriculum Advisory Committee (LC-CAC), Tim Dennis, and certified Carpentries instructor Zhiyuan Yao. Inspired by the Carpentries’
evidence-based teaching and learning model, the team will work closely to align new lessons with existing Carpentries’ lessons, and leverage the
Carpentries’ technical
infrastructure to create new open-source lessons on GitHub. In addition, a member of LC-CAC will serve on the project’s &lt;a href="https://ucla-imls-open-sci.info/#team">Review Committee&lt;/a>
each year with an eye toward aligning new lesson proposals with the existing Carpentries curriculum. One potential project outcome will be a series of new
lessons for possible integration with Software, Data, or Library Carpentry curricula. A broader goal of the project is for librarians to increase
their aptitudes in the principles and practices of open science, so that they can provide instruction to researchers and better support faculty by
advocating and teaching open and transparent techniques.&lt;/p></description></item><item><title>The Open Research Glossary</title><link>https://deploy-preview-705--carpentries-website.netlify.app/blog/2015/07/open-research-glossary/</link><pubDate>Thu, 16 Jul 2015 00:00:00 +0000</pubDate><guid>https://deploy-preview-705--carpentries-website.netlify.app/blog/2015/07/open-research-glossary/</guid><description>&lt;p>&lt;b>This post originally appeared on the &lt;a href="https://software-carpentry.org/">Software Carpentry website.&lt;/a>&lt;/b>&lt;/p>
&lt;p>
 It's been knocking around for a while now, but this week saw a big
 new release of
 the &lt;a href="http://dx.doi.org/10.6084/m9.figshare.1482094">Open
 Research Glossary&lt;/a>, a crowdsourced glossary of terms, acronyms,
 tools and concepts in and around open science. There's a lot of
 jargon in this area and it's often a barrier to understanding for
 the uninitiated. For example: 'green', 'gold', 'diamond' and
 'hybrid' open access are shorthand terms which aren't always fully
 understood.
&lt;/p>
&lt;p>
 The alphabet soup of acronyms are even worse!
 Take &lt;a href="http://www.sherpa.ac.uk/romeo/">SHERPA/RoMEO&lt;/a> for
 instance: it's a brilliant resource for checking author
 self-archiving rights relative to publisher-imposed restrictions and
 embargoes, but the name 'SHERPA/RoMEO' doesn't exactly make that
 clear. This glossary aims to elucidate all the need-to-know terms in
 open scholarship.
&lt;/p></description></item><item><title>How to Manage Confidential Data</title><link>https://deploy-preview-705--carpentries-website.netlify.app/blog/2014/11/how-to-manage-confidential-data/</link><pubDate>Thu, 27 Nov 2014 00:00:00 +0000</pubDate><guid>https://deploy-preview-705--carpentries-website.netlify.app/blog/2014/11/how-to-manage-confidential-data/</guid><description>&lt;p>&lt;b>This post originally appeared on the &lt;a href="https://software-carpentry.org/">Software Carpentry website.&lt;/a>&lt;/b>&lt;/p>
&lt;p>
 A couple of days ago,
 a member of our community wrote:
&lt;/p>
&lt;blockquote>
 &lt;p>
 I am very interested in working on improving research analytics in government
 using the principles developed by Software Carpentry.
 A key stumbling block I run into with my peers is their skepticism
 about these principles being able to protect data
 that is confidential or restricted use.
 &lt;/p>
&lt;/blockquote></description></item><item><title>The Open Scoop Challenge</title><link>https://deploy-preview-705--carpentries-website.netlify.app/blog/2014/02/open-scoop-challenge/</link><pubDate>Tue, 25 Feb 2014 00:00:00 +0000</pubDate><guid>https://deploy-preview-705--carpentries-website.netlify.app/blog/2014/02/open-scoop-challenge/</guid><description>&lt;p>&lt;b>This post originally appeared on the &lt;a href="https://software-carpentry.org/">Software Carpentry website.&lt;/a>&lt;/b>&lt;/p>
&lt;p>
 Sooner or later,
 in every discussion of open science,
 someone will say there's a risk of being scooped
 if you share your code or data with your peers.
 I think this is pure &lt;a href="http://en.wikipedia.org/wiki/Fear,_uncertainty_and_doubt">FUD&lt;/a>:
 in all the years I've worked with scientists,
 I have never met anyone this has actually happened to.
&lt;/p>
&lt;p>
 But absence of proof is not proof of absence,
 so I'd like to issue a challenge.
 If someone has ever published a result you were going to
 by taking advantage of software or data that you made publicly available,
 I'll send you a Software Carpentry t-shirt.
 You'll need to provide specifics,
 but I won't share those details with anyone without your permission.
 Please &lt;a href="mailto:{{site.contact}}">mail me&lt;/a> if you'd like to chat.
&lt;/p></description></item></channel></rss>