Property talk:P6337

From Wikidata
Jump to navigation Jump to search

Documentation

PCGamingWiki ID
identifier for PC video games tracked on PCGamingWiki
Applicable "stated in" valuePCGamingWiki (Q17013880)
Has qualityMediaWiki page title (Q83336425)
Data typeExternal identifier
Corresponding templateTemplate:PCGamingWiki (Q124061701)
Domainvideo 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) or video game compilation (Q16070115)
Allowed values[^\s]+
ExampleHalf-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 (Q910938)Fallout_2
Sourcehttps://pcgamingwiki.com/wiki/Category:Games
Formatter URLhttps://www.pcgamingwiki.com/wiki/$1
https://pcgamingwiki.com/wiki/$1
See alsoSteam 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
Proposal discussionProposal discussion
Current uses
Total39,413
Main statement39,283 out of 47,455 (83% complete)99.7% of uses
Qualifier7<0.1% of uses
Reference1230.3% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
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, SPARQL
Single value: this property generally contains a single value. (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 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)
Item “platform (P400): Items with this property should also have “platform (P400)”. (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#Item P400, search, SPARQL
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

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:

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[edit]

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)[reply]

Expanding coverage[edit]

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:

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)[reply]
@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)[reply]

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

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

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)[reply]