Hello visitor, I'm very happy to answer questions and inquiries. Please discuss at the place discussion get started.
Welcome to Wikidata, Conny!
Wikidata is a free knowledge base that you can edit! It can be read and edited by humans and machines alike, and you can help. Go to any item page now and add to this ever-growing database!
Need some help getting started? Here are some pages you can familarise yourself with:
If you have any questions, please ask me on my talk page. If you want to try out editing, you can use the sandbox to try. Once again, welcome, and I hope you quickly feel comfortable here, and become an active editor for Wikidata.
Regards, --Bene* (talk) 16:50, 4 November 2012 (UTC)
Ein herzliches Willkommen bei Wikidata :-) --Bene* (talk) 16:50, 4 November 2012 (UTC)
Dankeschön :) . --Conny (talk) 21:32, 4 November 2012 (UTC).
Hi, there is currently no adopted policy for using lower numbers, and that serves no purpose except being aesthetically pleasing. If you want to undelete, move all of the links over and lose the history associated with the page with more links - go ahead. However, there is no need to according to policy as of yet. See Wikidata talk:Deletion policy for a proposal on it. Ajraddatz (Talk) 14:02, 8 January 2013 (UTC)
So then ;) - the history get lost, if you use newer version. First ID ist ID to use for my oppinion. Conny (talk) 14:06, 8 January 2013 (UTC).
Usually, the version with the most links has the history that is usable (though in this case, both only had bot contributions so it doesn't matter). If you feel it is worth doing, then I won't stop you... but I don't see the need myself. Ajraddatz (Talk) 14:14, 8 January 2013 (UTC)
Hi Conny, bei Ben Nevis hast du für die Aussage "Geographisches Objekt" zwei Quellen angegeben:
Verlag: Axel Springer AG
Verlag: Scottish Mountaineering Club
Quellenangaben sind zwar fast immer gut, aber "Axel Springer AG" ist leider zu allgemein. Wo soll ich da nachschlagen? Autor, Buchtitel, Ausgabe, Seitenangabe: alles fehlt. Und der zweite Eintrag ist kein Verlag, sondern ein Club. Außerdem: Die Aussage, dass ein Berg ein "Geographisches Objekt" ist, ist weitgehend unstrittig. Belegt werden sollten weiterführende Angaben wie Höhe, Erstbesteigung etc. Fröhliches Schaffen --Kolja21 (talk) 18:16, 19 February 2013 (UTC)
PS: Die für Quellenangaben wichtige Eigenschaft (property) "Buchtitel" fehlt leider noch, kommt aber hoffentlich in den nächsten Tagen. --Kolja21 (talk) 18:25, 19 February 2013 (UTC)
Danke für deine Nachfrage. Ich habe erste Versuche unternommen, leider konnte ich die Inhalte, welche ich eintragen wollte nicht eintragen. Mit Buchtitel das ist mir auch aufgefallen :) . Aber Problem ist, nicht jeder Buchtitel einen Wikipediaartikel hat - im Moment scheinen dort nur Items als Quellen angebbar zu sein? Gibt es eine Beschreibungsseite für Sources - ich habe in kurzer Suche nichts gefunden. Grüße, Conny (talk) 20:08, 19 February 2013 (UTC).
Bislang hieß es immer, dass wir Quellen noch nicht verwenden sollen. Ich denke daran hat sich mit dem Update von gestern nichts geändert. Eine Beschreibungsseite gibt es noch nicht. --Kolja21 (talk) 20:48, 19 February 2013 (UTC)
Danke für den Hinweis. Keine Ahnung wie nicht informierte Benutzer damit umgehen - mangels Diffanzeige fällt dies leider auch nicht offensichtlich auf... Conny (talk) 11:29, 20 February 2013 (UTC).
Die Diffanzeige funktioniert jetzt für die Eigenschaften. Was die Quellen betrifft, habe ich einfach mal die Frage im Forum (Wikidata:Project chat#Sources) gepostet. Grüße --Kolja21 (talk) 15:24, 20 February 2013 (UTC)
I deleted the "Imported from: English Wikipedia" source because it referred to the 3.0.0 version, not the 3.0.1.
What I did was: noticed it needed to be updated; checked latest version at R official site; updated latest stable version at Wikidata; then removed the source.
Was this correct? I've read some of the Wikidata documentation, but not all of it. I may be doing things not in the appropriate way. How should it be done?
Hast du dazu eine Antwort? --Kolossos (talk) 22:24, 28 October 2014 (UTC)
Habs mal aus dem Archiv gesucht. Nach meinem Verständnis braucht man entweder einen neuen Wikipedia Artikel, um die Unterscheidung zu machen, oder man fügt als Qualifier eine Zusatzinformation mit dran. Tendiere aber eher zum ersten Punkt. Würde das was bringen? Soll ich mir das mal konkreter anschauen? Grüße, Conny (talk) 12:48, 1 November 2014 (UTC).
Hallo. Könntest du als Admin der deutschen Version dieses Artikels bitte ein "featured list" spendieren? Danke. --SamWinchester000 (talk) 04:19, 6 August 2016 (UTC) Dabei frag ich mich, wieso die Möglichkeit gegeben wird, dies als normaler Nutzer selbst zu tun, wenn es dann doch grundsätzlich nicht speicherfähig ist.
Vielen Dank für den Hinweis :) . Informative Liste vergeben. Habe mal getestet - Die Begründung bei dem Versuch als Benutzer zu speichern lautet, dass dies Konsensentscheidungen in den jeweiligen Wikipedien sind und somit nur durch Administratoren gemacht werden sollten :( . Grüße, Conny (talk) 16:39, 10 August 2016 (UTC).
Vielen Dank auch Dir! :) Auf Wikidata (nicht so meine Nische) scheint es wohl, noch Baustellen zu geben. ;) --SamWinchester000 (talk) 00:40, 13 August 2016 (UTC)
Auf jeden Fall. Fühl dich frei mich zu kontaktieren :D . Grüße, Conny (talk) 04:46, 13 August 2016 (UTC).
Hallo Conny - wie geht das nach dem Beantragen eines neuen Property weiter? - Da steht jetzt oben "ready". Kommt irgendwann jemand vorbei und erstellt das Property oder muss ich dafür noch irgendwas anstellen? (Wikidata lässt mich immer wieder mit einem ratlosen Gesicht zurück....) --Ordercrazy (talk) 09:34, 19 September 2017 (UTC)
Schau ich mir zeitnah an. Danke für Hinweis, Conny (talk) 09:37, 19 September 2017 (UTC).
15:16, 10 May 2018 Mahir256 (talk | contribs) blocked 22.214.171.124/16 (talk) with an expiration time of 3 months (anonymous users only, account creation disabled, email disabled, cannot edit own talk page) (This IP range has been abused by a vandal for a long time, please log in to edit)
Welcome to the third newsletter for the new Growth team!
The Growth team's objective is to work on software changes that help retain new contributors in mid-size Wikimedia projects.
Two Growth team projects to be deployed in next two weeks
We will be deploying the "Understanding first day" and "Personalized first day" projects on Czech and Korean Wikipedias in the coming weeks. See the new project pages below for full details on the projects, and our project updates page for their progress.
Understanding first day: learn about the actions new editors take right after creating their accounts. We will be careful with user privacy, and we hope to share initial results in December.
Personalized first day: learn about new editors' objectives by adding some optional questions to the new editor’s registration process, and personalizing their onboarding. We hope to share initial results in December.
Third Growth team project begins
Focus on help desk: direct newcomers to the local help desks where they can ask questions to help them make their first edits. We hope to have an initial experiment running in December.
Best practices for helping newcomers
We are going to direct newcomers to help desks. But what's the best way to reply to a newcomer there? We have gathered some best practices for successful interactions, based on community experiences and some external documentation. The page has also been reviewed by some experienced community members who suggested some changes. That page is now open for translations. Comments and suggestions are still welcome!
The survey is now being shown to half of new users (A/B test). Responses are being recorded in the database. We'll report on initial results during December.
We are planning to test a second version of the survey, called "Variation C", which we think will maximize the number of users who complete the survey and stay on the wiki.
The original objective of this project was to give newcomers the materials they need to achieve their goals, and so now we are currently planning how we will use the information collected in the welcome survey to personalize the newcomer's experience. We hope community members will read our current thinking and join the conversation here. Some of the plans we are considering include:
Making it easy for newcomers to see editing activity around the topic areas in which they indicated that they're interested.
Connecting interested newcomers to experienced editors.
Surfacing the help content most relevant to the reason for which the newcomers created their accounts.
Understanding first day (EditorJourney) was deployed on November 15 on both Czech and Korean Wikipedias. It has been done after a longer security review and final testing than expected. Data is now being recorded for all new users on those wikis, and we've been auditing the data and preparing to make initial reports during December. Stay tuned for the next newsletter!
Help panel is under construction
Focus on help desk (help panel) is planned to be deployed during the week of January 7 on both Czech and Korean Wikipedias.
In addition to giving the ability to ask a question, the help panel will also contain a set of links to existing help content. Our ambassadors on Czech and Korean Wikipedias are determining the right initial set of most helpful links in this task.
We began the "Personalized first day" project with the welcome survey so that we could gather information about what newcomers are trying to accomplish. The next step is to use that information to create experiences that help the newcomers accomplish their goal – actually personalizing their first day. We asked for community thoughts in the previous newsletter, and after discussing with community members and amongst our team, we are now planning two projects as next steps: "engagement emails" and "newcomer homepage".
Engagement emails: this project was first discussed positively by community members here back in September 2018, and the team how has bandwidth to pursue it. The idea is that newcomers who leave the wiki don't get encouraged to return to the wiki and edit. We can engage them through emails that send them the specific information they need to be successful – such as contact from a mentor, the impact of their edits, or task recommendations. Please read over the project page, and comment on its discussion page with any ideas, questions, or concerns. Do you think this is a good idea? Where could we go wrong?
Newcomer homepage: we developed the idea for this project after analyzing the data from the welcome survey and EditorJourney datasets. We saw that many newcomers seem to be looking for a place to get started – a place that collects their past work, options for future work, and ways to learn more. We can build this place, and it can connect to the engagement emails. The content of both could be guided by what newcomers say they need during their welcome survey, and contain things like contact from a mentor, impact of their edits, or task recommendations. Please read over the project page, and comment on its discussion page with any ideas, questions, or concerns. Do you think this is a good idea? Where could we go wrong?
We have published initial reports on each of the team's first two projects. These reports give the basic numbers from each project, and there are many more questions we will continue to answer in future reports. We're excited about these initial findings. They have already helped us define and design parts of our future projects.
The help panel was deployed in Czech and Korean Wikipedias on January 10. Over the past four weeks:
About 400 newcomers in each wiki have seen the help panel button.
About 20% of them open up the help panel.
About 50% of those who open it up click on one of the links.
About 5% of Czech users ask questions, and about 1% of Korean users ask questions.
We think that the 20% open rate and 50% click rate are strong numbers, showing that a lot of people are looking for help, and many want to help themselves by looking at help pages. The somewhat lower numbers of asking questions (especially in Korean Wikipedia) has caused us to consider new features to allow people to help themselves. We're going to be adding a search bar to the help panel next, which will allow users to type a search that only looks for pages in the Help and Wikipedia namespaces.
Hallo Conny, ich hab mich mal etwas genauer mit SPARQL befasst und angefangen ein paar nützliche Abfragen für Dresden zu schreiben. Falls du Ideen hast, lass es mich wissen. -- sk (talk) 19:28, 14 February 2019 (UTC)
Man spitze was du da alles gezaubert hast :) . Danke für Hinweis! Grüße, Conny (talk) 10:34, 19 February 2019 (UTC).
The Growth team has been working on features to increase new editor retention for the last seven months. We have made a lot of progress and learned a lot, and we've just finished planning for our next three months. During the next three months, we're going to focus on iterations of the help panel and the newcomer homepage. We have decided not to start the engagement emails project, because we think that we will be able to do better work by improving the projects we have already started. Specifically, these are our team goals:
Deploy and iterate on newcomer homepage
Continued iteration on help panel
Make the help panel available to more wikis
Add a fourth Wikipedia to our set of target wikis
Publish in-depth quantitative reporting on the data from this year
Assemble a report on what our team has learned so far about newcomers
The newcomer homepage is our current major project. We hope that community members can read over the project page, and comment on its discussion page with any ideas, questions, or concerns. You can see in the accompanying mockup how we are thinking about the homepage.
We have recently decided on the specifications for an initial version that we can deploy and iterate on:
Shown in the User space
Desktop only (mobile comes next)
Help module: help links and ability to ask help desk questions
Mentorship module: all newcomers assigned a mentor to whom they can ask questions
Impact module: shows the number of pageviews for pages the newcomer edited
Account completion module: gives some very simple recommendations of how to get started (add an email, start your user page)
Layout not yet personalized for each user
We're currently running live user tests on this configuration. Future work will include adapting the homepage for mobile, working on a task recommendation module, and considering how to encourage newcomers to visit their homepage.
Screenshot from Vietnamese Wikipedia showing the help panel open on the Community Portal, including the "search" bar.
During the last month, the help panel was deployed on Vietnamese Wikipedia, adding it to Czech and Korean Wikipedias.As of 2019-03-14:
2,425 newcomers have seen the help panel
422 of them have opened it
175 have clicked links
27 have run searches
40 have asked questions
We have been analyzing the data around usage, and we'll be publishing numbers in the coming weeks. At a high level, we see at least some users are being helped by the panel, with many clicking on links, running searches, and asking questions. We do not yet see any problems that have arisen from the help panel. Therefore, we think that the help panel is generally a positive feature – though data is still coming that will allow us to see its numerical impact. If other wikis are interested in using the help panel, please contact us on our team's talk page, in the language of your choice.
Over the past month, we have iterated on the help panel to take into account the usage patterns we are seeing. You can see in the accompanying image how the help panel currently looks.
We added a search capability, in which users can search the Help and Wikipedia namespaces.
The help panel was previously available whenever a newcomer was in "edit" mode. We are now also showing the help panel when a newcomer is in "read" mode on a page in the Help, Wikipedia, or User namespaces.
We want to see whether users find the "search" useful. If so, we may spend time on improving search results. We're also looking forward to learning whether exposing the help panel in "read" mode in more namespaces will increase usage.￼
Hallo Conny, oft stoße ich beim Abarbeiten der Listen von Objekten, bzw. Denkmallisten auf Objekte die abgerissen, zerstört oder verschwunden, also nicht mehr an diesem Ort vorhanden sind. Wie gehen wir auf Wikidata damit um?Lutz (talk) 10:07, 14 April 2019 (UTC).
@Lutzto: Ich handhabe es über die Eigenschaft end time (P582), da man ja beispielsweise auch historische Karten erstellen möchte. Um aktuelle Denkmale zu finden, kann man dann filtern, dass nur Objekte ohne Endzeitpunkt angezeigt werden sollen. Auch die Qualifikatoren dazu sind interessant. Wenn der genaue Endzeitpunkt nicht bekannt ist, kann man bei den kleinen Kästchen neben der Eingabebox für das Datum "Unbekannter Wert" eingeben. Somit ist das Ende definitiv, aber nicht bekannt. Was sagst du dazu? Grüße dir, Conny (talk) 08:28, 14 April 2019 (UTC).
Als Zwischenlösung sicher zu gebrauchen, aber oft weiß man nicht was damit geschehen ist, Beispiel Bernsteinzimmer, oder alte Gemälde die jetzt irgenwo im Keller eines Auftraggebers hängen. Irgendwie fehlt die Aussage ist Verschollen bei Objekten.Lutz (talk) 11:43, 14 April 2019 (UTC).
Screenshot of newcomer homepage in Test Wikipedia, in English.
The main feature that the team has been working on over the last month is the newcomer homepage. This feature gives newcomers a place on the wiki to get oriented, learn about editing, and see their impact (see the accompanying screenshot from Test Wikipedia). We intend to release this feature to Czech, Korean, and Vietnamese Wikipedias on May 2nd.
Like the other Growth team features, this will be deployed in a controlled experiment, in which half of newcomers will have access to their homepage and half will not. Users with the feature will be able to access it by clicking their username at the top of their browser, and it will only be available on desktop -- not mobile. Experienced users who want to see their homepage will be able to turn it on in their preferences.
Wikis receiving the newcomer homepage can expect these things:
Additional questions will come to the help desk from the "help module" on the homepage.
Mentors who have signed up for the "mentorship module" will start to receive questions on their user talk pages.
More users may create and edit user pages through the "start module".
The most important piece developed for the homepage over the last month is the "start module", which gives newcomers clear actions to take when they are new: add/confirm their email, go through a tutorial, start their user page. We learned about the need for this module from user tests last month. The next priorities for the newcomer homepage are:
Mobile design: to work well in mobile browsers, the homepage needs a separate design and engineering. See the accompanying mockups for potential mobile designs.
Features for discovery: only about 15% - 30% of newcomers will discover their homepage by clicking their username at the top of their browser. We are going to be designing additional ways for newcomers to find out about it.
Additional modules: the initial version contains some of the simpler modules. Potential upcoming modules include task recommendations and a feed of activity on the wiki.
Help panel leading indicators: our team published data on the help panel's initial performance. The evaluation exposes some areas for improvement, but we think the help panel's behavior so far is healthy and that it is not having a negative impact on the wikis. We will be publishing additional data, making plans, and asking for community thoughts around the future of the help panel over the course of the next two weeks. If you are interested in trying out the help panel on your wiki, please let us know on our team's talk page.
Long term plans: the team had a week of planning meetings, in which we talked about some longer-term ideas for Growth work. Some of the top ideas are: to extend the newcomer homepage to help user's build their identity through a user profile, and to revisit the "engagement emails" project that the team put on hold. Over the next month, we will be asking for community conversation around how the team can spend our time in the next fiscal year, that starts in July.
Call for submissions for the Community Growth space at Wikimania 2019Edit
Welcome to a special newsletter from the Growth team! This special newsletter is not about Wikimedia Foundation Growth team projects. Instead, it is a call for submissions for the Community Growth space at Wikimania 2019. We think that many people who receive this newsletter may have something valuable to contribute to this space at Wikimania. We haven't translated the newsletter, because Wikimania's language is English.
Since you are interested b Growth team projects, and potentially involved in welcoming newcomers initiatives on your wiki, we would like to invite you to submit a proposal to the Community Growth space because of the actions you’ve done around newcomers on wikis. The deadline for submission is June 1. See below for Community Growth submission topics and session formats. Topics and sessions have to be in English.
In the Community Growth space, we will come together for discussions, presentations, and workshops that address these questions:
What is and is not working around attracting and retaining newcomers?
How should Wikimedia activities evolve to help communities grow and flourish?
How should our technology and culture evolve to help new populations to come online, participate and become community members?
Recommended topics: please see this link for the list for the list of recommended topics. If you do not plan to submit a proposal, you can also suggest additional topics here. If your topic does not fit into our space, remember that there are 18 other spaces that could welcome you sharing your knowledge and perspective.
Types of session. We prefer sessions that are participatory, interactive, promote conversations, and give a voice to parts of our movement that are heard less often. Please see this link for the list of recommended session formats.
Poster submissions. Posters are also a good way to introduce a topic, or show some results of an action. Please consider submitting one!
More information about the Community Growth space, topics, and submission formats is available on the proposal page.
A newcomer homepage on Czech Wikipedia (displayed in English language)
The newcomer homepage was deployed in Czech and Korean Wikipedias on May 6 for desktop users. It is deployed in an A/B test, so that half of newcomers have access to the homepage and half do not. They access it by clicking on their username in their personal tools along the top of the window.
After about a month of usage, we see a few interesting trends. We think that the usage is going well so far, as we continue to work on the feature
About half of users who visit the homepage click on a link or button.
About half of users visit the homepage more than once, with about a fifth of users visiting on multiple days.
Users are interacting with all the different modules on the page -- there is no clear favorite.
Users have been asking questions to their mentors -- but not on the help desk.
Features to aid discovery: only a minority of newcomers who have a homepage will find their homepage on their own. The team is designing features that help newcomers learn where to find their homepage. The most important feature will point to the homepage link using a GuidedTour.
User tests showed that the most important thing to add to the homepage are clear task recommendations to help newcomers get started with editing right away. This is the module that we will be working on next.
The Growth team has been working since September 2018, and we're now planning for the work we'll be doing for the next fiscal year, which begins in July.
Though we have not yet developed a feature that clearly increases growth in our target wikis, we believe that the features we have been developing have high potential to increase growth if we continue to work on them.
Therefore, the team will continue to work on the features we have started, and we will develop related features that improve the overall newcomer experience. These features may include:
Improvements to how newcomers can build their user pages and develop their on-wiki identity. See initial notes here.
Improvements to how newcomers receive notifications on-wiki and through email, so that they quickly find out if other users are contacting them.
Processes that help newcomers get awards or recognition for good work.
Ways for newcomers to see the activity on the wiki and find others who share their interests.
We will start discussions with communities to help us define these ideas before we work on them.
Hallo Conny, dieser User hat bisher mehr Edits bei Wikidata als du gemacht. Was glaubst du, wie lange braucht er noch um zu lernen, wie Wikidata fünktioniert? Er löscht Informationen, weil eine Vorlage in der nowiki nicht funktioniert. Das ist aber kein Problem von Wikidata, das müssen die selber lösen, aber nicht in dem die anfangen hier Zeugs rauszulöschen. Grüße -- MovieFex (talk) 17:57, 3 July 2019 (UTC)
Das hat nichts mit der norwegischen Ausgabe zu tun. Es dreht sich ganz einfach darum, dass »sourced from« keine Reference ist. Weil die Vorlage Wikidata (die meines Wissens international in allen Wikipedia-Ausgaben vorhanden ist, siehe z.B. »reference« in der englischen Wikipedia-Ausgabe erwartet, dass ein Beleg ein reeller Weblink ist, wird alles Andere Fehlmeldungen auslösen – und das natürlich nicht nur in der norwegischen Wikipedia. Weil Wikidata hauptsächlich existiert um die verschiedenen Wikipedia-Versionen zu bedienen und nicht hauptsächlich ein Ziel an sich ist, müssen die Einzelposten dem »Kunden«, also Wikipedia, angepasst werden. Asav (talk) 19:53, 3 July 2019 (UTC)
Ist es nicht sinnvoll, einen Wert ohne URL einfach in der Box auszublenden? Solange bis eine Referenz nachgetragen ist. Denkt sich Conny (talk) 20:03, 3 July 2019 (UTC).
Asav, da liegst du ganz falsch: Wikidata ist nicht dazu da, um andere Wikipedia-Ausgaben zu bedienen. Andere Wikipedia-Ausgaben können sich aus Wikidata bedienen, das ist ein großer Unterschied. Wikidata ist ein eigenständiges Projekt, wie die norwegische Wikipedia auch. Offenbar ist in der Vorlage noch ein Bug drin, dann muss das eben gefixt werden. Wenn ihr diese Vorlage einsetzt geht das auf euer eigenes Risiko. Aber Wikidata zu manipulieren, dass das bei irgend jemand speziell funktioniert geht so nicht. Stell dir mal vor das machen andere auch noch. -- MovieFex (talk) 20:16, 3 July 2019 (UTC)
The Growth team has existed for about one year. During that time, we have developed several features that we think can help increase retention. Though we are still gathering data to detect scientifically whether the features increase retention, we think that some of the features are ready to be deployed on more wikis that want to experiment with them. If your community is enthusiastic about welcoming newcomers, we encourage you to contact us so that we can verify together if your wiki is eligible.
Then, go through the checklist to start the process of getting these features:
Help panel: allow newcomers to find help and ask questions while they edit.
Welcome survey: learn what topics and types of edits newcomers are interested in.
EditorJourney: learn what workflows newcomers go through on their first day.
Indicator that encourages users to look at their Notifications for responses to their questions
A new quarter of the year has started, and the team has set our goals for the next three months. The most important goals are:
Newcomer homepage: increase activity through a task recommendations module. Now that we have seen several weeks of positive activity on the newcomer homepage, we think that the most important thing to add is a way for newcomers to find tasks to work on. The challenge will be recommending the right kind of tasks at the right point of their journey.
Newcomer homepage: increase feature discovery rate by 100%. Right now, only 20% - 30% of newcomers ever visit their homepage. We want to double that number by making sure all newcomers know how to find it.
Help panel: increase usefulness through improvements to affordance, search, and UX flow. We have looked closely at data and anecdotes from the usage of the help panel, and we plan to pursue specific improvements to increase its effectiveness (see accompanying image of a feature that helps newcomers find responses to their questions).
Wikimania is coming up next month, which includes a "Community Growth" space. We hope to see people from all communities there to talk about how to bring newcomers into our movement.
We have started to deploy features to our team's fourth target wiki: Arabic Wikipedia. That wiki is the biggest one we target, it has a high percentage of mobile users, and also is our first right-to-left language. This will help us make sure that our features are valuable for as many types of users as possible.
Button to help newcomers find their homepage from their empty Contributions page
The mobile version of the newcomer homepage was deployed to Czech, Korean, and Vietnamese Wikipedias. Now, newcomers can access their homepage from both desktop and mobile devices.
We have published our first set of data about the performance of the newcomer homepage. In summary, we are happy with the homepage's performance so far. We see about half of visitors clicking on something, and the majority of them returning to the homepage multiple times.
Because we see positive usage of the homepage, we will deploy several small features in the next two weeks that help more newcomers discover their homepage (see accompanying image of a feature that helps newcomers discover their homepage from their empty Contributions page).
As listed in our goals above, we'll be starting to focus on adding task recommendations to the newcomer homepage. We'll be publishing early thoughts on this feature so that community members can give their thoughts and advice.
Growth team features are now fully deployed in Arabic Wikipedia and Basque Wikipedia (along with Czech, Korean, and Vietnamese Wikipedias). If your community is enthusiastic about welcoming newcomers, we encourage you to contact us so that we can verify together if your wiki is eligible. Then, go through the checklist to start the process of configuring the features.
We have deployed features that help newcomers find their newcomer homepage. These features were successful, and more than doubled the number of newcomers who find their homepage. In Czech Wikipedia, 72% of newcomers visit their homepage and in Korean Wikipedia, 49% of newcomers visit their homepage.
Several members of the Growth team attended Wikimania in Stockholm. We helped organize a conference track around Community Growth, presented about our team's work, and had many conversations with community members from around the world.
How to match to interests? Research shows that users are more likely to work on articles that are related to their interests. We are currently prototyping methods to ask newcomers their interests and then find articles that match.
How to guide the newcomer? Once a newcomer has selected a recommended article, they will need guidance on how to complete the edit. We have decided to use the help panel to provide that guidance while the newcomer edits.
We are currently engineering on this feature, and we recently published notes from user tests that give mostly positive feedback.
You can explore the design for newcomer tasks in these interactive mockups. We hope to hear from you about your thoughts on the project talk page. Do you think this could be helpful for newcomers? What are we missing?
Expanding to more wikis: the team is preparing to deploy Growth features to Ukrainian and Hungarian Wikipedias. Wikis that already have the features are Czech, Korean, Arabic, Vietnamese, and Basque Wikipedias. If your community is enthusiastic about welcoming newcomers, we encourage you to contact us so that we can verify together if your wiki is eligible. Then you can go through the checklist to start the process of configuring the features.
Mentor training: we tried out our first training for mentors with the Czech community, so that experienced users can build skills that help them retain newcomers.
Mockup of guidance while doing a suggested edit, using the help panel
The help panel was first deployed to newcomers in January 2019, and we have now finished analyzing data to determine its impact. A brief summary is below, and more in-depth information can be found here (in English).
In summary, although we have seen a good amount of usage of the help panel, the help panel has not shown an increase in activation (whether a user makes their first edit) or retention (whether a user returns to edit again).
This is a disappointing result, and our team has discussed potential reasons for the result and ideas for the future. Although we have many ideas for how to improve the help panel, we have decided to keep our attention on the newcomer homepage and newcomer tasks projects for the coming months.
We'll be using the help panel as part of the newcomer tasks project: using it to guide newcomers while they complete suggested edits.
The first version of the newcomer tasks workflow (V1.0) will be deployed in the next weeks on our 4 priority wikis. This version will suggest articles to edit based on maintenance templates. In this first version, we expect many newcomers to initiate the workflow, but not many to select articles to edit or complete edits. We expect future versions of the feature to increase those behaviors.
We're excited about this project because the majority of newcomers visit their newcomer homepage, and this will be the first element of the homepage that clearly asks the newcomer to start editing.
These are the next two versions of the feature, which are already being planned:
V1.1 (topic matching): will allow newcomers to choose topics of interest (such as Art, Music, Sports, or Technology) to personalize their suggestions. After evaluating several approaches, we have decided to use a new ORES model built by the WMF Scoring team. The model will automatically identify the topic area of each article. We expect this to increase how often newcomers select articles to edit.
V1.2 (guidance): once newcomers arrive on an article to edit, we will use the help panel to provide guidance about how to complete the editing task. We expect this to increase how many newcomers actually complete productive edits.
A training for mentors has been published. The training was first tried with the Czech community, and went well.
Growth team features have been deployed to Hungarian, Ukrainian, and Armenian Wikipedias. If your community is enthusiastic about welcoming newcomers, we encourage you to contact us so that we can verify together whether your wiki is eligible. Then you can go through the checklist to start the process of configuring the features.
The results from our user tests showed us that newcomers are likely to do more suggested edits if they can choose articles related to a topic that they're interested in, such as "science", "music", or "sports".
On January 21, we deployed topic matching on our pilot wikis. Newcomers are now using it. We expect it to cause more newcomers to try suggested edits, and to keep making more of them.
In the coming weeks, we will be making improvements to the accuracy of the algorithm used to topic matching, which is part of the ORES project.
Prototype of how the help panel will "peek" from the bottom of the page to offer guidance on mobile.
Because we are seeing positive results from newcomer tasks, the Growth team plans to concentrate our efforts on improving the workflow and encouraging more newcomers to use it.
Guidance: next, we will be using the help panel to provide guidance to newcomers as they do suggested edits, and to prompt them to do another edit after completing their first one. In user tests for this feature, demo videos were one of the favorite features, and we will think about how these might be added.
Starting the workflow: only about 20% of newcomer who visit their homepage begin the newcomer tasks workflow. We are going to be trying out different layouts of the homepage to encourage more newcomers to try newcomer tasks.
Additional task types: we are researching methods to recommend more specific tasks to newcomers, such as specific links to add, or images that could be added to articles from Commons.
ich habe angefangen, die Wikidata-Datenbankeinträge zu den Kulturdenkmalen in Großschönau zu vervollständigen und die teilweise noch fehlenden Commons-Kategorien zu erfassen. Leider ist mir bei der Hauptstraße 81 ein Fehler unterlaufen, ich hatte nicht richtig geschaut und versehentlich die Hauptstraße 81 in Waltersdorf (Ortsteil von Großschönau) statt der gleichen Adresse in Großschönau erwischt. Ich habe die falschen Eingaben wieder gelöscht, allerdings wird in der Wikidata-Infobox auf Commons in der dazugehörigen Kategorie nun das falsche Wikidata-Objekt angezeigt. Kannst Du mir bitte helfen, die Infobox zu korrigieren bzw. weißt Du eine Lösung dafür? Danke und viele Grüße, RoesslerP (talk) 17:26, 8 February 2020 (UTC)
Hallo RoesslerP, du bist sehr fleißig, das ist wunderbar :) . Die Boxen auf Commons unterliegen einer Verzögerung möglicherweise. Bei mir ist es korrekt. Du kannst einmal auf der Commons Seite versuchen, SHIFT auf der Tastatur zu halten und dann auf dem Browser oben auf "Diese Seite neu laden" zu klicken - dann werden alte Daten aus deinem Browser überschrieben. Siehe dazu auch en:Wikipedia:Bypass_your_cache. Ich Grüße dich und auf gute Zusammenarbeit, Conny (talk) 05:03, 10 February 2020 (UTC).
Hallo Conny, danke für das Lob und den Tipp. Viele Grüße, RoesslerP (talk) 15:27, 10 February 2020 (UTC)
There are 13 umgebinde houses on this map section. But the sum of the red dots and the values in the green circles is 27. The value in the green circle corresponds to the number of images for the WD item. Is not it a mistake? Jedudedek (talk) 19:03, 8 March 2020 (UTC)
@Jedudedek: The query has to be optimized with a filter for that. In the past this query showed two points, if there has been twi streets in f. e. czech and german name (two contents). I think we can (should ;) ), fix our query also for pictures. I will check this soon... Regards, nice to meet you, Conny (talk) 07:45, 9 March 2020 (UTC).
@Jedudedek: Use filtered map, so only one house is on map, if there are many pictures. The syntax is wrong, but it works :) . Regards, Conny (talk) 17:22, 18 March 2020 (UTC).
Thanks for treatment. I planned some photography, but it will have to wait. I will try to add WD items to already photographed objects in my free time. Jedudedek (talk) 16:58, 20 March 2020 (UTC)
"dvoulůžkový pokoj" is room with two beds ;-) We'll have to take a good look at the terminology sometimes. I suppose this is a variant of a three-part house. So far I have called it descriptively. Jedudedek (talk) 08:19, 14 April 2020 (UTC)
Sketch of an idea for a structured workflow for adding links to an article. The goal is to help newcomers edit at high volume.
We are looking for community input on a new project to make it easy for newcomers to make real article edits.
In our previous newsletter, we talked about the productive edits coming from the newcomer tasks feature. Those good results have continued: about 900 newcomers made over 5,000 suggested edits so far. We've learned that newcomers are interested in receiving suggested edits.
Now, we are thinking about how to supply them a feed of easy edits that will help more of them be successful quickly. We have a new idea called "structured tasks". This would aim to break down edits into steps that are easy for newcomers and easy on mobile devices.
In the past, certain kinds of editing tasks have been structured. For instance, adding categories through HotCat. Now, we are thinking about how to structure the editing of articles. The goal is to allow newcomers can make large content additions, especially from their mobile devices.
Please visit the project page and respond to the discussion questions listed on the talk page. You are welcome to show this project to others in your community. You can help by translating the materials to your language so that more voices can join in. We will be having this conversation until June 18.
We have expanded to six new wikis, and are looking for more interested communities.
In the last two months, we deployed Growth features to six new wikis: Ukrainian, Serbian, Hungarian, Armenian, and Basque Wikipedias, and French Wiktionary. Newcomers from these wikis have already contributed over 600 edits through Growth features.
We want to expand to more wikis in the coming months, and we are looking for interested communities. French Wikipedia already agreed and will be the next one to join the experiment. We will contact several other wikis in the coming weeks to offer them to participate.
Do you think the Growth Team features would be a good addition to your wiki? Please see this translatable summary of Growth features. You can share with your communities and start a discussion. Then, please contact us to begin the process!
Work continues on improving newcomer tasks and the homepage.
In March, we deployed an upgrade to the topic matching in newcomer tasks. The current version offers 39 different topics using new ORES models.
In April, we completed an A/B test of two homepage configurations. We learned that more newcomers will attempt suggested edits if the module is made more prominent. We are implementing those learnings in our next test. See the full results here.
We are currently working on guidance for newcomer tasks. It will use the help panel to guide newcomers through completing easy edits.
Our next step is to create new configurations of the homepage. The goal is to encourage more newcomers to begin doing suggested edits.
This feature uses the help panel to explain what to do after selecting a suggested edit. For instance, if a newcomer selects a copyedit task, they are guided on what sorts of errors to look for. They can see examples of how to rewrite the text. You can try this feature on test.wikipedia.org. First enable the homepage and the help panel in your preferences there.
Since we launched "Guidance", the data we collected show good results (see image). Now, we see more users completing suggested edits than before Guidance was deployed.
Design concept for the "add a link" structured task
Structured tasks is a project that aims to break down editing workflows into a series of steps. We hope newcomers can accomplish these tasks easily.
In the previous newsletter, we asked for feedback from community members on the idea. We had a good discussion in six languages with 35 community members (summary here). We have now posted new design mockups. We hope community members can check the mockups out and react to them (in any language). They are posted along with some of the main questions we are thinking about as we continue to refine our plans.
We are currently working on Variants C and D (adjacent image) of the homepage. The goal is to increase the number of newcomers who start the newcomer tasks workflow. This is the team's main project at the moment.
We've made it easier to hide the help panel when not needed. 
The welcome survey has a new question for people who created their account: language skills. The goal is to find out how many newcomers know multiple languages, so that we can learn whether it is a good idea to integrate Content Translation as a newcomer task. To make room for this question, we removed one that is not being used. 
Hello. Unfortunately your administrator permissions have been removed because you did not make the required 5 actions in the last 6 months. Thanks for your service! --Rschen7754 18:05, 1 October 2020 (UTC)
Thank you. Conny (talk) 23:09, 2 October 2020 (UTC).
So yesterday we exceeded the limit of 6000 items of umgebindehouse! We exceeded the limit of 5000 items at the end of August. 1000 items in two months! Now just keep up the pace ;-) Jedudědek (talk) 18:29, 28 October 2020 (UTC)
Your are so great man. I moved my house, so I searched my time ;) . The work of the last 7 years shows results now. Thank you very very much, your work is so impressive @Jedudedek, RoesslerP, Cieslak Jürgen, Karl_Gruber: Have a nice time, lets finish this ;) . Regards from Bautzen, Conny (talk) 06:35, 29 October 2020 (UTC).
Jsi tak skvělý muž. Přesunul jsem svůj dům, takže jsem hledal svůj čas;). Práce posledních 7 let nyní ukazují výsledky. Velice vám děkuji, vaše práce je tak působivá. Příjemně se bavte, dokončete to;). S pozdravem Budyšín, Conny (talk) 06:35, 29 October 2020 (UTC).
Ihr seid wunderbar. Ich bin umgezogen, also habe ich meine Zeit gesucht;). Die Arbeit der letzten 7 Jahre zeigt jetzt Ergebnisse. Vielen Dank, eure Arbeit ist so beeindruckend. Viel Spaß, lasst uns das beenden;). Grüße aus Bautzen, Conny (talk) 06:35, 29 October 2020 (UTC).
Variants C and D are two new arrangements of the newcomer homepage.
We hope they will increase the number of users using suggested edits.
They both make suggested edits the clear place where newcomers should get started on the page.
They have some differences in their workflows, because we want to test which design is better.
We deployed these variants on October 19; half of newcomers get each variant.
After about 5 weeks, we will analyze the data from the tests.
The goal is to determine which variant is helping more newcomers to make more suggested edits.
We will identify the better variant and then use it with all newcomers.
As we discussed in previous newsletters, the team is working on our first "structured task": the "add a link" task.
After community discussion on design ideas, we ran user tests on the mobile designs.
We decided on the design concept we want to use moving forward: Concept A.
We're now engineering the backend for this feature.
Next, we will be running user tests for desktop designs.
The team recently published our analysis of the impact of newcomer tasks. We are happy to announce that we found that the Growth features, and particularly newcomer tasks, lead to increased editing from newcomers.
In November 2019, the Growth team added the "newcomer tasks" feature to the newcomer homepage. After six months, we collected data from Arabic, Vietnamese, Czech, and Korean Wikipedias. We analyzed the overall impact of the Growth features, including newcomer tasks.
This analysis finds that the Growth features lead to increases in:
the probability that newcomers make their first article edit (+11.6%)
the probability that they are retained as editors
the number of edits they make during their first couple of weeks on the wiki (+22%)
We also find that the quality of their edits, as measured by revert rate, is comparable to that of a control group.
The number of suggested edits completed by each wiki each week, going from December 2019 to November 2020, with a line for the total.
The number of distinct users completing suggested edits by each wiki each week, going from December 2019 to November 2020.
Variants C and D are two new arrangements of the newcomer homepage. We deployed them in October. After six weeks of these variants being deployed, we can see that they have led to increased interactions with newcomer tasks. Next, we will determine which variant is best and use that for all newcomers.
Mentors are volunteers ready to help newcomers in their first steps. Newcomers can contact them using the mentorship module on their homepage.
A separate list for workshops hosts
During workshops organized by education programs through the communities, workshops hosts like to mentor people they train on wiki. Several wikis requested to have a way to claim their mentees without having other newcomers being randomly being assigned to them. To address this need, a separate list can be created on wiki, for mentors that wish to claim mentees, but prefer not to have random mentees being assigned to them. Learn more about this feature.
Claiming multiple mentees at once
Mentors can use Special:ClaimMentee to claim a newcomer as their mentee. The feature now allows mentors to claim multiple newcomers at once.
The help panel allows people to post a message to the local help desk while editing. Previously, the tool always posted messages to the bottom of help desks. Wikis are now able to configure it to display new messages at the top of the help desk page. T261714