Page MenuHomePhabricator

Making own work questions automatisable with GlobalPreference
Open, Needs TriagePublicFeature


Feature summary (what you would like to be able to do and where):
Current "own work" workflow for UploadWizard presents three questions: "Is this entirely your own work?", "What license do you want to publish this work under?", and "Please select the option that best describes the purpose of this work."

Of the three questions, only the second one is automatisable by expressing a user preference in GlobalPreferences. The request is to create a GlobalPreference also for the other two questions.

Use case(s) (list the steps that you performed to discover that problem, and describe the actual underlying problem which you want to solve. Do not describe only a solution):

All uploads of pictures and/or other media created entirely by the user.

Benefits (why should this be implemented?):

It would reduce the time in uploading media created entirely by the user, by eliminating two extra clicks.

Event Timeline

@Sannita: Assuming this task is about the UploadWizard code project, hence adding that project tag so other people who don't know or don't care about team tags can also find this task when searching via projects. Please set appropriate project tags when possible. Thanks!

@Aklapper Thanks, I usually get lost with the proper tags.

And may be if new options would be added to the Upload Wizard in the future it would be to have an option to choose default answers for them as well. Thanks for creating the task.

Samwilson subscribed.

I think this is about the addition of normal preferences for UploadWizard, and not specifically about GlobalPreferences. Those normal preferences are available in GlobalPrefereces on Commons, but because UploadWizard isn't used anywhere else it doesn't really make sense to make them globalized (although it doesn't matter if they are, either).

@Ymblanter - hi! Thanks for the suggestion. We had a little discussion about this internally, and have a few questions about your proposed solution.

First, just to help contextualize the new additions: These are meant to help us prevent uploads that potentially won't work for Commons, in order to reduce the rate of what could loosely be deemed "bad uploads" - they're *intended* to be additional barriers, not necessarily make things easier. And for what it's worth, while UploadWizard is the main upload tool on Commons, there are a _plethora_ of methods for uploading files, and many of them are more tailored to bulk uploads or experienced users. I've come to think of UploadWizard as the sort of catch-all/middle-ground, but it's far from the only way to get files onto Commons.

The other thing here is that "preference bloat" is an ongoing concern, not necessarily from a technical perspective, but just as a matter of...well, there's a lot of preferences already. I wonder if there's another way to solve this issue, say, with a user script, or some other external tool that either modifies UploadWizard itself, automates some of the process, or even offers a more advanced and customisable upload form. And even though we could use a preference for this use-case, it feels like it may not be the most elegant solution.

That being said, if there's a need to reduce the burden of these two additional clicks on certain prolific uploaders within UploadWizard itself, I wonder if there's a way for us to mitigate how it might impact our intended effect of reducing potentially out-of-scope files, or copyright violations, from relatively new users. One possibility might be to gate any interface changes behind a particular user right - say, autopatrolled - that would allow users to upload with fewer steps, assuming they know what they're doing, or assuming they set a preference first (but only if they have that certain user right).

Basically I'd like to better understand how you'd propose to balance the two competing concerns, and if you think doing so based on user rights makes sense, then what flag(s) you would suggest we use to best conform to what the community would consider a "trusted enough" user to not require these extra confirmation steps. This should hopefully give us a good starting point to figure out how to prioritize and flesh out your request and hopefully fit it into our ongoing work here.