MingleTerminator added projects: Multimedia, Structured-Multimedia-Data. TASK DESCRIPTION //Migrated from: https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/309 // == Narrative == As Multimedia and Wikidata team members, we want to move forward with the wikidata integration before Wikidata on Commons actually gets enabled. == Acceptance Criteria == * Create mock interfaces which behave like Wikidata interfaces but use wikitext to read/write data. * In terms of MediaViewer (where we only do reading, and already interact with the wikitext) that would mean looking at the [[https://bugzilla.wikimedia.org/show_bug.cgi?id=57259 | bug 57259]] ), and maybe some sort of "bundling" of related properties. (E. g. right now we have a bunch of independent fields for short license name, long license name, license URL etc; with Wikidata the file would have a license property, which would be a data item, and the name, URL etc. would be properties of that. Having these fields as independent when in reality they belong together causes us all sorts of problems with multiple values.) * For UploadWizard (where we only write information, in the form of information/license templates on a newly created page) we should hide the current code of generating template text behind an API similar to [[https://www.mediawiki.org/wiki/Extension:Wikibase/API#wbcreateclaim | wbcreateclaim]] . * Mocking a read/write API (i.e. changing metadata by updating already existing wikitext) is something I wouldn't touch with a ten-foot pole. Fortunately, there is nothing on our roadmap AFAIK that would require it. * Check the [[http://wikidata.org/ | wikidata.org]] javascript codefor getting/setting properties. Wikidata uses very specific data types for time, location etc. which can have undefined or uncertain values; we probably do not want to reinvent the UI for that. So we should see how reusablethe existing codeis, howmuch it fits into our use cases, give feedback to the Wikidata team (who plan on refactoring it anyway) on how it could be more useful for us. I think the interesting part for us is [[https://github.com/wikimedia/mediawiki-extensions-Wikibase | Wikibase extensions]] . * Have a look at the [[https://github.com/wmde/WikibaseDataModel/blob/master/src/Wikibase/DataModel/Entity/Item.php | Item]] classes, see if we need anything extra for the new media-info entity subtype which will be used to store file data on Commons. == Related Documents == * **Use cases for key features** to be supported by structured data (both multimedia and VE): [[http://etherpad.wikimedia.org/p/multimedia-visual-editor-wikidata-plans | http://etherpad.wikimedia.org/p/multimedia-visual-editor-wikidata-plans]] • **Wikidata for Media Info** - Proposal by Daniel Kinzler [[https://commons.wikimedia.org/wiki/Commons:Wikidata_for_media_info | https://commons.wikimedia.org/wiki/Commons:Wikidata_for_media_info]] • **Wikidata/Multimedia Team Meeting Notes** : See Nov. 7 - Commons section [[https://etherpad.wikimedia.org/p/Wikidata | https://etherpad.wikimedia.org/p/Wikidata]] • **Machine-readable data on Commons** - Community request [[https://commons.wikimedia.org/wiki/Commons:Machine-readable_data | https://commons.wikimedia.org/wiki/Commons:Machine-readable_data]] == Related Bugs == == Related Stories == [[https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/307 | #307]] - Plan for Structured Data on Commons == Related Changesets ==
TASK DETAIL https://phabricator.wikimedia.org/T77281 REPLY HANDLER ACTIONS Reply to comment or attach files, or !close, !claim, !unsubscribe or !assign <username>. To: MingleTerminator Cc: Aklapper, Wikidata-bugs, Fabrice_Florin, Gilles, Tgr _______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
