There are 3 columns in the sitelink section: "Language", "Code" and "Linked
page". Usually "language-code" and "wiki-code" have a permanent 1:1
correspondence , but not in all projects (incubator, meta, wikidata).
Would it be possible to add a configuration option so that for wikis that
host several languages the "language code" is also requested?
In this case it would be better to change the column order to "wiki code",
"language" and "linked page", that way the users would enter first the
wiki-code and then if that wiki has the multiple language configuration
enabled, it would request the language code as well.
For wikis that have pages translated into multiple languages (meta,
wikidata) the code "mul" can be used.
Thanks
Micru
Hey folks :)
We have quite a lot of changes lined up that are going to be deployed
soon. Here's an overview of what's coming up. I hope we can stick to
this but if there are any unforeseen issues we might have to delay
some of it.
== Tuesday August 19th ==
* Wikinews will be able to manage its sitelinks via Wikidata
* Wikidata will become its own client. This means you can for example
add a sitelink to Wikidata:Help to the item for all main help pages.
You will also be able to make use of the data in items on other pages
in Wikidata with lua. (Arbitrary access will be enabled for Wikidata
for this but when data in an item changes we will not be able to purge
the page using the data yet.)
* Sitelinks for projects with just one sitelink in the group (like
Commons, Wikidata and in the future Meta for example) will be grouped
together in one sitelink group.
* Badges for good and featured articles can be stored on Wikidata
right next to the sitelink. In a later roll-out we will make it
possible to show them on the Wikipiedias and sister projects in the
sidebar too. We will start with badges for featured and good articles.
More can be added on request later. Thanks to Bene* and lazowik for
this feature. I will send another email about this.
* Redirects between items will be possible. When two items are merged
one of them can then be turned into a redirect. This way our
identifiers can be considered much more stable by 3rd parties for
example. It will also make it unnecessary to delete duplicate items.
This will hopefully reduce the workload of our admins considerably.
For now redirects can only be created via the API.
* We are introducing the new datatype monolingual text. This will
allow you to make statements with a string and an associated language.
Please go and test these on test.wikidata.org and let me know if there
are any issues.
== Tuesday August 26th ==
* The entity suggester will be able to suggest properties in
qualifiers and references as well.
* BREAKING CHANGE: We'll switch the internal serialization format to
be the same as the one that is returned by the API. The xml dumps will
also be adjusted then. If your tool relies on either the dumps or the
internal serialization of an item page then it will likely need to be
adjusted. I will send a separate email about that. (This is one of the
remaining blockers for statements on properties and further progress
on Commons support.)
* We'll deploy the "in other projects" sidebar as a beta feature to
Wikipedia, Wikisource and Wikiquote. This way you will see links in
the sidebar of Wikipedia for example linking to Commons, Wikivoyage,
Wikisource and so on. This can be configured per-wiki. Thanks to Tpt
for this feature. (Wikipedias will get this 2 days later.)
* We will make it possible to show badges from Wikidata in the sidebar
on Wikipedia and co.
Cheers
Lydia
--
Lydia Pintscher - http://about.me/lydia.pintscher
Product Manager for Wikidata
Wikimedia Deutschland e.V.
Tempelhofer Ufer 23-24
10963 Berlin
www.wikimedia.de
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg
unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das
Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985.
Hey folks :)
We'll be rolling out a new beta feature on August 26th/28th to
Wikipedia, Wikisource and Wikiquote. It will add a new section to the
sidebar of an article. This section will contain links to related
articles in other sister projects. Which projects are shown can be
configured per-wiki. You can find out more about it at
https://www.mediawiki.org/wiki/Beta_Features/Other_projects_sidebar
If you have any questions about this please use the discussion page of
https://www.mediawiki.org/wiki/Beta_Features/Other_projects_sidebar
Cheers
Lydia
--
Lydia Pintscher - http://about.me/lydia.pintscher
Product Manager for Wikidata
Wikimedia Deutschland e.V.
Tempelhofer Ufer 23-24
10963 Berlin
www.wikimedia.de
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg
unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das
Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985.
Hi,
I just changed the Russian label of the Chelsea Manning item from Bradley
to Chelsea. The Russian Wikipedia article was already moved to Chelsea, but
nobody noticed that the label probably needs a change, too.
How can such things be handled better?
One thing I can think of is that after the Wikipedia article in language X
is moved, the label in language X is shown as "possibly needs update" -
similarly to FUZZY in the Translate extension. There can also be a button
that says "confirm current label", for when there is no reason to change
it. Finally, there could also be a page that lists such possibly labels.
Of course, there may be better ideas, and maybe some of them are already
implemented and I just didn't notice it.
--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
“We're living in pieces,
I want to live in peace.” – T. Moore
Hi Marco,
Thanks for getting in touch. Looking at the list there seems to be many
wrong mappings.
Is there any way that we can collaborate to increase the number of matches
or does it have to do with qualifiers? And do you plan to document 1:1
matches on your OntologyProperty namespace?
Thanks and regards,
Micru
On Wed, Aug 13, 2014 at 12:55 PM, Marco Fossati <hell.j.fox(a)gmail.com>
wrote:
> Hi everyone,
>
> The following spreadsheet contains the latest DBpedia <-> Wikidata mapping
> effort both for properties and classes (cf. the 2 sheets) made by the GSoC
> student so far.
>
> https://docs.google.com/spreadsheets/d/18W9xb5KXorotJ7qM58AsqK-
> myAHEjiDgnZrqNXHEnwk/edit#gid=716082733
>
> Since I am his main mentor, feel free to ask me further details.
> Hope this helps!
>
> Cheers,
>
> Marco
>
>
> On 8/13/14, 9:14 AM, David Cuenca wrote:
>
>>
>> On Wed, Aug 13, 2014 at 12:55 AM, Daniel Kinzler
>> <daniel.kinzler(a)wikimedia.de <mailto:daniel.kinzler@wikimedia.de>> wrote:
>>
>> I think it would be cool to use http://mappings.dbpedia.org/ - it
>> already has
>> mappings for hundreds of templates in different language versions to
>> the dbpedia
>> vocabulary. If we added a mapping for wikidata <-> dbpedia, it
>> should be easy
>> enough to derive a mapping between a wikipedia template and
>> wikidata. Actually,
>> I was under the impression the wikidata <-> dbpedia already existed,
>> but I don't
>> see it on the site right now. Adding Anja Jentzsch, she might know.
>>
>> Even if it proves too tricky to map individual template parameters
>> this way, it
>> should still be possible to at least detect the class (instanceof)
>> of an item
>> based on the templates the respective wikipedia page contains. We
>> should
>> definitely map dpedia classes to wikidata items.
>>
>>
>> Sergey Skovorodkin is working on a dbpedia<->wikidata mapping as a GsoC
>> for DBpedia this year
>> https://github.com/dbpedia/extraction-framework/wiki/
>> GSoC-2014-Progress-Sergey-Skovorodkin
>>
>> I'm CCing him to see if he can report the status or if he might need
>> help with our properties, maybe we are missing some or need to clarify
>> some others. Sometimes we are using qualifiers to extend properties
>> instead of creating new ones.
>>
>> Cheers,
>> Micru
>>
>
> --
> Marco Fossati
> http://about.me/marco.fossati
> Twitter: @hjfocs
> Skype: hell_j
>
--
Etiamsi omnes, ego non
Hey everyone,
After wikimania, I decided to contribute to wikipedia in my capacity. The
first thing I did was to check out my home town in wiki data, which is Zara
Turkey.
I used the search box, and found that Zara is not listed there. So I used
the option "containing Zara" which did help me find the right entry.
By the way, I see a tremendous impact of automatically generating
descriptions, which is what was proposed by the gentlemen next to me in our
outdoors meeting in wikimania. There were 4 Zara entries with no
descriptions making it difficult for me to find the correct entry.
In my opinion, I think manual descriptions should be kept, as opposed to be
deleted completely. Instead, automatically generated descriptions should be
provided when there is no manual description and people should be asked to
override automatically generated descriptions. In other words, provide a
default one and let people change it, if for some reason it is not good
enough.
https://www.wikidata.org/wiki/Q147630
I realized that, it is labeled as "Zara, Turkey" and not Zara.
This seem wrong to me, since "Turkey" part of this label is already in the
data as a country relation.
It appears to be a one-to-one mapping of the wikipedia article's title.
Maybe when first imported from wikipedia, its title is used as is.
I want to verify my understanding that labels of entities should be as
short as possible and should not attempt to disambiguate as it has to be
done in wikipedia article titles.
Thanks
I would like to contribute data to Wikidata that is in the form of CSV files,
geospatial shapefiles, etc.
Is there currently, or planned, functionality to store general structured data
on Wikidata?
--
Brylie Christopher Oxley
http://gnumedia.org