Property talk:P4685

Documentation

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

Nintendo of America Game Store ID (former scheme)
identifier for software sold on the Nintendo of America Game Store

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

Type “video game (Q7889), application (Q166142), video game expansion pack (Q209163), video game compilation (Q16070115), video game remake (Q4393107), group of video games often treated as a singular game (Q116779426)”: item must contain property “instance of (P31), subclass of (P279)” with classes “video game (Q7889), application (Q166142), video game expansion pack (Q209163), video game compilation (Q16070115), video game remake (Q4393107), group of video games often treated as a singular game (Q116779426)” 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).
List of violations of this constraint: Database reports/Constraint violations/P4685#Type Q7889, Q166142, Q209163, Q16070115, Q4393107, Q116779426, SPARQL

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

List of violations of this constraint: Database reports/Constraint violations/P4685#Unique value, hourly updated report, SPARQL (every item), SPARQL (by value)

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/P4685#Single value, SPARQL

Format “[\w\d_\-]+”: value must be formatted using this pattern (PCRE syntax). (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/P4685#Format, 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/P4685#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/P4685#Scope, SPARQL

Links no longer works

As of April 2019, it seems like the ID no longer works as it will link to a 404 page. Unless someone knows of an alternate link that works, I think the link should be deprecated. — Jeluang Terluang (talk) 18:48, 15 April 2019 (UTC)

@Jeluang Terluang: Seems that Nintendo's switched over to human-readable IDs rather than long random character strings. For instance Skyrim's Nintendo store page is now https://www.nintendo.com/games/detail/the-elder-scrolls-v-skyrim-switch/, while Pokemon Sun's is now https://www.nintendo.com/games/detail/pokemon-sun-3ds/. I guess it's a matter of just changing the IDs to the more readable versions. --Btcprox (talk) 16:04, 2 July 2019 (UTC)

While it looks like they've changed it, the ID is still stored inside each page when inspecting them but I can't find how these IDs could be linked. — Jeluang Terluang (talk) 17:05, 2 July 2019 (UTC)

I deactivated the formatter url. For futher discussion, please see Wikidata:Project_chat/Archive/2019/10#Marking_2000+_identifiers_as_deprecated_(and_add_relevant_qualifier). --- Jura 10:30, 4 November 2019 (UTC)

Bad constraints

I've taken the liberty of deprecating the current item-requires-statement constraint (Q21503247) constraints for this property. I've been running into Wii games that have distribution format (P437)digital download (Q54820071) and/or distributed by (P750)Nintendo eShop (Q3070866) statements added by a bot due these constraints, yet most Wii games only ever had a physical release (the exceptions being w:List of Wii games on Wii U eShop, and WiiWare/Virtual Console games). The issue is that the store used to have listings for physical-only games (example) where they just linked to 3rd-party retailers (possibly some were sold directly?), meaning it's incorrect to infer that anything with a store ID was digitally distributed. Is there an easy way to clean up the incorrect statements caused by these constraints? --NoInkling (talk) 09:26, 7 April 2024 (UTC)

applsdev Arlo Barnes BugWarp Coloradohusky CptViraj Cupkake4Yoshi Cwf97 Cynde Moya Danrok Datumizer Dexxor Diggr Dispenser Dollarsign8 DoublePendulumAttractor EdoAug Edolusill Eniehack Facenapalm Floyd-out FullyAwesome Harshrathod50 Jean-Frédéric Jotamide Keplersj Kirilloparma Lewis Hulbert LotsofTheories Macocobovi Macrike Master Of Ninja Matthias M. Metafire18 Nicereddy Nw520 Oduci Poslovitch Rampagingcarrot RampantSpirit Sanqui Santer Sight Contamination Sir Lothar thgiex Tomodachi94 VGPaleontologist Wd-Ryan WikiSyn YotaMoteuchi

Notified participants of WikiProject Video games: That was definitely a bad constraint, the Nintendo Game Store had identifiers for consoles with no eShop like the Wii or Nintendo DS, possibly older consoles too, I forget.

It'll probably be incredibly difficult to entirely clear this up, but querying for games that only have instance of (P31)Nintendo DS (Q170323) and/or instance of (P31)Wii (Q8079) along with distribution format (P437)digital download (Q54820071) / distributed by (P750)Nintendo eShop (Q3070866) could be a good start. --Lewis Hulbert (talk) 09:51, 7 April 2024 (UTC)

The IDs themselves commonly have a platform (P400) qualifier too which could also be used. I should have mentioned that the bot is nice enough to add references, here's a couple of example changes: [1] [2] That would presumably allow deletion of all the statements added due to these constraints, but maybe that's not desirable since there will be a bunch of items where these statements are appropriate (albeit added for the wrong reason). Out of interest, what's the typical tooling you'd use for doing a one-off batch deletion like this, QuickStatements? --NoInkling (talk) 11:10, 7 April 2024 (UTC)