Shortcuts: WD:PC, WD:CHAT, WD:?

Wikidata:Project chat

From Wikidata
(Redirected from Wikidata:Pc)
Jump to navigation Jump to search

Wikidata project chat
A place to discuss any and all aspects of Wikidata: the project itself, policy and proposals, individual data items, technical issues, etc.

Please use {{Q}} or {{P}} the first time you mention an item or property, respectively.
Other places to find help

For realtime chat rooms about Wikidata, see Wikidata:IRC.
Start a new discussion
Edit
On this page, old discussions are archived after 7 days. An overview of all archives can be found at this page's archive index. The current archive is located at 2024/09.

Populated places and their industries

[edit]

My interest is in using Wikidata to capture and present aspects of Scottish history. After a recent conversation about the decline of the Scottish fishing industry, I looked at the available data. Petscan gives a decent category-based list of towns [1], but the place items themselves (e.g. Eyemouth (Q1020260)) lack any data association with fishing.

Looking around, I can see some use of instance of (P31) fishing village (Q1317251) but that seems inappropriate for say Aberdeen. There is also occasional use of industry (P452) on a place (e.g. Bonon (Q2910327), but with warnings that it breaches the Subject Type Constraint, as the property is reserved for use on companies, etc.

I wonder if there is another property to capture the industries of a place? If not, should there be? Or should the use of P452 be relaxed to allow its use for populated places? It strikes me that this or some other Property can underpin a richer understanding of what forms of work activity led to a town emerging/declining: fishing, weaving, salt panning, etc. AllyD (talk) 13:02, 15 August 2024 (UTC)[reply]

I'd relax the use of industry (P452) Vicarage (talk) 05:47, 19 August 2024 (UTC)[reply]
Thanks for that response; unless someone suggests a more appropriate info structure, I will take this forward to a proposal at Property talk:P452. AllyD (talk) 07:09, 25 August 2024 (UTC)[reply]

Rendering of coordinate values

[edit]

Hi, please have a look at [2]. The values for the two coordinate location (P625) are almost the same (+- 4 meters), but the value displayed in D/M/S format differs a lot (by ~40"N and ~20"E). The real difference is the different precision. It is strange when we add the same decimal value but get quite different values in D/M/S format. I consider this to be a flaw. --Herzi Pinki (talk) 16:44, 21 August 2024 (UTC)[reply]

That's because of the precisions. In Wikibase, the precision determines how precisely the coordinates should be displayed. Without it, it doesn't know whether a value of "1" is intended to be to the nearest degree (i.e. 1°), the nearest minute (i.e. 1° 0'), or even the nearest 0.001 seconds (i.e. 1° 0' 0.000"). A precision of 0.013482119238374° means to the nearest 48.5 seconds, approximately, so that's what it rounds it to. The result is strange because the data itself is strange.
- Nikki (talk) 05:58, 29 August 2024 (UTC)[reply]

Wikidata birthday events & microgrants

[edit]

Hello all,

As a reminder, the microgrant program proposed by Wikimedia Deutschland to support Wikidata birthday events is still running. You can apply until September 1st at 23:59 UTC. You'll find all the relevant information on this page, feel free to reach out to me if you have any question or issue.

If you know Wikidata groups who may need support to organize a birthday celebration event, feel free to share this message with them!

We are also running organizers calls to answer questions about organizing events and grants. The next one is taking place on August 28th at 18:00 UTC. Feel free to join if you have questions or would like to share your event plans with other organizers.

Best, Lea Lacroix (WMDE) (talk) 07:51, 26 August 2024 (UTC)[reply]

Special rules for Wikinews categories?

[edit]

Hello! As I understand it, there is a general rule in Wikidata that if an item has its own category in at least 1 Wikimedia project (except Commons), then we create a separate item for the category and then we link all categories from around Wikimedia to this "category item" (example: Poland (Q36) is Poland and Category:Poland (Q1455901) is Category:Poland). However, my fellow Polish wikimedian Marek Mazurkiewicz has just pointed out to me that this rule does not apply to Wikinews. Apparently, Wikinews categories should be linked directly to the main item. Could anyone else please confirm that there is such an exception (and what are the reasons for that, if you know them?). Thank you in advance. Powerek38 (talk) 08:16, 26 August 2024 (UTC)[reply]

Yes, I can confirm this. The reason is that for Wikinews a category is the basic object, they do not have an analog of a Wikipedia article (a single news is not such an analog). Ymblanter (talk) 17:55, 26 August 2024 (UTC)[reply]

Source the item itself

[edit]

Could be the source the item itself? Let me give you an example. I add the item (let say Qfoo) of a certain book version, edition or translation (Q3331189) that it was printed 10 000 times. Can I reference total produced (P1092): 10 000 by the item I am in (Qfoo)? Juandev (talk) 09:55, 26 August 2024 (UTC)[reply]

References should be outside the Wiki* system, because of the "no original work" rule means they are just collating information, not defining it. So not only is Wikidata not a valid reference, nor is English Wikipedia, though the latter rule is often abused by bots. Vicarage (talk) 10:11, 26 August 2024 (UTC)[reply]
But this is not using Wikidata as a reference - books themselves often state how many exemplars were printed, so in this case it seems fine (to me) to use stated in (P248) with the item itself Uniwah (talk) 10:17, 26 August 2024 (UTC)[reply]
I think you are right. https://www.wikidata.org/wiki/Help:Sources#Books Vicarage (talk) 10:37, 26 August 2024 (UTC)[reply]
That is an interesting point. As books looks like a special case, because they include lots of standardized informations about themselves. Juandev (talk) 10:39, 26 August 2024 (UTC)[reply]

Mix'n'Match

[edit]

Anyone else have trouble loading https://mix-n-match.toolforge.org/#/? I'm either stuck infinitely loading a blank page or just the page being blank

Only way i have managed to access the site is by using an URL like https://mix-n-match.toolforge.org/?#/search/<insert anything here> Trade (talk) 11:18, 26 August 2024 (UTC)[reply]

Even when searching and matching entries it takes a really, really long time Trade (talk) 11:24, 26 August 2024 (UTC)[reply]

"The Future of Wikidata Events" Report Now Available on Wikimedia Commons

[edit]

Hello,

We are excited to announce the release of the "The Future of Wikidata Events" report, now available on Wikimedia Commons. This report provides valuable insights into the current state and future possibilities of Wikidata events.

Context and Purpose
Over the past several months, we conducted an in-depth review of Wikidata events, gathering feedback from community members, event organizers, and stakeholders. Our goal was to understand the strengths and challenges of these events and explore how they can better serve the Wikidata community moving forward.

This report is the culmination of that research. It highlights key findings, offers a comprehensive analysis of past events, and outlines potential directions for the future. While specific changes are still being determined, this report will serve as a foundation for future discussions and decisions.

Highlights of the Report

  • Objective: Investigates the range of possibilities and alternatives to the current formats, with emphasis on inclusivity, environmental sustainability, accessibility, and accommodating the varied requirements of different communities worldwide.
  • Community Feedback: Reflects a wide range of opinions and experiences from community members worldwide, ensuring a balanced and inclusive overview.
  • Strategic Opportunities: Identifies key opportunities for enhancing community support, engagement, and retention through innovative event formats.

What’s Next for Wikidata Events?

  • Adapting to Community Needs: We are committed to evolving our event formats to better meet the needs of our diverse community, including exploring both online and onsite models that foster deeper connections while maintaining broad accessibility.
  • Upcoming Changes: While we are excited about the potential changes highlighted in the report, specific changes are still being finalized. Final recommendations and any resulting changes will be communicated later this year.
  • Continuous Improvement: We will continue to seek feedback and work collaboratively with the community to ensure our events remain inclusive and impactful.

Your Feedback Matters
We encourage you to review the report and share your thoughts. Your feedback will play a crucial role in shaping the future of Wikidata events. Please don't hesitate to reach out with questions, discuss with each other, or provide general feedback regarding the report at Wikidata talk:Events#"The Future of Wikidata Events" Report Now Available on Wikimedia Commons.

We believe this report is a significant step towards creating a more inclusive and supportive environment for all members of the Wikidata community. We look forward to working with you to shape the future of our events together.

Cheers! -Mohammed Abdulai (WMDE) (talk) 12:29, 26 August 2024 (UTC)[reply]

Wikidata weekly summary #641

[edit]
Here's your quick overview of what has been happening around Wikidata over the last week.
This is the Wikidata summary of the week before 2024-08-26. Please help Translate.

Discussions

  • Open request for adminship:
    • Gwanki - RfP scheduled to end after 26 August 2024 05:54 (UTC)
    • Putnik 2 - RfP scheduled to end after 27 August 2024 23:17 (UTC)
  • Closed request for adminship: Both requests successful, welcome new admins: Mohammed Qays and Wüstenspringmaus!
  • New requests for permissions/Bot: Leaderbot - Task/s: reminds users when their rights are to expire (see Phab:T370842)
  • Closed request for permissions/Bot: Bot5958 1b - RfP successful!
  • New request for comments:

Events

Press, articles, blog posts, videos

Tool of the week

Other Noteworthy Stuff

  • New AI Project Manager to join Wikimedia Deutschland: We’re pleased to announce that a new AI project manager will be joining our team next week. Lydia and Jonathan (Director of Engineering) have been prototyping in this area and recently presented their work at the AI_dev summit (YouTube link). Our goal is to bring knowledge graphs and generative AI closer together, making AI more equitable, truthful, participatory, and open. More updates to come soon!

Newest properties and property proposals to review

You can comment on all open property proposals!

Did you know?

Development

  • Not much happened this week. Many of the developers are still on vacation, and some are out sick.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Weekly Tasks

Thanks for providing this :) So9q (talk) 05:27, 1 September 2024 (UTC)[reply]

Wiping 賀錦麗 off the aliases in Kamala Harris (Q10853588)

[edit]

Is there someone who could and would be willing to wipe 賀錦麗 off the nearly 100 remaining aliases it does not belong on on Kamala Harris (Q10853588)? Thanks. - Yupik (talk) 06:52, 27 August 2024 (UTC)[reply]

Why did nobody revert the bot that added these in a single edit? Would have been much easier. Sjoerd de Bruin (talk) 08:34, 27 August 2024 (UTC)[reply]
No idea, but it wouldn't let me anymore since other people had been deleting them off individually. - Yupik (talk) 10:24, 27 August 2024 (UTC)[reply]
This may be part of the problem: Q10853588#P742 RVA2869 (talk) 08:43, 27 August 2024 (UTC)[reply]
Thanks for deleting them! - Yupik (talk) 10:25, 27 August 2024 (UTC)[reply]

SPARQL to connect any two Qs

[edit]

Inspired by six degrees of separation (Q2855754), I am just wondering if there is a general SPARQL statement to connect any two entities. The key part is wildcard for Ps. Thanks

Think of Wikidata as directed graph as it is, Qs are nodes and Ps (as main properties and qualifiers) are edges. There are 2 versions :

(a) treat it as directed graph, with example : −1 (Q310395) instance of (P31) integer (Q12503) studied in (P2579) number theory (Q12479) and

(b) as Undirected graph , like between integer (Q12503) and real number (Q12916) via type of number (Q47460393)

Thanks. JuguangXiao (talk) 07:27, 27 August 2024 (UTC)[reply]

You can use RDF GAS API to query the number of steps between two items using some properties (directed or undirected), for example. However (1) RDF GAS API is a Blazegraph extension, and since WDQS will move out of Blazegraph (as it is abandonware), such feature will discontinue in some point; (2) It is not scalable for all of Wikidata items - the query example use child (P40) as undirected graph, and child (P40) is used in a little fewer than one million items, where the entire Wikidata has more than 100 million items; even with such number of items, the query often fails or timeouts so you need to try it multiple times before getting a result.--GZWDer (talk) 12:17, 27 August 2024 (UTC)[reply]

Fictional location from work vs. Fictional location in work

[edit]

Which one of the two descriptions is the better one to use? Trade (talk) 13:28, 27 August 2024 (UTC)[reply]

terrorist (Q12414919) being a subclass of political activist (Q11499147)

[edit]

This seems like a bit of a stretch or is that just me? Trade (talk) 16:42, 27 August 2024 (UTC)[reply]

Doesn't seem far-fetched to me. Do terrorists not seek political or social change? One man's freedom fighter is another man's terrorist. -Animalparty (talk) 01:41, 28 August 2024 (UTC)[reply]

Q2842000 is missing some info

[edit]

Ambazonia (Q2842000) has quite a ton of missing info. The presidents for example, need to have things identifying that they are "The President of the Interim Government". Remember, there are many factions. Also, you gotta have two new presidents in the "head of state" section; Marianta Njomia and Chris Anu.
And also, you need to add the vice presidents of the four. Dabney Yerima for Ayuk Tabe, Eric Ateh for Sako, Hariscine Abongwa for Marianta, and Rev Njini for Chris.
Since we're assuming that that page is just for the Interim Government and nobody else, there are three sites you need to put in there: "statehousebuea.org" for Sako, "federalrepublicofambazoniagov.org" for Marianta, and "ambazoniagov.org" for Chris Anu. Make it so that the link to ambagov.org leads to an archive of the page too.
People also seem to sometimes erroneously call the Interim Government's state not as the Federal Republic of Ambazonia, but as the Republic of Ambazonia. Not to be confused with the faction "Republic of Ambazonia". Gotta add that to the "also known as" part of the page.
The emblem of Ambazonia shouldn't be here too. I've read the constitution and I can provide an exerpt from it, Article 4, Section 4: "The national coat of arms shall be an escutcheon supported by two crossed fasces with the motto 'JUSTICE-UNITY-DEMORACY'. The escutcheon shall be composed of two gold stars and triangle gules, charged with the geographical outline of Ambazonia in azure and surcharged with the scales of Justice." (hold on, did copy-pasting this exerpt from the constitution break the rules?)
And guess what, Sako changed the coat of arms of the interim government at the start of 2024, and the constitution Sako made isn't even ON the web.
So since the two coat of arms of the IG haven't been uploaded to Wikicommons yet, let's just use the seals of the Interim Government.
Ambazonia also left the UNPO in 2021, it seems.
But everything else seems fine. Please try to edit the things described in this post into the Ambazonia Wikidata page. Thanks. Kxeon (talk) 13:36, 10 August 2024 (UTC)[reply]

Moved this section back to PC.

--Wüstenspringmaus talk 09:26, 28 August 2024 (UTC)[reply]

@Wüstenspringmaus: Wikidata operates under the Open-world assumption - "lack of knowledge does not imply falsity", or in other words, every item in Wikidata is missing info. But it's also a wiki. Editing should be done by people who are knowledgeable on the subject. Is there some reason why you are unable to add this information yourself? ArthurPSmith (talk) 17:28, 28 August 2024 (UTC) @Kxeon: sorry, I pinged the wrong person there. ArthurPSmith (talk) 17:29, 28 August 2024 (UTC)[reply]
@ArthurPSmith: Kxeon is unable to edit the item because it's semi-protected. --Wüstenspringmaus talk 19:00, 28 August 2024 (UTC)[reply]
@Wüstenspringmaus Maybe @Kxeon should edit some more (non-semi-protected pages) to become auto-confirmed.
Wikidata:Autoconfirmed users RVA2869 (talk) 16:59, 29 August 2024 (UTC)[reply]

possibly same organization

[edit]

I would be very surprised if Institute for Security Studies (Q18126017) and Institute for Security Studies (Q61931531) are distinct organizations (same name, same year of inception, same web domain for their official sites) and would not be at all surprised if Institute for Security Studies (Q74432455) is also the same. I'd want to add said to be the same as (P460), but may I do that without a citation? - Jmabel (talk) 23:11, 28 August 2024 (UTC)[reply]

So the first two items have different ROR ID (P6782) values, and their entries in ROR would indicate that Q61931531 is a child organisation of Q18126017 which would make sense as the latter is described as their "head office" and the former a "regional office" on their website. So perhaps tying them together using parent organization (P749) or part of (P361) would be better than said to be the same as (P460)? M2Ys4U (talk) 01:42, 29 August 2024 (UTC)[reply]
I merged Institute for Security Studies (Q74432455) into Institute for Security Studies (Q18126017) as they are surely the same. Institute for Security Studies (Q61931531) is said to be in Kenya, so it may be related but it is definitely not the same as the South African institution, assuming that location is correct. ArthurPSmith (talk) 19:29, 29 August 2024 (UTC)[reply]

Property:P1813 short name with countries

[edit]

The usage of this property differs from language to language. Looking at USA and UK, some write their form of "USA", while others write "United States" (hence UK and United Kingdom). I'm looking for a more or less reliable field to retrieve a short name (not an abbreviation!) and I'm asking myself if this would be the one, I could use for that. UK I would rather expect at international license plate code or something. I changed it for English and German in the UK and the US, but now I start to worry, that this might cause problems elsewhere. I would also like to change the value at Holy Roman Empire to Holy Roman Empire instead of HRE. Any advice on the topic? Flominator (talk) 05:10, 29 August 2024 (UTC)[reply]

Also states, like Kentucky, use it as KY, where I would have expected just "Kentucky" as opposed to the official name "State of Kentucky". Of course, I could also use the label, but that would be another API call. The claims I already have at hand at that point. --Flominator (talk) 05:35, 29 August 2024 (UTC)[reply]

Looking at the examples of this property, both abbreviation and "short text but not abbreviated" look to be both accepted https://www.wikidata.org/wiki/Property:P1813#P1855 Bouzinac 💬●✒️●💛 08:05, 29 August 2024 (UTC)[reply]
Its aliases "acronym" and "initialism" do make it ambiguous. Splitting off an "acronym" property might be best. Mind you, that wouldn't help the OP who naturally refers to USA and US in their post, as we all do, UK/GB are a muddle, and you'd code UK as both a short form and an acronym, and no-one has attempted to unravel Foreign, Commonwealth and Development Office (Q358834) !! Vicarage (talk) 08:22, 29 August 2024 (UTC)[reply]
Actually, it would help him a lot, because he could go then and set "United States" and "United Kingdom" as value for this property without getting his butt kicked (or at least to defend himself with a line of argumentation, in case it happens anyway). Flominator (talk) 09:01, 29 August 2024 (UTC)[reply]
Unfortunately, it looks like your proposal has been tried already in January of this year: Wikidata:Property proposal/abbreviation --Flominator (talk) 09:13, 29 August 2024 (UTC)[reply]
That proposal was very confused. What we'd want is 'initialism' ('acronym' is a a pronounceable word), but as Michael Caine would say, not a lot of people know that. But its not something that impacts me. Vicarage (talk) 16:52, 29 August 2024 (UTC)[reply]
Thanks. Let's hope Wikidata:Property proposal/initialism is less confused. --Flominator (talk) 10:03, 30 August 2024 (UTC)[reply]
That sounds like what the label is for. The label is supposed to be the name the item is most commonly known by (see Help:Label). We normally use official name (P1448) for the long/formal name. I don't know why United States of America (Q30) has the formal name as the label, even the English Wikipedia article is "United States". - Nikki (talk) 05:28, 1 September 2024 (UTC)[reply]

Settlement population by ethnic group

[edit]

I'm trying to find a good way to add the population of specific settlement (village, town, city) by ethnic group. I tested with Blagoevgrad (Q173277). I added statement ethnic group (P172), set it to Bulgarians (Q133255) and added qualifiers determination method (P459) with census (Q39825), point in time (P585) with the census year & quantity (P1114) with the number of citizens from that ethnical group. What I'm concerned is if ethnic group (P172) could be a statement at all for that object and is there better way to structure this data? StanProg (talk) 15:32, 29 August 2024 (UTC)[reply]

I would use population (P1082) but with qualifiers applies to part (P518) always having ethnic group (Q41710) as object and ethnic group (P172) having the particular ethnic group as object. Also each statement should have a reference to the census from which the data comes from. here is a sample statement on the same wikidata item. --Nikola Tulechki (talk) 15:49, 29 August 2024 (UTC)[reply]
That's what I would have suggested, but a different structure is used for places in North Macedonia (example: Q2862113). The ethnic group property is still used as the main statement, but since 2020 has linked to new items that are instances of ethnic group by settlement in Macedonia (Q106474968) instead of including the numbers directly in the item, although there are issues such as duplication of Macedonian cadastral municipality ID (P8542) values, and use of of (P642) (which could be improved by using located in statistical territorial entity (P8138) or located in the administrative territorial entity (P131) to link directly to the village Armatuš (Q2862113) (which should be an instance of cadastral municipality of North Macedonia (Q98497401) or whatever represents its administrative or statistical status). I don't know if there was a reason for the use of Q106474968 and could not find anything similar for other countries (although most just have population statements for different years. Peter James (talk) 16:04, 29 August 2024 (UTC)[reply]
OMG, that's bad. I can't believe they did this. It works, but it goes against Wikidata's philosophy and creates a boatload of items which have no other function than to "hold" the value. At least they didn't create a new one for each census, just for each settlement-ethnic group combination :). And I see no point whatsoever in modelling it this way, compared to the solution above. I might write to the North Macedonia Wikidata community and propose to harmonize the representation and free up several hundred thousand precious triples in the graph. --Nikola Tulechki (talk) 17:50, 29 August 2024 (UTC)[reply]

UK Parliament Image ID property

[edit]

Hi. Do we have a property describing the ID as here? If not, would it be useful to use it in Commons SDC? DaxServer (talk) 19:55, 30 August 2024 (UTC)[reply]

Mass-import policy

[edit]

Hi I suggested a new policy similar to OpenSteetMap for imports in the telegram chat yesterday and found support there.

Next steps could be:

  • Writing a draft policy
  • Deciding how many new items users are allowed to make without seeking community approval first.

The main idea is to raise the quality of existing items rather than import new ones.

I suggested a limit of 100 items or more to fall within this new policy. @nikki: @mahir256: @ainali: @kim: @VIGNERON: WDYT? So9q (talk) 12:11, 31 August 2024 (UTC)[reply]

@So9q: 100 items over what time span? But I agree there should be some numeric cutoff to item creation (or edits) over a short time period (day, week?) that triggers requiring a bot approval at least. ArthurPSmith (talk) 00:32, 1 September 2024 (UTC)[reply]
QuickStatements sometimes returns the error message Cannot automatically assign ID: As part of an anti-abuse measure, this action can only be carried out a limited number of times within a short period of time. You have exceeded this limit. Please try again in a few minutes.
M2k~dewiki (talk) 02:07, 1 September 2024 (UTC)[reply]
Time span does not really matter, intention does.
Let me give you an example: I recently imported less than 100 banks when I added Net-Zero Banking Alliance (Q129633684). I added them during 1 day using OpenRefine.
Thats ok. It's a very limited scope, we already had most of the banks. It can be discussed if the new banks which are perhaps not notable should have been created or just left out, but I did not do that as we have no policy or culture nor space to talk about imports before they are done. We need to change that.
Other examples:
  • Importing all papers in a university database or similar totaling 1 million items over half a year using automated tools is not ok without prior discussion no matter if QS or a bot account was used.
  • Importing thousands of books/monuments/whatever as part of a GLAM project over half a year is not ok without prior discussion.
  • Importing all the bridges in the Czech Republic e.g. Q130213201 during whatever time span would not be ok without prior discussion. @ŠJů:
  • Importing all hiking paths of Sweden e.g. Bohusleden (Q890989) over several years would not be ok.
etc.
The intention to import many object without prior community approval is what matters. The community is your boss, be bold when editing but check with your boss before mass-imports. I'm pretty sure most users would quickly get the gist of this policy. A good principle could be: If in doubt, ask first. So9q (talk) 05:16, 1 September 2024 (UTC)[reply]
@So9q: I'm not sure that the mention of individually created items for bridges belongs to this mass import discussion. There exist Wikidata:Notability policy and so far no one has questioned the creation of entries for physically existing objects that are registered, charted, and have or may/should have photos or/and categories in Wikimedia Commons. If a community has been working on covering and processing any topic for twenty years, it is probably not appropriate to suddenly start questioning it. I understand that what is on the agenda in one country may appear unnecessarily detailed in another one. However, numbered roads, registered bridges or officially marked hiking paths are not a suitable example to question; their relevance is quite unquestionable.
The question of actual mass importation would be moot if the road administration (or another authority) published the database in an importable form. Such a discussion is usually led by the local community - for example, Czech named streets were all imported, but registered addresses and buildings were not imported generally (but individual items can be created as needed). Similarly, the import of authority records of the National Library, registers of legal entities, etc. is assessed by the local community; usually the import is limited by some criteria.. It is advisable to coordinate and inspire such imports internationally, however, the decision is usually based on practical reasons, i.e. the needs of those who use the database. It is true that such discussions could be more transparent, not just separate discussions of some working group, and it would be appropriate to create some formal framework for presenting and documenting individual import projects. For example, creating a project page that will contain discussion, principles of the given import, contact for the given working group, etc., and the project page should be linked from edit summaries. --ŠJů (talk) 06:03, 1 September 2024 (UTC)[reply]
Thanks for chipping in. I do not question the notability of the items in themselves. The community in telegram has voiced the opinion that this whole project has to consider what we want to include and not and when and what to give priority.
Millions of our current items are in a quite sad state as it is. We might not have the man-power to keep the level of quality at an acceptable level as is.
To give you one example Wikidata currently does not know what Swedish banks are still in operation. Nobody worked on the items in question, see Wikidata:WikiProject_Sweden/Banks, despite them being imported many years ago (some are from 2014) from svwp.
There are many examples to draw from where we only have scratched the surface. @Nikki mentioned in Telegram that there are a ton of items with information in descriptions not being reflected by statements.
A focus on improving what we have, rather than inflating the total number of items, is a desire by the telegram community.
To do that we need to discuss imports whether already ongoing or not, whether very notable or not that notable.
Indeed increased steering and formality would be needed if we were to undertake having an import policy in Wikidata. So9q (talk) 06:19, 1 September 2024 (UTC)[reply]
Just as a side note, with no implications for the discussion here, but "The community in telegram has voiced" is irrelevant, I understood. Policies are decided here on the wiki, not on Telegram. Or? --Egon Willighagen (talk) 07:58, 1 September 2024 (UTC)[reply]
It is correct that policies are created on-wiki. However, it may also be fair to use that as a prompt to start a discussion here and transparent to explain if that is the case. It won't really carry weight unless the same people also voice their opinions here, but there is also no reason to belittle it just because people talked somewhere else. Ainali (talk) 08:13, 1 September 2024 (UTC)[reply]
+1. I'll add that the Wikidata channel is still rather small compared to the total number of active Wikidata editors (1% or less is my guess). Also the frequency of editors to chat is very uneven. A few very active editors/chatmembers contribute most of the messages (I'm probably one of them BTW). So9q (talk) 08:40, 1 September 2024 (UTC)[reply]
Sorry, I did not want to imply that discussion cannot happen elsewhere. But we should not assume that people here know what was discussed on Telegram. Egon Willighagen (talk) 10:36, 1 September 2024 (UTC)[reply]
Terminology matters, and the original bot policies are probably not clear anymore to the current generation Wikidata editors. With tools like OpenRefine and QuickStatements), I have the impression it is no longer clear what is "bot" and what is not. You can now easily create hundreds of items with either of these tools (and possibly others) in a editor-driven manner. I agree it is time to update the Wikidata policies around important. One thing to make clear is the distinction mass creation of items and mass import (the latter can also be mass importing annotations and external identifiers, or links between items, without creating items). -- Egon Willighagen (talk) 08:04, 1 September 2024 (UTC)[reply]
I totally agree. Since I joined around 2019 I have really struggled to understand what is okay and not when it comes to mass-edits and mass-imports. I have had a few bot requests declined. Interestingly very few of my edits have ever been questioned. We should make it simple and straightforward for users to learn what is okay and what is not. So9q (talk) 08:43, 1 September 2024 (UTC)[reply]
I agree that we need an updated policy that is simple to understand. I also really like the idea of raising the quality of existing items. Therefore, I would like the policy to recommend that, or to even make an exception for preapproval if, there is a documented plan to weave the imported data into the existing data in a meaningful way. I don't know exactly how it could be formulated, but creating inbound links and improving the data beyond the source should be behavior we want to see, whereas just duplicated data on orphaned items is what we don't want to see. And obviously, these plans need to be completed before new imports can be made, gaming the system will, as usual, not be allowed. Ainali (talk) 08:49, 1 September 2024 (UTC)[reply]

Q116172030 = Q116171429

[edit]

That is a duplicate! Carl Ha (talk) 16:12, 31 August 2024 (UTC) [reply]

I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. merged -- Reise Reise (talk) 17:48, 31 August 2024 (UTC)[reply]

Q115858229 = Q105221629

[edit]

That is a duplicate! Carl Ha (talk) 17:15, 31 August 2024 (UTC) [reply]

I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. merged -- Reise Reise (talk) 17:48, 31 August 2024 (UTC)[reply]

Q98410461 = Q111034095

[edit]

That is a duplicate! Carl Ha (talk) 17:42, 31 August 2024 (UTC) [reply]

I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. merged -- Reise Reise (talk) 17:48, 31 August 2024 (UTC)[reply]

Q98411001 = Q111182242

[edit]

Duplicate, by the way if there is a better place to report these, please let me know :) Carl Ha (talk) 17:50, 31 August 2024 (UTC)[reply]

No need to report if they are obviously duplicates. You can merge them yourself. -- Reise Reise (talk) 17:57, 31 August 2024 (UTC)[reply]
Ah thanks for the info, I thought I need admin rights or something like that. Then I will do it by myself in the future :)! Carl Ha (talk) 18:05, 31 August 2024 (UTC)[reply]
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. Reise Reise (talk) 17:57, 31 August 2024 (UTC)[reply]

Utilizing Wikidata for Enhanced Game Development

[edit]

As someone involved in game development, especially with creative games like Toca Boca, I’ve been thinking about how we can better utilize Wikidata to support and enhance our projects. Wikidata’s structured data could be incredibly valuable for game developers, particularly when it comes to organizing in-game data, tracking character relationships, or even managing large amounts of game-related content. For example, imagine using Wikidata to dynamically update in-game databases or to create more interactive and data-driven gaming experiences. This could also help in maintaining consistency across different game versions and localizations. Has anyone here explored using Wikidata in game development, or do you have any thoughts on how we could leverage its capabilities in this field? I’d love to hear about any experiences or ideas you might have. Stephan0098 (talk) 22:33, 31 August 2024 (UTC)[reply]

@Stephan0098: I'm a bit sceptical if all of that data would meet our notability policy, especially if the game is not yet published. However, the software behind Wikidata (Wikibase) is free and open for everone to use and customize. I would encourage you to have a look at that :) Samoasambia ✎ 00:58, 1 September 2024 (UTC)[reply]

Dating for painting at Q124551600

[edit]

I have a painting that is dated by the the museum as "1793 (1794?)", so it seems it was likely made in 1793 but there is a small chance that it was only made in 1794. When I type them both I get an error report. How to fix that? How to give one the preffered rank, I don't find a fitting field. Carl Ha (talk) 06:42, 1 September 2024 (UTC)[reply]

Mark the one with the highest chance as "preferred"? And add a 'reason' qualifier to indicate it preference is based on higher chance? The "deprecated" qualifier (reason for deprecated rank (P2241)) for the statements has hundreds of reasons (there is list of Wikidata reasons for deprecation (Q52105174) but I am not sure it is complete; I think my SPARQL query earlier this week showed many more). Similarly, there is reason for preferred rank (P7452) and maybe most probable value (Q98344233) is appropriate here. Egon Willighagen (talk) 08:09, 1 September 2024 (UTC)[reply]
How do I mark it as preferred? Which qualifier do I use? Carl Ha (talk) 08:11, 1 September 2024 (UTC)[reply]
Ranking is explained here: https://www.wikidata.org/wiki/Help:Ranking
I would suggest the qualifier property reason for preferred rank (P7452) with the value most probable value (Q98344233). Egon Willighagen (talk) 10:42, 1 September 2024 (UTC)[reply]
Thank you! Carl Ha (talk) 11:12, 1 September 2024 (UTC)[reply]

Inclusion of icons to Wikidata:WikiProject sum of all paintings/Collection/Russian Museum

[edit]

Could we include things that have P31 as "icons" (Q132137) as this is a type of painting. I don't know how to include that technically in the wiki code. Carl Ha (talk) 08:36, 1 September 2024 (UTC)[reply]

请求合并 Q31395213 和 Q4089188

[edit]

它们描述了同样的内容。Kone718 (talk) 09:17, 1 September 2024 (UTC)[reply]

Wikidata:WikiProject sum of all paintings/Collection/Art Culture Museum Petrograd

[edit]

Would it be possible to have in the column "inventory number" has just the inventory numbers connected with Art Culture Museum Petrograd and not the ones connected with other institutions (in this case always the Russian Museum) that later owned the paintings? Because now it is not sortable after the inventory number of the Art Culture Museum. Thanks! Carl Ha (talk) 09:40, 1 September 2024 (UTC)[reply]

Retrieved from "https://www.wikidata.org/w/index.php?title=Wikidata:Project_chat&oldid=2241452365"