This is an archive of past discussions with User:TCN7JM. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.
With the deployment next Tuesday you will be able to edit all sitelinks at once as well as all fields of the "in other languages" box. This is an intermediate step towards the new user interface and will evolve further over the next weeks. You can see what is coming on Tuesday now already on test.wikidata.org.
WikiProject Names aims to improve name related data on Wikidata. Initial focus is on first names (given names). Half of items for first names still need cleaning up, but 15% of items for persons already have a given name defined.
Worked on supporting statements on properties in WikibaseDataModelSerialization (bugzilla:66425)
Fixed broken xml api output (bugzilla:70531), as well as some inconsistencies in the xml format and added tests that should help avoid future breakage in the xml format
Finished performance improvements for badges
Worked on entity usage tracking
Pietro from the EAGLE project came to visit us, one of the first 3rd party users of Wikibase. See http://www.eagle-network.eu
Added a hook point to allow 3rd party users (like the EAGLE project) of Wikibase to control what goes into the search index
Started work on a widget that lets you edit badges right in the item instead of going to the special page
Want to be kept up-to-date on structured data on Commons? There is now a new newsletter you can subscribe to.
Interested in some statistics about the data on Wikidata? Check Wikidata Stats every now and then. (Thanks Magnus for moving it to the new dump format.)
Spent the week with the WMF multimedia team and volunteers to get more clarity about structured data on Commons. We'll be asking for feedback on a lot of stuff over the next weeks. The main info hub is taking shape at Commons:Structured data.
More fixes for the switch to HHVM
Looked into possible performance improvements. Some of them will be taken into the next sprint.
Battled a handful of nasty issues on the live-site
Here's your quick overview of what has been happening around Wikidata over the last week.
Events/Blogs/Press
Wikidata turned 2 on Wednesday! Have a look at the notes from the community and development team and add your note. Also don't forget to check out all the cool presents (a painting, speed improvements, a huge load of unconnected articles that you can help connect via the Wikidata Game, WikidataLDF, a recent changes visualisation)!
Hello TCN7JM. This message is part of a mass mailing to people who appear active in reviewing articles for creation submissions. First of all, thank you for taking part in this important work! I'm sorry this message is a form letter – it really was the only way I could think of to covey the issue economically. Of course, this also means that I have not looked to see whether the matter is applicable to you in particular.
The issue is in rather large numbers of copyright violations ("copyvios") making their way through AfC reviews without being detected (even when easy to check, and even when hallmarks of copyvios in the text that should have invited a check, were glaring). A second issue is the correct method of dealing with them when discovered.
If you don't do so already, I'd like to ask for your to help with this problem by taking on the practice of performing a copyvio check as the first step in any AfC review. The most basic method is to simply copy a unique but small portion of text from the draft body and run it through a search engine in quotation marks. Trying this from two different paragraphs is recommended. (If you have any question about whether the text was copied from the draft, rather than the other way around (a "backwards copyvio"), the Wayback Machine is very useful for sussing that out.)
If you do find a copyright violation, please do not decline the draft on that basis. Copyright violations need to be dealt with immediately as they may harm those whose content is being used and expose Wikipedia to potential legal liability. If the draft is substantially a copyvio, and there's no non-infringing version to revert to, please mark the page for speedy deletion right away using {{db-g12|url=URL of source}}. If there is an assertion of permission, please replace the draft article's content with {{subst:copyvio|url=URL of source}}.
Some of the more obvious indicia of a copyvio are use of the first person ("we/our/us..."), phrases like "this site", or apparent artifacts of content written for somewhere else ("top", "go to top", "next page", "click here", use of smartquotes, etc.); inappropriate tone of voice, such as an overly informal tone or a very slanted marketing voice with weasel words; including intellectual property symbols (™,®); and blocks of text being added all at once in a finished form with no misspellings or other errors.
