Wikidata:Project chat

From Wikidata
Jump to: navigation, search
Shortcut: WD:PC
Wikidata project chat
Place used to discuss any and all aspects of Wikidata: the project itself, policy and proposals, individual data items, technical issues, etc.
Please take a look at the frequently asked questions to see if your question has already been answered.
Requests for deletions and mergers can be made here.

IRC channel: #wikidata connect
On this page, old discussions are archived. An overview of all archives can be found at this page's archive index. The current archive is located at October.



What should we do with wrong data from Wikipedia ?[edit]

I have been trying to fix some coordinates using fr:Catégorie:Page avec coordonnées différentes sur Wikidata (currently triggered when wikipedia coordinates are more than 10 kms away from Wikidata's). When the issue comes from fr.wikipedia's coordinates, that is pretty simple: I just delete local frwiki data and the template calls Wikidata instead. But when the issue comes from Wikidata's coordinates, that is more complex. I can fix Wikidata's coordinates. But they have usually been copied from local Wikipedia's values that should be fixed too. I can fix them in the language indicated by the "imported from", but that takes more time. And as errors have often been copied across projects, that does not entirely solve the issue. I can also mark the erroneous data as "deprecated" and let bot see about fixing Wikipedia, but I am not sure this is the most efficient solution. Any other idea ? --Zolo (talk) 13:27, 17 September 2014 (UTC)

The deprecation solution seems not so bad : it leaves a trace that the value was checked by someone. TomT0m (talk) 14:37, 17 September 2014 (UTC)
Marking wrong coors as deprecated does not make a sense for me. In situations like that i simply delete wrond coors from WD (and hoping that some bot will not import wrong coors from another wiki), hoping that most of the wikis will call coors from WD soon. --Jklamo (talk) 10:10, 18 September 2014 (UTC)
+1. Deprecated should be used only with a value having a reference. If you have another value with a reference, the imported value from WP correct or not has to be deleted. Snipre (talk) 10:17, 18 September 2014 (UTC)
Just deleting incorrect (or inappropriate) coordinates are not enough. They are soon imported again. I have started to set "no value" in those cases instead. When it comes to imported data, French Wikipedia is the most frequent source of incorrect coordinate location (P625) and incorrect is in the administrative territorial entity (P131) when it comes to items with coordinates within Swedish territory. /ℇsquilo 12:06, 18 September 2014 (UTC)
@Jklamo: that seems to place a bit too much faith on hope ;). But anyway even if Wikidata want to switch to an all-Wikidata based system, this does not appear like a good solution. If we just delete wrong data in Wikidata without deleting we will have different data in Wikipedia and in Wikidata. If Wikipedia's data are different from Wikidata's, we should not remove them from Wikipedia until we have checked that Wikidata's are either the same or more accurate. If the bad data have been removed from Wikidata, there is no way to do it automatically, so we have to do that by hand all over again. That is one big time waste. If we keep the wrong data in Wikidata, but mark them as deprecated, we know that these are wrong data, and a bot can remove them from Wikipedia. There may be better solutions (that is why I was asking), but unless we have made sure wrong data have been removed from all Wikipedias, depcrecating is certainly better than just removing bad data in Wikidata.
@Snipre: if we have a value with an external reference but that is clearly wrong, it does not seem very reasonable to delete data imported from Wikipedia that appear to be right just because of that (not mentionning that most coordinates data will possibly never have a proper reference, and may not need one).
@Esquilo: Sorry but I do not understand how things would work with "no value", could you give an example ? --Zolo (talk) 12:19, 18 September 2014 (UTC)Zolo (talk) 10:32, 19 September 2014 (UTC)
The core of problem here is the way how data is transferred from Wikipedia to Wikidata. There always should be someone who is responsible for data. If all data is just copied from Wikipedia, noone is responsible -- because Wikipedia authors do not care about data on Wikidata. The only way to make the data actual and remove errors is to remove data from Wikipedia as soon as data is transferred to Wikidata. That's exactly as done in Russian wikipedia: all data from a number of infoboxes is moved from Wikipedia to Wikidata. Along with it we have a number of reports about differences -- and as soon as they resolved, data would be moved to Wikidata completely. Because of that Russian Wikipedia will look after those data (birthdays, deathdays, birth place, death place, nationality, gender, official website) because it is the data actually shown in infoboxes. If it's okay to repeat myself, as I already said on Wikimania-2014 meeting, there should not be any second data copy from Wikipedia to Wikidata. As soon as data is copied from some Wikipedia to Wikidata it shall be prohibited to copy them second time (the same data), i.e. Wikidata should me master copy of data, not any Wikipedia. Not even German. -- Vlsergey (talk) 07:31, 19 September 2014 (UTC)
You demonstrated the consequences of your way: Gadget to create local copy of Wikidata (to disable Wikidata update). Nobody at dewiki is willing to use unreferenced data. So the main question is: how do we improve referencing to relaiable sources. --Succu (talk) 09:09, 19 September 2014 (UTC)
@Succu: 1. It is very obvious consequence and i do not see anything wrong with it until we have sufficient technical support to do the same at MediaWiki level. We need to use common data and at the same time we need control over how it's embedded in protected and semi-protected wikipedia pages. 2. dewiki problem is more "deeper" -- they just don't want to. Doesn't matter if data would be referenced or not. It is just outside of dewiki, so dewiki will not use it. They want to have control over their data and references has nothing to do with it. 3. Original question was not how to handle unreferenced data, but how to remove errors from data. In wikipedia 99.99% of information has no references. Obviously Wikidata would have 90% at min unreferenced but sensitive data. Question should be not how to change it (it's impossible) but how to live with it. 4. The main idea of my answer was "data won't be good until someone would start to use them". Even with restrictions and limitations. -- Vlsergey (talk) 09:40, 19 September 2014 (UTC)
Vlsergey, I think I know a little bit more about the concerns of dewiki (2), but your statement proved them all: Yeah they have data (4), lets use us these unreliable (=unsourced) data (3), because they are data. If we don't like them, let's make us a local copy of wikidata, after we dropped our precious data into wikidata (1). Do you really think this bot-way leads to a better acceptability of wikidata? As you know dropping several database ids from ruwiki into wikidata causes a lot of work, fixing false data. --Succu (talk) 19:59, 19 September 2014 (UTC) BTW: Even coordinates could be sourced: Q4518823 (Q4518823) (see de:Liste der Galapagosinseln#Literatur, my only contribution to dewiki using coordinates).
re Vlsergey. I agree, but it cannot be done for all languages at the same time. Wikpedias often copy each other (especially for basic, language-independent things like coordinates). It means that if data were imported from xwiki to Wikidata, and removed from xwiki, and if someone finds that the data are wrong and corrects Wikidata, it may still be useful to keep them with rank "deprecated" in case other Wikis have the same wrong data.--Zolo (talk) 10:32, 19 September 2014 (UTC)
@Zolo: i don't think it is a good way. Let's consider an example:
  1. bot checks article in xxwiki and finds that birthday field is 1 April 1234 year;
  2. bot checks Wikidata and found there are two values: one is "1 April 1234" and marked as deprecated, second is "2 May 2345" and marked as normal
  3. bot does not edit xxwiki article (not removing "1 April 1234") neither edit Wikidata (add "1 April 1234" to values list), but adds the article to local "discrepansies" xxwiki report, because if he touch anything he would change article content (and by default he must not)
another variant:
  1. bot checks article in xxwiki and finds that birthday field is 1 april 1234 year;
  2. bot checks Wikidata and found there are single value: "2 May 2345" and marked as normal
  3. bot does not edit xxwiki article (not removing "1 April 1234") neither edit Wikidata (add "1 April 1234" to values list), but adds the article to local "discrepansies" xxwiki report, because if he touch anything he would change article content (and by default he must not)
since there is no difference, i don't see the reason to keep incorrect data in Wikidata unless some source (real source, not Wikipedia) displays them. -- Vlsergey (talk) 10:51, 19 September 2014 (UTC)
@Vlsergey:. I was assuming that if local data are equal to those marked as deprecated in Wikidata it was ok to automatically replace them with those marked as normal. Maybe Wikipedias will not be willing to do that, but still I think it would be a sensible way to go, especially for data like coordinates or birth dates, that should usually have just one value. If someone marks a birth date as deprecated and keeps the other one as normal, it is hopefully because the latter is more correct. It may happen that someone or a bot will add a wrong birth date after that. But that should not happen too often because we do not encourage bot to import birth dates from Wikipedia to Wikidata when there is already one. And if it does, we would end up with two birth dates, with at least one without "real" references, and that would be a suspicious case that needs to be checked. In a worst case scenario, the local wrong value will be replaced with an even wronger Wikidata value. But that will most likely be a small minority of cases, so that this way of doing things would still be reasonable. --Zolo (talk) 12:23, 19 September 2014 (UTC)
@Zolo: Wikipedias will never agree to replace their values with Wikidata ones -- not until we prove that Wikidata is more correct than Wikipedia (in 10-15 years, i believe). Because of that so far I don't see how having such values would help. If there is a error in bot code, bot can do anything, including deleting all the claims. Bot shall be fixed. If there is no error, it doesn't matter if we have deprecated value (alongside with correct one) or not. For existing Wikidata values xxwiki [bot] should check their data and not add their value to Wikidata, unless they provide sources and change the ranks accordingly. "If someone marks a birth date as deprecated and keeps the other one as normal, it is hopefully because the latter is more correct" -- the same here: "If someone removes a birth date and replace it with the other one, it is hopefully because the latter is more correct" -- Vlsergey (talk) 12:45, 19 September 2014 (UTC)
@Vlsergey:. It surely depends on the sort of data, but take coordinates that are rather non controversial. Errors usually have pretty trivial reasons like messing up with the decimal conversion. Once they are noticed they are pretty obvious. If someone has marked a value as deprecated there is not much doubt that the value is indeed wrong. The few coordinates that I marked as deprecated were mostly from Dutch and Russian Wikipedias, but it may be that 10 other Wikipedias have the same. If they see that their data matches a deprecated Wikidata value, can they automatically delete them and use the normal or preferred Wikidata values instead ? I think they can. --Zolo (talk) 15:21, 19 September 2014 (UTC)
@Zolo: "can they automatically delete them" -- let's start from other point. Do you already have some Wikipedia in mind that will do that? Does it have timeplan and bot flag/task request discussion? Because i just don't believe that any Wikipedia would do it. And if noone will -- such data is not required. In case someone would -- I would like to have some kind of "delete after" timestamp to cleanup those incorrect data. -- Vlsergey (talk) 17:21, 19 September 2014 (UTC)*
@Vlsergey: I would be willing to ask at fr.wikipedia, but the way I did it means that I did not detected bad values that were imported from fr.wikipedia. Yes, a "delete after" solution would be nice, but that may not be very easy to implement. At worst we can delete all those deprecated values imported from Wikipedia if, after some time, nobody appears to make any use of them. --Zolo (talk) 20:04, 24 September 2014 (UTC)
Many properties has {{Constraint:Single value}}. Bots must not add more than one value per item for these properties. And bots must not replace existing property values because bot can not decide that data is correct in general case. So it is enough to fix invalid data in Wikidata. And we need fix or block bots who are trying to add more than one value or replace existing. Saving a number of values with deprecated rank is very unpleasant way. Collecting errors — is not Wikidata goal. — Ivan A. Krestinin (talk) 07:29, 21 September 2014 (UTC)
@Ivan A. Krestinin:. Sorry, but that does not make much sense. The point of this thread is precisely that it is not always "enough to fix the invalid data in Wikidata". Bots can know that deprecated-rank data are incorrect. Actually, independently from this particular poin, it would seem to make a lot of sense that {{Constraint:Single value}} only take into account data with the bast rank, just like the Wikimedia inclusion syntax does by default. --Zolo (talk) 20:04, 24 September 2014 (UTC)

For manual checking of Wikidata, it may be useful to have the best available source associated with the normal value, and a different source associated with the depricated value that explains why the depricated value is wrong. The source associated with the depricated value might be good, but not as good as the source verifying the normal value. Jc3s5h (talk) 15:34, 25 September 2014 (UTC)

Label lister not working[edit]

The new (BETA) version of the labellister doesn't seem to work. Is it just me? --- Jura 14:08, 17 September 2014 (UTC)

Same for me, will not let me save my changes after Preview; had to switch back to released version. It somehow got broken in the last few days. Author is @Jitrixis: - LaddΩ chat ;) 02:03, 18 September 2014 (UTC)
I miss it already. --- Jura 22:58, 18 September 2014 (UTC)
@Jura1: Fixed. Sjoerd de Bruin (talk) 18:49, 25 September 2014 (UTC)

Label vandalism in a mainstream item[edit]

See Special:Diff/157874111/158717184 : 4 days of IP vandalism on the item on Mathematics. This seems pretty bad to me because it's not a burried item on an unknown topic ... Maybe a little tweaking of the vandalism filter would help a little though :) TomT0m (talk) 10:38, 20 September 2014 (UTC)

@TomT0m: These are things FlaggedRevs could help us with... :-)
What exactly is "a mainstream item"? How does AF recognize such an item?
By the way, the vandalized stuff was a description, not a label. Matěj Suchánek (talk) 17:10, 20 September 2014 (UTC)
I meant an item about a very important subject ( I guess the articles about maths are very consulted on Wikipedia, everybody child in school learns some maths ... compared to, let's say the mayor of a small town of a small country's item, I would think vandalism is caught fast ... This may be a bad sign for overall vandalism rate in Wikidata, hence for the quality of our datas (although less visible items are less exposed) (and it is not that much used yet. It could b a lot more I guess, alyhough a bit too general). TomT0m (talk) 18:19, 20 September 2014 (UTC)
It could be caught fast… if the wikipedia pages used the wikidata item, for label or description... but I don't think it's the case, for now ;) --Hsarrazin (talk) 19:10, 25 September 2014 (UTC)

Sortkey[edit]

Do we have a property for "Sortkey" ? (ie the string that ought to be used for sorting an item in a particular language). I can't seem to find it.

I see that we do have surname (P734) and given name (P735), but that is not helpful for an item like eg Sting (Q483203).

Sortkey is useful for eg: sorting WDQ results in order. It is also needed by some templates for ordering the categorisation of the page they are applied to.

Many many individuals on en-wiki have a Sortkey defined in their PERSONDATA. On Commons, it is also a standard part of the Creator template.

Did I miss it? Is it here all the time? Or is this a property that ought to be created? Jheald (talk) 18:32, 20 September 2014 (UTC)

I don't think you missed it. It actually seems a little weird in the Wikidata paradigm : sorting is something the user of the data might want to do but is not really a property of the datas themselves. It is moreother language (or worse) dependant. If you watch closely to surname (P734) and given name (P735), you will notice that their datatype is not string, which complicate further. Correct me if I'm wrong, but sortkey in your mouth means when we have to sort person by alphabeletical order of their name, we sort them by "sortkey" if available otherwise by family name then by proper name ? TomT0m (talk) 19:28, 20 September 2014 (UTC)
Well unless it is in the database, it is otherwise not possible to search by it. The <Family Name>, <Given Name> <Middle Names>, <title> format is pretty standard for many applications -- en:Wikipedia:Persondata notes that it is used both by the Library of Congress in the U.S. and by Deutsche NationalBibliothek -- so it is something that, if possible, we should aim to hold and be able to make available to those that want it. Another key example where this property is needed is to be able to properly format (or re-format) citations per certain style guides.
This is information that is not necessarily easy to extract from names. Of course, one can often make a good first guess; but it really needs the data to be stored to identify that it should be "Beethoven, Ludwig van" but "Van Zandt, Townes".
So, questions, before submitting a property proposal
  • Should this be a string or multilingual text ?
    Do different langages differ much, eg LoC <-> DNB ? Or are there clear language preferences ? If the latter, would language fallbacks work sanely ? Or, are there appropriate qualifiers that could be used to do the job.
In Irish names are sorted by the surname but without the Ó or Mac prefix. 86.6.111.107 02:27, 22 September 2014 (UTC)
  • Should diacritics be included ?
  • Should this apply only to personal names, or should eg Book-titles also have their standardised searchable forms recorded ?
  • Is there a better name for the property ?
... more ? Jheald (talk) 22:28, 20 September 2014 (UTC)
This seems to be a language characteristic or maybe a flag to be included in a query rather than a characteristic of the concept/item so I would be opposed to trying to describe this in the statements about the item. 86.6.111.107 02:27, 22 September 2014 (UTC)
And how do you propose to query it, if it's not in the database? Jheald (talk) 16:16, 23 September 2014 (UTC)
You pick a query and specify which associated property statements should be downloaded (into a table) and then specify which value (column) should be used as the sort key.
This won't help if you want to sort as "Beethoven, Ludwig van" but "Van Zandt, Townes" but the only reason you would want to do that would be if 'Van Zant' is considered one surname and 'van Beethoven' is considered a prefix and a surname in which case specify 'surname:Van Zant' and 'surname:Beethoven' and use 'surname' as the sortkey.. Filceolaire (talk) 18:43, 23 September 2014 (UTC)
@Filceolaire: Some reasons to prefer creating an item 'Sortkey':
  1. It accomodates names like Sting (Q483203), which is neither a surname nor a forename, and other such unusual cases.
  2. surname (P734) is a controlled vocabulary property -- it can only be used if an item exists for the surname. On the other hand, Sortkey as a string or multilingual text property can be universal
  3. The data to populate the property is readily available from en.wiki, de.wiki, LoC and DNB
  4. The property is required as part of Wikidata-ization of the Commons {{Creator}} template, which it would be good to ultimately be able to retire. Jheald (talk) 07:07, 25 September 2014 (UTC)
I can see this working as a multilingual text datatype so you can specify a different sortkey for each language (e.g. for Irish as the comment above) and every sortkey has a language (or languages) associated with it. Filceolaire (talk) 22:14, 27 September 2014 (UTC)

Wikidata Game Slow[edit]

The game is slow for me as I can it won't load in Chrome. I tried it yesterday and I couldn't login to it. Magnus anything? Eurodyne (talk | contribs) 21:58, 20 September 2014 (UTC)

Just restarted. Again. Currently on vacation, reduced connectivity. --Magnus Manske (talk) 20:03, 21 September 2014 (UTC)
Thanks a bunch! Eurodyne (talk | contribs) 20:07, 21 September 2014 (UTC)
Magnus Manske Is it down again? Eurodyne (talk | contribs) 02:01, 23 September 2014 (UTC)
Yes, it's been down for a few days now.... and so is Catscan - I think I saw Magnus is on vacation… which he much deserves… so, we'll try to be patient :D --Hsarrazin (talk) 19:15, 25 September 2014 (UTC)

Fresh category members tool idea[edit]

Hi. I'd like to (and I'm almost in the process on) write a tool which would show latest category members -- with subcats, recursively -- for new page patrol purposes. It would be a web app where you type a wiki name and category name and get a list of category members sorted by time. Later on I'd have to implement pages (if there's too many) or limit the time frame. Is this worth doing given that categories would move to Wikidata soon? If so, how soon? Thoughts? (P.S. Please distribute to sister projects village pumps). Gryllida 07:32, 21 September 2014 (UTC)

Could you develop the idea?
Maybe you could join a wireframe showing the UI? --Dereckson (talk) 13:21, 21 September 2014 (UTC)
What is a "wirefeame"? Yes, I can try to develop it. You might know how work with databases performance is pretty hard, but I hope to try to complete. Gryllida 01:08, 22 September 2014 (UTC)
A rough graphic representation of the user interface. Not the design, just the areas and elements to print (widgets).
We have some samples on Wikimedia Commons : commons:Category:Website wireframes. --Dereckson (talk) 16:58, 26 September 2014 (UTC)
  • I like the idea. I am even thinking about more advanced gadget - "Category history", which should show also deleted members. But obviously it is quite hard query by now. As for future of categories - their elimination is a question of quite long time (I'd say - years). --Infovarius (talk) 19:38, 21 September 2014 (UTC)
Eliminate categories? This sounds like a good recipe to wipe out all sisters that don't happen to have Wikipedia-like category hierarchies. Wikivoyage would probably be unaffected. Wikinews does things differently, and would be deprived of control of that part of its own infrastructure. Wikibooks uses categories in a very different way, using both manually arranged structures and lots of stuff automatically generated based on the arrangement of pages in five (or it is six) different namespaces. --Pi zero (talk) 21:49, 21 September 2014 (UTC)
At the Commons village pump I was told that Wikibase/Wikidata wouldn't replace categories but would complement them. (And even if replace, I think Wikibase/Wikidata would be capable of implementing all the pretty things that are done at various projects by hand.) I'm still querying for documentation (was expecting the folks here to enlighten me with the details, too). Gryllida 01:08, 22 September 2014 (UTC)
I'm not planning to make it a gadget, because JavaScript doesn't have a means of querying the DB directly. I already know - I already tried - that API is slow and it is inappropriate for this tool, were it to go recursively (and I currently think it needs to do that). Thought I'd try to have it be a tool on WM Labs (as they have a near-live replica of the wikimedia projects database there). Gryllida 01:08, 22 September 2014 (UTC)

Qualifiers for labels[edit]

Qualifiers for labels were discussed sometime ago but still not implemented. Obvious application is date based qualifiers for places which changed names over time.

Other useful application is for providing declension for nouns for languages (Russian, Belarusian, Ukrainian, Polish, etc) which use them. Labels provide only nominative case. But categories which could be deduced from data may require other cases. For example, categories by places (born in, died in, alumni of, etc) or by person (works of, translation by). MediaWiki use GRAMMAR for such purposes.

EugeneZelenko (talk) 13:54, 24 September 2014 (UTC)

Labels should not get qualifiers - Labels are used for identification and display, not as part of the knowledge about the entities. A "name" property (maybe Property:P1448 fulfills your requirements) on the other hand could have such qualifiers, and there it would make a lot of sense.
Regarding declension, this will be covered by the Wiktionary & Wikidata proposal (no matter how it will look like in detail), and will still take a while.
Just my two cents, --Denny (talk) 15:05, 24 September 2014 (UTC)
@Denny: official name (P1448) doesn't cover translations, it is only for names issued and supported by entity itself. And we need some field that will hold different names in different languages AND for different times. -- Vlsergey (talk) 15:09, 24 September 2014 (UTC)
I believe that categories shall be direct-linked to items like using category for people born here (P1464) and category for people died here (P1465) for places, not constructed on fly. For example, label can be changed at anytime and we will lost this category. But yes, we still need some way to get the "old name" of entity. Not sure shall be monolanguage or multilanguages field. -- Vlsergey (talk) 15:08, 24 September 2014 (UTC)
If official name or one of the other properties doesn't fit, yes, a new one should be made. @Vlsergey:, if you make a proposal let me know, and I will support it. --Denny (talk) 15:20, 24 September 2014 (UTC)
@Vlsergey: Same here, I would support a "name" or "natural language identifier" property with monolingual datatype to be used with qualifiers and with sources. A nice addition would be a bot to take the values of the statements using that property and to copy them as item labels too.--Micru (talk) 19:24, 24 September 2014 (UTC)
I don't think that it's good idea to create property for every something by place category (see en:Category:New York City with subcategories as example). --EugeneZelenko (talk) 13:49, 25 September 2014 (UTC)
Sorry Denny, I completely disagree. The use case is valid. Not showing the right label removes needed functionality from Wikidata. Thanks, GerardM (talk) 06:36, 2 October 2014 (UTC)

I'm not happy using labels, nor aliases, for former names. I was about to propose a "former names" property, when I saw this discussion. What do folks think about that option? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:48, 25 September 2014 (UTC)

May be I'm outdated :-), but do we have multiple language strings necessary for that? --EugeneZelenko (talk) 13:49, 25 September 2014 (UTC)
@Pigsonthewing: A "former name" is just a "name" that has an "end date". Therefore, a property "name" would be enough for cover all cases.--Micru (talk) 14:18, 25 September 2014 (UTC)
Andy I agree with Micru. Use the regular name properties with an end date. Make the current value the preferred value. Use qualifiers on each name to specify the given name, family name, prefix, suffix, language, start date, end date etc. for that name. Where an item has more than one official name (some cities have official names in more than one language) use additional values for that property. Create a new 'translation' property with multilingual datatype for informal/unofficial translations of that name. Filceolaire (talk) 22:53, 29 September 2014 (UTC)
See Wikidata:Property_proposal/Archive/16#name_.2F_name_.2F_nom_.2F_.D0.B8.D0.BC.D1.8F_.2F_in_wiktionary Filceolaire (talk) 22:56, 29 September 2014 (UTC)

Wikidata Auto Editors[edit]

Other than the Wikidata game which is currently down, what are some other auto edit tools I could use? Eurodyne (talk) 01:59, 25 September 2014 (UTC)

@Eurodyne: I know these three which also use WiDaR: Quick statements, AutoList (project page), AutoList2 (for the last two, study WDQ first). Matěj Suchánek (talk) 14:01, 25 September 2014 (UTC)
Thanks! The game is up and running again but I may use these in the future. Eurodyne (talk) 22:23, 25 September 2014 (UTC)

Good article label not automatically added to an article[edit]

Hello,

Recently, WikiData manages the "good article" labels by automatically put the image by the language links.

However, in this article, the portuguese "good article" label doesn't seem to be recognized. In the English version of the article, it is added manually ({{Link GA|pt}}), as it was in other languages. In the French version, I quit them (for wp:es and wp:pt), and only the Spanish one remains.

If you have a look on the WikiData page, you can see that there is indeed a label for the Spanish version, but none for the Portuguese one : is there any reason for that?

Thank you and best regards, --Daehan (talk) 08:48, 25 September 2014 (UTC)

PS: and sorry if I'm not clear: I don't use to work a lot on WikiData.

There's Portuguese label at Q1779837. Do you mean why the English article told "this is a good article in this language" when you put your mouse on the pt-wíki link? It was because there was still {{Link GA|pt}} in article text. I've now removed it from text and added the badge on Wikidata. Regards, --Stryn (talk) 16:06, 25 September 2014 (UTC)

Royal Society of Chemistry - Wikimedian in Residence[edit]

Hi folks,

I've just started work as w:Wikimedian in Residence at the w:Royal Society of Chemistry. Over the coming year, I'll be working with RSC staff and members, to help them to improve the coverage of chemistry-related topics in Wikipedia and sister projects.

You can keep track of progress at en:Wikipedia:GLAM/Royal Society of Chemistry, or use my talk page here if you have any questions or suggestions. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:58, 25 September 2014 (UTC)

Congratulations Andy, that's great news! Emw (talk) 12:54, 27 September 2014 (UTC)

Settlement's Claims[edit]

For:

1-en:Iran
2-en:Yazd Province
3-en:Ardakan County
4-en:Central District (Ardakan County)
5-en:Mohammadiyeh Rural District

Should I add all of these 5 level subdivisions to is in the administrative territorial entity (P131) or part of (P361)? and does it need to have separated property for each one? like country (P17), province ,....Yamaha5 (talk) 21:14, 25 September 2014 (UTC)

@Yamaha5: only add en:Mohammadiyeh Rural District. See Property talk:P131.--GZWDer (talk) 04:53, 26 September 2014 (UTC)

Request and proposal[edit]

German Dormitorium is here: Q1245527 and about the sleeping hall for monks.

I made at the engl. page Dormitory a notice where the Dormitorium comes from and a redirect from Dormitorium to Dormitory. And at the German version, that in English it has become a "Studentenwohnheim".

Studentenwohnheim ist hier: Q15635165

An error occurs: The link enwiki:Dormitory is already used by item Q847950. You may remove it from Q847950 if it does not belong there or merge the items if they are about the exact same topic.

Maybe somebody is smarter than me to merge them? Thanks and greeting --Palitzsch250 (talk) 14:18, 26 September 2014 (UTC)

You describe several notions, so merge isn't a solution. On Wikidata, a notion = an item.
We could do that in 4 items:
  • one, probably Dormitorium (Q1245527), for the monks dormitory (instance of the third), where you can link de:Dormitorium
  • one, probably invalid ID (Q15635165), for the students dormitory (instance of the third), where you can link de:Studentenwohnheim
  • one for the dormitory in general (subclass of the fourth), where you can link en:Dormitory
  • a last item for any place where we sleep (subclass of place, not room, to encompass outdoor places as well)
--Dereckson (talk) 14:49, 26 September 2014 (UTC)
There's also sleeping dormitory (Q3037266), large room with beds, only for sleeping, linked to fr:Dortoir. LaddΩ chat ;) 01:34, 27 September 2014 (UTC)

Crowdfunding information[edit]

Crowdfunding is an interesting 2010s fact. A lot of project use Internet crowdfunding platforms to get an initial capital and promote the product.

Do you think this is a pertinent fact to document on Wikidata? How to best express it?

Ash Crow suggests to use the significant event (P793). What are the best qualifiers?

I made three samples so we have a base for discussion:

Thank you to Okki for Star Citizen and Veronica Mars suggestion.

--Dereckson (talk) 14:43, 26 September 2014 (UTC)

User:ValterVB, how do you set numbers ± 0? --Dereckson (talk) 18:02, 27 September 2014 (UTC)
@Dereckson: Simply I have changed from "± 1" to "± 0". For a new number you must write "10 ± 0" --ValterVB (talk) 18:45, 27 September 2014 (UTC)
Thanks. --Dereckson (talk) 20:50, 27 September 2014 (UTC)

Wikidata IEG proposal: Tools for using wikidata items as citations[edit]

Hi all,

I've started this IEG draft on meta for a wikidata related IEG: Tools for using wikidata items as citations

I'm still looking for collaborators and it would be awesome if someone wanted to join up in a developer or community organiser role. Also, if you have a few minutes to read, comment, criticize, etc. that would be awesome! Mvolz (talk) 19:18, 26 September 2014 (UTC)

  • @Mvolz: just for your information w:ru:Module:Sources already can pull information from Wikidata and display it as citation. It is used to display citations for claims from Wikidata in infoboxes. The biggest issue is bugzilla:67538 -- you won't be able to display "deattached" descriptions (i.e. descriptions from separate entities_ unless you have "cached copy" of your entity (as LUA module for example). Another issue is social: "This hack could unify the citation structure" is more "contra" than "pro" according to some community members. -- Vlsergey (talk) 05:15, 27 September 2014 (UTC)
    • @Vlsergey: Thank you, I didn't know about that module! That's awesome! And also thank you for the bug link, I'd heard there were some difficulties with the current api but wasn't sure what they were exactly. Re: social, I am confused? Are you saying that some community members have seen that support comment and view it as a negative? If so they should comment! :). Mvolz (talk) 13:45, 27 September 2014 (UTC)
      • @Mvolz: no, community members didn't see this proposal/comment yet. But it is well known that some active community members are strictly oppose unification of articles, adding infoboxes, unification of sources and other "not-related-to-content-creation" business. Other active members would like to see their unique source descriptions (sometimes even with images, see Template:Ruheroes (Q12269760) for example), so they would be against unification as well. I'm not apologist of such points of view, but you shall be careful. -- Vlsergey (talk) 11:59, 28 September 2014 (UTC)

Can I get a list of entities with a specific property using just one call to /w/api.php?[edit]

I'm trying to find all the pages with a specific property and the property value for each entity. The best way I can figure out how to do this with the API is to use "/w/api.php?action=query&bltitle=Property:PPROPERTY&list=backlinks&blnamespace=0". I then either take batches of the resulting pages and running "/w/api.php?action=wbgetentities&ids=QENTITY|QENTITY|..&props=claims" or "/w/api.php?action=wbgetclaims&entity=QENTITY&property=PPROPERTY" one at a time.

Is there any way to get all the entities with a specific property and the property values in a single call (or multiple calls of the same type based on a query limit)? --Bskaggs (talk) 20:41, 26 September 2014 (UTC)

@Bskaggs: Use WDQ (API documentation), if you wish through the front-end Autolist or Autolist 2.
With WDQ it is easy to filter by a specified property (which may or may not be required to have a specified value, as you wish), and then to output the values of a given list of properties for that hit-set.
It should be just what you need. Jheald (talk) 22:14, 26 September 2014 (UTC)
@Jheald: Thanks for the pointers! The WDQ page mentions the data can be a few hours old; do you happen to know how much the lag is normally? --Bskaggs (talk) 17:59, 28 September 2014 (UTC)
@Bskaggs: Sorry, I don't know. The things I've used it for haven't been very time-critical. @Magnus Manske: would be the one who could say. Jheald (talk) 18:31, 28 September 2014 (UTC)

Wikidata proprietary number format[edit]

Discussed with parser ideas at ru-wiki Неизвестный тип снэка. If I understand properly Wikidata for some reason decided to not use numbers but its own proprietary string format:

  • Main value in the US notation with comma-separated groups like 1,500,000
  • Zero or more space(s)
  • ±
  • Zero or more spaces
  • precision part expressed either as a number or as a nn% percent value

First queston is — what in the name hey of it is that and who's that groundbreaker-genius?
The second question: is the new format described properly or are some more caveats missing?
As the change rendered a number of Wikipedia articles to the FOOBAR state with "unknown-snak-type" an extra parser is needed (or cancel using Wikidata whatsoever until some stabilization stage). Then are there some obligations at WD to keep this at least as it is right now? So it will not become say +/- instead of ± overnight. Some explanations would be highly appreciated. --NeoLexx (talk) 10:45, 27 September 2014 (UTC)
P.S. Needless to say that WDQ's QUANTITY filter is effectively killed as well by this "innovation", but OK for now, let's solve the basic functionaly issues first and ASAP. --NeoLexx (talk) 10:50, 27 September 2014 (UTC)

@Neolexx: Could some of your concerns answered in Wikidata:Development plan and Wikidata:Requests for comment/Dimensions and units for the quantity datatype. Tobias1984 (talk) 12:14, 27 September 2014 (UTC)
Hardly, as nowhere I see discussed numbers expressed in the US pretty-printing with commas (1,500 for one thousand five hundreds and so). Neither numbers expressed in the US pretty-printing with commas followed by ± sign followed by delta. At my best knowledge such number formats never existed at all in the programming since Mr. Turing time and until September of 2014 A.D. I am ready to stay corrected on that otherwise would anyone here (where invented) please tell me a sub to get numbers from WD rather than snaks errors? Whatever happens at WD is a private WD business, but foobared Wikipedia pages is a global project issue. I never did anything with mwLua (Javascript is just fine) yet I wrote a temporary parser-fixer. As an emergency help could anyone mwLua-savvy check it for functionality? --NeoLexx (talk) 12:57, 27 September 2014 (UTC)

Wikibase stores numbers. Works fine on frwiki: [1]. I think there’s an error on ruwiki. You don’t have to parse strings with Lua. --JulesWinnfield-hu (talk) 13:52, 27 September 2014 (UTC)

  • I am sorry, but no programming language on the Earth ever was or is able to recognize by default "numbers" such as 1,250±1 (Q286774) and the like. I fixed an emergency parser for the current "WD number format". Yet and sorry again but it is not a way of doing data bases, IMO. --NeoLexx (talk) 14:18, 27 September 2014 (UTC)
You don’t have to parse strings with Lua. See frwiki for example. Also works on huwiki. You do something wrong. --JulesWinnfield-hu (talk) 14:34, 27 September 2014 (UTC)
This was the problem: [2]. --JulesWinnfield-hu (talk) 14:41, 27 September 2014 (UTC)

Wiki Loves Monuments 2014 list items and merging[edit]

Whilst using the interactive map for Wiki Loves Monuments UK I noticed that the Wikidata item for Hampton Court Palace generated from English Heritage's list (Q17528007) could do with merging into the older Q205666, which I did. What I didn't realise was that another item from that list, "Walls And Railings To Hampton Court Palace", had already been merged into that item. This seems like a mistake; "Hampton Court Palace" would be a better fit for that item. My question is, should "Walls and Railings" be de-merged, or is it acceptable for both the Palace and its walls to have to have the same Wikidata item? Artifex (talk) 07:17, 28 September 2014 (UTC)

We have somelike discussion in Wikidata talk:WikiProject Cultural heritage The best would be to de-merge the "Walls and Railings" item and link it as as part of the Palace, or even beter, as a part of the estate (since [3] seem to be the estate entry). --Fralambert (talk) 12:12, 28 September 2014 (UTC)

is there a list of good wikidata items?[edit]

Are there pages that I can use as "role models"? items of all types that are more or less good examples of full usage of properties, qualifiers, references etc.? Thanks, DGtal (talk) 08:53, 28 September 2014 (UTC)

Have a look at Wikidata:Showcase items --Pasleim (talk) 09:02, 28 September 2014 (UTC)
Showcase answer! DGtal (talk) 09:43, 28 September 2014 (UTC)

Julian and Gregorian calendar UI - revisited[edit]

Revisiting the old chat threads like Calendar model: only display attribute or storage model?, stored to display time value conversion and Can't switch between julian and gregorian date.

The UI for dates is completely broken, even not counting that automatic calendar conversion is not working. There is no way to deduce that "Julian" and "Gregorian" attributes are related to display attributes - the natural assumption by any user is that you change the storage model of the attribute, ie. you either enter a Julian date or Gregorian date, or maybe both Julian date and Gregorian date. Nowhere it is hinted that the underlying storage model always assumes Proleptic Gregorian. The underlying storage model and the programming model seem to be badly documented too, as bot programmers have to seek forum advice to gain the understanding of dates and calendars.

This is further mitigated by the fact that the Russian Wikipedia initiated a massive WikiData upload of birth/death dates and the removal of said dates from the infoboxe templates, which now take WikiData dates into account when no explicit dates are provided to the template. The resulting error rate is close to 30-50% if you consider all Tsarist Russia articles.

Yesterday I had to correct at least dozen Russian Empire-related wikidata entries added by both bots and humans, and of course the two most common errors resulting from the unintuitive UI and badly written documentation are:

  1. Specifying Julian calendar dates instead of Gregorian dates, since the editors naturally think "Julian" means the storage model, not the display mode. So they think they enter a Julian date, when in fact they have entered a Gregorian date. This results in all dates being shifted 13-14 days forward in the infoboxes comparing to the text of the article.
  2. Providing two dates for the same attribute, as editors deduce they need to enter both "old style" and "new style", and again confuse "Julian" and "Gregorian" as storage attributes, not display attributes. This results in both dates being displayed in the infobox, as if the date is ambiguous - for example "Born: xx XXX[1] or yy YYY[2] 18nn"

Example edits by a confused user: [4] [5] This was the entry for Mikhail Lermontov, and the edit resulted in incorrect infobox dates being displayed for almost a month. I can only imagine the situation with other not-so famous entries which lack enough editor attention. It probably has become a complete mess that will have to be cleaned manually. --95.26.10.205 19:57, 28 September 2014 (UTC)

Support for mul language code[edit]

See here This is relevant for (e.g.) Q16503#sitelinks-wikisource. —Justin (koavf)TCM 08:20, 29 September 2014 (UTC)

Copyright and licensing of extracted facts[edit]

I'm trying to populate Stack Exchange tag (P1482) properly on as many entities as possible. As a first step, I want to seed the entity/tag links based on the Stack Overflow tag wikis on StackOveflow.com (example). From the May Stack Exchange data dump I have extracted a few thousand links to Wikipedia articles found in the Stack Overflow tag wikis. I've manually reviewed them to ensure an approximate one-to-one relationship between the tags and the Wikipedia articles. I'm very confident in the quality of the links, and now I want to add them to WikiData using User:StackerBot. However, now I'm concerned about licensing/copyright issues.

The Stack Exchange data in totality is CC-by-SA 3.0 licensed. WikiData is CC0/Public Domain. Would the nature of the extraction I've done (pulling out just the links to Wikipedia articles and converting them to WikiData entities) be transformative enough to permit me to use the fair use exemption to publish the derived data under the public domain suitable for use in WikiData? Or do I need to seek special permission from Stack Exchange? Or do I just have to fill this property out manually? (I've asked this question over on Meta.StackExchange, but haven't gotten an answer) --Bskaggs (talk) 13:12, 29 September 2014 (UTC)

StackOverflow is an US website. As there is no database sui generis right in United States, you don't have to worry about data extract.
Furthermore, there are precedents telling facts aren't copyrighted in the US: see for example Nester's Map 86 Guide Corp. v. Hagstrom Map Co., 796 F. Supp. 729, 733, 23 U.S.P.Q.2d 1749 (E.D.N.Y. 1992),
Finally, you don't do a mass copyrightdata extraction, you match StackOverflow tags and Wikidata items. This is a reference catalog work, not an extraction of the content of SO database.
--Dereckson (talk) 14:39, 29 September 2014 (UTC)
Is there an Help page explaining the licensing concepts applicable to WD, especially for massive import from other DB? Last time I checked, I couldn't find one.
On my side, I have been sitting on a csv file giving the full list of shares border with (P47) between French municipalities. I got that from the French OSM team a while ago, and when I checked the OSM license, it explicitely stated that data reuse had to be under the same license (here). So AFAICU, massive import to a CC0 license is not possible.
Any advice? --LBE (talk) 17:15, 29 September 2014 (UTC)
See here. Filceolaire (talk) 18:07, 29 September 2014 (UTC)
Is this a mandatory read & comply for anyone who gets a bot flag? Because as far as I can see, this puts a lot of the import work which is done here out of bounds.
I fixed my message below: I wanted to use the expression "mass data extraction". --Dereckson (talk) 09:38, 2 October 2014 (UTC)
LBE, in France, like in the others EU contries, you have a droit sui generis des bases de données, so you can't do mass extraction as long as the person doesn't relicense the data in CC0 or doesn't explicitly waive this intellectual property right (copyright isn't waivable in EU, but sui generis database right is).
In France, public agencies and organizations typically won't do it upon request, it must come from political decisions taken at ministry level. So you're stuck and should find another source to do that. --Dereckson (talk) 09:44, 2 October 2014 (UTC)

Wikinews interwiki[edit]

Guys (incl. JAn Dudík), so far i saw no summary neither consensus in the previous discussion about linking wikinews categories, so, please, asking you last time -- let the projects decide how they would work with wikidata. Do not move their categories links to wikipedia categories. Either you put other projects goals over your imaginary problems with bots or other projects would turn away from wikidata. It is very serious issue here, do we provide service to other projects like they need; or other projects like Wikinews would consider Wikidata as unfriendly project that they shall not go along with. -- Vlsergey (talk) 21:31, 29 September 2014 (UTC)

Properties to supply on-the-fly requests[edit]

Question for Lydia Pintscher or others better aware of upcoming development: how far are we from a capability to provide properties whose values would be obtained via on-the-fly requests to WD itself? Is it in the plans at all? I'm seeking something similar to arbitrary access, but that would be made available as normal properties on items, replacing or supplementing existing properties. LaddΩ chat ;) 02:39, 30 September 2014 (UTC)

I don't understand what it is you want exactly, sorry. Can you give an example please? --Lydia Pintscher (WMDE) (talk) 06:56, 30 September 2014 (UTC)
It start from a question I asked. Right now, a lot of informations are duplicated like the symetric properties : father/mother/son/daughter/brother/sister. So, would it be possible to ask to show on the son item the inverse property already indicated in the father item ? Cdlt, VIGNERON (talk) 07:33, 30 September 2014 (UTC)
I will have a team of students working on improving constraint violation reports starting in 2 weeks. Inverse properties is something they will be looking at. One thing I do know is that these properties will not be added automatically by the software. But we will have to make it easier. If you have ideas that you want me and the students to take into account please let me know. Once they started I plan to have a more formal page for idea collection. --Lydia Pintscher (WMDE) (talk) 09:04, 30 September 2014 (UTC)
@Lydia Pintscher (WMDE): Just a question: Will this feature be related to statements on properties? Matěj Suchánek (talk) 16:12, 30 September 2014 (UTC)
Yes it'll be build on top of it. Statements on properties are being worked on this sprint. We probably need another sprint or two to get it finished. --Lydia Pintscher (WMDE) (talk) 18:20, 30 September 2014 (UTC)

Wikidata for citations[edit]

I hope nobody has posted this yet, but there is still a lack in response to the proposal to use Wikidata items to store the citations for Wikipedia:

https://meta.wikimedia.org/wiki/Grants:IdeaLab/Tools_for_using_wikidata_items_as_citations#Endorsements

-Tobias1984 (talk) 07:11, 30 September 2014 (UTC)

#Wikidata IEG proposal: Tools for using wikidata items as citations. ;) --Succu (talk) 08:17, 30 September 2014 (UTC)

How to propose a new language within Wikidata[edit]

As far as I know the preconditions to add a language to Wikidata are much lower than to add a new Wikimedia project in such a language - as far as I know a ISO language code is already enough. However it seems there is no place where to ask for a new language - several months ago I tried to ask for Northern Thai language (Q565110) (ISO code nod) at Meta:Talk:Language committee which was ignored and later archived by a bot, another user tried to ask for Cape Verdean creole (Q35963) at Meta:Requests for new languages/Wikidata Cape Verdean Creole with effectively the same result. Is there any established place to propose languages for Wikidata? Does it really have to go through the long bureaucratic language committee process, though IIRC there already was a decision that every language is eligible for Wikidata. Ahoerstemeier (talk) 12:55, 30 September 2014 (UTC)

User:GerardM had proposed some months ago in the Language Committee that all languages with an ISO 639-3 code should be made eligible for Wikidata. It was agreed upon; and I had thought he would have taken the necessary steps? --MF-W 14:19, 30 September 2014 (UTC)
@Ahoerstemeier: Go to Wikidata:Contact_the_development_team or contact Lydia Pintscher (WMDE). Snipre (talk) 15:22, 30 September 2014 (UTC)
Yeah. The easiest way is to file a bug on bugs.wikimedia.org and then get someone from the language committee like Gerard to ok it there. --Lydia Pintscher (WMDE) (talk) 14:21, 1 October 2014 (UTC)

How to list new company ?[edit]

Many of the people thinks wiki and google r reliable source of legal informations

Sorry, but Wikidata is not an advertizing space. --Jakob (talk) 22:40, 30 September 2014 (UTC)

Too hard to cancel an edit now...[edit]

E.g. Template:@ (Q6133158), I've tried adding q:zh:Template:@, yup it's not exist, then clicked "cancel", I've waited for several minutes (and drank a cup of coffee), it's still "canceling"?! --Liuxinyu970226 (talk) 00:11, 1 October 2014 (UTC)

hhmm.. it takes some extra clicks to add an interwiki or edit a label today. Why? Michiel1972 (talk) 08:52, 1 October 2014 (UTC)
Aparently, a new interface, but adding extra clicks was possibly not a good idea--Ymblanter (talk) 10:07, 1 October 2014 (UTC)
Yea that is part of the move to the new interface. It is still being changed and we really have to fix the part where you have to scroll considerably more than before. --Lydia Pintscher (WMDE) (talk) 14:18, 1 October 2014 (UTC)
Just in case you still didn't notice, the "move" link for linked Wikipedia pages don't work.--Pere prlpz (talk) 18:25, 1 October 2014 (UTC)
Pere prlpz: Its a gadget, so see #problem with tools... --Succu (talk) 18:31, 1 October 2014 (UTC)

problem with tools...[edit]

Since yesterday I've had problems with some tools interface...

For example, now Wikidata usefuls displays in the bottom-left of the item (not the screen), and I have to drag and drop it back in top-right for every item, which is not really convenient...

I checked, there has been no change on this script since 8th of september, so I guess it's something with a general update or modif of GUI.

Is it possible to fix it, please ? --Hsarrazin (talk) 12:43, 1 October 2014 (UTC)

I have been noticing this problem as well, so...confirmed problem. I have also noticed that some userscript has stopped working, such as the WEF: Person (however the WEF: Links still works... :/ ) (tJosve05a (c) 13:11, 1 October 2014 (UTC)
Yeah sorry. A few things changed in the UI as part of the move to the new UI. That probably broke some of the gadgets relying on them :( If you need help fixing any of them let me know please. --Lydia Pintscher (WMDE) (talk) 14:20, 1 October 2014 (UTC)

Title[edit]

New Property title (monolingual text) (P1476) has been created to replace title (string) (P357). I want to change the labels on these properties to indicate that P357 is deprecated but I can't edit the property labels. Is there some new permission I need to edit property labels? where can I go to get this user right? Filceolaire (talk) 15:09, 1 October 2014 (UTC)

It's a bug, not a new user right. see Wikidata:Contact_the_development_team#Empty_labels_and_descriptions --Pasleim (talk) 15:24, 1 October 2014 (UTC)
Are you sure it was P2476? The page doesn't work for me. --Stryn (talk) 15:13, 2 October 2014 (UTC)

Creating tables with Wikidata - Directory of politicians[edit]

Dear all,

I am quite new in the wiki's world but I would like to develop a project that bring together the public contact details of all the politicians (address, email, Facebook, Twitter, etc).

The idea would be to have a table that could be updated by the community and readable both by humans and computers (if you want to do an extract or so) and liked to an external website. I already extracted the data from the European Parliament website and it looks like: First name / Last name / Position / Nationality / Party / Email / Address / Social networks / Assistants / Committees

And I wondering if Wikidata would be the best place do so? Can we create tables in or with Wikidata? Because as far as I understood, an item is only a label and a single description. But as indicated above I need a label and several fields.

And Wikidata doesn’t suit for the purpose, which Wiki project is the most appropriated?

Thanks and cheers.

Antonin

Most of that data would be great to have on Wikidata, perhaps with the exception of email addresses. Wikidata items have much more than just labels and descriptions. Please take a look at this item, for an example: Barack Obama (Q76). Plenty of data can be included on politicians, in the "Statements" section. --Yair rand (talk) 16:13, 1 October 2014 (UTC)
Once the data is entered as statements on each politicians item it can then be extracted into a table using a query. Except that the tool to create a table using a query is a part that is still being developed and is not available yet. It will come - there are too many ways it will be useful for it to be left for long. Once the data is in wikidata it can also be imported into infoboxes on all the wikipedia pages for that politician. Tools are being developed which will let people edit the info from the wikipedia page which should help keep the info up to date. Filceolaire (talk) 17:51, 1 October 2014 (UTC)
Thank you all for your answers and the guidance. I guess I didn’t knew all the possibilities of Wikidata and I’m glad it is feasible as it definitely looks the right tool to do it.
Is that possible to add directly data from a table to Wikidata? Because I have around 20000 entries (just for the European Parliament) and that would be too long to do it manually.
Where should I ask for help from the wiki community? Because that will be great to have a some people interested by the project and who could help me 1/to organize the data in the right way and 2/to include them into Wikidata.
About the extraction, I already talk previously with someone from Wikimedia and he told me that once we will have the data and the project, we might ask to develop new tools play with the data. (And about the email, it is the public email from the website so it shouldn’t be an issue I hope)
Thanks you again. --Pixelimpact (talk) 14:29, 2 October 2014 (UTC)

Area served by a radio station[edit]

Is there an existing property that can be used to identify the area served by a radio station? We have place served by airport (P931) for airports and primary destinations (P1302) for roads but I couldn't find anything for radio stations/TV stations/Satellite TV stations. Filceolaire (talk) 18:09, 1 October 2014 (UTC)

@Filceolaire: I would say this one: licensed to broadcast to (P1408).--Micru (talk) 15:57, 2 October 2014 (UTC)

How to deal with translations of creative works?[edit]

I have a creative work originaly witten in one language and later translated into other languages. Sometimes the new version justifies a seperate item, e.g. all major Translations and editions of the Bible. In many cases it's no more than a standard novel, play or song translated within a few years into another language without any major differences from the source, someting that a wikipedia in any language would just mention in the parent erticle and not create a seperate article for. The question is do I just add the language name under language (P407) or can should I add qualifers for ISBN, translator, publisher, date etc. like I did in The Informationist (Q7742011) or is this an "overkill"? DGtal (talk) 11:09, 2 October 2014 (UTC)

  • There two different questions: how to handle translations and how to handle interwiki to that translations. From my point of view any translation should be separate item, either book translation or movie translation. In addition, there are translations and publications. Each publication would need a separate item as well, if multiple publications exists (but you can use single item as long as only single publication per language exists, as per most of movies). Using single item for all translations and original item will create a mess in data and it would be very hard to manage them. And even if some would like to have several translations in the same item, it should be not like language[property], but claim[language] structure. -- Vlsergey (talk) 11:48, 2 October 2014 (UTC)
    Part of the question is what good comes out of a seperate item for a book translation if the interwiki is on the original item. You get an item with no articles linked. DGtal (talk) 12:17, 2 October 2014 (UTC)
    Well, you need some kind of agreement either to link all Wikipedia article to original item or somehow fetch interwiki from original item and it's translations. -- Vlsergey (talk) 13:21, 2 October 2014 (UTC)
@DGtal: See Help:Sources Snipre (talk) 13:09, 2 October 2014 (UTC)

Help needed[edit]

I am unable to link any pages to wikidata since yesterday. Cannot see the "add" button on "any" pages. Please help.--Kanags (talk) 11:15, 2 October 2014 (UTC)

New interface - save button inactive after an alert has been displayed[edit]

I was unscrambling Wikipedia links between Q1642648 and Q2976556, moving a number of links from the first item to the second. As the move gadget isn't available any more, for each wikilink I manually delete it from its former item and add a new line in the new item. At some point, I hit Enter while editing the new item, which correctly displays a conflict alert as I have not yet saved my edits (removals) on the old item, so far so good.

Problem is, after I dutifully save my removals from the old item, there is no way to save the new item. The save link is blue, but after clicking it the Wikipedia section remains grey and is never saved. Even more of a problem, when I tried to open the unsaved page in a new tab and add all links again from scratch, the unsaved links in the "frozen" tab are visible but cannot be selected and copy/pasted, which is problematic when they are in alphabets I can't type such as Hebrew or Chinese.

Do you see any way to fix that? (I am a Wikidata administrator and my display language is French, it this makes any difference.) Copied at Paper cuts Place Clichy (talk) 13:22, 2 October 2014 (UTC)

I'm not administrator and my display language is Catalan, but I'm experiencing the same issue, so status and language don't seem to make any difference.--Pere prlpz (talk) 14:57, 2 October 2014 (UTC)