Wikidata:Property proposal/Metacritic game ID

From Wikidata
Jump to navigation Jump to search

Metacritic game ID[edit]

Originally proposed at Wikidata:Property proposal/Creative work

Descriptionidentifier of a video game in the Metacritic database
RepresentsMetacritic (Q150248)
Data typeExternal identifier
Template parameterTemplate:Metacritic video game (Q22672219)
Domainvideo game (Q7889)
Allowed values^[a-z\d]+(\-[a-z\d]+){0,19}$
Example 1Hogwarts Legacy (Q99397854)hogwarts-legacy
Example 2Resident Evil 4 (Q112231148)resident-evil-4
Example 3Baldur's Gate 3 (Q64441774)baldurs-gate-3
Example 4Starfield (Q55286432)starfield
Example 5Cyberpunk 2077: Phantom Liberty (Q113826614)cyberpunk-2077-phantom-liberty
Sourcehttps://www.metacritic.com/browse/game
External linksUse in sister projects: [ar][de][en][es][fr][he][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][commons][species][wd][en.wikt][fr.wikt].
Number of IDs in source182,379 (as of 19.09.2023)
Expected completenessalways incomplete (Q21873886)
Implied notabilityWikidata property for an identifier that suggests notability (Q62589316)
Formatter URLhttps://www.metacritic.com/game/$1/
See alsoMetacritic ID (P1712), OpenCritic ID (P2864)
Applicable "stated in"-valueMetacritic (Q150248)
Single-value constraintYes
Distinct-values constraintYes
Wikidata projectWikiProject Video games (Q8485882)

Motivation[edit]

This proposal is related to the discussion that was recently started. I've decided to propose a separate property following Jean-Fred's advice, and I'll explain why it's better to split the Metacritic property into several possible ones.

Okay, even before the original property was created back in 2015, it had already been suggested that it should be split into several other properties, which is quite reasonable, as it is much easier to curate and maintain individual properties than a single one, which due to its broad scope can eventually become a dumping ground of values (which is exactly what happened). However, as the discussion progressed, we can see that for some reason a consensus was reached in favor of creating one single property for everything possible (i.e. games, movies, TV series, etc.). The reason why this decision was made is unfortunately not clear. So starting from 2015 until now, the property has been used for everything possible without any strict control.

Back to our days, Metacritic updated its design and a bit of its database in September. It is from this point that certain issues arise, as Metacritic decided to get rid of the use of the platform prefix, which is definitely the right decision, but the problem is that now all links that once led to a separate page for a particular platform, point to the same game ID, thus creating unnecessary duplicates (example). The solution to this is autofix (or QS batch), but that's not the point. This proposal was primarily made in order to move all corrected identifiers from the current broad property to a separate one for games after the autofix or QS batch has been applied. It would be fine, but there were participant who did not mind going back to the outdated scheme, i.e. the scheme of using platforms, since it is still possible.

As I already mentioned in that discussion, I'm clearly against such a scheme, as it's completely unnecessary primarily due to the fact that Metacritic now uses exactly a platform-less scheme for video game identifiers and if someone wants to look at scores on a particular platform again, they can simply go to View All Platforms or All platforms section right on the game's page. Going back to platforms would be a huge step backwards in this case. What do you think?

The only place where platforms would still be useful is review score (P444) property. They are definitely needed there, but those IDs should only be used as a reference. What I mean is that we would have two properties: one would be this one, which I proposed for specifying just the video game ID without applying the still possible scheme for platforms (new format), and another, already existing one (general/broad property), which would now be applied only as a reference in P444 property. Example:

Baldur's Gate 3 (Q64441774)

Metacritic game ID (new property)
Normal rank baldurs-gate-3
0 references
add reference


add value

So basically what I'm proposing to do is to do roughly what was done with the Filmweb.pl property (as example). In other words, the current Metacritic ID (P1712) property should be split into several other separate properties. Our project, as you can see, has already started such an initiative and I strongly recommend that members of other projects like WikiProject Movies or WikiProject Music do the same. Regarding the Wikis (reusers) that are currently using a generic property. I don't think it's a problem, as switching to the new property will only make things easier and the Wikis will follow suit. Especially since we have new MobyGames property (as a prime example), which various sections of Wikipedia are slowly starting to adopt (see [1], [2], [3]).

Based on all this, what do I propose to do and what is the plan here? The plan is the following:

  • Create a new proposal for a standalone property for video games and notify project participants which has already been done.
  • Before or after this proposal will be marked as ready (if it gets support at all), correct the IDs of the current general Metacritic ID (P1712) property to the new format, i.e. from game/some-platform/some-video-game to game/some-video-game. This will either be done by me personally, or it can be done by someone else using a QS/OR batch. We could also do it, as I said, with an autofix, but we are very likely to still have various qualifiers left like platforms afterwards, so I think it would be preferable to remove the values, and a bot that does autofixes doesn't fix that.
Here's what it would look like:


Metacritic ID
to →
Normal rank game/baldurs-gate-3
1 reference
add reference


add value
  • After the IDs are moved to the new format, add the following autofixes to the talk page of the outdated property:
  • This autofix is temporal. It is required to migrate the remaining identifiers (which will not be deleted) in the references to the correct format of the now deprecated property.
Here's what it would look like:
  • After the remaining IDs in the references have been corrected, we will add this already permanent autofix, which indicates the new schema IDs that will be automatically moved from the general and outdated property to the new one when detected. In short, if someone will continue to intentionally or mistakenly add new schema identifiers to an old property, you should not worry, because the bot will automatically move them to the correct (new) one because of this autofix. Here is an example of how this autofix works in the case of MobyGames group ID (former scheme) (P5360) property.
Here's what it would look like:


Metacritic ID
from →
Normal rank game/baldurs-gate-3
1 reference
add reference


add value
Metacritic game ID (PXXXXX)
to →
Normal rank baldurs-gate-3
1 reference
Metacritic game ID (PXXXXX) baldurs-gate-3
retrieved 4 May 2024
add reference


add value
  • Once all tasks from above have been completed, migrate the adjusted IDs (but this time without the /game prefix, as it is not required here) to the new property via QS/OR batch (or bot).
Here's what it would look like:


Metacritic ID
from →
Normal rank game/baldurs-gate-3
1 reference
add reference


add value
Metacritic game ID (PXXXXX)
to →
Normal rank baldurs-gate-3
1 reference
Metacritic game ID (PXXXXX) baldurs-gate-3
retrieved 4 May 2024
add reference


add value
  • Right after creating the new property, add Wikidata usage instructions (P2559) (to the generic property) to indicate that a separate property is now used for video games and that all IDs should lead there and not to the generic one. We should also specify that the generic superseded property for video games is still allowed, but it can only be used as a reference in the review score (P444) property.
Here's what it would look like:


Wikidata usage instructions
Normal rank For video games, please use the separate PXXXXX property instead. Note that using the superseded property (i.e P1712) for video game items is still allowed, but it should now only be used as a reference in P444 property. Game IDs of the current format "game/some-video-game", which will be added to this property intentionally or by mistake, will be automatically moved to the correct one because of the autofix appended to the talk page of this property. Meanwhile, IDs of the format "game/some-video-game/critic-reviews/?platform=some-platform" or "game/some-video-game/user-reviews/?platform=some-platform" should be found strictly in references for P444 property, not in values or elsewhere. If you find such IDs, you should remove them. (English)
0 references
add reference


add value
  • Change the regex to a new one (still there in P1712 property), which should not allow the new schema value, but still allow the format game/some-video-game/critic-reviews/?platform=some-platform or game/some-video-game/user-reviews/?platform=some-platform (should only be used in references in P444 property).
  • And finally, on the discussion page of the already new property, add the following autofix, which reduces all 4 obsolete formats to the correct one. That is, all those game identifiers that will be mistakenly added (to the new property) with different unnecessary prefixes will be automatically moved to the one and correct format.
Here's what it would look like:


Metacritic game ID (PXXXXX)
from →
Normal rank game/baldurs-gate-3/critic-reviews/?platform=pc
1 reference
Metacritic game ID (PXXXXX) game/baldurs-gate-3/critic-reviews/?platform=pc
retrieved 4 May 2024
add reference


add value
Metacritic game ID (PXXXXX)
to →
Normal rank baldurs-gate-3
1 reference
Metacritic game ID (PXXXXX) baldurs-gate-3
retrieved 4 May 2024
add reference


add value

For property creators[edit]

  • I have decided to make life much easier for those who will be creating this property and thus already prepared a ready to run QS file with all the necessary values for the new property. When the property will be marked as ready and you have decided to create it, just follow that link. All you need to do is just click on the Run button, but not Run in background, because for some unknown reason properties in this mode are not created correctly. Warning! When checking this file, be extremely careful not to accidentally run this batch before its time.

Discussion[edit]

@Kirilloparma, Lewis Hulbert: Done --Trade (talk) 22:37, 2 October 2023 (UTC)[reply]