May 23 2017
@Jonas I am very pleased to see you working on this, thank you! Here there is an example that I use often for maintenance:
Apr 28 2017
Ah, ok, thanks for the clarification! Looking forward to the announcement/activation!
@Ladsgroup When I try to create a property I see that "Geographic shape" is an option in the drop-down list, but I don't see "Tabular data set" in the list yet.
Apr 25 2017
@thiemowmde I don't know if you have any bone to pick with @Danwe but from an outside perspective his comment seems legitimate and constructive. The description of this task indeed misleading, and it should be corrected to reflect what the task is truly about.
Apr 24 2017
When I go to https://www.wikidata.org/wiki/Special:NewProperty there is a type by default (String). Shouldn't it be a blank value?
Apr 21 2017
Mar 16 2017
Where is the geoshape/dataset datatype being tracked? In WD it is still not available for property creation.
Jan 24 2017
Any news about this? See also: https://www.wikidata.org/wiki/Wikidata:Bot_requests#User_script_to_notify_participants_in_a_property_proposal
Jan 19 2017
Jan 12 2017
The webconsole says:
I can reproduce it on Firefox 50.1.0 on Windows 7.
Jan 6 2017
There is some criticism about using a fixed set of codes for the representation of languages and variants:
@Jonas If your patch adds a new datatype for Commons datasets, could you please update the ticket description? It seems to me that it doesn't have anything to do with KML files...
Jan 3 2017
Dec 23 2016
@Yurik What about using a wiki page to store categories and metadata about the dataset and then the dataset itself in a subpage. Would it work?
@Esc3300 There is data that cannot be modeled easily in WD, like geodata and climate data, and this is the ideal complement.
@Dereckson Yes, I was using HotCats at the bottom of the page.
Dec 22 2016
Structured datasets are officially available on Commons:
@Nikki Thanks for the query, I have completed the missing information and now it should return only one result - the sandbox item.
Dec 21 2016
Ok, I can imagine that it is not straight-forward. I hope that the same development for Lexicographical data can be reused for the monolingual text, because right now there are users selecting "mis" and not qualifying it with the corresponding language/dialect/variant.
It would be most useful if texts marked as "mis" would accept an item to specify the language used.
Dec 18 2016
@Yurik As the data blobs are finally stored on Commons, can this task be closed?
Dec 8 2016
Will it support URLs generated by external identifier?
Nov 17 2016
Nov 15 2016
Mar 13 2016
@Gymel the issue you describe is different and should be in a different task. This task is only for the "edition/edition of" relationship.
Mar 9 2016
The manual list of properties classifies them per topic. Propbrowse doesn't include the field of application, and that makes hard to find related properties, or properties applicable to a particular item. There is a property tree, from there it should be possible to automate a list of properties. See:
The extension Proofread page features section transclusion. Maybe it can provide some ideas.
Mar 8 2016
@Aklapper What happened with the code? Has it been reviewed?
Mar 5 2016
There is also needed a place to store JSON data, and CSV files for visualization. Would this be the right place for it?
Mar 4 2016
There is no need to create a new module, but some programming is needed to make it work with Template:infobox book. Some versions would need discussion in their talk pages to improve the layout, other wikipedias like the French, have designs better suited for the task. For instance, see the infobox on:
Mar 3 2016
I see that the stalled bug has been marked as resolved, Could this task become a GsoC project?
They could be different properties: "file creator on Commons", "file creator on Flickr", etc. however that would require more data types...
@Purodha It is not the same issue. This task refers to items in wikidata that are split into more two or more items to represent the metadata. Each of the so-called "edition items" has an interwiki link to a different domain. The problem is that since the structure it is like this, it is necessary to aggregate them. For example given the following wikidata items:
Work item (contains interwikis to wikipedia articles)
+Edition item 1 (contains 1 interwiki link to 1 wikisource page)
+Edition item 2 (contains 1 interwiki link to 1 wikisource page)
+Edition item 3 (contains 1 interwiki link to 1 wikisource page)
Mar 1 2016
Some users have created Lua modules that add extra interwiki links based on properties
IIRC @raylton.sousa was mentoring the project last year, I don't know if he could do it again, or if it should be listed as "looking for mentor"
@Aklapper Could it be again featured as a GsoC project?
Feb 28 2016
Feb 26 2016
Feb 25 2016
Some comments from 2014
Feb 24 2016
Aug 11 2015
Aug 10 2015
Jun 28 2015
Jun 27 2015
I am creating a task in Phabricator to make more open the survey process. As announced in the mailing list, the survey can be found here:
Jun 25 2015
Jun 23 2015
@Aklapper, what about:
Jun 20 2015
@jayvdb there is a serious lack of programmers in Wikisource proper.
Jun 17 2015
@Aklapper, as Quim says it is a group for the Wikisource community group activities, not for programming tasks.
Jun 15 2015
@aude you can use the same badge but with the colors of page status used in Wikisource:
Jun 12 2015
Jun 7 2015
Jun 4 2015
Jun 3 2015
The badges needed for Wikisource are:
- not proofread