← Older revision
Revision as of 19:23, 12 March 2014
Line 7:
Line 7:
|contact= oscar.diaz{{@}}ehu.es
|contact= oscar.diaz{{@}}ehu.es
<!--Write a short summary of your project, in 20 words or less in the space below-->
<!--Write a short summary of your project, in 20 words or less in the space below-->
−
|summary= Wikipedia's makes editions readily visible. A stepwise disclosure edition might help shy contributors to retain control of who and when see/contribute to their editions.
+
|summary= Wikipedia's makes editions readily visible. A stepwise disclosure edition might help shy contributors to retain control of who and when see/contribute to their editings.
|more participants=<!--If you want more participants in your proposal, add "YES"-->
|more participants=<!--If you want more participants in your proposal, add "YES"-->
|title={{SUBPAGENAME}}<!--You don't need to change this entry-->
|title={{SUBPAGENAME}}<!--You don't need to change this entry-->
Line 17:
Line 17:
==Project idea==
==Project idea==
−
Wikis in general, and Wikipedia in particular, rest on the premise that edition is readily followed by publication: ''edit&go''. As soon as editing is saved, it becomes readily published. However, this might not be the best approach depending on the type of user.
+
Wikis in general, and Wikipedia in particular, rest on the premise that editing is readily followed by publication: ''edit&go''. As soon as editing is saved, it becomes quickly published. However, this might not be the best approach depending on the type of user.
−
Wikipedia strives to tap into all kind of users. However, not all users feel equally confident when contributing to Wikipedia. Non-English speakers, new comers or youngsters might be intimated by being subject to public scrutiny. Different studies on the use of wikis in education (including Wikipedia) point out potential anxieties of students, namely:
+
Wikipedia strives to tap into all kind of users. However, not all users feel equally confident when contributing to Wikipedia. Non-English speakers, new comers or youngsters might be intimated by being subject to public scrutiny. Different studies on the use of wikis in education (including Wikipedia) point out the potential anxieties of students, namely:
* the fact that edits can be amended and deleted <ref>Raitman, R., Augar, N., and Zhou, W. 2005. [http://dx.doi.org/10.1109/ICITA.2005.127 "Employing Wikis for Online Collaboration in the E-Learning Environment: Case Study"]. Proceedings of the Fifth IEEE International Conference on Advanced Learning Technologies (ICALT ’05).</ref>.
* the fact that edits can be amended and deleted <ref>Raitman, R., Augar, N., and Zhou, W. 2005. [http://dx.doi.org/10.1109/ICITA.2005.127 "Employing Wikis for Online Collaboration in the E-Learning Environment: Case Study"]. Proceedings of the Fifth IEEE International Conference on Advanced Learning Technologies (ICALT ’05).</ref>.
* fear of edits being judged by other users on the accuracy and quality of the edits made <ref>Holtzblatt, L., Damianos, L., and Weiss, D. 2010. [http://doi.acm.org/10.1145/1753846.1754208 “Factors Impeding Wiki Use in the Enterprise: A Case Study”] in Proceedings of the ACM Conference on Human Factors in Computing Systems, Atlanta, Georgia, USA, pp. 4661 – 4675.</ref>.
* fear of edits being judged by other users on the accuracy and quality of the edits made <ref>Holtzblatt, L., Damianos, L., and Weiss, D. 2010. [http://doi.acm.org/10.1145/1753846.1754208 “Factors Impeding Wiki Use in the Enterprise: A Case Study”] in Proceedings of the ACM Conference on Human Factors in Computing Systems, Atlanta, Georgia, USA, pp. 4661 – 4675.</ref>.
* not amending others contributions due to a concern for hurting the feelings of other group members <ref> Kim, H. and Eklundh, K. 2001. [http://dx.doi.org/10.1023/A:1011229212323 "Reviewing Practices in Collaborative Writing"], Computer Supported Cooperative Work, v.10 n.2, p.247-259.</ref>.
* not amending others contributions due to a concern for hurting the feelings of other group members <ref> Kim, H. and Eklundh, K. 2001. [http://dx.doi.org/10.1023/A:1011229212323 "Reviewing Practices in Collaborative Writing"], Computer Supported Cooperative Work, v.10 n.2, p.247-259.</ref>.
* being intimidated by the responsibility of editing in an open wiki setting <ref>Guth, S. 2007. [http://dx.doi.org/10.1145/1296951.1296958 "Wikis in education:: is public better?"], Proceedings of the 2007 international symposium on Wikis, p.61-68.</ref>.
* being intimidated by the responsibility of editing in an open wiki setting <ref>Guth, S. 2007. [http://dx.doi.org/10.1145/1296951.1296958 "Wikis in education:: is public better?"], Proceedings of the 2007 international symposium on Wikis, p.61-68.</ref>.
−
+
−
Therefore, Wikipedia's approach "edit&go" might hinder Wikipedia contribution in educational institutions.
+
Based on these observations, we believe hesitant users might benefit from a more secluded and friendly setting where contributions are ellaborated till finally unveil to the public.
===What is your solution?===
===What is your solution?===
−
We believe edition and visibility should be two orthogonal concerns. Decoupling edition from visibility will account for customized contribution flows. The challenges ahead include (1) supporting distinct "spheres of visibility", and (2) making visibility transparent to edition, i.e. no difference should exists when editing no matter the visibility sphere being chosen.
+
The solution rests on making editing and visibility two orthogonal concerns. The challenges ahead include:
+
* supporting distinct "spheres of visibility", and
+
* making visibility transparent to edition, i.e. no difference should exist when editing no matter the visibility sphere being chosen.
−
'''Challenge 1.''' Contributors should be free to select “the sphere of visibility” with which they feel more confident. Initially, editions can be for their eyes only ('private' sphere). This private setting can be used to collect notes, references, and hold initial drafts, which might be in a too early stage to be release to the public or be shared in the article’s talk page. A first draft can next be shared with close mates who then start to ''collaboratively'' contribute (i.e. 'fellow' sphere). As additional confidence is gained, they can unveil their editing to their supervisors. Finally, they all back the version that ends up being disclosed at Wikipedia.
+
'''Challenge 1.''' Contributors should be free to select “the sphere of visibility” with which they feel more confident. Initially, editions can be for their eyes only ('private' sphere). This private setting can be used to collect notes, references, and hold initial drafts, which might be in a too early stage to be released to the public or be shared in the article’s talk page. A first draft can next be shared with close friends who then, start to ''collaboratively'' contribute (i.e. 'fellow' sphere). As additional confidence is gained, they can unveil their editing to their supervisors. Finally, they all back the version that ends up being disclosed on Wikipedia.
−
'''Challenge 2.''' The introduction of visibility spheres should not jeopardize Wikipedia editing affordance. Editions should be attained in the very same way than before: click the 'edit' tab, and you are done. No need to move somewhere else (i.e. [https://en.wikipedia.org/wiki/Microsoft_Word MS Word], [https://en.wikipedia.org/wiki/Diigo Diigo], [https://en.wikipedia.org/wiki/Evernote Evernote]). No need to learn a new interface. No change from traditional article edition. The difference stems from “the visibility sphere”. By default, the visibility is set to ‘private’. No one will see your edits. Next, contributors can share “their article view” with colleagues taken from their contact list. Finally, “the article view” can be consolidated as a traditional Wikipedia edition. Only after this step is the contribution publicly visible.
+
'''Challenge 2.''' The introduction of visibility spheres should not jeopardize Wikipedia editing affordance. Editions should be made in the very same way as before: click the 'edit' tab, and you are done. No need to move somewhere else (i.e. [https://en.wikipedia.org/wiki/Microsoft_Word MS Word], [https://en.wikipedia.org/wiki/Diigo Diigo], [https://en.wikipedia.org/wiki/Evernote Evernote]). No need to learn a new interface. No change from traditional article edition. The difference stems from “the visibility sphere”. By default, visibility is set to ‘private’. No one will see your edits. Next, contributors can share “their article view” with colleagues taken from their contact list. Finally, “the article view” can be consolidated as a traditional Wikipedia edition. Only after this step is the contribution publicly visible.
−
'''How is this achieved?''' The good news is that there is no need to touch the Wikipedia engine. Previous vision can be realized through a browser plugin. Editions are kept locally in the user's browser till finally consolidated in Wikipedia. Users connect to Wikipedia as before. When the article page is loaded, current Wikipedia content is seamlessly intertwined on the fly with locally-kept editions. This is achieved through sophisticated [https://en.wikipedia.org/wiki/Web_annotation annotation techniques] <ref>Hypothes.is - [https://hypothes.is/blog/fuzzy-anchoring/ Fuzzy anchoring]</ref> and [https://en.wikipedia.org/wiki/Augmented_browsing Web Augmentation]<ref>Díaz, O., Arellano, C. and Azanza, M. [http://dx.doi.org/10.1145/2460383.2460388 "A language for end-user web augmentation: Caring for producers and consumers alike"]. ACM Transactions on the Web 7 (2). pp. 9:1--9:51.</ref> that permits to preserve Wikipedia's GUI and Wikipedia's way of editing. Just an additional button to change the visibility of the editions.
+
'''How is this achieved?''' The good news is that there is no need to touch the Wikipedia engine. Previous vision can be realized through a browser plugin. Editions are kept locally in the user's browser till finally consolidated in Wikipedia. Users connect to Wikipedia as before. When the article page is loaded, current Wikipedia content is seamlessly and dynamically intertwined with locally-kept editings. This is achieved through sophisticated [https://en.wikipedia.org/wiki/Web_annotation annotation techniques] <ref>Hypothes.is - [https://hypothes.is/blog/fuzzy-anchoring/ Fuzzy anchoring]</ref> and [https://en.wikipedia.org/wiki/Augmented_browsing Web Augmentation]<ref>Díaz, O., Arellano, C. and Azanza, M. [http://dx.doi.org/10.1145/2460383.2460388 "A language for end-user web augmentation: Caring for producers and consumers alike"]. ACM Transactions on the Web 7 (2). pp. 9:1--9:51.</ref> that permits the preservation of Wikipedia's GUI and Wikipedia's way of editing. Just an additional button to change the visibility of the editions.
−
A bit more details for techies about the planned implementation. The [https://www.mediawiki.org/wiki/VisualEditor MediaWiki’s VisualEditor] module needs to be extended. This extension is realized in the browser, adding a hook to the MediaWiki’s ResourceLoader when the core of the VisualEditor extension. When adding MyWiki functionality, two new types of nodes are introduced: DissonanceNode and ContributionNode. DissonanceNode is similar to the existing MWReferenceNode; it is a ve.[ce/dm].LeafNode. ContributionNode is similar to the existing TextStyleBoldAnnotation; it is a ve.[ce/dm].Annotation. DissonanceNodes are introduced by the user through the toolbar (ve.ui.DissonanceDialog[Tool]). ContributionNodes are automatically used to annotate all the text introduced by the user capturing the events of content addition (contentChange of VeUISurface).
+
A bit more detail for techies about the planned implementation. The [https://www.mediawiki.org/wiki/VisualEditor MediaWiki’s VisualEditor] module needs to be extended. This extension is realized in the browser, adding a hook to the MediaWiki’s ResourceLoader when the core of the VisualEditor extension. When adding MyWiki functionality, two new types of nodes are introduced: DissonanceNode and ContributionNode. DissonanceNode is similar to the existing MWReferenceNode; it is a ve.[ce/dm].LeafNode. ContributionNode is similar to the existing TextStyleBoldAnnotation; it is a ve.[ce/dm].Annotation. DissonanceNodes are introduced by the user through the toolbar (ve.ui.DissonanceDialog[Tool]). ContributionNodes are automatically used to annotate all the text introduced by the user capturing the events of content addition (contentChange of VeUISurface).
==Project goals==
==Project goals==
−
* Engage fledgling users in Wikipedia editions.
+
* Engage fledgling users in Wikipedia editing.
* Support gradual disclosure of editions.
* Support gradual disclosure of editions.