I am SO through with customer service!

You know, with the library science background, the library employment experience, and some familiarity with technology, there are any number of possibilities in technology, software consulting, software development, knowledge management, etc. The buzzword that every company in the world was chasing last year was “customer experience”, which means something different to everyone you ask, but for many companies had to do with presenting information to customers in appropriate ways – knowing who the customers are, what the company’s previous interactions with the individual customer have been, what things interest the customer, etc. Some of this ties into the favorite buzzword of a few years ago, “Customer Relationship Management (CRM)”, but beyond managing the information about the customer, there’s another whole realm of managing content about the company, its products and services, etc. This realm, which is generally referred to as “Enterprise Content Management (ECM)”, has to do with the creation, management, tracking, and appropriate deployment of all of that information, in appropriate language, media, form, etc., when and where the customer needs it. To drive that effectively, companies are discovering that they have to deal with issues of ontology, taxonomy, metadata, etc. – they have to make sure that they know what there is to know about all of the content that they’re spending so much money to generate, and that that knowledge is maintained, organized, and disseminated in ways that make accessible to the people and, increasingly, systems that need it.

While I suspect that the hype around “customer experience” has died down somewhat (I got out of the ECM world about a year ago myself), a lot of those efforts – the ones that were better conceived and executed – will continue, and will generate opportunities for people like yourself who understand how information and knowledge can be most effectively organized and managed. My former employer, for example, had one product that was designed to automatically generate keyword, summary, and category information from textual content items (Word docs, PDFs, text files – including web pages – etc.) based on predefined taxonomic information. The rub was that developing the appropriate taxonomic information was beyond the abilities of most of the people at our customers who got assigned to work on it, and beyond the skills of our general consulting team. So we had two consultants with MLS degrees who had spent time in the general library, corporate library, and knowledge management fields. There were people with similar backgrounds involved in product management, support, and development for that product.

Of course, there’s still quite a bit of customer contact in any of those except development, and even there you’ve got product management as the customer to deal with. I would think that in the Boston area, however, there are likely to be any number of corporate library positions that might at least be a change of pace from the academic library world.

Customer service is a two-way street. Just as your opinions and attitudes have changed over the years towards customer service, so have your customers. Don’t beat up on yourself that you feel it’s all your fault.

On the contrary, your customers may share the bigger burden for you wanting out. Good customer service (even adequate customer service) is becoming rarer and rarer not because always having to deal with shitheads, but because more and more customers are becoming even worse shitheads than they used to be.

Forget about Cobol and learn XML. XML is used to organize data for whatever specific need you have, and is pretty common these days as part of the backend portion of websites and online software. I spend the majority of my day working with XML and Lua, which is an increasingly popular scripting language (although I find it a bit of a pain in the ass).

Ooh, a thread with library people in it!

Do you mind if I take an opportunity to ask a question? I don’t think it merits its own thread.
I love the library. I would love to work in a library. I would even enjoy volunteering at a library. But I’m guessing a lot of people feel that way, so my question is, should I ask about volunteer work, or is that the kind of thing that so many people do that there’s never a real need? And can a volunteer library job ever lead to a paying gig?
[/hijack]

Is it possible to get a job knowing just XML? XML is always used in some context (it is, after all, merely a way to represent data) and I would imagine that having some context-specific knowledge would be essential.

Depending on your prior educational experience, your location, and the volunteer job in question, it can definitely help you land a paid job in a library. I would stress to anyone interested in libraries that internships, volunteer positions, and anything else that gives you actual experience in a library are more important than your grades in library school, which you’ll also want to think about if you want to make libraries a permanent career.

Well, I’m not really interested in troubleshooting websites or the actual software itself, though. I’m going to be looking for a straight corporate gig. The reason I’m thinking about learning Cobol is that I’ve heard in here and on the outside that so many end-users of business app’s use it, and I feel it definitely couldn’t hurt. I know a bit of XML, but is that going to be useful to someone like me who’s not interested in the back-end of a server (Not a rhetorical question. I’ve been out of both the corporate and tech loop for a while, and for all I know, half the end-users know XML now).

Sheesh, too bad I don’t have any openings!

Motorgirl, back-office librarian managing several large systems, one of which is written primarily in COBOL. In Massachusetts.

I missed this post the first time around, but I just wanted to come back and say thank you, rackensack. Those are some excellent ideas. I guess that I’ve been so caught up in my academic library headspace that I’ve forgotten there are other types of libraries. Corporate libraries have actually occured to me, and while I haven’t started my job search in earnest yet, I will definitely be looking at these as options. The taxonomies definitely sound interesting, too. I was one of those geeks who actually liked my cataloging class.

You know, I almost didn’t start this thread. I thought it would sound too whiny and “poor-me,” but looking at this feedback, I’m really glad I did. Good stuff! :slight_smile:

Skip the COBOL. Go straight to PHP and SQL. Buy a book on XML for reference. Profit!

Glad you found it useful at least as food for thought. If you think it’s something that might interest you, I’d strongly suggest, as an intermediate step, that you follow up on the recommendation to brush up on XML, and in particular XML standards in the knowledge management arena, as well as tools for structuring information in XML form. The odds are good that it’ll be a key component of anything you do in those areas (for example, the taxonomic information used by the product I mentioned in my earlier post is specified using an XML file in a particular format).

It’s true that XML isn’t useful just sitting around by itself, but the whole point is that it is a powerful tool to add structure to data. If you are a librarian you know a lot about structuring a particular kind of data - the categorization of books. Put the two together and I’m sure you can think of way more possibilities than I could. Improving your C++ skills would help too.