This is the umbrella project for the Structured Data on Commons programme, adding structured data for multimedia files (primarily on Wikimedia Commons). For structured data in general, see Wikidata.
General tasks are in SDC General. Design tasks are in SDC Design. Engineering tasks are in Structured Data Engineering.
See also the documentation on Wikimedia Commons.
Some search operator setting should show all images like it's the case with MediaSearch so this can be used e.g. in the template
I'll let StructuredDataOnCommons and @AUgolnikova-WMF weight in on the expected behaviour. Please ping Search Platform if a decision is reached.
Change #1069624 merged by jenkins-bot:
[pywikibot/core@master] Add title function to MediaInfo.
Change #1069624 had a related patch set uploaded (by Aurorakiitaja; author: Aurorakiitaja):
[pywikibot/core@master] Add title function to MediaInfo.
Change #1063025 merged by jenkins-bot:
[pywikibot/core@master] Add tags to the wikibase functions in Pywikibot
I agree having a wrapper around DataSite.save_claim would be useful. I just disagree with the proposed solution. There is no point in adding this method to MediaInfo since DataSite.save_claim does not need the entity object at all.
Currently using it for edits like https://commons.wikimedia.org/w/index.php?title=File:John_Meintz,_punished_during_World_War_I_-_NARA_-_283633_-_restored.jpg&diff=prev&oldid=909842445 where I add missing qualifiers to an existing claim. ( self.site.save_claim(claim, summary=summary, tags='BotSDC') )
We don't have ItemPage.changeClaim either. DataSite.save_claim is wrapped around by Claim.changeRank, and there is also Claim.changeClaimTarget which should already work for all entity types.
Change #1063025 had a related patch set uploaded (by Multichill; author: Multichill):
[pywikibot/core@master] Add tags to the wikibase functions in Pywikibot
As I tried to explain on Telegram, you’re mixing two different things. Linking to another entity in a WikibaseRepo statement is not the same as using an entity in WikibaseClient. Usage tracking is only for the latter ({{#statements:}} and {{#property:}} parser functions, Scribunto/Lua data access), not for the former. As a random example, Q48143124 links to Q48378445 in a statement, yet Q48378445’s subscribers don’t include wikidatawiki. Likewise, as far as I know, Structured Data on Commons statements aren’t tracked as entity usage, neither in wb_changes_subscription on Wikidata nor in wbc_entity_usage on Commons. (The fact that wb_changes_subscription had a row anyway is probably a redirect-related bug due to statement usage from the redirect target, I think.)
Connecting this task to T362149: Alternative, affordable, lower-barrier approach(es) to reconciliation. Reconciliation will be a key part of this effort and this will be a great opportunity to have impact by researching more flexible and affordable approaches to that functionality.
In T370378 we're discussing potentially broadening the scope of gil_to to any pages rather than just files, so maybe we could normalize gil_to to a linktarget instead, and solve both this task and that one at the same time.
At a technical level whats happening is:
I'm interested on contributing, as it seems a great first issue for a python coder, but a noob in the project like me :)
@TheDJ Yes, that's also an issue. Does this happen also for the file I linked? The thumbnail gets displayed on my side but I have only refreshed the page with ctrl + F5 and ctrl + shift + R. The thumbnails are not displaying for all the files from 10 June or later here starting with "Ogham Stone at Church Island" so maybe something happened that day. The thumbnail for this item also doesn't load for more and it's been uploaded before 10 June which could be due to its very large filesize or because it just happens to be one of the few for which I didn't load the thumbnail earlier.
The whole preview image is also not being generated. Thumbor simply returns error 500.
Edge Legacy is no longer supported.
Tagging 3D after all – I doubt the relevant WikibaseQualityConstraints or WikibaseMediaInfo code has changed much recently, and at least the mediainfoview error is a known long-standing issue: T321532 – IMHO this error is more likely due to be due to some recent refactorings in 3D (e.g. es6 changes)
Web browser developer console shows for https://commons.wikimedia.org/wiki/File:3D_model_of_the_human_mouth.stl?debug=true :
TypeError: wikibase.quality.constraints.ui.ConstraintReportList is undefined
Later on there is also
Error: View mediainfoview does not exist
which maybe could be better guarded against this.
@Eugene233: Removing task assignee as this open task has been assigned for more than two years - see the email sent to all task assignees on 2024-04-15.
Please assign this task to yourself again if you still realistically [plan to] work on this task - it would be welcome! :)
If this task has been resolved in the meantime, or should not be worked on by anybody ("declined"), please update its task status via "Add Action… 🡒 Change Status".
Also see https://www.mediawiki.org/wiki/Bug_management/Assignee_cleanup for tips how to best manage your individual work in Phabricator. Thanks!
@Eugene233: Removing task assignee as this open task has been assigned for more than two years - see the email sent to all task assignees on 2024-04-15.
Please assign this task to yourself again if you still realistically [plan to] work on this task - it would be welcome! :)
If this task has been resolved in the meantime, or should not be worked on by anybody ("declined"), please update its task status via "Add Action… 🡒 Change Status".
Also see https://www.mediawiki.org/wiki/Bug_management/Assignee_cleanup for tips how to best manage your individual work in Phabricator. Thanks!