Wiki-research-l

wiki-research-l@lists.wikimedia.org

8 participants
2988 discussions

StrepHit IEG renewal: call for support
by Marco Fossati 24 Jul '16

24 Jul '16

[Begging pardon if you read this multiple times] Dear all, Remember StrepHit [1], the Natural Language Processing pipeline that extracts structured data from raw text and produces Wikidata [2] statements with reference URLs? StrepHit got funded for 6 months by a Wikimedia IEG [3]. Its datasets are now uploaded to the *primary sources tool* [4, 5]: the goal of the tool is to provide a standard workflow for data donations to Wikidata. Now, we believe that the primary sources tool *really needs lots of improvements*, which we have been collecting in a request for comment [5]. That's why we opened a renewal request for the StrepHit IEG [6]. If you like the idea, please endorse the renewal! Best regards, Marco Fossati [1] https://github.com/Wikidata/StrepHit [2] https://www.wikidata.org [3] https://meta.wikimedia.org/wiki/Grants:IEG/StrepHit:_Wikidata_Statements_Va… [4] https://www.wikidata.org/wiki/Wikidata:Primary_sources_tool [5] https://github.com/Wikidata/primarysources [6] https://meta.wikimedia.org/wiki/Grants:IEG/StrepHit:_Wikidata_Statements_Va…

1 0

Mobile Wikipedia, Commons, Wikidata, and Pokémon
by Pine W 22 Jul '16

22 Jul '16

Hi WMF Mobile and Research, I'm wondering if we (mostly meaning "you" but perhaps with external collaborators) have considered how the Wikipedia mobile apps, Wikipedia mobile web, the Wikidata game, and/or the Commons app could borrow some design ideas or features from Pokémon Go to make Wikimedia offerings more appealing, particularly to younger audiences. This would apply to content consumption and contribution, as well as community aspects of Wikimedia experiences, particularly on mobile platforms. Thanks, Pine

8 12

Watchlists
by Jan Dittrich 21 Jul '16

21 Jul '16

Hello Research list, Are you aware of research on the use of Watchlists on Wikipedia? There are is the wish in the German Community to improve watchlists (one suggestion is the ability to watch a page only for a certain amount of time) but I currently lack the data to find out about the needs behind that and other wishes. Jan -- Jan Dittrich UX Design/ User Research Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin Phone: +49 (0)30 219 158 26-0 http://wikimedia.de Imagine a world, in which every single human being can freely share in the sum of all knowledge. That‘s our commitment. 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/029/42207.

4 4

The Wikimedia Research Showcase (July 2016): Detecting personal attacks on Wikipedia; Wikipedia.org Portal Research
by Dario Taraborelli 20 Jul '16

20 Jul '16

We put the research showcase on hold for the past quarter due to other outreach initiatives (Wiki Workshop '16, WikiCite, Wikimania). We're back this month with two presentations by the Wikimedia Research team and our collaborators at Jigsaw. The showcase will be streamed <https://www.youtube.com/watch?v=eZgqzVuRDRs> on YouTube *tomorrow Wednesday July 20*, starting at *11.30 Pacific Time*. As usual, we'll be hosting a Q&A via our IRC channel (#wikimedia-research on irc.freenode.net). Look forward to seeing you there! Dario *Detecting Personal Attacks on Wikipedia*By *Ellery Wulczyn <https://meta.wikimedia.org/wiki/User:Ewulczyn_(WMF)>, Nithum Thain <https://meta.wikimedia.org/wiki/User:nthain>* Ellery Wulczyn (WMF) and Nithum Thain (Jigsaw) will be speaking about their recent work on Project Detox, a research project to develop tools to detect and understand online personal attacks and harassment on Wikipedia. Their talk will cover the whole research pipeline to date, including data acquisition, machine learning model building, and some analytical insights as to the nature of personal attacks on Wikipedia talk pages. *Wikipedia.org Portal Research*Search behaviors and New Language by article count Dropdown By *Daisy Chen <https://meta.wikimedia.org/wiki/User:Dchen_(WMF)>* What part do the Wikipedia.org portal and on-wiki search mechanisms play in users' experiences finding information online? These findings reflect research participants' responses to a combination of generative and evaluative questions about their general online search behaviors, on-wiki search behaviors, interactions with the Wikipedia.org portal, and their thoughts about a partial re-design of the portal page, the new language by article count dropdown. *Dario Taraborelli *Head of Research, Wikimedia Foundation wikimediafoundation.org • nitens.org • @readermeter <http://twitter.com/readermeter>

1 1

Re: [Wiki-research-l] [WikimediaMobile] Mobile Wikipedia, Commons, Wikidata, and Pokémon
by Pine W 19 Jul '16

19 Jul '16

Hi Joaquin, Thanks very much for the comments. I'm too buried in short-term issues to participate further in this discussion at the moment, but I'm glad that you're thinking in the way that you are. I hope that more people will participate in this discussion. Pine On Mon, Jul 18, 2016 at 7:04 AM, Joaquin Oltra Hernandez < jhernandez(a)wikimedia.org> wrote: > Hi Pine, > > I personally enjoyed your comments, you are looking ahead and want the > platforms to move forward in terms of user experiences and interaction, and > that is great. > > I was thinking along similar lines as Stuart, using OSM to navigate and >> encouraging users to take photos of landmarks and other buildings where >> that's permitted by FOP. Landmarks for which we have only small photos, old >> photos (more than about 3 years), or no photos could be prioritized. >> > This is very interesting, and a great contribution mechanic for mobile > users. Right now I'd visualize this as a native apps only feature, given > the need to do location background checks and notifications usage. This use > case in particular is possible as of lately in modern browsers too with > service workers I believe, but the technologies are still not widely > adopted by all vendors. > > What's your opinion on standalone focused experiences vs integrating this > sort of features into the other bigger products like the Wikipedia native > apps or the Wikimedia sites? > > Personally I believe that this sort of things would be better served by > standalone applications/websites that could be linked and interoperate with > the others, but everything has tradeoffs and that would make them have a > lot less exposure to users (which is sometimes a good thing). > > Regarding the case of mobile uploads, from what we learned from the mobile > web implementation some time ago, the feature set has to be well designed > and tested with real users, otherwise there's an inflow of vandalism (for > example via selfies) that is very damaging. In that case, the solution was > to disable the thing because that's the way to make sure that editors > wouldn't be overloaded. > > Also, for readers, how about showing the readers an OSM view of the world >> and noting which nearby features have Wikipedia articles as the users >> navigate on the map? >> > > This is something we're closer to being able to do. The Discovery Maps > team is working hard on getting OSM maps ready for wide usage ( > https://maps.wikimedia.org/#3/43.64/-38.14), and the Discovery Search > team has recently (like last week) enabled a geosearch endpoint that allows > you to search within the radius of a location (per iOS app team's request) > that enables this use case you just mentioned. > > All great work, I can't wait to see what the apps teams do with it. > > Finally, > > > I was going to comment on the next paragraph, but there is not much to > say. I completely agree and I feel the same way. Greatly put: > > >> I'd like users to have emotionally rewarding experiences when exploring >> our content, as well as creating new content or editing existing content. >> Editing is painful on mobile, and even on desktop in VE there are bugs >> which are frustrating. I'd like our tools to work properly, fast, and >> intuitively. I realize that WMF has a limited budget, but our interface is >> a ways from being a smooth and enjoyable experience, both on VE and on >> wikitext. And for readers, I'd like to have robust multimedia search and >> interactive features. We are far behind in our interfaces compared to sites >> and apps that others provide, and I hope that we can close that gap within >> the next two to three years. If WMF does not improve its interfaces >> rapidly, this leaves the door open for competitors to remix our content >> with better interfaces, and also encourages potential contibutors to leave >> Wikimedia for places that provide nice, modern designs and user experiences. >> > > Really ^, 10/10 IMO. > > Aside from the resource problem, I'd be keen in hearing other thoughts on >> how to accelerate WMF progress on design and features so that we can have >> some of the features that I mentioned above as well as have intuitive, >> fast, robust interfaces that our readers and contributors enjoy using. > > > What are your thoughts on this last paragraph? I have some of my own that > I'll share now, but it'd be great to know what you think. > > My take is that for accelerating progress on innovation on design and > features, you need and want to move fast, and be directly involved with > early adopters (engaged, adventurous, and in the target user space). > > To go fast, it is known that you need small teams, and to innovate and > make progress you need capable forward-thinking people. > > To get early adopters you need a pool of people to engage with long term > to drive the development of such projects, which the wikimedia community > has, if enough effort was put into involving people in such projects. > > With that in place, you can benefit of early feedback over working > prototypes, on which you can iterate and pivot, with less communication > overhead, and full sense of ownership of the work produced which usually > yields high engagement both from the development teams and the early users. > > Before answering the question, there's another thing to take into account, > what happens after a bunch of prototypes have become working products that > survived. There needs to be a clear life-cycle in place for the projects > once they get to a certain point, talking about how to integrate it into > existing offerings, drive users to benefit of this other project, or > finally sunset/get rid of it if it is not worth it later on. This part is > very important to increase reach and usefulness of the projects, and avoid > zombie projects lingering in limbo for a long time. > > So, how do you accelerate WMF progress on design and features so that we > can have some of the features mentioned above as well as have intuitive, > fast, robust interfaces that our readers and contributors enjoy using? > > My take is create small experimental teams with laser focus and tight > collaboration with early adopters, and shape those outputs into broader use > once they reach a critical point where it is clear they are a good idea, or > bury lingering projects quickly. > > I believe that the foundation has resources to at the very least try the > approach, but there are a few factors that are hard to overcome some times: > Accepting risks and saying no to safer, more conservative bets, believing > on bigger results later on. And trusting people you appoint to do this to > do a great job. > > One obstacle is that *Nobody ever got fired for choosing IBM* :p as they > say, and taking risks is hard. > > Also, this I just talked about is (as asked) *WMF progress on design and > features.* There are also awesome contributors that make very forward > thinking experiments where WMF could help via funding or resources, and > that may be the better way to go for WMF. > > Anyways these are my thoughts, looking forward to hearing other opinions. > > > On Fri, Jul 15, 2016 at 4:59 AM, Pine W <wiki.pine(a)gmail.com> wrote: > >> Sorry, I think that last paragraph sounded a bit like a rant. I think >> some of the problem here is that WMF lacks the financial resources to >> deploy many hundreds or thousands of researchers, designers and engineers >> like Google and Microsoft can. I'd like to see that resource problem >> solved. To be fair, even with all of their resources, Microsoft in >> particular has had problems (Windows 8 and Windows Vista come to mind). >> However, I do wonder, if WMF was able to borrow 500 researchers, designers, >> and engineers from other companies for a year or two, if WMF could make >> serious progress at the usability and features deficits between Wikimedia >> platforms and other major sites. >> >> Aside from the resource problem, I'd be keen in hearing other thoughts on >> how to accelerate WMF progress on design and features so that we can have >> some of the features that I mentioned above as well as have intuitive, >> fast, robust interfaces that our readers and contributors enjoy using. >> >> Pine >> >> On Thu, Jul 14, 2016 at 7:22 PM, Pine W <wiki.pine(a)gmail.com> wrote: >> >>> I was thinking along similar lines as Stuart, using OSM to navigate and >>> encouraging users to take photos of landmarks and other buildings where >>> that's permitted by FOP. Landmarks for which we have only small photos, old >>> photos (more than about 3 years), or no photos could be prioritized. >>> >>> Also, for readers, how about showing the readers an OSM view of the >>> world and noting which nearby features have Wikipedia articles as the users >>> navigate on the map? >>> >>> Finally, I'd like users to have emotionally rewarding experiences when >>> exploring our content, as well as creating new content or editing existing >>> content. Editing is painful on mobile, and even on desktop in VE there are >>> bugs which are frustrating. I'd like our tools to work properly, fast, and >>> intuitively. I realize that WMF has a limited budget, but our interface is >>> a ways from being a smooth and enjoyable experience, both on VE and on >>> wikitext. And for readers, I'd like to have robust multimedia search and >>> interactive features. We are far behind in our interfaces compared to sites >>> and apps that others provide, and I hope that we can close that gap within >>> the next two to three years. If WMF does not improve its interfaces >>> rapidly, this leaves the door open for competitors to remix our content >>> with better interfaces, and also encourages potential contibutors to leave >>> Wikimedia for places that provide nice, modern designs and user experiences. >>> >>> Pine >>> On Jul 14, 2016 15:03, "Stuart A. Yeates" <syeates(a)gmail.com> wrote: >>> >>>> A game built on a travel-photograph-upload loop would be a great way to >>>> build our depth of imagery. >>>> >>>> cheers >>>> stuart >>>> >>>> -- >>>> ...let us be heard from red core to black sky >>>> >>>> On Fri, Jul 15, 2016 at 9:52 AM, Toby Negrin <tnegrin(a)wikimedia.org> >>>> wrote: >>>> >>>>> Hi Pine -- did you have any specific ideas? I spent some time in the >>>>> gaming industry and am familiar with Ingress, the game that Pokeman Go is >>>>> based on, as well as the theories behind mechanics/compulsion loops that >>>>> mobile games use. >>>>> >>>>> I'll share one general thought -- the research-edit-publish loop is a >>>>> great mechanism -- it's quick and easy and very gratifying, especially >>>>> combined with a google search. >>>>> >>>>> However, we've generally found that the notion that we use gaming >>>>> mechanics to encourage people to read or edit wikipedia does not have broad >>>>> support in our communities. >>>>> >>>>> -Toby >>>>> >>>>> >>>>> >>>>> On Thu, Jul 14, 2016 at 2:26 PM, Pine W <wiki.pine(a)gmail.com> wrote: >>>>> >>>>>> Hi WMF Mobile and Research, >>>>>> >>>>>> I'm wondering if we (mostly meaning "you" but perhaps with external >>>>>> collaborators) have considered how the Wikipedia mobile apps, Wikipedia >>>>>> mobile web, the Wikidata game, and/or the Commons app could borrow some >>>>>> design ideas or features from Pokémon Go to make Wikimedia offerings more >>>>>> appealing, particularly to younger audiences. This would apply to content >>>>>> consumption and contribution, as well as community aspects of Wikimedia >>>>>> experiences, particularly on mobile platforms. >>>>>> >>>>>> Thanks, >>>>>> >>>>>> Pine >>>>>> >>>>>> _______________________________________________ >>>>>> Mobile-l mailing list >>>>>> Mobile-l(a)lists.wikimedia.org >>>>>> https://lists.wikimedia.org/mailman/listinfo/mobile-l >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Wiki-research-l mailing list >>>>> Wiki-research-l(a)lists.wikimedia.org >>>>> https://lists.wikimedia.org/mailman/listinfo/wiki-research-l >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Wiki-research-l mailing list >>>> Wiki-research-l(a)lists.wikimedia.org >>>> https://lists.wikimedia.org/mailman/listinfo/wiki-research-l >>>> >>>> >> >> _______________________________________________ >> Mobile-l mailing list >> Mobile-l(a)lists.wikimedia.org >> https://lists.wikimedia.org/mailman/listinfo/mobile-l >> >> >

1 0

Call for papers: The First Brazilian Wikipedia Science Conference on Wikipedia (CCBWIKI2016)
by Marcio Gonçalves 12 Jul '16

12 Jul '16

The submission is open until August 20, 2016. Please consider submitting your papers to I CCBWIKI. The First Brazilian Wikipedia Science Conference on Wikipedia in the scientific knowledge dissemination (CCBWIKI2016) October, 13-14, 2016 Brazil, Rio de Janeiro UNIRIO ================ IMPORTANT DATES ================ Submission Dates Open from now until Aug. 20, 2016 Notification of Acceptance Sep. 11-12, 2016 Registration Open until October 13, 2016 Conference Dates October 13-14, 2016 The event will be held over two days with presentations delivered by researchers from the international community, including presentations from keynote speakers. ----------------------------------------- For more info, go to http://ccbwiki.wikimedia.org.br [1] -- Marcio Gonçalves www.ciencianasnuvens.com.br Links: ------ [1] http://ccbwiki.wikimedia.org.br/

1 0

SEMANTiCS 2016, Leipzig, Sep 12-15, Contribute to the Vocabulary Carnival
by Sebastian Hellmann 12 Jul '16

12 Jul '16

The Vocabulary Carnival at SEMANTiCS 2016 is a unique opportunity for vocabulary publishers to showcase and share their work, meet the growing community of vocabulary publishers and users, and build useful semantic, technical and social links. *When?* The Vocabulary Carnival is part of the SEMANTiCS programme with the Carnival Minute Madness on the 13th of September and on the industrial marketplace. *What kind of vocabularies do we expect?* * *Any kind!* For this event we use a very open definition of what a vocabulary is. Ontologies, classifications, thesauri, concept and metadata schemes, whatever their format, in RDF or not, are all welcome. * *Bootstrap your new Vocabulary project:* At the carnival you can present your ideas and early stage vocabs to find the right people to get the Vocab discussion going. We require at least a project web site. *What is your benefit of submitting?* * *attention*: make people aware of your work * *feedback*: a room full of other vocabulary creators will guarantee expert feedback * *linking*: discover links from your vocabulary to others on-site *How to submit your Vocabulary to the Carnival?* 1. Make sure your vocabulary is accessible on the Web through a public URI. 2. Communicate your intention to participate at _https://goo.gl/mV3VpZ_ by joining and posting your vocabulary link and writing “See you at the Carnival in Leipzig” or send an email to monika.solanki(a)cs.ox.ac.uk , with subject “Vocabulary Carnival”. 3. Register to SEMANTiCS:<http://2014.semantics.cc/www.semantics.cc/registration/index.html>_http://2016.semantics.cc/registration/_ <http://2014.semantics.cc/www.semantics.cc/registration/index.html> 4. Submissions will be handled on a *first come, first serve basis* *Are there any technical requirements?* Your vocabulary submission will be evaluated in accordance to the following criteria: * *Reusability* - Which vocabularies and/or ontology design patterns have been reused in its development? Has it been mapped, aligned, imported within other ontologies yet? If not, where do you foresee potential reuse? * *Value addition* - How does the vocabulary provide value addition for the intended project or domain as compared to previous efforts and to Semantic Web in general? * *Design and Technical quality* - how do the ontologies incorporate best practices in design, i.e., using ontology design patterns or extending from upper level ontologies? * *Documentation* - does the vocabulary provide both human and machine readable documentation using for e.g., rdfs:label, rdfs:comment and HTML documentation? * *Availability*: We expect your vocabulary (terminology, taxonomy, ontology, etc.) to be hosted on the Web at a persistent URI (PURL, w3id, ODI) and with an appropriate licence specification. If it is not Linked Data or uploaded to<http://lov.okfn.org/>_http://lov.okfn.org_ <http://lov.okfn.org/> you can get technical help and advise at the conference. * *Usage*: Which academic/industrial projects have adopted the vocabulary? Which datasets have been annotated using the vocabulary? *At the SEMANTiCS 2016 Conference:* * Prepare a poster (max format A0) presenting your vocabulary: description, purpose, history and link to its publication page. Your description of the vocabulary must include the above criteria. * Present your poster in the dedicated space at SEMANTiCS conference. * Brace yourself to participate in the Vocabulary Minute Madness, where every vocabulary will have one minute to convince of its usefulness and quality. Sporting your vocabulary colors at this occasion is optional, but will be much appreciated. * An independent jury will select the best vocabulary poster and presentation. *Vocabulary Carnival and LOV* * If your vocabulary is already recorded at<http://lov.okn.org/>_http://lov.okn.org_ <http://lov.okn.org/>, check its record to see if everything is OK. Ping the LOV curators if something is missing or inaccurate, or if you brush up a brand new version for the Carnival. If you think your vocabulary is LOV-able but not yet recorded, submit its URI at<http://lov.okfn.org/dataset/lov/suggest/>_http://lov.okfn.org/dataset/lov/suggest/_ * If your vocabulary is not yet meeting the technical requirements to be included in LOV, and you wish it could, we can help you to achieve that during the Carnival. *About the Vocabulary Carnival* The Vocabulary Carnival will be hosted at the SEMANTiCS conference, Sep 12-15 2016 *Contact* Monika Solanki (_monika.solanki(a)cs.ox.ac.uk_ <mailto:monika.solanki@cs.ox.ac.uk>) Ghislain Atemezing (_ghislain.atemezing(a)mondeca.com_ <mailto:ghislain.atemezing@mondeca.com>)

1 0

Weigh in on whether to finalize "Cases" section of CoC
by Matthew Flaschen 12 Jul '16

12 Jul '16

Please comment on whether to approve the "Cases" section of the draft Code of conduct for technical spaces (https://www.mediawiki.org/wiki/Code_of_Conduct/Draft#Page:_Code_of_Conduct.…). You can comment at https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft#Finalize_.22Cases… . A position and brief comment is fine. You can also send private feedback to conduct-discussion(a)wikimedia.org . Thanks again, Matt Flaschen

1 0

Multi year page views statistics
by Avner Kantor 11 Jul '16

11 Jul '16

Can it be done by https://tools.wmflabs.org/pageviews or any other tool? Thanks, Avner

3 2

WMF Open Access Policy and Independent Researchers
by Maximilian Klein 09 Jul '16

09 Jul '16

Hello All, As you might know WMF has an Open Access Policy that requires all work that they fund to be Open Access[1]. A strange consequence of this policy, that I recently ran into, is that it requires researchers funded by grants to publish OA -- but without providing any funding to do so. That is, I recently completed an Individual Engagement Grant (IEG), part of whose scope was explicitly to write a paper about the work[2], and when I wrote to WMF to acquire funds for OA publishing, they confirmed that the paper was under the OA mandate but indicated that funds were not available to pay for OA publishing. Has anyone else use WMF's Open Access Policy? What was your experience? [1] https://wikimediafoundation.org/wiki/Open_access_policy [2] https://meta.wikimedia.org/wiki/Grants:IEG/WIGI:_Wikipedia_Gender_Index#Act… Make a great day, Max Klein ‽ http://notconfusing.com/

13 19

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Wiki-research-l