create repo

Author: drjwbaker

.DS_Store

@@ -0,0 +1,3 @@
+Library Carpentry is authored and maintained by the [community](https://github.com/data-lessons/library-data-intro/network/members).
+
+Credit for the Library Carpentry logos goes to [Tammy Nguyen](https://twitter.com/tammysongnguyen).

AUTHORS

@@ -0,0 +1,5 @@
+Please cite as:
+
+Library Carpentry:
+"Data Intro for Librarians."
+June 2016, http://data-lessons.github.io/library-data-intro/.

CITATION

@@ -0,0 +1,51 @@
+# Library Carpentry
+
+The Library Carpentry module '[Data Intro for Librarians](http://data-lessons.github.io/library-data-intro/)' is maintained by [Carmi Cronje](https://github.com/ccronje) and [James Baker](https://github.com/drjwbaker).
+
+## Background
+
+Library Carpentry is a software skills training programme aimed at library and information professions. It builds on the work of [Software Carpentry](http://software-carpentry.org/) and [Data Carpentry](http://www.datacarpentry.org/).
+
+These materials are based on the **Library Carpentry** materials initially developed and taught by [James Baker](https://github.com/drjwbaker), [Owen Stephens](https://github.com/ostephens) and [Daniel van Strien](https://github.com/davanstrien) in 2015.
+[http://librarycarpentry.github.io/outline/](http://librarycarpentry.github.io/outline/). The original Library Carpentry contained four modules:
+
+- Introduction, including jargon busting, data structures and regular expressions
+- The Unix shell, including use of the command line and commands such as`grep` and `sed` to find data within files
+- Git and version control
+- Using OpenRefine for data clean up.
+
+On 2-3 June 2016 during the [Mozilla Science Lab Global Sprint](https://science.mozilla.org/programs/events/global-sprint-2016) these existing four repositories were forked (links below) and re-developed within individual repositories, with the addition of a fifth module that introduces **SQL**, a topic which many librarians have expressed interest in learning. 
+
+- [library-data-intro](https://github.com/data-lessons/library-data-intro)
+- [library-shell](https://github.com/data-lessons/library-shell)
+- [library-git](https://github.com/data-lessons/library-git)
+- [library-openrefine](https://github.com/data-lessons/library-openrefine)
+- [library-sql](https://github.com/data-lessons/library-sql)
+
+The Library Carpentry sprint was co-ordinated by [Belinda Weaver](https://github.com/weaverbel) and attracted global participation.
+
+## Contribution
+
+There are many ways of contributing to Library Carpentry:
+
+- Join our [Gitter discussion forum](https://gitter.im/weaverbel/LibraryCarpentry).
+- Follow updates on [Twitter](https://twitter.com/search?f=tweets&vertical=default&q=%23librarycarpentry&src=typd).
+- Make a suggestion or correct an error by [raising an Issue](https://github.com/data-lessons/library-data-intro/issues).
+
+## Code of Conduct
+
+All participants should agree to abide by the [Software Carpentry Code of Conduct](http://software-carpentry.org/conduct/).
+
+## Authors
+
+Library Carpentry is authored and maintained by the [community](https://github.com/data-lessons/library-data-intro/network/members).
+
+## Citation
+
+Please cite as:
+
+Library Carpentry. Data Intro for Librarians. June 2016. http://data-lessons.github.io/library-data-intro/.
+
+## License
+
+All the lessons are licensed under a [Creative Commons Attribution-ShareAlike 4.0 International License](http://creativecommons.org/licenses/by-sa/4.0/). **Exceptions: embeds to and from external sources, and direct quotations from speakers.**

README.md

@@ -0,0 +1,10 @@
+---
+layout: page
+title: Discussion
+permalink: /discuss/
+---
+There are many ways to discuss Library Carpentry lessons:
+
+- Join our [Gitter discussion forum](https://gitter.im/weaverbel/LibraryCarpentry).
+- Follow updates on [Twitter](https://twitter.com/search?f=tweets&vertical=default&q=%23librarycarpentry&src=typd).
+- Make a suggestion or correct an error by [raising an Issue](https://github.com/data-lessons/library-data-intro/issues).

_extras/discuss.md

@@ -0,0 +1,236 @@
+---
+layout: page
+title: "Instructor Notes"
+permalink: /guide/
+---
+
+____
+# Making a handout
+
+Librarians like handouts. To make a handout for the [Regular Expressions episode](http://data-lessons.github.io/library-data-intro/04-regular-expressions/) do the following:
+
+- download the reference.md page for this lesson from [https://raw.githubusercontent.com/data-lessons/library-data-intro/gh-pages/reference.md](https://raw.githubusercontent.com/data-lessons/library-data-intro/gh-pages/reference.md) (right click, save page as). 
+- open the reference.md in a text editor and remove the header (the first five lines). Note for Windows users: if '.txt' has been added to the filename, resave without the '.txt'. 
+- you now have a markdown file ready to convert to .docx or .pdf for printing. Now either:
+  - *either* head to a webservice like [Dillinger](http://dillinger.io/), paste your markdown in the left hand columns, and use the 'Export As' dropdown to create a pdf document.
+  - *or* download and install [pandoc], open the shell, and from the directory the markdown file is in run `pandoc reference.md -f markdown -t docx -s -o reference.md`
+  
+____
+# General
+
+Two sets of sticky notes (ideally one red and one blue) are required to run a Library Carpentry workshop. Learners should be encouraged to put a red sticky note on the back of their laptop (raised like a flag) if they need help, and to put the blue sticky note on the back of their laptop if they don't need help.
+
+At each break, ask learners to provide feedback on their learning experience since the last break. They should do this by writing one thing that didn't go well on their red sticky note and and one thing that did go well on their white sticky note. Collect these sticky notes, keep them organised so you know which section of the lesson their pertain to, and collate them after the workshop. Matters arising should be raised as Github issues for the relevant lesson.
+  
+____
+# 02-jargon-busting.md
+
+Requirements for this task are:
+
+- boards/pads
+- pens
+
+The purpose of this task is threefold. First, it is an icebreaker. Second, it helps learners find their confidence level and situate their experience and knowledge in the context of fellow learners. Third, it helps manage expectation as the instructor can explain to learners which terms, phrases, or ideas will be covered by this Library Carpentry workshop, which terms, phrases, or ideas are covered by other Library Carpentry lessons, and which terms, phrases, or ideas are covered elsewhere.
+
+When collating feedback on the whiteboard, one strategy is to organise the board from sad (on the left) to happy (on the right), then to locate the terms, phrases, or ideas offered by learners on that spectrum. This performs three functions. First, it opens space to discuss which terms, phrases, or ideas people find or perceive to be easy to understand and what they find or perceive to be hard to understand. Second, it helps identify expertise in the room that learners may turn to for questions during breaks. Third, the instructor can return to the board at the end of the workshop to judge whether learners are more or less confident with some of the terms, phrases, or ideas identified at the outset.
+
+____
+# 03-foundation.md
+
+The material in this episode is intended as a guide. Instructors are recommended to use this section as an opportunity to discuss foundational skills that they think are relevant.
+
+The purpose of the section is to situate a Library Carpentry workshop in a wider landscape of practice and to demonstrate the value of commonsense approaches to software and data.
+
+_____
+# 04-regular-expressions.md 05-quiz.md 06-quiz-answers.md
+
+You may find it useful to use slides to work through episode four (see below for potential slides). Before starting the exercise, encourage learners to work with pen and paper, explain that with regex there are sometimes multiple answers to the same question (that is, some regex is perfect and some does the job given the likely data structures we use) and point them towards places to test their regex: for example regex101 [https://regex101.com/](https://regex101.com/), rexegper [http://regexper.com/](http://regexper.com/), myregexp [http://myregexp.com/]([http://myregexp.com/]), or whichever service you prefer. Also point them towards the quiz (episode five and six) as something they may move onto if they they finish the exercises early or look at after the workshop.
+
+____
+# Potential Slides for Instructor
+
+If you want, use the below as a basis for slides
+
+## Where go to for help
+
+*There are many places!*
+
+### Stickers
+
+### Helpers
+
+### Sticky notes
+
+### github.com/???
+
+## Jargon Busting
+
+### Teams of 5 or 6
+
+### Write terms you want busting on stickies
+
+### Cluster (retaining duplicates)
+
+### Discuss and explain
+
+### Note resolved terms
+
+### Note unresolved terms
+
+### Report back
+
+## Foundations
+
+### The Computer is Stupid
+
+### Why automate
+
+### Keyboard shortcuts are your friend
+
+### Plain text formats are your friend
+
+### Structuring files and folders
+
+## Foundations
+
+### The Computer is Stupid
+
+#### ERROR
+
+## Foundations
+
+### Why automate?
+
+#### Borrow, borrow, borrow
+
+#### There is no correct language
+
+#### Professional development
+
+#### Knowing some code \~ evaluating software
+
+#### Making time to do fun stuff!
+
+#### Andromeda Yelton, "Coding for Librarians: Learning by Example", *Library Technology Reports* 51:3 (April 2015), [doi: 10.5860/ltr.51n3](http://dx.doi.org/10.5860/ltr.51n3)
+
+## Foundations
+
+### Why automate?
+
+Credit: [Andy Kirk](https://twitter.com/visualisingdata/statuses/621957383464599552?tw_i=621957383464599552&tw_e=media&tw_p=archive)
+
+## Foundations
+
+### Keyboard shortcuts are your friend
+
+### Efficiency and control
+
+## Foundations
+
+### Plain text formats are your friend
+
+#### Computers process them better
+
+#### Platform agnostic
+
+#### Display orientated files aren't your friend
+
+#### Markdown
+
+## Foundations
+
+### Structuring files and folders
+
+#### Consistent and predictable data structure
+
+#### Semantic-data hybrid directory names
+
+#### Your own system is fine
+
+#### Links files and directories with names
+
+## You are the most likely person to forget what you once did!
+
+## Regular Expressions
+
+### Match on types of character
+
+### Match patterns
+
+### Capture the parts that match your pattern
+
+## Regular Expressions
+
+### `organi[sz]e`
+
+#### organise (match)
+
+#### organize (match)
+
+#### reorganise (match part so will also find)
+
+#### reorganize (match part so will also find)
+
+## Regular Expressions
+
+### `[ABC]` matches A or B or C.
+
+### `[A-Z]` matches any upper case letter.
+
+### `[A-Za-z0-9]` matches any upper or lower case letter or any digit.
+
+## Regular Expressions
+
+### `.` matches any character at all.
+
+### `\d` matches any single digit.
+
+### `\w` matches any part of word character.
+
+### `\s` matches any space, tab, or newline.
+
+### `\b` matches a word boundary.
+
+### `^` asserts start of the line.
+
+### `$` asserts end of the line
+
+## Regular Expressions
+
+### `^\[Oo\]rgani.e\b`
+
+## Regular Expressions
+
+### `*` matches proceeding character any number of times including zero.
+
+### `+` matches proceeding character any number of times excluding zero.
+
+### `?` matches the proceeding character one or zero times.
+
+### `{VALUE,VALUE}` matches proceeding character a defined number of times.
+
+### `|` simply means or.
+
+## Regular Expressions
+
+### `^[Oo]rgani.e\w\*`
+
+## Regular Expressions
+
+### `[Oo]rgani.e\w+$`
+
+## Regular Expressions
+
+### `^[Oo]rgani.e\w?\b`
+
+## Regular Expressions
+
+### `^[Oo]rgani.e\w?$`
+
+## Regular Expressions
+
+### `\b[Oo]rgani.e\w{2}\b`
+
+## Regular Expressions
+
+### `\b[Oo]rgani.e\b|\b[Oo]rgani.e\w{1}\b`

_extras/guide.md

@@ -0,0 +1,32 @@
+---
+title: "Introduction to Library Carpentry"
+teaching: 15
+exercises: 0
+questions:
+- What do librarians gain from code?
+objectives:
+- Explain why software skills are valuable to librarians
+- Know where to go for help during Library Carpentry
+keypoints:
+- Don't be scared to ask for help
+---
+
+## Overview
+
+### Introduction
+
+Welcome to Library Carpentry! This series of introductory workshops on software skills for librarians started life as an exploratory programme funded by the Software Sustainability Institute and supported by [Software Carpentry](http://software-carpentry.org/) and City University London. Thanks also go to the British Library and the University of Sussex where James Baker, who developed the workshops, worked when planning and delivering the workshops. The aim of Library Carpentry is to create a set of tools the community can manage, support, enrich, and reuse as it sees fit. Periodically during the sessions we will collect anonymous feedback that will go into improving the classes and ensuring that they best fit the evolving needs and requirements of the library and information science community.
+
+The rationale for Library Carpentry is twofold. First, as Andromeda Yelton argues in her excellent [ALA Library Technology Report](http://journals.ala.org/ltr/issue/view/506) 'Coding for Librarians: learning by example', code is a means for librarians to take control of practice and to empower themselves and their organisation to meet user needs in flexible ways. Second, librarians play a crucial role in cultivating world class research. And in most research areas today world class research relies on the use of software. Librarians with software skills are then well placed to continue that cultivation of world class research.
+
+### Where to go for help 
+
+First, identify people on your table who can help: you will all be working from the same material, so someone around you may have got mastered the point you are stuck at. 
+
+Second, there are helpers on hand to help if those around you can't. You should all have access to coloured sticky notes: attaching a red sticky note to your laptop indicates that you need help (it might also alert the attention of someone around you!). So, please use them. 
+
+Third, each part of Library Carpentry may require you to install software or download data. Breaks are a good time to ask for help.
+
+Fourth, we encourage you to finish up or repeat tasks after class time: if you run into any problem, please report them on the relevant Github issues page (see the bottom of each lesson page for a link).
+
+Most Library Carpentry lessons will require you to follow along whilst your instructor demonstrates a software tool or approach. Sometimes you will fall behind. If you do raise your red stick note and as a helper if we can slow the pace. Your issue may be specific to your computer. Computers are stupid, can frustrate, and as you all have different machines it can be tricky to resolve problems. Please be patient, particularly if your issue is local. Stepping outside and taking a gulp of fresh air always helps.

episodes/01-introduction.md

@@ -0,0 +1,26 @@
+---
+title: "Jargon Busting"
+teaching: 15
+exercises: 30
+questions:
+- What terms, phrases, or ideas around code or software development have you come across and perhaps feel you should know better?
+objectives:
+- Explain terms, phrases, and concepts associated with terms, phrases, or ideas around code or software development in libraries
+- Compare knowledge of these terms, phrases, and concepts
+- differentiate between these terms, phrases, and concepts
+keypoints:
+- It helps to share what you know and don't know about software development and data science jargon
+---
+
+## Jargon Busting
+
+### Task
+
+This group task is an opportunity for you to get help understanding terms, phrases, or ideas around code or software development in libraries that you've come across and perhaps feel you should know better.
+
+- Start by getting into pairs.
+- Talk for 3 minutes (your instructor will be timing you!) on any terms, phrases, or ideas around code or software development in libraries that you've come across and perhaps feel you should know better.
+- Get into groups of 4-6. 
+- Make a list of all the problematic terms, phrases, and ideas each pair came up. Retain duplicates. Then - taking common words as a starting point - spend 10 minutes working together to try to explain what the terms, phrases, or ideas means (note: use both each other and the internet as a resource!). Make a note of those your group resolves and those you are still struggling with.
+- Each group then reports back on one issue resolved by their group and one issue not by their group.
+- The instructor will collate these on a whiteboard and facilitate a discussion about what we will cover today and where you can go for help on those things we won't cover.