Hi Gergő,

Thanks for the extra detail.

On Sep 27, 2014 8:40 AM, "Gergo Tisza" <gtisza@wikimedia.org> wrote:
>
> [uploading many times in a row] suggests some fundamental failing in UW - Sage suggested it is the instability of uploading more than a few files at the same time. I wonder if others have relevant experience?

This has also happened to me. Either uploads time out or one in a set has an error, which iirc prevents any from completing.   But the multi file capability is also not so obvious.

> A little explanation about the more frequent [errors]:
> filename: these seem to be user errors - most often invalid filetype (doc, bmp etc),

<broken record>
These aren't user errors. If a user has material they wish to share under a free license, and we show then an error rather than facilitating that sharing and giving them tools to improve future file sharing, this is a sw + interface error.
</b. r.>

> Investigate if there is a low-effort way to recover entered details when the upload process has to be restarted. (There are drop-in solutions like garlic.js or sisyphus.js but the very dynamic nature of UW forms might be a problem.)
....
> Bigger / longer-term effort:
> figure out a way to retry when the user already entered all the details but publishing the file failed. (This points towards the per-file-workflow-instead-of-global-workflow direction.)
> make stashed / async uploads rely on the database instead of the session (bug 43967)

These three seem particularly good for reducing frustration. If retry is hard, you might at least store the details in a list of unfinished uploads the user can come back to later. That could be more robust than a sisyphus solution. Particularly handy for people using a multi uploader where they may have entered details for 50 items.

Sam