Jobs in Information Technology: June 17, 2015

New vacancy listings are posted weekly on Wednesday at approximately 12 noon Central Time. They appear under New This Week and under the appropriate regional listing. Postings remain on the LITA Job Site for a minimum of four weeks.

New This Week

Special Collections Audiovisual Archivist, University of Arkansas, Fayetteville, AR

Systems and Technology Librarian, Catawba College, Salisbury, NC

Visit the LITA Job Site for more available jobs and for information on submitting a job posting.

Embracing Modularity with the Unix Philosophy

Ken Thompson and Dennis Ritchie, creators of UNIX. CC BY-SA 2.0 from http://en.wikipedia.org/wiki/Unix#/media/File:Ken_Thompson_(sitting)_and_Dennis_Ritchie_at_PDP-11_(2876612463).jpg
Ken Thompson and Dennis Ritchie, creators of UNIX (image from Peter Hamer, CC BY-SA 2.0 via Wikimedia Commons)
Unix, the ancient operating system that powered mainframe computers in the 1970’s, couldn’t have been easy to design. Computers of that era were unbelievably expensive and slow compared to what we have today, and this put extreme limitations on the software that they could run. Programs had to take up as little disk space and system memory as possible because there just wasn’t much to go around. With that in mind, the original Unix programmers focused on writing tiny programs that 1) had one functional focus, and 2) played nicely with other programs. The reasoning behind this was that small, simple, single-purpose programs would be easier to improve than large, complex, multi-purpose ones, and if a user didn’t like the way one program worked they could swap it out for a different one (as opposed to being stuck with one mediocre way to do things). In practice, programs would be linked together in pipes, where the output of one program becomes the input to another. The user chooses what programs they use in the pipe, and those programs can be replaced at will if the user finds something they like better. This design principle of making tiny but highly-specialized programs that work together instead of “monolithic” swiss-army knife style programs has been dubbed “The Unix Philosophy“, and it has had a huge effect on the software development community because its just such a gosh dang great idea. Really.

The Unix philosophy as a design heuristic has taken on a life of its own outside of Unix and its descendents, and it seems to be taking root in the community of library-focused open source software. The repository software community in particular seem to be moving away from monolithic all-in-one solutions to modular systems where many different pieces of software all talk to each other and work together to achieve a common goal. Developers are taking successful non-library-focused open source software and co-opting it into their stack. This “don’t reinvent the wheel” approach increases the overall quality of the system AND reduces developer time spent since the chosen software already exists, works well and has its own development community. Consider the use of the Solr search server and the Fuseki triplestore used by the Fedora Commons community. If they had tried to implement their own built-in search and triplestore capabilities it would have required far more developer time to reimplement something that already exists. By using externally developed software like Solr, the Fedora community can rely on a mature project that has its own development trajectory and community of bug squashers.

The Unix philosophy need not be tied just to software, either. I’ve found myself applying it in a managerial sense lately while working on certain projects by creating small, focused teams that do one thing well and pass the work amongst themselves (as opposed to everyone just doing whatever). Another way of looking at it is understanding and capitalizing on the strengths of your coworkers: I’m okay at managing projects but our project manager is much better, and our project manager is okay at coding but I’m much better. It doesn’t make much sense for our project manager to spend time learning to code when he has me, just like it doesn’t make sense for me to focus on project management when I have him (of course there are benefits to this, but in practice its a much smaller return on investment). We both serve the organization better by focusing on and developing our strengths, and leaning on others’ expertise for our weaknesses. This lets us work faster and increases the quality of our output, and in this day and age time and effort are as valuable and limited as the system memory and disk space of a 1970’s mainframe.

LITA Updates, June 2015

This is one of our periodic messages sent to all LITA members. This update includes information about the following:

  • Election Results
  • Learning Opportunities at Annual Conference
  • Annual Conference Highlights
  • LITA Executive Director Plans to Retire

Election Results

Please join in congratulating the newly elected LITA Board Members:

Aimee Fifarek, Vice-President/President-Elect,
Ken Varnum and Susan Sharpless Smith, Directors-at-Large for three-year terms.

Thanks go to the Nominating Committee which included Karen G. Schneider, chair, Pat Ensor, Adriene Lim, and, Chris Evjy, members.

LITA members elected to the ALA Council include: Eric Suess and Joan Weeks, Councilors-at-Large.

Congratulations to all, and, thank you to every candidate who was willing to stand for office.

AC15_logo_FINAL_150px_revLearning Opportunities at Annual Conference

Three full day workshops are being offered in San Francisco on Friday, June 26th. Two of the sessions are in the Moscone Convention Center; the third preconference is off site in a maker/hacker space. These are your choices:

  1. Creating Better Tutorials Through User-Centered Instructional Design. Hands-on workshop with experts from the University of Arizona. Moscone Convention Center 2008 (W)
  2. Learn to Teach Coding and Mentor Technology Newbies – in Your Library or Anywhere! Work with experts from the Black Girls CODE to become master technology teachers. Moscone Convention Center 2010 (W)
  3. Build a Circuit & Learn to Program an Arduino in a Silicon Valley Hackerspace. This workshop will convene at Noisebridge, 2169 Mission Street, a hacker space in San Francisco. Clearly, it will be hands on.

To register for one of these three LITA workshops simply go to the ALA Annual Conference registration and sign up. If you are already registered for conference, the workshop will be added to your registration. If you can’t attend the Annual Conference but a full day workshop on Friday, June 26th from 8:30 – 4:00 pm would be perfect for you, please go to the ALA Annual Conference registration site and sign up. Although you register for these full day workshops through the Annual Conference registration site, please note: you do not have to register for the entire conference in order to register for a workshop. Registration will be accepted on site outside the classrooms for the two workshops in the Moscone Center.

  • Register online through June 19
  • Call ALA Registration at 1-800-974-3084
  • Onsite registration will also be accepted in San Francisco.

Be sure to watch the LITA web sites for announcements about online learning opportunities that are being developed for July and August.

Annual Conference Highlights

The Open House on Friday, June 26, from 3:00 to 4:00pm, MCC-2005 (W), provides members and non-members alike an opportunity to explore with the LITA leadership the many opportunities within LITA. If there is a Committee or an Interest Group that might provide you with the leadership experience you are seeking, this is the perfect time to get some f2f advice. If you have ideas about how LITA might serve you better, this is the perfect time to share those ideas. If you are interested in programming or publications, if you are looking for people who share your interests in various aspects of technology, and/or if you are seeking a good conversation with engaged members, then you will want to attend the Open House.

“Sunday Afternoon with LITA” is scheduled for the Moscone Convention Center, 3014-3016 (W). The Afternoon starts with the popular Top Technology Trends program on June 28th from 1:00 to 2:00pm. This program features our ongoing roundtable discussion about trends and advances in library technology. The panel of experts includes: Carson Block, Andrea Davis, Grace Dunbar, Bonnie Tijerina, and Sarah Houghton, moderator.

A brief awards program at 3:00 will be followed by the LITA President’s Program. The award winners include:

  • Ed Summers, Frederick G. Kilgour Award for Research in Library and Information Technology,
  • David Walker, LITA/Library Hi Tech Award for Outstanding Communication in Library and Information Technology,
  • Heather Terrell, LITA/Ex Libris Student Writing Award for her paper “Reference is dead, long live reference: electronic collections in the digital age.”

Following the awards ceremony, you will want to stay for Rachel Vacek’s President’s Program with Lou Rosenfeld, Rosenfeld Media, which publishes some of the best-loved books in user experience, produces UX events, and equips UX teams with coaching and training.

The Top Technology Trends program, LITA awards ceremony, and LITA President’s Program are all in the same room.

At 5:30, we transition from afternoon to evening at the LITA Happy Hour at DaDa Bar, 86 2nd Street.

LITA provides 20 programs at Annual Conference. Be sure to review the LITA Highlights page for detailed information on all LITA programs and activities planned for Annual Conference.

LITA Executive Director plans to retire

I have good news to share. After 24 years with ALA (14 of those with LITA), over 10 years with OCLC, and various other employment, I plan to retire. My last day will be July 31, 2015. I’m very excited. I’ve had a number of recommendations on what to do including: “spend the first day in your PJs”, and, “really enjoy not working”. I do plan to enjoy not working. I have a number of projects and plans I’ll be exploring, plus, people and places I hope to visit.

If you are in the San Francisco area on Sunday, June 28th, please come to the LITA Happy Hour to celebrate with me and the Membership Development Committee and other LITA leaders and members. The Happy Hour/Party is at the DaDa Bar, 86 2nd Street.

Hope to see you in San Francisco.


I encourage you to connect with LITA by:

  1. Exploring our web site.
  2. Subscribing to LITA-L email discussion list.
  3. Visiting the LITA blog and LITA Division page on ALA Connect.
  4. Connecting with us on Facebook and Twitter.
  5. Reaching out to the LITA leadership at any time.

Please note: the Information Technology and Libraries (ITAL) journal is available to you and to the entire profession. ITAL features high-quality articles that undergo rigorous peer-review as well as case studies, commentary, and information about topics and trends of interest to the LITA community and beyond. Be sure to sign up for notifications when new issues are posted (March, June, September, and December).

If you have any questions or wish to discuss any of these items, please do let me know.

All the best,

Mary

Mary Taylor, Executive Director
Library and Information Technology Association (LITA)
50 E. Huron, Chicago, IL 60611
800-545-2433 x4267
312-280-4267 (direct line)
312-280-3257 (fax)
mtaylor (at) ala.org
www.lita.org

Join us in Minneapolis, November 12-15, 2015 for the LITA Forum.

Congratulations to the LITA UX Contest Winners

The results are in for LITA’s Contest: Great Library UX Ideas Under $100. Congratulations to winner Conny Liegl, Designer for Web, Graphics and UX at the Robert E. Kennedy Library at California Polytechnic State University for her submission entitled Guerilla Sketch-A-Thon. The LITA President’s Program Planning Team who ran the contest and reviewed the submissions loved how creative the project was and how it engaged users. From the sketches that accompanied the submission, and from looking at the before and after screenshots of the library website, it was clear the designers incorporated ideas from the student sketches.

Conny won a personal one-year, online subscription to Library Technology Reports, generously donated by ALA Tech Source. She gets to have lunch with LITA President Rachel Vacek and the LITA President’s Program speaker and UX expert Lou Rosenfeld at ALA in San Francisco. She gets a free book generously donated from Rosenfeld Media. And finally, her winning submission will be published in in Weave, an open-access, peer-reviewed journal for Library User Experience professionals published by Michigan Publishing.

There were so many entries submitted for the contest, picking a single winner was difficult. The Planning Team unanimously agreed to recognize first and second runner-up entries.

The First Runner-Up was the team at the University of Arizona Libraries who submitted their project Wayfinding in the Library. The team included people from multiple departments in their library including the User Experience department, Access & Information Services, and Library Communications. Congrats to Rebecca Blakiston, User Experience Librarian, Shoshana Mayden, Content Strategist, Nattawan Wood, Administrative Associate, Aungelique Rodriguez, Library Communications Student Assistant, and Beau Smith, Usability Testing Student Assistant. Each team member gets a book from Rosenfeld Media.

The Second Runner-Up was the team from Purdue University Libraries who submitted their project Applying Hierarchal Task Analysis Method to Discovery Tool Evaluation. The team consisted of Tao Zhang, Digital User Experiences Specialist and Marlen Promann, Graduate Research Assistant. Each team member gets a book from Rosenfeld Media.

In the coming months, interviews with the winners from each institution will be posted to the blog.

Jobs in Information Technology: June 10, 2015

New vacancy listings are posted weekly on Wednesday at approximately 12 noon Central Time. They appear under New This Week and under the appropriate regional listing. Postings remain on the LITA Job Site for a minimum of four weeks.

New This Week

Electronic Resources Librarian, Samuel Merritt University, John A. Graziano Memorial Library, Oakland, CA

Public Services Manager – Digital Experience, Jefferson County Public Library, Lakewood, CO

Programmer Analyst, Information Services, University of Missouri-Kansas City, Kansas City, MO

Digital Infrastructure Developer, Princeton University, Princeton, NJ

Head of Library Assessment, Pennsylvania State University Libraries, University Park, PA

Reference and Instruction Librarian, York Campus, Pennsylvania State University Libraries, York, PA

Visit the LITA Job Site for more available jobs and for information on submitting a job posting.

Sunday Routines: Susan Sharpless Smith

In this series, inspired by the New York Times’ Sunday Routines, we gain a glimpse into the lives of the people behind LITA. This post focuses on Susan Sharpless Smith, who was recently elected 2015-2018 Director-at-Large.

smith-headshotSusan Sharpless Smith is an Associate Dean at Wake Forest University’s Z. Smith Reynolds Library. She’s been in that role since 2011, but has worked in a range of positions at that library since 1996. Her current job provides a wide variety of responsibilities and opportunities, and fills her week with interesting, meaningful professional work.

Sunday is the day Susan reserves to enjoy her family and her interests. It normally unfolds slowly. Susan is an early riser, often heading for the first cup of coffee and the Sunday newspaper before 6 am. In the summer, the first hour of the day is spent watching the day emerge from her screen porch in Winston-Salem, NC. She is not a big TV watcher but always tunes into the Today Show on Sunday mornings.

Bicycling is one of Susan’s passions, so a typical Sunday will include a 15-40 mile bike ride, either around town or out into the surrounding countryside. It’s her belief that bicycling is good for the soul. It also is one of the best ways to get acquainted with new places, so a bike ride is always on her agenda when traveling. Plans are already underway for a San Francisco bike excursion during ALA!

Susan’s second passion is photography, so whatever she is up to on any given Sunday, a camera accompanies her. (The best camera is the one you have with you!). She has been archiving her photographs on Flickr since 2006 and has almost 10,500 of them. Her most relaxing Sunday evening activity is settling in on her MacBook Air to process photos from that day in Photoshop.

photography

Her son and daughter are grown, so often the day is planned around a family gathering of some sort. This can involve a road trip to Durham, an in-town Sunday brunch, a drive to North Carolina wine country or an hike at nearby Hanging Rock.

family

Her best Sunday would be spent in her favorite place in the world, at her family’s beach house in Rehoboth Beach, DE. Susan’s family has been going there for vacations since she was a child. It’s where she heads whenever she has a long weekend and wants to recharge. Her perfect Sunday is spent there (either for real, or in her imagination when she can’t get away). This day includes a sunrise walk on the beach, a morning bike ride on the boardwalk stopping for a breakfast while people-watching, reading a book on the beach, eating crab cakes for every meal (there’s no good ones in Piedmont North Carolina), a photo-shoot at the state park, a kayak trip on the bay and an evening at Funland riding bumper cars and playing skeeball. It doesn’t get any better than that!

hiking-hanging-rock

LITA Annual Report, 2014-2015

statswinnersmembershipAs we reflect on 2014-2015, it’s fair to say that LITA, despite some financial challenges, has had numerous successes and remains a thriving organization. Three areas – membership, education, and publications – bring in the most revenue for LITA. Of those, membership is the largest money generator. However, membership has been on a decline, a trend that’s been seen across the American Library Association (ALA) for the past decade. In response, the Board, committees, interest groups, and many and individuals have been focused on improving the member experience to retain current members and attract potential ones. With all the changes to the organization and leadership, LITA is on the road to becoming profitable again and will remain one of ALA’s most impactful divisions.

Read more in the LITA Annual Report.

Agile Development: Sprint Review

800px-BIS-Sprint-Final-24-06-13-05

At the boundary between sprints, there are three different tasks that an Agile team should perform:

  1. Review and demo the work completed in the finished sprint (Sprint Review)
  2. Plan the next iteration (Sprint Planning)
  3. Evaluate the team’s performance during the sprint and look for improvements (Sprint Retrospective)

While it may be tempting to package that entire list into one long meeting, these should really be separate sessions. Each one requires a different focus and a unique cast of characters; plus, meetings can only last so long before efficiency plummets. Over the next set of posts I will be discussing each of these tasks separately, in the order in which I listed them. Even though planning happens first in any particular sprint, I prefer to look at the transition between sprints as a single process. So, we’ll start with Sprint Review.

Objective

As we’ve discussed previously, one of the core values of Agile is to prioritize working software; an Agile team should deliver a potentially shippable product at the end of each sprint. This approach increases flexibility (each new sprint is an opportunity to begin with a clean slate and completely change direction if necessary), and forces the entire team (on both the technology and business sides) to optimize feature design. Therefore, at the end of every sprint, the team should be able to demo a new piece of working software, and that is indeed what the focus of the Sprint Review meeting should be.

Participants

This should be the most crowded meeting out of the three; it should be open to all project stakeholders. The development team should attend and be ready to demo their product. This should be an informal presentation, focused on the software itself rather than presentation slides or backlog lists. A more formal approach would take the focus away from the product itself, and it would mean unnecessary prep work for the developers. The team knows what they built, and they should present that to the rest of the participants.

The Product Owner will be there to compare the completed product to the predefined sprint goals, but the focus should be on whether the software fulfills user needs, rather than checking off assigned tickets. The team may have found a better way to solve the problem during the sprint, and the Product Owner would have been consulted at that time, so there should be no surprises.

The demo should also include the Scrum Master, organization management, customers (if possible), and anyone else who is invested in the success of the project. Developers from other teams should be allowed to attend if desired, as a way to promote cross-team communication and organizational knowledge sharing.

Meeting Agenda

The Product Owner should begin the meeting by briefly articulating the sprint goals and providing context for attendees. Again, this shouldn’t be a big formal presentation. Sprints typically only last 1-3 weeks, so no one should be taking up valuable hours getting ready for a review meeting. Each participant is only asked to talk about her specific areas of expertise, so she should be able to almost improvise her remarks.

Next, the development team will demo the completed work, within an environment that mimics production as closely as possible. If the object of the sprint is to produce releasable software, the demo should feel as if the software has been released, so the audience can get a feel for the true user experience. Hard-coded constants and mock-ups should be used minimally, if at all.

Next, the audience should ask questions and offer feedback on the demo, followed by the Product Owner describing next steps and goals. The purpose of this meeting is not for the Product Owner to approve completed work, or for the development team to share their work with one another; that will have happened during the course of the sprint. It is for the PO and the development team to showcase their work and receive feedback on whether the product fulfills the needs of the user.

If you want to learn more about sprint review meetings, you can check out the following resources:

I’ll be back next month to discuss sprint planning.

What are your thoughts on how your organization implements sprint reviews? Who should (or shouldn’t be present a sprint review demo? What do you do about work that has not been completed by the end of the iteration?

BIS-Sprint-Final-24-06-13-05” image By Birkenkrahe (Own work) [CC BY-SA 3.0 (http://creativecommons.org/licenses/by-sa/3.0)], via Wikimedia Commons

 

 

Jobs in Information Technology: June 3, 2015

New vacancy listings are posted weekly on Wednesday at approximately 12 noon Central Time. They appear under New This Week and under the appropriate regional listing. Postings remain on the LITA Job Site for a minimum of four weeks.

New This Week

Content Designer-Bibliographic, EBSCO Information Services, Ipswich, MA

Library Systems Engineer, Analog Devices Inc., Wilmington, MA

Digital Project Manager, Backstage Library Works, Bethlehem, PA

Dean of the Library, Information, and Technology Services, Wilson College, Chambersburg, PA

Digital Services Librarian, Marymount University, Arlington, VA

Visit the LITA Job Site for more available jobs and for information on submitting a job posting.