Linking Databases, part 1

Posted in

#1 by Yorhel
2019-08-09 at 15:07
< report >Adding more links to external resources has been on by backlog for quite a while. This update is one step in that direction.

The short version: Wikipedia links (for VNs, producers and staff entries) have been replaced with Wikidata IDs.

The longer version: Wikidata links a whole lot of different resources together, so linking to a Wikidata ID is a simple way of linking to several other places. VNDB automatically fetches those links from Wikidata and displays them on the site. These include:

- Wikipedia (English & Japanese)
- MobyGames
- GameFAQs
- VGMdb
- IndieDB
- HowLongToBeat
- AnimeCharactersDatabase
- MusicBrainz (for artists)
- Discogs (artists)

Unfortunaterly, Wikidata is not a very comprehensive database on visual novels and is also rather sparse on links to other sites than Wikipedia, but, hey, every link we can fetch automatically is a win, right? If a visual novel on Wikidata is missing some of those links, I encourage people to contribute them directly to Wikidata - they should then show up on VNDB within a day. I also plan to look into the possibility to automatically contribute VNDB links to Wikidata based on what we have - that way everyone benefits!

As the thread title suggests, I have a few more linking plans. My next goal is to add store links to releases, but I'm still figuring out the details on that.Last modified on 2020-05-27 at 08:40
#2 by Mutsuki
2019-08-09 at 17:13
< report >This is gonna sound really dumb but does it really have to be right at the top there on each page? It's far less useful than the other things at the top (e.g. developer, who's made it)
#3 by Yorhel
2019-08-09 at 17:48
< report >That's where the links have always been. But you're right, I moved them down a few rows.Last modified on 1970-01-01 at 00:00
#4 by dk382
2019-08-14 at 23:17
< report >I think during this change the developer website links were somehow removed from the producer pages. No producer page shows that link anymore.
#5 by kratoscar2008
2019-08-15 at 02:22
< report >Yeah, just noticed this. Hope its fixed.
#6 by Ninigi
2019-08-15 at 05:26
< report >Is it just me or some of the producer's homepages no longer visible because they are replaced by VNstat?

Edit: example linkLast modified on 2019-08-15 at 05:28
#7 by Yorhel
2019-08-15 at 06:06
< report >Yup, I broke that yesterday when adding support for multiple site links fetched from Wikidata. Fixed now.Last modified on 1970-01-01 at 00:00
#8 by kratoscar2008
2019-08-15 at 13:17
< report >Nice, thanks.
#9 by alto
2019-09-15 at 20:54
< report >What's the best thing to do where Wikidata (or Wikipedia itself) have the same entry for things which VNDB has separate entries for? E.g. Nexton has Rasen as an alias in Wikidata and redirects there on JP Wikipedia. Cyberworks has WendyBell as an alias and information on all the other brands on its wiki page.

Link child companies/brands to the parent wikidata? Leave them blank? Create new wikidata entries (if wikidata allows that sort of "duplication")?
#10 by lunaterra
2019-09-15 at 22:33
< report >On the reverse side, what do we do when there's multiple Wikidata entries for a single VN? Hakuouki ~Shinsengumi Kitan~ is a mess right now because it's been rereleased so many times, and some of those releases have their own Wikidata pages...

#11 by Yorhel
2019-09-16 at 07:24
< report >
What's the best thing to do where Wikidata (or Wikipedia itself) have the same entry for things which VNDB has separate entries for?
The "proper" way would be creating separate Wikidata entries (which they ought to allow, Wikidata is fed by Wikipedia articles but they can deviate from its structure where that makes sense). But that's extra work so, alternatively, leave them blank.

what do we do when there's multiple Wikidata entries for a single VN?
Uh, that *is* quite a mess. The current solution of referring to the franchise seems alright. I'm wondering if splitting that VN entry up will help clear up the relations, but that's another can of worms.


You must be logged in to reply to this thread.