2000 · 18 citations · 0 references
BusinessInformation SystemsInformation Systems ManagementJob DesignWeb TechnologiesCustomer SatisfactionJob SatisfactionE-service SatisfactionTrainingUser Roles
ARL library webmasters were surveyed about aspects of their roles and job tasks. Information was obtained about their education, job responsibilities, job satisfactions and dissatisfactions, and their opinions about Web committees and the role of librarians in Web site development. The article summarizes the information obtained by the survey with recommendations for libraries and library schools. As the Web expanded, libraries began developing Web sites for their patrons. It is not uncommon to hear that the person in charge of the Web site acquired that responsibility only because of his or her early interest in the Web and not because of special training and skills. Similarly, Web site design often has been based on reaction to the need for access to specific local information or other online resources. Early Web sites frequently consisted of lists of links with no other organization or description. As Web page development expanded, so have the positions associated with the activity. Many authors have discussed their role as webmaster and Web site developer (Adams 1997; Block 1998; Commings 1997). In general, a webmaster is responsible for the development and maintenance of a Web site. A webmaster plays many roles, including content provider, editor, designer, programmer, and site administrator (Spainhour and Quercia 1996). Additional responsibilities involve communicating with users of the site, training members of the organization in the use of the Web (Pardue 1998), and researching new technologies (Pardue 1998; Quint 1998). The various aspects of the webmaster's role might be carried out by one person or by as many as dozens of people. A survey of library webmasters of member institutions of the Association of Research Libraries (ARL) was conducted in order to get a clearer understanding of the current roles of library webmasters. Results of this survey and a review of pertinent literature provide insight into a number of expectations and areas of satisfaction and dissatisfaction of library webmasters. Methods The survey was sent out to ARL institutions on January 7, 1998. Recognizing that some institutions have several libraries with their own Web sites, we asked that the webmaster of the Web site of the central library fill out the survey. For the purposes of this survey, a webmaster was someone whose responsibilities may have included, but were not limited to, Web site policy development, editorial oversight of content and graphics, organization of files and directories, page maintenance, and user support. Webmasters at eighty-two institutions returned the survey. Five more institutions stated that the responsibility for their Web site was so distributed that they could not identify one person as the webmaster and so would not fill out the survey. Not every respondent answered every question. Percentages were calculated based on the number who responded to each question, and were rounded to the nearest percent. Results: Who Are the Webmasters? Education Most respondents (78 percent) had an MLIS degree. Eighty-three percent of the holders of this degree graduated during or before 1993, the year that the first version of Mosaic was released (table 1). Ten percent had undergraduate or master's degrees in computer science, information technology, or telecommunications. Over 80 percent of all of the respondents reported teaching themselves computer science and HTML skills, in addition to taking formal courses and workshops (table 2). Table 1 Webmaster Degrees and M.L.I.S. Degree Holders' Graduation Dates Degrees (N=77) No. % Webmasters with the M.L.I.S. degree 60 78 Webmasters without the M.L.I.S. degree 17 22 M.L.I.S. Degree Holders' Graduation Dates (N=58) No. % 1994-96 10 17 1991-93 14 24 1988-90 7 12 1980-87 12 21 1970-79 15 26 Table 2 Educational Background: Computer Science/Instructional Technology and HTML Computer Science/IT(*) HTML(**) Instructional Method No. …