Christina's LIS Rant
Tuesday, November 07, 2006
ASIST2006: Knowledge Sharing in Online Communities: Digital Trends in Practice
Knowledge Sharing in Online Communities: Digital Trends in Practice
Tuesday, 8:30am
Online Communities of Practice Typology Revisited
Noriko Hara, Pnina Shachaf, Sharon Stoerger
SLIS Indiana, Bloomington
Generally literature of CoPs tends to mainly consist of case studies. There is a need for research on interorganizational CoPs and a typology of CoPs. Dube et al 2003 did a typology of online CoPs. They studied
Learning on a Jet Plane: Distributed Problem Solving and Knowledge Sharing in a Virtual Community of Frequent Fliers
Thomas Haigh
U Wisc – Milwaukee
FlyerTalk. Culture and practice of mileage runs. Large community that is pretty popular online. Demographic information is limited as is the information on lurkers. Profile contains status information based on miles flown per year.
Mileage run – “series of flights taken in a very short amount of time, solely for the purpose of accumulating frequent flyer miles, with a blatant disregard for the destination” (!) (never leave the airport at the destination??)
Mattress run (for hotel stays)
Issues in broader project – interaction of technology and communities, elite status hierarchy, relationships with hotel and airline companies, social codes and rituals in the community
Relevant concepts – virtual communities, distributed problem solving, social capital, social networking…
Exploring authorship and collaboration in student-centered course blogs
Thomas Mackey
SUNY Albany
http://www.albany.edu/~mackey
How do students understand their experience with course blogs? Relevance of blogging to student learning and critical thinking skills.
He reviewed Technorati and Pew statistics and reports, discussing demographics and the public/private combination that blogs are.
Survey on WebCT at the end of the semester (n=90). Setting up a blog was easy, knew about blogs, did not have blogs before, did “provide opportunity to reflect”, more like writing in a diary than writing a research paper, helped them understand the process of blogging, audience professor and classmates.
Hm, for his RQ, I would have liked to see qualitative research instead of quantitative. I would like more information on how they thought of their audience that would be gained from qualitative research.
Knowledge Creation and Sharing in Software Problem Management
Rob Sandusky
U Tenn, Knox
{this was actually really interesting and really well presented. He did a very good job explaining how this all worked and I feel that I inadequately captured it – assume, therefore, that the misconceptions, inaccuracies, and unclear sections below are purely mine}
How can we understand process by which a distributed CoP transforms a phenomenon – a bug - into a manageable representation, leading to a code change that fixes the bug?
Coordination mechanism to support sense making… Mozilla sw dev community. OSS community. Software problem management (SWPM) – to achieve/maintain quality, same in open/closed source projects. Bug ID to close lifecycle. Large-scale information problem, 200-300 reports per day, with 33% duplicates (or rather marked as duplicates by the community, he says).
He looked at “certificate manager crashes mozilla” – 30 month total lifecycle.
Weick version of sense making – community structures the unknown, creation of knowledge when working the bug.
From initial state of uncertainty -- there is a mismatch with what the program is doing and what is supposed to happen, a bug – to repair.
Distributed sense making relies on shared tools and processes, we have the bugzilla tracking database. Coordination mechanism supports learning. – affordances in bug report help create consistent reports easily.
Appended text messages in bug reporting allow for explicit feedback on how to submit bug reports, discourse of the community.
asist2006
Tuesday, 8:30am
Online Communities of Practice Typology Revisited
Noriko Hara, Pnina Shachaf, Sharon Stoerger
SLIS Indiana, Bloomington
Generally literature of CoPs tends to mainly consist of case studies. There is a need for research on interorganizational CoPs and a typology of CoPs. Dube et al 2003 did a typology of online CoPs. They studied
Learning on a Jet Plane: Distributed Problem Solving and Knowledge Sharing in a Virtual Community of Frequent Fliers
Thomas Haigh
U Wisc – Milwaukee
FlyerTalk. Culture and practice of mileage runs. Large community that is pretty popular online. Demographic information is limited as is the information on lurkers. Profile contains status information based on miles flown per year.
Mileage run – “series of flights taken in a very short amount of time, solely for the purpose of accumulating frequent flyer miles, with a blatant disregard for the destination” (!) (never leave the airport at the destination??)
Mattress run (for hotel stays)
Issues in broader project – interaction of technology and communities, elite status hierarchy, relationships with hotel and airline companies, social codes and rituals in the community
Relevant concepts – virtual communities, distributed problem solving, social capital, social networking…
Exploring authorship and collaboration in student-centered course blogs
Thomas Mackey
SUNY Albany
http://www.albany.edu/~mackey
How do students understand their experience with course blogs? Relevance of blogging to student learning and critical thinking skills.
He reviewed Technorati and Pew statistics and reports, discussing demographics and the public/private combination that blogs are.
Survey on WebCT at the end of the semester (n=90). Setting up a blog was easy, knew about blogs, did not have blogs before, did “provide opportunity to reflect”, more like writing in a diary than writing a research paper, helped them understand the process of blogging, audience professor and classmates.
Hm, for his RQ, I would have liked to see qualitative research instead of quantitative. I would like more information on how they thought of their audience that would be gained from qualitative research.
Knowledge Creation and Sharing in Software Problem Management
Rob Sandusky
U Tenn, Knox
{this was actually really interesting and really well presented. He did a very good job explaining how this all worked and I feel that I inadequately captured it – assume, therefore, that the misconceptions, inaccuracies, and unclear sections below are purely mine}
How can we understand process by which a distributed CoP transforms a phenomenon – a bug - into a manageable representation, leading to a code change that fixes the bug?
Coordination mechanism to support sense making… Mozilla sw dev community. OSS community. Software problem management (SWPM) – to achieve/maintain quality, same in open/closed source projects. Bug ID to close lifecycle. Large-scale information problem, 200-300 reports per day, with 33% duplicates (or rather marked as duplicates by the community, he says).
He looked at “certificate manager crashes mozilla” – 30 month total lifecycle.
Weick version of sense making – community structures the unknown, creation of knowledge when working the bug.
From initial state of uncertainty -- there is a mismatch with what the program is doing and what is supposed to happen, a bug – to repair.
Distributed sense making relies on shared tools and processes, we have the bugzilla tracking database. Coordination mechanism supports learning. – affordances in bug report help create consistent reports easily.
Appended text messages in bug reporting allow for explicit feedback on how to submit bug reports, discourse of the community.
asist2006
Labels: asist2006
¶ 10:46 AM| |cites (technorati) |
Comments:
Post a Comment
