{'fraction_non_alphanumeric': 0.025525525525525526, 'fraction_numerical': 0.0, 'mean_word_length': 5.4396135265700485, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
The Organizational Role of Web Services

I recently had a conversation with a Web services librarian who was grappling with the changing roles of his Web-related duties. The list of duties had grown to include Web site specific and non-Web site specific tasks, including design, updates, archiving, and information architecture; multimedia design for non-Web publications, such as annual reports, event announcements, and marketing materials; systems-focused duties, including server configuration and management; and development duties, including both self-created and third-party applications. The problem we discussed was a common one—finding a way to balance available time against a growing list of projects and responsibilities. As we talked through the list, we found that his span of duties also included marketing, project management, committee work (often marketing or publishing related), and departmental collaboration. While not always explicit in formal job descriptions, libraries often turn to Web services positions to fill a wide range of roles, in part because of the current high visibility of the library Web site. Throughout the conversation, I began to wonder how these duties had evolved and what current expectations of Web librarians might say about the state of organizational transformation in libraries.