| Marc Smith|
(Alternative names for this author)
|Co-authors||Austin Lin, Dan Cosley, David Sierkowski, Fedor Dokshin, Geri Gay, Gueorgi Kossinets, Howard T. Welser, Rebecca Klein|
|Authorship||Publications (2), datasets (0), tools (0)|
|Citations||Total (5), average (2.5), median (2.5), max (5), min (0)|
|DBLP · Google Scholar|
|Export and share|
|BibTeX, CSV, RDF, JSON|
|Browse properties · List of authors|
Marc Smith is an author.
PublicationsOnly those publications related to wikis are shown here.
|Title||Keyword(s)||Published in||Language||DateThis property is a special property in this wiki.||Abstract||R||C|
|Finding social roles in Wikipedia||English||2011||This paper investigates some of the social roles people play in the online community of Wikipedia. We start from qualitative comments posted on community oriented pages, wiki project memberships, and user talk pages in order to identify a sample of editors who represent four key roles: substantive experts, technical editors, vandal fighters, and social networkers. Patterns in edit histories and egocentric network visualizations suggest potential "structural signatures" that could be used as quantitative indicators of role adoption. Using simple metrics based on edit histories we compare two samples of Wikipedians: a collection of long term dedicated editors, and a cohort of editors from a one month window of new arrivals. According to these metrics, we find that the proportions of editor types in the new cohort are similar those observed in the sample of dedicated contributors. The number of new editors playing helpful roles in a single month's cohort nearly equal the number found in the dedicated sample. This suggests that informal socialization has the potential provide sufficient role related labor despite growth and change in Wikipedia. These results are preliminary, and we describe several ways that the method can be improved, including the expansion and refinement of role signatures and identification of other important social roles.||0||5|
|Reduce response time: Get "hooked" on a wiki||Collaboration
|Proceedings ACM SIGUCCS User Services Conference||English||2007||Managing the flow of information both within the IT department and to our customers is one of our greatest challenges in the Office of Technology Information at Valparaiso University. To be successful, IT staff first need to acquire the right information from colleagues to provide excellent service. Then, the staff must determine the most effective way to communicate that information to internal and external customers to encourage the flow of information. To advance the IT department's goals, how best can we utilize "information" and "communication" vehicles to exchange information, improve workflow, and ultimately communicate essential information to our internal and external customers? We've asked ourselves this question and have resolved that "information" and "communication" need to work cooperatively! How better than with a wiki. Recent changes in departmental structure gave us the opportunity to examine our communication vehicles - specifically the software tools we use to facilitate the flow of information. Our previous knowledge base, First Level Support, a module of the HEAT support software produced by FrontRange Solutions, once met our needs as an internal knowledge base solution. We realized we had outgrown FLS and needed a more robust alternative. Our student employees asked for a newer, more interactive method of sharing information. With the assistance of our UNIX systems administrator, we investigated various options and decided to implement the MediaWiki system. As we had anticipated, use of this wiki system reduced the response time a customer must wait for an answer to their inquiry. What we didn't realize was that utilization of the wiki would meet many more needs than we had anticipated. It has also helped us meet other departmental needs, such as increased collaboration, an online knowledge base, and a training tool for staff. Come see how a sprinkle of pixie dust improved communication through adoption of the wiki, and brought information to the forefront of our operations.||0||0|