Issue reporting in Wikibase edit schema, focused on the Wikimedia Commons use case

[trnstlntk]

When using OpenRefine's schema editor to prepare edits and uploads to Wikimedia Commons, users should get clear feedback (in the 'issues' tab) about what may go wrong in their edit/upload batches.

This feedback will in some cases be different from the generic feedback for any Wikibase (i.e. not just constraint related) and specific to Wikimedia Commons: think about feedback that concerns duplicate file names, file names with invalid characters...

• @trnstlntk to write specifications for this (what potential problems do we need to cover here; draft copy for clear error messages?..) - deadline May 31, 2022
• @wetneb to build this - deadline June 30, 2022

[trnstlntk]

I hope I got / remembered this one right from our team roadtripping exercise last week. Feel free to tweak.

[trnstlntk]

This one fell between the cracks somehow. Error reporting is important, and we talked about it quite a bit in various contexts.

I feel inclined to close this task (merely for cleanup purposes) because we are tackling this partly in different areas, example: OpenRefine/OpenRefine#5032

[wetneb]

#5032 is about reporting errors after we attempted the upload
This GitHub issue seems to be about the "Issues" tab, which is about reporting problems before the upload (which is something we already have the infrastructure for). It is worth opening issues for issues related to file upload that should be flagged in this Issues tab, for instance like this one: OpenRefine/OpenRefine#5181
(those issues should be in the OpenRefine repo, because file upload is in the Wikibase extension)

[trnstlntk]

There's also this issue: OpenRefine/OpenRefine#5192

I agree that separate issues are better as they emerge (I'm not sure if I'll ever be able to comprehensively list everything that may go wrong).