Skip to content

[Asset Library] Improve asset categorization, filtering, and ranking #3498

Description

@CORCTON

Background

Some existing sprite assets have missing or incorrect categories, which limits category filtering and search ranking. The Asset Library's current People / Animals / Fantasy / UI shortcuts are suggested search terms, not filters based on extraSettings.category.

Complete the category metadata and support explicit category filtering as a foundation for further ranking improvements. Related search issue: #3489.

Scope

  • Backfill and correct extraSettings.category for existing sprites using character, item, effect, ui, and unspecified.
  • Consider AI-assisted batch classification using the original images and existing metadata. Keep uncertain results unspecified and support manual corrections.
  • Preserve original values and execution records so batch updates can be reviewed and rolled back. Avoid overwriting confirmed classifications.
  • Support category-based filtering and distinguish it from keyword search.

Open questions

  • Should AI-generated origin and official curation status be recorded separately, and how should they relate?
  • How should assets be marked or unmarked as officially curated, and who should maintain that selection?
  • Should asset cards display labels such as "AI-generated"?
  • How should official curation, character categories, and search relevance affect ranking priority?

Expected result

  • Category filtering uses asset metadata rather than requiring category words in asset names or descriptions.
  • Missing or uncertain categories are not treated as characters or other known categories.
  • Category corrections are auditable and reversible, and existing keyword search remains available.

Non-goals

Keep the existing automatic publication flow unchanged. Do not disable its entry point, introduce animation-count requirements, add publication confirmation dialogs or review workflows, or automatically publish or unpublish assets as part of the category backfill. Do not add backend parsing of SPX internals.

#3486, #3488, and goplus/builder-backend#364 previously discussed animation requirements for publication. That direction is deferred and is not part of this work. The open questions above are not implementation requirements until agreed.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions