Description of the Problem

• Problem description: Each upload gets currently post-processed by bots to add structured data according to: Commons:Structured data/Modeling, see for example this diff:

• Proposal type: feature request: the Upload wizard should include some basic structured data (which are not depicts) or prepopulate SDCs in the last step of the upload for the user to confirm

• Proposed solution: After an upload with the upload wizard all information after this diff is already included

• Further remarks:

Discussion

Hello, I'm interested in learning more about this. So, just to confirm, by implementing this change, are we adding an extra step to the upload process? --iMahesh (talk) 10:21, 8 February 2024 (UTC)

@IM3847: Not that you can see. Maybe a teeny bit more processing time.   — 🇺🇦Jeff G. ツ _{please ping or talk to me}🇺🇦 11:07, 8 February 2024 (UTC)

@Jeff G.: In that case, having the structured data analyzed during the upload process would indeed be a valuable feature. --iMahesh (talk) 11:11, 8 February 2024 (UTC)

@IM3847: The Upload Wizard already has a step "Add Data" where the user can add structured data as they wish. Currently, the page does not contain any claims when the user arrives there. One possible implementation of this idea is to not present an empty page there, but a page with SDC claims pre-populated based on all the claims (see diff in the proposal) that would be added by bots as structured data. Then during the same step, the user could see what will be added, modify it if needed or add additional claims prior to finalizing the upload wizard. --Schlurcher (talk) 08:21, 9 February 2024 (UTC)

@Schlurcher: Okay, got it. --iMahesh (talk) 08:31, 9 February 2024 (UTC)

Votes

•  Support -- Supporting as proposer and also as operator of User:SchlurcherBot who does exactly these edits and could otherwise focus on the less well understood SDC cases. --Schlurcher (talk) 08:19, 19 December 2023 (UTC)
•  Support.   — 🇺🇦Jeff G. ツ _{please ping or talk to me}🇺🇦 09:53, 22 December 2023 (UTC)
•  Support Jklamo (talk) 20:56, 1 January 2024 (UTC)
•  Support If the schlurcherbot (one of the most efficient bots I believe) operator believes something could be improved, I of course support it.Paradise Chronicle (talk) 05:31, 14 January 2024 (UTC)
•  Support MGeog2022 (talk) 19:22, 22 January 2024 (UTC)
•  Support — Draceane ^talk_contrib. 08:28, 23 January 2024 (UTC)
•  Support SWinxy (talk) 03:03, 6 February 2024 (UTC)
•  Support --GPSLeo (talk) 18:30, 13 February 2024 (UTC)
•  Support --Askeuhd (talk) 08:47, 22 February 2024 (UTC)
•  Support --Zache (talk) 09:45, 23 May 2024 (UTC)
•  Oppose for adding any structured data that is already in the RDF as this is redundant and a waste of resources, regardless if it is added with the UploadWizard or by a bot like it is now. Ainali (talk) 16:32, 29 March 2026 (UTC)
•  Oppose, partially, per Ainali. The redundant data in SchlurcherBot’s edits should be stopped, not moved to the upload. That said, much of the example diff is not RDF-exported by WikibaseMediaInfo automatically. Some of it perhaps should be RDF-exported automatically – if a computer is going to extract the exposure time (P6757), f-number (P6790), focal length (P2151) or ISO speed (P6789) from the EXIF metadata and represent it as RDF, then we might as well do that in WikibaseMediaInfo at export time, rather than with a bot storing a copy of the information in SDC. But there might also be a grey zone where it’s still valuable to store the information in SDC, such as the copyright license (P275); and in that case, doing it in UploadWizard instead of in SchlurcherBot seems reasonable. --Lucas Werkmeister (talk) 20:38, 29 March 2026 (UTC)