Chicago Librarian

Peter Merholz serves up a welcomed reality check amid all the hoopla of 'mobile first':

My concern with "mobile first" is that we'll mistake that for "mobile only" (the way that the Web was seen as the end-all be-all for quite a while) and not appreciate just what our customers are actually doing, nor prepare ourselves for what's next.

I'll be the first to admit, proudly in fact, that 'responsive web design' was clearly the right way to go. We had multiple devices and we needed some coherent way of accommodating them.

But I've never been able to comprehend why this required (at least among some) a second -- and to my mind completely unrelated -- step, namely that of having to start your design at the level of the least capable device (i.e. mobile) especially since 'least capable' doesn't necessarily mean 'least complicated'. You might as well have told people back in the old days, 'design for telnet' -- 'telnet first'!

Yeah, I went to the Ribfest and had a great time. Beyond the event itself what impressed me the most was the website. Great professional job! (And responsive to boot.)

Taking the Blue line home from O'Hare I couldn't resist getting off at Western Ave. which put me within a couple of blocks of Honey 1 BBQ. It was a Sunday and they weren't going to be open for long but I had just enough time to order (and partially devour) an extra-large order of rib tips. Mama mia, Chicago has its advantages!

Okay, they say this happens every time but maybe 19 people signed up for the event -- and 67 showed up. I'd say it was 'standing room only' except that maybe a dozen people were sitting on the carpet in the central aisle. People were standing alongside all the walls and needless to say there wasn't a free chair in the place.

Even with that number of people, we went from person to person, each telling us his or her name and institution. We had a good mix of academic, public and special libraries. This variety showed up repeatedly in the quality of the discussion.

Nina started things off with a presentation of the new Arapahoe Library District website. We next moved to an open discussion on everything from Drupal's compatibility with repository software such as Islandora to the possibilities of Drupal replacing the ILS entirely. One theme that manifested itself through the course of the discussion was the strong desire to collaborate more on projects. Possible vehicles for this include the Drupal Library Group, the Drupal4Lib ListServ and of course, the Drupal4Lib LITA IG.

Clearly we could have gone another hour but 60 minutes was all we had. People were encouraged to continue the discussions throughout the day and also, at our Drupal4Lib IG Meeting at ALA Chicago on June 30 (10:30a-11:30a).

I know a couple of library people are going to DrupalCon in Portland in a week or two.

Looks to me like a great opportunity to get together and talk shop. So how about if we organize a Drupal4Lib BoF -- maybe on the Wednesday (5/22) sometime mid-day or in the early afternoon?

Topics could be open or suggested ahead of time. People could present projects they're working on, ask whatever questions they want. It'd be a great time!

If you've got a suggestion, either email me back or leave a comment here.

Is this a good general time to meet? Do you have a topic you'd want to suggest?

Any feedback would be appreciated! And hope to see you in Portland!

(UPDATE1): I set up a poll at the Drupal Library Group asking people what timeslot they prefer:

Poll: Drupal4Lib BoF - 10:45a-12p or 3:15p-4:30p?
http://groups.drupal.org/node/297483

(UPDATE2): Okay, '10:45a-12p' wins. Here's a link to the event on the Drupal Library Group:

Library BoF at DrupalCon Portland (5/22, 10:45a-12p)
http://groups.drupal.org/node/297878

I swear if I get another one of these as a design proposal for the main page of a website, I'm going to sue Microsoft for crimes against usability. (P.S. Why Microsoft? Hint...)

Mom at the Reference Desk dealing with an unruly patron.

Slides from the presentation I gave today. A couple people came up afterwards and said it had inspired them to go off and try it themselves.

Matt Enis from Library Journal writes about the 'Fail4Lib pre-conference workshop' at this year's Code4Lib Conference where people talked about failed or problematic projects and the lessons they learned.

As I wrote in comments to the piece, I find the greatest cause of failed projects to be those based on received wisdom. Let’s call it, the ‘Wrong Bandwagon Effect’. Some mis-identified trend is taken up and you can’t argue against it because “everyone knows” (i.e. received wisdom) that it's the way of the future. Everyone knows! Only "everyone" never seems to include the end-user. But that doesn't matter since before you know it, yet another mis-identified trend pops up and nothing says ‘cutting edge’ like jumping from one of these trends to the other. (Classic example.)

This isn’t an argument against innovation. Rather it’s an argument against not doing one’s homework, of coasting along without anyone ever looking back and asking, what’s the guru's record so far?

UPDATE (3/28/2013): Here's an even better, not to mention more contemporary example ...

If I sleep long enough, maybe it'll go away!