THATcamp Libraries

THATcamp Libraries
Saturday, February 23, 2013 (All day)

 

THATcamp Libraries

February 23, 2013

Simmons College in Boston, MA

All text from: http://libraries2013.thatcamp.org/

New technology is coming on the scene all the time. Digital Humanities, MOOCs, social media, and more are transforming the content and services libraries, and their staff, provide to their constituents. Even ‘old’ technologies, such as databases and metadata are evolving in the face of these changes.

THATCamp Libraries will provide a venue to further explore on-going conversations about strategic partnerships and services libraries are uniquely situated to offer to the humanities, moving away from a support model to a truly collaborative framework in which librarians foster and contribute as experts and scholars in their own right.

THATCamp Libraries will take place on Saturday, February 23rd at Simmons College in Boston, MA. Visit the Register page to sign up.

Questions? Concerns? E-mail the session organizers at: thatcamplibraries@googlegroups.com

THATCamp Libraries Organizers:

  • Beatrice Pulliam, Library Commons Librarian for Technology and Access, Providence College
  • Rebecca Darling, Assistant Director, Instructional Technology, Wellesley College
  • Hailie Posey, Coordinator of Digital Publishing Services, Providence College

Follow THATCamp Libraries on Twitter: @THATCampLib

 

What is a THATCamp?

Here are the key characteristics of a THATCamp:

  • It’s collaborative: there are no spectators at a THATCamp. Everyone participates, including in the task of setting an agenda or program.
  • It’s informal: there are no lengthy proposals, papers, presentations, or product demos. The emphasis is on productive, collegial work or free-form discussion.
  • It’s spontaneous and timely, with the agenda / schedule / program being mostly or entirely created by all the participants during the first session of the first day, rather than weeks or months beforehand by a program committee.
  • It’s productive: participants are encouraged to use session time to create, build, write, hack, and solve problems.
  • It’s lightweight and inexpensive to organize: we generally estimate that a THATCamp takes about 100 hours over the course of six months and about $3000 to organize.
  • It’s not-for-profit and either free or inexpensive (under $30) to attend: it’s funded by small sponsorships, donations of space and labor, and by passing the hat around to the participants.
  • It’s small, having anywhere from 25 or 50 to about 150 participants: most THATCamps aim for about 75 participants.
  • It’s non-hierarchical and non-disciplinary and inter-professional: THATCamps welcome graduate students, scholars, librarians, archivists, museum professionals, developers and programmers, K-12 teachers, administrators, managers, and funders as well as people from the non-profit sector, people from the for-profit sector, and interested amateurs. The topic “the humanities and technology” contains multitudes.
  • It’s open and online: participants make sure to share their notes, documents, pictures, and other materials from THATCamp discussions before and after the event on the web and via social media.
  • It’s fun, intellectually engaging, and a little exhausting.

What is an “unconference”?

The shortest answer is this: an unconference is a highly informal conference. Two differences are particularly notable. First, at an unconference, the program isn’t set beforehand: it’s created on the first day with the help of all the participants rather than beforehand by a program committee. Second, at an unconference, there are no presentations — all participants in an unconference are expected to talk and work with fellow participants in every session. An unconference is to a conference what a seminar is to a lecture; going to an unconference is like being a member of an improv troupe where going to a conference is (mostly) like being a member of an audience. Unconferences are also free or cheap and open to all. For more information, see Wikipedia’s entry on the unconference.

Who should attend?

Anyone with energy and an interest in the humanities and/or technology.

What are “the humanities”?

Good question. Turns out there’s a legal definition! As the National Endowment for the Humanities puts it: “According to the 1965 National Foundation on the Arts and the Humanities Act, ‘The term “humanities” includes, but is not limited to, the study of the following: language, both modern and classical; linguistics; literature; history; jurisprudence; philosophy; archaeology; comparative religion; ethics; the history, criticism and theory of the arts; those aspects of social sciences which have humanistic content and employ humanistic methods; and the study and application of the humanities to the human environment with particular attention to reflecting our diverse heritage, traditions, and history and to the relevance of the humanities to the current conditions of national life.’ ”

What is “technology”?

We suggest you read this brilliant article by Professor Leo Marx, American cultural historian at the Massachusetts Institute of Technology: “Technology: The Emergence of a Hazardous Concept.” (Side note: those who love technology should be those who are most aware of its hazards.)

What should I propose?

Sessions at THATCamp will range from software demos to training sessions to discussions of research findings to half-baked rants (but please no full-blown papers; we’re not here to read or be read to). See the list of sample sessions at thatcamp.org/proposals/ for ideas, or come up with a creative idea of your own for a session genre or topic. You should come to THATCamp with something in mind, and on the first day find a time, a place, and people to share it with. Once you’re at THATCamp, you may also find people with similar topics and interests to team up with for a joint session.

Is a THATCamp only for scholars / grad students / librarians / archivists / programmers / instructional technologists? Can scholars / grad students / librarians / archivists / programmers / instructional technologists apply?

No to the first, yes to the second. THATCamp aims at the broadest diversity of backgrounds and skills possible.

I’m poor. How can I get funds to travel to THATCamp?

Some academic participants have mentioned that their universities will not fund any travel unless for the purpose of presenting a paper, and since there are no presentations and no papers at THATCamp, they cannot come to THATCamp. We have a few suggestions. First, you might frame your trip to THATCamp as “professional development,” if such a category exists at your organization — coming to THATCamp is definitely much more of a learning experience than a showing-off experience. Second, you might wait for a THATCamp to pop up nearby so that travel will be cheap: you can sign up for THATCamp News to be notified of new THATCamps. Third, some THATCamps offer fellowships — be sure to check individual THATCamp sites to see if there are fellowship funds available. Fourth, you might consider simply organizing your own THATCamp — that way, the world will have to come to you.

Write the THATCamp Coordinator at info@thatcamp.org with further general questions about THATCamp.

 

120

No comments
https://www.hastac.org/opportunities/thatcamp-libraries
www.hastac.org
crawl=CC-MAIN-2020-45
65500
application/http; msgtype=response
sha1:AI7JKWP7WIZWM3DLT77RDPWIK2UYGB54
<urn:uuid:61e330ef-1ed4-452e-8e2d-60b503463210>
2020-10-20T23:12:43Z
23.185.0.2
text/html
sha1:HDVN47FNH45VM7FGEDO7QEANXDYGTT6G
<urn:uuid:62a4d307-ef27-4372-828b-05fd21bffffc>
https://www.hastac.org/opportunities/thatcamp-libraries
response
<urn:uuid:33efa3e6-bccc-4dc7-8b81-d55ab9a2b23d>
isPartOf: CC-MAIN-2020-45
publisher: Common Crawl
description: Wide crawl of the web for October 2020
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-253.ec2.internal
software: Apache Nutch 1.17 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.2-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/