Wikidata:Property proposal/Hardcore gaming 101 ID
Hardcore gaming 101 ID
[edit]Originally proposed at Wikidata:Property proposal/Creative work
| Description | identifier on the Hardcore gaming 101 website |
|---|---|
| Represents | Hardcore Gaming 101 (Q98713444) |
| Data type | External identifier |
| Example 1 | Outlaws (Q2302060)→132173 |
| Example 2 | Command & Conquer: Red Alert (Q388225)→115427 |
| Example 3 | The Dig (Q1411498)→15249 |
| 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 | 7048 |
| Expected completeness | eventually complete (Q21873974) |
| Formatter URL | https://www.hardcoregaming101.net/?p=$1 |
| Single-value constraint | yes |
| Distinct-values constraint | yes |
| Wikidata project | WikiProject Video games (Q8485882) |
Motivation
[edit]Hardcore Gaming 101 (Q98713444) is a Wikipedia recognized and well established source on video game history. While sadly not using numeric IDs we, however, have the opportunity to link not just games but also developers, genres, and platforms with one property. Thanks to User:Jean-Frédéric we also have a Mix-n-Match catalog already. Special:WhatLinksHere/Q98713444 indicates we already link it here, although not by standard means, which I would like to convert into proper external IDs. Matthias M. (talk) 12:13, 8 April 2025 (UTC)
Discussion
[edit]
Notified participants of WikiProject Video games by Matthias M. (talk) 12:13, 8 April 2025 (UTC)- Comment Thank you for proposing this! I would be leaning towards having this only about games, and a separate property for “tags” − as listed at http://www.hardcoregaming101.net/reviews/ (Genres, Subgenres, Company, System, Themes). I realize they would have the same formatter url, but I still think it makes sense to separate the two, because the website does make it clear these are separate concepts (on the page for a game, the tags are all listed under, well, “Tag” heading. Also, my reasoning is that the website also has series as first-class entity (see mixnmatch:5862), and these would need a different formatting URL (http://www.hardcoregaming101.net/series/$1). Does that make sense? Jean-Fred (talk) 14:23, 17 April 2025 (UTC)
- A separate property for series does make sense, but I don't think we should go with two properties that have the same formatter URL. Matthias M. (talk) 17:52, 20 April 2025 (UTC)
- I can see it go both ways ; but personally I think extIds should reflect the entity types in the databases, based on the relationships between the entity types. It’s clear to me that HG101 handles games and tags differently (one or more tags are assigned to a game, but a game is not assigned to another game) − conversely, while there are 4-5 types of tags (genres vs companies vs systems vs themes), I would not advocate for making 4 properties for these because they have the same relationship to games-entities. Jean-Fred (talk) 08:18, 30 April 2025 (UTC)
- Replaced the examples with just games. Matthias M. (talk) 06:33, 15 July 2025 (UTC)
- Thanks! Jean-Fred (talk) 07:54, 15 July 2025 (UTC)
- Replaced the examples with just games. Matthias M. (talk) 06:33, 15 July 2025 (UTC)
- I can see it go both ways ; but personally I think extIds should reflect the entity types in the databases, based on the relationships between the entity types. It’s clear to me that HG101 handles games and tags differently (one or more tags are assigned to a game, but a game is not assigned to another game) − conversely, while there are 4-5 types of tags (genres vs companies vs systems vs themes), I would not advocate for making 4 properties for these because they have the same relationship to games-entities. Jean-Fred (talk) 08:18, 30 April 2025 (UTC)
- A separate property for series does make sense, but I don't think we should go with two properties that have the same formatter URL. Matthias M. (talk) 17:52, 20 April 2025 (UTC)
- @Matthias M., Jean-Frédéric: Do I understand correctly that we are creating this property for games and leaving aside everything that is in pages for now? In the meantime, I have created a catalog in Mix'n'Match for games. Regards Kirilloparma (talk) 01:26, 17 July 2025 (UTC)
Support --Trade (talk) 07:15, 22 April 2025 (UTC)- Comment @Matthias M., Jean-Frédéric, Trade: To avoid using the same formatter URL for many properties, I suggest using numeric identifiers (see for example: game, genre, developer/publisher) and filtering out only the entries we need. There's a reason the site doesn't use a prefix like
/game,/genre,/developeror something like that, since it's typical of the API I'm already familiar with, which instead of the usual slugs, provide stable numeric identifiers (see properties like Steam Deck HQ game ID (P13489) or Gematsu game ID (P12058)). But there's a problem. Everything related to games is under the post type /posts, and everything related to the game industry (like companies, genres, etc.) is under the post type /pages, and we will have to use categories to determine what to filter out, so that when we create a catalog in Mix'n'Match, we don't get unnecessary stuff from categories like 30 (Podcast), 1364 (News), 29 (Video) and so on[1]. By the way, both post types support the universal formatter URLhttp://www.hardcoregaming101.net/?p=$1orhttp://www.hardcoregaming101.net/?page_id=$1.
- Please correct me if I'm wrong, but as far as I understand the games are in category 40 (Review), which is fine, but this is the parent category. That means that it will also include its child categories like 1229 (Anime / Film Review). It will be impossible to exclude it and we will have to mark some entries in the Mix'n'Match catalog as N/A, but I think it's not a big deal, especially since there is only one of these categories and according to this page, there's only 19 entries in it. I'm not sure about the others though. I see that some games are also available in categories such as: 320 (500-Word Indies); 41 (Game Series) btw, has nothing to do with the video game series, everything that goes into it is just video games (see [1]); 1707 (Japanese Obscurities) maybe, I don't know. So for now, perhaps such an endpoint would work for us http://www.hardcoregaming101.net/wp-json/wp/v2/posts?page=1&per_page=100&orderby=title&order=asc&categories=40,41&_fields=id,title,guid,slug,link.. What do you think?
- If everything that is in /posts can still be filtered using categories, then unfortunately the same with /pages will not work. You may find some unnecessary stuff there too, but I don't think it's critical, because it can be flagged in Mix'n'Match anyway. As for the property for a video game series, it's exactly the opposite. As you can see the site here uses a prefix
/seriesand in this case it is just a custom URL and there are no numeric identifiers in the REST API, so you can safely create a new property proposal where the formatter URL ishttp://www.hardcoregaming101.net/series/$1and use URL slugs as IDs.
- [1] There is also the idea of creating two separate properties. The first for games that can be filtered and found in /posts and the second for everything related to the gaming industry in /pages. Regards Kirilloparma (talk) 01:59, 15 July 2025 (UTC)
- Switched to WordPress numeric identifiers. This invalidates the existing mixnmatch:5863. Matthias M. (talk) 06:33, 15 July 2025 (UTC)
- Thanks for all the research into this! I’m not 100% sure about using these internal Wordpress identifiers. I’m not really convinced that they would be more stable than the slugs (if someone recreates an entry in the backend, then it would have a different WP id but it could have kept the same slug). This reminds me of MediaWiki page ID (P9675) that we only use as qualifier ; I wonder if that pattern − different properties for each wordpress site, qualified with a generic “Wordpress post ID” − could make sense here too. I can go either way though. Jean-Fred (talk) 08:00, 15 July 2025 (UTC)
- I think it would make sense to apply slugs if a database that uses the WordPress REST API like Gematsu (Q104627194) had a clear prefix (in this case
/games). By the way we already have at least 1 database with WordPress API using slugs but no prefix and that is Delisted Games ID (P12635). I don't know, but for some reason I have quite mixed feelings when databases don't use at least some prefix. It's also, as seen above, an inconvenience when it comes to creating 2 or more properties where the same formatter URL will be used.
- I think it would make sense to apply slugs if a database that uses the WordPress REST API like Gematsu (Q104627194) had a clear prefix (in this case
- I honestly don't know if it's worthwhile to use slugs whenever we come across a similar database with an available WordPress API, but I'm surprised to see the fuzzy matching phenomenon here. That's when there is an identifier that tolerates the absence of some words at the end (for example see full URL and trimmed URL; full URL and trimmed URL). That is, even if we remove some words we will be redirected correctly, but this is a partial slug match, which is in fact implemented through a search by numeric identifier. In other words, the numeric identifier is searched and then redirected to the correct, canonical URL, regardless of the accuracy of the slug (which turns out to be typical behavior of the WordPress API). Or even simpler: the numeric identifier here is the actual identifier, and the slug is mostly decorative. Regards Kirilloparma (talk) 01:28, 17 July 2025 (UTC)
- Support. Rzuwig► 12:43, 29 October 2025 (UTC)
