The randomness that is life...: January 2012

Tuesday, January 31, 2012

Library Day in the Life - Round 8, Day 2

This post is part of Library Day in the Life project. See the Library Day in the Life wiki for info on the project. I also participated previous rounds. You can find all my posts for this project by searching my blog's librarydayinthelife tag. You can also follow my Twitter posts @slmcdanold with the hashtag #libday8.

Tuesday, January 31, 2012

I get to my desk around 8:05am, login to the work network. This is followed by logging in to email, my work calendar, Voyager and Connexion, opening GTalk, opening a browser (Firefox at work, but Chrome at home), and logging in to various web programs (including Evernote), start TweetDeck.

While everything warms up, I compile the paperwork and receipts to submit for reimbursement for ALA Midwinter. Must remember to turn these in TODAY.

Read email. Forward and respond to necessary messages. Catch up on news feeds, work email listservs, and library-related Twitter lists. Scan subjects and then delete mass numbers of listserv messages.

Check calendar to find out what's on today's schedule.

Send out finalized version of one of the three sets of minutes I typed up on Sunday.

Send request to load update file for one of our ongoing ebook collections. We subscribe to regular updates of MARC record files for quite a few of our ebook collections. Mostly these are science publications, or conference proceedings type resources. Each time an updated file is posted, I send a message with instructions to our systems folks that there's a file ready for loading. They run it through a couple of scripts, both the generic one standardizing certain fields I described previously, followed by a script we wrote summarizing any additional edits for that collection specifically. These edits are typically things like additional title access points per request from our collection development librarians. Once the file is loaded, I'm emailed a report that all is complete and if there were any errored records or problems. All in all it's a fairly seamless workflow.

I also make sure I update the two spreadsheets where we track our bulk loads. One is the "master" that tracks all the collections and what the status is for loading MARC record sets. The other is just a summary count of the number of records loaded for each collection broken up by fiscal year for reporting purposes (statistics, y'all).

In cleaning up my inbox this morning, I realized I went right past an email sent out yesterday afternoon about access to Lynda.com. They have great technology training and I'm excited my library has purchased a site license! I did a bit of exploring, and discover they have a 4 hour session on programming fundamentals among many other interesting options. Professional development opportunity FTW!

9:10am - Start work on troubleshooting an error file from a recent record load. 169 records loaded fine, but 16 of them errored out. I have to figure out why and then re-load them by hand. With any batch load, there's always the possibility of records that error out. The issues can be anything from record length (too long and the batch load process hangs and spits the record back), diacritics problems, MARC field validation issues, to complete mysteries. Sometimes the records load fine by hand even though they errored on the back-end batch load. For these 16 records it was three things: a random floating empty subfield b in the 300 field, an indicator error in a name entry, and a random character string ({A0}) inserted at the end of some of the subjects.

9:25am - Chat with my supervisor about a bizarre record display resulting from an e-item created for reserves module purposes. We don't create items for our online stuff, because there's nothing physical to track. For reserves, however, they create a "temp e-item" to put things in a professor's class list. Theoretically the item is removed later and all is well, but we've encountered a few irregularities in displays.

My morning so far can be summed up thusly: ebook record troubleshooting. Good times.

10:30-11am - Bi-weekly check-in meeting with 1 of my 4 staff. This is the other half of my staff meeting for this week. Next week I'll have my meeting with my remaining two staff.

More email and ebook troubleshooting.

11:30am - Meet with a colleague to discuss some issues that have arisen regarding e-items and the reserves module. This is the follow up from the earlier conversation with my supervisor. The reserve module and that workflow isn't part of technical services, but the access services department. So to fix the issues we're seeing of floating holdings records, e-items attached to incorrect holdings (and titles), etc., it requires a bit of inter-departmental cooperation and troubleshooting.

12:15pm - LUNCH. I need to eat a good lunch today before I donate blood so I don't pass out. I speak from personal experience that I need to do this when I donate...no donating before I've had at least 2 good meals that day.

12:35pm - Phone call from a colleague about getting together to write a charge for a subgroup for a committee I'm on. [Note: this is the same colleague that called me yesterday right before I had to leave to be somewhere. He swears he's actually trying to time his phone calls for the 10 minutes before I have to leave my desk. :cP] We have a group that's working on creating (from scratch) an digital repository (beyond our existing scholarly commons repository). We're starting from nothing, so the first step is figuring out what we need to actually store by putting together a census to interview our colleagues to find out what files they are hoarding and need preserved. Simultaneously, we're putting together a subgroup to investigate the various metadata schema available that can accommodate preservation, descriptive, structural, and administrative elements for a wide variety of types of materials that may be included in the repository.

1pm - My appointment to donate for the campus blood drive with the Red Cross. Luckily it's a beautiful day for a walk across campus to the donation site. They were a bit backed up so I had to wait a while for them to get to me. But the best thing? The after donation cookies were the mini-Keebler Fudge Stripes! NOM NOM NOM

2:20pm - After I'm done giving up a pint of my blood and am back at the library, I check email to discover that our system is kicking people out again this afternoon and had to be restarted. Sigh. I also find a request to schedule a meeting. I put together the meeting request and send it out via our networked calendar to various individuals. It's always fun to try to find an hour of time that 6 different people are available (/sarcasm).

3pm - My weekly meeting for the committee I'm on that's working on the user interface design of our new public catalog interface. We have a beta version live now (http://dla.library.upenn.edu/dla/franklin/) but are still fine tuning and working on getting some missing data (and indexes) into our display. In addition to the fine tuning, we're working on the next step of the implementation: the account services pieces (renew, view your checked out items, etc.). We're writing up the functional specs for various pieces including how to log in and log out of the account services, how to renew items, viewing and acting on your items already checked out, placing requests, etc. These functional specs will be used by a team of indexers and programmers to actually make the various pieces work. Writing a functional specs is an iterative process. We talk through the most straight forward process, step by step, identifying where the various pieces of data need to come from (what systems and indexes within each system, and on down the rabbit hole), how things need to be mapped (within the display and from one screen to the next), labels, and then we start introducing the exceptions, and then it blows up into a massive document with references, referrals, and more and suddenly what you thought would be simple and straight forward really is quite complicated. That complicated mess is then reviewed by systems folks (those indexers and programmers), and returned to us with questions, comments, and general feedback. We turn around and make more changes, and the review cycle starts over again. Eventually we get to a functional spec that can be used by the people to actually start the creation/programming process.

It's been an interesting (and positive) experience to be on a user interface team. I'm so used to looking at the data behind the scenes, all that underlying gibberish of MARC and codes and more (that frighteningly makes more sense and is easier to read to me than a cleaned up public display), and I've definitely had to stretch myself to look at things differently. I have to think about how the data is *used* and what is useful for the user needs (find - identify - select - obtain, hello FRBR our old friend). Our primary focus is on what displays and how the user interacts with the system. Aesthetics come in later (and are partially pre-determined). I've learned how to explain our data to non-data people, talking about what is there, what all the codes mean, data variations (both known and possible), how data could potentially be used, and explaining limitations. It's been a fascinating process and has really forced me to understand what I work with on a daily basis (data) in a completely new way and on a new level.

4:15pm - Back from meeting. Ended up spending part of the time chatting with colleague about related but not committee specific work going on. Good to get updates. And time for more email. Seven messages while I was gone for an hour. SEVEN. Yeesh.

Last major task for the day: more statistics, y'all (yes, it's the last day of the month why do you ask?). I copy the statistics for my unit from the website system reports interface. These are generic reports from the system to ensure an accurate count of items added (I have staff that barcode over 1,000 items each month, asking them to count that by hand would be just cruel), newly added records, etc. There's little (if any) context to these generic system reports, so I mesh these generic system reports with the specifics given to me by my staff each month, and then compile them all at the end of the fiscal year for use in a variety of reports on the Libraries, including sending reports to the Association for Research Libraries.

4:50pm - Manually sync local shared calendar system with my personal GoogleCalendar. Meeting Maker doesn't have a push function that plays nice, so I have to save events to an .ics file and then import them into Google. Why? Because I can't see my Meeting Maker calendar without either my desktop client or a web browser. Again, Meeting Maker just doesn't seem to play nice with things I need it to (including my Android cell phone). So I manually sync it whenever meetings are added/changed. Final email check. Clean out email listservs. Check Twitter and blog feeds. Schedule this post.

5:15pm - Shut things/programs down and log out from work network. Shut down (restart) computer. Leave work.

Monday, January 30, 2012

Library Day in the Life - Round 8, Day 1

It's time for another round of Library Day in the Life posts. See the Library Day in the Life wiki for info on the project. I also participated previous rounds. You can find all my posts for this project by searching my blog's librarydayinthelife tag. You can also follow my Twitter posts @slmcdanold with the hashtag #libday8.

Obligatory background: I'm a cataloger at a rather large academic library. Specifically a cataloger of electronic resources (anything online, in any format), and continuing resources (serials, etc.). I participate in the PCC program, doing NACO and both CONSER and BIBCO work depending on what I'm dealing with at the time. I also participate in committee work for the PCC, ALA ALCTS, and NASIG.

I am head of a unit that handles the cataloging, maintenance and inventory control of continuing resources (both serials and integrating resources) and electronic resources (online resources) for all units of the Libraries by updating and maintaining bibliographic, holdings and item records. I have four para-professional (or support) staff in my unit. Two that work an early shift, and two that work a later shift. In an attempt to cover the most ground, my schedule says I work from 8am to 4pm, although I usually don't actually get out of the office until 4:30 or 5pm.

The majority of time spent on the cataloging for continuing resources and many online resources is maintenance work and updating of the bibliographic records to reflect current information. Changes can be anything from the frequency, to a change in publisher, to a title variation or title change. Cataloging these types of materials is like trying to hit a moving target or nailing jello to the wall. There's also the ongoing inventory maintenance on our holdings records to deal with keeping our holdings current, including withdrawn/lost/missing volumes, general edits to fix accuracy issues, etc. I also spend a large amount of time managing the bulk loads of MARC records for title-level access to online resources such as streaming media and ebooks (including batch editing the records prior to loading using tools like MarcEdit) and managing the cataloging of individual ebooks and ebooks series that aren't available in sets but require regular maintenance and updating.

Monday, January 30, 2012

I was a bit late this morning courtesy of my cat and a hairball incident. It upset my routine enough that I left my travel mug of coffee at home on the counter. I am not so much a morning person, so my routine is fine tuned to make sure I get out of the apartment in once piece, wearing shoes not slippers, and without locking myself out. I'm lucky the only thing I forgot was my coffee. So I made a quick stop before heading into the library for some coffee. Coffee is a non-negotiable morning requirement.

Once I acquired my precious brew and got to my desk, I login to the work network. This is followed by logging in to email, my work calendar, Voyager and Connexion, opening GChat, opening a browser (Firefox at work, but Chrome at home), and logging in to various web programs (including Evernote), start TweetDeck.

Read email. Forward and respond to necessary messages. Catch up on news feeds, work email listservs, and library-related Twitter lists. Scan subjects and then delete mass numbers of listserv messages.

Check calendar to find out what's on today's schedule.

10-10:30am: Bi-weekly check-in meeting with 1 of my 4 staff. The other staff person I meet with this week (2 people each week) is out today so we'll meet Tuesday instead. And next week I'll have my meeting with my remaining two staff. This is something I started back in July. These bi-weekly meetings have greatly improved and increased communication with my staff by having regular face-to-face conversations. They also present more opportunities to get solutions for things directly from them. I don't have to solve the problems, I just have to support the solution and the process. The feedback from my staff on our bi-weekly meetings has been overwhelmingly positive. It helps us all stay on top of things and address issues before they get out of hand and become critical. It's also helped our unit come together and work better together. Communication has improved not just between myself and individual staff, but between staff members. Our unit has really "jelled" and is working well as a single functional unit rather than individuals thrown together. It's incredibly encouraging and satisfying to see that happen (it's been a long road and a lot of hard work from all of us to get here).

And yet I'm constantly reminded that management is a work in progress, ever evolving. I try different things, some work, some don't. I'm constantly having to learn and improve as a manager. I've attended seminars and workshops, read articles, and received honest feedback from colleagues and my own supervisor, all of which have been valuable in various ways to help me be a better manager. It's not easy. Anyone that tells you otherwise is a liar.

11am: We have several new professionals. This morning was an orientation meeting between the new head of a unit in a different department and my department. Essentially we use the time to break down the relationships between units and departments and review workflows.

Noon: Code4Lib Conference online meeting for pre-conference planning. It has become clear that I will not be able to attend Code4Lib after all. The pre-conference proposal was last minute so I hadn't planned to attend and it's just not possible with everything going on right now. I tried to find a way to make it work (both financially and work related), but alas, no dice. Sometimes having to be responsible can really suck. But that doesn't stop me from finishing up the pre-conference planning. I'll still do my part and put together slides for what would have been my portion of the brief presentation. I'm seriously disappointed, but now even more determined to plan ahead to attend next year. We are exploring the possibility that I may be able to participate via Skype, and I really hope that happens. Either that or someone better figure out cloning quickly...I volunteer as a test subject!

We've been using Adobe Connect for our online meetings. It's quite powerful, and I've used it for other committee work where we need to bring people together from all over the country and for presentations/trainings since you can upload files and share your desktop. There's nothing to install beyond the basic Adobe software suite (and who doesn't have the reader these days) which has the underpinnings to run the meeting space. The connection is via a URL. No registration or passcodes needed. Which is very user friendly, especially when you are trying to throw a meeting together at the last minute. All participants need is a headset with microphone for conversation (although there is a chat box if microphone isn't an option), and an internet connection and browser. The only issue we've encountered is that it's not as reliable when someone connects via wireless, but is perfectly stable when connecting via Ethernet (a "wired" connection).

As soon as we were done with the Code4Lib meeting, I switched over to the (free!) ALA Midwinter Midwinter Tech Wrapup 2012 which started at 1pm. A panel presents their "observations and analysis of the top technology trends from the conference, and what they see as the implications for libraries". It's an interesting snapshot of all the new stuff that gets presented at ALA.

Mid-way through the Tech Wrapup presentation, I realize I haven't eaten lunch yet. My stomach reminded me with an annoyed growl/grumble. Oops. Fortunately the Wrapup is being recorded, and they will be sending out the recording and links to the slides in the next few days.

1:30pm - LUNCH.

2:00pm - A colleague sends me many helpful emails to address my need to swap Date1 and Date2 in a large number of files of MARC records. Holly Tomren is my hero today. Sometimes the best thing is to share your challenges openly and freely (and without shame). Chances are someone else has encountered it too and can either provide a solution or some helpful guidance or at least some sympathy. :)

As much as I would like to play with what she sent immediately, I have a small list of things in our catalog to clean up. Since our system has decided to be cooperative and stable today (note: our server has been cranky and the reasons for its' crankiness continue to elude our local systems folks and the systems folks at the company that owns the ILS software), the clean up edits take priority.

2:30pm - And just as I find all my notes and emails and bring up the first record, the system crashes. Dammit.

2:40pm - I try to log in to the system again and success! Edits ahoy!

2:57pm - And not so fast. System crash. I think I saved the record I was editing in time. ::crosses fingers::

3:04pm - System restarted. And we're back up. Yea gods...whiplash!

3:30pm - Editing of some of the meeting notes I typed up yesterday. It's tricky, as I'm reporting on what was said by someone else on a committee I'm not on. Needless to say the individual has had quite a few suggestions for edits to my notes.

3:45pm - Respond to an email from a colleague about loading a set of records for digitized historical newspapers into our catalog. Add the requested collection to the master spreadsheet so it can be placed in the queue by our collection development team. They evaluate priorities and determine the order of the sets that have been requested or purchased for loading into the catalog. We have a bit of a backlog, but we're slowly catching up. Some of the sets we load are quite large (the Congressional Serial Set and the Parliamentary Papers are two good examples of extremely large sets consisting of many files with upwards of 50,000 records per file) so they take some time. We can only load so many records at a time, due to system limitations and post-load re-indexing needs (re-indexing can be a demanding and potentially resource eating process for a server).

4:10pm - I had the privilege of serving on the ALCTS Continuing Resources Section Ulrich's Serials Librarianship Award jury committee this year. One of our final tasks is reviewing the press releases and announcements that will be going out celebrating and honoring the recipient of the award. These are the kinds of documents I love reviewing and editing. A feel-good way to end the day.

While editing, I also get pinged via Google Talk by a colleague from another institution with a serials cataloging question. There are some complicated changes to an institution name that require edits in multiple places on top of a migration from print format to online. Serials can be complicated and tricky when they are feeling onerous. But I do love that I live in the future and such things can be discussed via online chat. :)

4:30pm - Final email check. Clean out email listservs. Check Twitter and blog feeds. Schedule this post.

4:35pm - Phone call from colleague asking me about next steps for a workflow revision.

4:40pm - A staff person asks me a question about some strange notes in a holdings record. We figure out the best way to edit the notes so they make sense.

4:50pm - Rush to shut things/programs down and log out from work network. Shut down (restart) computer. Leave work. I have somewhere to be at 5:30pm and must get out of here!

[Edited to finish filling in the last 30 minutes of my day...didn't have a chance before I had to leave and it was already scheduled to publish! Oops.]

Sunday, January 29, 2012

Library Day in the Life - Round 8, Day 0

Saturday, January 28, 2012

Cat and mouse

My cat caught a mouse the other morning. She brought it to me, all proud of her new real! live! toy, wanting to show off her hunting skills. She was making her chirping meow when she's feeling playful and has "caught" a toy or caught a bug.

Naturally, I didn't realize it was a LIVE mouse. I've been in this apartment for over 2 years now with no evidence of mice or mouse sightings. So I thought it was a toy. I reached down to take it from her, thinking Capri wanted me to toss it (we play "catch").

And then it twitched in my hand.

::SHUDDER::

It was ALIVE. This was no toy mouse. It was a real live fuzzy mouse she had caught. ::GASP::

Needless to say I dropped it pretty quickly.

The cat resumed her play while I danced around shuddering and chanting "ick ick ick!!" at the top of my lungs and tried not to hyperventilate from the shock.

Once I got over it, I retrieved a few tissues and confiscated the poor creature once again. It was clearly mortally wounded, so I put it out of it's misery (kinder than letting it suffer), and deposited it in the trash outdoors. And then washed my hands in the hottest water I could stand at least a half a dozen times.

The cat watched me do this while meow-screaming at me, baffled and annoyed that I had taken away her toy. I soothed her with some cat treats and lots of praise for her skills. This was our first live mouse episode in this apartment and the first time she's caught something other than a bug, and I truly hope it's our first and ONLY mouse. The bug catching? I encourage it. Praise her for it. It keeps the flies under control in the summer when the balcony door is open. But I can live without another live mouse incident.

Capri now spends at least a few hours each day staring intently under the stove. I'm guessing she's standing guard against further fuzzy intruders.

Good kitty. That's my good little huntress. Keep the mouses away.

::SHUDDER::

Talking about Code Year

It's really weird to watch yourself talk. And listen to yourself. Oh boy.

Anyway, here's a link to Andromeda Yelton and I talking about the Code Year phenomenon and what we've got going on:

http://americanlibrariesmagazine.org/ala-members-blog/beginning-lita-code-year-interest-group

[Note: I'm on the left, wearing the Stewie from Family Guy "OBEY ME!" lanyard.]

Watch. And then come join us!! Thanks to Tina Coleman for posting her video and sharing it. :)

We are working on making the ALA Interest Group a joint LITA/ALCTS venture. There are far too many catalogers involved fro ALCTS to not participate! Yay for dialogue between catalogers and coders!

Catcode twitter list
Catcode wiki
Code Year on ALA Connect

Wednesday, January 18, 2012

ALA Midwinter 2012 Dallas

Over the weekend I'm off to Dallas for the ALA Midwinter Meeting 2012. As usual, there's a lot going on and I expect I'll be quite busy. I'm also looking forward to catching up with and seeing my colleagues from all over the country. :)

For anyone wanting/needing to track me down at ALA, here's my ALA Midwinter 2012 Dallas schedule:

I'll be spending a lot of time in the Omni Dallas Hotel and the Convention Center this Midwinter. Yes, my schedule is full. It always is. Yes, there are conflicts. They're unavoidable. If anyone has figured out how to clone themselves, please share. In the time slots with conflicts, I will be at one of the listed sessions...I just don't know which one. You can assume I'll be at the PCC/CONSER/BIBCO stuff, anything under the type committee meeting, or anything marked private because I most likely have to be.

Drop me an email or contact me via GoogleChat or Twitter if you want to meet up. :)

Tuesday, January 10, 2012

Code Year, the first week

Again, I am overwhelmed by the interest in the Code Year project from fellow catalogers. Kudos to everyone for taking on the challenge of learning to code. It's time to dive in and get dirty!

How is the first week of Code Year 2012 for everyone (Code Year Course list/Calendar)? Did you complete the course yet or are you working on it bit by bit (lesson by lesson) all week? Who did the Supplemental lesson?

Did you feel like tearing your hair out? Or was it fun? Or was it both?

Who got started early? I admittedly signed up for Codecademy this weekend and plowed through the first 4 lessons of Getting Started with Programming course. I'll be working on the other half of the course lessons throughout the week. I know it will help to cement it in my brain if I spread it out and have to keep going back and reviewing. I also have a sneaking suspicion I might have to create a command cheat sheet until they stick in my brain.

A trouble spot for me I've already identified: TYPOS. Lordy. Talk about error messages. I had to re-do a few of the lessons just because of typos. I know I have some minor dyslexia (spellchecker was invented for people like me, I swear it's true), and I've learned I need to be extra careful when coding or writing in mark-up language(s) (HTML, MARC, etc.) where capitalization, spelling, and punctuation are critical. That was reinforced quite strongly by a couple of the coding lessons this week (damn "ReferenceError:" returns). Clearly I have to take my time, work carefully, and can't do this when distracted or frequently interrupted so I don't lose my focus. At least not yet. Maybe when I'm more comfortable/experienced I'll be able to code successfully in my office. But for right now I need a quiet environment (no distractions) where I'm not interrupted by questions/staff/colleagues/etc.

What are your trouble spots? Does noise distract you or do you like music while you work? Does a busy environment help or hinder?

Oh, btw, I've learned that M&Ms help the coding process. ;)

Resources:

CatCode Wiki (we have a Resources page now!) - PLEASE just ask to be added. The request gateway is there to keep out the spammers. If you're not a bot, you'll be approved. I have over 110 people listed on the Code Year Catalogers post and less than 80 users on the wiki at the time I wrote this post. If you haven't signed up, why?
CatCode Twitter list - over 90 members! whoa
Search #catcode hashtag on Twitter
Code Year ALA Connect group
Lifehacker's Learn to Code
O'Reilly books and videos (try the Head First series of books, Head First Programming)
CatCode posts on this blog

Thursday, January 5, 2012

CatCode is born!

The number of people interested in the Code Year 2012 catcode project has grown by leaps and bounds the past few days! I'm slightly overwhelmed. I'm also stupidly excited and keep doing a little happy dance in my chair at work with each new person that adds themselves as a participant. I can hardly keep up with all the Twitter messages and post comments! To see the growing list, check out my previous post. I've been actively updating the post to add names as I receive them.

To help facilitate participation going forward, I've created a space in PBWiki for all of us to use: CatCode is born! The CodeYear project may have spawned the space, but my hope is that it becomes a more general space for dialogue and learning for catalogers and coders beyond the CodeYear project. A girl can dream, right?

Please go visit the wiki and sign up as a user (it's free!). Once your access has been granted (please be patient with me on verifying you! I'm trying to prevent spammers), please update your information on the Participants page. If you submitted your name before, I've pre-populated the participant's table with some information...please find your info and update it!

We (my partners in crime and I) are still working on setting up a discussion/q&a space. We'll post the information far and wide as soon as it's ready.

And don't forget to follow the Twitter list too! Catcode and send a message on Twitter to me to add yourself to the list. We're also using #catcode as the hashtag.

Tuesday, January 3, 2012

CodeYear Catalogers

CodeAcademy is offering an excellent opportunity for anyone interested in getting started with coding: Code Year. Each week they'll be emailing out to anyone that signs up an interactive lesson on coding. Code Academy offers some fantastic interactive courses, so you learn in a supportive environment.

Naturally this has piqued the interest of a number of catalogers that have been interested in learning to code or want to brush up or learn new code languages, myself included. Catalogers work with massive amounts of curated bibliographic data, and being able to manipulate it in new and different ways and in ever increasing amounts is key as we move forward into the bibliographic future and the world of linked data and the semantic web.

So I started compiling names. This is my curated list of catalogers on Twitter participating in CodeYear so far:

@slmcdanold (me)
@lauramac95
@jaleh_f
@erinaleach
@HLPitts
@yo_bj (no longer has cataloger in her title but it's in her soul)
@jen_young
@cjclib
@cursedstorm
@enimsakont
@debdegeorge
@evil_jen
@chrpr (not a cataloger...but we like him anyway)
@amyrpennington
@skiddie2
@johnmac38
@wabashcanonball
@EstherArens
@lagina
@sidesmirk
@libdespot
@shelitwits
@AnneWelsh
@yanajenn
@orangeaurochs
@maryacat
@campbell_b
@strong_stuff
@dchud
@lrobare
@ahitchens
@dorevabelfiore
@kate80
@jenniferswright
@SuzanGriffiths
@lynncorrigan
@alyssa_briggs
@springyrice
@caschwartz (no longer has cataloger in her title but it's in her soul)
@HtebLuap
@prburley
@frleibo
@cololibrarygirl
@srodr2
@htomren
@shomj
@rachelmcw
@schammond
@StephenTEarly
@cindywho23
@Headstrongways
@ynde
@ces43
@infod1va
@teagueamania
@israelcsus
@meta_cat
@diriwh
@bibliosaurustxt
@pikesar
@BarbaraBrownell
@tminchew
@keribrary
@lrts
@barnlib
@adriennerad
@spaghettiwall
@zemkat
@AhavaCohen
@deans
@catlib56
@bookmender11
@diseming
@jnavia
@violibrarian
@egelliott
@koklbr
@plummerkaren
@nossis
@PhillyKatia
@jmyntti
@mrlindner
@metalib
@AllisonJaiODell
@strettoc
@bohyunkim
@wendyrlibrarian
@maggienunley
@alison_felstead
@RachaelCohen1
@bibliographics

Add yourself to the list by posting your Twitter handle as a comment. I'll update as needed. :) You can also send me a message via Twitter (@slmcdanold) and add yourself that way. Or use the newly created hashtag #catcode (thanks @chrpr for the suggestion)!

There is now an actual LIST on Twitter: catcode. Subscribe!

If you're not on Twitter, let me know where we should email you when we get some sort of wiki/webpage/IRC channel going so we can all ~~suffer~~ learn together and help each other.

Non-Twitter list:

Cecilia G. (gener002@umn.edu)
Joe O. (Joe_Orth@ca6.uscourts.gov)
Martin J. (martin.jenkins@wright.edu)
Nancy H. (nancy.hunter@colostate.edu)
Ann H. (alh5456@sbcglobal.net) [on Twitter as @alh5456 but forgets to use it. ;) ]
chrisallenstanton@gmail.com
Susie R. (sridgeway@me.com)
Deborah Tomaras (dtomaras@southportland.org)
Melodie Frances (mfrances@gtu.edu)
Linda Frankel (lf92355@gmail.com)
Leigh Billings (rednaal@umich.edu)
Bill Anderson (William.Anderson@ct.gov)
Catherine Kellett (catherine.kellett@yale.edu)
Christine DeZelar-Tiedman (dezel002@umn.edu)
Cindy (cbarrilleaux@slol.lib.la.us)
Ashley Dietrick (akdietrick@gmail.com)
Joan Milligan (jmilligan1@udayton.edu)
Chris Blackman (cblackma@williams.edu)
Kristi Bergland (krisser@gmail.com)
Euem C. Osmera (eosmera@unmc.edu)
flinchba@umbc.edu
David A. Johnson (djohnson@highline.edu)
deg7@nyu.edu
Pauline (myrtlebell@centurylink.net)
Mike Mitchell (deeptexas10@gmail.com)
R.A. Stewart (rstewart@indiantrailslibrary.org)
Melissa VanTine (melissa.vantine@yale.edu)
Tina (spielmat@uwm.edu)
Carolyn (chufford@gmail.com)
Julie (julie.howe@kctcs.edu)
Peter Rolla (peter_rolla@hms.harvard.edu)
lloydgerard@hotmail.com
kvalenzuela@csustan.edu

The randomness that is life...

Tuesday, January 31, 2012

Library Day in the Life - Round 8, Day 2

Monday, January 30, 2012

Library Day in the Life - Round 8, Day 1

Sunday, January 29, 2012

Library Day in the Life - Round 8, Day 0

Saturday, January 28, 2012

Cat and mouse

Talking about Code Year

Wednesday, January 18, 2012

ALA Midwinter 2012 Dallas

Tuesday, January 10, 2012

Code Year, the first week

Thursday, January 5, 2012

CatCode is born!

Tuesday, January 3, 2012

CodeYear Catalogers

About Me

About this blog

Use License

Twitter Updates

Training Widget

Photos

Links

LibraryThing

Blog Archive

Blog Labels

Tuesday, January 31, 2012

Monday, January 30, 2012

Sunday, January 29, 2012

Saturday, January 28, 2012

Wednesday, January 18, 2012

Tuesday, January 10, 2012

Thursday, January 5, 2012

Tuesday, January 3, 2012

About Me

About this blog

Use License

Twitter Updates

Training Widget

Photos

Links

LibraryThing

Blog Archive

Blog Labels

Subscribe To