Introduction
This is the page finally documenting the data model for game releases, i. e. everything that publishers throw at us.
UML overview
Property details
Game
| attribute | type | description |
|---|---|---|
| Entry Type | Data List 5 | see below |
| Description | text | A short and sweet description of what this game is about. |
| Long Description | text | A long and comprehensive description of what this game is about. |
Involved data lists:
Data List 5: Game Entry Type
| id | key | text | Comment |
|---|---|---|---|
| 1 | Game | This is the standard case. It is used for new games that don't fall under the other types of this list, or when a new release of a previously released game fulfills the different game criteria developed here. | |
| 2 | Compilation | This is the switch for game bundles. It shall only be used if two or more games are bundled together, or one game and at least one of its significant add-ons. This rule is to exclude minor compilations like included demos, or minor DLCs coming with the release. Furthermore, the compilation shall be marketed as just that, a bundle of games, and usually comes with its own title. This rule is to exclude re-releases of games with playable goodies included. The aforementioned "technical" compilations are dealt with elsewhere in the data model, at game release level. | |
| 3 | Add-on (significant) | This is the switch for full-price add-ons. It shall only be used when the release can't be played without the base game, and when it meets Oregami's significance criteria. Basically, significant add-ons will later be handled just like a normal game, i. e. will show up in default searches and game lists. | |
| 4 | Add-on (insignificant) | Releases which can't be played without a base game and do not meet the significance criteria are flagged here. These releases will be more hidden than the significant add-ons, i. e. the user will have to opt-in to see this stuff in searches and data lists. | |
| 5 | Episodic Game | ||
| 6 | Episode |
Open issues
References