Specifications

Data

The data at the core of the application is grouped into two types of nodes (predictions and realisations) and links between those nodes. For now, a realisation can only be created in relation to a prediction.

Prediction structure

field	Description	type	required
id	Unique ID for the prediction	number	automatically
source type	select from a predefined array of types: Literature, Movies, TV series, Games, other	string	required
literature_title	Title of the literary work	string	required1
literature_author	Author of the literary work	string
movie_title	Title of the movie	string	required1
movie_director	Director of the movie	string	optional
series_name	Name of the TV series	string	required1
series_season	Season number of the series	number	optional
series_episode	Episode number of the series	number	optional
game_name	Name of the game	string	required1
game_studio	Game studio who produced the game	string	optional
other_title	Title of the work	string	required1
other_creator	Person who made it	string	optional
year_published	when the source work was first published	number	optional
prediction_E	description of the prediction (limited to 300 chars), in English	string	required2
prediction_D	description of the prediction (limited to 300 chars), in German	string	required2
year_predicted	year for which the prediction is made, if available	number	optional
category	select from a predefined array of categories, like transportation, health, surveillance	string	required
more_info	hyperlink to a page where more info on the prediction can be found	string	optional
timestamp created	time when the prediction was created	date	automatically
timestamp last edited	time when the prediction was last edited	date	automatically
title	editors can assign a title to a prediction in the backend	string	optional
image	editors can attach an image to a prediction	img	optional
editors_pick	editors can highlight a prediction from the backend as editor's pick	boolean	optional

1 at least one of those properties must have a value, 2 at least on of those properties must have a value

Realisation structure

field	Description	type	required
id	Unique ID for the realisation	number	automatically
realisation_E	description of the realisation (limited to 300 chars) in English	string	required3
realisation_D	description of the realisation (limited to 300 chars) in German	string	required3
year_introduced	Year when realisation was first introduced	number	required
more_info	hyperlink to a page where more info on the realisation can be found	string	optional
image	editors can attach an image to a prediction	img	optional
timestamp_created	time when the realisation was created	date	automatically
timestamp_edited	time when the realisation was last edited	date	automatically
3 at least one of those properties must have a value

Connection structure

field	Description	type	required
node1	Endpoint one of the connection	object?	required
node2	Endpoint two of the connection	object?	required
timestamp_created	time when the connection was created	date	automatically
timestamp_edited	time when the connection was last edited	date	automatically

Categories

This list needs to be refined once we test it against our initial set of predictions

• Communication
• Energy
• Finance, Economics
• Food
• Health
• Home & Living
• Law
• Leisure
• Love, Friendship, Relationships
• Media
• Nature
• Politics
• Production
• Science
• Society
• Space
• Sports
• Surveillance
• Transportation
• War & Weaponry
• Work

URL Structure

proposed url structure would be: dystopiatracker.com/p/ + creator/ + work/ + prediction-id

eg. dystopiatracker.com/p/george-orwell/1984/id=12

Features

First, we will focus on implementing two features: A card overview of all content and the ability for users to contribute data themselves.

Card view

Predictions are displayed as cards. The user can filter the view or select a prediction.

The user can apply three filters, separately or combined

• by category (select from dropdown)
• by media type (select from dropdown)
• by work (typeahead search)

For each view (home or any filters applied), the results are displayed in two groups.

• 1-8 latest matching predictions with property editors_pick. if no matches for the given filter, don't display this section
• latest predictions

On mobile, only the category filter is displayed (and maybe the "search by work" field).

User generated content

Any user, no registration needed, can enter data, i.e. a prediction or a realisation connected to a prediction.

On all list views, there is a button that leads to the input form. On desktop, the button is placed at the top left corner of the latest predictions (see image above), on mobile the button is floating above the content fixed in the bottom right corner (see image above).

The input process is designed in a 4-step way to avoid the creation of duplicates.

1. User selects the source type.