Yes Karen, as I recall, as we prioritized, we wanted to focus on the novice, then, we looked at the subject matter that rose to the top (as foundational) AND would fit in a 2-day structure.
We did do OpenRefine at the first DC, but as a Demo. I do seem to recall discussions at SESYNC though, that versioning was challenging to teach to novices. But I concur, that's not the main reason we left if out. For my self, I think it's like much of what we teach, where the motivation is key. That is, if I need to learn versioning to work with my colleagues, or to work with my code, then "it's time to jump in." But, it's difficult to start with versioning if you're just starting to learn how to better organize, structure, and query data. Best, Deb On 2019-10-16 12:40 PM, Karen Cranston wrote: As I remember it (and other early DC-ers should chime in here), we didn't choose not to teach git because git is hard, but rather prioritized the skills we thought were necessary for better data management, and version control wasn't close enough to the top to warrant an episode in a two-day workshop. Note also that the early DC curriculum included bash and bash scripting (see the blog post [1] and first course website [2]), which we later removed in favour of episodes on spreadsheets and open refine [3]. So, I can't corroborate the statement that DC doesn't teach git and GitHub because they are hard. Cheers, Karen [1] https://software-carpentry.org/blog/2014/05/our-first-data-carpentry-workshop.html<https://urldefense.com/v3/__https://software-carpentry.org/blog/2014/05/our-first-data-carpentry-workshop.html__;!5Xm4_O-4tfk!mRf9m27iM9RMvCIK4J3krmBNSL0F3q1EpRn64NhLyswfRpvDR8gd3HhZPBRVQA$> [2] http://nescent.github.io/2014-05-08-datacarpentry/<https://urldefense.com/v3/__http://nescent.github.io/2014-05-08-datacarpentry/__;!5Xm4_O-4tfk!mRf9m27iM9RMvCIK4J3krmBNSL0F3q1EpRn64NhLyswfRpvDR8gd3HjZTQQbfQ$> [3] https://datacarpentry.org/lessons/#ecology-workshop<https://urldefense.com/v3/__https://datacarpentry.org/lessons/*ecology-workshop__;Iw!5Xm4_O-4tfk!mRf9m27iM9RMvCIK4J3krmBNSL0F3q1EpRn64NhLyswfRpvDR8gd3HjBbuLDsg$> On Wed, Oct 16, 2019 at 12:22 PM Brooks Kieffer, Elizabeth Jamene <[email protected]<mailto:[email protected]>> wrote: Hi everyone, I’m reading the Baker et al article about the initial instance of Library Carpentry (Baker, J., et al, (2016). Library Carpentry: Software skills training for library professionals. LIBER Quarterly, 26(3), 141–162. https://doi.org/10.18352/lq.10176<https://urldefense.com/v3/__https://doi.org/10.18352/lq.10176__;!5Xm4_O-4tfk!mRf9m27iM9RMvCIK4J3krmBNSL0F3q1EpRn64NhLyswfRpvDR8gd3HiD3FyjcA$>). In the Next Steps section, the authors mention learners’ struggles with Git during this workshop, and note that other curricula exclude Git because of its difficulty. Specifically: “…this is a finding of comparable training programmes and is a reason for Data Carpentry not teaching Git and GitHub” (p. 158). There isn’t a citation for the information about why Data Carpentry doesn’t teach Git and GitHub, and the Teal et al article describing Data Carpentry doesn’t mention Git (Teal, T. K., et al, (2015). Data Carpentry: Workshops to Increase Data Literacy for Researchers. International Journal of Digital Curation, 10, 135–143. https://doi.org/10.2218/ijdc.v10i1.351<https://urldefense.com/v3/__https://doi.org/10.2218/ijdc.v10i1.351__;!5Xm4_O-4tfk!mRf9m27iM9RMvCIK4J3krmBNSL0F3q1EpRn64NhLyswfRpvDR8gd3Hj2qzjT7w$>). I would appreciate any insight and/or links to discussions specifically about this decision to exclude Git from Data Carpentry. I’m not interested in debating the decision. Rather, I’m working on a paper on teaching Git; documentation of this discussion would be helpful supporting information for the paper’s opening contention that Git is difficult to both teach and learn (something that’s not news to this group!). Thanks very much in advance, Jamene Jamene Brooks-Kieffer Data Services Librarian University of Kansas Libraries 785-864-5238 [email protected]<mailto:[email protected]> she/her/hers -- ~~~~~~~~~~~~~~~~~~~~~~~ [email protected]<mailto:[email protected]> kcranston.github.io<https://urldefense.com/v3/__http://kcranston.github.io__;!5Xm4_O-4tfk!mRf9m27iM9RMvCIK4J3krmBNSL0F3q1EpRn64NhLyswfRpvDR8gd3HgkfP_m8A$> @kcranstn ~~~~~~~~~~~~~~~~~~~~~~~ The Carpentries<https://urldefense.com/v3/__https://carpentries.topicbox.com/latest__;!5Xm4_O-4tfk!mRf9m27iM9RMvCIK4J3krmBNSL0F3q1EpRn64NhLyswfRpvDR8gd3HgWriYRPw$> / discuss / see discussions<https://urldefense.com/v3/__https://carpentries.topicbox.com/groups/discuss__;!5Xm4_O-4tfk!mRf9m27iM9RMvCIK4J3krmBNSL0F3q1EpRn64NhLyswfRpvDR8gd3HgmJJoUIw$> + participants<https://urldefense.com/v3/__https://carpentries.topicbox.com/groups/discuss/members__;!5Xm4_O-4tfk!mRf9m27iM9RMvCIK4J3krmBNSL0F3q1EpRn64NhLyswfRpvDR8gd3Hi7uzQhUA$> + delivery options<https://urldefense.com/v3/__https://carpentries.topicbox.com/groups/discuss/subscription__;!5Xm4_O-4tfk!mRf9m27iM9RMvCIK4J3krmBNSL0F3q1EpRn64NhLyswfRpvDR8gd3HgCOF1I6g$> Permalink<https://urldefense.com/v3/__https://carpentries.topicbox.com/groups/discuss/T914cb72e74e12319-M388c8792d2085f1e44cb664b__;!5Xm4_O-4tfk!mRf9m27iM9RMvCIK4J3krmBNSL0F3q1EpRn64NhLyswfRpvDR8gd3HgpM8cJlw$> -- -- Upcoming iDigBio Events https://www.idigbio.org/calendar -- Deborah Paul, iDigBio Digitization and Workforce Development Manager iDigBio -- Steering Committee Member SPNHC Liaison, Member-At-Large and Member International Relations Committee SYNTHESYS3 Representative, ICEDIG External Advisory Board Member Vice Chair, Biodiversity Information Standards Organisation (TDWG)(2019-2020) Institute for Digital Information, 234 LSB Florida State University Tallahassee, Florida 32306 850-644-6366 ------------------------------------------ The Carpentries: discuss Permalink: https://carpentries.topicbox.com/groups/discuss/T914cb72e74e12319-M3c5564d950dbf094d16bb690 Delivery options: https://carpentries.topicbox.com/groups/discuss/subscription
