Require enough metadata to identify the game, explain its configuration, establish publishing eligibility and reproduce a launch problem. A title, thumbnail and URL are not an adequate procurement record.
Recommended minimum fields:
| Field group | Suggested fields |
|---|---|
| Identity | Internal game ID, supplier game ID, studio, title, variant |
| Editorial detail | Mechanics, features, language, release date and release-date source |
| Configuration | Build/version where available, displayed RTP, relevant feature settings |
| Rights | Agreement reference, permitted domains, territories, asset permissions, expiry |
| Launch | Delivery method, endpoint reference, required credentials, lifecycle status |
| Evidence | Source document, retrieval date, evidence status, last human review |
| Operations | Last tested environment, result, incident reference, retirement reason |
Do not overwrite your own stable game identifier when changing suppliers. Store each supplier’s identifier as a mapping.
Separate facts supplied by a studio from editorial interpretations and automatically generated descriptions. Require a source for numerical attributes and preserve disagreements for review rather than silently selecting one value.
Metadata subscriptions also need a publication-rights check. SlotCatalog’s public commercial PDF says its data should not be published on affiliate resources and asks subscribers to identify products using the data. The document is not a current negotiated quote; obtain written confirmation before designing an affiliate publication around that feed. (slotcatalog.com)