Standardized Developer & Publisher Naming (Parent Linking)

📋 Summary

Introduce a standardized system for developer and publisher naming, including optional parent company linking to group variations under a single entity.

❗ Problem

Developer and publisher names are currently inconsistent across the database:

Multiple variations exist for the same company, for example:
- Capcom, Capcom Ltd, Capcom Co., Ltd.
No clear standard for naming conventions
Difficult to filter, search, or group games accurately
Moderators often conflict on what the “correct” name should be

This leads to fragmented data and poor discoverability.

💡 Proposal

Introduce a structured system for developer and publisher entities:

Define a standardized “primary name” for each company
Allow aliases or variations to map to that primary name
Introduce optional parent company relationships:
- For example, subsidiaries grouped under a parent entity
Apply consistent naming rules across the database
Provide guidance within moderation tools for naming decisions

🧩 Use Cases

All variations of “Capcom” are grouped under a single canonical entry
Users can filter games by a developer without missing entries due to naming differences
Subsidiaries can optionally roll up under a parent company
Moderators no longer debate minor naming differences

📦 Benefits

Improves search, filtering, and organization
Reduces duplicate or fragmented entries
Creates consistency across the database
Simplifies moderation decisions

⚠️ Considerations

Defining parent relationships can become complex
Clear boundaries are needed to avoid overcomplication
Migration of existing data will require careful handling

✅ Outcome

A standardized naming system improves data integrity and usability, making the database more reliable and easier to navigate.

Posted by AstroBob · Apr 14

Open To Community2

JoeViking245

•

Apr 15

In keeping the spirit of Historical Preservation, I feel that the Developer and Publishers primary names displayed should be their official/legal name used at the time of release of “the game”. From there, alias, a subsidiary of…, etc. can be sub-categorized.

Here, I’m using “primary name” as the legal/copyrighted name registered at the time of release. And “alias” as the umbrella or “filtered” or also-known-as name. (semantics)

An option may be to list the primary name(s) at the time of release similar to how game titles are listed with their regions, placing the alias [in brackets]. e.g. Capcom Co., Ltd. [Capcom]. This will reduce the need for [some of the] additional fields and can still be easily filtered.

3333333333333333
•
May 6
While I’m not on board with this right now, I would be if a few things were handled differently. Adding business filings isn’t the current standard for the database, and it would pile extra text onto the frontend—which is exactly what the LaunchBox project is best known for and what we’d have to filter through. On top of that, a lot of companies have weird naming quirks: they change their filings or use the same name with different legal structures. Ubisoft and Sega are perfect examples. Ubisoft goes by different legal names depending on the country, and Sega has changed its business type multiple times—if I remember right, it even switched back to an earlier filing at one point.

That said, I’d support this if we can meet a few conditions:
Give users an option to hide business filing suffixes (like SAS, Ltd., Corp.) from the front end entirely.
Use some kind of aliasing instead of a plain text field for each game’s publisher and developer.
Enforce a strict naming approach for the business filings themselves.