This is an archive of past discussions. 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.
Wikidata is a free knowledge base that you can edit! It can be read and edited by humans and machines alike, and you can help. Go to any item page now and add to this ever-growing database!
Need some help getting started? Here are some pages you can familarise yourself with:
Wikidata:Tools - A collection of user-developed JS tools to allow for easier completion of some tasks.
If you have any questions, please ask me on my talk page. If you want to try out editing, you can use the sandbox to try. Once again, welcome, and I hope you quickly feel comfortable here, and become an active editor for Wikidata.
Thanks! I'm mostly keeping an eye on this project to see if there's anything that might be helpful to us, like shared infobox data or anything like that. --Rschen7754 (talk) 19:01, 11 November 2012 (UTC)
I've taken a brief look over and it seems fine. I don't think I'll be doing any editing on this site for another week though, since I'm out of town. --Rschen775421:01, 23 December 2012 (UTC)
You added the label "U.S. Route 412 in Oklahoma" to this item. Why is the "in Oklahoma" necessary? Is that really the common name for the highway? Note that labels do not need to be unique. --Yair rand (talk) 17:43, 1 January 2013 (UTC)
On the English Wikipedia (and on a few other Wikipedias) we have both a "U.S. Route 412" and a "U.S. Route 412 in Oklahoma". Both are technically highways in Oklahoma. However, the first one contains an overview of the second one, as well as the other states that US 412 goes through. Hope this helps. --Rschen775421:02, 1 January 2013 (UTC)
Ah, got it. Thank you for explaining. Another issue is items like "New Mexico State Road 6563". The article seems to refer to it primarily as "State Road 6563" or "NM 6563". Would one of these perhaps be a more appropriate label than "New Mexico State Road 6563"? --Yair rand (talk) 20:47, 2 January 2013 (UTC)
No, they're different per w:WP:USSH - and that resulted out of a long drawn out conflict that ended in an arbitration case on the English Wikipedia. It seems to me that globally, most Wikipedias use the full name as the article title, so in my opinion we should remain consistent (I don't think that they follow that particular guideline globally, though I could be wrong). --Rschen775421:19, 2 January 2013 (UTC)
But we don't have any reason to follow Wikipedia naming conventions when deciding labels. Wikipedia titles have different requirements, such as having every title be unique, which leads them to different standards. Here, disambiguating in done in the description field, and multiple labels can be the same. --Yair rand (talk) 21:28, 2 January 2013 (UTC)
Yes, but that doesn't mean that we shouldn't follow them when all the articles are named that way. Also, some states do include the state name in the official name of the highway. --Rschen775421:31, 2 January 2013 (UTC)
I understand that when the actual name of the highway includes the state name it makes sense to include it, but where it doesn't, wouldn't it just be extra disambiguating text? --Yair rand (talk) 21:38, 2 January 2013 (UTC)
Not necessarily, since there are also different types of highways that all could be in the same state: state highways, county highways, Interstates, U.S. Routes, etc. --Rschen775421:45, 2 January 2013 (UTC)
I don't quite understand how the existence of different types of highways is relevant. Could you please explain further? --Yair rand (talk) 21:51, 2 January 2013 (UTC)
"Route x" could refer to a county route or a state route or an Interstate. Also, "NM 6563" could be anything, really, and is too vague. --Rschen775421:53, 2 January 2013 (UTC)
Labels are allowed to be vague. There isn't really any problem if a it can refer to a county route or a state route or an Interstate. That's why the description field is there. --Yair rand (talk) 22:06, 2 January 2013 (UTC)
My opinion remains that the state name and the type of route need to be included in the label as they are very essential. You are welcome to start a discussion elsewhere if you disagree. --Rschen775422:11, 2 January 2013 (UTC)
Hello! Please note that the confirmation vote for your adminship on Wikidata is scheduled to take place from Mar 18 to Mar 22. You should create a nomination statement at Wikidata:Administrators/Confirm 2013/8 before the beginning of the vote. Thank you! Regards --Iste (D)13:41, 4 February 2013 (UTC)
Activity note: I will be offline for the rest of today, Tuesday, and most of Wednesday. I will be back on Thursday. --Rschen775423:48, 11 February 2013 (UTC)
More or less out of courtesy, since you were concerned that it would reflect badly on you. I am willing to revert it though if you want. --Rschen775400:03, 15 February 2013 (UTC)
Thank you, but I think that's not me who is badly involved by purely displaying the content; I was involved with the events, not the history of the events. :-) Bináris (talk) 00:21, 15 February 2013 (UTC)
Descriptions and more
Hi, due to some illness I have been offline for the last weeks and did not much in Wikidata, but now I want to return. I Have some short questions: Phase 2 is active now and I saw that you are adding several items. When will the other items (length etc.) be online? I think, it's better to edit a road only once and not several times (should be more effective). And another question: I tried to add an description for the item P14 "highway shield". Is it only for sysops allowed, to add such descriptions or is there any bug in my user rights? Greetings from Germany, -- feuerst – talk22:25, 25 February 2013 (UTC)
Sorry to hear that! The other data types (numbers, strings, etc.) are under development and will hopefully be done soon. I'm not sure why the description isn't working - there isn't one, so the field should be open for you to edit... It's not restricted to admins. --Rschen775422:30, 25 February 2013 (UTC)
I found a way to edit the description, in a German forum there had been an answer. To avoid this problem, I have to login in www.wikidata.org, not de.wikidata.org. -- feuerst – talk22:41, 25 February 2013 (UTC)
Wikidata weekly summary #47
Here's your quick overview of what has been happening around Wikidata over the last week.
Development
Extended diff view to include references now
Fixed bug where incorrect statements revision was shown in diff view
Added first version of Linked Data interface (RDF/XML); will be accessible from Special:EntityData
Rollout of phase 1 (language links) on all remaining Wikipedias is still planned for March 6
Next update on wikidata.org is also planned for March 6. This will have bugfixes and if all goes well string as a new available data type.
Proposal was made to the Hungarian, Hebrew and Italian Wikipedias to be the first batch to use phase 2 of Wikidata (infoboxes). Scheduled timeframe for this is end of March
P.S. You might see this message on more than one of your Wikimedia sites: I want to make sure you received this message, as I do not know which Wikimedia site you use the most. Steel1943 (talk) 05:20, 5 March 2013 (UTC)
Wikidata weekly summary #48
Here's your quick overview of what has been happening around Wikidata over the last week.
Development
More work on widget to add language links on the Wikipedias directly without having to go to Wikidata
Bug fixes for Wikipedias, including:
don't show edit link when noexternallanglinks magic word suppresses Wikidata links (bugzilla:45037)
use Q## links instead of linking to Special:ItemByTitle for “edit links” link (bugzilla:44536)
preference for showing Wikidata edits by default in watchlist (bugzilla:44973)
Catching up on writing tests for untested functionality
More work on the Lua support for accessing data from the repository (wikidata.org) on the Wikipedias
Updated Wikidata’s Vagrant development machine
Created initial QueryStore interface
Created initial setup code for the SQL QueryStore
Discussed and created initial schema for the SQL QueryStore
Simplified code for client settings, including which namespaces can have Wikidata links. The default is now all namespaces, without needing to explicitly specify them in the settings
Improved code for sorting interwiki links in the clients, with step towards allowing the communities to specify custom sort orders per Wikipedia
Improved handling of deleted properties
Further work on replacement for current search box
More work on improving error reporting and edit summaries in the API
Tim and Aaron killed the mystery bug that caused corrupt login tokens (bugzilla:41586)
Asked the Italian, Hebrew and Hungarian Wikipedias if they want to be the first to use phase 2 (will ask a few more to join the first batch later today)
Is a specific bug report really important to you? If you have an account on bugs.wikimedia.org you can easily add yourself to the CC list of the bug and then receive updates about its status via email
Here's your quick overview of what has been happening around Wikidata over the last week.
Development
Design improvements to the SetClaim API module
More work on implementing the simple inclusion syntax that will be 1 way to access Wikidata data on Wikipedia
More work on Lua (the second way to access Wikidata data on Wikipedia)
Added parser page property to hold entity id in client. This fixes:
bugzilla:45037 - don’t show edit link if noexternallanglinks has suppressed all Wikidata links
bugzilla:44536 - have the edit link go directly to the Q### pages, instead of Special:ItemByTitle which shall make the link be more reliable and work for all namespaces
Selenium tests for deleted-property-handling
Selenium tests for multiline references
Selenium tests for add-sitelinks-from-client
Selenium tests for Entity-Selector-as-Searchbox
Selenium tests for language-table
Implemented in-process caching for entities
Lua support to access the repo data and implement getEntity (so you can use stuff like entity = mw.wikibase.getEntity("Q1459") in Lua modules)
rebuildTermSearchKey is now ready for production (this still needs to be run but once done it will make search case-insensitive)
Improved error reports from the API
Ground work for better edit summaries from the API
Added a table of content to item pages
Added debug functionality to be able to investigate why it takes longer than it should for Wikidata changes to show up on recent changes and watchlists on Wikipedia
Finished implementation of References-UI
Implemented GUID generator in JavaScript
Worked on fixing a bug related to deleted properties where the UI would display wrong information
Minor fixes/additions to the JS datamodel implementation
If you add a Babel box to your user page Wikidata will show you items and descriptions in other languages you speak as well without you having to switch the language
Want to know which items use a certain property? Try the “what links here” link on a property page
What you wrote does not make sense. It is clear that you do not understand what makes a good admin on this site or on other WMF sites. I can explain further if you wish. --Rschen775408:17, 13 March 2013 (UTC)
Because i think User:Mateuszek045 will probably make a GREAT Administrator.
Probably? Being an admin is a serious thing and is not a game. Will he make a great administrator, or will he not? "Probably" is a very bad thing to say.
Mateuszek045 has been here on the English wiki-data since 25 - January - 2013 ( which is enough to become admin here on wiki -data )
Is it? If I went to some random wiki and made 2 edits, came back 6 months later, and ran for admin, would I be qualified? Also it's Wikidata, not wiki-data.
has autopatrolled rights here
Not everyone who is autopatrolled will make a great administrator.
( but i'm pretty sure you also need the rollback right so that it can be moved in the admin flag ( or other user rights ) ),
That is not written in understandable English.
knows some of the policies/guidelines here,
Some? Why not all?
and is friendly, helpful and busy to other editors and pages, ( and other good things here ).
How can you be "busy" to other editors and pages?
I am definitely sure Mateuszek 045 will become a great, awesome, wonderful, and happy administrator with the mop and new tools than user can use.
There are plenty of unhappy administrators - just look at the English Wikipedia.
Here's some better things to look for:
Click the SULinfo link. Does this editor have any permissions elsewhere? What is their edit count like? Are they blocked anywhere? If you can read the language, what are they like on the wiki where they have the most edits?
Do they understand Wikidata? 500 edits are a minimum now, but the more the better.
Do they participate in Wikidata discussions? Project chat? RfD? RfP?
Have they tried to canvass? In other words, are they campaigning for being an admin? Wikimedia sites are not places for politics.
User rights (admin, rollbacker, bureaucrat, etc.) are not toys. There are 700 Wikimedia projects and none of them will give user rights to you without you showing them that you can be trusted. Right now all you are doing is creating fancy userpages (I've seen you on the English Wikinews, Commons, English Wikiversity, and English Wikisource). That will not get you any userrights. Can you at least please try to work on content? There are plenty of people on Wikidata and the English Wikivoyage that are willing to help you, but you have not asked. Both of these places are a lot easier to edit than Wikipedia. (I am an admin on all 3). If you do good work on content, in 2-3 years you may be able to be an admin, and you can get unblocked on the English Wikipedia.
Curtaintoad, I would like for you to refrain from editing any project, user, or user talk pages until you have made at least five edits to a property or item. Please take your focus off your userpage and userrights (in general).--Jasper Deng (talk) 19:56, 13 March 2013 (UTC)
Well, even wikignomes contribute to content. All that you have been doing is treating WMF sites like Facebook. --Rschen775406:37, 18 March 2013 (UTC)
You (apparently) promised to heed my request, Curtaintoad. Yet you have not and do not seem to understand why I made that request.--Jasper Deng (talk) 01:45, 19 March 2013 (UTC)
I think I am fine with some of the things I have right now (but please help me, I will try help) :*( thanks anyway. Also, could you please not send me the messages such as "that was a very bad idea", "you are treating like Facebook", etc as it gives me personal panic attacks and I really don't like it. Thanks, Curtaintoadcurtain or toad07:40, 21 March 2013 (UTC)
Well what do you want me to say? Do you want me to say "you're doing a good job!" when you're not really accomplishing anything? If you ever want to be an admin, or even an editor, you will have to learn how to face criticism. Check out what some people have said about me here. --Rschen775408:44, 21 March 2013 (UTC)
Let me be more direct. As I previously said, it is your responsibility to avoid "panic attacks", not ours, especially in the face of reasonable criticism. Criticism is sometimes hard to deal with, trust me, but accepting critcism is very important.
If we were to do a plus/delta chart of you, then this is the "delta" side. It is not the same as a "minus" side, in that this criticism is intended for you to know and address what we see as problems with your editing on Wikimedia projects. It can only work if you accept it.
You also say that you want us to help you. This is exactly what we're trying to do. However, if you don't accept our criticism and suggestions, you won't benefit from it.--Jasper Deng (talk) 21:15, 21 March 2013 (UTC)
Wikidata weekly summary #50
Here's your quick overview of what has been happening around Wikidata over the last week.
Development
Rolled out new code on wikidata.org. The new stuff you probably care about is:
Improved references. They can now have multiple lines. This should make references much more useful. You can now have one reference with for example values for each of the properties "book", "author", "page" to describe one source.
Widget to add language links on the Wikipedias directly: added setting to enable/disable it per wiki and made it available for logged-in users only
Widget to add language links on the Wikipedias directly: improved layout / size
Made it so that the “edit links” link on Wikipedia is also shown when the corresponding item only has a link to this one language and no other languages
Submitted improved Apache config patch to make wikidata.org always redirect to www.wikidata.org, which is awaiting code review and deployment.
Improved the script that is responsible for taking Wikidata changes to the Wikipedias
Added a few ways to better debug the script responsible for taking Wikidata changes to the Wikipedias. This should help with investigating why some changes take way to long to show up on the Wikipedias.
Started work on automatically adding edited items to the user’s watchlist (according to preferences)
Finished script for rebuilding search keys, so we can finally get case insensitive matches in a lot of places
Support for multi-line references in diff view
Selenium tests for inclusion syntax
Improved parser function (that will be used to access Wikidata data on the Wikipedias) to accept property ID or label
Increased isolation of data model component to increase clarity and visibility of bad dependencies
Worked on schema access in the SQLStore (of the query component)
When you edit a statement there is a little wheel in front of the text field. This lets you choose between “custom value”, “unknown value” and “no value”. “No value” means that we know that the given property has no value, e.g. Elizabeth I of England had no spouse. “Unknown value” means that the property has a value, but it is unknown which one -- e.g. Pope Linus most certainly had a year of birth, but it is unknown to us.
Worked on making properties accessible from the client using their label so you can use {{#property:executive director}} instead of {{#property:p169}} for example
Made qualifiers ready for the next deployment (Please test. See details further down.)
Selenium tests for qualifiers
Fixed some issues related to QUnit testing
Worked on improved handling and code design of multiple snak lists in the UI (qualifiers, references)
Discussions/Press
Denny wrote down how we’re planning to support queries on Wikidata. Feedback welcome.
Now that improvements for references have been deployed here’s a discussion on the best way to use them. (You can see an example of how it could be used in the source for “CAS registry number” on d:Q153)
We’re currently carefully monitoring performance after the deployment of phase 2 on the first 11 Wikipedias. There seem to be a few small issues. As soon as they are resolved we'll deploy on English Wikipedia. All other Wikipedias are planned to follow very soon after that.
Bye and a big thank you to Anja, Silke, Jens and John who are leaving the development team at the end of the month and will work on other cool things. You’ll be missed!
Ever had any doubt about the possibilities of Wikidata? Talk to Wiri!
We worked on reducing the time it takes for Wikidata edits to show up in the Wikipedias and made some progress. Daniel posted an analysis
We started running a script on the database in order to make search on Wikidata case-insensitive. This should be finished in a few days and then search should be more useful.
In addition to the above we have rolled out a new search box that suggests items. This should also make finding things on Wikidata a lot easier for you.
We’re making some progress with Internet Explorer 8 support but there are a lot of issues with it (some outside our control). It’s unclear at the moment how much we can improve it still without spending an unjustified amount of time on it. You can follow the progress at bugzilla:44228
Edits are now auto-confirmed for users with more than 50 edits and account age 4 days: bugzilla:46461
Do you need old-style interwiki links for a sister project for example? This is for you
The Wikimedia Foundation applied as a mentoring organisation for Google Summer of Code again. We have proposed some Wikidata projects for students to take up if the Foundation is accepted again. At least 2 other organisations that applied also propose Wikidata ideas. More details on that once we know which organisations are accepted.
Denny hacked together a tree of life based on data from Wikidata
Did you file a bug report for Wikidata or did someone else do it for you? Please take a minute to check if it is still valid. (Thanks for filing it btw!)
Could I have 2 mins of your time? As I’ll be working on some other projects for Wikimedia Germany as well from now on the time I can spend on Wikidata will be reduced. This means I’ll have to figure out what is useful to spend time on. If you’re reading this could you let me know for example on this discussion page? Also if you have ideas how to improve the weekly summaries please post them. --Lydia Pintscher (WMDE) (talk)
Here's your quick overview of what has been happening around Wikidata over the last week.
Development
The first year is over. Thank you everyone for being amazing and helping to build Wikidata and making it more than we could possibly have hoped for already. <3
Put a lot of work into improved support for Internet Explorer 8
Worked on improving recent changes code in client
Finished valueview refactoring. Created new extension “ValueView”
Deployment of phase 2 on English Wikipedia is currently planned for April 8. The remaining Wikipedias are scheduled for April 10. As usual this might change if we run into problems along the way.
There is now a page showing the current lag for changes propagating to the Wikipedias so they can show up in watchlists and recent changes for example. This should ideally be in the range of a few minutes. Right now it is higher because of some abnormally high bot activity but decreasing. Should be down to a few minutes soon.
There’s now a badge you can add to Wikipedia articles to indicate there is data about it on Wikidata
Based on feedback for last week’s call for comments we will continue this newsletter. However more community help will be needed. From now on they’ll be drafted at d:Wikidata:Status updates/Next and your help is very welcome.
All our main policies are at Wikidata:List of policies and guidelines - there aren't that many compared to enwiki. Unfortunately there is no date data type yet, the developers are still working on it. There's only links to other items, links to Commons files, and strings that cannot be translated right. now. --Rschen775418:54, 6 April 2013 (UTC)
Much of our policy is still under development, as Rschen says. One thing to note is that everything has no citation at the moment - that's something the developers are working on.--Jasper Deng (talk) 05:53, 7 April 2013 (UTC)
Wikidata weekly summary #53
Here's your quick overview of what has been happening around Wikidata over the last week.
Development
Got some external professional review of our code and architecture and started working on their feedback
Worked on reducing the dispatch lag (the time it takes for changes on Wikidata to be sent to the Wikipedias for display in watchlist, recent changes and to purge affected pages)
Worked on using Redis for job queue to improve the lag situation even further
Created new Wikibase Query extension for phase 3 functionality
We need feedback from contributors working on references addition or having tried to add references to statements. Please comment about your problems or your trials at d:Help:Sources
Other Noteworthy Stuff
Deployment of phase 2 on the remaining Wikipedias was delayed because of a high lag of changes being propagated to the Wikipedias. The lag has been reduced considerably now and is going down even more. The new date for deployment will not be next week because there are other large changes on Wikimedia infrastructure scheduled that we do not want to interfere with. It will hopefully happen very soon after that though.
Next code update on wikidata.org is planned for Wednesday. This should include qualifiers and bugfixes.
There will probably be a short outage/read-only for wikidata.org on Tuesday (database is being switched to MariaDB)
Based on feedback for last week’s call for comments we will continue this newsletter. However more community help will be needed. From now on they’ll be drafted at d:Wikidata:Status updates/Next and your help is very welcome.
The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section.A summary of the conclusions reached follows.
If you delete part of the information ("buried here"), please ensure that it's present as "place of burial". -- Docu at 06:40, 13 April 2013 (UTC)
Absolutely not - we have too many statements to remove, because you continued to add them when the property was at PFD. --Rschen775406:42, 13 April 2013 (UTC)
The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.
Wikidata weekly summary #54
Here's your quick overview of what has been happening around Wikidata over the last week.
Development
Dispatch lag is now down to 0 so changes should show up very quickly on the Wikipedias in watchlists and recent changes
wikidata.org now always redirects to www.wikidata.org. This should among other things solve the issue where people were not able to edit when on wikidata.org (bugzilla:45005)
Fixed weird blocked-user/protected-page handling in UI (bugzilla:45140)
Final meetings for the external professional review of our code and architecture. They were quite happy with the quality of the codebase and gave useful tips for improvements
Worked on automatic summaries for editing claims
Investigation of different JavaScript frameworks dealing with date and time
Worked on using Redis and the job queue for change notifications to clients
Deployment of phase 2 (infoboxes) on English Wikipedia is planned for April 22. All remaining Wikipedias are planned for April 24.
Qualifiers are available now. In the same update several bugs have been fixed mainly related to Internet Explorer 8. At the same time search has been made case-insensitive. More details here.
The problem is that on the translated variants of the page the links to subpages also change. Was it your intention? --Michgrig (talk) 10:26, 23 April 2013 (UTC)
I think there are two ways out. 1) Change the links to subpages from relative ones (like /United States) to absolute ones (like Wikidata:Roads task force/United States), or 2) Move the translatable header to a subpage. Which one do you select? :) --Michgrig (talk) 11:20, 23 April 2013 (UTC)
If fixing a particular bug is especially important for you then please consider voting for it in Bugzilla to help the development team prioritize. A list of all of the currently open ones is here.
Bugfixes were deployed on wikidata.org. The ones you probably care about are:
when clicking "edit links" on a Wikipedia article the user is automatically taken to the language links part of the item. Hopefully it is now more obvious how to change the links.
fixed a few cases where edit conflicts where detected in error
added automatic edit summaries for adding qualifiers and claims
Hey! I just thought I would drop by and introduce myself. I'm AutomaticStrikeout (in case you didn't know) and I'm just saying a friendly hello. AutomaticStrikeout02:56, 11 May 2013 (UTC)
Yeah, I'm familiar from you from enwiki, though I don't know that we've interacted too much over there. --Rschen775403:31, 11 May 2013 (UTC)
Given that it looks like the current RfB will not succeed, I would encourage you to run. It would be good to have another crat and I'd be surprised if you didn't pass. AutomaticStrikeout18:56, 17 May 2013 (UTC)
Thanks, but I don't really feel a need for the bureaucrat tools. I already have three adminships on WMF content wikis and will eventually become an OS on this wiki, and that is already is a large time commitment, so anything that I "run" for in the future will have to be thought out carefully. --Rschen775420:25, 17 May 2013 (UTC)
Deployed new bugfixes on wikidata.org including a fix for pages not being added to the watchlist automatically plus the first version of the RDF exort
The ability to include data using the property label is planned to be deployed on English Wikipedia on Monday and all others on Wednesday (You can then for example use {{#property:logo image}} in addition to {{#property:P154}}.)
Did you know?
Newest properties: exclave of, enclave within, HURDAT identifier, ISO standard, home port, general manager, ISO 15924, Swedish county code, BNFC Thesaurus, cause of death, brother-in-law (sister's husband), honorific prefix, academic degree, birth name, interleaves with, state, phase, powerplant, interaction, part concerned, armament, scheduled service destination, type of orbit, temporal range start, temporal range end, Swedish municipality code, located on island, consists of
{{Property|123}} can be used on Wikidata to get the label of the given property (P123) in the readers language. {{label|Q123}} does the same for items.
Development
Simplified the inclusion syntax (this is one way how you access data from Wikidata in a Wikipedia article - the other one is via Lua)
I am not doing a crosswiki vandalism spree anymore so therefore I would like my account unlocked because I want to edit wikidata and meta wiki with that account and change my signature on english wikipedia. If unlocked, reply on my accounts English Wikipedia talk page and go here but please reply here and leave a talkback notice. Im sorry for that vandalism spree and Im not going to do it again. --74.131.177.23322:00, 23 May 2013 (UTC)
The time datatype can now be tested on the demosystem and should become available on Wikidata next week.
Did you know?
Newest properties: catalog code (P528), runway (P529), diplomatic relation (P530), diplomatic mission sent (P531), diplomatic mission sent (P531), port of registry (P532), target (P533), streak color (P534), Find a Grave (P535), ATP id (P536), twinning (P537), fracturing (P538), Museofile (P539)
d:Template:Constraint:Item allows to check if items using a given property also have other properties. To find items to fix, it links to one of Magnus' tools and to a daily report. Sample: items with property mother should also have main type (GND) with value person.
Development
A lot of discussions and hacking at the MediaWiki hackathon on Amsterdam
Worked on content negotiation for the RDF export
Bugfixing for editing of time datatype
Added validation in the api for claim guids. This also resolves bug 48473, an exception being thrown in production, whenever a bot or api user requested a claim with an invalid claim guid
Improved error message popup bubbles to show HTML and parse the links correctly
Fixed bug 48679, to hide the view source tab for item and property pages
Newest properties: venue (P540), office contested (P541), officially opened by (P542), oath made by (P543), torch lit by (P545), docking port (P546), commemorates (P547), version type (P548), MGP ID (P549), chivalric order (P550), residence (P551), handedness (P552), social media account on (P553), social media address (P554), doubles record (P555), crystal system (P556), DiseasesDB (P557), unit symbol (P558), terminus (P559), direction (P560), NATO reporting name (P561), central bank/issuer (P562), ICD-O (P563), singles record (P564), crystal habit (P565)
Added MediaWiki setting wgLogAutopatrol to allow wikis the option to disable logging of autopatrol actions
Improved EntityPerPage rebuild script, which is needed to fix the situation where some Wikipedia articles can't access data from Wikidata (bugzilla:48506)
Fixed bug in SetQualifiers API module; Moved both SetQualifiers and RemoveQualifiers out of experimental mode
Newest properties: basionym (P566), hangingwall (P567), footwall (P568), date of birth (P569), date of death (P570), foundation/creation date (P571), date of scientific description (P574), discovery date (P575), date of dissolution (P576), date of publication (P577), Sandbox-TimeValue (P578), IMA status (P579), start date (P580), end date (P582), as of (P585), IPNI author ID (P586), MMSI (P587), coolant (P588), point group (P589), GNIS (P590), EC Number (P591), ChEMBL (P592), Homologene ID (P593), Ensembl ID (P594), IUPHAR ID (P595), in the direction of (P596), WTA ID (P597), commands (P598), ITF ID (P599), Wine AppDB-ID (P600), MedlinePlus ID (P604), NUTS (P605), first flight (P606)
I think the best things to do is to restore the old translation markers and correct the translations eventually made in the meantime. --β16 - (talk) 08:19, 10 June 2013 (UTC)
Personally though, I don't see a way around this; putting the new section at the bottom would have been problematic as it would be out of logical order. --Rschen775408:29, 10 June 2013 (UTC)
Newest properties: battle/war (P607), exhibition history (P608), terminus location (P609), exhibition history (P608), terminus location (P609), highest point (P610), religious order (P611), mother house (P612), OS grid reference (P613), CHRC (P616), yard number (P617), source of energy (P618), spacecraft launch date (P619), spacecraft landing date (P620), spacecraft decay date (P621), spacecraft docking/undocking dates (P622), crew photo (P623), guidance system (P624), coordinate location (P625), Sandbox-GeoCoordinateValue (P626), IUCN-ID (P627)
If you're interested in a specific topic then the task forces are a good place to find like-minded people. Can't find one for your interest? Start one!
Development
More progress on supporting links to sisterprojects
Fixing issues with geocoordinate datatype that popped up after deployment
Selenium tests for time and geocoordinate interface
Newest properties: E number (P628), edition of (P629), Paris city digital code (P630), structural engineer (P631), cultural properties of Belarus reference number (P632), Répertoire du patrimoine culturel du Québec identifier (P633), captain (P634), ISTAT ID (P635), route of administration (P636), Protein ID (P637), PDB ID (P638), RNA ID (P639), Léonore ID (P640), sport (P641), of (P642), Genloc Chr (P643), Genloc Start (P644), Genloc End (P645), Freebase identifier (P646), drafted by (P647), Open Library identifier (P648), NRHP (P649), RKDartists (P650), BPN (P651), UNII (P652), PubMed Health (P653), direction relative to location (P654)
Development
Worked on site-link group editing to make it possible to link to sisterprojects
Further work on input validation
Further work on handling invalid data gracefully
Use Serializers for generating API results
Finished selenium tests for TimeUI and CoordinateUI
Changed globe coordinate value input to use backend coordinate parser
Fixed issues with data type definitions not being available in the frontend
Wrote a little hack so that on statements with a long list of values you will always be able to see the name of the property of the current section you are in (since the label moves when scrolling the page)
Road is the more general term, and better in my opinion - some roads are highways and some are not, and some are for part of the length and some are not. Also, there are former highways, and highways that are half controlled access and half not. --Rschen775401:57, 24 June 2013 (UTC)
Willingness to cooperate
Hi! I've read your proposal to join to WD:USRD and I'm ready to join this, but I don't know where to start so can you tell how to help you? --DiegoTheMasterPL (talk) 11:39, 24 June 2013 (UTC)
d:User:Byrial is creating database reports that are useful to find issues in the current data
Denny created a map of all geocoordinates currently in Wikidata (normal and huge version - updated daily)
Did you know?
Newest properties: RTECS number (P657), RefSeq (P656), translator (P655)
Development
The Wikidata bug report with the most votes was closed (bugzilla:36729 - updating the link on Wikidata automatically when a page on Wikipedia is moved)
Wikipedia pages will soon have a link named "Data item" in the toolbox section of the sidebar that links to the Wikidata item that is connected to the page (bugzilla:49105 - You can already see it on the main page of test2.wikipedia.org for example.)
Calendar names displayed for time values can now be translated (bugzilla:49080)
Added serializers for the Ask query language
Buuuugfixes and testing
Refactoring
Worked on better handling of bad values (= values that don't fit the datatype they should have)
Open Tasks for You
Update, expand and translate one of the help pages to make it easier for newcomers
You recently participated in a deletion discussion for P107 - main type (GND). The discussion has been closed, as it is clear that a resolution won't come from PfD, and an RfC has been opened on the matter at Wikidata:Requests for comment/Primary sorting property. You are invited to participate there. Please note that this is a mass delivered message, and that I will not see any replies you leave on this page.
Hi, I have created located on street (P669) and house number (P670) to which you had opposed. I realize that are some shortcomings with those properties, but I think we really need something, and the discussion has been inactive for a few days. Feel free to comment on the properties talk page, or even to nominate it for deletion if you think it is necessary. --Zolo (talk) 19:30, 3 July 2013 (UTC)
Wikidata weekly summary #65
Here's your quick overview of what has been happening around Wikidata over the last week.
Continued work on validation and handling of partially invalid data
Breaking change for 'wbeditentity' in the API fixing (bugzilla:49526) - when creating new items the 'new' parameter must now be given
Improved handling of broken UTF-8 encoding
Made it possible to enter the direction in a geocoordinate also at the beginning now (for example 52°31′N 13°23′E can soon also be entered as N 52°31′ E 13°23′)
Introduced PropertyInfoStore for quick access to meta-info about properties
Deserialization of Description objects in Ask
Lots of bugfixing
Open Tasks for You
Update, expand and translate one of the help pages to make it easier for newcomers
Update and expand Wikidata:Contribute to provide more information for newcomers
