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.
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
Hello all,
We started integrating the constraint violations into the Query Service.
That means you can build queries using the constraint violations, with the
predicate wikibase:hasViolationForConstraint. This will hopefully help you
to watch better the quality of Wikidata content.
Please note that this is a first step. Not all constraint violations are
exposed yet, only the ones that can be checked fast enough. We're working
on having more available in WDQS.
You can base your queries on these few examples:
#10 statements with constraint violations that are currently
includedSELECT * WHERE {?x wikibase:hasViolationForConstraint ?y.}
LIMIT 10
Try it!
<https://query.wikidata.org/#%2310%20statements%20with%20constraint%20violat…>
#Map/timeline/image grid of items that have a statement with a
constraint violation#defaultView:MapSELECT DISTINCT ?item ?itemLabel
?image ?coordinate_location ?point_in_time ?date_of_birth WHERE {
?s wikibase:hasViolationForConstraint ?y.
?item ?z1 ?s.
SERVICE wikibase:label { bd:serviceParam wikibase:language
"[AUTO_LANGUAGE],en". }
OPTIONAL { ?item wdt:P18 ?image. }
OPTIONAL { ?item wdt:P625 ?coordinate_location. }
OPTIONAL { ?item wdt:P585 ?point_in_time. }
OPTIONAL { ?item wdt:P569 ?date_of_birth. }}
Try it!
<https://query.wikidata.org/#%23Map%2Ftimeline%2Fimage%20grid%20of%20items%2…>
#Bar chart of statements that have a constraint violation, grouped by
instance of the regarding item:#defaultView:BarChart#TEMPLATE={
"template": { "en": "Bar chart of statements that have a constraint
violation grouped by ?property the regarding item" }, "variables": {
"?property": { "query":"SELECT ?id WHERE { VALUES ?id { wd:P31
wd:P17 wd:P571 wd:P361 wd:P19 } }" } } }SELECT ?instance_ofLabel
(COUNT(?instance_ofLabel) AS ?count) WHERE {
?s wikibase:hasViolationForConstraint ?y.
?item ?z1 ?s.
BIND(wdt:P31 AS ?property)
SERVICE wikibase:label { bd:serviceParam wikibase:language
"[AUTO_LANGUAGE],en". }
OPTIONAL { ?item ?property ?instance_of. }}GROUP BY
?instance_ofLabelORDER BY DESC(?count)LIMIT 30
Try it!
<https://query.wikidata.org/#%23Bar%20chart%20of%20statements%20that%20have%…>
The modules included on the property talk pages, Module:Constraints
<https://www.wikidata.org/wiki/Module:Constraints>,
Module:Constraints/SPARQL
<https://www.wikidata.org/wiki/Module:Constraints/SPARQL> etc. has been
updated with a new query link (thanks Matěj!)
See also:
- the adding to the ontology
<https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/Wikibase/+/449329/1…>
- the Phabricator ticket <https://phabricator.wikimedia.org/T192567>, if
you have any issue to report
If you have any question, feel free to ping me.
--
Léa Lacroix
Project Manager Community Communication 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/029/42207.
Dear Mr. or Ms.,
I thank you for your efforts. As risk factor Wikidata property is added to Wikidata yesterday night, we will use it to enrich Wikidata with the risk factors of diseases using an automatic method of bibliometric-enhanced retrieval of biomedical relations. As we would like to have your opinions about this automatic method, we invite you for a Skype discussion tomorrow at 11 AM (GMT). For those who would like to participate to this meeting, please reply to this email and confirm your participation. I will send you my Skype username.
Yours Sincerely,
Houcemeddine Turki
Dear Mr. or Ms.,
I thank you for your answer. I thank you as well for your interest in my research work. For those who cannot attend the meeting in 11AM GMT, they can attend a second meeting in 3PM GMT. If you would like to participate to the second meeting, please just inform me about that and I will send you my username.
Yours Sincerely,
Houcemeddine Turki
________________________________
De : Wikimedia-Medicine <wikimedia-medicine-bounces(a)lists.wikimedia.org> de la part de Scott MacLeod <sgkmacleod(a)worlduniversityandschool.org>
Envoyé : vendredi 17 août 2018 18:12
À : Wiki Medicine discussion
Cc : Wikidata technical discussion; Discussion list for the Wikidata project.; wiki-research-l(a)lists.wikimedia.org
Objet : Re: [Wiki-Medicine] Invitation to discuss RiskData:, Wikidata as a high-scale database of risk factors for human diseases
Hi Nancy, Houcemeddine, Wiki Medicine and Wikimedians,
Thanks for your emails.
I thought that you had written 11am PDT and not 11am GMT on Saturday, August 18th, Houcemeddine, so unfortunately I can NOT make this time (http://www.thetimezoneconverter.com/). Please keep me posted if you decide to meet again at a different time. Thank you.
Sincerely, Scott
Scott_WUaS
Dear Mr. Houcemeddine Turki, WikiMedicine, Wikidatans (and Wikimedians),
I would like to participate in this Skype conference (and with regard too to WUaS's planned online medical schools, with online teaching hospitals for online clinical care - planned in each of all ~200 countries' official and main languages). Please send me your Skype username off-list. Thank you, Houcemeddine.
...
Here's the beginning online Medical School at WUaS in English - https://wiki.worlduniversityandschool.org/wiki/World_University_Medical_Sch… - which will connect with Wikidata as its "backend" eventually. And WUaS also seeks to emerge out of Stanford Medicine and with OpenCourseWare in multiple languages for our medical schools.
Sincerely, Scott
Scott_WUaS
On Fri, Aug 17, 2018 at 9:56 AM, Nancy Gertrudiz <nancy.gertrudiz(a)gmail.com<mailto:nancy.gertrudiz@gmail.com>> wrote:
I am interested. my skype user ngertrudiz.
Just confirm, tomorrow 17 Aug, 11 AM GTM?
Best,
2018-08-17 10:26 GMT-05:00 Houcemeddine A. Turki <turkiabdelwaheb(a)hotmail.fr<mailto:turkiabdelwaheb@hotmail.fr>>:
Dear Mr. or Ms.,
I thank you for your efforts. As risk factor Wikidata property is added to Wikidata yesterday night, we will use it to enrich Wikidata with the risk factors of diseases using an automatic method of bibliometric-enhanced retrieval of biomedical relations. As we would like to have your opinions about this automatic method, we invite you for a Skype discussion tomorrow at 11 AM (GMT). For those who would like to participate to this meeting, please reply to this email and confirm your participation. I will send you my Skype username.
Yours Sincerely,
Houcemeddine Turki
_______________________________________________
Wikimedia-Medicine mailing list
Wikimedia-Medicine(a)lists.wikimedia.org<mailto:Wikimedia-Medicine@lists.wikimedia.org>
https://lists.wikimedia.org/mailman/listinfo/wikimedia-medicine
--
Nancy Gertrudiz
mobile (+52) 5554192839
t: @ngertrudiz
_______________________________________________
Wikimedia-Medicine mailing list
Wikimedia-Medicine(a)lists.wikimedia.org<mailto:Wikimedia-Medicine@lists.wikimedia.org>
https://lists.wikimedia.org/mailman/listinfo/wikimedia-medicine
--
--
- Scott MacLeod - Founder, President & Professor
- World University and School
- http://worlduniversityandschool.org<http://worlduniversityandschool.org/>
- 415 480 4577
- http://scottmacleod.com<http://scottmacleod.com/>
- CC World University and School - like CC Wikipedia with best STEM-centric CC OpenCourseWare - incorporated as a nonprofit university and school in California, and is a U.S. 501 (c) (3) tax-exempt educational organization.
IMPORTANT NOTICE: This transmission and any attachments are intended only for the use of the individual or entity to which they are addressed and may contain information that is privileged, confidential, or exempt from disclosure under applicable federal or state laws. If the reader of this transmission is not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this transmission in error, please notify me immediately by email or telephone.
Dear Mr. or Ms.,
I thank you for your efforts. Several days ago, I created a proposal for risk factor so that it can be added as a Wikidata property. https://www.wikidata.org/wiki/Wikidata:Property_proposal/risk_factor. The status of the proposal is currently ready. This means that the property is eligible for creation. That is why I invite you to create it so that I can organize this week a Skype discussion about our method of the automatic enrichment of Wikidata with risk factors. Of course, in this online meeting, I will absoolutely show the method in details and adjust it according to your opinions.
Yours Sincerely,
Houcemeddine Turki
Hi!
Today we are indexing in ElasticSearch almost all string properties
(except a few) and select item properties (P31 and P279). We've been
asked to extend this set and index more item properties
(https://phabricator.wikimedia.org/T199884). We did not do it from the
start because we did not want to add too much data to the index at once,
and wanted to see how the index behaves. To evaluate what this change
would mean, some statistics:
All usage of item properties in statements is about 231 million uses
(according to sqid tool database). Of those, about 50M uses are
"instance of" which we are already indexing. Another 98M uses belong to
two properties - published in (P1433) and cites (P2860). Leaving about
86M for the rest of the properties.
So, if we index all the item properties except P2860 and P1433, we'll be
a little more than doubling the amount of data we're storing for this
field, which seems OK. But if we index those too, we'll be essentially
quadrupling it - which may be OK too, but is bigger jump and one that
may potentially cause some issues.
So, we have two questions:
1. Do we want to enable indexing for all item properties? Note that if
you just want to find items with certain statement values, Wikidata
Query Service matches this use case best. It's only in combination with
actual fulltext search where on-wiki search is better.
2. Do we need to index P2860 and P1433 at all, and if so, would it be ok
if we omit indexing for now?
Would be glad to hear thoughts on the matter.
Thanks,
--
Stas Malyshev
smalyshev(a)wikimedia.org
Hey all,
we had a productive “strategy meetup” at Wikimania with a group of about 20 people, to talk about the future of WikiCite and a roadmap for source metadata in Wikidata more generally.
The motivation for this meetup was a set of concerns around scalability and “growing pains” around bibliographic and citation data in Wikidata, as well as the need (that many in the community have expressed) for a clearer goal, value proposition, and scope for WikiCite.
The result is a series of notes fleshing out 4 possible scenarios for the future of bibliographic data as structured data—from a centralized scenario to a fully federated one—discussing their possible risks and benefits at the technical, social, and governance level:
https://www.wikidata.org/wiki/Wikidata:WikiCite/Roadmap
The question these notes try to address is whether Wikimedia should aim to build a “bibliographic commons”, and if so, what it would look like, and where it should live.
This document is not a formal proposal or an RfC open for a vote, but a conversation starter to evaluate what type of future makes most sense for this data and the communities and stakeholders that will benefit from it. A shared understanding on what we’re building towards is also going to help us inform the program of the upcoming WikiCite 2018 conference in November (the application process will open in a few days).
If you wish to share your thoughts on these four scenarios, please chime in on wiki, rather than replying here, to avoid thread splintering (I’m cross-posting this on a few mailing lists).
Dario
on behalf of the meetup participants