User talk:GualdimG

Welcome to Wikidata, GualdimG!

Wikidata is a free knowledge base that you can edit! It can be read and edited by humans and machines alike and you can go to any item page now and add to this ever-growing database!

Need some help getting started? Here are some pages you can familiarize yourself with:

Introduction – An introduction to the project.
Wikidata tours – Interactive tutorials to show you how Wikidata works.
Community portal – The portal for community members.
User options – including the 'Babel' extension, to set your language preferences.
Contents – The main help page for editing and using the site.
Project chat – Discussions about the project.
Tools – A collection of user-developed tools to allow for easier completion of some tasks.

Please remember to sign your messages on talk pages by typing four tildes (~~~~); this will automatically insert your username and the date.

If you have any questions, don't hesitate to ask on Project chat. 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.

Best regards! Jon Harald Søby (talk) 23:15, 28 September 2017 (UTC)[reply]

Merging items

Hallo GualdimG,
When you (want to) merge items, you may want to use the merge.js gadget from help page about merging. It helps with merging, gives the option to always keep the lower number (which is older, so preferable in most cases) and removes the need to file a request on Wikidata:Requests for deletions.
With regards,- cycŋ - (talk • contribs • logs) 15:17, 7 December 2018 (UTC)[reply]

What was the first

Regardless of Q72618772 being earlier it was merged into the Q73760983. This is recurrent with the same editor. GualdimG 16:37, 31 December 2020 (UTC)

Why do you consider this a problem? Where did you discuss the issue with the editor previously (if you didn't it's the next step and not the admin noticeboard)? User:ChristianKl 01:42, 2 January 2021 (UTC)

Whenever I try to merge two items, I get prompted to merge from the oldest. If "this is not a problem", why is there this rule to merge? But whenever I notice, in the case of the items created by me, the editor merges from the item that I did not create. This is the behavior of the editor and I cannot change it. Perhaps an administrator. GualdimG07:12, 2 January 2021 (UTC)

This is the third time that I have presented the same type of question here, always due to the same editor. The first time, the editor was called into the discussion, but gave no answer. An administrator, at my request, reversed his action. The second time, as far as I know, nothing was done. This time, the subject goes the same way. I would say that crime pays off. For some (the majority) the rules apply, for others it is discretion. GualdimG 10:56, 3 January 2021 (UTC)

location (P276) usage

Hi GualdimG, I noticed you changed the location on San Gallo Annunciation (Q1241129) from Galleria Palatina (Q866498) to Florence (Q2044). For location we try to use the most exact location so you shouldn't put the city in there, but the gallery or museum it's in. It can be quite precise. For example the The Night Watch (Q219831) is in location Nightwatch hall (Q25845794). Multichill (talk) 21:02, 18 March 2019 (UTC)[reply]

OK, @Multichill: In many times we are repeating the Location and the Collection. When I had made some Lists of paintings the two columns about Location and Collection are the same. I think is more useful have the two values imediately visible. But, if you prefer the two same values I sugest we can put another value, in the location, for the city. I am sorry, had made same changes over the time, changing for the location, the city for the museu, because, as I had said, the museum is already named as the collection. Greetings, GualdimG (talk) 21:13, 18 March 2019 (UTC)[reply]

Call for participation in a task-based online experiment

Dear GualdimG,

I hope you are doing well,

I am Kholoud, a researcher at King's College London, and I am working on a project as part of my PhD research, in which I have developed a personalised recommender model that suggests Wikidata items for the editors based on their past edits.

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 model 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 should take no more than 15 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

Then, 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 Kholoudsaa (talk) 16:55, 17 February 2023 (UTC)[reply]

Incorrect use of instance of (P31)

Hello –

This statement on "Q122211991" (Q122211991) was incorrect, and I have removed it. Errors with instance of (P31) and subclass of (P279) lead to numerous false inferences, in this case including Q122211991instance of (P31)process (Q3249551). When using instance of (P31) and subclass of (P279), check the description of your value item, and make sure the statement is valid per Help:Basic membership properties. (In this case, the item is used for a process, but it wouldn't make sense to say it is that process.) There is often another property that can accurately express the relationship you had in mind; in this case, has use (P366) works better. You can search through available properties here. Thanks! Swpb (talk) 21:34, 17 November 2023 (UTC)[reply]