Koxinga

Bonjour Koxinga. Je sui très déçu de ta fusion depuis Goze (Q113611491) vers Goze (Q79696120). En effet, tu as conservé l'élément le plus ancien qui indiquait rivière de France (et c'est tout) au détriment de mon travail de mise à jour complet de ce cours d'eau sur Wikidata et donc mes apports n'apparaissent plus du tout dans l'historique. Il y a d'ailleurs un souci avec Goze (ruisseau) (Q113836108) qui est encore un doublon.

Garder l'élément le plus ancien est simplement l'option par défaut, je ne l'ai pas changée. N'hésite pas à annuler le changement et faire le merge dans l'autre sens si tu préfères. Pour moi l'important est le résultat, pas l'historique.

L'option par défaut n'est pas toujours la meilleure et peut être modifiée lors de la fusion. L'historique représente le travail effectif des participants. Remplacer par l'élément où figure seulement la participation de deux personnes qui ont indiqué pour l'une que c'était une rivière, et pour l'autre qu'elle était en France, alors que pour l'autre élément, j'avais indiqué la nature réelle de l'élément (ruisseau), sa localisation administrative, les libellés et description en trois langues, la catégorie commons, le bassin versant, la longueur, l'image et l'identifiant du Sandre.

Je ne vais pas rectifier ton travail mais j'espère qu'à l'avenir tu prendras le temps de regarder les historiques avant de fusionner dans la rapidité. Cordialement.

Dear Koxinga,

I hope you are doing good,

I am Kholoud, a researcher at King's College London, and I work on a project as part of my PhD research, in which I have developed a personalised recommender system that suggests Wikidata items for the editors based on their past edits. I am collaborating on this project with Elena Simperl and Miaojing Shi.

I am inviting you to a task-based study that will ask you to provide your judgments about the relevance of the items suggested by our system based on your previous edits.

Participation is completely voluntary, and your cooperation will enable us to evaluate the accuracy of the recommender system in suggesting relevant items to you. We will analyse the results anonymised, and they will be published to a research venue.

The study will start in late January 2022 or early February 2022, and it should take no more than 30 minutes.

If you agree to participate in this study, please either contact me at kholoud.alghamdi@kcl.ac.uk or use this form https://docs.google.com/forms/d/e/1FAIpQLSees9WzFXR0Vl3mHLkZCaByeFHRrBy51kBca53euq9nt3XWog/viewform?usp=sf_link

I will contact you with the link to start the study.

For more information about the study, please read this post: https://www.wikidata.org/wiki/User:Kholoudsaa

In case you have further questions or require more information, don't hesitate to contact me through my mentioned email.

Thank you for considering taking part in this research.

Regards

Hello.

Could you create the article en:Lists of Azerbaijani films and en:Template:Azerbaijan film list in Chinese?

Thank you.

It appears that "Kinema Junpo award" (Q13601550) & "Kinema Junpo award" (Q28059044) are identical. Any reason that they should not be merged? ~~~~

No reason, you are right. I merged them.

In RFD there are one or more item proposed for the deletion created by you. If you do not agree you can participate in the debate

(That message in other languages: العربية • ‎bosanski • ‎català • ‎Deutsch • ‎Esperanto • ‎français • ‎עברית • ‎polski • ‎português • ‎português do Brasil • ‎русский • ‎اردو • ‎中文 – ‎translate that message)

Hello!

Like some other community members, you are using Flow.

An increasing number of communities now use Flow or are considering it. Although Flow itself is not scheduled for major development during 2016 fiscal year, the Collaboration Team remains interested in the project and in providing an improved system for structured discussions.

You can help us make decisions about the way forward in this area by sharing your thoughts about Flow — what works, doesn't work or should be improved?

Please fill out this survey (available in multiple languages), which is administered by a third-party service. It will not require an email or your username. See our privacy statement.

Thanks for your ideas and opinions about Flow!

Trizek (WMF), on behalf of the Collaboration team, 11:56, 7 September 2016 (UTC)

I reverted your change to human who may be fictional (Q21070568). We have gone to a lot of trouble to separate 'fictional humans' from 'humans' so that a search on human (including subclasses) doesn't throw up any fictional characters. Making "human who may be fictional" a subclass of:human messes this up. "said to be the same as" does the job of linking these two items - that is what it was created to do.

Understood. However this means that all the instances of Q21070568 will cause constraints violations when the domain is defined as human (Q5), fictional character (Q95074) (for example for the family relationships like Property:P7, Property:P9 etc.). Is it normal and expected? Does this mean the domain should be extended?

as Q21070568 is neither fictional nor non-fictional then I guess the constraints do need to be changed to add Q21070568 to the domain.