Skip to content

Metadata fields as tags #287

@Seirade

Description

@Seirade

Is your feature request related to a problem? Please describe.
A lot of the current metadata fields are string-based, which prevents coordinating a standard of options. By converting them to tags, not only can they be streamlined, but also given aliases.

Describe the solution you'd like
The metadata fields should use the same, if not similar, system as tags. One concern is that with the amount of possible collisions, tag labels may need to be scoped in such a way that they don't have to be unique. Another benefit to using this would be the ability to use tag filters to remove unwanted content by default, without having to add it to the search query, such as broken games, specific developers/publishers, foreign languages, certain platforms, etc.

Describe alternatives you've considered
In order to coordinate, curators need to know all possible aliases that, for example, a developer would use. Since the developer field is a string, the full list has to be added for each curation. It would be possible to just make a big spreadsheet to keep track, but it would be inefficient and not everyone would think to check it all of the time.

Additional context
Screenshot below. Also pictured is tag icons (#275). Two types of tag icons are also pictured simultaneously for Language, but this is only for comparison purposes.

details

Some of the fields were also rearranged. Since the Developer fields would be tags, it makes more sense to put them below the Play button along with all of the other fields. Alternate Titles has been moved underneath the main title, where it feels a bit more appropriate. It might also make sense to bring Version and Release Date near the top, underneath Alternate Titles, where that information would be more relevant.

Not pictured/forgot:

  • It may be worth having alternate titles on multiple lines, similar to the other fields, so that you can see more of them at a glance, rather than truncating a large string.
  • Developer field might make more sense to be renamed to "Credits" for a more generic term.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions