Page MenuHomePhabricator

Encouraging users to annotate
Closed, DeclinedPublic

Assigned To
Authored By
Nov 22 2016, 3:35 PM
Referenced Files
F4822735: 6encourage.png
Nov 22 2016, 3:35 PM
F4822737: 7encourage.png
Nov 22 2016, 3:35 PM
F4822723: 2encourage.png
Nov 22 2016, 3:35 PM
F4822728: 3encourage.png
Nov 22 2016, 3:35 PM
F4822730: 4encourage.png
Nov 22 2016, 3:35 PM
F4822732: 5encourage.png
Nov 22 2016, 3:35 PM
F4822720: 1encourage.png
Nov 22 2016, 3:35 PM
F4822739: 8encourage.png
Nov 22 2016, 3:35 PM


When reading about "Stahl House", Henry finds an interesting image of the house where some parts are annotated. Henry discovers that annotations are possible and feels invited to add more. He adds some annotations for testing and is able to quickly remove his own tests without affecting the existign ones. Finally, he annotates a piece of furniture to indicate it was the "tulip chair" by Eero Saarinen. Later, when going back to the article Henry feels he has made a good contribution.

The following ideas can be used in combination with each other. Some of them are appropriate for Commons, some for Wikipedia, and some for both.

WARNING: The table below is not really a table, just saving vertical space
1encourage.png (894×945 px, 586 KB)
2encourage.png (894×950 px, 1011 KB)
3encourage.png (617×576 px, 254 KB)
4encourage.png (894×860 px, 813 KB)
5encourage.png (894×860 px, 811 KB)
6encourage.png (894×570 px, 521 KB)
7encourage.png (755×776 px, 252 KB)
8encourage.png (692×776 px, 507 KB)
This field is intentionally left blank.


  • Control to the editors (4,5) vs. control to the machine (2,6)


  • Users viewing annotations would eventually add them too (1,3)
  • Users adding images, and images to articles should be adding annotations too (7,8)

Event Timeline

Prtksxna renamed this task from Discovery of annotations to Encouraging users to annotate.Nov 22 2016, 3:36 PM
MarkTraceur moved this task from Untriaged to Next up on the Multimedia board.

The only issue I see in these is that "tags" (in #3) is a freak-out word for some people, but that's a minor problem. I like all of these options, so I'm just going to call out the things I really, really loved: Empty annotations are a great idea, and the icon is amazing. Running OCR on images would also be super cool, and it might make Wikisource poke their heads up and wonder how we can help them. 7 and 8 seem like super-natural extensions of our existing workflows, and we definitely had thoughts about tying this in anyway.

There are many interesting patterns here to consider. One aspect I found it may be missing, is that I'm invited to add an annotation but I'm not told why I should do so. We probably don't have room for an in-detail explanation (which is probably not worth it in any case since these tend to be ignored), but we can connect the messages we use with the purpose a bit more. For example, "Would you like to add an annotation to better describe the image?", "Would you like to add an annotation to connect parts of the image with relevant information about them?", etc. The example 1, can use some of these concepts to avoid the guided tour to just replicate the main action label.

Another aspect to consider is how much we want to present this as a blocking step. I think it makes sense to present this as a convenient option for those interested but not add friction or get in the way. This is my main concern about the use of a modal in 7, although a non-blocking alternative would make sense. The rest seem to integrate fluently with existing processes, although we may want to consider options to discard the calls to action in case users want to focus on the image.

Ramsey-WMF changed the task status from Open to Stalled.Nov 17 2017, 5:14 PM
Ramsey-WMF lowered the priority of this task from Medium to Lowest.
Ramsey-WMF added a project: SDC General.
Ramsey-WMF subscribed.

Since the 2016/2017 FileAnnotations prototype work is now quite outdated and both Wikidata and Commons have new features and design plans (like moving new features to Vue.js on Commons), and the extension is not actively under development, the best thing to do is close these tasks and create new ones when/if there's a team available to pick up development on this feature.