<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Library Carpentry</title>
    <description>Software and data skills for library professionals</description>
    <link>https://librarycarpentry.github.io/</link>
    <atom:link href="https://librarycarpentry.github.io//feed.xml" rel="self" type="application/rss+xml" />
    
      <item>
        <title>Library Carpentry sprint, 10-11 May, 2018</title>
        <description>&lt;p&gt;The &lt;a href=&quot;https://www.mozillapulse.org/entry/642&quot;&gt;Library Carpentry sprint&lt;/a&gt; is part of 
the &lt;a href=&quot;https://foundation.mozilla.org/opportunity/global-sprint/&quot;&gt;2018 Mozilla Global Sprint&lt;/a&gt;, 
which will take place worldwide on 10-11 May, 2018. Check out our sprint entry 
on &lt;a href=&quot;https://www.mozillapulse.org/entry/642&quot;&gt;Mozilla Pulse&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;For those new to the field, a sprint is like a hackathon - it is a way to get people working together to create, 
update or extend open projects like Library Carpentry.&lt;/p&gt;

&lt;h3 id=&quot;join-us-to-be-part-of-it&quot;&gt;Join us to be part of it!&lt;/h3&gt;

&lt;p&gt;We are using this sprint to amend, update, and extend the existing &lt;a href=&quot;https://librarycarpentry.github.io/&quot;&gt;Library Carpentry&lt;/a&gt; 
lessons and to finalise the new &lt;a href=&quot;https://github.com/richyvk/library-carpentry-redesign&quot;&gt;draft website&lt;/a&gt; for launch.&lt;/p&gt;

&lt;p&gt;For the lessons, we welcome contributions from librarians, archivists, information workers, 
digital humanities researchers … anyone who wants to contribute to building either the lessons and this burgeoning community (or both!).&lt;/p&gt;

&lt;p&gt;For the website, we welcome suggestions, edits, pull requests, corrections - you name it.&lt;/p&gt;

&lt;p&gt;Not sure what &lt;strong&gt;Library Carpentry&lt;/strong&gt; &lt;em&gt;is&lt;/em&gt;? Check out our &lt;a href=&quot;https://librarycarpentry.github.io/&quot;&gt;‘front page’&lt;/a&gt;. 
This provides links to our published lessons.&lt;/p&gt;

&lt;p&gt;For the ‘back end’, repository view of the lessons, check out the lessons prefixed &lt;code class=&quot;highlighter-rouge&quot;&gt;lc-&lt;/code&gt; &lt;a href=&quot;https://github.com/librarycarpentry&quot;&gt;here&lt;/a&gt;.&lt;/p&gt;

&lt;h3 id=&quot;registering-a-site&quot;&gt;Registering a site&lt;/h3&gt;

&lt;p&gt;Use this form to tell Mozilla you are hosting a site. https://docs.google.com/forms/d/e/1FAIpQLSdyLD5iv0HvURB-r9ejUz3NAO4wD0B1g-FBvIBgyZCaZj627g/viewform&lt;/p&gt;

&lt;p&gt;Add your site as well to our sprint etherpad: http://pad.software-carpentry.org/lc-sprint-2018&lt;/p&gt;

&lt;h3 id=&quot;how-will-the-sprint-work&quot;&gt;How will the sprint work?&lt;/h3&gt;

&lt;p&gt;We will use our &lt;a href=&quot;https://gitter.im/LibraryCarpentry/Lobby&quot;&gt;chatroom&lt;/a&gt; and 
this &lt;a href=&quot;https://github.com/data-lessons/librarycarpentry&quot;&gt;GitHub repository&lt;/a&gt; to organise work during the 2-day sprint. 
Join the chatroom at any time using your GitHub username or your Twitter handle.&lt;/p&gt;

&lt;p&gt;These are the &lt;a href=&quot;https://github.com/data-lessons/librarycarpentry/issues&quot;&gt;issues&lt;/a&gt; we want to work on during the sprint. 
To find out how you can help, look at the &lt;a href=&quot;https://github.com/data-lessons/librarycarpentry/blob/master/README.md&quot;&gt;README&lt;/a&gt; 
and &lt;a href=&quot;https://github.com/data-lessons/librarycarpentry/blob/master/CONTRIBUTING.md&quot;&gt;CONTRIBUTING&lt;/a&gt; files. 
The &lt;a href=&quot;https://github.com/data-lessons/librarycarpentry/issues&quot;&gt;issues&lt;/a&gt; we hope to resolve are all labelled &lt;strong&gt;#mozsprint&lt;/strong&gt;. 
Feel free to create new issues if you need to.&lt;/p&gt;

&lt;p&gt;People can start working straightaway on &lt;em&gt;any&lt;/em&gt; of the &lt;strong&gt;#mozsprint&lt;/strong&gt; &lt;a href=&quot;https://github.com/data-lessons/librarycarpentry/issues&quot;&gt;issues&lt;/a&gt;. There will be designated people available to answer questions at most times during the sprint. We will use the chatroom to wrangle those questions and clarifications. You will be able to ask questions via scheduled video calls as well (which we will also use for networking). If you are not sure about something, please post a question in the chatroom (directed to someone in particular, if need be) and someone will get back to you.&lt;/p&gt;

&lt;h3 id=&quot;how-the-sprint-will-be-organised&quot;&gt;How the sprint will be organised&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;There are a number of dedicated sprint site locations (&lt;a href=&quot;http://pad.software-carpentry.org/lc-sprint-2018&quot;&gt;see them here&lt;/a&gt;), 
all of which will start working at different times as the sun moves around the globe. People may also be working remotely. 
Sites will organise their own work and report back on how things are going during video calls, via the chatroom, or 
through the daily handovers (where the baton will be passed on to the next locations). regisyter your site here: https://docs.google.com/forms/d/e/1FAIpQLSdyLD5iv0HvURB-r9ejUz3NAO4wD0B1g-FBvIBgyZCaZj627g/viewform and add it to the &lt;a href=&quot;http://pad.software-carpentry.org/lc-sprint-2018&quot;&gt;etherpad&lt;/a&gt; as well&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;Handovers will take place at the end of the work day in the southern hemisphere and at the beginning of the new work day there.&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;Sprinters can work on whatever lessons or issues they like. If you are not a coder, try to pair up with others and work 
through a lesson of your choice. Then raise issues, ask questions, suggest changes, or propose scenarios or workflows you 
would like to see addressed. We are interested as much in ideas and feedback as in new code. Our aim is to make the 
lessons as useful and as relevant as possible to librarians, archivists and other information workers. If you have a dataset to 
contribute that would help make a good lesson, that would also be useful.&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;You can use the sprint to network. Most of the Library Carpentry community will be taking part in this sprint at different times. Use the sprint to meet these people virtually and talk about running a workshop, hosting a workshop, or other issues that have cropped up for you, your institution or your country. We want to spread the Library Carpentry word as far and wide as possible, so use the sprint to find out how you can help.&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;Our &lt;a href=&quot;http://pad.software-carpentry.org/lc-sprint-2018&quot;&gt;etherpad&lt;/a&gt; is another tool we will use for organising the work of the sprint. 
Dedicated etherpads will be created for each lesson being worked on - they will be listed on this etherpad once the sprint is underway. 
The individual repositories are all listed below.&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;Links to video calls will also be posted on the etherpad, with the scheduled times - all links will show the time and date in your zone.&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;Since people are working both at dedicated sites (see the &lt;a href=&quot;http://pad.software-carpentry.org/lc-sprint-2018&quot;&gt;etherpad for locations&lt;/a&gt;) 
and remotely, we will touch base regularly so everyone feels part of things. You can use the &lt;a href=&quot;https://gitter.im/LibraryCarpentry/Lobby&quot;&gt;chatroom&lt;/a&gt;
at any time to say in touch, or to post updates or ask questions.&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;If you are a tweeter, please tweet about the event using the handle &lt;strong&gt;@LibCarpentry&lt;/strong&gt; and the hashtags &lt;strong&gt;#lc2018&lt;/strong&gt; and &lt;strong&gt;#mozsprint&lt;/strong&gt;. Photos are good too. It would be great to have photos of each site’s people working away so we can do an illustrated blog post of how the sprint went.&lt;/p&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;what-you-can-do&quot;&gt;What you can do&lt;/h3&gt;

&lt;p&gt;Work on existing lessons by&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;submitting pull requests&lt;/strong&gt; to suggest changes (please keep each pull request small - one or two changes only per PR - to make 
them easier to manage for maintainers)&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;raising issues&lt;/strong&gt; for discussion/amendment against specific lessons using the &lt;em&gt;Issues&lt;/em&gt; tab on each lesson&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;chatting with others&lt;/strong&gt; in the &lt;a href=&quot;https://gitter.im/LibraryCarpentry/Lobby&quot;&gt;chatroom&lt;/a&gt; or via the daily catchups and video calls&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;working through lessons with colleagues&lt;/strong&gt; as a way of familiarising yourself with the material&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;discussing the project with colleagues&lt;/strong&gt;, especially about how you might bring &lt;a href=&quot;http://librarycarpentry.github.io/&quot;&gt;Library Carpentry&lt;/a&gt; to your institution&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;identifying any confusing gaps or assumptions&lt;/strong&gt; in lessons so we can make the lessons more learner-friendly.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;social-media-and-communications&quot;&gt;Social Media and Communications&lt;/h3&gt;

&lt;p&gt;The sprint hashtag are &lt;strong&gt;#lc2018&lt;/strong&gt; and &lt;strong&gt;#mozsprint&lt;/strong&gt;. Please use these to tie tweets together, and also include 
Library Carpentry’s Twitter handle, &lt;a href=&quot;https://twitter.com/LibCarpentry&quot;&gt;&lt;strong&gt;@LibCarpentry&lt;/strong&gt;&lt;/a&gt;, if you can.&lt;/p&gt;

&lt;p&gt;If you post images on Instagram or Facebook, please send us a link via the chatroom so we can tweet them.&lt;/p&gt;

&lt;h3 id=&quot;lesson-maintainers&quot;&gt;Lesson Maintainers&lt;/h3&gt;

&lt;p&gt;This is a list of people who maintain each Library Carpentry lesson. If you are editing a lesson, be sure to check 
in with them throughout the sprint. Volunteers to help maintain a lesson after the sprint are always welcome!&lt;/p&gt;

&lt;h3 id=&quot;individual-lesson-links-and-github-ids-of-lesson-maintainers&quot;&gt;Individual Lesson links and GitHub IDs of Lesson Maintainers*&lt;/h3&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/librarycarpentry/lc-git&quot;&gt;Git&lt;/a&gt; - weaverbel, jezcope&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/librarycarpentry/lc-shell&quot;&gt;Shell&lt;/a&gt; - weaverbel, jt14den&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/librarycarpentry/lc-open-refine&quot;&gt;OpenRefine&lt;/a&gt; - ostephens, ccronje, pitviper6&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/librarycarpentry/lc-python-intro&quot;&gt;New Draft Python&lt;/a&gt; - c-martinez, richyvk&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/LibraryCarpentry/lc-spreadsheets&quot;&gt;Tidy Data from Spreadsheets&lt;/a&gt; - jezcope&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/librarycarpentry/lc-sql&quot;&gt;SQL&lt;/a&gt; - c-martinez, icejan&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/librarycarpentry/lc-data-intro&quot;&gt;Data Intro, Jargon Busting, Regex&lt;/a&gt; - drjwbaker, ccronje&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/LibraryCarpentry/lc-data-intro-archives&quot;&gt;Data Intro for Archives&lt;/a&gt; - drjwbaker&lt;/p&gt;
</description>
        <pubDate>Mon, 23 Apr 2018 00:00:00 +0000</pubDate>
        <link>https://librarycarpentry.github.io//lc-sprint-18/</link>
        <guid isPermaLink="true">https://librarycarpentry.github.io//lc-sprint-18/</guid>
      </item>
    
      <item>
        <title>Library Carpentry: Update from the Community Calls</title>
        <description>&lt;p&gt;Community members came together on 10-11 October for two calls about the future direction of Library Carpentry.&lt;/p&gt;

&lt;p&gt;You can see the discussions from those calls on the &lt;a href=&quot;http://pad.software-carpentry.org/lc-call&quot;&gt;calls etherpad&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;It was great to have such a good roll-up for both calls, and we managed to make some important decisions about the future.&lt;/p&gt;

&lt;h3 id=&quot;website-redesign&quot;&gt;Website redesign&lt;/h3&gt;

&lt;p&gt;We voted to move ahead with &lt;a href=&quot;https://github.com/richyvk&quot;&gt;Richard Vankoningsveld&lt;/a&gt;’s &lt;a href=&quot;https://www.richyvk.me/library-carpentry-redesign/&quot;&gt;proposed redesign&lt;/a&gt;
of the existing &lt;a href=&quot;https://librarycarpentry.github.io/&quot;&gt;Library Carpentry&lt;/a&gt; website. John Chodacki would prefer the logo be 
white or grey rather than yellow, and Richard still has some work to do to get the blog to render in the same &lt;a href=&quot;https://github.com/y7kim/agency-jekyll-theme&quot;&gt;Agency theme&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;This theme is designed for projects rather than for blogs but, with some tweaking, this should not be a problem. So things are looking good!&lt;/p&gt;

&lt;p&gt;We are also hoping to be able to use the &lt;code class=&quot;highlighter-rouge&quot;&gt;librarycarpentry.org&lt;/code&gt; domain which is currently owned by Software Carpentry.&lt;/p&gt;

&lt;h3 id=&quot;new-funded-library-carpentry-position-based-at-cdl&quot;&gt;New funded Library Carpentry position based at CDL&lt;/h3&gt;

&lt;p&gt;John Chodacki filled us in on the &lt;a href=&quot;https://www.imls.gov/grants/awarded/RE-85-17-0121-17&quot;&gt;recently awarded IMLS grant&lt;/a&gt; which will support the work of Library Carpentry both within the US (for example, fostering local communities of new instructors in underserved areas such as the Southeast US) and globally. 
Using the grant, California Digital Library will hire a person on a two-year contract, with a remit of growing the community, especially
the instructor pool, and responding to the ever growing demand for workshops. There will also be work to develop and finish lessons
created during the 2016 and 2017 sprints.&lt;/p&gt;

&lt;h3 id=&quot;governance&quot;&gt;Governance&lt;/h3&gt;

&lt;p&gt;Since there was general agreement across both calls for eventual merger with the Carpentries (&lt;a href=&quot;http://www.datacarpentry.org/blog/merger/&quot;&gt;which will themselves merge in January 2018&lt;/a&gt;), 
it was decided that the Library Carpentry community 
should elect an interim Steering Committee to guide us through that process. The proposal was to have around five to seven people (to prevent tied votes) and to 
revisit the Committee post-merger.&lt;/p&gt;

&lt;p&gt;Several people expressed interest in serving on such a committee. Belinda Weaver will dig up the Software Carpentry Steering Committee’s
terms of reference and propose something similar for Library Carpentry’s interim committee. We will then make a proposal about that, ask for feedback, and then try to organise a vote.&lt;/p&gt;

&lt;p&gt;The people interested were:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;John Chodacki (US)&lt;/li&gt;
  &lt;li&gt;Belinda Weaver (Australia)&lt;/li&gt;
  &lt;li&gt;Cam Macdonell (Canada)&lt;/li&gt;
  &lt;li&gt;Owen Stephens (UK)&lt;/li&gt;
  &lt;li&gt;Tim Dennis (US)&lt;/li&gt;
  &lt;li&gt;Scott Peterson (US)&lt;/li&gt;
  &lt;li&gt;Juliane Schneider (US)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It would be good to have a representative from Africa as there has been considerable activity in South Africa around Library
Carpentry. New Zealand has also been involved.&lt;/p&gt;

&lt;h3 id=&quot;regular-calls&quot;&gt;Regular calls&lt;/h3&gt;

&lt;p&gt;We also decided to have monthly community calls to ensure we all stay in touch and people know what is going on.&lt;/p&gt;
</description>
        <pubDate>Tue, 17 Oct 2017 00:00:00 +0000</pubDate>
        <link>https://librarycarpentry.github.io//latest-news/</link>
        <guid isPermaLink="true">https://librarycarpentry.github.io//latest-news/</guid>
      </item>
    
      <item>
        <title>Helping the Helper - practical advice for Library Carpentry Helpers</title>
        <description>&lt;p&gt;Post by &lt;a href=&quot;https://twitter.com/_miss_golightly&quot;&gt;Claire Wallnutt&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;A couple of months ago my line manager asked if I would be interested in helping out at an upcoming workshop our Library was helping to deliver. The workshop was entitled Library Carpentry. The first thing I asked was “is this to do with the Library Furniture Working Group?” A fair response if you ask me, as we do have a Library Furniture Working Group tasked with the job of creating a functional space (complete with said furniture) for our now empty Microfiche room.  He explained it had nothing to do with carpentry actually, but was a software skills workshop aimed at information professionals borne from the &lt;a href=&quot;https://software-carpentry.org/&quot;&gt;Software Carpentry Foundation&lt;/a&gt;. Relieved, and with the image of me whittling a new piece of library furniture fading, I agreed to help.&lt;/p&gt;

&lt;h2 id=&quot;preparation&quot;&gt;Preparation&lt;/h2&gt;

&lt;p&gt;As this was my first time volunteering, it wasn’t a case of just turning up on the day. My line manager helpfully sent on the link to the online &lt;a href=&quot;https://librarycarpentry.github.io/lessons/#lessons&quot;&gt;lesson plans&lt;/a&gt; a couple of weeks in advance. Workshops are split into specific software sessions and each session is broken down into individual lessons with introductions, exercises, and examples throughout. Crucially, these exercises are the same ones attendees would be working through on the day and the questions I would be helping them with, should they have any difficulties. Having this information in advance meant I could familiarize myself with the material beforehand. It was all very new to me but I found the step-by-step information accessible and practical to work through. So far, so good. The particular lessons I would be helping with were Unix Shell, GitHub, and Open Refine. I worked through the lessons about a week in advance of the workshop.&lt;/p&gt;

&lt;p&gt;A couple of days before the workshop myself, my line manager (who would be delivering one of the sessions), and another helper met to run through the exercises together.  This was invaluable, as any uncertainties we had about particular sections were explained and solved at this stage.&lt;/p&gt;

&lt;h2 id=&quot;the-software-unix-shell-github-and-openrefine&quot;&gt;The software: &lt;a href=&quot;https://librarycarpentry.github.io/lc-shell/&quot;&gt;Unix Shell&lt;/a&gt;, &lt;a href=&quot;https://librarycarpentry.github.io/lc-git/01-what-is-git/&quot;&gt;GitHub&lt;/a&gt;, and &lt;a href=&quot;https://librarycarpentry.github.io/lc-open-refine/&quot;&gt;OpenRefine&lt;/a&gt;&lt;/h2&gt;

&lt;p&gt;Workshops generally cover a data introduction, Unix Shell, GitHub, and OpenRefine. Unix Shell is a command line interface that allows users to efficiently find and manipulate the metadata within their PCs’ directories and files. It does this without opening those files or directories within an application such as Microsoft Word. OpenRefine is a tool that makes cleaning and enhancing metadata relatively quick and easy. The interface resembles those of spreadsheets such as Microsoft Excel or Google Sheets, but offers more features and flexibility in terms of manipulating large data sets. GitHub is collaborative version control tool for those working on group projects, similar to Google Drive or SharePoint.&lt;/p&gt;

&lt;h2 id=&quot;the-workshop&quot;&gt;The Workshop&lt;/h2&gt;

&lt;p&gt;The workshop took place over the course of a working day and was broken into the four sessions. &lt;a href=&quot;https://twitter.com/j_w_baker&quot;&gt;Dr. James Baker&lt;/a&gt;, lecturer in Digital Humanities at the University of Sussex and founder of Library Carpentry, oversaw the workshop. Dr. Baker also delivered the first two sessions of the day: Data Intro and Unix Shell. An introductory session to GitHub followed, delivered by Rod Tatham co-founder of &lt;a href=&quot;https://twitter.com/SerenoUK&quot;&gt;local company Serano&lt;/a&gt;. &lt;a href=&quot;https://twitter.com/AntonyGroves&quot;&gt;Antony Groves&lt;/a&gt;, Learning and Teaching Librarian at the University of Sussex delivered the closing session covering OpenRefine.&lt;/p&gt;

&lt;p&gt;There was full attendance on the day - 15 people in total, with three instructors and three helpers. Attendees were a mix of public librarians, university librarians, FE and NHS librarians. “The group sat in pairs and shared access to devices if there was only one per table; there are a number of advantages to this &lt;a href=&quot;https://www.codefellows.org/blog/peer-programming-5-reasons-learning-in-a-group-beats-studying-on-your-own/&quot;&gt;peer programming&lt;/a&gt; approach.” In order to have a minimally disruptive method of asking for help, we gave each attendee two different colored post-it notes, one pink and one orange. They stuck the pink post-it note to the front of their laptop devices if they were able to work through an exercise with no problems. If they had difficulties or needed something clarified, they stuck the orange post-it instead. This acted as a prompt to the helpers in order for them to quickly identify and address any difficulties.&lt;/p&gt;

&lt;p&gt;Helpers sat at the back of the room during the delivery of the lesson; when the group worked through an exercise, helpers would wander around the room on hand to help when an attendee flagged the orange post-it note.&lt;/p&gt;

&lt;p&gt;Surprisingly there were very few instances were helpers were called upon by attendees and, those instances when we were, were for very quick easily corrected issues. The most frequently recurring difficulty during the Unix Shell lesson was incorrect inputting of text command - a simple typo, and once you know what the correct command format is it’s easily corrected. Another issue was attendees keeping up with the pace of the lesson. Naturally, we all work at varying levels of speed, and there were times when a person spent a little longer on an exercise than the majority and then lost their place for the next exercise. The majority of those attending were novices or complete beginners to the software we were exploring and that played a part in their seeking of help.&lt;/p&gt;

&lt;p&gt;During the OpenRefine session, there were again only a handful of instances that attendees required help. OpenRefine is an interface that I think information professionals are more familiar or comfortable navigating as it is a little like excel, and not as alien as the Shell interface. For that reason, I think it made our jobs as helpers easier, and our help was needed less often.&lt;/p&gt;

&lt;h2 id=&quot;help-is-at-hand&quot;&gt;Help is at hand&lt;/h2&gt;

&lt;p&gt;If you are considering volunteering as a helper, you might find the below useful to know in advance of a workshop:&lt;/p&gt;

&lt;ol&gt;
  &lt;li&gt;The &lt;a href=&quot;https://librarycarpentry.github.io/blog/&quot;&gt;Library Carpentry&lt;/a&gt; and &lt;a href=&quot;https://software-carpentry.org/blog/&quot;&gt;Software Carpentry&lt;/a&gt; blogs are full of useful information and blog posts by other volunteers so you know what to expect. I didn’t know about the blogs before the workshop and only discovered them afterward. It definitely would have been helpful to skim through in advance.&lt;/li&gt;
  &lt;li&gt;Library Carpentry is completely volunteer led. We are all giving up our time to spread knowledge and information. Helpers are not expected to be complete experts in this field, so don’t feel you have to have a solution to every problem.&lt;/li&gt;
  &lt;li&gt;Be familiar with the lesson material and structure. &lt;a href=&quot;https://librarycarpentry.github.io/lessons/&quot;&gt;Lesson plans are available online&lt;/a&gt; and all exercises come with solutions. I printed these off in advance so I would have them during the workshop to refer back to, making it much easier to answer any questions on the day. This was also helpful when I was trying to follow along in the session and anticipate what was going to be covered next.&lt;/li&gt;
  &lt;li&gt;Do a dry run of the exercises in advance on multiple operating systems - Macs, non-Windows, and Windows. Each operating system brings with it its own nuances, such as slightly different commands for example. It was invaluable doing a run through of all the exercises on the different systems, as it not only meant I was familiar with how each setting works, but more importantly familiar with the issues and difficulties they threw up in advance of the session.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2 id=&quot;takeaways&quot;&gt;Takeaways&lt;/h2&gt;

&lt;p&gt;I highly recommend volunteering as a helper, especially if you are unfamiliar with Library Carpentry. That might sound ill-advised, but I think it makes perfect sense. The role of helper allowed me to develop a greater understanding and working knowledge of the software taught, than I would have had I attended the workshop as a learner, because I had to prepare and familiarize myself with the lesson materials in advance. As another helper noted: it reinforces your own learning. Volunteering at workshops such as these helps us to keep up-to-date with current practices and advancements in the LIS field. There’s also something very enjoyable and rewarding about being a part of a community of professionals volunteering their free time to the continuing professional development of others. Now I’d imagine that’s a far greater return than the Furniture Working Group…&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Many thanks to &lt;a href=&quot;https://twitter.com/j_w_baker&quot;&gt;Dr James Baker&lt;/a&gt; &lt;a href=&quot;https://twitter.com/AntonyGroves&quot;&gt;Antony Groves&lt;/a&gt; and &lt;a href=&quot;https://twitter.com/SerenoUK&quot;&gt;Rod Tatham&lt;/a&gt; for delivering such an enlightening and engaging workshop.&lt;/em&gt;&lt;/p&gt;
</description>
        <pubDate>Fri, 04 Aug 2017 00:00:00 +0000</pubDate>
        <link>https://librarycarpentry.github.io//helping-the-helper/</link>
        <guid isPermaLink="true">https://librarycarpentry.github.io//helping-the-helper/</guid>
      </item>
    
      <item>
        <title>Library Carpentry at the University of Sussex</title>
        <description>&lt;p&gt;Post by &lt;a href=&quot;https://twitter.com/j_w_baker&quot;&gt;James Baker&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Last Wednesday 14 Librarians from 8 libraries in the Brighton area convenved at the &lt;a href=&quot;http://www.sussex.ac.uk/shl/&quot;&gt;Sussex Humanities Lab&lt;/a&gt; for a Library Carpentry workshop. The session was organised by the University of Sussex Library and colleagues from there were out in force both to instruct and as helpers. The workshop covered &lt;a href=&quot;https://librarycarpentry.github.io/lc-data-intro/04-regular-expressions/&quot;&gt;Regular Expressions&lt;/a&gt;, &lt;a href=&quot;https://librarycarpentry.github.io/lc-shell/&quot;&gt;Shell&lt;/a&gt;, Git (in a short introductory session organised by &lt;a href=&quot;https://twitter.com/SerenoUK&quot;&gt;local company Serano&lt;/a&gt;), and &lt;a href=&quot;https://librarycarpentry.github.io/lc-open-refine/&quot;&gt;OpenRefine&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;http://www.youtube.com/watch?feature=player_embedded&amp;amp;v=Hf7K02MlYDg &quot; target=&quot;_blank&quot;&gt;&lt;img src=&quot;http://img.youtube.com/vi/Hf7K02MlYDg/0.jpg&quot; alt=&quot;Library Carpentry Sussex&quot; width=&quot;240&quot; height=&quot;180&quot; border=&quot;10&quot; /&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;As ever Refine was a hit. As one attendee wrote in their feedback:&lt;/p&gt;

&lt;blockquote&gt;
  &lt;p&gt;OpenRefine definitely offers improvements to working with Excel alone&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;But learners looked positively upon the other sessions as well. On Shell, for example, one learner reported:&lt;/p&gt;

&lt;blockquote&gt;
  &lt;p&gt;Explanation of commands easier to understand than expected&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Breaking down perceived barriers between librarians and computational skills is central to the mission of Library Carpentry. And whilst there is still work to do - learners reported wanting to know a greater sense of the big picture for using Shell and more time to grasp the meaning of terms like ‘array’ and ‘string’ - the workshop clearly struck a chord: a discussion over coffee on how to integrate Shell, Git, and OpenRefine into existing workflows suggested attendees could see the potential for using these tools in their work.&lt;/p&gt;

&lt;p&gt;My thanks to Rod Tatham and &lt;a href=&quot;https://twitter.com/AntonyGroves&quot;&gt;Antony Groves&lt;/a&gt;for instructing. Back in 2015 Antony attended &lt;a href=&quot;https://cradledincaricature.com/2015/12/01/library-carpentry-in-words-and-numbers-all-code-no-woodwork/&quot;&gt;the very first Library Carpentry&lt;/a&gt;: it is great to see someone transition from learner to instructor in such a short period of time.&lt;/p&gt;
</description>
        <pubDate>Mon, 17 Jul 2017 00:00:00 +0000</pubDate>
        <link>https://librarycarpentry.github.io//Sussex/</link>
        <guid isPermaLink="true">https://librarycarpentry.github.io//Sussex/</guid>
      </item>
    
      <item>
        <title>Teaching Library Carpentry at the New Librarians' Symposium</title>
        <description>&lt;p&gt;Post by &lt;a href=&quot;https://twitter.com/machinical&quot;&gt;Carmi Cronje&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;My colleague &lt;a href=&quot;https://twitter.com/FionaJ_Lib&quot;&gt;Fiona Jones&lt;/a&gt; and I recently taught a workshop called &lt;strong&gt;Introduction 
to the Library Carpentry Toolbox&lt;/strong&gt; at the &lt;a href=&quot;http://www.nla.gov.au/&quot;&gt;National Library Australia (NLA)&lt;/a&gt; for the &lt;a href=&quot;http://nls8.com/program/&quot;&gt;ALIA New Librarians’ Symposium (NLS)&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The New Librarians’ Symposium is held every two years - aimed at LIS and GLAMR students, managers, mentors, coders, hackers and more. This year’s was themed &lt;strong&gt;DIY Library Career&lt;/strong&gt;, and held in Canberra 23rd-25th June. It was our first time at NLS so we weren’t sure what to expect, but it didn’t take long to get a sense of the positive environment outlined in their &lt;a href=&quot;https://web.archive.org/web/20171003193455/http://nls8.com/inclusion-statement/&quot;&gt;Inclusion Statement&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;We ran this introduction to Library Carpentry as a three-hour workshop, and had 20 learners packed into 
&lt;a href=&quot;https://www.nla.gov.au/venue-hire#L4ITtrainingroom&quot;&gt;NLA’s IT Training Room&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;In the first 45 minutes, Fiona and I talked about:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;Our context: Macquarie University, the Library and being a Research Librarian&lt;/li&gt;
  &lt;li&gt;How we got involved with Library Carpentry&lt;/li&gt;
  &lt;li&gt;How Library Carpentry came about, what it’s for and what it teaches&lt;/li&gt;
  &lt;li&gt;Examples of how we’ve applied &lt;code class=&quot;highlighter-rouge&quot;&gt;OpenRefine&lt;/code&gt; (which they were about to learn) to our work, and&lt;/li&gt;
  &lt;li&gt;Last but not least, the &lt;a href=&quot;https://librarycarpentry.github.io&quot;&gt;Library Carpentry&lt;/a&gt; community.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;We learned later via our feedback survey that &lt;a href=&quot;https://misskokothelibrarian.com/2017/06/26/conference-day-1-of-nls8/&quot;&gt;the introduction was too long&lt;/a&gt; and learners would have preferred more ‘learning by doing’. The first part was wrapped up with a true/false quiz about Library Carpentry, which got neighbours talking and the room buzzing. A few librarians mentioned finding the background information useful, e.g. ‘I didn’t know that Library Carpentry was its own community’.&lt;/p&gt;

&lt;p&gt;In the last two hours we taught the Library Carpentry &lt;a href=&quot;https://librarycarpentry.github.io/lc-open-refine/&quot;&gt;OpenRefine lesson&lt;/a&gt;, 
created by &lt;a href=&quot;https://twitter.com/ostephens&quot;&gt;Owen Stephens&lt;/a&gt;. Fiona set the scene by explaining … ‘we’re here to help each other, 
this is a safe learning space’, and the use of the sticky note system … ‘if you need help, flag our attention by placing a 
pink sticky note on top of your monitor’. Our group was respectful and loved what they were learning. It was fantastic to hear the ‘aha’ moments and their engagement as we worked through the exercises.&lt;/p&gt;

&lt;h2 id=&quot;positive-feedback-about-the-lesson-material-included&quot;&gt;Positive feedback about the lesson material included:&lt;/h2&gt;

&lt;ul&gt;
  &lt;li&gt;‘Real life examples &amp;amp; future applications’&lt;/li&gt;
  &lt;li&gt;‘Structure &amp;amp; organisation …’&lt;/li&gt;
  &lt;li&gt;‘How easy it was to use, and [how] intuitive’&lt;/li&gt;
  &lt;li&gt;‘Making connections with participants prior knowledge, e.g. similar features to Excel’&lt;/li&gt;
  &lt;li&gt;‘Knowing that I can apply what we covered in the real world!’&lt;/li&gt;
  &lt;li&gt;‘… Already seeing the potential’&lt;/li&gt;
  &lt;li&gt;‘It was really clear and an intuitive progression through the process’&lt;/li&gt;
  &lt;li&gt;‘Showing how database management is doable for someone like me who isn’t geeky. I love cleaning up and streamlining things, 
and now I know I could do this with data if I wanted to - that data is ultimately things to be managed.’&lt;/li&gt;
&lt;/ul&gt;

&lt;h2 id=&quot;critical-feedback-was-constructive-as-well&quot;&gt;Critical feedback was constructive as well:&lt;/h2&gt;

&lt;ul&gt;
  &lt;li&gt;‘Potential is huge - but will need to pass the gatekeepers on home turf’&lt;/li&gt;
  &lt;li&gt;‘A hand-out with key functions covered would have been useful :)’&lt;/li&gt;
  &lt;li&gt;‘The slight feeling of overwhelm (which probably just means I was learning something new!)’&lt;/li&gt;
  &lt;li&gt;‘Because this is so far outside what I do and what I’ve always considered wanting to do, it was a little challenging
 thinking of applications. I would have liked some more examples of how it can be used apart from journals, 
 (as someone not working with academic resources).’&lt;/li&gt;
&lt;/ul&gt;

&lt;h2 id=&quot;what-did-we-learn-from-this-experience&quot;&gt;What did we learn from this experience?&lt;/h2&gt;

&lt;ul&gt;
  &lt;li&gt;External workshops take a lot of preparation and planning. You need a strong comrade-in-arms to keep you on track. Thanks &lt;a href=&quot;https://twitter.com/FionaJ_Lib&quot;&gt;FJ&lt;/a&gt;.&lt;/li&gt;
  &lt;li&gt;Communicating technical requirements long distance is difficult. Once you arrive, you can only hope nothing was lost in translation. NLS8 co-convener &lt;a href=&quot;https://twitter.com/sallyturbitt&quot;&gt;Sally Turbitt&lt;/a&gt; and committee member &lt;a href=&quot;https://twitter.com/GoAskJay&quot;&gt;Jay&lt;/a&gt; did a superb job. Jay also stayed to make sure all went smoothly.&lt;/li&gt;
  &lt;li&gt;We would have liked to have known more about our learners (a few even joined us from a waitlist queue outside the room!). In hindsight we should have cut down our introduction and opened up to the room instead.&lt;/li&gt;
  &lt;li&gt;It would have been useful for us to incorporate the collaborative note-taking tool, Etherpad, a popular part of Carpentry workshops, into our session. We could have used it to paste OpenRefine &lt;code class=&quot;highlighter-rouge&quot;&gt;GREL&lt;/code&gt; expressions for participants to refer to, and as a space for learners to record their thoughts and questions for the Q&amp;amp;A. Another benefit of using Etherpad is that it lives on, so attendees can revisit it later or share the information with colleagues.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2 id=&quot;how-did-learners-feel-about-library-carpentry-after-the-workshop&quot;&gt;How did learners feel about Library Carpentry after the workshop?&lt;/h2&gt;

&lt;p&gt;There were lots of tweets - check out &lt;a href=&quot;https://twitter.com/inlibraryland/status/878133590344646656&quot;&gt;one&lt;/a&gt;, &lt;a href=&quot;https://twitter.com/lissertations/status/878124981309235201&quot;&gt;two&lt;/a&gt;, &lt;a href=&quot;https://twitter.com/debfuller66/status/878121277289934848&quot;&gt;three&lt;/a&gt;, &lt;a href=&quot;https://twitter.com/AnitrarossB/status/878118816349274112&quot;&gt;four&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Where to from here?&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;Read about what happened at this year’s &lt;a href=&quot;https://software-carpentry.org/blog/2017/06/lc-sprint.html&quot;&gt;Mozilla Science Lab Global Sprint&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;Chat with the &lt;a href=&quot;https://gitter.im/LibraryCarpentry/Lobby&quot;&gt;Library Carpentry community via Gitter&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;Follow &lt;a href=&quot;https://twitetr.com/LibCarpentry&quot;&gt;Library Carpentry on Twitter&lt;/a&gt; and browse the latest #librarycarpentry tweets&lt;/li&gt;
  &lt;li&gt;&lt;a href=&quot;https://librarycarpentry.github.io/&quot;&gt;Find out more&lt;/a&gt; …&lt;/li&gt;
&lt;/ul&gt;
</description>
        <pubDate>Thu, 06 Jul 2017 00:00:00 +0000</pubDate>
        <link>https://librarycarpentry.github.io//nls8/</link>
        <guid isPermaLink="true">https://librarycarpentry.github.io//nls8/</guid>
      </item>
    
      <item>
        <title>Library Carpentry chatrooms proliferate</title>
        <description>&lt;p&gt;After the massive success of the &lt;a href=&quot;https://software-carpentry.org/blog/2017/06/lc-sprint.html&quot;&gt;2017 global sprint&lt;/a&gt;, the Library 
Carpentry community decided it was time for create new chatrooms to handle the increasing volume of posts.&lt;/p&gt;

&lt;p&gt;There are now three rooms - the &lt;a href=&quot;https://gitter.im/LibraryCarpentry/Lobby&quot;&gt;Lobby&lt;/a&gt; which is a bit of a social, ‘meet-and-greet’ 
kind of place; &lt;a href=&quot;https://gitter.im/LibraryCarpentry/lesson-dev&quot;&gt;lesson-dev&lt;/a&gt; for discussing lesson ideas, planning and maintenance;
and a third room, &lt;a href=&quot;https://gitter.im/LibraryCarpentry/lesson-dev&quot;&gt;workshops&lt;/a&gt;, for questions, discussions and debriefs about workshops past 
and upcoming.&lt;/p&gt;

&lt;p&gt;Instructions have been posted in the old chatroom about how to join the new one.&lt;/p&gt;

&lt;p&gt;As before, anyone can join any or all of the chatrooms with their GitHub or Twitter credentials.&lt;/p&gt;

&lt;p&gt;We look forward to welcoming you to our new rooms.&lt;/p&gt;
</description>
        <pubDate>Mon, 03 Jul 2017 00:00:00 +0000</pubDate>
        <link>https://librarycarpentry.github.io//chatrooms/</link>
        <guid isPermaLink="true">https://librarycarpentry.github.io//chatrooms/</guid>
      </item>
    
      <item>
        <title>Library Carpentry workshop call</title>
        <description>&lt;p&gt;Library Carpentry is software skills training aimed at the needs and requirements of library professionals (that is, coding and data manipulation that goes beyond the use of familiar office suites). It is made &lt;strong&gt;by librarians, for librarians&lt;/strong&gt; to help you:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;automate repetitive, boring, error-prone tasks&lt;/li&gt;
  &lt;li&gt;create, maintain and analyse sustainable and reusable data&lt;/li&gt;
  &lt;li&gt;work effectively with IT and systems colleagues&lt;/li&gt;
  &lt;li&gt;better understand the use of software in research&lt;/li&gt;
  &lt;li&gt;&lt;em&gt;and much more..&lt;/em&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Training takes places in face-to-face workshops where one or more of the developed modules are taught. Modules are also made available online (&lt;a href=&quot;https://librarycarpentry.github.io/lc-data-intro/license/&quot;&gt;CC BY&lt;/a&gt;, published via GitHub Pages) for self-directed study or for adaption and reuse by library professionals.&lt;/p&gt;

&lt;p&gt;Thanks to the generosity of &lt;a href=&quot;http://labs.bl.uk/&quot;&gt;British Library Labs&lt;/a&gt;, Library Carpentry has £500 (or non-GBP equivalent) available to an individual or group who wish to run a Library Carpentry workshop at a library or for librarians. A Library Carpentry workshop is a face-to-face event where one or more of the currently developed modules are taught. Each module is designed to be taught over a half-day and a typical workshop combines these over one or more days, consecutive or otherwise (for more on what a Library Carpentry workshop is, see our &lt;a href=&quot;https://librarycarpentry.github.io/about/&quot;&gt;About&lt;/a&gt; page).&lt;/p&gt;

&lt;p&gt;Applications for these funds should include the following information:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;Where the workshop will be held&lt;/li&gt;
  &lt;li&gt;The workshop host and a contact email address&lt;/li&gt;
  &lt;li&gt;The workshop instructors(s) and helper(s)&lt;/li&gt;
  &lt;li&gt;The format of the workshop
    &lt;ul&gt;
      &lt;li&gt;For example: 1 day, 2 consecutive days, 3 non-consecutive half-days (or whatever format works for you)&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;Which Library Carpentry modules will be taught
    &lt;ul&gt;
      &lt;li&gt;Maintained lessons are ‘Data Intro for Librarians’, ‘Unix Shell for Librarians’, ‘Git Intro for Librarians’, ‘OpenRefine for Librarians’, and ‘SQL for Libraries’. See https://github.com/librarycarpentry. If you want to teach something else, describe what it is and why you want to teach it&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;How many people the workshops hopes to accomodate&lt;/li&gt;
  &lt;li&gt;The communities that will be targeted and why those communities are important&lt;/li&gt;
  &lt;li&gt;Plans to capture feedback from attendees that will aid the future development of Library Carpentry&lt;/li&gt;
  &lt;li&gt;The expected media presence of the workshop (before, during, and after)&lt;/li&gt;
  &lt;li&gt;What the money will be spent on. This can be used to cover:
    &lt;ul&gt;
      &lt;li&gt;Travel expenses for trainers&lt;/li&gt;
      &lt;li&gt;Refreshments for attendees&lt;/li&gt;
      &lt;li&gt;Room bookings&lt;/li&gt;
      &lt;li&gt;If you want to fund something else, ask James at &lt;a href=&quot;mailto:james.baker@sussex.ac.uk&quot;&gt;james.baker@sussex.ac.uk&lt;/a&gt; before submitting your application.&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Applications should be sent as an attachment to &lt;a href=&quot;mailto:james.baker@sussex.ac.uk&quot;&gt;james.baker@sussex.ac.uk&lt;/a&gt; by 16 December 2016. The funded workshop should take place by July 2017. Applicatants will be notified in early-January 2017. Those that are not selected, we’ll do our best to support in some way!&lt;/p&gt;

&lt;p&gt;By &lt;a href=&quot;drjwbaker&quot;&gt;James Baker&lt;/a&gt;&lt;/p&gt;
</description>
        <pubDate>Tue, 01 Nov 2016 00:00:00 +0000</pubDate>
        <link>https://librarycarpentry.github.io//workshop-call/</link>
        <guid isPermaLink="true">https://librarycarpentry.github.io//workshop-call/</guid>
      </item>
    
      <item>
        <title>Library Carpentry is coming to Africa</title>
        <description>&lt;p&gt;The first Library Carpentry workshop in Africa will be held in Pretoria, South Africa on August 25 &amp;amp; 26.  Here is the &lt;a href=&quot;https://cmacdonell.github.io/2016-08-25-CSIR/&quot;&gt;site&lt;/a&gt; for the workshop which is being
generously hosted by &lt;a href=&quot;http://www.csir.co.za/&quot;&gt;CSIR&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;This Library Carpentry workshop is supported by &lt;a href=&quot;https://nedicc.com/&quot;&gt;NeDICC&lt;/a&gt;, &lt;a href=&quot;http://nwu.ac.za/&quot;&gt;North-West University&lt;/a&gt; and &lt;a href=&quot;http://www.talarify.co.za/&quot;&gt;Talarify&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;By &lt;a href=&quot;cmacdonell&quot;&gt;Cam Macdonell&lt;/a&gt;&lt;/p&gt;
</description>
        <pubDate>Fri, 19 Aug 2016 00:00:00 +0000</pubDate>
        <link>https://librarycarpentry.github.io//africa/</link>
        <guid isPermaLink="true">https://librarycarpentry.github.io//africa/</guid>
      </item>
    
      <item>
        <title>Library Carpentry - update</title>
        <description>&lt;p&gt;Last week a global team of volunteers spent two days improving and enriching the original Library Carpentry materials. Belinda Weaver describes this AMAZING effort in a &lt;a href=&quot;http://software-carpentry.org/blog/2016/06/LibrarCarpentrysprint.html&quot;&gt;blog post&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The upshot of this is that the original materials have been superseded. To find the latest Library Carpentry lessons, please now head to &lt;a href=&quot;https://github.com/librarycarpentry&quot;&gt;https://github.com/librarycarpentry&lt;/a&gt; where the community will continue to update, maintain, and improve the lesson materials as they as used and reused across the globe!&lt;/p&gt;

&lt;p&gt;Library Carpentry was funded by the &lt;a href=&quot;http://software.ac.uk/&quot;&gt;Software Sustainability Institute&lt;/a&gt;. The Software Sustainability Institute cultivates world-class research with software. The Institute is based at the universities of Edinburgh, Manchester, Southampton and Oxford.&lt;/p&gt;

&lt;p&gt;By &lt;a href=&quot;drjwbaker&quot;&gt;James Baker&lt;/a&gt;&lt;/p&gt;
</description>
        <pubDate>Tue, 07 Jun 2016 00:00:00 +0000</pubDate>
        <link>https://librarycarpentry.github.io//update/</link>
        <guid isPermaLink="true">https://librarycarpentry.github.io//update/</guid>
      </item>
    
      <item>
        <title>Library Carpentry - Fin, for now</title>
        <description>&lt;p&gt;Library Carpentry was an exploratory programme of four three-hour software skills sessions focused on the needs and requirements of the library professionals. For further details, see the &lt;a href=&quot;https://librarycarpentry.github.io/outline/&quot;&gt;outline post&lt;/a&gt;. Sessions were held on Monday the 9th, 16th, 23th, and 30th of November 2015 at City University London. We thank the &lt;a href=&quot;https://www.city.ac.uk/department-library-information-science/centre-for-information-science&quot;&gt;Centre for Information Science&lt;/a&gt; for generously agreeing to host Library Carpentry.&lt;/p&gt;

&lt;p&gt;Library Carpentry is far from over, but we now into a phase of reflection and planning. If you are interested in what happened during this exploratory run, I direct your attention to two blog posts:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;James Baker, ‘&lt;a href=&quot;http://cradledincaricature.com/2015/12/01/library-carpentry-in-words-and-numbers-all-code-no-woodwork/&quot;&gt;Library Carpentry in words and numbers: all code, no woodwork&lt;/a&gt;’ (1 December 2015)&lt;/li&gt;
  &lt;li&gt;Clare Playforth, ‘&lt;a href=&quot;http://software.ac.uk/blog/2015-12-03-why-information-profession-needs-library-carpentry-0&quot;&gt;Why the information profession needs Library Carpentry&lt;/a&gt;’ (3 December 2015)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;More information or to discuss putting on a future event, please contact me via &lt;a href=&quot;https://twitter.com/j_w_baker&quot;&gt;Twitter&lt;/a&gt; or &lt;a href=&quot;http://www.sussex.ac.uk/profiles/371022&quot;&gt;Email&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Library Carpentry is funded by the &lt;a href=&quot;http://software.ac.uk/&quot;&gt;Software Sustainability Institute&lt;/a&gt;. The Software Sustainability Institute cultivates world-class research with software. The Institute is based at the universities of Edinburgh, Manchester, Southampton and Oxford.&lt;/p&gt;

&lt;p&gt;By &lt;a href=&quot;drjwbaker&quot;&gt;James Baker&lt;/a&gt;&lt;/p&gt;
</description>
        <pubDate>Thu, 03 Dec 2015 00:00:00 +0000</pubDate>
        <link>https://librarycarpentry.github.io//fin/</link>
        <guid isPermaLink="true">https://librarycarpentry.github.io//fin/</guid>
      </item>
    
  </channel>
</rss>