A librarian I once supervised is now heading the systems and digital services department at a mid-size academic library. I’ve recently been e-mailing him some suggestions and things to keep in mind for managing technology in an academic library.

Over a ten year period of managing library technology, I learned some of these the hard way. Some are rudimentary, some are more subtle. I thought that I would share these items (not necessarily listed in any order) for others to take or leave, as they find useful:

1. Hire good people and stay out of their way.
2. Hire for aptitude, the ability to learn new skills and not just based on a person’s current capabilities.
3. Don’t expect every person to work the same way that you work.
4. Don’t make assumptions (remember the first three letters of that word).
5. Encourage systems staff to learn a new skill every 6 months.
6. Ensure that learning time is built into everyone’s work schedule.
7. Have a white board by the department door that staff can use to indicate if they’re out of the office, at a meeting, working on the 2nd floor, or at lunch.
8. Everything a person needs to know about technology can be found through reading a book or on the Internet.
9. No one is born knowing everything about technology.
10. A Unix wizard (or any other kind of techno wizard) is not someone who knows everything there is to know but someone who knows how to find what she needs to know when needed.
11. Make sure there is a backup plan for servers and desktops.
12. Backups of servers should be stored off-site, preferably with a data storage service and not in someone’s bedroom. Test the backups to make sure that files actually can be recovered and loaded onto the system again.
13. Desktop support is a critical function that must receive higher priority than any digital project.
14. Have a multiyear plan for upgrading, replacing computers throughout the library. Not planning this in advance is a huge oversight.
15. Providing the best desktop support will help gain support from others in the library for more exciting digital projects.
16. Occasionally, you may have to remind people that the library is not a hospital; lives will not be lost if a system crashes. But, if the OPAC or Web site goes down, make it a priority over everything else.
17. Follow the lead of the campus IT division.
18. Become friends and supporters of campus IT and not their adversary
19. Let campus IT handle the core functions, such as security and networking.
20. Encourage your staff to meet regularly with their counterparts in campus IT.
21. If campus IT has a standard configuration for desktops, then use it unless the library has extraordinary desktop support staff of its own.
22. But even if you use the campus IT desktop configuration, have your own dedicated desktop support staff who can respond immediately to problems within the library.
23. Use the campus e-mail system rather than an e-mail server managed entirely by the library. (Is any academic library still going it alone with their e-mail?)
24. If the campus has a centralized file storage service, then use it rather than having the library manage its own Windows/Novell file servers.
25. Consolidating certain services with campus IT then allows library systems staff to focus on technologies specific to the library.
26. Work hard to build collaborations with whatever academic technology center exists on campus.
27. Many academic departments will have a negative opinion of campus IT; the library can be a bridge between those two areas, liked and respected by both.
28. Remember that you are not in a competition. You are not competing with other computing groups on campus or with other libraries in the country. You’re just trying to provide the best library services to the faculty and students at your institution.
29. There are always new users.
30. The systems department exists to support the needs of the library, providing a support function to other library departments.
31. Develop a staff training plan for each person.
32. Find projects where staff can incrementally develop their skills.
33. Setup a developmental server, a sandbox.
34. At conferences spend more time in the exhibit hall speaking to vendors and other librarians than sitting in a dark room listening to a presentation that you can download from the Internet.
35. Invest in your own development, including using some of your own funds for travel so that you can attend more events. (Priceline is really useful for hotels).
36. Don’t always stay at the conference hotel; enjoy walking a few blocks from your hotel to the conference hotel so that you have a bit of time to appreciate the town you’re visiting.
37. Learn about project management but don’t obsess over project management tools.
38. Process is important but don’t let a process get in the way.
39. Old but faithful: Treat people the way you want to be treated.
40. Be prepared for your library director to have questions and new ideas whenever she returns from a conference.
41. Don’t ever let anyone tell you there is not money; there is always funding if you know how to ask for it.
42. Learn to say no.
43. The library director doesn’t want to see more than a 1 page report. Learn to summarize, write in bullet points, outlines that can be scanned quickly.
44. Don’t bring problems to the director, bring solutions.
45. Three of the most important people in the library: the director’s secretary, the business officer, and the person who orders equipment, software, supplies.
46. Learn the names of the senior university officials and what they look like.
47. Develop plans for strategic accomplishments, think in terms of 18 - 24 months.
48. Have an excellent understanding of the university’s budget cycle.
49. Know in which month the library director makes her case to the university administration for the following fiscal year’s budget. (Usually in January or February).
50. June and July is too late to be thinking up ideas for new initiatives in the upcoming academic year. (Prepare those proposals before the budget requests are due).
51. But, sometimes new ideas come along: it’s easier to get funding very early in the fiscal year, but don’t wait too long.
52. Around March always be prepared for the availability of end-of-yearing funding for one-time purchases.
53. In the 2nd half of the fiscal year recognize that the budget is tighter, so don’t make many unexpected requests. The administration will like you more for that.
54. Understand the difference between one-time and recurring costs.
55. Understand personnel costs, including the fringe percentage that is added to salary (often between 24% – 30%).
56. Prepare for budget presentations to the library management.
57. Present realistic budget requests but include “throw aways” since administrators always want to cut something from the budget. (Just don’t be extravagant and overload the request with things that are clearly not needed).
58. Be ready to explain the purpose of every item on a budget request.
59. Realize that your budget requests are not the only concerns of the library; you have to share the funding with other library departments.
60. The objectives and goals of the systems department follows those of the library, which follows those of the university.
61. Get a copy of the university’s strategic plan.
62. Try to get involved in the university’s strategic planning process.
63. Become a leader in the library’s planning process.
64. Meet regularly one-on-one (formally or informally) with every department head within the library.
65. Learn to bounce ideas off other department heads and managers before approaching the director (or assistant director).
66. Never make a proposal to the library management group before you already have acquired the support of two other department heads.
67. Old but useful: carefully choose which battles you want to fight.
68. Leadership comes from a person’s quality to inspire and motivate, not from one’s position.
69. Practice “leadership from behind.”
70. Don’t lead by intimidation.
71. Don’t refer to people who work for you as “my staff.” (They have names).
72. Don’t ever refer to yourself as someone’s boss, especially not in front of that person.
73. On the first day of work for a new employee on your staff, take him or her for lunch to a nice place that is off-campus. You pay.
74. On an employee’s first day, give him or her a tour of the library and introduce each person by name.
75. Listening is a very important skill.
76. Ensure that your staff have a good workspace, good chairs, furniture, and that there are always plenty of office supplies.
77. Reference is the most important department within the library; work to keep the head of reference on your side, regardless of your personal opinion of him.
78. No library can do everything. Carefully decide which services and technologies that you want to pursue and make those decisions in collaboration with other stakeholders in the library.
79. It only takes a couple of good people for a library to do remarkable things with technology.
80. Encourage the library to develop professional positions that takes the technologists out of the systems office and into other parts of the library.
81. Your authority has nothing to do with the number of people you supervise.
82. Foster awareness of digital technologies through regular seminars, presentations, or discussions to everyone working in the library.
83. Plan for redundant responsibilities among staff (the “in case someone gets hit by a bus” scenario).
84. Learn to let go, especially if you delegated a task to someone.
85. Not everyone will do a task the way you will have done it, but they will usually do a good job.
86. Some people just need more structured supervision than others and that’s okay.
87. Sometimes, talented employees need more structured supervision on some assignments than others, particularly if the tasks are in an area that is entirely new to the person. (Don’t fault him for that).
88. For some people, working in the library will simply be a job and not a career. Learn to accept that.
89. Help your colleagues understand the possibilities of technologies for developing new library services but also keep their expectations close to what can be accomplished.
90. Look for best practices at other institutions.
91. Work yourself out of a job. You know you’ve been successful when you’re no longer needed.
92. Don’t stress over organizational conflict.
93. Most organizational problems stem from miscommunications.
94. Staff sometimes will need to meet with you in order to vent, express their frustrations with a co-worker. That’s necessary but also encourage the person to think about the work at hand, the objectives and not personality issues.
95. Never make a decision or take an action based on hearsay; second-hand information is the most dangerous element in an organization.
96. We all are always learning how to do our jobs, even library directors and assistant directors. Don’t agonize over every word spoken by a library director. Sometimes, he is just thinking aloud.
97. Likewise, your staff will pay attention to every utterance you make and may at times misconstrue an innocent remark.
98. When socializing with your staff, remember that they never forget that you are their supervisor. So socialize but don’t expect them to be your buddy.
99. Read the Path of Least Resistance. Read it twice.
100. As a librarian you’re making a wonderful contribution to the world, but remember to find time for enjoying your own life.

When programming and developing for the Web I’ve always preferred a Linux box or, in the past few years, Mac OS X. Lately I’m finding myself on a Windows machine and before I go about installing Linux, I wanted to revisit the difficulty of setting up a development environment in Windows (mysql, php, apache). With XAMPP the whole process is remarkably easy.

XAMPP is also available for Linux and versions are in development for Mac OS X and even Solaris. As the documentation strongly states, XAMPP isn’t secure enough for a production environment and is only intended for development purposes. How long does it take to install on Windows? Let’s see…

With the installer version XAMPP is a 33 MB download, so that gives you time to read the documentation. On my connection the download took 3 minutes but there’s really not a lot to read.

The actual install was under 2 minutes. …. since I’m on a Spanish language version of Windows the installed location is C:\Archivos de programa\xampp … I guess that is “c:\Program Files\xampp” for most of you, rigth? I forget.

After installation the XAMPP Control pops up. At this point you need to be sure to have read the part about security. After configuring a couple of passwords you’re then ready to go.

So, just 15 minutes after beginning the download I now have mysql, php, phpmyadmin, apache, and a few other things all working fine on my Windows machine. Simple, I like that.

XAMPP also includes a little batch file that you can use to switch between PHP 5 and PHP 4. You have to stop the apache service first before running the batch file but the XAMPP control panel makes that easy.

Maybe it’s not all that difficult to install all these things individually anymore on Windows. It has been a while since I did that. But with XAMPP I don’t really see why anyone should bother if you just want a development machine. Unless, that is, you’re needing to work with a specific version of MySQL. The version supplied with XAMPP is 5.0.24a.

Of course, I always think that the best development environment is a developmental server that is similar to your production server (same OS, same configuration). But that’s not always a possibility.

Working with technology can be fun when you’re presented with a challenge and need to find a solution. One of my latest tasks is to figure out how to manage more than 100 Web sites, each with its own domain (not subdomain or subdirectory), in the most effective way possible. Some sites will be blogs, others will be more traditional Web site.

I’m very fond of WordPress and my initial thinking was to figure out how to make it work for my needs. I particularly like the way that themes work in WordPress and the ease of designing, customizing the interface will be a factor in implementing all these sites.

And though I do have a dedicated server for all these sites I don’t want to have a hundred instances of WordPress. I would like to have one application installed that can manage sites over multiple domains.

Keeping WordPress in mind I looked at WordPress MU and Lyceum, which are both forks of WordPress designed for multiple users. There are some interesting aspects to those projects that require further examination.

I’ve also collected a number of URLs on this topic, particularly relating to the use of WordPress that I may later add to this post.

For my needs it would be even better to be able to manage these sites all from one admin interface since these will be sites all maintained by one company rather than a lot of different users unaffiliated with each other. So, this makes things a little more complicated.

Also, multilingual capabilities will be nice since some of these sites will be in English and Spanish while some also will be in French.

I started to broaden my search to other content management systems. Drupal immediately came to mind since it’s an impressive project. I thought about Joomla! but it doesn’t seem to support multiple sites from one installation. Seems like Drupal offers a good option for many of the tasks that I need. Will definitely be examining it closer.

But I also decided to think about other CMS options and headed over to the CMS matrix, which lists hundreds of content management systems. I didn’t know that there were so many…not sure why the world needs so many, particularly the ones that costs > $75,000 but, hey, whatever …

A tool that seems very attractive to me is Typo3, particularly for its multi-lingual support and a number of other options. Since I’m less familiar with Typo3 I’m going to be spending some time exploring it. The drawbacks that I gather so far is that it has a high learning curve (no big worry to me) and it is very resource intensive (again, no worry here since I have a dedicated server for this project). Coming next, more info about Typo3….