Hello everyone,
I have been iteration on the post upload actions for the commons app. These actions allow the user to add a description, categories and share it on his preferred social network.
The challenge here was to keep the user in the context of the image he is uploading and at the same time not overwhelming him with input fields.
Do have a look at them. I look forward to your feedback and comments.
[1] https://upload.wikimedia.org/wikipedia/commons/0/04/Multiple-upload-post-upl... [2]http://upload.wikimedia.org/wikipedia/commons/3/38/Post-upload.png
On Tue, Mar 19, 2013 at 11:05 AM, Shankar Narayan notnarayan@gmail.comwrote:
Hello everyone,
I have been iteration on the post upload actions for the commons app. These actions allow the user to add a description, categories and share it on his preferred social network.
The challenge here was to keep the user in the context of the image he is uploading and at the same time not overwhelming him with input fields.
Do have a look at them. I look forward to your feedback and comments.
[1] https://upload.wikimedia.org/wikipedia/commons/0/04/Multiple-upload-post-upl... [2]http://upload.wikimedia.org/wikipedia/commons/3/38/Post-upload.png
Hi Shankar,
These workflows are coming along nicely – pretty excited to try them out soon! :)
For the multiple upload workflow, I prefer option 1 (creating a default title + sequential number for each image, and allowing the user to edit the description/add categories after upload). This generally follows the UI pattern on other sites that allow batch uploading (I'm thinking specifically of Facebook and our very own desktop Upload Wizard, but there are probably other examples), and given the high user/contribution quality we're seeing on the app, I'm not particularly worried about people dumping a bunch of files and then not describing/categorizing them.
I'm still wondering whether there's any real merit in making the user enter a custom title *and* a description, though. There's more thinking and room for error involved on the user's part (if they pick a filename that's taken, they won't be able to upload), and in practice most titles and descriptions are identical. I know this is a legacy workflow from desktop uploading, but I still think we should shake things up a bit and push for less work on the user's part/more streamlined metadata :)
On Wed, Mar 20, 2013 at 12:23 AM, Maryana Pinchuk mpinchuk@wikimedia.orgwrote:
For the multiple upload workflow, I prefer option 1 (creating a default title + sequential number for each image, and allowing the user to edit the description/add categories after upload).
The multiple upload itself (without the post upload actions) has been implemented, should be out on the play store today or tomorrow :)
I'm still wondering whether there's any real merit in making the user enter a custom title *and* a description, though. There's more thinking and room for error involved on the user's part (if they pick a filename that's taken, they won't be able to upload), and in practice most titles and descriptions are identical. I know this is a legacy workflow from desktop uploading, but I still think we should shake things up a bit and push for less work on the user's part/more streamlined metadata :)
Dirty secret: The Android app doesn't yet check for name collisions, and will happily replace them. The reason I've not been torched & pitchforked by the community yet is because the app uses .jpeg as extension, rather than .jpg, thus avoiding a majority of the collisions :) Should be something that is fixed at some point (soon!), yes. I still haven't figured out how the UX for that should look like ('this title already exists, please rename'). Should do at some point. Suggestions for this welcome!
Hi All,
I'm new here, my name is Nicole.
Looking at these, as a user of a lot of uploading applications, I would say get rid of the description field. Title, and categories or tags is enough to find one's images. Otherwise it's too much data and inputting, especially for a mobile app. If you were developing a library app or something, I would understand adding description, because you'd need room for talking about where the image came from, history of the image, etc. But for a mobile app, a title and a category (Title: Noodle Shop, Catagory: Japan 2013) is enough.
Nicole
On Tue, Mar 19, 2013 at 7:06 PM, Yuvi Panda yuvipanda@gmail.com wrote:
On Wed, Mar 20, 2013 at 12:23 AM, Maryana Pinchuk mpinchuk@wikimedia.org wrote:
For the multiple upload workflow, I prefer option 1 (creating a default title + sequential number for each image, and allowing the user to edit the description/add categories after upload).
The multiple upload itself (without the post upload actions) has been implemented, should be out on the play store today or tomorrow :)
I'm still wondering whether there's any real merit in making the user enter a custom title and a description, though. There's more thinking and room for error involved on the user's part (if they pick a filename that's taken, they won't be able to upload), and in practice most titles and descriptions are identical. I know this is a legacy workflow from desktop uploading, but I still think we should shake things up a bit and push for less work on the user's part/more streamlined metadata :)
Dirty secret: The Android app doesn't yet check for name collisions, and will happily replace them. The reason I've not been torched & pitchforked by the community yet is because the app uses .jpeg as extension, rather than .jpg, thus avoiding a majority of the collisions :) Should be something that is fixed at some point (soon!), yes. I still haven't figured out how the UX for that should look like ('this title already exists, please rename'). Should do at some point. Suggestions for this welcome!
-- Yuvi Panda T http://yuvi.in/blog
Design mailing list Design@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/design
On Wed, Mar 20, 2013 at 10:48 PM, Nicole R. Tucker nicole@gala.ws wrote:
Hi All,
I'm new here, my name is Nicole.
Welcome :)
Looking at these, as a user of a lot of uploading applications, I would say get rid of the description field. Title, and categories or tags is enough to find one's images. Otherwise it's too much data and inputting, especially for a mobile app. If you were developing a library app or something, I would understand adding description, because you'd need room for talking about where the image came from, history of the image, etc. But for a mobile app, a title and a category (Title: Noodle Shop, Catagory: Japan 2013) is enough.
This is my current thinking too. It is already optional. But we shouldn't completely get rid of description, I think - there are restrictions on what the title can be (240 bytes only, not too long, can not be a duplicate) that a lot of times we do need a well written description for the image to be usable. I also think that at some point we should (on the app) allow people to do multi-lingual descriptions. Commons is very 'feature' rich, and it's going to be a challenge to bring that out on mobile in a way that doesn't throw out too many features without cluttering everything up. Should be a fun ride!
Hey,
On Wed, Mar 20, 2013 at 10:48 PM, Nicole R. Tucker nicole@gala.ws wrote:
Looking at these, as a user of a lot of uploading applications, I would say get rid of the description field. Title, and categories or tags is enough to find one's images. Otherwise it's too much data and inputting, especially for a mobile app. If you were developing a library app or something, I would understand adding description, because you'd need room for talking about where the image came from, history of the image, etc. But for a mobile app, a title and a category (Title: Noodle Shop, Catagory: Japan 2013) is enough.
A user does expect to have a description field while uploading the image only be it desktop or mobile. If I am uploading from Mobile and it does not have a description field then it would be tedious for me to add description later and possibly sometimes user won't add a description to the file. So maybe we shouldn't get rid of it. Thanks.
Nicole
On Tue, Mar 19, 2013 at 7:06 PM, Yuvi Panda yuvipanda@gmail.com wrote:
On Wed, Mar 20, 2013 at 12:23 AM, Maryana Pinchuk <
mpinchuk@wikimedia.org>
wrote:
For the multiple upload workflow, I prefer option 1 (creating a default title + sequential number for each image, and allowing the user to edit
the
description/add categories after upload).
The multiple upload itself (without the post upload actions) has been implemented, should be out on the play store today or tomorrow :)
I'm still wondering whether there's any real merit in making the user enter a custom title and a description, though. There's more thinking
and
room for error involved on the user's part (if they pick a filename
that's
taken, they won't be able to upload), and in practice most titles and descriptions are identical. I know this is a legacy workflow from
desktop
uploading, but I still think we should shake things up a bit and push
for
less work on the user's part/more streamlined metadata :)
Dirty secret: The Android app doesn't yet check for name collisions, and will happily replace them. The reason I've not been torched &
pitchforked by
the community yet is because the app uses .jpeg as extension, rather than .jpg, thus avoiding a majority of the collisions :) Should be something
that
is fixed at some point (soon!), yes. I still haven't figured out how the
UX
for that should look like ('this title already exists, please rename'). Should do at some point. Suggestions for this welcome!
-- Yuvi Panda T http://yuvi.in/blog
Design mailing list Design@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/design
-- Nicole Tucker, GRP Green Apple Land Arts www.gala.ws
Design mailing list Design@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/design
On 20/03/13 17:35, Arnav Sonara wrote:
Hey,
On Wed, Mar 20, 2013 at 10:48 PM, Nicole R. Tucker <nicole@gala.ws mailto:nicole@gala.ws> wrote:
Looking at these, as a user of a lot of uploading applications, I would say get rid of the description field. Title, and categories or tags is enough to find one's images. Otherwise it's too much data and inputting, especially for a mobile app. If you were developing a library app or something, I would understand adding description, because you'd need room for talking about where the image came from, history of the image, etc. But for a mobile app, a title and a category (Title: Noodle Shop, Catagory: Japan 2013) is enough.A user does expect to have a description field while uploading the image only be it desktop or mobile. If I am uploading from Mobile and it does not have a description field then it would be tedious for me to add description later and possibly sometimes user won't add a description to the file. So maybe we shouldn't get rid of it. Thanks.
Yeah, the description is pretty important to have - they're not always helpful, but not having a description is never helpful, and usually leaves one trying to recategorise or use something on an article wanting. For instance where was the noodle shop, what kind, what's the significance (in other words what might it illustrate in an article)?