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.