You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Filling in system metadata by hand (description, publisher, genre, year, license, cover, and the new fields proposed in the metadata-expansion issue) is tedious and error-prone. Much of this data already exists on public sources.
What would you like to see?
A "fetch metadata" action on a game system that looks the system up on an external source and pre-fills its fields, letting the user review/edit before saving. Two proposed sources:
TTRPG Wiki — community-maintained system data.
DriveThruRPG — product/publisher data and cover art.
Flow: pick a source → search/match the system → preview fetched fields → apply selectively.
Notes / open questions
Feasibility depends on each source's API/terms — DriveThruRPG in particular may have no public API and would need scraping (respect ToS) or a manual paste-a-URL approach. Needs a research spike per source.
What problem does this solve?
Filling in system metadata by hand (description, publisher, genre, year, license, cover, and the new fields proposed in the metadata-expansion issue) is tedious and error-prone. Much of this data already exists on public sources.
What would you like to see?
A "fetch metadata" action on a game system that looks the system up on an external source and pre-fills its fields, letting the user review/edit before saving. Two proposed sources:
Flow: pick a source → search/match the system → preview fetched fields → apply selectively.
Notes / open questions
Filed for tracking.