Property talk:P6337

Documentation

• Start a query
• Current uses
• Statistics by class
• String length
• List of qualifiers
• Count

PCGamingWiki ID
identifier for PC video games tracked on PCGamingWiki

Applicable "stated in" value	PCGamingWiki (Q17013880)
Has quality	MediaWiki full page title (Q83336425)
Data type	External identifier
Corresponding template	Template:PCGamingWiki (Q124061701)
Domain	video game (Q7889), video game mod (Q865493), game controller (Q865422), video game console emulator (Q1196126), virtual reality headset (Q19600329), video game series (Q7058673), game engine (Q193564), video game compilation (Q16070115), video game perspective (Q125984830), video game genre (Q659563) or company (Q783794)
Allowed values	[^\s]+
Example	Half-Life 2 (Q193581) → Half-Life_2 FTL: Faster Than Light (Q4308783) → FTL:_Faster_Than_Light Portal (Q274897) → Portal Bastion (Q810662) → Bastion Star Wars: Knights of the Old Republic (Q725902) → Star_Wars:_Knights_of_the_Old_Republic Fallout 2: A Post Nuclear Role Playing Game (Q910938) → Fallout_2
Source	https://pcgamingwiki.com/wiki/Category:Games
Formatter URL	https://www.pcgamingwiki.com/wiki/$1 https://pcgamingwiki.com/wiki/$1
See also	Steam application ID (P1733), GameSpot game ID (P5494), IGN game ID (P5385), Giant Bomb ID (P5247), Internet Game Database game ID (P5794), MobyGames game ID (P11688)
Lists	Items with the most statements of this property Count of items by number of statements (chart) Items with the most statements Items with the fewest statements Count of items by number of sitelinks (chart) Items with the most sitelinks Items with the most sitelinks, but no link to one Wikipedia (sample: Welsh Wikipedia, cywiki) Items with the fewest sitelinks Most linked wikis Items with the most identifier properties Items with no other external identifier Items with no other statements Most recently created items Items with novalue claims Items with unknown value claims Usage history (total) Usage history (main statement) Chart by item creation date Mix'n'match (Report) Mix'n'match (Report) Database reports/Constraint violations/P6337 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 44,751 Main statement 40,217 out of 47,455 (85% complete) 89.9% of uses Qualifier 7 <0.1% of uses Reference 4,527 10.1% of uses
Search for values

[create Create a translatable help page (preferably in English) for this property to be included here]

Type “video game (Q7889), video game mod (Q865493), game controller (Q865422), video game console emulator (Q1196126), virtual reality headset (Q19600329), video game series (Q7058673), game engine (Q193564), video game compilation (Q16070115), video game perspective (Q125984830), video game genre (Q659563), company (Q783794)”: item must contain property “instance of (P31)” with classes “video game (Q7889), video game mod (Q865493), game controller (Q865422), video game console emulator (Q1196126), virtual reality headset (Q19600329), video game series (Q7058673), game engine (Q193564), video game compilation (Q16070115), video game perspective (Q125984830), video game genre (Q659563), company (Q783794)” or their subclasses (defined using subclass of (P279)). (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Source Filmmaker (Q4049816), Team Shanghai Alice (Q1377647)
List of violations of this constraint: Database reports/Constraint violations/P6337#Type Q7889, Q865493, Q865422, Q1196126, Q19600329, Q7058673, Q193564, Q16070115, Q125984830, Q659563, Q783794, SPARQL

Single best value: this property generally contains a single value. If there are several, one would have preferred rank (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P6337#single best value, SPARQL

Distinct values: this property likely contains a value that is different from all other items. (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P6337#Unique value, SPARQL (every item), SPARQL (by value)

Format “[^\s]+”: value must be formatted using this pattern (PCRE syntax). (Help)

List of violations of this constraint: Database reports/Constraint violations/P6337#Format, hourly updated report, SPARQL

Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P6337#Entity types

Scope is as main value (Q54828448), as reference (Q54828450): the property must be used by specified way only (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P6337#Scope, SPARQL

Label required in languages: en: Entities using this property should have labels in one of the following languages: en (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P6337#Label in 'en' language, search, SPARQL

Required qualifier “MediaWiki page ID (P9675)”: this property should be used with the listed qualifier. (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P6337#mandatory qualifier, SPARQL

This property is being used by: ru:Шаблон:Внешние ссылки en:Template:PCGamingWiki he:תבנית:PCGamingWiki de:Vorlage:PCGamingWiki Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Pattern ^([^\ ]+)\ ([^\ ]+)$ will be automatically replaced to \1_\2. Testing: TODO list

Pattern ^([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)$ will be automatically replaced to \1_\2_\3. Testing: TODO list

Pattern ^([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)$ will be automatically replaced to \1_\2_\3_\4. Testing: TODO list

Pattern ^([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)$ will be automatically replaced to \1_\2_\3_\4_\5. Testing: TODO list

Pattern ^([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)$ will be automatically replaced to \1_\2_\3_\4_\5_\6. Testing: TODO list

Pattern ^([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)$ will be automatically replaced to \1_\2_\3_\4_\5_\6_\7. Testing: TODO list

Pattern ^([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)$ will be automatically replaced to \1_\2_\3_\4_\5_\6_\7_\8. Testing: TODO list

Pattern ^([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)$ will be automatically replaced to \1_\2_\3_\4_\5_\6_\7_\8_\9. Testing: TODO list

Pattern ^([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)$ will be automatically replaced to \1_\2_\3_\4_\5_\6_\7_\8_\9_\10. Testing: TODO list

Pattern ^([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)$ will be automatically replaced to \1_\2_\3_\4_\5_\6_\7_\8_\9_\10_\11. Testing: TODO list

Pattern ^([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)$ will be automatically replaced to \1_\2_\3_\4_\5_\6_\7_\8_\9_\10_\11_\12. Testing: TODO list

Pattern ^([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)$ will be automatically replaced to \1_\2_\3_\4_\5_\6_\7_\8_\9_\10_\11_\12_\13. Testing: TODO list

Pattern ^([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)$ will be automatically replaced to \1_\2_\3_\4_\5_\6_\7_\8_\9_\10_\11_\12_\13_\14. Testing: TODO list

Pattern ^([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)$ will be automatically replaced to \1_\2_\3_\4_\5_\6_\7_\8_\9_\10_\11_\12_\13_\14_\15. Testing: TODO list

Pattern ^([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)$ will be automatically replaced to \1_\2_\3_\4_\5_\6_\7_\8_\9_\10_\11_\12_\13_\14_\15_\16. Testing: TODO list

Pattern ^([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)$ will be automatically replaced to \1_\2_\3_\4_\5_\6_\7_\8_\9_\10_\11_\12_\13_\14_\15_\16_\17. Testing: TODO list

Pattern ^([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)$ will be automatically replaced to \1_\2_\3_\4_\5_\6_\7_\8_\9_\10_\11_\12_\13_\14_\15_\16_\17_\18. Testing: TODO list

Pattern ^([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)$ will be automatically replaced to \1_\2_\3_\4_\5_\6_\7_\8_\9_\10_\11_\12_\13_\14_\15_\16_\17_\18_\19. Testing: TODO list

Pattern ^([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)\ ([^\ ]+)$ will be automatically replaced to \1_\2_\3_\4_\5_\6_\7_\8_\9_\10_\11_\12_\13_\14_\15_\16_\17_\18_\19_\20. Testing: TODO list

This property is being used by: he:תבנית:PCGamingWiki en:Template:PCGamingWiki Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Adding PCGW IDs to video games across Wikidata

I'm interested in adding PCGW IDs to Wikidata entries for video games across Wikidata. I'm currently still investigating how to best pull this off, but I'm starting by generating a list of all the PCGW articles using a Ruby script and then putting it up on Mix'n'match.

Nicereddy (talk) 22:13, 9 January 2019 (UTC)

• I've added the catalog to mix'n'match: https://tools.wmflabs.org/mix-n-match/#/catalog/2159 Nicereddy (talk) 23:25, 9 January 2019 (UTC)

• I've written a script to automatically add PCGW IDs on relevant pages when we find a match between the Steam AppIDs on the PCGW entry and the Wikidata entry: https://gist.github.com/connorshea/943ce81e8ff21abe6db7fbeaf38c3b69, I started running it but I think I got rate limited(?), so I'll have to look into this more. Nicereddy (talk) 05:36, 10 January 2019 (UTC)

• I've written up a blog post about how I've added this property to 3500+ video game items, maybe it's useful to someone :) https://connorshea.gitlab.io/blog/connecting-pcgw-and-wikidata.html Nicereddy (talk) 06:35, 13 January 2019 (UTC)

Expanding coverage

I wanted to suggest that the PCGamingWiki ID property be expanded beyond video games, to also support game engine (Q193564), video game publisher (Q1137109), video game developer (Q210167), and video game series (Q7058673).

There aren't as many engines and companies as there are games in the database, only 281 Engines (https://pcgamingwiki.com/wiki/Category:Engines), 2255 Companies (https://pcgamingwiki.com/wiki/Category:Companies), and 2048 Series (https://pcgamingwiki.com/wiki/Category:Series). Engines, at least, can easily be handled manually via Mix'n'match. Companies and Series can probably be handled to some extent in the same way. Companies (and some engines) also often have Wikipedia articles in PCGW, so they can be automatically matched that way. Series unfortunately don't have any link to Wikipedia articles, so they can't be automatically matched in that way.

For example:

• Companies: https://pcgamingwiki.com/wiki/Company:Valve_Corporation => Valve Corporation (Q193559)
• Engines: https://pcgamingwiki.com/wiki/Engine:Source => Source (Q643572)
• Series: https://pcgamingwiki.com/wiki/Series:Half-Life => Half-Life (Q752241)

I've already created a simple script that gets all the Engines on PCGamingWiki and their associated English Wikipedia article (if one exists): https://gist.github.com/connorshea/7cfbd099dceabc2b5456cd1541c83b1d, this isn't that useful alone, and due to the lack of Wikipedia articles for game engines probably can't be automatically associated, but I intend to iterate upon it and also create similar scripts for Companies and Series'.

See also my previous messages about this on the Project chat and WikiProject Video Games talk page.

Pinging the people who responded on the original property request: @Lewis Hulbert:, @Cwf97:, @Jean-Frédéric:, @Kirilloparma:, @ديفيد عادل وهبة خليل 2:, @Pintoch:

Nicereddy (talk)

I think that’s a good idea. I’m never quite sure what’s best between creating additional properties for each type (eg Q56462477#P1687) or have one property for all types (eg Giant Bomb ID (P5247) − I used to argue for the former, but User:VIGNERON convinced me otherwise. The former certainly makes things like constraints easier, but it’s a bit of ID proliferation and definitely hard to justify if the formatter URLs would be the same − which would now exactly be the case here: we can have the namespace in the ID (Engine:Source or have it in the formatter URL (and just have Source).

As I’m really on the fence, I would suggest asking on the Wikidata:Project Chat − we usually get swift answers there :)

Jean-Fred (talk) 21:02, 7 February 2019 (UTC)

@Jean-Frédéric: I actually already did ask on the project chat, though I'm not sure if you want me to ask something more specific? https://www.wikidata.org/wiki/Wikidata:Project_chat#Expanding_what_a_property_can_be_used_on? Nicereddy (talk)

@Nicereddy: 4 years later :D If that’s okay with you I will go ahead and propose 4 more PCGamingWiki properties − Series, Company, Engines, and Glossary (I notice the Store namespace too, but might not be worth it). Jean-Fred (talk) 08:54, 4 July 2023 (UTC)

@Jean-Frédéric that works for me! Go for it. Nicereddy (talk) 15:10, 4 July 2023 (UTC)

Useful queries for finding games that are missing the PCGamingWiki ID property, or other properties

The queries are all available here: https://gist.github.com/connorshea/d813cae2bad4dd72a490efe925dfb6c2

The idea is to find games that are represented in other datasets but that don't yet have a PCGW, as many of these _do_ have PCGW IDs but haven't been associated with their respective Wikidata item yet. These should be relatively easy to repurpose for other properties if any wants to use them.

Nicereddy (talk) 19:55, 17 February 2019 (UTC)