Reminder: Technical Advice IRC meeting again **Wednesday 3-4 pm UTC** on
#wikimedia-tech.
Question can be asked in English, German, Hungarian.
The Technical Advice IRC Meeting (TAIM) is a weekly support event for
volunteer developers. Every Wednesday, two full-time developers are
available to help you with all your questions about Mediawiki, gadgets,
tools and more! This can be anything from "how to get started" over "who
would be the best contact for X" to specific questions on your project.
If you know already what you would like to discuss or ask, please add your
topic to the next meeting:
https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting
Hope to see you there!
Michi (for the Technical Advice IRC Meeting crew)
--
Michael F. Schönitzer
Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
http://wikimedia.de
Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen
Wissens frei teilhaben kann. Helfen Sie uns dabei!
http://spenden.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.
I have a tool I wrote to do this with properties and items. See:
https://github.com/stuppie/wikibase-tools
It creates the properties or items in your local wikibase with the same
label, description, and aliases as it exists in Wikidata (but of course,
with different Q/P ID). It then adds a "equivalent property" or "equivalent
class" statement to the newly created item with a URI back to the Wikidata
item/property. This allows sparql query federation for use of these items
in your wikibase with the associated Wikidata statements (available through
federation).
I've tested it locally and hosted on AWS and the data federation works
fine. LMK if this is what you had in mind..
-Greg
Dear Mr. or Ms.;
I thank you for your efforts. I tried to add the following statement using QuickStatements
Q18557565 P5642 Q662860 P1542 Q217690 S698 27125965.
The statement is added. However, the PubMed ID of the reference was not added. I ask if this matter can be fixed.
Yours Sincerely,
Houcemeddine Turki
Reminder: Technical Advice IRC meeting again **Wednesday 3-4 pm UTC** on
#wikimedia-tech.
Question can be asked in English, German, Persian.
The Technical Advice IRC Meeting (TAIM) is a weekly support event for
volunteer developers. Every Wednesday, two full-time developers are
available to help you with all your questions about Mediawiki, gadgets,
tools and more! This can be anything from "how to get started" over "who
would be the best contact for X" to specific questions on your project.
If you know already what you would like to discuss or ask, please add your
topic to the next meeting:
https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting
Hope to see you there!
Michi (for the Technical Advice IRC Meeting crew)
--
Michael F. Schönitzer
Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
http://wikimedia.de
Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen
Wissens frei teilhaben kann. Helfen Sie uns dabei!
http://spenden.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.
Hi:
How can I control the form of CONSTRUCT results from the wikidata query
service?
On the web interface I can get the results in various formats (but not
something that can be read into SPARQL, I don't think). Using curl all I get
is XML/RDF.
What I really want is n-triples so that I can concatenate several results, but
Turtle would be better than RDF/XML.
peter
Dear Mr. or Ms.,
I thank you for your efforts. We are beginning a new project to enrich Wikidata with high-scale information about the risk factors of diseases. If you are interesting in the project, you can join the discussion within two hours in Skype at 3PM UTC about the project and the PubMed-based method of the automatic enrichment of Wikidata we will use. My account is csisc1994. Just to know if there will be participants to this RiskData second meeting, please confirm your participation by answering this email.
Yours Sincerely,
Houcemeddine Turki
Dear Mr. or Ms.,
I thank you for your efforts. Due to the lack of participants, the Skype meeting was reported to 3PM GMT http://www.timebie.com/std/gmt.php?q=15. The meeting is about converting Wikidata into a high-scale database of risk factors of diseases. You can discover our method of enriching Wikidata from PubMed with medical knowledge. My account is csisc1994.
Yours Sincerely,
Houcemeddine Turki
3:00 PM 15:00 GMT to Local Time Conversion -- TimeBie<http://www.timebie.com/std/gmt.php?q=15>
3 PM ( 15:00 ) Greenwich Mean Time to Your Local Time and Worldwide Time Conversions
www.timebie.com
Has anyone imported a subset of Wikidata into another Wikibase? How
did you do it?
I am working a project which wants to import Wikidata properties into
their Wikibase. I looked into how to do this, but I am hitting
roadblocks.
1) Fetching data
This part is easy, can do it via the API or dumps. If I only take
labels and descriptions and datatypes, then I don't even need to worry
about fetching any items referenced in the properties' properties.
2) Importing data
It's possible to create properties via api.php?action=wbeditentity,
but it does not allow specifying the id for new entities. We would
like to keep the ids same as in Wikidata for simplicity. I thought
that I would just create all properties up to P6000 or so, edit them
via the api, and then delete the unused properties. However, this
won't work because the property datatype must be specified at creation
time and cannot be changed afterwards.
Possible solutions:
a) Make it possible to specify the id of newly created entity (likely
guarded with a special right).
b) Make it possible to change property datatype after creation.
c) Drop the requirement of using the same ids in our wikibase.
d) Use a MediaWiki maintenance script where it is possible to bypass
restrictions and specify the id of the newly created entity.
Afterwards database must be updated manually to increase the tracker
for next free entity number to match the highest used id.
e) Avoid having to import properties (e.g. wait for support for
federated wikibases, implement an another storage mechanism that only
refers to Wikidata ids without having them in place.)
I am currently dreaming of (a) and probably going for (d) for which I
already have a rudimentary script. Any comments, suggestions or tips?
-Niklas