On Tue, Apr 2, 2013 at 9:54 PM, Denny Vrandečić <
[email protected]> wrote:

> Hi Janyong,
>
> as Michael said, Wikidata does not automatically get updated in any case.
> We are planning to improve a bit the experience with moving a page in the
> Wikipedias, but it won't become automatic. Mostly because these issues are
> in general complicated.
>
>
> 2013/4/1 Jianyong Zhang <[email protected]>
>
>> Hi,
>>
>> Wikidata is a very useful effort. It seems associating an item with a
>> wikipedia article. Then I'm thinking the following scenarios to understand
>> it further:
>>
>> Say, an article is associated with an item Qx.
>>
>> 1)  It becomes redirect to another article, will Qx be changed in this
>> scenario?
>>
>>
> I expect that if a Wikipedia article gets moved, this will be updated on
> the Wikidata item manually. Otherwise the language links that were
> displayed on the original article would not show up.
>
> If an article gets turned into a redirect to an already existing article,
> this would be a merge (see Question 4).
>
>


Thanks for the detailed reply. I still have some question on redirect. See,
if the article A redirects to the article B, will we have 2 items or only
one for the final targets and all its redirects?

>From my point of view, if a redirect talks about same topic as its final
target, then it makes sense to only have 1 item. Such as,
http://en.wikipedia.org/wiki/Obama and http://en.wikipedia.org/wiki/Obamaand
http://en.wikipedia.org/wiki/Barack_Obama.

But in many cases, a redirect talks about a related but different topic
with its final target. Such as, http://en.wikipedia.org/wiki/Social_activistand
http://en.wikipedia.org/wiki/Activism.
how will wikidata handle such redirects?

And back to the original question, if an article becomes a redirect, for
the above 2 different scenarios,what will we do?


>
>
>> 2) It is deleted. Will Qx be also deleted?
>>
>>
> In some cases. If all articles in all languages of an item got deleted,
> than it might mean that the item itself should be deleted too, but this is
> not necessarily the case.
>
>
>
>> 3) That article is split as 2 new articles, how will we generate items
>> for them?
>>
>>
> It depends. Let us assume there was one article "Castor and Pollux". Now
> it gets split into two articles, "Castor" and "Pollux". In this case we
> would probably have three items in Wikidata: one for Castor, one for
> Pollux, and one for the pair of them.
>
>
>
>> 4) Or multiple articles are merged as one, how will their items be
>> changed?
>>
>>
> The same. There *might* be items for the individuals as well as for the
> compound. Not all Wikipedias might slice the world equally. How a merge
> really is handled, depends on what the corresponding articles and items are
> about.
>


>
> The good news is that these cases actually got a lot simpler than they
> used to be: they happened previously as well, but in that case you had to
> struggle with an ecosystem of bots who might revert your edits that were
> trying to clean up the interwiki links. Now it is all in Wikidata, and the
> situations should be easier to resolve.
>
> Just my two cents on these questions,
> Cheers,
> Denny
>
>
>
>> _______________________________________________
>> Wikidata-l mailing list
>> [email protected]
>> https://lists.wikimedia.org/mailman/listinfo/wikidata-l
>>
>>
>
>
> --
> Project director Wikidata
> Wikimedia Deutschland e.V. | Obentrautstr. 72 | 10963 Berlin
> Tel. +49-30-219 158 26-0 | http://wikimedia.de
>
> Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
> Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
> der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
> Körperschaften I Berlin, Steuernummer 27/681/51985.
>
> _______________________________________________
> Wikidata-l mailing list
> [email protected]
> https://lists.wikimedia.org/mailman/listinfo/wikidata-l
>
>
_______________________________________________
Wikidata-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikidata-l

Reply via email to