Property proposal:	Generic	Authority control	Person	Organization
	Creative work	Place	Sports	Sister projects
	Transportation	Natural science	Computing	Lexeme

Cultural heritage

See also: Wikidata:WikiProject Cultural heritage, Wikidata:WikiProject Intangible Cultural Heritage

Other related projects: Category:Cultural heritage WikiProjects

National Historical Museums of Sweden object ID

On hold

Description	authority identification for an object in the collections of the National Historical Museums of Sweden
Data type	External identifier
Example 1	Streiff (Q10681657) → https://samlingar.shm.se/object/A4B754D2-5CB6-4FA1-997A-970250E32044
Example 2	Mosjömadonnan (Q10589526) → https://samlingar.shm.se/object/7C505995-EBF5-4106-BBEE-17F52BB3EA83
Example 3	Elizabeth Reliquary (Q26253636) → https://samlingar.shm.se/object/8BA2743C-5065-438B-9FAA-D854606DB716
Allowed values	[0-9A-Z]{8}-[0-9A-Z]{4}-[0-9A-Z]{4}-[0-9A-Z]{4}-[0-9A-Z]{12}
Source	https://samlingar.shm.se
Planned use	Matching and creating items in the collection that are depicted on Wikimedia Commons
Number of IDs in source	1 300 000
Expected completeness	no label (Q21873886 (always incomplete))
Formatter URL	https://samlingar.shm.se/object/$1
See also	Nationalmuseum Sweden artwork ID (P2539)
Single-value constraint	yes
Distinct-values constraint	yes

Motivation

Needed to be able to matching and creating items on Wikidata that are objects in the collection of NHM and that are depicted in images on Wikimedia Commons, for example. / LinneaKarlberg (talk) 12:58, 7 April 2022 (UTC)[reply]

Discussion

Support Azad Karimi (talk) 13:56, 7 April 2022 (UTC)[reply]

Support LinneaKarlberg (talk) 13:05, 7 April 2022 (UTC)[reply]

Support Eva L Vedin (talk) 13:08, 7 April 2022 (UTC)[reply]

Support Elinor Rajka (talk) 19:13, 7 April 2022 (UTC)[reply]

Support Azad Karimi (talk) 13:56, 7 April 2022 (UTC)[reply]

Comment @LinneaKarlberg:, @Eva L Vedin:, @Elinor Rajka:, @Azad Karimi: coordinating support votes with ones colleagues is not helpful, the property proposal process is in place for a reason. Abbe98 (talk) 22:34, 7 April 2022 (UTC)[reply]

Sorry, we did not know. LinneaKarlberg (talk) 07:19, 8 April 2022 (UTC)[reply]

Comment Considering that National Historical Museums of Sweden ID (P9495) exists and that other properties from SHM are likely to be proposed in the future(places, events, heritage sites, ect) maybe there should only be one property? As far as I'm aware the UUIDs are unique across the various types and even if that wouldn't be the case one could include the type prefix in the id. Abbe98 (talk) 22:40, 7 April 2022 (UTC)[reply]

@Abbe98: Sure, that would probably work. Do you have an example of another external identifier that includes several different types so I can check how it works? Is it possible then to change the name and details of P9495? LinneaKarlberg (talk) 07:22, 8 April 2022 (UTC)[reply]

Europeana entity (P7704) would be one example. I would imagine migrating/generalizing National Historical Museums of Sweden ID (P9495) by: 1. updating the formatter URL 2. adding the agent prefix to existing values 3. updating the label/description of the property Abbe98 (talk) 10:08, 8 April 2022 (UTC)[reply]

Oppose Per the discussion above, I would suggest generalizing National Historical Museums of Sweden ID (P9495) rather than creating a new property for each type. I cave created a section on the discussion page. Abbe98 (talk) 10:20, 8 April 2022 (UTC)[reply]

Hello Abbe98

, It would then be necessary to differentiate "agents" from "object". How would you like to do? (incorporate it into the identifier as a general property? or use an external URL formatter?) We can also consider that each property will be dedicated to the type (less errors with dedicated constraints). It would be necessary to recontact those who have already voted, as well as the voters of the other property, to find out if your idea appeals to them, but with more information. I don't see a URL leading directly to the correct page without using the type (with only the UUID). Example: type:UUID. Cordially. —Eihel (talk) 03:47, 13 April 2022 (UTC)[reply]

Hi! I would imagine we would use one of the seven possible prefixes like agent/<UUID> and object/<UUID>. We could also use a generic resolver but there isn't an official one so I think such a solution is less optimal. Abbe98 (talk) 06:48, 13 April 2022 (UTC)[reply]

@Abbe98: @Eihel: @LinneaKarlberg: We just had a discussion about this with the Wikidata team at the National Historical Museums of Sweden. Our conclusion is that this property should not be created, and Abbe98's solution (using prefixes) is better. This will include us (WMSE is supporting the museum in their Wikidata work) generalizing National Historical Museums of Sweden ID (P9495) and removing /person/ from the formatter URL and then adding the person prefix to all the existing uses of the property. --Alicia Fagerving (WMSE) (talk) 12:10, 21 April 2022 (UTC)[reply]

@Alicia Fagerving (WMSE) I have pinged all the people who voted on National Historical Museums of Sweden ID (P9495). I think we should leave it over the weekend at least but then if there are no one oposing this I can migrate it early next week. Abbe98 (talk) 12:32, 21 April 2022 (UTC)[reply]

We at NHM are all on board with this approach instead of several Properties. LinneaKarlberg (talk) 08:09, 29 April 2022 (UTC)[reply]

Sounds like an excellent idea. Many thanks Abbe98 . /André Costa (WMSE) (talk) 08:51, 24 May 2022 (UTC)[reply]

Thanks everyone, I've started re-defining National Historical Museums of Sweden ID (P9495) and will migrate the existing items using it. --Alicia Fagerving (WMSE) (talk) 12:19, 9 June 2022 (UTC)[reply]

National Archives of Sweden persistent identifier

On hold

Description	persistent identifier for objects in the National Archives of Sweden main archival database
Represents	National Archives of Sweden (Q1724971)
Data type	External identifier
Domain	archival resource (Q106815942), document (Q49848), work (Q386724)
Example 1	No 2. Elbing. (Q111517198) → eYHMeAFOm4sNVmxKK3M5L2
Example 2	No 3. Elbing (Q111517379) → 0zDW3BS0Gw9Haap2yUVspE
Example 3	No 4. Danzigk wir es Eltere und newer werck (Q111519390) → zmQwWNi2ag9DQGJxnSVmD0
Allowed values	Base62-encoded UUID
Implied notability	Wikidata property for an identifier that does not imply notability (Q62589320)
Formatter URL	https://sok.riksarkivet.se/arkiv/$1
See also	Swedish National Archive reference code (P5324)
Applicable "stated in"-value	National Archives of Sweden (Q117288060)
Single-value constraint	yes
Distinct-values constraint	yes

Motivation

Wikidata-objekt med denna egenskapen kan också ha Nationell Arkivdatabas Referenskod (P5324), men den persistenta identifieraren är enklare att använda för att skapa webbsides-URLer och länkad data-URIer. Nils Weinander (Riksarkivet Sverige) (talk) 13:28, 28 April 2022 (UTC)[reply]

Discussion

Comment Hi - could you fix your examples to look more like other property proposals (should look like: item → id) ? Also it would be useful to have formatter URL and some of the other template parameters filled out if possible. ArthurPSmith (talk) 14:21, 29 April 2022 (UTC)[reply]
Thanks for the feedback! This is my first property proposal so I am very unsure of how to do things. I have reformatted the examples, added URL format and a see also reference. Nils Weinander (Riksarkivet Sverige) (talk) 08:22, 2 May 2022 (UTC)[reply]
Support Ok, looks good to me now! ArthurPSmith (talk) 15:48, 9 May 2022 (UTC)[reply]
Support Jneubert (talk) 05:53, 10 May 2022 (UTC)[reply]
Comment are the above examples also the canonical URIs? Considering that the RA has quite a lot of identifiers, could there be a less generic name/description? "primary database" doesn't say much to the average user. Abbe98 (talk) 21:18, 11 May 2022 (UTC)[reply]
Support,
Ainali Belteshassar so9q Vätte Popperipopp Tulipasylvestris Esquilo Daniel Mietchen — with focus on topics related to research (Q42240) VisbyStar Haxpett QubeCube Marcus.linneberg Vitplister Spisen Sollentuna Myohmy671 Autom S4b1nuz E.656 JoranL
Notified participants of WikiProject Sweden —MasterRus21thCentury (talk) 06:36, 21 March 2023 (UTC)[reply]

It has been created as Swedish National Archive agent ID (P9713) se discussion - Salgo60 (talk) 07:43, 21 March 2023 (UTC)[reply]

Not the same as I understand. This proposal is for objects in archives (maybe even archives or series, though I struggle to come up with a case where they would have a wikidata item). The property you link is for an agent (Swedish: arkivbildare). Belteshassar (talk) 09:15, 21 March 2023 (UTC)[reply]

@Belteshassar, Nils Weinander (Riksarkivet Sverige), Abbe98: Dont we make it more complex than needed. Formatter url is the same

https://sok.riksarkivet.se/agent/$1

My suggestion change the name on Swedish National Archive agent ID (P9713) to be both... I have used (maybe wrongly) both for the "person agent" and the "archive agent"

1) List examples nota bene August Strindberg seems to have more person identifiers at the National Archive looks like something that needs to be cleaned at "the National Archive"...

Having 2 different properties is like if someone should connect with Wikidata and add new properties for every type of instance instance of (P31) Wikidata has... ?

Also Swedish National Archive reference code (P5324) is used for both persons and archives

- Salgo60 (talk) 20:35, 24 March 2023 (UTC)[reply]

Comment, I think this would be useful, perhaps also on commons. I’m not sure how many entries in NAD reference individual works, as I understand the purpose of the proposal, and to what degree those works are notable for Wikidata. Perhaps the creator of the proposal could enlighten me. Belteshassar (talk) 09:23, 21 March 2023 (UTC)[reply]
- pushed the question also to github.com/Riksarkivet/dataplattform - Salgo60 (talk) 13:24, 27 March 2023 (UTC)[reply]
Comment read the thoughts over at the National Archive - Salgo60 (talk) 03:10, 28 March 2023 (UTC)[reply]
Comment Writing as the original author of this propopsal, I would like to put this on hold for the moment. I realize that this should probably be the RDF URI rather than just the PID. I have to think this over and if I do end up with wanting the RDF URI, there are issues to clear with the format of this. - Nils Weinander (Riksarkivet Sverige) (talk) 11:26, 28 Mars 2023 (UTC)
FYI: Nils is working at the Swedish National Archives with this - Salgo60 (talk) 17:17, 28 March 2023 (UTC)[reply]

Looks like Nils left Riksarkivet and the whole thing died. I tried to ask about Riksarkivets terms but get odd answers see issue #22 - Salgo60 (talk) 10:53, 11 June 2024 (UTC)[reply]

CAMEO page ID

Ready ^Create

Description	Page identifier for the Conservation and Art Materials Encyclopedia Online (CAMEO)
Data type	External identifier
Example 1	lac (Q15112450)→Lac
Example 2	Strasbourg turpentine (Q138005782)→Strasbourg_turpentine
Example 3	adhesive (Q131790)→Adhesive
Formatter URL	https://cameo.mfa.org/wiki/$1

Motivation

Conservation and Art Materials Encyclopedia Online (Q58888853) (CAMEO) is a database that compiles, defines, and disseminates technical information on the distinct collection of terms, materials, and techniques used in the fields of art conservation and historic preservation. It developed by Museum of Fine Arts Boston (Q49133)--Shizhao (talk) 07:15, 4 February 2026 (UTC)[reply]

Discussion

Support — Dcflyer (talk) 08:21, 10 February 2026 (UTC)[reply]

Cinematography

See also: Wikidata:WikiProject Movies

Other relevant projects: Category:Movie WikiProjects

ShotOnWhat film ID

Under discussion

Description	ID for shotonwhat.com database
Data type	External identifier
Domain	item
Example 1	Minority Report (Q244604)→[1]
Example 2	Bram Stoker's Dracula (Q107325)→[2]
Example 3	subject→value
Allowed values	[A-Za-z0-9-]
Source	https://shotonwhat.com/
Planned use	Import IDs for popular and recent movies
Single-value constraint	yes
Distinct-values constraint	yes
Wikidata project	Q8485793

Motivation

1) Enriches Film Data: Provides detailed info about the equipment used to shot the film, not extensively covered in Wikidata. Crucial for film researchers, collectors, and curators seeking specific details. 2) Improves Interoperability: Seamless navigation from Wikidata to the specialized external database. – The preceding unsigned comment was added by FinixFighter (talk • contribs) at 14:18, January 20, 2026 (UTC).

Discussion

Comment ShotOnWhat? (Q136643926) is a WordPress (Q13166) site, so it's probably better to use the postID instead of the clean URL (Q6451799) as the identifier, since the ID redirects to that anyway. It will also be more stable in case a post slug ever changes for some reason. You can find the post ID referenced in various places in the page source or by copying the ID from the URLs on the Update Details or Update Poster buttons below the poster image. It's also possible to do scraping with the JSON API [3] or from the RSS feed [4] on many WP sites including this one.

Here are the WordPress post IDs for the examples you used above:
Minority Report (Q244604)→26930
Bram Stoker's Dracula (Q107325)→39864
Finnius00 (talk) 08:30, 1 February 2026 (UTC)[reply]

‎Japanese Location Database ID

Under discussion

Description	identifier for entries in the Japanese Location Database
Represents	Japan Location Database (Q136687366)
Data type	External identifier
Example 1	Echizen Railway (Q1007890) → 180400028
Example 2	Ōno Castle (Q1072530) → 180400066
Example 3	Dōgo Onsen Honkan (Q11641713) → 380100001 (cf. en, zh)
Example 4	Shikayose (Q137321683) → 290200143
Example 5	Hakodate Historical Museum of Photography (Q137321701) → 010400049
Source	https://jl-db.nfaj.go.jp
Number of IDs in source	12,774 filming location (Q1045481) (Japanese (Q5287)); 4,971 filming location (Q1045481) (English (Q1860)); 1,160 filming location (Q1045481) (Chinese (Q7850))
Expected completeness	always incomplete (Q21873886) / eventually complete (Q21873974)
Formatter URL	https://jl-db.nfaj.go.jp/location/$1

Motivation

A high-quality external identifier (Q21754218) with entries in Japanese (Q5287), English (Q1860), and Chinese (Q7850); as in example 1, there are some entries broader than mere "places"; while I believe there is a preference for an English-language default where possible, I suggest defaulting to the Japanese for the formatter URL as there are many more entries in Japanese than either English (+"/en") or Chinese (+"/zhcn") (one can then toggle between available languages at the top of the page); thank you, Maculosae tegmine lyncis (talk) 21:23, 1 November 2025 (UTC)[reply]

Discussion

Notified participants of WikiProject Japan Regards, ZI Jony ^(Talk) 18:27, 7 December 2025 (UTC)[reply]

Hello, @ZI Jony, thanks for the ping.

Hello, Maculosae tegmine lyncis, I am new to discussing nomination, and would you guide me what is the subject/poll here? Are we to discuss feasibility of a new data source, which is still to have its own QID?

I read the url and the publisher is a non-profit film commission, or a body supporting a specific sector of users: people among film/movie/video, and perhaps audio industry as well.

If you'd better gather data to support/fill parameters, I will be available midweek or 12 December 2025 (: Added params to the publisher for 全国ロケーションデータベース (Q136687366). Cheers, Omotecho (talk) 03:36, 10 December 2025 (UTC)[reply]

Hello, as with the two new examples I have added (4 & 5), the idea is to use this property (if the proposal is supported and approved) as an external identifier (Q21754218) to reference existing and support the creation of new Wikidata item (Q16222597); perhaps this Wikidata property proposal (Q114746893) should be listed under the topic "Place" or "Generic" as the items are quite diffuse; part of the value of the identifier is its multi-lingual nature, as (semi-)official English (and Chinese) names are not always readily available; there are also typically photos and short descriptions, maps, etc; its function specifically in relation to filming location (Q1045481) per se is perhaps secondary; thank you, Maculosae tegmine lyncis (talk) 05:36, 10 December 2025 (UTC)[reply]

@Omotecho, would you like to give your opinion? Regards, ZI Jony ^(Talk) 16:37, 10 December 2025 (UTC)[reply]

Yes, thank you @Maculosae tegmine lyncis for clarification:

Support I support the idea to have Japan-focused source of information.

I guess it calls for separate thread: How about the governing NFAJ, a GLAM parent institute, if we talk about films/movies/cinema released in Japan?[1]

NFAJ's Collection and Articles

OPAC Search for films https://opac.nfaj.go.jp/opac/opac_search/?lang=1
NFAJ Film Collection Search http://nfad.nfaj.go.jp/ (in Japanese)

also offers data for films with English subtitles.

NFAJ Digital Gallery https://www.nfaj.go.jp/onlineservice/digital-gallery/
Japanese Animated Film Classics http://animation.filmarchives.jp/en

With the first public movie show took place in 1917.

64 videos: early Japanese animations from our collection are shown in the site.
"Noburo Ofuji Memorial Museum", a page you find old documents, leaflets and production materials: Ofuji is the artist who donated his private collection to the NFAJ.

Others ← JL-DB
Japanese Film Resources Online (JFROL) https://jfrol.jp (in Japanese)

JFROL is a search system for locating non-film materials. Cross-search the non-film collections of the following institutions:
Toei Kyoto Studio Park Library;
Shochiku Otani Library,
Kawakita Memorial Film Institute,
Matsunaga Bunko Library of Kitakyushu, and
the Tsubouchi Memorial Theatre Museum of Waseda University.

[1] https://www.nfaj.go.jp/english/onlineservice/ They hold fliers and booklets film theaters sold/circulated to movie goers, since 1900.

--Omotecho (talk) 18:03, 10 December 2025 (UTC)[reply]

@Omotecho: I wondered if a NFAJ Film Collection ID property might be in order along the lines of BFI National Archive work ID (P2703); however, with this BFI ID, as in use eg on Robin Hood (Q19090) ([5]), the BFI entry is about the film itself (in this case, seemingly the BFI itself has no related material in its archive, only this information); by contrast, for Late Spring (Q743203), the National Film Archive of Japan (Q51371009) search system returns two entries, for a 35 mm film (Q226528) print [6], and for a 16 mm film (Q194383) print [7]; the スタッフ/cast listing is quite comprehensive, including the シテ and ワキ in the Noh scene, so perhaps it would be a useful identifier anyway (information such as フィート長 is presumably specific to the (in)complete print in the collection, but the cast list would make the identifier relevant to the main Late Spring (Q743203) item, not merely a subsidiary edition or translation of (P629) or equivalent print of item for these particular prints), Maculosae tegmine lyncis (talk) 18:53, 10 December 2025 (UTC)[reply]

@Maculosae tegmine lyncis, well comprehended on my side: Thank you contrasting with BFI National Archive work ID (P2703) very much, it cleared my uncertainty or confusion. (: Omotecho (talk) 04:21, 11 December 2025 (UTC)[reply]

‎MPA certificate number

Under discussion

Description	unique certificate number from the Motion Picture Association as included in a film's credits
Represents	Motion Picture Association film rating system (Q1987792)
Data type	External identifier
Example 1	Star Wars: Episode IV – A New Hope (Q17738) → 24925
Example 2	Jurassic Park (Q167726) → 32451
Example 3	A Lad in Bagdad (Q41573722) → 21550
Example 4	Sleepless in Seattle (Q107167) → 32238
Example 5	Jurassic World Rebirth (Q124380480) → 55488
Allowed values	\d{1,5}
Source	https://www.filmratings.com
Formatter URL	https://www.filmratings.com/search-results/?cn=$1
See also	MPA film rating (P1657), BBFC reference (P8794), ICAA film catalogue ID (P5128)
Applicable "stated in"-value	FilmRatings.com (Q47425783)

Motivation

This number is often included for film items with MPA film rating (P1657) using the qualifier rating certificate ID (P2676) – see the example of Star Wars: A New Hope. Now that the new filmratings.com website surfaces this information, we could track this more formally, similar to BBFC reference (P8794). —Chchowmein (talk) 08:42, 15 January 2026 (UTC)[reply]

Discussion

Support Looks like a good addition. Jean-Fred (talk) 09:09, 15 January 2026 (UTC)[reply]
Comment Out of curiosity − why does the Star Wars certificate in the example has two hits in the database? Jean-Fred (talk) 09:09, 15 January 2026 (UTC)[reply]
I was wondering about that also. The entry has a note that it was edited and re-rated. I think the current rating is a re-issue from 2004. But presumably, that number 24925, appears "sequentially older" than 2004. Presumably, they reused the original certificate number. And that might have something to do with two entries appearing? Happily the two duplicate entries share the exact same number. Chchowmein (talk) 20:44, 15 January 2026 (UTC)[reply]
Comment Since these are numerical identifiers in search form, I am afraid that we are dealing with the same situation as with PEGI. The identifier may be duplicated, as in this case [8], [9], [10], [11], [12] or even worse, shared with several others (see for example [13], [14], [15], [16], [17], [18], [19], [20], [21]), which, as I am noticing, is typical for identifiers in search form. Of course, we could try using identifier shared with (P4070) for each search ID, but as I mentioned earlier in the PEGI proposal, these are not the usual numerical IDs that we think of. Regards Kirilloparma (talk) 02:00, 16 January 2026 (UTC)[reply]
Wow, really strange there are those later collisions! It looks like 32451 is unique to Jurassic Park, you can see it included here in the film's end credits roll at 6:05. It also looks like Jurassic World Rebirth is correct with 55488 which is included in MPA CARA Ratings Bulletin No. 2883 (found as a PDF here from archive.org). Maybe those collisions are cataloging errors. Chchowmein (talk) 04:39, 16 January 2026 (UTC)[reply]

So, I looked into this. The consensus appears to be that the certificate numbers are intended to be unique.

The first film to be issued a number is the 1934 film The World Moves On (Q600904). Its certificate number is 1. You can see the certificate number appearing at the beginning of the film here.

From 1934 until 1968, certificate numbers were were issued by the Production Code Administration of the MPA. This showed that they complied with the Production Code. You can see more certificates in use here in the Audiovisual Identity Database.

The relevant section of the production code reads: The completed picture shall be submitted to the Code Office and if it is approved by the Administrator, the producer or distributor shall upon public release of the picture place upon an introductory frame of every print distributed for exhibition in the United States the official Seal of the Association with the word “Approved” above the Seal, and below, the words “Certificate Number,” followed by the number of the Certificate of Approval.

Beginning in 1968, the system switched from the Motion Picture Production Code (Q610292) to the Motion Picture Association film rating system (Q1987792) but the numbering appears to have continued sequentially. Every (compliant) film exhibited after Friday, November 1, 1968 was required to have a rating.

It appears the first film to be issued a certificate in the new MPA ratings system is possibly Pillaged (Q3316293) with 21787. I'm assuming that other titles like Prefabricated Pink (Q7239791) had earlier certificates such as 21587 and ratings were retroactively attached to them.

There is a list of films from 1 to 46047 here at filmonsuper8.com and archived from chello.nl here with contributors listed but there are some mistakes such as Hellfighters (Q1217025) being listed as 21651 but it is apparently 21851.

There was previous known collision on certificate number 39360 (My Boss's Daughter) discussed on reddit in 2012 but apparently it was brought to their attention and they fixed it by issuing Scary Movie 3 40335, Adventureland 44388, and so on. Chchowmein (talk) 09:18, 16 January 2026 (UTC)[reply]
Oh, one other note, those particular examples are mysterious for another reason: they all are 3 digits. I'm confident the first ratings occurred around the 21xxx series. Three digit certificates should have been issued decades earlier. As a possible clue, in your link 6, The Scarlett Letter (1934) has certificate 158 (issued in 1934, and presumably the canonical of the two). Letter appears to have had a (post-1968) rating retroactively added in 1970. The film that collides with it is Cherry, Harry & Raquel! which originally came out in 1969. This makes me think Cherry… is supposed to have a 5 digit certificate but maybe a data entry problem has omitted two of the digits. Chchowmein (talk) 09:50, 16 January 2026 (UTC)[reply]

Artdoc.Media film ID

Done: Artdoc.Media film ID (P14139) (Talk and documentation)

Description	identifier for a film at Artdoc.Media
Represents	Artdoc.Media (Q137905636)
Data type	External identifier
Domain	film (Q11424)
Example 1	The Other Chelsea: A Story from Donetsk (Q4168679) → drugoy__chelsi___isto_2011_89
Example 2	Q56314079 → drugaya_zhizn__2017_150
Example 3	We Are Russia (Q133850860) → rossiya___eto_my_2019_63
Source	https://artdoc.media/movie
External links	Use in sister projects: [ar] • [az] • [bn] • [de] • [en] • [es] • [fa] • [fr] • [he] • [hi] • [it] • [ja] • [ka] • [kn] • [ko] • [ml] • [mr] • [nl] • [pl] • [pt] • [ro] • [ru] • [sv] • [te] • [tr] • [ur] • [vi] • [zh] • [commons] • [species] • [wd] • [en.wikt] • [fr.wikt].
Planned use	for usage in stated in (P248) and for Template:Authority control (Q3907614)
Expected completeness	eventually complete (Q21873974)
Formatter URL	https://artdoc.media/movie/$1

Motivation

The site contains a wealth of information about documentaries from the post-Soviet space. --Mitte27 (talk) 21:32, 26 January 2026 (UTC)[reply]

Discussion

Support Well very well (talk) 21:57, 26 January 2026 (UTC)[reply]

@Mitte27, Well very well: Done ArthurPSmith (talk) 18:27, 16 February 2026 (UTC)[reply]

Russian Register of Film Distribution Certificates ID

Ready ^Create

Description	identifier for a film at Russian Register of Film Distribution Certificates
Represents	no label (Q137908550)
Data type	External identifier
Domain	film (Q11424)
Example 1	The Other Chelsea: A Story from Donetsk (Q4168679) → 481271
Example 2	Jurassic Park (Q167726) → 435501
Example 3	Lermontov (Q136548389) → 13744435
Source	https://culture.gov.ru/services/reestr-prokatnykh-udostovereniy
External links	Use in sister projects: [ar] • [az] • [bn] • [de] • [en] • [es] • [fa] • [fr] • [he] • [hi] • [it] • [ja] • [ka] • [kn] • [ko] • [ml] • [mr] • [nl] • [pl] • [pt] • [ro] • [ru] • [sv] • [te] • [tr] • [ur] • [vi] • [zh] • [commons] • [species] • [wd] • [en.wikt] • [fr.wikt].
Planned use	for usage in stated in (P248) and for Template:Authority control (Q3907614)
Expected completeness	eventually complete (Q21873974)
Formatter URL	https://culture.gov.ru/services/reestr-prokatnykh-udostovereniy/$1

Motivation

The State Film Registry of the Russian Federation contains information about films that have received distribution certificates. It allows you to search for a film by various criteria and find the distribution certificate number. --Mitte27 (talk) 06:36, 27 January 2026 (UTC)[reply]

Discussion

Support Well very well (talk) 10:34, 27 January 2026 (UTC)[reply]

Erotica and pornography

Xcity actress ID

Under discussion

Description	identifier for an actress on the Xcity website
Represents	Kuki Inc. (Q10879079)
Data type	External identifier
Domain	human (Q5), AV idol (Q1079215)
Example 1	Ai Nagase (Q9013243) → 945
Example 2	Hibiki Ōtsuki (Q9187572) → 3208
Example 3	Jessica Kizaki (Q8976570) → 2805
Source	https://xcity.jp/
External links	Use in sister projects: [ar] • [az] • [bn] • [de] • [en] • [es] • [fa] • [fr] • [he] • [hi] • [it] • [ja] • [ka] • [kn] • [ko] • [ml] • [mr] • [nl] • [pl] • [pt] • [ro] • [ru] • [sv] • [te] • [tr] • [ur] • [vi] • [zh] • [commons] • [species] • [wd] • [en.wikt] • [fr.wikt].
Formatter URL	https://xcity.jp/idol/detail/$1
Robot and gadget jobs	might be imported from ja:Template:Xcity

Motivation

This property links Wikidata items of Japanese adult video actresses to their profiles on the Xcity website. Xcity has long been used as a major reference database for Japanese adult video actresses and is widely cited in Japanese Wikipedia articles. This identifier will help improve consistency and cross-referencing of biographical and filmography information across Wikimedia projects.ならちゃん (talk) 11:04, 7 February 2026 (UTC)[reply]

Discussion

Support --Sabelöga (talk) 15:45, 7 February 2026 (UTC)[reply]

Television

See also: Wikidata:WikiProject Movies

Anime and manga

See also: Wikidata:WikiProject Anime and Manga

‎Manga-DB person ID

Ready ^Create

Description	identifier for this mangaka at Manga-DB
Represents	Manga-DB (Q136922464)
Data type	External identifier
Domain	human (Q5)
Example 1	Q111112998→愛上陸 (NSFW)
Example 2	Kyoden Sanbun (Q11468731)→山文京伝 (NSFW)
Example 3	Key (Q38276629)→きい (NSFW)
Source	https://adultcomic.dbsearch.net/user/favorite-author.html (NSFW)
Number of IDs in source	Unknown
Expected completeness	always incomplete (Q21873886)
Implied notability	Wikidata property for an identifier that suggests notability (Q62589316)
Formatter URL	https://adultcomic.dbsearch.net/author/$1.html
Applicable "stated in"-value	Manga-DB (Q136922464)
Type constraint – instance of	human (Q5)
Single-value constraint	yes
Distinct-values constraint	yes
Wikidata project	WikiProject Anime and manga (Q7098843)

Motivation

Manga-DB is a Japanese manga database. While the works themself are not necessarily notable many of the mangaka in the database certainly are

Keep in mind this is not a scanlation website and does not have any copyright infringement beyond what you would reasonable find on any other online manga database --Trade (talk) 02:40, 23 November 2025 (UTC)[reply]

Discussion

@Jotamide, Sd5605:--Trade (talk) 03:06, 23 November 2025 (UTC)[reply]
Neutral leaning towards Support - I'm not too well-versed in manga but if this is the only site that covers doujin works and authors, then it has a scope that existing properties at Special:WhatLinksHere/Q101083593 seemingly don't cover. Jotamide (talk) 09:59, 23 November 2025 (UTC)[reply]
I am not actually sure if this website is about doujin works. The fact that all titles on the site have been published in magazines would suggest its not since doujins translates to "self-[ublished"". There are also no mention of dōjin circle (Q2013644) anywhere on the site @Jotamide:--Trade (talk) 13:21, 23 November 2025 (UTC)[reply]
@Jotamide, would you like to give your final opinion based on the response? Regards, ZI Jony ^(Talk) 18:58, 7 December 2025 (UTC)[reply]
I cannot really distinguish this from the other Wikidata property to identify manga (Q101083593) items so I'll just stay Neutral Jotamide (talk) 21:50, 9 December 2025 (UTC)[reply]

One item I looked at (NSFW) was for a 298 pages long e-book with several publishing houses listed, ISBN number and a listed sales price, doesn't look self-published at all. Looks like i can create a user account and log in so I would guess this is a crowd sourced website which means entries usually don't have implied notability. Infrastruktur (talk) 07:15, 15 February 2026 (UTC)[reply]

@Wd-Ryan:--Trade (talk) 14:32, 11 December 2025 (UTC)[reply]
Support -wd-Ryan (Talk/Edits) 19:32, 15 December 2025 (UTC)[reply]

‎Manga-DB magazine ID

Ready ^Create

Description	identifier for this manga magazine at Manga-DB
Represents	manga magazine (Q15296520)
Data type	External identifier
Domain	manga publisher (Q136925103)
Example 1	Comic X-Eros (Q28685552)→COMIC%20X-EROS (NSFW)
Example 2	Q28689987→COMIC%20BAVEL (NSFW)
Example 3	Comic Pengin Club (Q11193604)→ペンギンクラブ (NSFW)
Source	https://adultcomic.dbsearch.net/magazine/ (NSFW)
Number of IDs in source	Unknown
Expected completeness	always incomplete (Q21873886)
Implied notability	Wikidata property for an identifier that suggests notability (Q62589316)
Formatter URL	https://adultcomic.dbsearch.net/magazine/$1.html
Applicable "stated in"-value	Manga-DB (Q136922464)
Type constraint – instance of	manga magazine (Q15296520)
Single-value constraint	yes
Distinct-values constraint	yes
Wikidata project	WikiProject Anime and manga (Q7098843)

Motivation

Manga-DB is a Japanese manga database. While the works themself are not necessarily notable the same cannot be applied to most of the magazines in the datavase

Keep in mind this is not a scanlation website and does not have any copyright infringement beyond what you would reasonable find on any other online manga database--Trade (talk) 03:03, 23 November 2025 (UTC)[reply]

Discussion

Support -wd-Ryan (Talk/Edits) 19:33, 15 December 2025 (UTC)[reply]

‎Manga-DB publisher ID

Ready ^Create

Description	identifier for this manga publisher at Manga-DB
Represents	Manga-DB (Q136922464)
Data type	External identifier
Domain	manga publisher (Q136925103)
Example 1	KASAKURA PUBLISHING (Q11599796)→笠倉出版社 (NSFW)
Example 2	Q11319019→ティーアイネット (NSFW)
Example 3	Magazine Magazine (Q11306126)→マガジン・マガジン (NSFW)
Source	https://adultcomic.dbsearch.net/publisher/ (NSFW)
Number of IDs in source	Unknown
Expected completeness	always incomplete (Q21873886)
Implied notability	Wikidata property for an identifier that suggests notability (Q62589316)
Formatter URL	https://adultcomic.dbsearch.net/publisher/$1.html
Applicable "stated in"-value	Manga-DB (Q136922464)
Type constraint – instance of	manga publisher (Q136925103)
Single-value constraint	yes
Distinct-values constraint	yes
Wikidata project	WikiProject Anime and manga (Q7098843)

Motivation

Manga-DB is a Japanese manga database. While the works themself are not necessarily notable most of the publishers in the database certainly are

Keep in mind this is not a scanlation website and does not have any copyright infringement beyond what you would reasonable find on any other online manga database--Trade (talk) 06:12, 23 November 2025 (UTC)[reply]

Discussion

Support -wd-Ryan (Talk/Edits) 19:33, 15 December 2025 (UTC)[reply]

Music

See also: Wikidata:WikiProject Music

Other relevant projects: Category:Music WikiProjects

Topplista artist ID

Under discussion

Description	identifier for an artist on Topplista site
Represents	Topplista (Q61882726)
Data type	External identifier
Domain	human (Q5), group of humans (Q16334295)
Example 1	Basshunter (Q383541) → 3833
Example 2	Stromae (Q313453) → 4383
Example 3	Alan Walker (Q21808729) → 684
Example 4	Sean Paul (Q200577) → 722
Example 5	Arash (Q236748) → 4768
Allowed values	[1-9]\d{0,8}
Source	https://topplista.no
External links	Use in sister projects: [ar] • [az] • [bn] • [de] • [en] • [es] • [fa] • [fr] • [he] • [hi] • [it] • [ja] • [ka] • [kn] • [ko] • [ml] • [mr] • [nl] • [pl] • [pt] • [ro] • [ru] • [sv] • [te] • [tr] • [ur] • [vi] • [zh] • [commons] • [species] • [wd] • [en.wikt] • [fr.wikt].
Planned use	putting value to artists available on the Topplista site
Expected completeness	always incomplete (Q21873886)
Formatter URL	https://topplista.no/artist/$1

Motivation

Property for artists included in Topplista (Q61882726). Eurohunter (talk) 20:39, 13 February 2026 (UTC)[reply]

‎Bach digital work ID

Under discussion

Description	identifier for a work at the "Bach digital" project
Data type	External identifier
Domain	musical work/composition (Q105543609)
Example 1	Toccata and Fugue in D minor, BWV 565 (Q392734)→00000645
Example 2	Die Auferstehung und Himmelfahrt Jesu (Q1211115)→00002259
Example 3	Mass in B minor (Q310549)→00000289
Allowed values	\d+
Formatter URL	https://www.bach-digital.de/receive/BachDigitalWork_work_$1
Applicable "stated in"-value	Bach digital (Q19835087)

Motivation

Bach digital is a project by the Bach Archiv that provides manuscripts and printed sheet music of the Bach family. This property is about works by Johann Sebastian Bach and his sons. Another property proposal that I wrote is "Wikidata:Property proposal/Bach digital person ID". --Anvilaquarius (talk) 17:09, 9 February 2026 (UTC)[reply]

Discussion

Comment Please flesh out the proposal a bit more, see what I did for Wikidata:Property proposal/Bach digital person ID. In particular, what is the domain here? musical work/composition (Q105543609)? Can you provide existing items for the examples above? Thanks! Jean-Fred (talk) 08:49, 10 February 2026 (UTC)[reply]

Apple Music Classical work ID

Under discussion

Description	identifier for a musical composition in Apple Music Classical
Data type	External identifier
Domain	musical work/composition (Q105543609)
Example 1	Symphony No. 9 (Q11989) → ludwig-van-beethoven-1770-pp32
Example 2	Prelude and Fugue in C major, BWV 846 (Q4376908) → johann-sebastian-bach-1685-pp503
Example 3	The Magic Flute (Q5064) → wolfgang-amadeus-mozart-1756-pp53
Allowed values	[0-9a-z\-]*
External links	Use in sister projects: [ar] • [az] • [bn] • [de] • [en] • [es] • [fa] • [fr] • [he] • [hi] • [it] • [ja] • [ka] • [kn] • [ko] • [ml] • [mr] • [nl] • [pl] • [pt] • [ro] • [ru] • [sv] • [te] • [tr] • [ur] • [vi] • [zh] • [commons] • [species] • [wd] • [en.wikt] • [fr.wikt].
Expected completeness	always incomplete (Q21873886)
Formatter URL	https://classical.music.apple.com/work/$1
Single-value constraint	yes
Distinct-values constraint	yes

Motivation

Apple Music Classical (Q124249772) has portal pages for recordings of the same composition. I didn't find its equivalent in the generic app. --魔琴 (talk) 14:01, 14 February 2026 (UTC)[reply]

Discussion

Support -wd-Ryan (Talk/Edits) 20:33, 14 February 2026 (UTC)[reply]

Board game

See also: Wikidata:WikiProject Board Games

Video game

See also: Wikidata:WikiProject Video games

Other relevant projects: Category:Video game WikiProjects

CriticDB game ID

Done: CriticDB game ID (P14093) (Talk and documentation)

Description	numeric identifier of a video game in the CriticDB database
Aliases	CDB game ID
Represents	CriticDB (Q131917281)
Data type	External identifier
Domain	video game (Q7889)
Example 1	Black Myth: Wukong (Q98582386)→107722
Example 2	God of War (Q18345138)→108598
Example 3	Doom: The Dark Ages (Q126091569)→99860
Example 4	Clair Obscur: Expedition 33 (Q126462072)→52250
Example 5	Stellar Blade (Q108481438)→21952
Allowed values	[1-9]\d{3,5}
Source	https://www.criticdb.com/games
External links	Use in sister projects: [ar] • [az] • [bn] • [de] • [en] • [es] • [fa] • [fr] • [he] • [hi] • [it] • [ja] • [ka] • [kn] • [ko] • [ml] • [mr] • [nl] • [pl] • [pt] • [ro] • [ru] • [sv] • [te] • [tr] • [ur] • [vi] • [zh] • [commons] • [species] • [wd] • [en.wikt] • [fr.wikt].
Mix'n'match	7600
Planned use	~~Once the property is approved, I'll make a Mix'n'Match catalog for it.~~ already done
Number of IDs in source	4,600 (as of 12.01.2026)
Expected completeness	always incomplete (Q21873886)
Formatter URL	https://criticdb.com/games/request/similar/$1
URL match pattern	^https?:\/\/criticdb\.com\/games\/request\/similar\/(\d+) ↳ web page title extract pattern (P10999) no value
See also	OpenCritic ID (P2864), Metacritic game ID (P12054).
Applicable "stated in"-value	CriticDB (Q131917281)
Single-value constraint	yes
Distinct-values constraint	yes
Wikidata project	WikiProject Video games (Q8485882)

CriticDB outlet ID

On hold

Description	identifier of a gaming media outlet in the CriticDB
Aliases	CDB outlet ID
Represents	CriticDB (Q131917281)
Data type	External identifier
Domain	website (Q35127), magazine (Q41298), newspaper (Q11032).
Example 1	GameSpot (Q45836) → 28
Example 2	IGN (Q207708) → 69
Example 3	Video Games Chronicle (Q108734192) → 53
Example 4	Polygon (Q7226423) → 36
Example 5	Eurogamer (Q281243) → 8
Allowed values	[1-9]\d{0,2}
Source	https://criticdb.com/outlets, https://criticdb.com/api/outlets?page=1
External links	Use in sister projects: [ar] • [az] • [bn] • [de] • [en] • [es] • [fa] • [fr] • [he] • [hi] • [it] • [ja] • [ka] • [kn] • [ko] • [ml] • [mr] • [nl] • [pl] • [pt] • [ro] • [ru] • [sv] • [te] • [tr] • [ur] • [vi] • [zh] • [commons] • [species] • [wd] • [en.wikt] • [fr.wikt].
Planned use	Once the property is approved, I'll make a Mix'n'Match catalog for it.
Number of IDs in source	99 (as of 16.01.2026)
Expected completeness	always incomplete (Q21873886)
Formatter URL	none
See also	OpenCritic outlet ID (P11223), Metacritic publication ID (P12079).
Applicable "stated in"-value	CriticDB (Q131917281)
Single-value constraint	yes
Distinct-values constraint	yes
Wikidata project	WikiProject Video games (Q8485882)

CriticDB author ID

Done: CriticDB author ID (P13319) (Talk and documentation)

Description	identifier of a critic in the CriticDB database
Aliases	CDB author ID
Represents	CriticDB (Q131917281)
Data type	External identifier
Domain	human (Q5)
Example 1	Kallie Plagge (Q98930803)→2862
Example 2	Christian Donlan (Q97823707)→1158
Example 3	Oli Welsh (Q97826421)→1179
Allowed values	[1-9]\d{0,3}
Source	https://www.criticdb.com
External links	Use in sister projects: [ar] • [az] • [bn] • [de] • [en] • [es] • [fa] • [fr] • [he] • [hi] • [it] • [ja] • [ka] • [kn] • [ko] • [ml] • [mr] • [nl] • [pl] • [pt] • [ro] • [ru] • [sv] • [te] • [tr] • [ur] • [vi] • [zh] • [commons] • [species] • [wd] • [en.wikt] • [fr.wikt].
Planned use	Once the property is approved, I'll make a Mix'n'Match catalog for it.
Number of IDs in source	? (the latest ID seems to be 5533 but I am not really sure that this is the exact number of IDs in the database and if it is the latest ID at all)
Expected completeness	always incomplete (Q21873886)
Formatter URL	https://criticdb.com/authors/$1/wd
URL match pattern	^https?:\/\/(?:www\.)?criticdb\.com\/authors\/([1-9]\d{0,3})(?:\/(?:[a-z\d]+(?:\-[a-z\d]+)*)) ↳ web page title extract pattern (P10999) ^(.+?)\s+Reviews and Features\s+\\|\s+CriticDB\s?$
See also	MobyGames person ID (P3913), Internet Game Database person ID (archived) (P5796).
Applicable "stated in"-value	CriticDB (Q131917281)
Single-value constraint	yes
Distinct-values constraint	yes
Wikidata project	WikiProject Video games (Q8485882)

Motivation

Notified participants of WikiProject Video games

CriticDB (Q131917281) is a recently launched video game database and review aggregator. Performs essentially the same function as OpenCritic (Q21039459) and Metacritic (Q150248), but differs in that the information entered into the database is manually verified without the use of AI. Also differs in that it pays more attention to games, game creators and outlets that provide reviews.

I noticed at once that the database besides slugs for all potentially three properties, uses numeric identifiers as well (e.g. for game and outlet), but unfortunately I couldn't find a suitable URL (except for authors) that would be able to use only them, so we'll leave slugs as an option for now. If anyone can find a suitable formatter URL for numeric IDs, please feel free to provide it here. Regards Kirilloparma (talk) 04:20, 2 February 2025 (UTC)[reply]

Discussion

Support Matthias M. (talk) 08:47, 2 February 2025 (UTC)[reply]
Support ―Applsdev (talk) (contribs) 15:14, 2 February 2025 (UTC)[reply]
Support A Mix'n'Match catalog for the game IDs won't be needed as the game slugs are the same as Internet Game Database game ID (P5794). In fact, there's a decent chance that the URL https://criticdb.com/games/$1 will resolve for a random IGDB game ID. The new property should only be used for the 2050 games on CriticDB that have a review score. Dexxor (talk) 21:40, 3 February 2025 (UTC)[reply]
Support --Kdkeller (talk) 22:19, 4 February 2025 (UTC)[reply]
Comment FYI, I’m asking on their Discord about having the numeric IDs resolve − will keep posted. Jean-Fred (talk) 14:34, 7 February 2025 (UTC)[reply]
Got an answer:
Dev is working on a way to surface the IDs you need! i.e. /games/88888 will redirect to games/star-wars-jedi-survivor
Jean-Fred (talk) 16:06, 7 February 2025 (UTC)[reply]

Oh, thank you for contacting them, and of course thanks to the website creators for taking the time and trying to provide this opportunity! Regards Kirilloparma (talk) 02:13, 9 February 2025 (UTC)[reply]

After a few months we unfortunately have no news from the database maintainers. The numeric identifier link still hasn't worked, so I guess we can now focus on slugs and use them. @Jean-Frédéric: What do you think? – The preceding unsigned comment was added by Kirilloparma (talk • contribs).

Thanks for following up. I poked my contact on Discord, he’s going to check. Jean-Fred (talk) 16:10, 5 May 2025 (UTC)[reply]

Comment These seem ready to create, except if you want to switch to numeric id's then we should settle that before creating. ArthurPSmith (talk) 15:48, 10 February 2025 (UTC)[reply]

Yes, now the website creators are trying to provide this opportunity for us, so we can wait. If they then reply that they unfortunately can't do it, that's not a problem. In the meantime, we can mark 1 property out of 3 (for authors) as ready, which I've already done. Regards Kirilloparma (talk) 04:03, 13 February 2025 (UTC)[reply]

@Kirilloparma, Matthias M., Applsdev, Dexxor, Kdkeller, Jean-Frédéric: Done: CriticDB author ID (P13319), and leaving the others under discussion for now. --Lewis Hulbert (talk) 05:35, 19 February 2025 (UTC)[reply]
@Lewis Hulbert I think the discussion was about all 3 at once not just the author ID. Matthias M. (talk) 11:52, 1 August 2025 (UTC)[reply]
Support Also, support the others. Storing the slug has its own benefits like URL matching (with tools like Wikibase for Web (Q99894727)) or easily being able to migrate the property to archive.org in the result of a database going down. I think it would be ideal to store both numeric IDs and slugs. --Lewis Hulbert (talk) 05:42, 19 February 2025 (UTC)[reply]
In this case the slugs can be stored in Internet Game Database game ID (P5794) as CriticDB imported lots of data from IGDB and copied their slugs, so a new property for the slugs is unnecessary. Dexxor (talk) 07:59, 19 February 2025 (UTC)[reply]
Update I reached out to the database maintainers and got a reply telling me they've prioritized this task. In the meantime, I found a partially working formatter URL that allows using numeric IDs, here it is: https://criticdb.com/games/request/similar/$1 (example). Nevertheless, in order to access the identifier (this is what it looks like), you need to register on the website, so this is only a partially working solution. As for outlets, unfortunately, there are no alternatives yet, so this property remains on hold for now. @Matthias M., Applsdev, Dexxor, Kdkeller, Jean-Frédéric, Lewis Hulbert What do you think? Regards Kirilloparma (talk) 03:50, 13 January 2026 (UTC)[reply]
Sounds all good, thanks for moving this forward! Jean-Fred (talk) 15:41, 21 January 2026 (UTC)[reply]
Just in case pinging others as well
Nicereddy — 13:40, 04 May 2015 (UTC) Danrok — 18:20, 30 October 2015 (UTC) Lewis Hulbert — 20:26, 13 December 2017 (UTC) Santer — 22:03, 26 May 2018 (UTC) Kirilloparma — 00:30, 5 August 2018 (UTC) Cwf97 — 18:33, 22 October 2018 (UTC) YotaMoteuchi — 08:09, 22 May 2019 (UTC) CptViraj — 02:49, 17 September 2019 (UTC) BugWarp — 23:19, 26 October 2019 (UTC) WikiSyn — 21:52, 26 December 2019 (UTC) Cynde Moya — 16:07, 31 March 2020 (UTC) Dexxor — 14:51, 02 May 2020 (UTC) Floyd-out — 09:14, 22 July 2020 (UTC) Jean-Frédéric — 11:22, 11 September 2020 (UTC) A particle for world to form — 11:15, 17 May 2021 (UTC) Dollarsign8 — 01:40, 01 November 2021 (UTC) Wd-Ryan — 02:20, 03 October 2022 (UTC) Master Of Ninja — 17:37, 18 October 2022 (UTC) Matthias M. — 09:28, 12 February 2023 (UTC) VGPaleontologist — 21:03, 12 February 2023 (UTC) Tomodachi94 — 18:34, 26 February 2023 (UTC) thgiex — 12:17, 6 April 2023 (UTC) DoublePendulumAttractor — 17:48, 05 May 2023 (UTC) Metafire18 — 12:55, 21 August 2023 (UTC) applsdev — 18:44, 25 September 2023 (UTC) Cupkake4Yoshi — 06:54, 26 October 2023 (UTC) Eniehack — 07:56, 07 November 2023 (UTC) RampantSpirit — 17:59, 11 November 2023 (UTC) Macocobovi — 07:35, 22 November 2023 (UTC) EdoAug — 17:10, 02 January 2024 (UTC) Keplersj — 20:53, 10 February 2024 (UTC) Arlo Barnes — 23:48, 10 March 2024 (UTC) Odjob16 — 16:24, 21 June 2024 (UTC) CommanderKefir — 14:57, 17 September 2024 (UTC) Athayahisyam — 03:10, 15 October 2024 (UTC) SuperUltraHardCoreGamer — 11:25, 25 November 2024 (UTC) MicroTato — 15:13, 17 September 2025 (UTC) Jwillikers — 18:34, 24 October 2025 (UTC) Jakub Vrána — 6:38, 29 January 2026 (UTC)[reply]
Notified participants of WikiProject Video games. Regards Kirilloparma (talk) 04:06, 14 January 2026 (UTC)[reply]
Since there were no particular objections, I marked the property for games as ready (2nd property out of 3). Regards Kirilloparma (talk) 02:00, 15 January 2026 (UTC)[reply]
@Trade: Can you please help me create this property? I've already prepared a ready-to-run batch. Regards Kirilloparma (talk) 22:46, 19 January 2026 (UTC)[reply]
@Kirilloparma, Trade, Matthias M., Applsdev, Dexxor, Kdkeller: @Jean-Frédéric, Lewis Hulbert Done The game id property is created now too. ArthurPSmith (talk) 20:37, 20 January 2026 (UTC)[reply]

‎file name

Under discussion

Description	name used for this entity in a computer file system
Data type	String
Example 1	gitignore (Q135227906)file name.gitignore
Example 2	Windows thumbnail cache (Q930281)file nameThumbs.db
Example 3	EICAR test file (Q1889416)file nameeicar.com
Example 4	Jak and Daxter: The Precursor Legacy (Q1784103)checksum (P4092)87bab4d563a73c3d61a12394f6997779file nameJak and Daxter - The Precursor Legacy (USA) (En,Fr,De,Es,It).iso (source)
Example 5	Spider-Man (Q2539517)checksum (P4092)1c26a0602691862a06a5f68d1589fd22file nameSpider-Man (USA) (v2.01).iso (source)
Example 6	Adventure (Q379915)checksum (P4092)157bddb7192754a45372be196797f284file nameAdventure (USA).a26 (source)
Example 7	Ubuntu 18.04.1 LTS (Q110234321)checksum (P4092)f430da8fa59d2f5f4262518e3c177246file nameubuntu-18.04.1-desktop-amd64.iso (source)
See also	checksum (P4092), Redump.org ID (P5290)

Motivation

Many items which exist as a digital file of some kind will have a commonly-used file name, either the default name used by the original creator/distributor of the file, or a name widely adopted by the community that uses the file (e.g. for video games, the file names designated by Redump, No-Intro or TOSEC tend to be broadly used elsewhere). Although the information in a file name can often be captured with other Wikidata properties (e.g. file format (P2701), software version identifier (P348), applies to jurisdiction (P1001), language of work or name (P407)), it is still useful to also have the file name as it is often recognizable to an end user. It's also valuable because a file name typically will convey the most important information about a file to disambiguate it from other related files, which makes it ideal for displaying to end users; if you only use other properties for disambiguation, you may run into situations where there is ambiguity.

As examples 1-3 show, there are some cases where this property may be used as a main value with no qualifiers, in cases where we have a Wikidata item about a specific file. I think more often, it'll be attached to a piece of software or video game which may have multiple files associated with it, so either it will be used as a qualifier, or it will need to have qualifiers attached to it. Examples 4-7 show my motivation for the proposal – I want to import checksums of video games and other software to Wikidata, but I worry that the checksums would get confusing without file names. –IagoQnsi (talk) 00:58, 11 July 2025 (UTC)[reply]

Discussion

Support Dexxor (talk) 12:17, 11 July 2025 (UTC)[reply]
Comment Should this property also be used for file paths, e.g. /etc/passwd (Q307510)file name/etc/passwd? I'm inclined to say no, because we might want to model this as /etc/passwd (Q307510)file namepasswd with an additional /etc/passwd (Q307510)directory/etc (Q4027922) statement. Dexxor (talk) 12:17, 11 July 2025 (UTC)[reply]
Hmm, interesting! I think I'd actually be more inclined to prefer the first example you gave. If we model it the second way you described, it would only work if the directory in question already has a Wikidata item, and there are many directories that don't (and probably shouldn't). I also don't like that the property becomes somewhat misleading if the qualifier isn't understood; a file named `passwd` anywhere else in the filesystem isn't the same type of file. The other option is to simply not support this use case at all and keep the property pretty narrow, which would make it easier to parse. I think I ultimately prefer the first example you described, putting the full path "/etc/passwd" in the 'file name' property, as it's the most recognizable to an end user. IagoQnsi (talk) 16:17, 11 July 2025 (UTC)[reply]
Comment I want to import checksums of video games to Wikidata Regardless of the outcome of this property proposal, please discuss and gain consensus for this. I for one would oppose that, I really don’t think this is a good idea (I’m happy to explain why, not sure this is the right place). Jean-Fred (talk) 20:14, 11 July 2025 (UTC)[reply]
Sure i will love to hear Trade (talk) 23:48, 12 July 2025 (UTC)[reply]

I agree that having a discussion before importing is a good idea. I've started one here: Wikidata talk:WikiProject Video_games#Importing checksums. Best, IagoQnsi (talk) 16:25, 13 July 2025 (UTC)[reply]
Not convinced that a filename in isolation is useful for a software distribution. So many variants for different platforms and configurations for which a URL makes more sense. It has more use for configuration files, but they are often best qualified by a directory path, like /etc/passwd. And much useful filename information is actually stored as a pattern match, like *.html. It would work better as a qualifier than a direct property. – The preceding unsigned comment was added by Vicarage (talk • contribs) at 19:40, 14 July 2025 (UTC).[reply]
I agree – my thinking is that it should only be used as a direct property when there is a universal filename for the entire item (not a specific version/edition of the item), which is pretty rare. –IagoQnsi (talk) 23:16, 18 July 2025 (UTC)[reply]
Oppose This seems to be two things or someone hijacked this proposal. Regarding checksums. These are worthless if you don't state the algorithm like SHA-256 (Q110651361). They are also primary data, so they need a reference. When I see .iso filenames for video games, I think warez and that is a no go. The first three examples where a hardcoded filename is an identifier for a file format are valid. Matthias M. (talk) 13:09, 24 July 2025 (UTC)[reply]
I didn't bother to include the determination method in the examples for sake of brevity, but I definitely would include it in an import (all the examples are MD5). I would also have citations pointing to Redump, No-Intro, or TOSEC; I would not be checksumming the game data myself. Whether a disc-based game is pirated or obtained legitimately, the file extension is going to be .iso; that's just the most common file format for dumping a disc. The sites I mentioned have anti-piracy policies and do not provide downloads; they are not "warez" sites. IagoQnsi (talk) 15:20, 24 July 2025 (UTC)[reply]
I think you should propose the first three examples at Wikidata:Property proposal/Computing instead. As you have been told multiple times now the checksum proposal is controversial. Matthias M. (talk) 11:54, 1 August 2025 (UTC)[reply]
It's posted in computing and in creative work. –IagoQnsi (talk) 15:42, 1 August 2025 (UTC)[reply]
Usually we do not post property proposals in multiple subpages Trade (talk) 14:17, 8 October 2025 (UTC)[reply]
Why not. More exposure is better, as we struggle to get opinions Vicarage (talk) 14:47, 8 October 2025 (UTC)[reply]
Support maybe file-path in addition. --Prototyperspective (talk) 17:48, 28 July 2025 (UTC)[reply]

‎backwards compatible with

Under discussion

Description	software or video games from (usually) precedessor platforms that this system or platform have interoperability with
Represents	backward compatibility (Q844605)
Data type	Item
Domain	item, product model (Q10929058)
Example 1	PlayStation 5 (Q63184502)backwards compatible withPlayStation 4 (Q5014725) (distribution format (P437)distribution formatBlu-ray Disc (Q47770), (distribution format (P437)distribution formatdigital download (Q54820071))
Example 2	Wii (Q8079)backwards compatible withNintendo GameCube (Q182172) (distribution format (P437)distribution formatNintendo GameCube Disc (Q55215790))
Example 3	PlayStation 3 60GB (Q136091325)backwards compatible withPlayStation 2 (Q10680) (distribution format (P437)distribution formatcompact disc (Q34467))
Example 4	PlayStation Portable (Q170325)backwards compatible withPlayStation (Q10677) (distribution format (P437)distribution formatdigital download (Q54820071) (statement is subject of (P805)statement is subject ofPS one Classics (Q136091378))
Example 5	FM broadcasting (Q1368380)backwards compatible withmonoaural (Q1323979)
Allowed values	subclasses or instances of home video game console (Q17589470)
Wikidata project	WikiProject Video games (Q8485882)

Motivation

For now i can only have game consoles in mind but we always have the option to expand the scope later on if we want to --Trade (talk) 23:47, 3 September 2025 (UTC)[reply]

Discussion

Oppose. Seems like these examples are all in the scope of emulates (P4043). I would support adding "backwards compatible with" as an alias for that property. –IagoQnsi (talk) 01:24, 4 September 2025 (UTC)[reply]

The Wii have almost the exact same hardware as the GameCube. To say that the Wii is emulating the GameCube is the same as calling the GameCube itself an emulator. By moving some of the examples to emulates (P4043) you are essentially putting Wikidata in charge of deciding that which backwards compatible consoles are valid and which are not through the use of our own subjective judgement. Just allowing us to have a property for this subject is the easiest and simplest way to avoid any headaches Trade (talk) 02:50, 4 September 2025 (UTC)[reply]

I don't think emulates (P4043) necessarily means that the subject of the claim is video game console emulator (Q1196126); just that the subject is able to replicate the behavior of the object. The PS5/Wii are able to play PS4/GameCube games because they are built on a very similar hardware platform; the early PS3s were able to play PS2 games through hardware emulation (they included the PS2's Emotion Engine chips in addition to the normal PS3 hardware); and the PSP is able to play PSX games through software emulation. I think it would be subjective/original research for us to try to say which of these cases belongs in emulates (P4043) and which belongs in 'backwards compatible with'; it would be better to just have one property. –IagoQnsi (talk) 19:09, 10 September 2025 (UTC)[reply]

And my other concern is that "backward compatibility" is just a buzzword with no precise definition. Sometimes it means that you can just put your old games in the new system and they just work; sometimes it means you can put your old games in and you will be granted a digital copy for the new system, if the game is on the supported list; sometimes your old games are not usable at all and it just means you can rebuy the old games for the new platform. I think our focus should be describing what the consoles actually do, not the marketing terms used to sell them. IagoQnsi (talk) 19:20, 10 September 2025 (UTC)[reply]

The property proposal and description for P4043 states that it is to be used for software and not consoles. If you want to expand the scope of that property (which i am vehemently against) you need to get consensus from the rest of the community

So far all the proposed solutions have only created new problems Trade (talk) 18:09, 17 September 2025 (UTC)[reply]

Okay, I posted a note on the talk page for P4043 asking for more input on this proposal. I'm curious what your take is on my above concerns – how would we deal with wide array of disparate features that are all called "backwards compatibility"? Even the four examples you gave could be contentious – in particular, I wouldn't agree that the PSP is backwards compatible with the PSX. –IagoQnsi (talk) 20:45, 17 September 2025 (UTC)[reply]

I would say you are using a very technical and rigid definition of "backwards compatability" that does not reflect the way that the word is used by the vast majority of people (and companies) in daily use Trade (talk) 19:31, 28 September 2025 (UTC)[reply]

I've been looking and I can't find a reliable source that uses the term "backwards compatible" to describe PSone classics on the PSP. I've found an article about the PSP's PSone emulator, but it never says "backwards compatibility". The fact that we don't agree on what "backwards compatible" means speaks to why I don't think it would be a good property. If the property were named something like "can play games from this platform", that's more clearly defined, but then I don't know how you decide when to use that property vs emulates (P4043). IagoQnsi (talk) 20:04, 28 September 2025 (UTC)[reply]

I do not agree with merging this with emulates (P4043). P4043 is about the emulation software itself, not the entire console that contains it. The term "backward compatibility" simply means that a console is able to play games from previous, older systems and that this feature is officially supported by the manufacturer. --Trade (talk) 02:56, 4 September 2025 (UTC)[reply]

If the question of "true" backwards compatible is something that bothers you can simply use object of statement has role (P3831) as a qualifier to convey whether or not the backwards compatability is hardware or software based. --Trade (talk) 19:39, 28 September 2025 (UTC)[reply]

Okay, based on that definition, some possibilities:

MiSTer (Q110413966) is a hardware device can play games from all of these systems, and that feature is officially supported by the MiSTer developers. Should we use 'emulates' or 'backwards compatible with' here?
ScummVM (Q145568) can play games for a variety of old platforms (DOS, Commodore 64, Apple II, etc), and this feature is officially supported by the ScummVM developers as well as many of the original game developers; ScummVM is frequently used to re-release old games on Steam and GOG. Should we use 'emulates' or 'backwards compatible with' here? Should the property be used on ScummVM, or on the systems which ScummVM can run on?
The game Animal Crossing (Q5345827) ships with a NES emulator that comes with a few built-in games (and can also load any game from an N64 controller pak or GameCube memory card). Nintendo is the developer of the game and all involved consoles, so this is certainly official. Should we use 'emulates' or 'backwards compatible with' here? Should this property go on "Animal Crossing", or should it go on the Nintendo 64 and the GameCube?

Even with the definition you gave, there isn't a clear line between emulation and backwards compatibility. –IagoQnsi (talk) 21:07, 28 September 2025 (UTC)[reply]

An FPGA is not backwards compatible as it is not a newer generation of the same model but a completely different device. ScummVM is a game engine recreation. It is also a new software not an older one that is backwards compatible. These examples don't make any sense in this context. Matthias M. (talk) 21:33, 28 September 2025 (UTC)[reply]

Okay, if the MiSTeR doesn't count because it's not a new generation of the same model, then does the ROG Xbox Ally (Q134739802) count as a new generation of the Xbox (even though it's a handheld PC)? Does the NES Classic Edition (Q26706777) count as a new generation of the Nintendo Entertainment System (Q172742) (even though it uses software emulation)? Is the Super Game Boy (Q1190117) a newer generation of the Game Boy (Q186437) (even though it's not a standalone console)? And for ScummVM, I'm not sure what you mean by " It is also a new software not an older one that is backwards compatible." – all cases of backwards compatibility are based on a new system being created that can run older games. IagoQnsi (talk) 21:46, 28 September 2025 (UTC)[reply]

Must say those are interesting examples. Thanks. Gave me something to think about

1: Emulates. It's a hardware device that comes shipped with pre-existing emulators and hardware to support it. The MiSTer might be endorsed by all or some of the emulator developers but neither MiSTer or the emulators are endorsed or supported by the original game companies. In addition none of the platforms listed are considered to be precedessor of the MiSTer device by anyone
2: Emulates. ScummV is software made explicitly to be able to play games from older platforms on modern hardware. It might technically be called a "game engine recreations" but i don't believe that changes what i say.
"Should the property be used on ScummVM, or on the systems which ScummVM can run on?" This property is meant to be used for products, not individual software.
"Should we use 'emulates' or 'backwards compatible with' here?" You are not paying for an emulator. You are paying for the game. It just so happens that the game comes shipped with an emulator that it needs to run. Add P1547 to the games that use it and use distribution format (P437) and distributed by (P750) as qualifiers
3: Make an item for the NES emulator and use the emulates property. Use depends on software (P1547) and part of (P361) with Animal Crossing as the value of both. For Animal Crossing use P527 to link it to the emulator. The article specifically mentions that using the emulator to play ROMs other than the ones already provided is something done by "hackers" at which point you are already going beyond the scope of what is intended by Nintendo

Trade (talk) 21:44, 28 September 2025 (UTC)[reply]

Notified participants of WikiProject Video games--Trade (talk) 19:53, 28 September 2025 (UTC)[reply]

Oppose seems redundant to PlayStation 5 (Q63184502)compatible with (P8956)PlayStation 4 (Q5014725)has characteristic (P1552)backward compatibility (Q844605) so you can already model this. Matthias M. (talk) 21:00, 28 September 2025 (UTC)[reply]

That statement is nonsensical. The PS5 does not have feature parity with the PS4. Only the games specifically are backwards compatible.

The PlayStation Dynamic Menu graphical shell is not on PS5. The Playroom augmented reality application that comes pre-installed on every PS4 is not on PS5. The Remote Play to Vita application is not on PS5. The PS4 Media Player is not on PS5. The PS4 web browser is not on PS5. The in-game Live from PlayStation feature is not on PS5. The PS4's tournament feature for PS4 games is not on PS5. You cannot use PS4 controllers for PS5 games Trade (talk) 21:11, 28 September 2025 (UTC)[reply]

I don't like this model, because the PS5 is not compatible with the PS4 as a whole; it's compatible with games from the PS4. If one console is listed as compatible with (P8956) another console, that suggests the two consoles can be used together somehow (e.g. Nintendo GameCube–Game Boy Advance link cable (Q3009653)). I think broadening the scope of emulates (P4043) is a better way to model it. –IagoQnsi (talk) 21:12, 28 September 2025 (UTC)[reply]

That can be specified with applies to part (P518)video game (Q7889). I am not sure if the PlayStation 5 is actually running an emulator. I think they achieve this by using the same architecture and an API layer. Like what the appreviation Wine (Q188558) stands for. It is technically not emulation, so using that term is wrong ontologically. Matthias M. (talk) 21:29, 28 September 2025 (UTC)[reply]

So you would be okay if we used excluding (P1011) as a qualifier to list every PS4 game that this does not apply to? Trade (talk) 21:56, 28 September 2025 (UTC)[reply]

We could change the label of emulates (P4043) if the wording is the hangup; maybe something like "provides compatibility with". Wine calls itself "not an emulator" because it only reimplements Windows APIs and does not do any hardware emulation or virtualization. ScummVM and Ruffle (Q97671415) also do no hardware emulation or virtualization, but most people call those both emulators. The line between "emulator" and "compatibility layer" is blurry and arbitrary. It seems pointless to have separate properties for them in Wikidata, and then have to argue about which one to use in many cases. IagoQnsi (talk) 22:10, 28 September 2025 (UTC)[reply]

Can't we just have one for software and one for products that have interoperability with previous iterations? Trade (talk) 01:41, 29 September 2025 (UTC)[reply]

But many things are both. If I'm looking for data about emulators, I would want official emulators to be included too, not just third-party ones. So most items with a "backwards compatible with" claim would also need an "emulates" claim, which is just redundant. In the newer cases, where the compatibility is achieved not through emulation, but instead by having the new console use the same OS and hardware platform... that is probably better represented with, say, operating system (P306)Xbox One and Xbox Series X/S system software (Q17048762). That's how we handle it with other computing platforms. We wouldn't want to have to list that the iPhone 17 is backwards compatible with the iPhone 16, 15, 14, 13, 12, and 11; instead, we just note that all those devices support iOS 26, and the compatibility can be inferred. –IagoQnsi (talk) 02:18, 29 September 2025 (UTC)[reply]

But then you also have the PlayStation consoles who do not share operating system at all Trade (talk) 05:33, 29 September 2025 (UTC)[reply]

Yep, hadn't looked into it before but based on Sony's own presentations and third-party sources, it looks like the PS5's chips include custom logic for mimicking the behavior of the PS4. That would fit into "emulates" (or "provides compatibility with"). Whereas the Xbox Series X/S is able to run Xbox One games natively.

That said, I would also be fine with it if we wanted to model it where PS4 and PS5's system software are versions of the same operating system. That's kind of how it is with Windows – throughout Windows release history, they've added tons and tons of bits of code where new versions of the OS emulate behavior of older versions. But typically we just describe Windows as one continuous operating system.

My point is just that we already have two possible ways to describe this relationship. We can say that the new system is a new version of the old system (with "operating system") or we can say that the new system is separate but is able to mimic the old system (with "emulates"). Those two properties work well: they are distinct and don't have any overlap. I don't think it makes sense to throw in a third property that has heavy overlap with those. –IagoQnsi (talk) 22:02, 29 September 2025 (UTC)[reply]

I just noticed that emulates (P4043) is a subproperty of simulates (P12328) − how about that property? Jean-Fred (talk) 10:17, 2 December 2025 (UTC)[reply]
@Trade, could you please response comments above. Regards, ZI Jony ^(Talk) 17:57, 7 December 2025 (UTC)[reply]
My response to that is the same as my responses to IagoQnsi Trade (talk) 18:19, 7 December 2025 (UTC)[reply]

‎level or map of

Under discussion

Description	video games that this video game level or map belongs to
Aliases	level of\|video game level of\|map of\|video game map of\|stage of\|video game stage of\|map of\|multiplayer map of\|video game map of\|stage of\|stage of\|video game stage of
Represents	video game (Q7889)
Data type	Item
Domain	level (Q1046315), multiplayer map (Q118645825) and virtual pinball table (Q63283385)
Example 1	Dust II (Q43369920)→Counter-Strike 2 (Q111165107)
Example 2	E1M7: Computer Station (Q115474731)→Doom (Q189784)
Example 3	Dust II (Q43369920)→Counter-Strike (Q163628)
Example 4	Black Mesa Inbound (Q133296100)→Half-Life (Q279744)
Example 5	Pinball FX: Agents (Q133294825)→Pinball FX (Q3388606)
Example 6	World 1-1 (Q104640587)→Super Mario Bros. 3 (Q639619)
Example 7	Cell Stage (Q125679627)→Spore (Q210844)
Single-value constraint	no
Distinct-values constraint	no
Wikidata project	WikiProject Video games (Q8485882)

Motivation

--Trade (talk) 23:58, 3 September 2025 (UTC)[reply]

Discussion

Oppose. All of the example links already exist using present in work (P1441); why do we need a new property? –IagoQnsi (talk) 01:15, 4 September 2025 (UTC)[reply]

present in work (P1441) explicitly states that it should only be used with fictional entities. All of the examples listed are elements used to set the time and place within the narrative. They are not considered to be fictional in the context of the games themselves.

"Black Mesa" exists in the Half-Life universe. "Black Mesa Inbound" does not. Because the later is a section of the game itself, not an entity that exists within the story unlike "Black Mesa"

I hope this makes sense for you Trade (talk) 03:03, 4 September 2025 (UTC)[reply]

Sounds like a reasonable argument. It would seemingly be a subproperty of the vague part of (P361), instead of present in work (P1441). -wd-Ryan (Talk/Edits) 16:51, 4 September 2025 (UTC)[reply]

Hmm, okay, I see what you're saying. But this proposal still has the same problem that I described in my !vote on Wikidata:Property proposal/levels: levels/maps are conceptually distinct from chapters/episodes, and combining them into one property seems unuseful. I think levels/maps should go in present in work (P1441), and chapters/episodes should go in part of (P361) (or there could be a new property proposed that also includes chapters/episodes in TV shows and other types of media). –IagoQnsi (talk) 06:42, 7 September 2025 (UTC)[reply]

TV show episodes are already included in "part of series" Trade (talk) 10:41, 7 September 2025 (UTC)[reply]

The part of the series (P179) and season (P4908) properties would definitely work for episodic video games, or any sort of game that's released in a serialized way. Otherwise I think part of (P361) is probably the best fit for chapters. Thinking about other forms of media that are split into chapters, that seems to be the go-to property (e.g. Ulysses (Q6511), Symphony No. 9 (Q11989)). IagoQnsi (talk) 15:17, 7 September 2025 (UTC)[reply]

For this to work the description of either of these properties need to be changed to have their scope widened. I am not of using P361 on or with video game items as a whole. It's so generic that it becomes incredible difficult to actually define an workable scope for it's use Trade (talk) 00:22, 5 October 2025 (UTC)[reply]

Comment For context − see Wikidata:Property proposal/levels for an earlier property proposal in the other direction game → level; several people (including me) argued that it should be modeled in the other direction, level → game, like is proposed here. Jean-Fred (talk) 11:57, 4 September 2025 (UTC)[reply]
Support - This property is a good feature; this will help linking items with each other and is diff from present in work (P1441), it is more generic for items such as level (Q1046315). QwertyZ34 (talk) 20:51, 8 September 2025 (UTC)[reply]
Comment "level or map of" is definitely a bad name when you search for it and don't know that the context is exclusively for video games. I also dislike that this requires such a specific property when present in work (P1441) or published in (P1433) already exist, but I also don't have a better idea. Matthias M. (talk) 10:22, 4 October 2025 (UTC)[reply]
Both of these properties have a respective 186K and 46 million uses. I think we can survive having a subproperty for the sake of improving our modeling Trade (talk) 00:20, 5 October 2025 (UTC)[reply]
Comment Video game levels are already variously modeled using present in work (P1441) (680 instances; SPARQL) and part of (P361) (58 instances; SPARQL). I think technically the latter is more correct, and I don't see why it being generic is a problem—can you give an example in which an instance of level (Q1046315) with a part of (P361) statement whose value is an instance of video game (Q7889) would ever mean anything else than the property you're proposing? AVDLCZ (talk) 21:24, 18 October 2025 (UTC)[reply]
If you query items whose value are video games you get everything from video game levels, video game editions to downloadable content, expansion packs, fictional missions and even whole theme songs

It's awful modeling plain simply Trade (talk) 23:20, 18 November 2025 (UTC)[reply]
I think you misunderstand my question. If you just query for items that are a part of (P361) of a given video game, then you will get all those things, but if you additionally limit the query to items that are an instance of (P31) of level (Q1046315) then I believe you should get exactly what you're looking to get with this proposed property. AVDLCZ (talk) 01:10, 19 November 2025 (UTC)[reply]
You shouldn't have to limit the query to items with P31 because the property used should already indicate the relationship between the two items in the first place Trade (talk) 20:40, 20 November 2025 (UTC)[reply]
Is there any precedent for this? Applying this consistently would mean we'd be creating thousands of subproperties of part of (P361) for all kinds of subjects, which certainly isn't the case now, and it doesn't seem there's anything special about video game levels in this regard. Items can have parts of different types, and distinguishing them in a query using P31 seems to be the intended method, not creating a new property for each type. AVDLCZ (talk) 09:20, 21 November 2025 (UTC)[reply]

Oppose based on discussion above. The inconsistent use of present in work (P1441) and part of (P361) in video game levels should be fixed, preferably by using part of (P361) everywhere. AVDLCZ (talk) 09:25, 21 November 2025 (UTC)[reply]

So in short your solution to the inconsistent use of present in work (P1441) is to move the inconsistent use to part of (P361)

All you have accomplished is to make part of (P361) Trade (talk) 00:18, 23 November 2025 (UTC)[reply]

Comment I think part of (P361) is meant for when the part does not exist without the whole ; are there cases where a level is present in more than one game? I’m thinking of eg Mario Kart circuits. Because if yes, then I’m not sure we can use P361 Jean-Fred (talk) 10:24, 2 December 2025 (UTC)[reply]

Audiovisual work

SFDb original ID

Done: SFDb original ID (P14138) (Talk and documentation)

Description	identifier of an original work that a visual work is based on at the Swedish film database
Issued by	Swedish Film Database (Q1139587)
Data type	External identifier
Example 1	Michael "Crocodile" Dundee (Q16209856)→536628
Example 2	1408 (Q4028807)→537875
Example 3	2010: Odyssey Two (Q1751752)→536774
Allowed values	\d+
Source	https://www.svenskfilmdatabas.se/sv/forlagor/
External links	Use in sister projects: [ar] • [az] • [bn] • [de] • [en] • [es] • [fa] • [fr] • [he] • [hi] • [it] • [ja] • [ka] • [kn] • [ko] • [ml] • [mr] • [nl] • [pl] • [pt] • [ro] • [ru] • [sv] • [te] • [tr] • [ur] • [vi] • [zh] • [commons] • [species] • [wd] • [en.wikt] • [fr.wikt].
Planned use	There are some uses of exact match (P2888)
Number of IDs in source	8 271
Expected completeness	always incomplete (Q21873886)
Implied notability	Wikidata property for an identifier that suggests notability (Q62589316)
Formatter URL	https://www.svenskfilmdatabas.se/sv/item/?type=original&itemid=$1
URL match pattern	^https?:\/\/(?:www\.)?svenskfilmdatabas\.se\/sv\/item\/\?type=original&itemid=((1\d{6}\|[1-9]\d{3,5}))
Robot and gadget jobs	Migrate the uses of exact match (P2888) into this property when created
Country	Sweden (Q34)
See also	Swedish Film Database ID (P2334), Swedish Film Database person ID (P2168), Swedish Film Database company ID (P2335), Swedish Film Database soundtrack ID (P2336), Swedish Film Database group ID (P2337)
Applicable "stated in"-value	Swedish Film Database (Q1139587)
Single-value constraint	yes
Distinct-values constraint	yes
Wikidata project	WikiProject Sweden (Q11509296)

Motivation

Type of identifier for original works at the Swedish film database. Other properties for this source already exists, would be useful works based on the same work. Can be plays, books, video games or original characters etc. – The preceding unsigned comment was added by Sabelöga (talk • contribs).

Discussion

Support Yes, looks like a good addition. Jean-Fred (talk) 11:55, 25 January 2026 (UTC)[reply]
@Sabelöga, Jean-Frédéric: Done ArthurPSmith (talk) 18:21, 16 February 2026 (UTC)[reply]

Literature

See also: Wikidata:WikiProject Books

Other relevant projects: Category:Book WikiProjects

‎IRIS UNIL author ID

Under discussion

Description	identifier for an author in IRIS UNIL, the open-access repository of the University of Lausanne
Data type	External identifier
Domain	human (Q5)
Example 1	Amar Abderrahmani (Q132774948)→10460d01-393e-4475-90ec-9f43f25ecbad
Example 2	Annelore Bessat (Q132774978)→87a671b3-6802-4ae2-be2f-be890b79bcdf
Example 3	Jacques Dubochet (Q41585344)→3a3a2f35-3d86-4521-b3c6-49291b8b63a1
Allowed values	([0-9a-f]{4})(?1)(\-(?1))(?2){3}(?1){2}
Source	https://iris.unil.ch/browse/rpname?scope=10ef7f4d-1859-447d-ba77-365cbd941f2c&bbm.rpp=40
Planned use	manual match; eventually Mix'n'match similarly to other property created under by Wikidata:WikiCite/Researchers in Switzerland.
Number of IDs in source	29272
Expected completeness	always incomplete (Q21873886)
Formatter URL	https://iris.unil.ch/entities/person/$1
Applicable "stated in"-value	IRIS (Q131744810)
Wikidata project	Wikidata:WikiCite/Researchers in Switzerland (Q125422363)

Motivation

Notified participants of WikiProject Switzerland New open-access repository. Nwidmer (talk) 23:06, 14 February 2025 (UTC)[reply]

Discussion

Neutral Please add examples --Kdkeller (talk) 23:03, 19 February 2025 (UTC)[reply]
Done Nwidmer (talk) 08:27, 23 February 2025 (UTC)[reply]
- In the three examples, the page starts loading correctly but afterwards it transforms into "Erreur lors de la récupération de l'Item" - the website seems unstable. --Epìdosis 13:48, 26 February 2025 (UTC)[reply]

I did my best, but I am cautious in general when proposing repository IDs, so I also don’t expect it to be “mature.” We have a dedicated section on our project page to discuss in advance such proposals, and we take our time for this reason. In a way, we prefer to create items of researchers sometimes also hoping to improve the overall architectues of these websites.--Alessandro Marchetti (WMCH) (talk) 13:56, 26 February 2025 (UTC)[reply]

Hi all, I just noticed this proposal and I am trying my best to fix it; the "Researchers in Switzerland" project is usually suggesting new propoerties at an adequate pace (that is if we can properly handle the reconciliation within few years) but if approved I can ask User:Bargioni if he can help with the Mix'n'Match. --Alessandro Marchetti (WMCH) (talk) 13:20, 26 February 2025 (UTC)[reply]

Neutral Interesting repo because it contains more than 30200 names of researchers. But at the moment, it looks like it is not accurate: no ORCIDs, and especially too many "Unnamed" (e.g.: https://iris.unil.ch/entities/person/1f136f40-b810-49ea-9aa3-f5989d0f7367). I prefer to wait before creating a P. -- Bargioni 🗣 14:50, 26 February 2025 (UTC)[reply]

Thank you for your comment and information. This repository is based on Dspace-CRIS (Q96473537), such as the repository from the University of Bern (Q659080): BORIS - Bern Open Repository and Information System (Q111308607). It seems that various properties exist for similar repositories in Italy for instance: [22]. Nwidmer (talk) 22:42, 28 February 2025 (UTC)[reply]

‎Kantonsspital St.Gallen Author ID

Under discussion

Description	identifier for an author in the repository of the Kantonsspital St.Gallen
Data type	External identifier
Domain	human (Q5)
Example 1	Daniel Mojon (Q29050592)→32145-daniel-mojon
Example 2	Monika Renz (Q92423574)→61-monika-renz
Example 3	subject→value
Source	forschung2.kssg.ch
External links	Use in sister projects: [ar] • [az] • [bn] • [de] • [en] • [es] • [fa] • [fr] • [he] • [hi] • [it] • [ja] • [ka] • [kn] • [ko] • [ml] • [mr] • [nl] • [pl] • [pt] • [ro] • [ru] • [sv] • [te] • [tr] • [ur] • [vi] • [zh] • [commons] • [species] • [wd] • [en.wikt] • [fr.wikt].
Number of IDs in source	584
Formatter URL	https://forschung2.kssg.ch/en/profiles/$1
Wikidata project	Q125422363

Motivation

Notified participants of WikiProject Switzerland New Swiss repository. Nwidmer (talk) 23:19, 14 February 2025 (UTC)[reply]

Discussion

Neutral Please add examples --Kdkeller (talk) 22:59, 19 February 2025 (UTC)[reply]
Done Nwidmer (talk) 10:09, 23 February 2025 (UTC)[reply]
- Both examples show an error ERR_CERT_COMMON_NAME_INVALID - I would suggest solving it before the creation of the property. --Epìdosis 13:50, 26 February 2025 (UTC)[reply]

I leave the same comment I have left also in this proposal. These repositories of local institutions can be quite “delicate,” so proposing two at the same time can be challenging. We adopt a “baby step” approach to avoid too much dispersion, and we do our best to monitor these requests... but in general, we try at the moment to converge the energy into the creation of higher-quality items rather than adding more identifiers. Do we have any direct contact with the manager of this website, if needed?--Alessandro Marchetti (WMCH) (talk) 14:02, 26 February 2025 (UTC)[reply]

Comment The resolvable URL appears to be https://forschung.kssg.ch/en/profiles/$1 now (not forschung2 anymore). Also, only the numeric ID appears necessary − https://forschung.kssg.ch/en/profiles/61 resolves just fine. Jean-Fred (talk) 10:29, 2 December 2025 (UTC)[reply]

identifier of a version or edition, in the Lubimyczytać website

Under discussion

Description	Lubimyczytać is a Polish version of Goodreads, very similar and widely used.
Data type	External identifier
Example 1	Smutek spełnionych baśni (Q136750216)→154218/smutek-spelnionych-basni
Example 2	Smutek spełnionych baśni (Q136750216)→89881/smutek-spelnionych-basni
Example 3	Inne pieśni (Q133806638)→87695/inne-piesni
Formatter URL	https://lubimyczytac.pl/ksiazka/$1

Motivation

Many Polish books are indexed there, and not in Goodreads. --Piotrus (talk) 07:35, 10 November 2025 (UTC)<[reply]

Discussion

Sorry, this form is so painful to fill in I can only explain it in words. I don't even know if I got data typəexternal identifier correctly. Even some keyboard shortcuts don't work here. Anyway, Lubimyczytać is Polish version of Goodreads, very similar and widely used. I would like to request a LC equivalent of Property:P2969 Goodreads work ID and may be others, see Wikidata property of Q2359213 Goodreads . For example, book Q136750216 has two editions and two page on Lubimycztać but not on Goodreadsː https://lubimyczytac.pl/ksiazka/154218/smutek-spelnionych-basni and https://lubimyczytac.pl/ksiazka/89881/smutek-spelnionych-basni. I assume the ID is ksiazka/154218 and ksiazka/89881 (ksiazka means book in Polish). Note I am unable to identify a LC equivalent of Property:P8383 , unfortunately. For the equivalent of Goodreads author ID , see https://lubimyczytac.pl/autor/11936/jozef-kozielecki. Autor =author = (so I am also requesting a corresponding Lubimyczytać author ID). TIA. --Piotrus (talk) 07:35, 10 November 2025 (UTC)[reply]

I use lubimyczytać.pl myself, I understand the need for such a property, but the fact that lubimyczytać.pl does not have "elements" for literary works but only for editions makes little sense for me. We would have to create Wikidata elements for e.g. 10 Symposiums of Plato, which would be linked to 10 editions at lubimyczytać.pl, and none of them would be linked to a wikidata element (Q486727) for the exact literary work due to the lack of an equivalent on lubimyczytać.pl. That website has numerous errors. Maybe using Property:P1325 or else could help temporarily? In any case, I am not against the creation of such a property, but it seems to me that its application will necessarily be limited. Gower (talk) 18:41, 10 November 2025 (UTC)[reply]

@Gower Yes, the lack of main work page is quite annoying. We could, perhaps, make a temporary rule that until LC creates a proper work category, we can use the first edition as an equivalent? In either case, their version/edition ID is perfectly fine, just as Goodreads (and ditto for their author). If we cannot get a LC equivalent of P8383, oh well. The use of P1325 is an option too. Piotrus (talk) 03:32, 13 November 2025 (UTC)[reply]

You cannot expect anyone to fill this out for you if you wont even give us any property examples Trade (talk) 01:40, 28 November 2025 (UTC)[reply]

@Trade What do you mean? The template is opaque, I am not a wikidata expert, I don't know what's missing. I provided links and description in discussion. What's missing? Piotrus (talk) 06:07, 11 December 2025 (UTC)[reply]

You could try and ask ArthurPSmith for help filling out the proposal@Piotrus:--Trade (talk) 11:44, 11 December 2025 (UTC)[reply]

@Trade Thank you. @ArthurPSmith - could you help? Piotrus (talk) 11:45, 11 December 2025 (UTC)[reply]

@Piotrus, Trade: I have updated the proposal template per the above discussion. However note the ID seems to require the book name slug appended to resolve properly. It would be helpful to have at least one or two more books to link as examples. ArthurPSmith (talk) 19:28, 11 December 2025 (UTC)[reply]
@ArthurPSmith Sureː 1) https://lubimyczytac.pl/ksiazka/4943329/wiek-kapitalizmu-inwigilacji 2) https://lubimyczytac.pl/ksiazka/3943/inne-piesni . The latter is for Q6035299 . Note specific editions we - actually have a separate wikidata version for 2003 one which is https://lubimyczytac.pl/ksiazka/87695/inne-piesni Q133806638

Do you need more examples? Piotrus (talk) 00:41, 12 December 2025 (UTC)[reply]
No - however as an external identifier this property maybe should be limited to specific editions like that last example you provided? This should be discussed further here. Wikidata does encourage items for each edition of a book, so that shouldn't be a problem. See Wikidata:WikiProject Books on Work Items and Editions Items for details on the preferred data model. ArthurPSmith (talk) 19:35, 15 December 2025 (UTC)[reply]
@ArthurPSmith Makes sense. Piotrus (talk) 00:46, 22 December 2025 (UTC)[reply]
Support. --Wyslijp16 (talk) 16:41, 25 December 2025 (UTC)[reply]

Goodreads genre ID

Under discussion

Description	identifier for a genre or subject on Goodreads
Represents	Goodreads (Q2359213)
Data type	External identifier
Example 1	Warhammer 40,000 (Q209026)→40k
Example 2	non-fiction literature (Q27801)→non-fiction
Example 3	manga (Q8274)→manga
Example 4	feminist literature (Q26987750)→feminism
Example 5	Wikipedia (Q52)→wikipedia
Source	https://www.goodreads.com/genres
External links	Use in sister projects: [ar] • [az] • [bn] • [de] • [en] • [es] • [fa] • [fr] • [he] • [hi] • [it] • [ja] • [ka] • [kn] • [ko] • [ml] • [mr] • [nl] • [pl] • [pt] • [ro] • [ru] • [sv] • [te] • [tr] • [ur] • [vi] • [zh] • [commons] • [species] • [wd] • [en.wikt] • [fr.wikt].
Number of IDs in source	Unknown
Expected completeness	always incomplete (Q21873886)
Formatter URL	https://www.goodreads.com/genres/$1
Country	United States (Q30)
Single-value constraint	yes
Distinct-values constraint	yes

Motivation

--Trade (talk) 13:07, 7 December 2025 (UTC)[reply]

Discussion

Support -wd-Ryan (Talk/Edits) 18:02, 8 December 2025 (UTC)[reply]
Comment This doesn't look like a curated identifier of some background list of genres. It's rather a direct output of user-generated labels, and not de-duplicated. This could lead to many redundant entries. For example, see fantasy, Ｆａｎｔａｓｙ, ℱantasy and Fañtasy. Schmidt Fu (talk) 21:43, 9 December 2025 (UTC)[reply]

Scientific literature

Standard Number

Under discussion

Description	A standard serial number
Represents	Standard Number (Q138013541)
Data type	String
Domain	technical standard (Q317623),specification edition (Q55155149)
Example 1	International Standard Book Number (Q33057) → ISO 2108
Example 2	ASTM D638 (Q57838245) → ASTM D638
Example 3	Information and documentation - Rules for bibliographic references and citation to information resources (Q11079651) → GB/T 7714
Example 4	ISO/IEC 7942-1:1994: Information technology—Computer graphics and image processing—Graphical Kernel System (GKS)—Part 1: Functional description (Q26874730) → ISO/IEC 7942-1:1994
Single-value constraint	yes
Distinct-values constraint	yes

Motivation

Each technical standard (Q317623) has a unique Standard Number (Q138013541). Most standards have a standard number.--Shizhao (talk) 14:41, 5 February 2026 (UTC)[reply]

Discussion

Support --Tinker Bell ★ ♥ 21:29, 10 February 2026 (UTC)[reply]
Is Standard Number (Q138013541) just for the concept of a number that can identify a standard, or something more specific with the name "Standard Number"? If just for the concept, string is the correct type, but the labels of Q138013541 and the proposal shouldn't be in title case; if it is the name of something it should be an identifier. Standard Number (Q138013541) also uses subclass of (P279) which makes it a type of standard - facet of (P1269) or part of (P361) is more likely. Peter James (talk) 14:14, 11 February 2026 (UTC)[reply]
Q138013541 is similar to an International Standard Book Number (Q33057)(ISBN); while ISBNs are used for books, Q138013541 is used for most standards. And fixed Standard Number (Q138013541) about problem of P279 Shizhao (talk) 03:03, 12 February 2026 (UTC)[reply]
Is this a unique identifier? Is it just the number part of these, or is it the full string with the "ISO" or whatever prefix as well? ArthurPSmith (talk) 00:12, 13 February 2026 (UTC)[reply]
Each standard number is unique, including prefixes such as ISO. Shizhao (talk) 03:07, 13 February 2026 (UTC)[reply]
In that case the data type probably should be external-id ? ArthurPSmith (talk) 16:55, 16 February 2026 (UTC)[reply]

Video

‎DVD region code

Under discussion

Description	DVD release is restricted to region code
Represents	DVD region code (Q746611)
Data type	Item
Domain	item
Example 1	Barbarella (Q131454252)→DVD region code 1 (Q55901337)
Example 2	新スター・トレック DVDコンプリート・シーズン 6 ― コレクターズ・ボックス (Q131454144)→DVD region code 2 (Q55901567)
Example 3	The Video Collection: 1997–2003 (Q26356)→DVD region code 1 (Q55901337)
Allowed values	DVD region code 1 (Q55901337), DVD region code 2 (Q55901567), DVD region code 3 (Q55901697), DVD region code 4 (Q55901713), DVD region code 5 (Q55901721), DVD region code 7 (Q55901736), DVD region code 6 (Q55901755), DVD region code 8 (Q124719022)
Expected completeness	always incomplete (Q21873886)
Single-value constraint	no
Distinct-values constraint	no
Wikidata project	WikiProject Film (Q8485793)

Motivation

Meant for DVD releases of films, shows etc. –Shisma (talk) 17:47, 16 December 2024 (UTC)[reply]

Discussion

WikiProject Movies has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead. –Shisma (talk) 17:49, 16 December 2024 (UTC)[reply]

Support Rémi sim (talk) 18:16, 16 December 2024 (UTC)[reply]

Comment no opinion; I don't really understand the significance of this data point Jerimee (talk) 20:38, 16 December 2024 (UTC)[reply]

Comment Can you explain where you sourced those example values from? I thought the region is per release and not per title. Matthias M. (talk) 19:39, 17 December 2024 (UTC)[reply]

You are right, the region is per release. The examples only refer to releases, not titles. In the first example, the region was specified on amazon, in the second example, it is specified on the box (which it is usually), in the third example, the region was specified on the discogs page. – Shisma (talk) 21:41, 17 December 2024 (UTC)[reply]

Leaning towards

Oppose. This is too narrowly focused. I doubt that a separate property is needed for this data (and I doubt that this data is significant at all). Most likely some existing properties can be used as qualifiers for this purpose, and if not, it should be something more universal (to also handle NTSC/PAL/SECAM and others regional media codes). Solidest (talk) 00:28, 30 December 2024 (UTC)[reply]

Support --Trade (talk) 11:45, 30 December 2024 (UTC)[reply]

There is no point restricting this property to just one type of media. If you change this to a media-agnostic property (for instance "AV-media region code; region lockout code for audiovisual media") I will support it. Then you can use it for Bluerays too, which have different regions. I think it's worth documenting this since releases of a movie might not be available in an regions of the world. Infrastruktur (talk) 18:57, 14 January 2025 (UTC)[reply]

@Shisma: One other user have spoken in favor of a media-agnostic property. DVD region code and Blueray region code can be aliases. What is your opinion on this? Infrastruktur (talk) 14:17, 10 February 2025 (UTC)[reply]

I didn't know there is a blueray region code. sure, but what should we call it? DVD region code and Blueray region code or technically restricted to region? – Shisma (talk) 15:24, 10 February 2025 (UTC)[reply]

If you put "technically restricted to region" as the label and the two others as aliases. Whenever you edit claims and start typing "DVD reg" it will show up in the search results as "technically restricted to region (DVD region code)" Add it as "mul" aliases too. Infrastruktur (talk) 16:09, 10 February 2025 (UTC)[reply]

Comment leaning to

Oppose. I don't think we should usually have separate items for individual DVD releases. Perhaps this property might be useful as a qualifier on publication date (P577), to be used alongside place of publication (P291) and distribution format (P437). But I would tend to think that, unless a particular release is very noteworthy, or unless there were very few releases ever worldwide of a title, then this level of detail is better left to other more specialist databases, rather than here. Jheald (talk) 23:24, 20 January 2025 (UTC)[reply]

What other specialist databases Trade (talk) 17:16, 27 January 2025 (UTC)[reply]

There seem to be only 5 DVD releases listed in Wikidata atm. Apologies for not checking this before. Since we should have 100 notable items to use this on, this effectively means we can only use this as a qualifier, unless we also decide to change the modelling (which is outside the scope of this discussion). Infrastruktur (talk) 14:04, 10 February 2025 (UTC)[reply]

Comment leading to

Support: should there be an option for region 0 (ALL)? Or should we somehow signal that a a DVD announced as region 0 or region free should be filled in as having all regions 1 to 8? Mind Booster Noori (talk) 19:56, 27 January 2025 (UTC)[reply]

No value for no restrictions? –Shisma (talk) 21:51, 27 January 2025 (UTC)[reply]

the first Trade (talk) 09:25, 9 February 2025 (UTC)[reply]

Comment I wonder if digital rights management system (P1032) combined with another general qualifier like has part(s) (P527) would be better in this case? Granted, I have little knowledge of DVD region codes. —Tomodachi94 (talk) 17:43, 16 March 2025 (UTC)[reply]

Comment I like this proposal broadly, but I would definitely like the scope to be widened from just DVDs, as there are many other forms of media that have region-locking. Blu-rays have regions A, B, C, and ABC; PlayStation 2/3/4 have about a dozen regions defined by a two-digit code; many consoles (Xbox 360, PlayStation) have PAL, NTSC-U/C, and NTSC-J; etc etc. I think we should have one generic "region code" property that incorporates all of these. –IagoQnsi (talk) 23:59, 17 July 2025 (UTC)[reply]

Support. Rzuwig^► 12:57, 29 October 2025 (UTC)[reply]

Image

See also: Wikidata:WikiProject Visual arts

print matrix state

Under discussion

Description	stage of development of the relief matrix, after a permanent modification
Represents	state (Q7602996)
Data type	Quantity
Domain	item, print (Q11060274)
Example 1	Frontispiece to Christopher Saxton's Atlas of the Counties of England and Wales State I (Q105949375)→ 1
Example 2	Frontispiece to Christopher Saxton's Atlas of the Counties of England and Wales State II (Q105949380)→ 2
Example 3	La vengeance de Hop-Frog (Q86915014)→ 2
Planned use	edition number (P393) is sometimes incorrectly used to provide state information in existing items and should be replaced.
Single-value constraint	yes
Wikidata project	WikiProject Visual arts (Q13627814)

Motivation

This proposed property will become the way to fill in the state of a print, which is an important information for museums to document their items. Ideally value should be displayed as Roman numeral but as far as I know, it's currently impossible in Wikibase. Peuc (talk) 14:22, 18 June 2025 (UTC)[reply]

Discussion

Notified participants of WikiProject Visual arts - Peuc (talk) 14:30, 18 June 2025 (UTC)[reply]

Comment @Peuc: No idea of what this is about, but to display it with roman literals I think the Wikidata way is to create items for states, and put the roman literals as labels, and describe what those states are about in descriptions. This also allows to describe the states with statements. For those like me who knows nothing it allows to get documentation in a few clicks by getting to the state item and its data. author TomT0m / talk page 14:46, 18 June 2025 (UTC)[reply]

I've only come across these being referred to in English-language prose as "first state", "second state", etc., e.g. here. I would have assumed that Roman numerals were a way of indicating these in French, as that's how ordinal numbers for centuries, etc., are written in that language, but en:State (printmaking) seems to imply that Roman numerals are used in English for these. Nonetheless, if we were to follow TomT0m's suggestion, I would still expect the English-language labels of the items to be "first state", etc. @Johnbod: any thoughts on whether/how often Roman numerals are used in English for states in printmaking? Ham II (talk) 16:57, 18 June 2025 (UTC)[reply]

I'm not sure it is absolutely necessary to impose the roman numerals. To be more universal, standard digits should be use, imo. --Daehan (talk) 18:05, 21 June 2025 (UTC)[reply]

If they are items they can have labels according to language, so standard numbers are OK. And clients like infoboxes can render them however they like. And there can be descriptions to the items to help those who does not know what it is about. author TomT0m / talk page 18:15, 21 June 2025 (UTC)[reply]

Arabic numbers are fine for this property. Peuc (talk) 21:19, 5 January 2026 (UTC)[reply]

Support--Oursana (talk) 17:15, 18 June 2025 (UTC)[reply]

Support Really useful to distinguish between different states of a same print. --Daehan (talk) 18:04, 21 June 2025 (UTC)[reply]

Comment I think this needs a clearer label (in French and English) - 'state' can mean a lot of different things from locations to conditions. "print matrix state" perhaps? ArthurPSmith (talk) 19:10, 2 July 2025 (UTC)[reply]

@Peuc: What ArthurPSmith said is important: ¿could you consider using a more specific label for this property? --Tinker Bell ★ ♥ 21:34, 9 September 2025 (UTC)[reply]
@Tinker Bell Thanks for your reminder! "print matrix state" sounds good to me. I suggest however the description of the property reminds contributors temporality is important: the value describes the matrix state at the time of printing, which may or may not have evolved since then. Peuc (talk) 20:34, 3 October 2025 (UTC)[reply]
Oppose with current label/description. I agree with ArthurPSmith that this should have label and description that make it easy to understand what a property is about. ChristianKl ❪✉❫ 22:15, 2 October 2025 (UTC)[reply]
- @ChristianKl: The label has been corrected. Do you agree with this? --Tinker Bell ★ ♥ 21:44, 3 October 2025 (UTC)[reply]
  I think the label is better but I think the description still doesn't make it clear to people who don't understand what the concept is about what it means. ChristianKl ❪✉❫ 12:23, 4 October 2025 (UTC)[reply]
  @ChristianKl: Since it’s in the property name, I think we can remove the ambiguous word "state" from the description to replace it with something more common like "version". Would it help? Peuc (talk) 14:47, 6 October 2025 (UTC)[reply]
  Do you honestly think that replacing a single world would make someone who doesn't know what it is know what it is? I would expect that using more than a single world is likely helpful for bringing the concept across. ChristianKl ❪✉❫ 17:40, 7 October 2025 (UTC)[reply]
  @ChristianKl What about "stage of development of the print source as modified by the artist"? Peuc (talk) 20:01, 8 October 2025 (UTC)[reply]
  - @Peuc, ChristianKl: What about «stage of development of the relief matrix, after a permanent modification»? --Tinker Bell ★ ♥ 03:57, 9 November 2025 (UTC)[reply]
    @Tinker Bell, ChristianKl: Sounds good to me. Peuc (talk) 15:34, 11 November 2025 (UTC)[reply]
    @Tinker Bell, ChristianKl, Peuc: How about "in printmaking, a stage of development of the relief matrix"? Then everyone can take away that it's a term in printmaking, which is the main thing one needs to know about it. Are the modifications necessarily permanent, or can they themselves be modified in later states? Ham II (talk) 21:06, 12 November 2025 (UTC)[reply]
    @Ham II: Sounds good to me too. Modifications are necessarily permanent and can be modified further in later states. What you cannot do is "undo" modifications to go back to the previous state. Peuc (talk) 21:12, 5 January 2026 (UTC)[reply]
@Tinker Bell, ChristianKl, Peuc: I had marked this as ready per the above discussion, but then realized there still seemed to be an open question about the datatype - it seems to me this should probably be item datatype, and not just a number, as there seem to be language differences in how this is represented (from @TomT0m, Ham II: above). ArthurPSmith (talk) 02:28, 12 November 2025 (UTC)[reply]
Precisely because there are several ways to represent this value, I think its numerical value should be stored. After all, it's just an ordinal. I don't like Item datatype either, how many items should we create in that case? --Tinker Bell ★ ♥ 15:38, 12 November 2025 (UTC)[reply]
Grove Art Online's entry for "State" mentions Degas's After the Bath as having 23 surviving states, which is implied to be an exceptionally high number. No impressions (i.e., "copies") of this print in any collection seem to have an item on Wikidata. Ham II (talk) 21:06, 12 November 2025 (UTC)[reply]

After thinking a little bit about that I'm not sure why edition number (P393) is actually incorrect. It's very similar if not exactly the same ? It should be of domain "print work" of something like this instead of just "written work". author TomT0m / talk page 17:49, 12 November 2025 (UTC)[reply]
@TomT0m: MARC indeed uses same field to describe both edition numbers and state. However, for me, these are two distinct concepts: 1- Each published book is considered a final work, regardless of its edition number while in printmaking only the work with the greatest state number is the final version. When a new state exists, prints from previous version becomes drafts or technical tests of lesser importance. 2- States are the result of irreversible physical modifications of the source print matrix (made of wood, copper, metal, …). You can always print previous editions of a book but it’s impossible to print new copies of a previous state after the matrix is altered. Peuc (talk) 21:05, 5 January 2026 (UTC)[reply]

Podcast show

See also: Wikidata:WikiProject Podcasts

Theatre art

See also: Wikidata:WikiProject Performing arts, Wikidata:WikiProject Theatre

Fiction

See also: Wikidata:WikiProject Fictional universes, Wikidata:WikiProject Narration

For projects about specific universes, see: Category:Fiction WikiProjects

health/hit points

Under discussion

Description	health or armor points of this video game, board game or role-playing game character
Represents	health (Q668136)
Data type	Quantity
Example 1	Adam Warlock (Q130232493) > 250
Example 2	Infested Girl (Q130232401) > 16
Example 3	Mercy (Q28592386) > 225
Example 4	Sniper (Q128164668) > 90
Example 5	Sniper (Q128164668) > 50 (applies to part > armor (Q130232601))
Example 6	Claude Speed (Q2721597) > 10
Example 7	Claude (Q14805400) > 100
Example 8	Zoey (Q65924442) > 100
Example 9	Creeper (Q13164404) > 20 (applies to work (P10663) > Minecraft (Q49740))
Example 10	Cacodemon (Q108324133) > 400 (applies to work (P10663) > Doom (Q189784))
Wikidata project	WikiProject Video games (Q8485882)

Motivation

We have no way of modeling this so a property is needed

TomT0m Valentina.Anitnelav Shisma (talk) ElanHR Arlo Barnes (talk) Maria zaos (talk) EEMIV (talk) OmegaFallon (talk) Kurzov (talk) dseomn (talk) Natureshadow (talk)
Notified participants of WikiProject Fictional universes--Trade (talk) 21:52, 3 September 2024 (UTC)[reply]
Nicereddy — 13:40, 04 May 2015 (UTC) Danrok — 18:20, 30 October 2015 (UTC) Lewis Hulbert — 20:26, 13 December 2017 (UTC) Santer — 22:03, 26 May 2018 (UTC) Kirilloparma — 00:30, 5 August 2018 (UTC) Cwf97 — 18:33, 22 October 2018 (UTC) YotaMoteuchi — 08:09, 22 May 2019 (UTC) CptViraj — 02:49, 17 September 2019 (UTC) BugWarp — 23:19, 26 October 2019 (UTC) WikiSyn — 21:52, 26 December 2019 (UTC) Cynde Moya — 16:07, 31 March 2020 (UTC) Dexxor — 14:51, 02 May 2020 (UTC) Floyd-out — 09:14, 22 July 2020 (UTC) Jean-Frédéric — 11:22, 11 September 2020 (UTC) A particle for world to form — 11:15, 17 May 2021 (UTC) Dollarsign8 — 01:40, 01 November 2021 (UTC) Wd-Ryan — 02:20, 03 October 2022 (UTC) Master Of Ninja — 17:37, 18 October 2022 (UTC) Matthias M. — 09:28, 12 February 2023 (UTC) VGPaleontologist — 21:03, 12 February 2023 (UTC) Tomodachi94 — 18:34, 26 February 2023 (UTC) thgiex — 12:17, 6 April 2023 (UTC) DoublePendulumAttractor — 17:48, 05 May 2023 (UTC) Metafire18 — 12:55, 21 August 2023 (UTC) applsdev — 18:44, 25 September 2023 (UTC) Cupkake4Yoshi — 06:54, 26 October 2023 (UTC) Eniehack — 07:56, 07 November 2023 (UTC) RampantSpirit — 17:59, 11 November 2023 (UTC) Macocobovi — 07:35, 22 November 2023 (UTC) EdoAug — 17:10, 02 January 2024 (UTC) Keplersj — 20:53, 10 February 2024 (UTC) Arlo Barnes — 23:48, 10 March 2024 (UTC) Odjob16 — 16:24, 21 June 2024 (UTC) CommanderKefir — 14:57, 17 September 2024 (UTC) Athayahisyam — 03:10, 15 October 2024 (UTC) SuperUltraHardCoreGamer — 11:25, 25 November 2024 (UTC) MicroTato — 15:13, 17 September 2025 (UTC) Jwillikers — 18:34, 24 October 2025 (UTC) Jakub Vrána — 6:38, 29 January 2026 (UTC)[reply]
Notified participants of WikiProject Video games--Trade (talk) 21:52, 3 September 2024 (UTC)[reply]

Discussion

Comment is this really within Wikidata:Scope? You can only look this up from the game data which makes this original research. Also how do you compare this across games? 100 hitpoints might be a lot for one game and not so much for a game where the weapons kill you at first shot. Matthias M. (talk) 21:58, 3 September 2024 (UTC)[reply]
It can also be referenced from wikis about the game. Original research isn't the only option. -wd-Ryan (Talk/Edits) 22:01, 3 September 2024 (UTC)[reply]
@Wd-Ryan: Are you referring to Fandom/Wikia wikis and other player-maintained wikis? These are considered unreliable (due to it being user-generated content) on many other Wikimedia projects. Is this "allowed for" on Wikidata? EdoAug (talk) 22:48, 3 September 2024 (UTC)[reply]
I'm not sure if it makes the statement ineligible for inclusion altogether, but most identifiers can be entered as a reference. These websites, however, do not make the subject of the item notable. Either way, it isn't accurate to say health points wouldn't be found in any other external resource. For example, this random news article I quickly found references hitpoints (Not that this specific one is applicable).

I'd also be fine with having this data in an existing property if there's a good one. -wd-Ryan (Talk/Edits) 23:11, 3 September 2024 (UTC)[reply]
If someone for whatever reason wishes to ban Fandom as a source then this is not the right place to discuss it anyways Trade (talk) 22:30, 5 September 2024 (UTC)[reply]

Wikidata has no general policy that declares player-maintained wikis to be unreliable. In practice it depends on the individual source. When it comes to information about these statistics I would expect those Wikis to be very reliable. ChristianKl ❪✉❫ 19:35, 22 September 2024 (UTC)[reply]

Naturally in some games 100 hitpoints will be a lot and in others very little. This is an issue of scaling and balancing and not something that affects the truthness of the statement Trade (talk) 22:41, 3 September 2024 (UTC)[reply]
Comment This could be used on all items of Minecraft mobs. -wd-Ryan (Talk/Edits) 22:02, 3 September 2024 (UTC)[reply]
Comment What about using properties such as has characteristic (P1552) (or something similar) and quantity (P1114) for the plethora of (video, board, role-playing) game attributes? A similar property is personality trait of fictional character (P9652). EdoAug (talk) 22:34, 3 September 2024 (UTC)[reply]
How about we just widen the scope to include board and role-playing games? Trade (talk) 22:50, 3 September 2024 (UTC)[reply]
@Trade: I'm referring to other types of attributes, such as strength, charisma, armour, running speed, mana, agility, dexterity, and the many other traits that characters may have in video games (but also other types of games), as well as health (and damage). Instead of creating bespoke properties for these, why not just have one for "gameplay trait of fictional character or item", or just use one of the aforementioned properties (and qualifier)? EdoAug (talk) 22:58, 3 September 2024 (UTC)[reply]
Mechanics such as hit points and damage are largely universal across game genres and (arguable) inherent to most of them. Being able to spend skill points across multiple attributes for your characters is not Trade (talk) 23:17, 3 September 2024 (UTC)[reply]
Not all usage of other attributes include spending skill points. Health and damage are not static numbers, either – many non-player characters in RPG video games have an ever-changing array of numbers, such as Jaina Proudmoore (Q819585), whose health is different in various expansions of World of Warcraft, as well as spin-off games such as Heroes of the Storm and Hearthstone, where her damage and mana (resource) is also relevant.

I am simply offering an alternative way of portraying these numbers in a way that may include a wider spectrum of similar traits. I don't really think specific properties are necessary, but I'm not too opposed to them either. I think it would be better to have a more open-ended property that would accommodate for multiple types of statistics (including health and damage... and mana, agility, running speed, level, et cetera). EdoAug (talk) 23:28, 3 September 2024 (UTC)[reply]
I agree we need a property with a wider scope, there's going to be plenty of stats that only apply to items from specific games so a general purpose property in the same area as has characteristic (P1552) would likely work best. Taking Pokémon items as an example (I believe we have over 1000 of those at this point) it would be advantageous to be able to provide their base statistics: HP, Attack, Defense, Special Attack, Special Defense and Speed. Since these stats are quite relevant to gameplay it should be easy to find sources without having to resort to fan wikis. --Lewis Hulbert (talk) 02:22, 4 September 2024 (UTC)[reply]
I agree with you, Lewis. Some kind of "has statistic" property with a number data type and units for each statistic type. (health point, attack point, etc.) -wd-Ryan (Talk/Edits) 17:15, 4 September 2024 (UTC)[reply]
That's something along the lines I meant. EdoAug (talk) 17:25, 4 September 2024 (UTC)[reply]
@EdoAug, @Lewis Hulbert, @Matthias M., @Wd-Ryan, would you like to give your opinions? Regards, ZI Jony ^(Talk) 19:21, 16 September 2024 (UTC)[reply]
We need some kind of scope for that type of property to work. Otherwise it just becomes an unworkable mess Trade (talk) 14:49, 18 September 2024 (UTC)[reply]
Oppose This type of data belongs in a specific fan wiki. The numbers aren't meaningful to non-players. Dexxor (talk) 00:02, 4 September 2024 (UTC)[reply]
Wikidata is contributed by people active in different topics and have very different goals of contribution, so "not meaningful to non-players" is not a good reason against it. However we does have a Wikia equalvent of Wikidata (Wikibase Cloud), so I have no position for or against the property.--GZWDer (talk) 11:20, 4 September 2024 (UTC)[reply]
The values are only comparable within other actors of the same game so a per game https://wikiba.se/ is the only option that makes sense to me. I am biased because I think this is the equivalent of en:WP:GAMECRUFT and I am not at all interested in these values as well. Matthias M. (talk) 19:28, 16 September 2024 (UTC)[reply]
There are plenty of property proposals that doesnt interest me. Doesnt mean that it somehow doesnt belong on Wikidata Trade (talk) 11:39, 18 September 2024 (UTC)[reply]
Actually, this whole proposal process is mostly not about validity, but if people find it interesting. You can also get rejected when nobody replies. Also note that I did not vote against your proposal even though I raised concerns. On Wikipedia this kind of content would be removed and Fandom wiki (Q106513246) took over the niche. Maybe this wants to live in a Wikidata instanced hosted by Fandom, Inc. (Q20466202) instead? I am not sure where to draw the line and if this has been discussed already. I think even video game character classes like Sniper (Q128164668) and Sniper (Q56363410) are a bit of a stretch of what I assume this website is about. Matthias M. (talk) 09:54, 21 September 2024 (UTC)[reply]
"Actually, this whole proposal process is mostly not about validity, but if people find it interesting." Dunno. If i were to oppose any identifiers for scholarly papers with the reasoning that the subject bored me i can imagine it would get some push back

Either way i think it would be beneficial for both of us if we had something like Wikidata:Arguments to avoid in property proposals Trade (talk) 18:20, 21 September 2024 (UTC)[reply]
The thing with these numbers is that they are not comparable across game franchises. I can't imagine a situation where you would want to query for them on Wikidata instead of processing a table of health values collected by fans of the game, especially considering it's unrealistic to create items for every game entity that has health points. While there's nothing wrong with this property per se, we also need to take into account whether it's useful (external identifiers are often useful because they help with disambiguation and data reconciliation). Dexxor (talk) 21:51, 21 September 2024 (UTC)[reply]
I cant imagine a situation where someone would want to compare health points across completely different games in the first place. If one wishes to query this property, limiting the results to characters from specific works or franchises shouldn't be too hard Trade (talk) 16:43, 24 September 2024 (UTC)[reply]

"not meaningful to non-players" is not a good reason against. -- Jerimee (talk) 23:47, 3 October 2024 (UTC)[reply]
Support (without comment) Jerimee (talk) 23:47, 3 October 2024 (UTC)[reply]
Comment So far, fictional objects have been primarily modeled based on lore/story information, like we would describe/model a real object. So the focus was mostly on the fiction aspect, not the specific technical implementations in games or other works. But health points, damage, mana, strength, dexterity or number of weapon slots are purely gameplay-specfic technical details that developers apply to game characters for gameplay and balancing-related reasons and don't necessatily correlate with their lore-version. Adding properties like this and the other proposals could IMO shift the focus of the items to the rather specific, purely technical details of individual implementations. --2A02:810B:581:C300:6C68:1127:8BA5:DCF9 17:26, 8 October 2024 (UTC)[reply]
As long as the properties are broad enough to be able to be applied to a wide range of fiction items i don't think it's an issue. As it is, hitpoints is a fairly generic statistic that exists in virtually all games featuring combat Trade (talk) 06:46, 23 November 2024 (UTC)[reply]
Comment How would this work for characters with variable health points? For example, Nick Valentine (Q107028136) of Fallout 4 has health points which are dependent on player level. His HP is calculated as follows: 225 + (([Player Level] - 10) × 5). 1857a (talk) 23:59, 29 October 2024 (UTC)[reply]
I would just stick with the base HP. People can read the fandom page themselves if they want to calculate something more specific Trade (talk) 06:47, 23 November 2024 (UTC)[reply]
Oppose Info belongs on a fan site IMO. Infrastruktur (talk) 14:24, 11 February 2025 (UTC)[reply]
Support Had the same in my mind, useful to compare within a fictional universe :) --PantheraLeo1359531 (talk) 10:47, 21 February 2025 (UTC)[reply]

@PantheraLeo1359531, Jerimee: Could you please explain the reason behind your support because it is not at all obvious. Why is this even remotely useful for Wikidata? Infrastruktur (talk) 10:57, 21 February 2025 (UTC)[reply]

Hitpoints are an elementary principle in games and are a fundamental property to characters (giving one aspect of power compared to enemies/other units). It creates a bridge to more gaming-specific elements and users. Having several values make it possible to create comparative lists of characters within a game. Adding hitpoints gives more information about unit balancing of a game (which is also useful in scissors-stone-paper games like Age of Empires games) --PantheraLeo1359531 (talk) 11:06, 21 February 2025 (UTC)[reply]

Remotely useful? That's not a very high benchmark. It is a numeric characteristic and numbers provide a way to compare and identify things. The HP concept is readily identifiable to many people worldwide. Digital game culture is ubiquitous, and an HP stat is a primary metric for many game objects. Play is a human activity, and wikidata provides information about and for human activities. Jerimee (talk) 14:46, 21 February 2025 (UTC)[reply]

+1 --PantheraLeo1359531 (talk) 16:59, 21 February 2025 (UTC)[reply]

Support. I'm a little mixed on this one but ultimately I do think it has some value and meets WD:N criterion #2. Could be useful to display in a list of characters (especially nice for sorting the list by strength), could be useful for queries like "list the strongest NPCs from every game on the Nintendo 64", etc. –IagoQnsi (talk) 02:34, 12 August 2025 (UTC)[reply]
Oppose Importing raw data from game rules with no credible sources is not adding quality content. Especially as it can't be compared across different video games this is not a good way to model it in a generic database. Ask Fandom (Q17459) if they want to host this for your favorite franchises instead. Matthias M. (talk) 20:05, 19 August 2025 (UTC)[reply]
You can't compare hit points one-to-one between games, but you can still use them to make interesting comparisons. You can use them to see which characters are the strongest/weakest in each game, so you could perhaps have a list of games and show the strongest characters for each game. You can also use normalization to do comparisons between games; you could calculate a ratio of a character's HP to the player's HP, or to the strongest character's HP, or the weakest character's HP, or the average of all characters' HP. Then you could say "CharacterA from Game1 is 1.2x stronger than the average character in Game1, and CharacterB from Game2 is 1.5x stronger than the average character in Game2, so CharacterB would seem to slightly stronger than CharacterA." –IagoQnsi (talk) 20:29, 21 August 2025 (UTC)[reply]
That is still too simple, as most games have different types of armor that lower the effectiveness of weapons and different damage types. You can't just normalize the hitpoints. Game rules are much more complex. If you want to find out who the strongest character in a game is, then using WikiBase for it might be overkill. Matthias M. (talk) 14:12, 22 August 2025 (UTC)[reply]

We do not list the "effectiveness of weapons and different damage types" on Wikidata so this will have no effect on this property Trade (talk) 21:11, 24 August 2025 (UTC)[reply]
Support I think references should be mandatory for this property --Tinker Bell ★ ♥ 17:26, 3 October 2025 (UTC)[reply]

‎game attributes

Under discussion

Description	metric to what extent a character in a role-playing game (or game with role-playing elements) possesses a specific natural, in-born characteristic common to all characters in the game
Represents	character attribute (Q135772042)
Data type	Item
Domain	item, video game character (Q1569167)
Example 1	Miku (Q135841477)‎game attributeStrength (Q130215603)numeric value (P1181)"5"
Example 2	Alte (Q135770689)‎game attributeATK (Q135772235)numeric value (P1181)"0"applies to work (P10663)100% Orange Juice (Q44292046)
Example 3	Aiko Takahashi (Q134955019)‎game attributeCharisma (Q133504320)numeric value (P1181)"6"
Allowed values	subclasses or instances of character attribute (Q135772042)
Wikidata project	WikiProject Video games (Q8485882)

Motivation

--Trade (talk) 01:05, 28 August 2025 (UTC)[reply]

Discussion

How does this look? @IagoQnsi, Valentina.Anitnelav:--Trade (talk) 01:07, 28 August 2025 (UTC)[reply]

Support ―Applsdev (talk) (contribs) 05:51, 28 August 2025 (UTC)[reply]
Nicereddy — 13:40, 04 May 2015 (UTC) Danrok — 18:20, 30 October 2015 (UTC) Lewis Hulbert — 20:26, 13 December 2017 (UTC) Santer — 22:03, 26 May 2018 (UTC) Kirilloparma — 00:30, 5 August 2018 (UTC) Cwf97 — 18:33, 22 October 2018 (UTC) YotaMoteuchi — 08:09, 22 May 2019 (UTC) CptViraj — 02:49, 17 September 2019 (UTC) BugWarp — 23:19, 26 October 2019 (UTC) WikiSyn — 21:52, 26 December 2019 (UTC) Cynde Moya — 16:07, 31 March 2020 (UTC) Dexxor — 14:51, 02 May 2020 (UTC) Floyd-out — 09:14, 22 July 2020 (UTC) Jean-Frédéric — 11:22, 11 September 2020 (UTC) A particle for world to form — 11:15, 17 May 2021 (UTC) Dollarsign8 — 01:40, 01 November 2021 (UTC) Wd-Ryan — 02:20, 03 October 2022 (UTC) Master Of Ninja — 17:37, 18 October 2022 (UTC) Matthias M. — 09:28, 12 February 2023 (UTC) VGPaleontologist — 21:03, 12 February 2023 (UTC) Tomodachi94 — 18:34, 26 February 2023 (UTC) thgiex — 12:17, 6 April 2023 (UTC) DoublePendulumAttractor — 17:48, 05 May 2023 (UTC) Metafire18 — 12:55, 21 August 2023 (UTC) applsdev — 18:44, 25 September 2023 (UTC) Cupkake4Yoshi — 06:54, 26 October 2023 (UTC) Eniehack — 07:56, 07 November 2023 (UTC) RampantSpirit — 17:59, 11 November 2023 (UTC) Macocobovi — 07:35, 22 November 2023 (UTC) EdoAug — 17:10, 02 January 2024 (UTC) Keplersj — 20:53, 10 February 2024 (UTC) Arlo Barnes — 23:48, 10 March 2024 (UTC) Odjob16 — 16:24, 21 June 2024 (UTC) CommanderKefir — 14:57, 17 September 2024 (UTC) Athayahisyam — 03:10, 15 October 2024 (UTC) SuperUltraHardCoreGamer — 11:25, 25 November 2024 (UTC) MicroTato — 15:13, 17 September 2025 (UTC) Jwillikers — 18:34, 24 October 2025 (UTC) Jakub Vrána — 6:38, 29 January 2026 (UTC)[reply]
Notified participants of WikiProject Video games--Trade (talk) 01:09, 28 August 2025 (UTC)[reply]
Comment Can you elaborate a bit? The motivation section is empty. I think stats (Q130215587) is a weird item as only links to a https://community.fandom.com/wiki/w:c:woh:Category:Stats for one video game World of Horror (Q64026226) so it is not a general term. character attribute (Q135772042) was just created for this proposal and is not an established term. Matthias M. (talk) 07:56, 28 August 2025 (UTC)[reply]
@Matthias M.:--Trade (talk) 23:02, 28 August 2025 (UTC)[reply]

I updated the item to the corect one Trade (talk) 18:30, 28 August 2025 (UTC)[reply]
You are trying to generalize en:Statistic (role-playing games) now, which is a term used only in RPGs. Note that the article establishing it is also underreferenced. Matthias M. (talk) 09:08, 29 August 2025 (UTC)[reply]
Have there ever been a data property proposal related to fiction that you didn't oppose? Some of the comments that you have made before seems to imply that you oppose the creation of in-universe data statements out of principle Trade (talk) 23:18, 29 August 2025 (UTC)[reply]
I am indeed concerned with scope but also with data quality. You want to import data from a single game; however, this proposal wishes to generalize it to a Wikidata-wide property and fails. For example, ATK (Q135772235) does not even explain what it is. The name implies an attack strength. How does it work? Why does it only apply for this game? It does have no references so it could be deleted anytime if the notability rules were enforced. I am not the only one that is concerned. I'd say stop submitting data here where the Wikipedia counterpart would only be accepted at Fandom as a rule of thumb. Matthias M. (talk) 14:41, 31 August 2025 (UTC)[reply]

So far you have not proposed a term that you believe to be correct. Nor have you proposed a better way that this could modeled on Wikidata Trade (talk) 23:30, 29 August 2025 (UTC)[reply]
Personal attacks against me don't count as arguments. Matthias M. (talk) 13:54, 31 August 2025 (UTC)[reply]
Oppose The examples used are ATK (Q135772235) and Strength (Q130215603) are all items for stats specific for one game. It would mean the creation of multiple items for each game (or game series) that we have, and I don't think that that level of granularity is useful. Looking at it, the property examples gives stats that appear static, which in many games that is not true. I don't think that a property like this would be useful for Wikidata. DoublePendulumAttractor (talk) 14:40, 28 August 2025 (UTC)[reply]
There are plenty of games franchises that share attributes across entries. These i listed in examples are just those that i am currently playing Trade (talk) 23:02, 28 August 2025 (UTC)[reply]
Oppose It is a generalization of Wikidata:Property proposal/health points and Wikidata:Property proposal/damage but conceptually it shares the same problems. You can't compare across games. It will be difficult to find credible sources to reference these numbers. I am not a native speaker, but I think "game stat" is also not an established term. Matthias M. (talk) 09:03, 29 August 2025 (UTC)[reply]
At no point did i ever said or imply that this was supposed to replace or serve the same purpose as these two previous proposals. Please retract that claim because it's flat out not true Trade (talk) 23:20, 29 August 2025 (UTC)[reply]
I also wanna point out that me (and others) have already responded to the claim about comparing stats across games multiple times. Please re-read the responses that you have been given previously Trade (talk) 23:26, 29 August 2025 (UTC)[reply]
Your previous proposal have a lot of opposition so maybe you should have re-read them. Matthias M. (talk) 14:46, 31 August 2025 (UTC)[reply]

From previous discussion @PantheraLeo1359531:--Trade (talk) 23:40, 29 August 2025 (UTC)[reply]
Thanks for pinging! The "game stat" sounds like an umbrella term, I could only imagine this to be useful if you have very many game stats you want to group. --PantheraLeo1359531 (talk) 09:20, 30 August 2025 (UTC)[reply]
What would you rather call the property Trade (talk) 17:27, 30 August 2025 (UTC)[reply]
Comment If this does go through, I would prefer we have unified values (i.e. one ATK or "attack point" item for all games). -wd-Ryan (Talk/Edits) 01:30, 1 September 2025 (UTC)[reply]
The term ATK do not necessarily carry the same meaning or function across hundreds of games Trade (talk) 23:16, 3 September 2025 (UTC)[reply]
Support Games and game related items are not really my domain, but from an "outsider perspective" these attributes seem quite useful to characterise game characters (which are in Wikidata's scope). The generalisation (from health/hit points) and renaming to "game attribute" seems reasonable to me. In order to be comparable between games one should probably also indicate an upper bound, maybe even a lower bound (in case this isn't generally 0). I'm thinking about something like upper limit (P5448) / lower limit (P5447), but I'm not sure if these qualifiers are useable in this context (currently they require a property reference value (P5446) which is meant for medical data). In order to not repeat the maximum / minimum value at every character one could think about expressing them at the game item. - Valentina.Anitnelav (talk) 17:33, 22 September 2025 (UTC)[reply]

Just one note: I'd also prefer unified values, if possible. E.g. if a game attribute corresponds roughly to "attack point" or "strength" a general item "attack" or "strength" should be used (object named as (P1932) may be used to indicate the name of this attribute in the game). - Valentina.Anitnelav (talk) 13:46, 23 September 2025 (UTC)[reply]

Amusement ride

Written work

‎part

Under discussion

Description	exact number denoting the part of a creative work or edition
Represents	part of a work (Q88392887)
Data type	Quantity
Domain	literary work (Q7725634), version, edition or translation (Q3331189), volume (Q1238720) etc.
Example 1	Bhagabat-dharmma (Part 3) (Q125957333) → 3
Example 2	Srikanta (Part 1) (Q51528956) → 1
Example 3	Akhyanmanjari (Part 2) (Q106832935) → 2
Planned use	I will add this property to the relevant existing items, starting with the book editions present on Bangla Wikisource.
Wikidata project	WikiProject Books (Q8487081)

Motivation

We have volume (P478) to denote volumes of literary work or their editions. But we miss a property denoting part of a work (Q88392887) which is also essential for handling bibliographic metadata. Currently, due to lack of this property, we are forced to wrongly add volume (P478) instead of part, see Akhyanmanjari (Part 2) (Q106832935) for example. But when sometimes, an entity contains both volume and part, we are facing difficulty to describe that correctly. This property will help resolve all these issues. -- Bodhisattwa (talk) 07:06, 15 December 2025 (UTC)[reply]

Discussion

Comment I'm not sure we actually need this kind of properties. This lacks clarity about what it is a part of. We need an item for the whole (edition in this case?), and use qualifiers for part of (P361) like series ordinal (P1545) to note the sequence number. We would get in your example :

⟨ Bhagabat-dharmma (Part 3) (Q125957333)  

 ⟩ part of (P361) ⟨ Bhagabat-dharmma ⟩
series ordinal (P1545) ⟨ 3 ⟩

⟨ Bhagabat-dharmma (Part 2) (Q125957325)  

 ⟩ part of (P361) ⟨ Bhagabat-dharmma ⟩
series ordinal (P1545) ⟨ 2 ⟩

Also the (new) item for the whole edition would have a statement like number of parts of this work (P2635)

to see there are, say, three volumes for the whole work edition. author TomT0m / talk page 09:35, 15 December 2025 (UTC)[reply]

Comment That is another kind of a solution, for sure, but that complicates the already-complicated data model structure by adding another layer of items to link them to these items. The proposed property can be a simpler alternative. Also, these statements are fetched in different Lua modules and tools to display bibliographic data, a simple way to query can be useful there too. -- Bodhisattwa (talk) 13:42, 15 December 2025 (UTC)[reply]

Considering how many properties we have for this kind of stuffs, it's only adding complexity.

The best thing to do is to go to WikiProject Books and WikiProject Source MetaData to see if there is a standard model for this, regularity is key. And the difference between a "tome" and a "part" … it's just a wording problem, not exactly a semantic difference. author TomT0m / talk page 20:05, 15 December 2025 (UTC)[reply]

Is not edition number (P393) what you want? --Tinker Bell ★ ♥ 17:42, 15 December 2025 (UTC)[reply]
Comment series ordinal (P1545) is exactly for this purpose. If this property does move forward the property name needs to be clearer to indicate it is referring to a number in a sequence within a larger work. ArthurPSmith (talk) 20:50, 15 December 2025 (UTC)[reply]

Creative work

See also: Wikidata:WikiProject Infoboxes/works

Software products and brands, see: Wikidata:WikiProject Infoboxes/terms

headword language of dictionary

Under discussion

Description	headword language of dictionary
Data type	Item
Example 1	Muʻjam al-muṣṭalaḥāt al-ʻIlmīyah : Rūsī-ʻArabī (Q131448986) → Arabic (Q13955)
Example 2	Muʻjam muṣṭalaḥāt al-ʻilm wa-al-tiknūlūjiyā (Q130204326) → Arabic (Q13955)
Example 3	Muʽjam al-muṣṭalaḥāt al-fannīyah wa-al-ʽilmīyah wa-al-handasīyah : faransī-ʽarabī (2006) (Q123110925) → Arabic (Q13955)

definition language of dictionary

Under discussion

Description	definition language of dictionary
Data type	Item
Example 1	Muʻjam al-muṣṭalaḥāt al-ʻIlmīyah : Rūsī-ʻArabī (Q131448986) → Russian (Q7737)
Example 2	Muʻjam muṣṭalaḥāt al-ʻilm wa-al-tiknūlūjiyā (Q130204326) → English (Q1860)
Example 3	Muʽjam al-muṣṭalaḥāt al-fannīyah wa-al-ʽilmīyah wa-al-handasīyah : faransī-ʽarabī (2006) (Q123110925) → French (Q150)

Motivation

These two properties are essential in dictionaries.

headword languge of dictionary: The language from which the text is being translated.
definition language of dictionary: The language into which the text is being translated.

For example, if you're translating from Arabic to English:

headword languge of dictionary: Arabic
definition language of dictionary: English.--Mohammed Qays (talk) 13:43, 6 January 2025 (UTC)[reply]

Discussion

Support We need this property in Documentation and Arabization initiative (Q117383650), we have documented more than 500 Arabic dictionary in wikidata, and this will be very useful for us.--Michel Bakni (talk) 23:17, 6 January 2025 (UTC)[reply]
Support This property is essential for us.--Faisal ^talk 23:15, 6 January 2025 (UTC)[reply]
Support--باسم (talk) 06:47, 7 January 2025 (UTC)[reply]
Please named it "headword languge of dictionary" and "definition language of dictionary". The current name is too ambigous.--GZWDer (talk) 11:25, 7 January 2025 (UTC)[reply]
@GZWDer I said a essential for dictionaries, and not only mandatory for dictionaries, it can be used in acoustics, so I find their description and explanation accurate about their work. Mohammed Qays (talk) 14:27, 7 January 2025 (UTC)[reply]
Please do not use this property for any translated work. Previously we have a original language of film or TV show (P364) with label "original language", but the usage of it for written work are discontinued by consensus, since it is redundant with edition or translation of (P629)+language of work or name (P407). GZWDer (talk) 14:31, 7 January 2025 (UTC)[reply]
Done According to your suggestion @GZWDer Mohammed Qays (talk) 11:53, 9 January 2025 (UTC)[reply]
Support.--عبد الجليل 09 (talk) 09:55, 11 January 2025 (UTC)[reply]
Support --Sandra Hanbo (talk) 21:32, 11 January 2025 (UTC)[reply]
Comment: Alternatively we could make this imporant distinction with qualifiers like this: language of work or name (P407)Arabic (Q13955)object of statement has role (P3831)headword language and language of work or name (P407)Russian (Q7737)object of statement has role (P3831)definition language. I think this could be a better approach compared to creating very narrow language properties. Samoasambia ✎ 18:41, 13 January 2025 (UTC)[reply]

I removed the ready status since there hasn't yet been any answers to this option. Samoasambia ✎ 00:07, 5 February 2025 (UTC)[reply]
@Samoasambia I explained the topic above clearly. I don't know the purpose of disabling the creation of a Property despite the consensus among colleagues. Mohammed Qays (talk) 09:55, 5 February 2025 (UTC)[reply]
@ArthurPSmith Mohammed Qays (talk) 12:43, 28 February 2025 (UTC)[reply]

Oppose The resolution of @Samoasambia is best, less of duplicated data.--حبيشان (talk) 21:31, 5 April 2025 (UTC)[reply]

Artvee artwork ID

Under discussion

Description	Unique identifier for artworks available in the Artvee online archive, a subscription-based platform offering high-resolution public domain images
Data type	External identifier
Domain	visual artworks present in artvee.com
Example 1	Cinderella at the Kitchen Fire (Q18658481) → cinderella-at-the-kitchen-fire
Example 2	Q104370974 → femme-a-leventail-portrait-de-rejane
Example 3	Lady in Black (Q19924651) → lady-in-black-3
Planned use	To connect artworks on Wikidata with their digital reproductions on Artvee and make them easier to find
Expected completeness	always incomplete (Q21873886)
Formatter URL	https://artvee.com/dl/$1
See also	Federico Zeri Foundation image ID (P3272)

Motivation

Artvee offers high-resolution images of public domain artworks from major museums and libraries. Adding this property lets us link artworks on Wikidata to their Artvee pages, making it easier to find and use those images. Niketto sr. (talk) 10:48, 21 June 2025 (UTC)[reply]

Discussion

Comment Doesn't seem like the hash fragment of the URL (#00) does anything. Unless I'm missing something, those should be removed. –IagoQnsi (talk) 01:56, 12 August 2025 (UTC)[reply]
Done! Niketto sr. (talk) 20:46, 22 August 2025 (UTC)[reply]
@IagoQnsi:, would you like to give your opinion? Regards, ZI Jony ^(Talk) 17:35, 7 December 2025 (UTC)[reply]

‎non-free official cover art URL

Under discussion

Description	URL of a copyrighted cover image for a creative work at an authorized distributor's website
Data type	URL
Example 1	Who Will Look After the Dogs? (Q134543366)→https://f4.bcbits.com/img/a3526487161_10.jpg (via Bandcamp)
Example 2	Everything Is Tuberculosis (Q130612897)→https://play.google.com/books/publisher/content/images/frontcover/zUYpEQAAQBAJ?fife=w480-h690 (via Google Play)
Example 3	Ted Lasso (Q96407897)→https://is1-ssl.mzstatic.com/image/thumb/ageP1PYyLi7UlNiWMva32Q/1200x675.jpg (via Apple TV)
Example 4	One Piece (Q710324)→https://imgsrv.crunchyroll.com/cdn-cgi/image/fit=contain,format=auto,quality=85,width=480,height=720/catalog/crunchyroll/757bae5a21039bac6ebace5de9affcd8.jpg (via Crunchyroll)
Example 5	Minecraft (Q49740)→https://store-images.s-microsoft.com/image/apps.808.14492077886571533.be42f4bd-887b-4430-8ed0-622341b4d2b0.c8274c53-105e-478b-9f4b-41b8088210a3 (via Microsoft Store)
Example 6	Half-Life 2 (Q193581)→https://shared.fastly.steamstatic.com/store_item_assets/steam/apps/220/library_600x900_2x.jpg (via Steam)
See also	non-free artwork image URL (P6500) podcast logo URL (P10286) Commons compatible image available at URL (P4765) Wikidata:Property proposal/external image URL Wikidata:Property_proposal/Archive/7#Image Wikidata:Property_proposal/Archive/22#non-free_data_available_at Wikidata:Property_proposal/Archive/29#non-free_file_URL Wikidata:Property_proposal/Proposals_for_files

Motivation

It is, broadly speaking, common for cover art (e.g. book covers, movie posters, album art, etc) to be shown when discussing or providing info about a copyright work. Cover art is commonly made freely accessible by licensed distributors of copyrighted works. My proposal is that we include links to the cover art, with a strict requirement that the URL be one published by a legal distributor of the work (e.g. Steam, Bandcamp, Spotify, Google Play, etc). This could perhaps be enforced via a whitelist using a format constraint (Q21502404). A whitelist would limit us to only having images for works that are on certain distribution platforms, but it'd make it a lot easier to prevent misuses.

Past proposals for non-free external images have often been opposed on the basis that Wikidata has an international audience, and such content might be illegal in some countries. However, even in countries which lack an equivalent of United States fair use laws, there still exist limited exceptions to copyright for quotational, informational, educational, archival, and/or journalistic purposes. What's more, we would not be republishing the content but instead hyperlinking to an legal copy of the content; this distinction is legally significant in many countries. I don't see any good reason to believe that having this property would cause problems for Wikidata or its users. –IagoQnsi (talk) 01:17, 9 August 2025 (UTC)[reply]

Discussion

Comment I like the idea but for the examples given, data consumers are better off by taking the store ID from Wikidata and then using the store's API. For example, the Steam cover art URL can be derived from Steam application ID (P1733) so storing it would be redundant. Dexxor (talk) 14:25, 12 August 2025 (UTC)[reply]
The main problem with that is that there are a ton of stores, and it'd be a ton of work for a client to implement every single one of them. Even the ones that seem to be straightforward can have lots of weird caveats. For example, that Steam URL format doesn't work for every single game; you'll get a 404 error if you try it on, say, Rag Doll Kung Fu (Q7282779): https://shared.fastly.steamstatic.com/store_item_assets/steam/apps/1002/library_600x900_2x.jpg. Of the six examples I gave, only the URL for #2 (Google Play Books) can be safely guessed just from our existing identifiers without having to make additional queries. IagoQnsi (talk) 17:29, 12 August 2025 (UTC)[reply]
Comment I am not sure how stable those URLs are. Matthias M. (talk) 19:55, 19 August 2025 (UTC)[reply]
I can confirm from years of dealing with them that the Steam and Bandcamp URL formats are stable. I would imagine the Google Play URL is given that it's just derived from the product ID. For Apple TV, it looks like there are URLs of the same format that Internet Archive saved in mid-2022 that still work today (some URLs from back then are dead, though it looks like they were montages of 4 album covers, perhaps cover art for playlists?). For the Microsoft Store, there are archives of still-working URLs going back to at least 2017. It looks like Crunchyroll did change their URL format in 2024, but they kept the old URLs up; here's the old-style URL for the example I gave: https://www.crunchyroll.com/imgsrv/display/thumbnail/480x720/catalog/crunchyroll/757bae5a21039bac6ebace5de9affcd8.jpe. It looks like URLs in the old format that were archived in 2022 still work today, and there's an even older URL format they used 2012–2021 that also still works: https://img1.ak.crunchyroll.com/i/spire1/612f38b507e628b6777b2ba9009b6df31425939473_large.jpg

I think in general, these big streaming/distribution platforms have so many versions of their apps out in the wild that they really try to avoid killing off old URLs. IagoQnsi (talk) 20:29, 19 August 2025 (UTC)[reply]
Strong oppose We can't continue proposing nor creating non-free versions of all media properties we have, I think P6500 is an error that must not be repeated. I'll propose doing this instead: Half-Life 2 (Q193581)image (P18)unknown valueURL (P2699)https://shared.fastly.steamstatic.com/store_item_assets/steam/apps/220/library_600x900_2x.jpg. Also, I know there's a concern to link to non-free version from a libre project, so I think it would be ok if we make mandatory using copyright license (P275) as a qualifier too in these cases. --Tinker Bell ★ ♥ 06:32, 20 August 2025 (UTC)[reply]
But... the image of Half-Life 2 is not unknown. We just cannot host it in a way that can be displayed on Wikidata

"so I think it would be ok if we make mandatory using copyright license (P275) as a qualifier too in these cases" You already know these images are under a proprietary license. So do i and everyone else. What is exactly is the benefit of this qualifier? Trade (talk) 10:06, 20 August 2025 (UTC)[reply]
- Q193581->P18->somevalue does not mean that we don't known the value for the concept (image), but that we don't have a right value for that statement, since P18 only accepts Commons image URIs as values for social (all of us are here, I hope, because we want to build a libre database) and technical (Wikibase won't let us store arbitrary URIs as value) reasons (and we know P18 does not just means 'image on Wikimedia Commons' but 'image' because P1628 states P18 is equivalent to, e.g., "https://schema.org/image"). About P275: surely licensing issues are the most common, but there could be other reasons for what an image cannot be uploaded to Commons, e.g. unsupported format. After all, this 'schema' is not just for images but any external resource. In summary, we need P2699 and P275 qualifiers to express the statement: "Half-Life 2 (Q193581) has an (somevalue) image (P18) whose URI (P2699) is http://... (value for P2699) and whose license (P275) is proprietary (Q3238057)". --Tinker Bell ★ ♥ 02:00, 21 August 2025 (UTC)[reply]
I think the solution with unknown value Help/URL (P2699) is bad because people might use it with any copyrighted content and even content where it produces legal problems.

As a general principle I think we should strive to keep illegal links from being on Wikidata to produce no legal liability. Additionally, I don't want links to images that are in competition with images that can be hosted on WikiCommons to be linked in Wikidata. If someone wants to add images to Wikidata, they should have an incentive to upload the images under WikiCommons compatible license to WikiCommons.

non-free artwork image URL (P6500) is about a class of images where there's no copyright problem with having a link to the official image and where images on WikiCommons frequently aren't available for structural reasons.

This property enforces legal usage by having "authorized distributor's website" in the property description. There are also structural reasons why people won't upload their cover images to WikiCommons that are similar to the case with non-free artwork image URL (P6500).

Support to the proposal. ChristianKl ❪✉❫ 17:56, 3 October 2025 (UTC)[reply]

KCI article ID

Under discussion

Description	identifier for an article in the Korea Citation Index (KCI) database provided by National Research Foundation of Korea
Data type	External identifier
Example 1	The Activities of the Korean Language Society directly after the Liberation on August 15- from August 15. 1945 to February 1946 - (Q119346674) → ART001637687
Example 2	Effect of Biophilic-Horticultural Education on Children’s Multisensory Enhancement (Q127832718) → ART002416751
Example 3	A Study of Quality Assurance/Quality Control between Institutions for Reduced Sulfur Compounds in the Ambient Air Using Cryofocusing Thermal Desorber with GC/PFPD (Q132669540) → ART001296993
Example 4	Simultaneous Assessment of Left Ventricular Function and Coronary Artery Anatomy by Third-generation Dual-source Computed Tomography Using a Low Radiation Dose (Q91726222) → ART002554191
Source	Korea Citation Index (Q6431606)
External links	Use in sister projects: [ar] • [az] • [bn] • [de] • [en] • [es] • [fa] • [fr] • [he] • [hi] • [it] • [ja] • [ka] • [kn] • [ko] • [ml] • [mr] • [nl] • [pl] • [pt] • [ro] • [ru] • [sv] • [te] • [tr] • [ur] • [vi] • [zh] • [commons] • [species] • [wd] • [en.wikt] • [fr.wikt].
Number of IDs in source	2342745
Expected completeness	always incomplete (Q21873886)
Formatter URL	https://www.kci.go.kr/kciportal/ci/sereArticleSearch/ciSereArtiView.kci?sereArticleSearchBean.artiId=$1

Motivation

KCI Korea Citation Index (Q6431606) is South Korean national citation index and links to article pages in KCI is common in Wikipedia. Toolipo (talk) 17:06, 11 January 2026 (UTC)[reply]

Discussion

Support ArthurPSmith (talk) 20:30, 20 January 2026 (UTC)[reply]

‎Thyssen-Bornemisza work ID

Under discussion

Description	ID for works at the online gallery of the Thyssen-Bornemisza Museum
Data type	External identifier
Domain	creative work (Q17537576)
Example 1	Imaginary Numbers (Q21713169) → 972
Example 2	Saint John the Evangelist in Patmos (Q21711463) → 138
Example 3	The Dream (Q18685517) → 1132
Allowed values	number (Q11563)
Source	https://www.museothyssen.org/en/collection
Number of IDs in source	>1000
Expected completeness	eventually complete (Q21873974)
Formatter URL	http://www.museothyssen.org/en/thyssen/ficha_obra/$1
See also	Thyssen-Bornemisza artist ID (P2431)

Motivation

This property could come in handy for the reference sections of automatically-generated summaries of artwork images at Commons. Thyssen-Bornemisza artist ID (P2431) already exists, so I don't see how this addiction wouldn't be welcome. A lot of items already have a described at URL (P973) parameter containing the URL, so it probably could be automated in some way. Hitsuji777 (talk) 20:48, 12 January 2026 (UTC)[reply]

Discussion

Support ArthurPSmith (talk) 22:04, 21 January 2026 (UTC)[reply]

General