Warning message

ALA Connect User logins are disabled for a temporary "gray-out" period, to prevent new posts while we upgrade into the New Connect. This gray-out period will begin on March 26th, and the new site will be launched on April 25th.

Users can use Search to view public content. Logins will be reinstated and users can create new posts, upload files, etc. post launch.

Thank you for your patience in cooperation. Check out training resources and schedule at:

Or contact Julianna Kloeppel for training or Pam Akins with questions/concerns.
Go to:
Online Doc
Meeting Request
Andromeda Yelton's picture

Plans for Annual

A big happy welcome to the 33 of you who have joined so far!


So: we've reserved meeting space at 1:30-3:30 on Saturday at Annual.  What do you think we should do with it?

Marliese Thomas's picture

My first thoughts for topics are:

  • Check in with each other on Code Year progress? Roadblocks? How can we support each other?
  • What has been created/incorporated/planned using new CY skills? Specifically for libraries?
  • Has your participating in CY helped in your library (cross-training/in-sourcing/understanding another person's job more) so that productivity can improve in another way, or will it?
  • Are we 'preaching to the choir'? How can we encourage non-techy people (well, even less techy than I am) to reach beyond their boundaries for this kind of activity in the future? 

We probably wouldn't have time to get into all of these, but thoughts? Priorities? Discuss amongst yourselves.


Coral Sheldon-Hess (non-member)'s picture

I would very much like to talk about what we've accomplished, so far, and what we're getting out of the program. 

In addition to that, though, perhaps we should meet and do some serious talking about what we're going to do NEXT year?

For instance:

  • Are we going to mentor people doing Code Year 2013? (Is Code Year every year?)
  • Are we going to find some other awesome continuing education activity and all do THAT together?
  • Are our female IG members going to work with The Ada Project? And then where does that leave our male members? (Actually, I think men can be involved in TAP, but I'm not sure to what level.)
  • Are we going to all band together and each commit to making at least one patch to one open source project during the year 2013? 

What does this IG look like, past the end of 2012? I'd love to talk about that.



Marliese Thomas's picture

I second that emotion, as the song goes! Let's definitely talk about keeping the momentum going, especially as some of us (cough, me, cough) might not get through all the code year lessons by the end of 2012. And I doubt they remove the lessons now that they're existing and online. 

Jodie Gambill's picture

What does this IG look like, past the end of 2012? I'd love to talk about that.

Yes. This. And everything else Marliese and Coral said. :)

Erica Findley's picture

I second Marlise on sharing what we have done with our new Code A Year skills in our libraries. It's too early for me to tell how I might be able to apply this locally.



Erica Findley, MLS

Carli Spina's picture

I would also be very interested to hear whether any libraries are working with patrons who are participating in Code Year (i.e., providing space for a meetup group, organizing sessions for participants, providing supplemental classes, etc.) and, if so, whether that has been successful.

Andromeda Yelton's picture

So looking at this, I see three basic possibilities emerging:


1) Talk about what people have been doing with code.  This could be a lot of things: ways you've been applying code in your work life, ways your library has been working with CodeYear, things you've learned while learning code, etc.  Maybe we could get a range of perspectives by getting a half-dozen people or so to do some Ignite-style talks?


2) Brainstorming session on what we want the group to be doing after Annual.


3) Hackathon/time to work on lessons, catch up, mentor, etc.


I think in a 2-hour slot we have time for at most 2 of these, and my preference would be the first 2.  But I've also been thinking it would be really fun to have some Google Hangouts or similar before Annual to do some focused conversations and keep the momentum going.  We could totally use those to check in/work on CodeYear lessons.  Could also use them to talk about how we're using code in our lines of work (I could demo some of my jquery, e.g.), tools we've found for learning, et cetera.



LITA Board of Directors, 2013-2019; President-Elect, 2017-2018

Eric Phetteplace's picture

I really like idea #1 of showing what people can do with the code they've learned. It's hard to tell where Code Year is going and how/if they'll eventually hook JavaScript up to an output other than console.log but I would really like to see where people take it. I've already made some little snippets of JS code that do things in the browser but by Annual presumably we'll all have a much firmer base upon which to experiment.

#3 also sounds nice but I don't know, an unstructured hackfest might not go anywhere. Perhaps if we could agree upon some projects beforehand that would help?

-Eric Phetteplace

Systems Librarian

California College of the Arts

Aaron Dobbs's picture

Several years ago (2007?!) at EMA (the Endeavor Mid-Atlantic Users Group meeting) we had an almost completely unstrucured hackfest.

I came in with the desire to hack a way to be able to one-click add item records to del.icio.us - nobody else had any burning desires about this, so we hacked a way around teh systems constraints and made it happen. See: "Tag Item (Beta)" in this catalog record.

Long story short, if someone has a burning desire to buiild something specific a hackfest is a great collaborative effort.


"Always remember everyone is working to make the organization better in their own way."
-Eli Mina, ALA Parliamentarian