Please use {{ Q }} or {{ P }} the first time you mention an item or property, respectively. Other places to find help Frequently asked questions Requests for deletions Requests for new items Merging instructions Report a technical problem Requests for protections, undeletions and other matters requiring administrator attention. To report vandalism , click here . беларуская (тарашкевіца) словѣньскъ / ⰔⰎⰑⰂⰡⰐⰠⰔⰍⰟ Bahasa Indonesia davvisámegiella srpskohrvatski / српскохрватски српски / srpski oʻzbekcha / ўзбекча Translators' noticeboard Lexicographical data Request a query Requests for permissions Interwiki conflicts Administrators' noticeboard Requests for deletions Property proposal Bureaucrats' noticeboard Report a technical problem Requests for comment Properties for deletion Requests for checkuser Connect disambiguation pages Hi, these two disambiguation pages for Jorge Rodríguez ; Caracciolo and Phillip Island were recently created on the it.Wiki; is it possible to link them to Wikidata? I don't know the procedure could someone with more experience do it? Thanks in advance for the help. ~2026-47511-02 ( talk ) 09:50, 1 September 2026 (UTC) Reply Should identifier properties be deleted when the external website goes offline? Reviewing Wikidata:Properties for deletion over time, I have noticed a recurring pattern: deletion requests for identifier properties based on the sole premise that the underlying website behind formatter URL (P1630) is no longer available online, or the identifier scheme has been superseded . I would like to open a discussion on whether this should remain a valid ground for property deletion. Identifiers in Wikidata are fundamentally entity keys for linked open data and authority control , not merely clickable external links . When a website or database goes offline, deleting the corresponding Wikidata property presents several issues: Loss of data provenance and historical mapping: The ID itself retains value. Scientific literature, legacy datasets, offline dumps, and external archives still reference these specific identifiers. Preserving them in Wikidata maintains cross-dataset traceability. Archivability: Many "dead" databases remain accessible via the Wayback Machine (Q648266) , archive.today (Q13515725) (use it under your own risk), or institutional data repositories. The formatter URL (P1630) can often be updated to point to archived snapshots. Potential resurrection or migration: Web services frequently undergo domain changes, server migrations, or rebranding. If a database comes back online under a new URL or host, having deleted the property creates unnecessary overhead to recreate and re-link the data. Distinction between Property and Formatter URL: A property represents a unique identifier scheme from an external authority or dataset. The availability of the current website ( formatter URL (P1630) ) is just an access layer, not the identifier itself. Instead of deleting identifier properties when a website goes down: Mark the property as deprecated or add a dedicated property state/qualifier indicating the target database is offline or unmaintained, or if the maintainer superseded the identifier scheme (eg. MobyGames). Use the archive URL (P1065) qualifier as we use it at Wikipedia for references (even, there is a bot that update dead links to Wayback Machine (Q648266) ). Reserve property deletion strictly for cases involving bad data design, copyright/privacy violations, or widespread invalid/spam identifiers. I would welcome the community's thoughts on establishing a clearer consensus or guideline regarding offline identifier properties. -- Amitie 10g ( talk ) 21:42, 2 September 2026 (UTC) Reply Identifiers may be migrated to a new system Identifiers may be merged with another id Maintainer of the identifier takes it down Mark as deprecated and create a specific reason for deprecation item that explains why this ID is deprecated. Adjust the property name and description to reflect the new state Add a qualifier that marks as defunct without deprecation replace formatters with archive link replace formatters with new target replace all the ids with a new system and probably other options "So my suggestion would be to have a different board for defunct/dead identifier properties" "Identifiers may be migrated to a new system" "Mark as deprecated and create a specific reason for deprecation item that explains why this ID is deprecated." For website where the identifier has been replaced with a new scheme, Wikidata property for a former identification scheme (Q108951239) is the right answer (eg. MobyGames game ID (former scheme) (P1933) ). For identifiers where the underlying website behind formatter URL (P1630) is not longer available, we have Wikidata property for a discontinued website (Q60457486) . As I seen, the right scope for both items are at property level as value for instance of (P31) (eg. Gamepedia wiki ID and MobyGames game ID (former scheme) ), while I don't see incorrect its usage at item level within such claim (eg. official demo URL (P11201) ) with the qualifier reason for deprecated rank (P2241) with the value Wikidata property for a discontinued website (Q60457486) (eg. TASVideos ). "Adjust the property name and description to reflect the new state" MobyGames game ID (former scheme) (P1933) MobyGames group ID (former scheme) (P5360) MobyGames company ID (former scheme) (P4773) "Add a qualifier that marks as defunct without deprecation" I thing the rank at item-level may be changed its rank to deprecated, adding the qualifier reason for deprecated rank (P2241) with the new item I suggested above as value. "replace formatters with new target" If the organizaction just changed the target, just change formatter URL (P1630) value. If the organization does not longer exist and other organization takes the control of the website, request a new property for the new organization, even if the ID remains exactly the same, and use values formatter URL (P1630) directing to the new website. "replace all the ids with a new system" As I understand, you want to implement a new system for implementing IDs, so I cant answer if I m unsure. If the organization uses the same dataset but superseded the scheme: propose the creation of a property for the new scheme. If the same organization changed the underlying formatter URL (P1630) but still uses the same dataset and the same scheme: modify the value of formatter URL (P1630) . If the organization becomes defunct and other organization takes the database and the same scheme: propose the creation of a new property , keeping the older identifier, as it refers to the older database. Daask , I carefuly read your comments,and I concluded you're right. Bad quality or heavily corrupted identifiers is an issue that fixing is worthless. Therefore, I reflected your concerns onto my proposal (see below section) to flexibilize it by adding "Involve heavily corrupted, mismanaged, or structurally misleading data ...", and, adding "and stable" tag on the "Belong to a valid and stable identifier" claim, and modified "Properties should not be requested for deletion nor deleted" with "Properties that deletion should be avoided". Regards Changes to the Deletion policy Before opening a Request for Comment , I propose changes/updates to the Deletion policy here, the Project Chat, specially because the Deletion policy lacks of a section regarding properties! What I suggest for now, is adding the following to the policy: General properties They involve poor data design (e.g., lack of atomicity, such as combining multiple data types in a single field). They involve heavily corrupted, mismanaged, or structurally misleading data that leads to persistent data entry errors, widespread misuse, or an unsustainable maintenance burden for the community. They are non-identifier properties that are no longer used in any entities and have been formally marked with their obsolete status (e.g., by adding obsolete Wikidata property (Q18644427) via instance of (P31) , adding a property constraint, and/or updating the property label/description). Properties may be speedily deleted when: They were created in error or by a property creator bypassing the reular procedure descried in Wikidata:Property proposal . External identifier properties The external database uses unstable identifiers (e.g., the identifier format changes frequently or is dynamically generated without persistence). External identifier properties may be speedily deleted when: They consist of widespread invalid or spam identifiers. The identifiers are sourced from stolen or illegal datasets. The property belongs to a valid and stable identifier , even if the underlying target behind formatter URL (P1630) is no longer available online. Instead of deletion, the property should be set as obsolete by adding obsolete Wikidata property (Q18644427) to instance of (P31) . Additionally, archive URL (P1065) may be used at the item level as a qualifier to provide an alternative link to archival services like the Wayback Machine (Q648266) . The property belongs to a valid and stable identifier , even if the maintainer of the external database has superseded the scheme. To adopt the new scheme, a new property proposal must be opened . Claims using the old, superseded scheme may be ranked as deprecated , where appropriate, and archive URL (P1065) may be used as a qualifier for archival links if the original URL formatter is dead. Regards. -- Amitie 10g ( talk ) 23:54, 3 September 2026 (UTC) Reply Should there potentially be separate sections for properties in general and then one specific for external id properties? Since the third part only applies to them. Are the speedily deleted based on examples you know off? If not I don't think this is necessary at this point. I would avoid using the term "deprecated" in the first policy. Additionally -> The property should then be marked for their new status, for example with obsolete Wikidata property (Q18644427) or similar item via instance of (P31) , a property constraint, and/or a change to the property label/description. Remove the " from the deprecated in the last policy. "Should there potentially be separate sections for properties" I reworded the proposal and separated the non-identifier with identifier properties. "Are the speedily deleted based on examples you know off?" Them are examples I guessed, but more examples may be found. "I would avoid using the term "deprecated" in the first policy" As I mentioned above, I reworded the proposal. "Remove the " from the deprecated in the last policy" As I mentioned above, I reworded the proposal. Russian-Czech matching problem Hi! I’ve been working for quite some time on reviewing the import of biographical entries from the Czech database. There are currently around 6,000 entries about people from the USSR and Russia that don’t have a Russian label. However, roughly 15–20% of these people already have corresponding Wikidata items under other entries. Is there any tool that could help match the Czech-labeled entries from this list that are missing a Russian label with existing Wikidata items, for example, based on similar birth and death dates? Also, is there any way to compare Czech Latin transliterations (e.g. *Timofej Onisimovič Tverdynskij*) with Russian Cyrillic spellings (e.g. *Тимофей Онисимович Твердынский*)? In other words, something that could account for transliteration patterns such as Czech *j* = Russian *й*, etc. Maybe there are some additional tools, approaches, or tips that could help with this task? Mitte27 ( talk ) 05:30, 3 September 2026 (UTC) Reply Don't disrupt Wikidata to illustrate a point I have imported the famous "Don't disrupt projects to illustrate a point" policy/guideline/essay (depending on the project) here, Wikidata. For now, I have developed an essay at my sandbox , mentioning aspects relevant to Wikidata, as well as importing some aspects from the Commons' counterpart relevant to this project. The objective of this thread is to officialy import that essay onto Wikidata: namespace (including the ability to be translated), and, if the community decide, upgrade it to a guideline or a policy. I'm listening. -- Amitie 10g ( talk ) 00:55, 5 September 2026 (UTC) Reply My page for Wikidata Q141261843 has been deleted, I would like to speak to someone regarding this matter ~2026-47854-98 ( talk ) 01:03, 5 September 2026 (UTC) Reply VIAF conflation I have created a new item for Molly Miller (Q141287500) , an English historian who died in 1982, and looked for identifiers. Two of them list books written (or illustrated) by the historian and about four other people called Molly Miller, who don't have Wikidata items. Do I need to create a conflation page? Library of Congress: https://id.loc.gov/authorities/names/no2009087586.html VIAF: https://viaf.org/en/viaf/238850741 TSventon ( talk ) 15:52, 5 September 2026 (UTC) Reply Historical events on a 3D globe — feedback on dates and locations I built Geotemporal Transurfing, a prototype for exploring historical events on a 3D globe. You can orbit Earth, move forward or backward in time, and see what was happening elsewhere around the same time. The dataset is collected offline from Wikidata, Wikipedia and some manual event inclusions, with media from Wikimedia Commons. I'd appreciate feedback on the experience, event coverage, features, and accuracy of representation of the events. Are there properties, queries or existing projects I should look at? Try it: https://geotemporal-transurfing.pages.dev/ Prototype GitHub: https://github.com/aregmii/geotemporal-transurfing Ibstellar ( talk ) 23:11, 5 September 2026 (UTC) Reply Navigating the timeline is hard. The "Read more" button link is not obvious. I started wondering where each piece of information came from. Additionally, often the headline is not in the "Read more" source. For transparency, it should be more clear where the headline comes from, or if it is made by you. can i copy entire Ps and Qs from one identical item to other multiple or single item? example: copy entire Ps and Qs of 2015 Champion versus Champion (Q132673167) to 2016 Champion versus Champion (Q141317895) কল্কি ( talk ) 04:25, 6 September 2026 (UTC) Reply

ListeriaBot off since two days ago It seems that ListeriaBot has been stopped since September 4th in all wikis. It doesn't update lists even when the update button is clicked. The issue has already been reported at https://github.com/magnusmanske/listeria_rs/issues/181 and m:User_talk:Magnus_Manske#ListeriaBot_stopped_for_two_days but I'm unsure about whether any other action could help to solve the issue faster. Pere prlpz ( talk ) 08:07, 6 September 2026 (UTC) Reply What is the difference between these items? I have a government agency unit that is supervised under ministry X, that is tasked to operate Y airport, then I tried to search for the appropriate item to fill the instance of (P31) value, and found three candidates: port authority (Q652812) aviation authority (Q1875618) airport authority (Q4698967) Which one is more appropriate and what is the difference between them? FenyMufyd ( talk ) 10:14, 6 September 2026 (UTC) Reply w:en:Port authority w:id:Otoritas penerbangan sipil w:id:Otoritas bandar udara Anything goes for P18? P18 usage notes requires images to be "exemplary: representative, unambiguous, and high quality". But sometimes people add images like this to personalities' items. I removed this one, but @ Jcb reverted it. I made the edit again, explaining the obvious in the summary ; they reverted it again and told me that we should keep any bad quality image in P18. I explained that it's not intended use; Jcb did not respond to this. Month later I removed the image again; Jcb's reaction this time was reverting the edit, threatening me with block , and checking my recent contributions to revert another edit (this time it was some unknown modern artist's painting of a person without any lifetime portraits). I restored the edits, pointing out that they are well founded, and urged the user to initiate blocking me if they believe I'm in the wrong here. Instead, they reverted the edits once again, discarded my explanation and accused me of vandalism. From the user's contributions in Talk space I get the impression that they often engage in conflicts of similar sort with P18 usage being a common point of contention. I suspect the process is similar: some user sees incorrect type of image inserted into a Wikipedia infobox; they find out it comes from Wikidata and remove the image here; Jcb reverts the edits, insists on his "anything goes into P18" policy and accuses their opponents of vandalism. Someone should tell them already that: other projects expect certain type of content here people don't like it when something unwanted gets inserted in articles via Wikidata (and it prompts the projects to disengage like English Wikipedia did) disregarding other editors' concerns with edit wars, silence, threats and vandalism accusations is disruptive Qbli2mHd ( talk ) 14:23, 6 September 2026 (UTC) Reply Should Wikidata regulate media quality for downstream consumption? Due to the insistence of Qbli2mHd , I think we need a policy regarding the sovereignty of Wikidata over other projects, specifically the usage of multimedia files as a value for commonsMedia properties (e.g. image (P18) ). The intention of this thread is to establish clearly the scope of Wikidata as a database—a scope that regulates the quality of structured data, but not the quality of media files (this is a matter of Commons and the Wikimedia projects that use the files). Commons has its Project scope (which is a policy ), which explicitly states the educational value of multimedia files, and explicitly states that the quality doesn't matter as long as the file has educational value (e.g., the file is in use on any Wikimedia project page), and explicitly states that Commons does not overrule other projects about what is in scope. For instance, the Wikidata usage instructions (P2559) for image (P18) states (in English): I can conclude two things: It is not a policy , convention , or guideline —it is merely a description of a property. Since it is not a policy, it merely suggests that claims related to multimedia files (e.g., image (P18) ) should use high-quality media files. While "should" sounds imperative, not being a policy means it cannot be taken as mandatory. It does not mean it is legitimate to remove claims with poor-quality multimedia files as a value. In 2016, someone asked about the quality of multimedia files we may use as a value for image (P18) . 10 years later, I just answered that. Low quality images aren't ideal, but if there is nothing else to add .. Personally I avoid group images unless it's fairly easy to determine who is the person (e.g. a female in a group of males). I'm not much into cropping .. --- Jura 11:27, 19 April 2016 (UTC) Which I conclude "worse is nothing", and, quality of media files is not a matter of Wikidata. I have added to my essay about "Do not disrupt Wikidata to illustrate a point": do follow the policies of the Wikimedia project where the file is used, and discuss the matter there. do not replace the value nor remove the claim under the sole premise the media file is low resolution. Consider replacing it with a better quality media file, if available. do follow the policies of the Wikimedia project where the file is used, and discuss the matter there. do not replace the value nor remove the claim under the sole premise the media file is low resolution. Consider replacing it with a better quality media file, if available. This, precisely, to avoid this kind of situations. That said, I ask should Wikidata regulate media quality for downstream consumption? Do we need a policy defining the relationship between Wikidata's policies and those of other Wikimedia projects when Wikidata data is consumed downstream, in light of what Commons' Project scope establishes? I'm listening. -- Amitie 10g ( talk ) 13:53, 7 September 2026 (UTC) Reply I see problem here other than unnecessary conflicts. If the administration of wikidata insists on keeping irrelevant, misleading or low-grade images - it's their call. Other projects will simply use something else. No big deal to me. Retired electrician ( talk ) 18:09, 9 September 2026 (UTC) Reply As I already mentioned previously in this thread, I don't think this is merely a matter of "unnecessary conflicts". image (P18) has a defined scope, and its usage notes explicitly call for images that are "representative, unambiguous, and high quality", but that does not mean you can remove a claim solely on the grounds that the image is low quality, especially if the media file is in use; once a media file is in use, it is no longer solely a matter of Wikidata. If a value is irrelevant or misleading, the fact that another project happens to use it does not automatically make it an appropriate image (P18) value. Other projects are free to use something else, of course, but that does not mean Wikidata should deliberately retain values that do not fit the property's intended use. The whole point of having property usage notes and constraints is to provide meaningful structured data for downstream use. And finally, please be familiar with how Wikimedia projects work. Administrators cannot simply impose whatever they want; they are expected to act according to the community's decisions, as established in policies and other applicable rules. As I mentioned before, Wikidata's policies should not overrule the policies of other Wikimedia projects. In fact, Commons' own project scope explicitly states that Commons does not overrule the policies of other Wikimedia projects. Amitie 10g ( talk ) 18:31, 9 September 2026 (UTC) Reply Are full scans of books and their translations suitable for P18 for the original work? As this discussion is going on, I am at odds over whether a full scan of the 50+ page 1881 Spanish translation El Cíclope (Q87073857) is suitable for use in image (P18) to illustrate the 5th-century BCE Greek satyr play by Euripides Cyclops (Q1206121) that the translation is based on. The item already has File:Tragedie di Euripide (Romagnoli) VI-0232.png (shown at right) listed under related image (P6802) , and so an image is already present on the data item. But is a book (full book scan, not an image of a page or part of the book) suitable for use as an illustration for the work the book is about? Could, for example, a scan of a biography of Julius Caesar (Q1048) be used as a value in image (P18) for the historical person's data item? And what if the linked book is a translation into another language of the work to which the translation is being added as a image (P18) value? Would a Russian translation of Wuthering Heights (Q202975) be suitable as an image for the data item used for the work in general? You can see the full discussion so far on this user talk page , with arguments that a book functions as a supporting reference. My opinion is that this conflated the function of image (P18) with the function of references. The counter-argument is that a "reference may have no veracity", and an image "here I can with my own eyes" [sic]. -- EncycloPetey ( talk ) 21:05, 12 September 2026 (UTC) Reply There are so many uses of this value (oh, I forgot that Reasonator became useless...). I didn't remove them because I believe that the problem is more deep and should be resolved somehow. What if... we would use special value "multiple values" (in addiion to "unknown" and "novalue") instead? Infovarius ( talk ) 19:43, 6 September 2026 (UTC) Reply most years,decades and centuries don't have start and end times I was happily coding up an application using centuries, decades and years and am baffled why we mostly, but not always don't have start and end dates. Now they do have points in time with appropriate precision, but that is of limited use when doing a SPARQL query as that throws to a particular date, the start of the period, which is of limited use if I wanted the 1960s to give me 2 date strings 10 years apart. I could hack the point in time outside WD, but it seems better to do it inside. Before I add start and end times at highest precision, is there some obvious reason I'm missing why something so fundamental is like this? Vicarage ( talk ) 22:36, 6 September 2026 (UTC) Reply Use of member of/position held properties I'm not sure if I would be better to use member of (P463) or position held (P39) for members of committees of the Scottish Parliament [3] . Not sure if it makes sense to use 'member of' since this is more of a role fulfilled within the parliament than like a voluntary organisation, but from what I understand 'position held' would require creating another item for the membership of each of the 16 committees? Tigered27 ( talk ) 01:16, 7 September 2026 (UTC) Reply Raising an issue with Q40608 - wrong pronunciation audio file Q40608 Could someone with the permission to do so remove the incorrect pronounciation audio from this entry, as it has spread to a few non-english wikipedia's data boxes (such as this one ) Doctor spelling ( talk ) 11:06, 7 September 2026 (UTC) Reply Wikidata weekly summary #748 New requests for permissions/Bot: HsfBot - Task/s: Mostly add missing Indonesian Wikipedia sitelinks to Wikidata items for taxonomy templates created by HsfBot on idwiki. CrossrefIDsBot - Task/s: Adding Crossref ID, DOI, Print ISSN, and Online ISSN from Crossref dataset where they are missing in Wikidata. CatmapperBot - Task/s: Add SocioMap ID statements for reviewed SocioMap category mappings, and provisionally add exact match URLs for reviewed ArchaMap category mappings until Wikidata approves an ArchaMap-specific identifier property. BenchfolkBot - Task/s: Add or correct sourced statements on existing items after explicit human approval. HsfBot - Task/s: Mostly add missing Indonesian Wikipedia sitelinks to Wikidata items for taxonomy templates created by HsfBot on idwiki. CrossrefIDsBot - Task/s: Adding Crossref ID, DOI, Print ISSN, and Online ISSN from Crossref dataset where they are missing in Wikidata. CatmapperBot - Task/s: Add SocioMap ID statements for reviewed SocioMap category mappings, and provisionally add exact match URLs for reviewed ArchaMap category mappings until Wikidata approves an ArchaMap-specific identifier property. BenchfolkBot - Task/s: Add or correct sourced statements on existing items after explicit human approval. New request for comments: Class Q1048835 as a not valid value-type constraint - To remove an incorrect value for value-type constraint (Q21510865) for P27 (country of citizenship) Project chat: What images are appropriate for P18? - a lengthy discussion about quality control and what is acceptable for a P18 (image) value. Class Q1048835 as a not valid value-type constraint - To remove an incorrect value for value-type constraint (Q21510865) for P27 (country of citizenship) Project chat: What images are appropriate for P18? - a lengthy discussion about quality control and what is acceptable for a P18 (image) value. Upcoming events : Open Workshop: Connecting Basque heritage authors (Persons and entities) in Wikipedia and Wikidata - 22 September - 09:00 - 11:30 CEST. Press, articles, blog posts, videos Blogs: What Does a Wikidata-Powered Abstract Wikipedia Article Look Like? (Links: Substack and Medium ) Papers: Bemme, J., & Winkler, A. (2026). Mehr Edits wagen? Virtuelle Ausstellungen erschließen mit Wikidata und Commons. LIBREAS. Library Ideas, (48). https://doi.org/10.18452/37905 / https://libreas.eu/ausgabe48/bemme/ Tool of the week Tabernacle is a tool by User: Magnus Manske it generates a table of Wikidata items and statements. Allows for quick addition of some types via WiDaR. Other Noteworthy Stuff The 10th issue of the Wikidata Platform Newsletter is out. Also remember to join the next Blazegraph Migration Office Hour , that will take place Tuesday, 8th September 2026 at 16:00 UTC The Castle Map - every Castle, Fortress and Palace recorded on Wikidata, on a map. Newest properties and property proposals to review Newest properties : General datatypes: none External identifiers: CREDDO author ID , ‎World Athletics competition ID , Platform for Taiwan Religion and Folk Culture record identifier , T&F NCAAdb athlete ID , COMDT author ID , Clergy Memorial (1914-1918) ID , ‎Texas Legislators: Past & Present ID , Stiftungsarchive ID , Redalyc author ID , Kudos author ID General datatypes: none External identifiers: CREDDO author ID , ‎World Athletics competition ID , Platform for Taiwan Religion and Folk Culture record identifier , T&F NCAAdb athlete ID , COMDT author ID , Clergy Memorial (1914-1918) ID , ‎Texas Legislators: Past & Present ID , Stiftungsarchive ID , Redalyc author ID , Kudos author ID New property proposals to review: General datatypes: Pokémon Ability (Pokémon Ability assigned to this Pokémon species or form in games of the Pokémon series) Collective bargaining coverage (Percentage of workers covered by collective agreement coverage. This is distinct from union membership rate, because non-union members can also be covered, for example France has 7% union density but 98% collective bargaining coverage.) encompasses (specific entity this placeholder item may represent when the exact one is unknown) marionetteist (Person who manipulates a marionette in real time to create the illusion of life.) has expression of concern ((article) has an expression of concern (expression of concern notice)) External identifiers: Common Core Ontologies concept ID , AbeBooks author ID , DEHIO digital Deutschland Bauwerk ID , VocaDB tag ID , CCLI song ID , LIDO concept ID , The Telegraph topic ID , BLL-Ontology concept ID , GOLD linguistic concept ID , ISBNdb author ID , BookWyrm author ID , BookWyrm book ID , China Railway station telegraph code , Darija.io ID , Vietnamese Administrative Unit Codes , Officials of Nazi Reich Ministries ID , Fandom.com universe page , KennisWest ID , identifiant d'un(e) auteurice dans le catalogue du Centre Delavouët , Phenotype and Trait Ontology ID , National Governors’ Association ID , Numista engraver or designer ID , Encyclopedia of Alabama ID (new schema) General datatypes: Pokémon Ability (Pokémon Ability assigned to this Pokémon species or form in games of the Pokémon series) Collective bargaining coverage (Percentage of workers covered by collective agreement coverage. This is distinct from union membership rate, because non-union members can also be covered, for example France has 7% union density but 98% collective bargaining coverage.) encompasses (specific entity this placeholder item may represent when the exact one is unknown) marionetteist (Person who manipulates a marionette in real time to create the illusion of life.) has expression of concern ((article) has an expression of concern (expression of concern notice)) Pokémon Ability (Pokémon Ability assigned to this Pokémon species or form in games of the Pokémon series) Collective bargaining coverage (Percentage of workers covered by collective agreement coverage. This is distinct from union membership rate, because non-union members can also be covered, for example France has 7% union density but 98% collective bargaining coverage.) encompasses (specific entity this placeholder item may represent when the exact one is unknown) marionetteist (Person who manipulates a marionette in real time to create the illusion of life.) has expression of concern ((article) has an expression of concern (expression of concern notice)) External identifiers: Common Core Ontologies concept ID , AbeBooks author ID , DEHIO digital Deutschland Bauwerk ID , VocaDB tag ID , CCLI song ID , LIDO concept ID , The Telegraph topic ID , BLL-Ontology concept ID , GOLD linguistic concept ID , ISBNdb author ID , BookWyrm author ID , BookWyrm book ID , China Railway station telegraph code , Darija.io ID , Vietnamese Administrative Unit Codes , Officials of Nazi Reich Ministries ID , Fandom.com universe page , KennisWest ID , identifiant d'un(e) auteurice dans le catalogue du Centre Delavouët , Phenotype and Trait Ontology ID , National Governors’ Association ID , Numista engraver or designer ID , Encyclopedia of Alabama ID (new schema) You can comment on all open property proposals ! Query examples: UNESCO Heritage sites 100km or less from the centre of the Meditrranean Sea (source) Schema examples: spaceport (E213): schema for spaceport (Q194188) locations, used to launch and receive spacecraft. WikiProject Highlights: Project Medicine / Knee Arthroplasty - a comprehensive subpage to model the techniques and procedures for knee-related surgery. Newest database reports : Same Humans/List by Occupations - this report presents possible human duplicates by comparing name and birth/death dates. They can be reviewed and flagged for merging and/or deletion. Sustainability: We are looking into improvements to caching for Property labels ( phab:T434204 ) We are continuing to prepare the move of the entity_usage table to the extension database cluster. Moving the tables is tentatively scheduled to begin after 24. September. ( phab:T427472 ) We are looking into improvements to caching for Property labels ( phab:T434204 ) We are continuing to prepare the move of the entity_usage table to the extension database cluster. Moving the tables is tentatively scheduled to begin after 24. September. ( phab:T427472 ) Newcomer homepage: We are working on making the Newcomer Homepage show labels for Items instead of just the ID ( phab:T429345 ) Wikidata changes in Watchlist and Recent changes of Wikipedia and co: We are deciding how filtering will look for hiding language link changes on wikis where the sitelink has not changed ( phab:T435904 ) REST API: We are continuing to expand the support for Lexemes in the API, specifically creating a Lexeme, adding a statement to a Lexeme and adding a Form to a Lexeme 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 . Add labels, in your own language(s), for the new properties listed above . Contribute to the showcase Item and Lexeme above . Govdirectory weekly focus country: Tunisia Summarize your WikiProject's ongoing activities in one or two sentences. Help translate or proofread the interface and documentation pages, in your own language! Help merge identical items across Wikimedia projects. Help write the next summary! The Wikibase/DataModel page contains Lua errors Hello, can someone with Lua expertise take a look to this page and fix it? There are many errors that appear in red: https://www.mediawiki.org/wiki/Wikibase/DataModel 5628785a ( talk ) 22:48, 7 September 2026 (UTC) Reply Help panel question on Q141363686 (10:05, 8 September 2026) Statement edit -- Reyking bobyzily ( talk ) 10:06, 8 September 2026 (UTC) Reply Split needed from Wikimedia category (Q4167836) The item for the concept of a wiki category has somehow become the same item as the project page page about categories/categorization . I had never really looked closed at the item, so I'm not sure how or why this happened. It may have been one of those unfortunate aggregations rather than a merge. Luckily it should be (in theory, anyway) fairly doable to split off the policy page as I assume very few links relate to the policy aspect instead of the category concept, but I'm very nervous about doing it myself! Any thoughts? Circeus ( talk ) 03:42, 11 September 2026 (UTC) Reply official website (P856) of Clube Atlético Itapemirim (Q9778920) is broken. Can someone kindly delete? Many thanks in advance for all you can do!!! ~2026-49122-17 ( talk ) 09:20, 11 September 2026 (UTC) Reply Help panel question on Q138673292 (10:57, 11 September 2026) How to add references??? -- Elijah265 ( talk ) 10:57, 11 September 2026 (UTC) Reply Hello I have left a request to merge two names , Onofrio in italiano and in other languages are separated. You may find the page in russian , Онуфрий, it is the same name ~2026-49241-28 ( talk ) 18:00, 12 September 2026 (UTC) Reply Removing disambiguators from train station labels The other day, I noticed an inconsistency in the English labels for train stations in the San Francisco Bay Area (Q213205) : many ended with "station" per the English Wikipedia, while a number of others did not (and never did). For consistency within these systems, I relegated the "station" form of each station to an alias and added the proper name as the mul label. Another editor has asked me to undo some of these changes, so I want to get a second opinion from the community. Please see my full reasoning in Wikidata talk:WikiProject Railways#Removing disambiguators from train station labels . Thank you. – Minh Nguyễn 💬 19:40, 12 September 2026 (UTC) Reply